Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistent rate limit errors in HTTPClient.modify_channel #178

Open
TAG-Epic opened this issue Jan 19, 2023 · 0 comments
Open

Consistent rate limit errors in HTTPClient.modify_channel #178

TAG-Epic opened this issue Jan 19, 2023 · 0 comments
Labels
scope/nextcore.http Any changes to the nextcore.http namespace type/bug A bug fix

Comments

@TAG-Epic
Copy link
Member

Check #162 for a test case
Logs

INFO     nextcore.http.client.client:client.py:301 Requesting PATCH /channels/1065579508025020506
DEBUG    nextcore.common.times_per.times_per:times_per.py:137 Releasing 0 requests
DEBUG    nextcore.http.client.client:client.py:313 Response status: 429
DEBUG    nextcore.common.dispatcher:dispatcher.py:439 Dispatching event request_response
INFO     nextcore.http.client.client:client.py:356 Exceeded rate-limit on shared route! (None1065579508025020506NoneNonePATCH/channels/{channel_id})This is not unexpected as shared rate-limits are shared by multiple users (and therefore, are out of our control). This does not count towards a cloudflare ban. Retry after: 1.667
DEBUG    nextcore.common.times_per.times_per:times_per.py:86 Calculated remaining: 49
DEBUG    nextcore.common.times_per.times_per:times_per.py:87 Reserved requests: 0
INFO     nextcore.http.client.client:client.py:301 Requesting PATCH /channels/1065579508025020506
DEBUG    nextcore.http.client.client:client.py:313 Response status: 429
DEBUG    nextcore.common.dispatcher:dispatcher.py:439 Dispatching event request_response
INFO     nextcore.http.client.client:client.py:356 Exceeded rate-limit on shared route! (None1065579508025020506NoneNonePATCH/channels/{channel_id})This is not unexpected as shared rate-limits are shared by multiple users (and therefore, are out of our control). This does not count towards a cloudflare ban. Retry after: 1.268
DEBUG    nextcore.common.times_per.times_per:times_per.py:86 Calculated remaining: 48
DEBUG    nextcore.common.times_per.times_per:times_per.py:87 Reserved requests: 0
INFO     nextcore.http.client.client:client.py:301 Requesting PATCH /channels/1065579508025020506
DEBUG    nextcore.http.client.client:client.py:313 Response status: 429
DEBUG    nextcore.common.dispatcher:dispatcher.py:439 Dispatching event request_response
INFO     nextcore.http.client.client:client.py:356 Exceeded rate-limit on shared route! (None1065579508025020506NoneNonePATCH/channels/{channel_id})This is not unexpected as shared rate-limits are shared by multiple users (and therefore, are out of our control). This does not count towards a cloudflare ban. Retry after: 1.044
DEBUG    nextcore.common.times_per.times_per:times_per.py:86 Calculated remaining: 47
DEBUG    nextcore.common.times_per.times_per:times_per.py:87 Reserved requests: 0
INFO     nextcore.http.client.client:client.py:301 Requesting PATCH /channels/1065579508025020506
DEBUG    nextcore.http.client.client:client.py:313 Response status: 429
DEBUG    nextcore.common.dispatcher:dispatcher.py:439 Dispatching event request_response
INFO     nextcore.http.client.client:client.py:356 Exceeded rate-limit on shared route! (None1065579508025020506NoneNonePATCH/channels/{channel_id})This is not unexpected as shared rate-limits are shared by multiple users (and therefore, are out of our control). This does not count towards a cloudflare ban. Retry after: 0.827
DEBUG    nextcore.common.times_per.times_per:times_per.py:86 Calculated remaining: 46
DEBUG    nextcore.common.times_per.times_per:times_per.py:87 Reserved requests: 0
INFO     nextcore.http.client.client:client.py:301 Requesting PATCH /channels/1065579508025020506
DEBUG    nextcore.common.times_per.times_per:times_per.py:137 Releasing 0 requests
DEBUG    nextcore.http.client.client:client.py:313 Response status: 429
DEBUG    nextcore.common.dispatcher:dispatcher.py:439 Dispatching event request_response
INFO     nextcore.http.client.client:client.py:356 Exceeded rate-limit on shared route! (None1065579508025020506NoneNonePATCH/channels/{channel_id})This is not unexpected as shared rate-limits are shared by multiple users (and therefore, are out of our control). This does not count towards a cloudflare ban. Retry after: 0.422
DEBUG    nextcore.common.times_per.times_per:times_per.py:86 Calculated remaining: 49
DEBUG    nextcore.common.times_per.times_per:times_per.py:87 Reserved requests: 0
INFO     nextcore.http.client.client:client.py:301 Requesting PATCH /channels/1065579508025020506
DEBUG    nextcore.http.client.client:client.py:313 Response status: 429
DEBUG    nextcore.common.dispatcher:dispatcher.py:439 Dispatching event request_response
INFO     nextcore.http.client.client:client.py:356 Exceeded rate-limit on shared route! (None1065579508025020506NoneNonePATCH/channels/{channel_id})This is not unexpected as shared rate-limits are shared by multiple users (and therefore, are out of our control). This does not count towards a cloudflare ban. Retry after: 0.085
@TAG-Epic TAG-Epic added scope/nextcore.http Any changes to the nextcore.http namespace type/bug A bug fix labels Jan 19, 2023
@TAG-Epic TAG-Epic moved this to TODO in Nextcore Jan 19, 2023
@TAG-Epic TAG-Epic moved this from TODO to Pending review in Nextcore Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/nextcore.http Any changes to the nextcore.http namespace type/bug A bug fix
Projects
Status: Pending review
Development

No branches or pull requests

1 participant