Repository navigation
fix: wait for prepared template readiness within its deadline - #122
Merged
Merged
Conversation
anycodes
marked this pull request as ready for review
October 25, 2026 16:00
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.
Description
Process-start acknowledgement can precede application readiness. Public a2 rejected the first nonzero ready_cmd result even though the same owned process and port became healthy within readiness_timeout. Poll only nonzero ProcessResult values inside one monotonic ready-command budget, constrain each probe by the remaining time and preserve cancellation/error cleanup. Creation and startup are never replayed. Prepare the lockstep 0.4.0a3 pair without changing published a2 artifacts.
Refs #121
Refs Alibaba-Agent-Sandbox/awesome-providers#40
Type of Change
Testing
Definition of Done
The budget covers ready_cmd probes; existing startup-acknowledgement and per-service health budgets are unchanged. No new user option, provider capability, compatibility alias or launch mode. This draft does not claim public a3 or whole-catalog acceptance.