Context cancellation from a shutdown or a caller that went away is logged as an error or warning. Counts over 7 days: State Store 318 staterpc call failed ERROR lines (mostly context canceled: PutPresence 112, PutApplyStatus 59, ListSteps 37, StatusCounts 32), daemon 107 and gateway 59 WARN apply status not reported, 41 State Store identity store failed, UI 832 control-plane watch ended; reconnecting WARN (mostly connection refused during a peer restart), 96 container network auto-detect: could not inspect self by hostname WARN (once per boot on a native, non-container install). These bury the real faults in the same journals.
Done when
A cancelled or deadline-exceeded context caused by shutdown or a departing caller is not logged at WARN or ERROR (presence.Run already does this; apply it to the others).
A reconnecting watch logs once per outage, not once per attempt.
The container-network auto-detect line is logged only when the daemon is actually in a container.
Verified by the journal counts for these messages on a normal restart being zero.
## What is wrong
Context cancellation from a shutdown or a caller that went away is logged as an error or warning. Counts over 7 days: State Store 318 `staterpc call failed` ERROR lines (mostly `context canceled`: PutPresence 112, PutApplyStatus 59, ListSteps 37, StatusCounts 32), daemon 107 and gateway 59 WARN `apply status not reported`, 41 State Store `identity store failed`, UI 832 `control-plane watch ended; reconnecting` WARN (mostly connection refused during a peer restart), 96 `container network auto-detect: could not inspect self by hostname` WARN (once per boot on a native, non-container install). These bury the real faults in the same journals.
## Done when
- A cancelled or deadline-exceeded context caused by shutdown or a departing caller is not logged at WARN or ERROR (`presence.Run` already does this; apply it to the others).
- A reconnecting watch logs once per outage, not once per attempt.
- The container-network auto-detect line is logged only when the daemon is actually in a container.
- Verified by the journal counts for these messages on a normal restart being zero.
Fixed in 1d9eff65: context.Canceled is logged at debug in staterpc, identity store and apply status; the control-plane watch logs once per outage; the container network auto-detect runs only inside a container. Deadline-exceeded stays at its level since it can be a real database timeout.
Fixed in 1d9eff65: context.Canceled is logged at debug in staterpc, identity store and apply status; the control-plane watch logs once per outage; the container network auto-detect runs only inside a container. Deadline-exceeded stays at its level since it can be a real database timeout.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What is wrong
Context cancellation from a shutdown or a caller that went away is logged as an error or warning. Counts over 7 days: State Store 318
staterpc call failedERROR lines (mostlycontext canceled: PutPresence 112, PutApplyStatus 59, ListSteps 37, StatusCounts 32), daemon 107 and gateway 59 WARNapply status not reported, 41 State Storeidentity store failed, UI 832control-plane watch ended; reconnectingWARN (mostly connection refused during a peer restart), 96container network auto-detect: could not inspect self by hostnameWARN (once per boot on a native, non-container install). These bury the real faults in the same journals.Done when
presence.Runalready does this; apply it to the others).Fixed in
1d9eff65: context.Canceled is logged at debug in staterpc, identity store and apply status; the control-plane watch logs once per outage; the container network auto-detect runs only inside a container. Deadline-exceeded stays at its level since it can be a real database timeout.