brokerd: runbook pointers for startup failures, no thread panics, args_os
M3a review findings 3, 5 (the cast), 6, 7 (brokerd), 11. A config, directory or socket failure at start now ends with docs/runbook.md#brokerd-start-failed, and losing a listener with #brokerd-listener-lost; both entries are new. Threads start through thread::Builder, so a refused thread is reported instead of silently killing a listener; an aborted connection no longer stops the daemon. brokerd reads args_os and keeps the config path as a path. The "requester went away" result is recorded at the time it happens. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -301,7 +301,7 @@ fn pending(
|
||||
ToolResponse::Failed {
|
||||
message: GONE.to_string(),
|
||||
},
|
||||
now,
|
||||
Timestamp::now(), // now, not when it was decided: records keep time order
|
||||
);
|
||||
return None; // 5. the peer left at the last look; nothing ran
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user