Lab lifecycle: send again a request CMO turned away while busy #151

Manually merged
vinny merged 0 commits from vinny/lifecycle-busy into master 2026-10-17 15:25:56 -04:00 AGit
Owner

Summary

  • In lab run 10b the provider/socket trial failed at its CMOnet restart: the runner's pause came back "The simulation Lua queue did not reach the lifecycle barrier" while CMO ran at about 1.1x, and the trial ended.
  • That refusal means CMO ran nothing, so tools/lab_cmo.py now sends such a request again under a new ID for up to three minutes. Any other failure still ends the request, and a lost reply is still settled by its ID.
  • A pause or run also waits up to three minutes for its state reads while CMO's dispatcher is too busy to answer.
  • CORPUS_BUILD.md describes the resend.

Test plan

  • tests/test_laboratory_lifecycle.py: a request turned away twice is sent a third time and succeeds, with busy state reads; one turned away for too long fails; an unknown side is not resent.
  • Background tools/check.py --rev

🤖 Generated with Claude Code

## Summary - In lab run 10b the provider/socket trial failed at its CMOnet restart: the runner's pause came back "The simulation Lua queue did not reach the lifecycle barrier" while CMO ran at about 1.1x, and the trial ended. - That refusal means CMO ran nothing, so `tools/lab_cmo.py` now sends such a request again under a new ID for up to three minutes. Any other failure still ends the request, and a lost reply is still settled by its ID. - A pause or run also waits up to three minutes for its state reads while CMO's dispatcher is too busy to answer. - CORPUS_BUILD.md describes the resend. ## Test plan - [x] `tests/test_laboratory_lifecycle.py`: a request turned away twice is sent a third time and succeeds, with busy state reads; one turned away for too long fails; an unknown side is not resent. - [ ] Background `tools/check.py --rev` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
A pause before the CMOnet restart failed with "The simulation Lua queue did not
reach the lifecycle barrier" while CMO ran at about 1.1x, and the trial ended.
Such a request ran nothing, so lab_cmo now sends it again under a new ID for up
to three minutes; any other failure still ends the request. A pause or run also
waits that long for its state reads while CMO's dispatcher is too busy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Version 0.7.94 (lifecycle-busy)
Some checks failed
check / check (ubuntu-latest) (push) Has been cancelled
check / check (windows-latest) (push) Has been cancelled
check / check (windows-latest) (pull_request) Has been cancelled
check / check (ubuntu-latest) (pull_request) Has been cancelled
0db295ba91
vinny manually merged commit 0db295ba91 into master 2026-10-17 15:25:56 -04:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
vinny/CMOnet!151
No description provided.