test-case: cloud fallback fires on local transport failure #48
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps
cfg.routing.fallback = trueandcfg.routing.fallback_model = "cloud". Ensuremodels.cloudis configured (anthropic/claude-haiku-4.5 in default config).models.fast.endpointto an unreachable URL (e.g.http://localhost:9999).hi.Expected
[aish] local fast failed (<reason>); retrying via cloud.broker error: ...(Phase 1 behavior).What this exercises
Couldn't resolve host,Connection refused, etc.)Likely failure modes
:route checkand check the err message format.PASS after one fix (autonomous run, 2026-05-13).
First run failed — the actual libcurl error string for
http://localhost:9999(port closed, host resolves) wasCould not connect to server(CURLE_COULDNT_CONNECT, code 7) — not in the original FALLBACK_PATTERNS set. Pattern added in commit8e0e735(now alongside Couldn't-resolve-host, Connection-refused, timeouts, HTTP 5xx, HTTP 408).Second run:
local fast failed (Could not connect to server); retrying via cloudstatus fired; cloud (anthropic/claude-haiku-4.5 via openrouter) responded normally withHi there friend.. Single-hop fallback works end-to-end. Closing.