Release YJ (v0.51.680): explicit session-index rebuild thread ownership (#4993, #3894) - #5003
Merged
Merged
Conversation
Contributor
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release YJ (v0.51.680) — session-index rebuild ownership hardening
Ships #4993 (@rodboev) — addresses #3894 (bookkeeping hardening).
What it fixes
_rebuild_session_index_background()cleared the rebuild bookkeeping globals in itsfinallyblock when only the target tuple matched — so a late-finishing older worker could wipe a newer rebuild's registered state. The cleanup now also requires_SESSION_INDEX_REBUILD_THREAD is current_thread(under the rebuild lock), so an out-of-order older worker leaves the newer owner intact.Gate
_SESSION_INDEX_REBUILD_LOCK(no TOCTOU); an older worker can't clear a newer same-target owner; the genuine owner still clears the globals (no stuck-owner leak). The +27 test is non-vacuous (simulates a same-target handoff, asserts the newer owner survives).test_skills_stats_cache, passes in isolation).Credit @rodboev.