-
Notifications
You must be signed in to change notification settings - Fork 32
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
Default to higher timeout ? #18
Comments
I think this issue is related to the broken pipe messages that happen if an error occurs. Increasing the timeout won't help. A quickfix is to just |
I'm having the same issue. after a couple of completions, I start to get only timeouts |
For me For me it feels like either model returns some sort of error (for incorrect action), and it get interpreted as timeout, or more complex actions take longer time to complete and they hit timeout. |
I changed my copilot timeouts to 10 seconds and now they are working |
Is there another way for raising the timeout? Most of my code completions run into timeouts Edit: I see, I can change it via env var :) |
Anyone with timeout problems might want to check #74 |
Is your feature request related to a problem? Please describe.
For the copilot handler, I'm hitting a lot of timeout. Is there a way to customize the timeout ?
Describe the solution you'd like
I'm sure it's not without tradeoffs, but ideally there should be a way to have actions without a timeout for things triggered explicitely by the user (like code actions). And for everything that is triggered automatically (completions), then I think it makes sense to have a timeout.
Describe alternatives you've considered
you could customize the timeout with an env var, but I don't think it's an amazing solution, you might hit a lot the api or not enough, depending if the timeout is too short or too long.
Additional context
Thanks again for making this!
The text was updated successfully, but these errors were encountered: