Error decorations persist in jupyter notebooks (ipynb) after resolution

[sfc-gh-catkinson]

When the errors origin lies in a different code cell after resolution the decoration still persists:

Reproducing:

1. create a new jupyter notebook

2. create a new code cell containing

   mymessage = "something very interesting"

3. Create s econd code cell containing

   print(mymessages)

5. Run the two cells , decoration highlights the name error correctly

6. Correct the second cells value to:

   print(mymessage)

7. Run the second cell. the code runs successfully, but the error decoration persists

[toiletbowlkuku]

Having the same issue here. There should be a mechanism to update the error decoration after running code.

[usernamehw]

Thing is - I don't use Python or Jupyter or Notebooks.

It doesn't even show errors with the steps provided(Only a warning from Pylance):

[usernamehw]

Added command to force update decorations. Example to run from keybindings.json (after Run All):

{
	"key": "ctrl+shift+5",
	"command": "runCommands",
	"args": {
		"commands": [
			"notebook.execute",
			"errorLens.updateEverything",
		],
	},
},

[emretepedev]

Same issue here. The last highlight still appears even after it's resolved until the Reload Window command. The Update Everything command does not work for me @usernamehw

[usernamehw]

Is that command not working at all? Maybe runCommands doesn't wait for the previous command to be executed. What if you run it via Command Palette Error Lens: Update Everything? If it works - then maybe the delayed version will work; like when using Commands extension.

{
	"key": "ctrl+shift+5",
	"command": "commands.run",
	"args": [
		{
			"command": "notebook.execute",
		},
		{
			"delay": 2000,
			"command": "errorLens.updateEverything",
		},
	],
},

[Oskar-Idland]

Bumping this as I have the exact same issue, using VSCode on Linux. The reload function does not help either. The only fix is to move to another file and back again, or create a new error somewhere else. Both forces some kind of "refresh".

When trying to record this I made a new notebook to test. There was no problem in the new notebook. Going back to the original notebook with the problem, the problem was gone! Closing and opening VSCode did not change this and it is currently working??

[kirby-jack]

I also have this same issue.

[usernamehw]

Does it still reproduce if you use this setting(version > 3.22.1):

"errorLens.experimental": {
	"fixNotebookStaleProblems1": true,
},

[mtolmacs]

The experimental setting fixed the issue for me.

[usernamehw]

Ok. 1 person tried the fix, no other feedback.

Closing the issue as fixed, since experimental behavior is now the default one starting with 3.23.0.