fix(cli): repair managed Server startup bootstrap - #27
Open
salmonumbrella wants to merge 1 commit into
Open
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.
What changed
Repair a missing, malformed, or non-array
startupThreadIDsvalue before starting a managed Server. Fresh profiles are inspected read-only after first launch, then stopped, repaired, and restarted once when needed. Valid arrays are preserved and repair never writes while the tracked process is running.Why
A self-hosted Server can be healthy and searchable while its higher-level startup bootstrap has no usable thread seed, leaving chats and contacts empty. This adds a bounded CLI-side startup repair without changing the closed-source Server binary.
Usage
Refs #14