From f486150c069a2ef2d92a4535fc28fb6a05e2ccff Mon Sep 17 00:00:00 2001 From: teernisse Date: Mon, 23 Feb 2026 01:31:55 -0500 Subject: [PATCH] Update upstream error classification to match current API client errors The API client consolidates response decoding into a single code path that produces "decoding response" errors instead of the previous "decoding savings" / "decoding stores" / "reading response" variants. Update classifyCLIError to match the current error strings, and add "fetching savings" alongside the existing "fetching deals" / "fetching stores" cases. Co-Authored-By: Claude Opus 4.6 --- cmd/robot_mode.go | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/cmd/robot_mode.go b/cmd/robot_mode.go index 610200a..d7d131f 100644 --- a/cmd/robot_mode.go +++ b/cmd/robot_mode.go @@ -175,10 +175,9 @@ func classifyCLIError(err error) *cliError { } case strings.Contains(lowerMsg, "unexpected status"), strings.Contains(lowerMsg, "executing request"), - strings.Contains(lowerMsg, "reading response"), - strings.Contains(lowerMsg, "decoding savings"), - strings.Contains(lowerMsg, "decoding stores"), + strings.Contains(lowerMsg, "decoding response"), strings.Contains(lowerMsg, "fetching deals"), + strings.Contains(lowerMsg, "fetching savings"), strings.Contains(lowerMsg, "fetching stores"), strings.Contains(lowerMsg, "finding stores"): return &cliError{