Repository navigation
Fix large-history backend startup for v0.1.44-beta.2 - #320
Merged
Merged
Conversation
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.
A newly spawned backend was killed after eight seconds even when it was still creating the consistent pre-migration snapshot of a large session database. This change ties preparation phases to the spawned process and a unique token, allows bounded backup/migration work, and starts the shorter client-readiness deadline after preparation. Exited/failed children stop the wait and startup failures identify their phase record.
Updates the beta.2 changelog and public documentation for release channels, the large-history failure and promotion boundaries. Experimental features remain opt-in.
Validation: eight startup/slow-child tests passed (28 assertions), fourteen adjacent storage/TUI tests passed (25 assertions), package typecheck and whitespace checks passed. All test databases are temporary. The slow-child regression exceeds the ordinary connection deadline before reaching ready; it also rejects another PID/token and checks bounded failure paths. Live release artifact acceptance follows the release workflow.