fix: pre-populate headerSessionIndex from DB on startup#304
Merged
Conversation
After process restart, headerSessionIndex was empty so Tier 1 session identification failed — generating new session IDs and orphaning old persisted state. Fix by loading header→session mappings from DB in initIfNeeded() before the first identifySession() call. Also clear headerSessionIndex in resetPipelineState() for test isolation.
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
1 participant
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.
Summary
Follow-up to #303. Fixes a pre-existing bug where
headerSessionIndexwas empty after process restart, causing Tier 1 session identification to fail and orphan persisted session state.session_statetable ininitIfNeeded()(before the firstidentifySession()call)headerSessionIndexinresetPipelineState()for test isolationloadHeaderSessionIndex()DB function + tests