Repository navigation
perf: report a daemon that is not ready yet as starting - #15
Merged
Merged
Conversation
A ready check that returns `loading` while its daemon is still coming up is re-polled every 30 s under start-sdk's default trigger, so every daemon that requires it waits up to 30 s after it is actually ready. `starting` is re-polled every second. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
helix-a
approved these changes
Oct 16, 2026
helix-a
left a comment
helix-a
left a comment
Member
There was a problem hiding this comment.
The shared probes correctly return starting until ready, retaining their success criteria across normal startup, bootstrap/update, and password-reset chains. Confirmed the installed SDK polls starting every 1 second versus loading every 30 seconds. SDK 3.0.6 matches npm latest; beta still serves 16.51.0:0, so keeping 16.51.1:0 is appropriate.
Verified clean merge with master; local TypeScript, Prettier, JavaScript bundle, probe success/unready assertions, and SDK polling assertions pass. Reused successful x86_64 and aarch64 CI package builds. No runtime installation or startup timing measurement performed. No changes requested.
Helix-Harness: pi
Helix-Model: openai-codex/gpt-6.1-sol
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.
A daemon
readycheck that isn't satisfied yet now returnsstartinginstead ofloading, in the sharedredisReadyandmariadbReadyhelpers.loadingmeans operational but catching up, and start-sdk's default trigger re-polls it every 30 s. A sidecar that reportedloadingon an early probe therefore held every daemon requiring it for up to 30 s after it was ready.startingis re-polled every second. The pattern came from the packaging guide's Postgres example, corrected in Start9Labs/start-technologies#4272. Start9Labs/start-technologies#4273 makes the SDK back offloadinginstead, for packages that don't change.No version bump:
master's 16.51.1:0 isn't on beta yet, so this ships with it. Its release notes gain "Performance improvement".Verified:
tsc --noEmit, Prettier andmake javascript/index.jspass. Not installed on a box.🤖 Generated with Claude Code