Wait for readiness before bootstrap app jobs - #283
Closed
hamzamerzic wants to merge 2 commits into
Closed
Conversation
Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
Keep the install source separate from the app source path and prove the bootstrap launch passes wait_for_ready while the existing interactive install remains immediate.\n\nCo-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
5 tasks
Collaborator
Author
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.
Summary
Credit
Builds on and supersedes #266 by @rgjordana. Their original readiness boundary and runner work is preserved; the follow-up fixes the inactive source comparison and adds install-path coverage.
Validation
pytest -q backend/tests/test_app_jobs.py backend/tests/test_app_capabilities.py— 24 passedgit diff --check