[AUTOMATED] docs(re-pipeline): SIGTERM to a supervisor ends the round - #432
Merged
Conversation
run.sh traps SIGTERM into a graceful stop, which writes the SHARED .kuna-repipe/STOP file -- so killing one supervisor drains every supervisor and puts the round into DRAINING, which is one-way (DRAINING -> RUNNING is not a legal edge). Removing the file does not undo it. Use kill -9 to remove a duplicate without ending the round. Records the upstream mistake too, since it is the cheap one to catch: a supervisor launched hours earlier had been declared failed because `tail` could not read its log -- wrong path, live process -- so two ran for five hours. They do not corrupt anything (the captain slot lease serialises them) but they double the tick rate and each counts budget independently. Includes the check, with the wrapper filtered out: a naive `pgrep -cf` matches the operator's own shell and hides a real duplicate in the noise. Cost when this happened: one round boundary. Round 3's testers, gate, refutation, triage and 16 needs were already complete, so its open needs simply carry into round 4. Co-Authored-By: Claude Opus 5 (1M context) <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
1 participant
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.
run.sh traps SIGTERM into a graceful stop, which writes the SHARED .kuna-repipe/STOP
file -- so killing one supervisor drains every supervisor and puts the round into
DRAINING, which is one-way (DRAINING -> RUNNING is not a legal edge). Removing the
file does not undo it. Use kill -9 to remove a duplicate without ending the round.
Records the upstream mistake too, since it is the cheap one to catch: a supervisor
launched hours earlier had been declared failed because
tailcould not read its log-- wrong path, live process -- so two ran for five hours. They do not corrupt anything
(the captain slot lease serialises them) but they double the tick rate and each counts
budget independently. Includes the check, with the wrapper filtered out: a naive
pgrep -cfmatches the operator's own shell and hides a real duplicate in the noise.Cost when this happened: one round boundary. Round 3's testers, gate, refutation,
triage and 16 needs were already complete, so its open needs simply carry into round 4.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
🤖 Generated with Claude Code
https://claude.ai/code/session_01YcFmfZndNjgfqLQVBZCdkY