microsoft / microsoft/copilot-for-eclipse
[Bug] Validates the aka.ms short urls, update the out-of-date ones
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Environment
- OS: Windows 11
- Eclipse Version: Spring Tools for Eclipse 5.3.0.RELEASE
Version: 5.3.0.RELEASE
Build Id: 202607290337
Revision: 573f714dc76f178bfb2af392d03864f2a0a540ac
Copyright (c) 2007 - 2026 Broadcom
All rights reserved. Visit https://spring.io/tools
This product includes software developed by the
Eclipse Foundation https://www.eclipse.org
This product includes software developed by the
Apache Software Foundation https://www.apache.org
- Plugin Version: 0.21.0
Describe the bug
I see a message. You've reached your additional usage limit for your plan. Go to GitHub Settings for more details.
Then I go to github AI, increased from 10 to 20. Yet it keeps on poppping up same error despite my code generation is in halfway.
To Reproduce
Steps to reproduce the behavior:
- Use code generation until you exhaust your additional limit.
- You will see error You've reached your additional usage limit for your plan.
- Goto github.com and increase limit
- It will not be reflected for long time in eclipse. It took 1 day for me to refresh.
Expected behavior
After I increase the limit in github, the eclipse plugin should work immediately.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the usage-limit flow in the Eclipse plugin: exhaust the additional limit, increase it in GitHub Settings, and observe how long the plugin continues showing the error. Done means the updated GitHub limit is recognized without requiring a day-long delay; the issue names no source file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100