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

Default to higher timeout ? #18

Open
happysalada opened this issue Feb 3, 2024 · 6 comments
Open

Default to higher timeout ? #18

happysalada opened this issue Feb 3, 2024 · 6 comments

Comments

@happysalada
Copy link

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!

@leona
Copy link
Owner

leona commented Feb 5, 2024

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 :lsp-restart but I'll look at implementing a catch all solution.

@cd-a
Copy link

cd-a commented Feb 5, 2024

I'm having the same issue. after a couple of completions, I start to get only timeouts

@dani0854
Copy link

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 :lsp-restart but I'll look at implementing a catch all solution.

For me :lsp-restart doesn't help much. It happens during actions, and some selection+action will always fail with timeout, while others will always succeed. It also seems to correlate with complexity of the action.

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.

@nilsherzig
Copy link

I changed my copilot timeouts to 10 seconds and now they are working

@pandalec
Copy link

pandalec commented Sep 4, 2024

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 :)

@dpc
Copy link

dpc commented Jan 5, 2025

Anyone with timeout problems might want to check #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants