-
Notifications
You must be signed in to change notification settings - Fork 8
fix: Fix deepnote notebook deserializer and file change watcher #363
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
Draft
tkislan
wants to merge
10
commits into
main
Choose a base branch
from
tk/fix-project-notebook-picker
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+205
−39
Draft
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
6802960
fix: Fix deepnote notebook deserializer
tkislan 2de7885
Add tests
tkislan bc2de06
Merge branch 'main' into tk/fix-project-notebook-picker
tkislan 3a418c1
Fix file change watcher
tkislan 9b5c107
Merge remote-tracking branch 'origin/main' into tk/fix-project-notebo…
tkislan 77c0347
Improve error handling in DeepnoteFileChangeWatcher to prevent stale …
tkislan 6dc77a0
Add unit tests for DeepnoteFileChangeWatcher to handle scenarios with…
tkislan 8898be9
Format code
tkislan c74ffa7
Enhance error handling in DeepnoteFileChangeWatcher to check save ope…
tkislan 8d061ac
Add post-snapshot read grace period in unit tests for DeepnoteFileCha…
tkislan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
In the VS Code extension API, does FileSystemWatcher guarantee a separate onDidChange event for each write to the same file, or can consecutive writes to the same path be coalesced into a single event?💡 Result:
No.
FileSystemWatcherdoes not guarantee oneonDidChangeevent per write to the same file. Consecutive writes (and even multiple low-level filesystem operations) can be coalesced/folded into fewer notifications, depending on the underlying watcher implementation and VS Code’s own performance optimizations. (code.visualstudio.com)Citations:
Remove the second
markSelfWrite()on theworkspace.save()path.Lines 356 and 371 both arm
selfWriteCountsfor the same file. VS Code's FileSystemWatcher does not guarantee separateonDidChangeevents per write—consecutive writes can be coalesced into a single notification. If bothwriteFile()andworkspace.save()collapse into one event, the second marker never gets consumed and persists for 30s, suppressing the next real external change on that file.Keep the marker on
writeFile()only. Letworkspace.save()events pass through tocontentActuallyChanged()without arming a marker.Fix
// Save to clear dirty state. VS Code serializes (same bytes) and sees the // mtime from our recent write, so no "content is newer" conflict. - this.markSelfWrite(fileUri); try { const saved = await workspace.save(notebook.uri); if (!saved) { - this.consumeSelfWrite(fileUri); logger.warn(`[FileChangeWatcher] Save after sync write returned undefined: ${notebook.uri.path}`); return; } } catch (saveError) { - this.consumeSelfWrite(fileUri); logger.warn(`[FileChangeWatcher] Save after sync write failed: ${notebook.uri.path}`, saveError); }🤖 Prompt for AI Agents