You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(filter-quality): preserve error signal in go test/vet/golangci filters
Every retry these filters caused had the same root: RTK kept the cosmetic
summary but dropped the one actionable line (the error/failure message), then
advertised a verbose tee-log -- so agents retried and pulled back more bytes
than the unfiltered output.
- go test: drop the tee for 'go test'. The [full output: ...go_test.log]
pointer handed out the raw 'go test -json' dump (3-8x verbose); agents cat'd
it on failure. Build errors and per-test failures are already inline.
- go vet: keep every finding line, not just '.go:' lines. Location-less
compiler/cgo failures (fatal error: pcap.h: No such file or directory) were
dropped, then reported as 'No issues found' on a hard failure. Stop
truncating the message tail mid-line.
- golangci-lint: emit standard 'file:line:col: message (linter)' findings. The
violation message (Text) was parsed and discarded, leaving only counts.
- golangci-lint: passthrough verbatim when the user supplies --out-format /
--output.* instead of force-parsing JSON and emitting a parse-error string
that reads as a tool failure.
Savings stay high vs raw (golangci 78-84%); go vet passes tiny failures
through by design (compressing 323 B is negative value).
// The actionable detail of a `could not import` line lives at its tail;
1157
+
// a mid-message cut is exactly what an agent retries to recover.
1158
+
let long = "./capture.go:9:2: could not import github.com/google/gopacket/pcap (-: # github.com/google/gopacket/pcap: fatal error: pcap.h: No such file or directory)";
1159
+
let result = filter_go_vet(long);
1160
+
assert!(
1161
+
result.contains("pcap.h: No such file or directory"),
0 commit comments