clawpatrol

on a host whose daemon can't boot prints: Neither line is actionable, and the second one is wrong. The real cause was sitting in the whole time: That message is exactly what the operator needs, and it never reaches them. Diagnosing this took reading to learn the log existed. Two separate defects: 1. The ready-pipe EOF is content-free.* () waits for on the inherited fd 3. The daemon boots its transport before binding the control socket — deliberate, per 's comment, so a parent that reads can go straight to a session START — and s when fails. So every transport-boot failure reaches the client as an unadorned EOF, regardless of cause. already computes a few lines earlier. Sketch: stat the log before to record its size, and on a ready-read failure read from that offset and fold the last non-empty line into the returned error. Reading from the recorded offset rather than tailing matters because the log is opened and shared across respawns — the last line may belong to an older daemon. 2. The hint is unconditional. appends it to every failure. On the host above it is actively misleading: there is no marker, and — already checked earlier in the same function at — had returned false. Either gate the hint on that same predicate, or replace it with a pointer to the daemon log, which covers more failure modes than the one it guesses at. Worth noting what triggered it, since it may deserve its own fix: the host was joined by a build predating the marker. 's empty-mode fallback () rescues legacy joins by stat'ing and assuming WireGuard, but a legacy tailscale* join has neither file, so it falls through to the fatal error. The remedy is a re-join either way; the point of this issue is that the operator should be able to learn that from the command's own output.

Summary synchronize body sampling and record complete, incomplete, or aborted state emit a full-body SHA only when the body is complete preserve denied and partial-read request captures reject fixtures built from incomplete, lossy, redacted, or transformed bodies show partial capture state in the dashboard Why An early response could snapshot a body while it was still being written. Fixture export could also treat a partial or changed body as the original request. Tests focused race tests dashboard tests, format, lint, and build

Hi, I was trying clawpatrol for couple of weeks and was able to make it work end to end on ubuntu24.04 with wiregaurd after following changes Some of these changes are disabling default apparmor security features in Ubuntu24.04. I am curious if there is a cleaner way to run clawpatrol on ubuntu24.04 without disabling the same.