Repository navigation
session: a run finishes what it starts, or says it did not - #5
Merged
Merged
Conversation
A mention to fix the conflicts on pip-web#161 ran twice for fourteen minutes, merged the branch, and pushed nothing. The test suite ran past Claude Code's ten-minute Bash cap, was moved to the background, and the agent ended its turn to wait for it. In an unattended run that ends the session, so the work died with the runner and the run was recorded as a success. - Background tasks are off and the Bash cap is 45 minutes, so a slow gate finishes inside the turn whatever the repo's test command is. - A mention that exits without a reply in its thread, or without the issue being closed, fails the job, is recorded as "unanswered", and the existing notice tells the human in the thread. - The operating guide says to finish inside the run and to push before a slow check.
Deploying roster with
|
| Latest commit: |
04804d6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://967a8c92.roster-7ih.pages.dev |
| Branch Preview URL: | https://session-finishes-what-it-sta.roster-7ih.pages.dev |
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.
What this changes
A mention asking the CTO to fix the conflicts on playpip/pip-web#161 ran twice (playpip/cto runs 37121977804 and 37202943003), each time for about 14 minutes. Each time it merged the branch, pushed nothing, posted nothing, and was recorded as a success.
The cause:
pnpm test:allran past Claude Code's 10-minute Bash cap, so it was moved to the background. The agent then said "the background job will tell me when it finishes" and ended its turn. In an unattended run, ending the turn ends the session, and the work was lost with the runner.CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1andBASH_MAX_TIMEOUT_MS=2700000at job level. A slow gate now finishes inside the turn, whatever the tenant's test command is.unanswered. The portal already shows it as hot.Type of change
fixbug fixTesting
Automated: three new tests: the env vars are set, the answer check exists and runs before the record, and
outcomeOfhandlesunanswered.Manual: dry-ran the check's
gh apiqueries against playpip/cto. #135 comes out unanswered, as it should. #132, where pip-cto[bot] replied at 12:03 after a 12:01 start, passes.Checklist
pnpm test:allpassestemplates/roster promptoutput checked, androster upgradereviewedBreaking changes
None to manifests. Tenants pick up the new session.yaml and operating.md with
roster upgrade. From then on, a mention run that exits without answering shows red rather than green.🤖 Generated with Claude Code