Skip to content

Add chunkId to abuse key to prevent rate limit for SDKs - #7154

Merged
christyjacob4 merged 2 commits into
1.4.xfrom
fix-rate-limit-error-on-large-uploads
Nov 17, 2023
Merged

christyjacob4 merged 2 commits into
1.4.xfrom
fix-rate-limit-error-on-large-uploads

Conversation

@vermakhushboo

@vermakhushboo vermakhushboo commented Nov 16, 2023 •

Copy link
Copy Markdown
Contributor

What does this PR do?

Add chunkId to abuse key to prevent rate limit for SDKs

Test Plan

Tested manually for node SDK.

Related PRs and Issues

Checklist

  • Have you read the Contributing Guidelines on issues?
  • If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?

@TorstenDittmann

Copy link
Copy Markdown
Contributor

Can we add a Test to the existing large file upload? @vermakhushboo

There should be headers in the response giving us informations about the rate limits 👍🏻

@christyjacob4
christyjacob4 merged commit e16387e into 1.4.x Nov 17, 2023
@christyjacob4
christyjacob4 deleted the fix-rate-limit-error-on-large-uploads branch November 17, 2023 18:01
stnguyen90 added a commit that referenced this pull request Apr 3, 2024
A previous PR added chunkId as an abuse key param to fix a problem where uploading multiple chunks of a file would trigger the `general_rate_limit_exceeded` error. For some reason, the parameter disappeared from the abuse key causing a regression. This PR adds the param back to fix the regression.

Reference:
* #7879
* #7154
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants