Closed ruifengx closed 2 years ago
Further experiment shows that a vertically-split view is not necessary to reproduce this issue. If I left the Agda panel open and restart VSCode (and that panel will remain open, though without any content), I get the same error after C-cC-l.
I also have been getting this issue. Just a regular Agda file and C-c C-l briings up the same issue. The file will load but the Agda output pane will not show anything. The functionality works fine if you can input what you need into goals, e.g. C-c C-c, but you can only do this when the variable is inside the goal. No inputting in the pane input, doesn't show at all. No error either :(
Also just reverted back to Version 1.64.2 and it immediately worked fine. It annoyingly auto-updated me back to the latest and it failed again. Like ruifengx said, likely a new update issue
I can confirm that we have also been seeing this error on both MacOS and Windows machines with our students after the most recent VS Code update.
I still encounter the issue on vscode 1.65.2. Are there any instructions on how to debug the extension? I tried the instructions in CONTRIBUTING.md, but that did not give me a debugger that I could attach.
Reverted to 1.64.2 and now I don't get any error message. Had the same problem as others on newer versions. It's frozen on Loading page
Same as #86
@rkochar, I think this issue is unrelated to #86.
The extension only gets stuck at "Loading..." when using the language server on versions ≥1.64.2. On ≥1.65, it is broken even when using agda
directly (no language server).
@phijor I also have this problem on vsc 1.59. Did clean install of everything, vsc, agda and vsc extension, problem persists. Issue may be unrelated to #86 but it has the same characteristics.
This is really bad! I'm on it!
Sorry guys, been quite busy recently.
Thanks for the info regarding VS Code update.
It should be fixed in v0.3.8
!
Steps to Reproduce
AbstractContextKeyService
has been disposed.Seems this problem has something to do with the recent VSCode update, because I had no problem for such use cases before.