Modifica/rimozione limite di velocità API con creazione categoria

Sviluppatore
1

Sto riscontrando un problema con la creazione di categorie tramite API. Sembra esserci un limite, ma questo non sembra essere personalizzabile e non sembra esserci alcuna impostazione per disabilitarlo.

L’errore che ricevo è: Abbiamo un limite giornaliero su quante volte può essere eseguita questa azione. Attendi 17 secondi prima di riprovare.

Il numero di secondi sembra essere sempre inferiore a 20 secondi, ma non è mai accurato, dato che viene indicato come un limite giornaliero e ho provato entro un minuto dal tentativo precedente. Ho anche provato a regolare TUTTI i limiti di velocità nella dashboard di amministrazione a 1000+, ma nessuno di essi sembra influenzare la creazione di categorie.

I limiti di velocità disponibili nella dashboard sono: topic massimi, messaggi privati, like, segnalibri, segnalazioni, modifiche, inviti, inviti ai topic, topic, stampe e accessi.

Sto utilizzando GitHub - discourse/discourse_api: Ruby API for Discourse · GitHub per questo scopo, che funzionava correttamente fino al raggiungimento del limite di velocità non specificato.

Sto dimenticando qualcosa? Il messaggio non proviene da nginx, poiché proviene da Discourse e il template di limitazione della velocità per nginx è stato disabilitato.

2

See:

3

Thanks @sam, not sure how I missed that!

4

No worries, I have meant to make that post for a while @mpalmer asked for it a few weeks ago ;p

@community FYI ^^^

5

Ahh, it’s new, didn’t notice that either. Not on top of it today I guess…

I’m only performing one request though to create a category and don’t see any daily limits there. Is there another limit that would be attributing to the 429 error?

6

Well first thing I would try is another API endpoint to see if this is the global rate limit or some specific rate limit on category creation (or maybe a user rate limit in the app), be sure your api_username is an admin

7

Using ‘system’ and the key was generated via the admin dashboard. It don’t have an issue grabbing the category list, only creating a category.

8

Not seeing anything particular in the app, I would try a different admin user to see what happens, maybe the error you are getting is a different limit.

9

Tried another user and a generic key for all users, but both hit the same 429 error and limit when trying to create a category.

10

Is there anything in the response body you are receiving?

11

Just the error message:

 {"errors"=>["We have a daily limit on how many times that action can be taken. Please wait 21 seconds before trying again."], "error_type"=>"rate_limit"} (DiscourseApi::TooManyRequests)
12

Are you 100% sure nothing is stuck in some sort of a loop hitting the server?

Also are you running latest version of Discourse?

Does it come back with 21 seconds every time?

13

Running 2.0.0.beta1. Not aware of anything looping, only I have access to these keys and the script that runs them is ran manually by me as I’m developing something to automate creating categories. I have 1 call to get the existing category lists, then one call per category creation (only 1 category right now). It has worked to create most of the categories before the rate limit got hit.

The ‘seconds’ varies; often 12, 17, 21, or other amount around that amount.

14

What happens if you disable the global admin api rate limit (raise it to say 500 a minute and 500 per ten seconds)? Does this go away?

I would guess that something about your script is pummeling too many requests at the server.

15

Yup… you appear to have been right! A variable wasn’t being set when it needed to be, so it was bypassing a check I had. Seems to be working fine now, no hammering the API anymore. Still good to know the info you posted though, so I appreciate that.

16

Hey @sam, could you point me to where I can disable the global admin api limit? I have a script to pull response times that requires getting all the topics in a timeframe and then for each topic, getting all of the posts for the topic, and I keep running into the rate limiting (You’ve performed this action too many times. Please wait 6 seconds before trying again.').

Apologies if this old thread i dug up is now really out of date :smiley:

17

Are you 100% sure it is not covered in: