Repository navigation
merge queue: checking #140 on main (ac65515) - #141
Closed
mergify[bot] wants to merge 2 commits into
Closed
mergify[bot] wants to merge 2 commits into
mergify[bot] wants to merge 2 commits into
Conversation
…arts
Measured live 2026-10-14 (feature 004, phase 4): an adopted regression
chain's yield named an exit_code_file that an earlier job had already left
on disk. The wait ended after 0 s ("yield satisfied ... job rc unknown") and
the next pass was told the job had ended while the chain was still running
and taking the lab down.
A yield whose explicit exit_code_file / file_exists path already exists when
it is accepted is now refused (yield_invalid "completion marker already
exists"), and the agent is told to remove it first, name a fresh path, or
wait on the pid. specstride's own rc file for a launched job is unaffected
(it is removed before launch).
Signed-off-by: mairp <oec.valle.art@gmail.com>
Co-Authored-By: Claude <noreply@anthropic.com>
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.
Note
This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch dashing-chevrotin-9b1m8h of the
defaultqueue, to test #140 before it merges intomain. Pushing to this branch or closing this pull request removes #140 from the queue.What this draft tests
Mergify checks that #140 still passes CI on top of
main. CI runs on this draft's code, built in this order:mainatac65515🎉 Where it stands: checks passed
CI passed on this draft.
Follow the
defaultqueue in the dashboardWhat happens next
mainand closes this draft.Metadata for CI tooling, read by
mergify ciRequired conditions of queue rule
defaultfor merge#review-threads-unresolved = 0[🛡 GitHub branch protection]-body ~= (?i)claude[.]ai-title ~= (?i)claude[.]aicheck-success = lintcheck-success = no-session-linkscheck-success = testgithub-review-approved[🛡 GitHub branch protection]github-review-approved[🛡 GitHub repository ruleset rulepr-only]check-success = lintcheck-neutral = lintcheck-skipped = lintcheck-success = testcheck-neutral = testcheck-skipped = testRequired conditions to stay in the queue
#review-threads-unresolved = 0[🛡 GitHub branch protection]-body ~= (?i)claude[.]ai-conflict-draft-title ~= (?i)claude[.]aibase = maincheck-success = lintcheck-success = no-session-linkscheck-success = testgithub-review-approved[🛡 GitHub branch protection]github-review-approved[🛡 GitHub repository ruleset rulepr-only]label != do-not-mergecheck-success = lintcheck-neutral = lintcheck-skipped = lintcheck-success = testcheck-neutral = testcheck-skipped = test