False warning regarding unsaved files

[GregSal]

Applies To

• Notebooks (.ipynb files)
• Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

VS Code indicating that a file is unsaved when all files are actually saved.
It appear to only happen when Jupyter Notebooks are open.

VS Code Version

1.96.0

Jupyter Extension Version

2024.11.0

Jupyter logs

N/A

Coding Language and Runtime Version

Python v3.11.9 Jupyterlab v4.3.2 cupyter_core v5.72

Language Extension Version (if applicable)

Python Extension

Anaconda Version (if applicable)

24.1.2

Running Jupyter locally or remotely?

Local

[DonJayamanne]

I'm sorry you are running into this issue and thank you for reporting this.
Please can you share some steps to replicate this issue.
Please can you disable all extensions other than Jupyter, Python, Notebook Renderers and see if this issue reproduces.

[GregSal]

Further tests have not replicated the issue on any other PC, but the on the PC where I noticed it, VS code showed an unsaved file even when no files were open in the editor.

I was finally able to clear the problem by closing the workspace. When I closed the workspace it prompted me to save a file that was not open. When I selected "Save" it told me that the file in the editor was older than the file in the local folder and asked me if I wanted to overwrite it. I selected "Overwrite" and the "Unsaved" file warning disappeared. After closing and re-opening the workspace, Source Control did not show any changes in the "Overwritten" file. and the "Unsaved" file warning did not reappear.

It is worth noting that I had closed and reopened VS code multiple times prior to finding this solution with the "Unsaved" file warning showing up every time I opened this particular workspace, but not when I opened other workspaces. It just happened to be the case that this was the workspace that used Jupyter notebooks.

I have not been able to reproduce the situation since then, so the problem was likely due to an unclean shutdown of VS code.
If I ever manage to reproduce the problem I will let you know, and attach a copy of the workspace file. Are there any other files that might also be useful in identifying the problem?

Thanks
Greg Salomons

[GregSal]

I have encountered the issue again on two different occasions on two different PCs with different profiles. In both cases VS Code thinks that a notebook is unsaved. In one case the problem showed up after I was forced to do an ungraceful shutdown of VSCode due to a bug in my code that hung the IDE. In the second case it seemed to appear randomly.

When I try to close the workspace I get a prompt to save the .ipynb file followed by a warning that the file is older than the saved version. If I accept the merge changes option I get a diff that shows no differences between the files.

Let me know what info I should capture next time I encounter this.

[DonJayamanne]

I have encountered the issue again on two different occasions on two different PCs with different profiles.

Can you try to disable all extensions and see if this issue repros.

VSCode due to a bug in my code that hung the IDE. In the second case it seemed to appear randomly.

Hanging VS Code could have caused a few other issues, hence interested in the latter case.

When I try to close the workspace I get a prompt to save the .ipynb file followed by a warning that the file is older than the saved version. If I

Are you editing this file using some other application like Jupyter Lab/notebook or another application.
Are you using remote SSH/docker containers or the like?

[vs-code-engineering]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[GregSal]

I have encountered the issue again on two different occasions on two different PCs with different profiles.

Can you try to disable all extensions and see if this issue repros.

Once a phantom unsaved file appears disabling all extensions does not resolve the issue. Clearing the phantom unsaved file required deleting VS Code workspace cache files in APPDATA (windows)

I have not yet reproduced the problem with all extensions disabled, but the amount of testing is limited because the problem is intermittent and there is very little work I can do with all extensions disabled.

VSCode due to a bug in my code that hung the IDE. In the second case it seemed to appear randomly.

Hanging VS Code could have caused a few other issues, hence interested in the latter case.

When I try to close the workspace I get a prompt to save the .ipynb file followed by a warning that the file is older than the saved version. If I

Are you editing this file using some other application like Jupyter Lab/notebook or another application. Are you using remote SSH/docker containers or the like?

All edits were done within VS Code. Containers were not in use for any the occurrences. In some cases the repository was on a network drive, in other cases on a local hard drive. In all cases the phantom unsaved file was reported as one of the recently edited jupyter notebooks in the repository. When all open files were closed VS Code would continue to indicate an unsaved file, but would not specify the file. In all cases VS Code was being run in a Windows 10 environment.

I will re-open the issue if I encounter any new information that may help. Reply to this if you would like me to try something specific.