diag: log on writer/reader exits in driver bridge + orch server#55
Merged
diag: log on writer/reader exits in driver bridge + orch server#55
Conversation
The headline AWS run consistently shows: first 2 commands ACK fully, then every subsequent command reports 0 acks / 12 missing — drivers disconnect after handling a few commands. Without logs we can't tell whether the writer task on the driver side or the orchestrator side is dying first, or whether it's a WS send error vs a channel-closed condition. Adds eprintln! on every exit point of the writer/reader loops so the next AWS run produces actionable evidence in container logs. No behavior change. Co-Authored-By: Claude Opus 4.7 (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.
Diagnostic-only PR — the headline AWS run consistently shows drivers disconnecting after the first 2-3 commands, but without exit logs we can't tell whether the writer task on the driver side or the orchestrator side is dying first.
Adds
eprintln!on every exit point of the writer/reader loops so the next AWS run produces actionable evidence in container logs.No behavior change. All 25 tests still pass.