Circumvent the rate limits on the API requests #65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
|
Here's a test where I set the rate limit of the API requests to 5. If you like those colours, this is how it would end up looking like.
Here's the colourless variant otherwise. While you are free to review this pull request, please note that I have yet to write some test cases for the newly added functionality so this pull request cannot be merged yet. |
gridhead
force-pushed
the
ratecirc
branch
2 times, most recently
from
451d290
to
7d3beeb
Compare
Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
This stalls the transfer for the time period proposed in the standard configuration (which is 60 by default) and resets the index counter to 0 when it reaches the amount proposed in the standard configuration (which is 500 by default) Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
For any HTTP request of type POST or PUT, the index counter is incremented by 1 to ensure that the attempts are kept track of to compare against the maximum possible number of attempts required to break the rate limit on the API requests Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
This was
linked to
issues
Nov 20, 2023
Also removed a stray `print()` command that I previously added for debugging Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
samyak-jn
approved these changes
Nov 21, 2023
There was a problem hiding this comment.
Hello @gridhead 👋
Thanks for working on this. verified most of the files consists of license description renaming which is good; otherwise the callwait functions seems right to me along with a supported testcase, so here's my +1 to this.
Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
This was referenced Nov 21, 2023
|
Apart from a couple of hiccups in between (reported in #66 and #67), my attempt to transfer issue tickets of all states (irrespective of OPEN or SHUT) along with their comments and states from the Here are some tickets to confirm the success of such a long-winded transfer https://gitlab.com/gridhead/protop2g-test/-/issues/3609, https://gitlab.com/gridhead/protop2g-test/-/issues/3606, https://gitlab.com/gridhead/protop2g-test/-/issues/3603, https://gitlab.com/gridhead/protop2g-test/-/issues/3600, https://gitlab.com/gridhead/protop2g-test/-/issues/3557, https://gitlab.com/gridhead/protop2g-test/-/issues/3554 and https://gitlab.com/gridhead/protop2g-test/-/issues/3551. Here's the complete result.
Here's where it is shown that the tool takes a pause for 60 seconds after having made 195 requests before continuing on to do some more.
|
|
Thanks for the review, @samyak-jn! |
Zlopez
approved these changes
Nov 21, 2023
gridhead
added a commit
that referenced
this pull request
Dec 13, 2023
Circumvent the rate limits on the API requests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Circumvent the rate limits on the API requests
Fixes #10, #33 and #60