Skip to content

docs: note the broker-shutdown teardown log pattern in the README#148

Open
kyle-sexton wants to merge 1 commit into
mainfrom
task/64-readme-broker-teardown-noise
Open

docs: note the broker-shutdown teardown log pattern in the README#148
kyle-sexton wants to merge 1 commit into
mainfrom
task/64-readme-broker-teardown-noise

Conversation

@kyle-sexton

Copy link
Copy Markdown
Contributor

Summary

Adds a short Troubleshooting note to README.md naming the ERR BrokerServer / TaskCanceledException pattern that appears in a completed one-job worker's captured runner log, and pointing to the observability doc's "Cancellation and runner shutdown noise" section for the full contract. Pointer, not restatement: the ERR BrokerServer token (what an operator greps their worker log for) does not appear in that section, so the note adds findability without duplicating the exit-lifecycle-classification mechanism the section already documents.

Test plan

  • npx markdownlint-cli2 README.md — 0 errors
  • lychee --offline --config lychee.toml README.md — 0 errors; the new relative fragment link docs/observability.md#cancellation-and-runner-shutdown-noise resolves [200] under include_fragments = "full"
  • CI green

Related

Closes #64

Companion research (whether any actions/runner release at or above the pinned 2.335.1 quiets this teardown logging) is recorded as a comment on #64. No dependency pin is changed here — pin updates ride #72.

🤖 Generated with Claude Code

Name the `ERR BrokerServer` / `TaskCanceledException` pattern that appears
in a completed one-job worker's captured runner log, in a new README
troubleshooting section, and point to the observability doc's
"Cancellation and runner shutdown noise" section for the full contract.
The token operators grep for (`ERR BrokerServer`) does not appear in that
section, so the note is a findability pointer, not a restatement.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Worker logs end with ERR BrokerServer stack traces on every successful run-once exit

1 participant