-
Notifications
You must be signed in to change notification settings - Fork 29.9k
Turbopack: Split Dirty into Dirtyness and CleanInSession #86070
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
sokra
wants to merge
3
commits into
canary
Choose a base branch
from
sokra/refactor-session-dependent-dirty-1
base: canary
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.
+162
−127
Draft
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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.
When a
SessionDependenttask is being made fully dirty, if the correspondingCleanInSessionentry is missing, the code returns early without updating the aggregations and scheduling the task. This skips critical system state updates.View Details
Analysis
Missing aggregation update when SessionDependent task lacks CleanInSession entry
What fails: In
make_task_dirty_internal(), when a task withDirty { SessionDependent }is being transitioned to fully dirty but the correspondingCleanInSessionentry is missing, the function silently returns without updatingAggregatedDirtyContainerCountand scheduling the task.How to reproduce: This requires the data structure invariant to be violated:
Dirty { SessionDependent }must exist without a correspondingCleanInSession { SessionId }entry. This can occur due to bugs in the storage layer, concurrent access issues, or incomplete state transitions.What happens:
Dirty { Dirty }, replacingDirty { SessionDependent }CleanInSessionupdate_with_dirtyness_and_session()Expected behavior: Per the refactoring commit 08f394e2cf that split
DirtyStateinto separateDirtynessandCleanInSessionitems, a data structure invariant was introduced: ifDirty { SessionDependent }exists,CleanInSessionmust also exist. Violating this invariant should be treated as a bug and exposed with a panic rather than silently skipping critical state updates.Fix: Convert the None case to a panic that exposes the invariant violation, matching the pattern used elsewhere in the codebase for invariant violations (e.g., immutable task invalidation at line 212).