You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wrote a buggy recursive function which executed forever. When I ran it in the repl, it caused the entire extension to become unresponsive. I couldn't interact with the repl, couldn't kill any threads, and couldn't restart the LSP. I ended up using "Developer: Reload Window" to recover. Obviously, I will try to do less looping in the future, but I was wondering if there is a way to recover from this situation, or one should be added. Some ways I could think of:
Add a "Restart LSP" command to Alive
Add a maximum execution time for code running in the repl. This could probably be a setting.
The text was updated successfully, but these errors were encountered:
Reload Window is the standard way to restart an LSP in VSCode. It makes sure the client reconnects, anything cached doesn't get out of sync, etc.
I can try adding a time limit, but I'm not sure how well it'll work. The timer thread would still need to run and try to kill the offending thread, which might not behave very well given the CPU is maxed out.
I wrote a buggy recursive function which executed forever. When I ran it in the repl, it caused the entire extension to become unresponsive. I couldn't interact with the repl, couldn't kill any threads, and couldn't restart the LSP. I ended up using "Developer: Reload Window" to recover. Obviously, I will try to do less looping in the future, but I was wondering if there is a way to recover from this situation, or one should be added. Some ways I could think of:
The text was updated successfully, but these errors were encountered: