Replies: 1 comment 1 reply
-
Pretty sure plenary has a high default timeout |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@olimorris I noticed this very weird thing with the copilot adaptor where there are periods where server can take a long time (>600s) to respond to a request. The server does not have a timeout, and the request is held for the entire duration, causing the chat buffer to be in an unmodifiable state for the entire duration. From a user experience perspective, the chat just appears to be frozen.
It seems like there is a http adaptor with the following defaults:
I was wondering whether it would make sense to set a default
--max-time
to short circuit the request beyond a certain sensible default time period. In this instance, neither connect timeout nor keepalives were an issue. Not surprisingly,gD
didn't show any issues and I closed the neovim session altogether, only managed to figure out what went wrong because I had MITM opened.MITM logs
Beta Was this translation helpful? Give feedback.
All reactions