-
Notifications
You must be signed in to change notification settings - Fork 1.9k
fix(core): keep RLAC cycle-detection state per analyzer invocation #2619
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
Open
ttw225
wants to merge
1
commit into
Canner:main
Choose a base branch
from
ttw225:fix/core-analyzer-request-local-cycle-state
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.
+196
−46
Open
Changes from all commits
Commits
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
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.
Now that the stack is per-invocation and never crosses a thread boundary, the
Mutexis permanently uncontended — and, more importantly, the type now says the opposite of what this PR just established.Mutexreads as "shared across threads", which is precisely the property being removed.RefCellwould encode the new invariant in the type system: it is!Sync, so any future attempt to move this back ontoModelAnalyzeRuleas a field, or to share it across threads, becomes a compile error rather than a silently reintroduced race. That seems worth having right before step 3 removescall_lockand real concurrent traffic starts arriving here.Secondary benefit: the scoped block in
build_model_plan_nodethat drops the borrow before recursing is load-bearing. If someone later widens it across the recursive call,parking_lot::Mutex(non-reentrant) deadlocks, whereasRefCellpanics with a location. The latter is far easier to diagnose.I prototyped it to make sure this is not just theory — it is a 4-line change:
Result:
clippy --all-targets --all-features -- -D warningsclean (exit 0, zero warnings, forced fresh analysis),cargo test --lib148/148, concurrency regression still passes. NoSend/Syncobstacles.(Unrelated and pre-existing, just noting it while we are here:
ModelStack/ModelStackGuardare named "stack" but the underlying type is aHashSet, which has no ordering.)