Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execution count cannot be cleaned even after "Clear All Outputs" #16367

Open
1 of 2 tasks
XuShenLZ opened this issue Jan 10, 2025 · 0 comments
Open
1 of 2 tasks

Execution count cannot be cleaned even after "Clear All Outputs" #16367

XuShenLZ opened this issue Jan 10, 2025 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@XuShenLZ
Copy link

XuShenLZ commented Jan 10, 2025

Applies To

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

What happened?

After I clicked the "Clear All Outputs", some fields have the execution_count field set to null but some fields still have some number. This looks like #16052 and people claimed that it is fixed. However, it is still happening to me, creating a lot of unnecessary diffs when I try to commit.

It is very confusing that all kinds of behaviors can happen:

Set a cell without execution_count before to null, or change its value from one number to a new number:
Image

Set a cell without execution_count before to either null or some number:
Image

Set a cell with a number in execution_count before to null
Image

I am running the notebook inside a Docker container.

VS Code:

Version: 1.96.2
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.8.0-51-generic snap

VS Code Version

1.96.2

Jupyter Extension Version

2024.11.0

Jupyter logs

Coding Language and Runtime Version

Python 3.11.10

Language Extension Version (if applicable)

2024.22.2

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

None

@XuShenLZ XuShenLZ added the bug Issue identified by VS Code Team member as probable bug label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants