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

fix language server crash on interactive mode cells and notebooks that haven't yet been saved to disk #1066

Merged
merged 2 commits into from
Feb 12, 2025

Conversation

DetachHead
Copy link
Owner

fixes #1064

…s sent for newly created notebook documents that don't yet exist on disk. as far as i can tell this is a vscode bug
@DetachHead DetachHead enabled auto-merge (rebase) February 12, 2025 12:06
@DetachHead DetachHead merged commit 5640561 into main Feb 12, 2025
20 checks passed
@DetachHead DetachHead deleted the fix-jupyter-interactive-cell-crash branch February 12, 2025 12:07
Copy link
Contributor

Diff from mypy_primer, showing the effect of this PR on open source code:

AutoSplit (https://github.com/Toufool/AutoSplit): 174.77x slower (0.1s -> 17.7s in a single noisy sample)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"failed to find cell index" errors when running in VSCode Interactive Mode or unsaved notebook file
1 participant