Repository navigation
mia-data: re-trigger of a failed develop round should resume the existing snippet PR - #51
Conversation
A develop round that ends in needs-human for a reason of our own (a lost
job, a failed status write) could not be resumed: the next go reset the
state, matched again and opened a second mia-snippets issue, so autodev
wrote the same snippet twice.
MiaDataDataset._round now remembers the snippets issue and PR of a
needs-human round. When the PR is still open, the new round (fresh id and
pins, tests cleared) resumes it: the issue goes to testing with a comment
saying so and the current head gets test crops again. A PR closed or
merged meanwhile falls through to the normal match, and the remembered
snippets issue is handed to open_snippet_issue, which reuses it while it
is open and ours instead of opening another. Guarded with
workflow.patched("resume-snippet-pr"); the recorded histories replay
unchanged.
Tests: the resume (same PR re-tested, no second issue, new round's job
keys), a closed and a merged PR (new match), and the activity reusing a
remembered issue only while open, ours and this dataset's. Docs and the
spec's re-trigger rule updated.
Closes #38
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
autodev-rokickik: round 1 pushed
|
| check | result |
|---|---|
| ruff check + format check | clean |
| mypy autodev mia_data mia_ops | clean |
git diff | grep 'rokickik|/nrs/' |
empty |
| tests/test_mia_workflows.py + test_mia_activities.py | 61 passed, incl. both replay tests |
| all other test modules | 291 passed |
| tests/test_autodev_workflows.py | not run |
The autodev workflow tests were not run: they need Temporal's time-skipping test server, which is downloaded from GitHub at test time and unreachable here. The mia workflow tests ran against a Temporal CLI dev server instead; they poll rather than use timers, so time skipping is not needed for them. The autodev package is untouched by this change, so CI should be the confirming run for that module.
Deploy note for the PR: in-flight MiaDataDataset runs are unaffected. The activity signature change is additive, and the workflow passes the extra argument only when it carries a value.
Closes #38: ## Problem
Implemented by autodev-rokickik: Claude Code running in a sandboxed job on the cluster. The agent's own
summary is the first comment.
/approve <head sha>(needed when running under a personal token).autodev-rokickik merges once an approval matches the current head and checks are not failing.
/revise <what to change>.Up to 3 revision rounds.