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.

Sign up for GitHub

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

Jump to bottom

Lower the concurrency when "TOOMANYREQUESTS: Rate exceeded" occurs #383

Open
joaopapereira opened this issue May 3, 2022 · 2 comments
Open

Lower the concurrency when "TOOMANYREQUESTS: Rate exceeded" occurs #383

joaopapereira opened this issue May 3, 2022 · 2 comments
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@joaopapereira
Copy link
Member

Describe the problem/challenge you have
When talking to some registries imgpkg might be doing more requests than the registry allows.

Describe the solution you'd like
Whenever imgpkg encounters the TOOMANYREQUESTS error it would be interesting to automatically adapt by lowering the number of concurrent workers it is using.

Anything else you would like to add:
Investigate to understand what it would look like to implement this feature.

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help work on this issue.
@joaopapereira joaopapereira added enhancement This issue is a feature request carvel triage This issue has not yet been reviewed for validity priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels May 3, 2022
@cmoulliard cmoulliard mentioned this issue Jun 8, 2022
Closed
@github-actions
Copy link

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

@github-actions github-actions bot added the stale This issue has had no activity for a while and will be closed soon label Jun 15, 2022
@joaopapereira joaopapereira removed the stale This issue has had no activity for a while and will be closed soon label Jun 15, 2022
@github-actions
Copy link

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

@github-actions github-actions bot added the stale This issue has had no activity for a while and will be closed soon label Jul 26, 2022
@joaopapereira joaopapereira added carvel accepted This issue should be considered for future work and that the triage process has been completed and removed carvel triage This issue has not yet been reviewed for validity stale This issue has had no activity for a while and will be closed soon labels Jul 26, 2022
@aaronshurley aaronshurley moved this to To Triage in Carvel Aug 18, 2022
@github-project-automation github-project-automation bot moved this to To Triage in Carvel Feb 14, 2023
@joaopapereira joaopapereira moved this from To Triage to Unprioritized in Carvel Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
Carvel
Status: Unprioritized
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joaopapereira