Closed MakingMadness closed 1 year ago
I agree that some feedback could be nice. I'll see what I can do in terms of visuals.
Currently, error messages are displayed in a dialog whenever something happens (error on server, bad API key, prompt errors, etc.). I believe this includes timeouts, however the maximal waiting period is very long by default.
I can implement a timeout mechanism (did it for the VS Code version of Jarvis at some point), where you can set the timeout period in the settings, and get an error dialog whenever time runs out. Does this sound helpful?
Sure, that sounds great. It would be nice to not have to consider these things causing the delay instead:
And instead just see that something is clearly happening and everything is good.
Can we have some feedback on what's happening after a request is sent? An indicator that we're awaiting a response, and an error message if there is one?
For instance, I might press Ctrl+Shift+C and the border of the textarea starts glowing for the duration of whatever timeout period we're waiting. It gets an error message so the textarea stops glowing and the message is displayed to the user. If there's no response, once the timeout is reached the textarea stops glowing and the error "Request timed out. Check your connection." is displayed.