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've noticed that there are stale error/warnings that show up in the problems panel when I close an VS Code Native REPL editor tab.
If you see the video you will notice that the diagnostics from Pylance will disappear right away when I close the Native REPL window but the ones from ruff will remain.
Screen.Recording.2025-04-02.at.12.38.54.PM.mov
I realized that there are two ways extension provide/interact with diagnostics when it comes to communicating with VS Code.
Thanks for the report and providing the reproduction steps. I can reproduce it for the untitled notebook. I'll convert the issue as specific to untitled Jupyter Notebook and look into native REPL later.
dhruvmanila
changed the title
Stale issues remain in problems panel with VS Code Native REPL
Diagnostics linger in problems panel after closing untitled Jupyter Notebooks
Apr 3, 2025
And, it seems that we're removing the text document before the textDocument/didClose request:
2025-04-03 10:58:38.671507000 DEBUG Unable to close document with key vscode-notebook-cell:Untitled-1.ipynb?jupyter-notebook#W0sdW50aXRsZWQ%3D - the snapshot was unavailable
I've noticed that there are stale error/warnings that show up in the problems panel when I close an VS Code Native REPL editor tab.
If you see the video you will notice that the diagnostics from Pylance will disappear right away when I close the Native REPL window but the ones from ruff will remain.
Screen.Recording.2025-04-02.at.12.38.54.PM.mov
I realized that there are two ways extension provide/interact with diagnostics when it comes to communicating with VS Code.
/cc @rchiodo @amunger
The text was updated successfully, but these errors were encountered: