Repository navigation
fix(agent): keep a slow Simlock daemon instead of restarting it - #12
Merged
Merged
Conversation
Three status timeouts while the host wiped and re-warmed an iPhone Duo made the agent stop Simlock; its start then hit the old daemon going away and the run shut down after serving for two hours. Ask Simlock's health route first and restart only a daemon that does not answer it; give stop 90s and start a second try. Status warnings now say why the read failed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Why
Two v0.6.7 iPhone Duo runs (kek9256/sims 42596484136 and 42612379553) were live and serving for ~2h. When the client's lease ended, Simlock began wiping and re-warming the Duo, and the 3-vCPU host saturated: "Host load read timed out" and
simctl listtiming out at 120s.simlock statusthen failed three times in a row (20s timeout). The agent stopped the daemon, the newsimlock daemon startfailed withDAEMON_CONNECTION_LOST("Daemon connection closed"), and the run shut down with exit 1.What
/v1/healthz(60s budget). Restart only when that fails too.simlock daemon stopgets 90s (was 20s). A failedstartwaits 15s and tries once more.bun testandbun run checkpass.🤖 Generated with Claude Code