-
Notifications
You must be signed in to change notification settings - Fork 33
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
Getting error 429 - rate limits. No logs available. Please clarify error cause. #17
Comments
I've got the same issue here, a lot of times. |
I am also frequently getting this error with the latest version. |
That's quite a big issue and not really clear which advantage a rate limitation should add here. Please remove or reduce the rate limitation, otherwise you cannot productively use this plugin for AI development. |
I also encounter this several times a day. It can sometimes happen at the first request. I suspect there is some other underlying issue. |
this is still happening |
any updates? |
According to the MCP specification software should implement this kind of limits, so this might be intentional. For anyone who are prepared to fork the repo and build the plugin themselves, here is the fix: |
Tbh, I stopped using this MCP because if this. Would recommend to simply use the filesystem MCP. It works 100% and because it can edit files by replacing text, it also doesnt burn through the conversation and reach the limit as quickly. Great fan of jetbrains, respect for bringing this MCP out so quickly, but it's not very usable. |
Hey everyone! Could some of use please provide IDE logs when this happened? |
Folks, we fixed the issue in the new plugin version - 1.0.17. Please update! |
Hi there,
title explains it all. I'm hitting 429 errors at times. Claude indicates a rate limit error. Logs are empty.
It is not clear to me, which rate limit I am hitting. Does jetbrains impose limits?
In any case it would be a surprising, as I am hitting this error after just a couple calls.
Best,
Filipp
The text was updated successfully, but these errors were encountered: