fix(ci): contextualize log-stream errors in job-view #14
fix/job-view-log-error-context
into main
Summary
When `anvil ci job-view ` succeeded at fetching metadata but then failed streaming logs, the bare `Error: API error (…)` line at the bottom made it look like the whole command had failed.
Before
``` CI Job 7a1731da43 Status passed Exit Code 0 …
Error: API error (406): server returned an HTML error page (expected JSON) ```
After
``` CI Job 7a1731da43 Status passed Exit Code 0 …
Could not fetch logs: API error (406): server returned an HTML error page (expected JSON) (Job metadata above was retrieved successfully.) ```
The 406 path itself was fixed by fangorn/anvil#131; this just polishes the framing for any future log-stream failure (5xx, network, etc.).
Test plan
- `cargo test` — 28/28 pass
- `cargo clippy –all-targets – -D warnings` clean
- `cargo fmt` clean
- Verified against prod (post-#131): job-view streams logs and exits 0
Closes #9