Skip to content

fix(files): report the status code when ingest-file fails - #225

Merged
jfrench9 merged 1 commit into
mainfrom
bugfix/ingest-error-status-code
Sep 30, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
bugfix/ingest-error-status-code

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

  • FileClient.upload now returns Failed to complete file upload: <status> when the ingest step fails, matching the upload-URL failure (Failed to get upload URL: <status>).
  • Without the code, a caller cannot tell a rate-limited ingest (429) from any other failure, so it cannot back off and retry. Seen in production: a five-table load was refused at ingest-file, and the caller's 429 retry never fired.

Tier

Stable tier (FileClient facade): only the error string changes, adding the status after the existing prefix. Callers that check "Failed to complete file upload" in error keep matching. Patch release.

Test plan

  • just test-all: 595 passed, 17 skipped; lint, format and typecheck clean
  • test_upload_update_fails now asserts the exact message, including the status

🤖 Generated with Claude Code

A failed ingest returned "Failed to complete file upload" with no status,
while a failed upload-URL request already reports its code. Callers that
retry on a 429 could not tell a rate-limited ingest from any other
failure, so a rate-limited load failed instead of backing off.

Claude-Session: https://claude.ai/code/session_018kncpCo1113kH9HrBC8GYy
@jfrench9
jfrench9 merged commit 34e1897 into main Sep 30, 2026
4 checks passed
@jfrench9
jfrench9 deleted the bugfix/ingest-error-status-code branch September 30, 2026 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant