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

[New Feature]: Avoid "API rate limit" #189849

Open
Dragon1573 opened this issue Nov 8, 2024 · 1 comment
Open

[New Feature]: Avoid "API rate limit" #189849

Dragon1573 opened this issue Nov 8, 2024 · 1 comment
Labels
In-PR Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.

Comments

@Dragon1573
Copy link
Contributor

Description of the new feature/enhancement

This is a re-request of a feature. It was implemented before, but soon opted-out with a reversion. I want to re-add this feature back. ❤

Proposed technical implementation details (optional)

No response

@Dragon1573 Dragon1573 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 8, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Nov 8, 2024
@Dragon1573
Copy link
Contributor Author

Note

Before winget.exe version 1.9.x generally available, I can simply perform #170577 on my local repository and keep syncing with upstream by using rebase action. Then Tools/SandboxTest.ps1 changed a lot and I met huge merge conflicts.

"API rate limit" problem really affects me. I'd request an official support resolving this problem. 🙏🏼

@stephengillie stephengillie removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
In-PR Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants