diff options
| author | artmetla <77324544+artmetla@users.noreply.github.com> | 2026-01-27 13:34:55 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2026-01-27 15:07:50 +0000 |
| commit | 6f7d599f34a221a1df513475c6ba53bbc573dc32 (patch) | |
| tree | 6422332913df87d8aa9cb7ba5d4e9fe344ed74be /pkg/aflow/flow/patching/patching.go | |
| parent | 211d25f08379711bd9fc8640d64a2bcd0b5eb743 (diff) | |
tools/syz-aflow/aflow.go: improve error handling for non-JSON responses
When an extID exists but access is restricted, the syzbot server may return an HTTP 200 OK response containing an HTML
instead of the expected JSON payload.
Currently, this causes "json.Unmarshal" in "downloadBug" to fail with the generic error message:
"invalid character '<' looking for beginning of value".
This change wraps the unmarshalling error to return an explicit message:
"response for bug ID <id> was not valid JSON: <original error>"
This makes it clear the issue is the response format (HTML vs JSON).
Diffstat (limited to 'pkg/aflow/flow/patching/patching.go')
0 files changed, 0 insertions, 0 deletions