RunicGateway/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(rust): the step-2 site walk, and the run it found stuck pending

Browse Source 
Walked on a core running Module-Rust#22 on website#209 against rust-oxide:
F8, F13/F14, F7, F5/F6 and the helper's state all pass. The expiry walk found
a run left cleanup-pending for ever when its last resource expires while it
runs; website#209 now settles it, and EVENTS.md §L says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
claude
2026-09-27 01:05:35 -05:00
parent a199823513
commit 383f3bdbe5
3 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/EVENTS.md
View File

@@ -1805,7 +1805,9 @@ It is **terminal and green, like `reverted`**: it releases the target (it is not
hold it), it is not "unreverted", and the sweep never tries to give it back. A row a revert has already
claimed (`reverting`) is left to that revert, which finds nothing and succeeds. A finished run whose last
unresolved row this was goes to `cleanup_status = 'complete'`, including from `incomplete`, which the
sweep no longer scans.
sweep no longer scans. A run still going when its last resource expires is settled by the sweep once it
ends: finished, `pending`, and no unresolved row is `complete` — the scan that joins on an unresolved row
could not see it, and the step-2 walk's run 46 sat `pending` until it could.
---