Skip to content

A.3: is_retryable assertions on OpenAI chat errors (phase 1A; on #20) - #30

Open
cunninghamcard-bit wants to merge 1 commit into
exp/u1R.2-remove-retry-configfrom
exp/a3-openai-is-retryable
Open

cunninghamcard-bit wants to merge 1 commit into
exp/u1R.2-remove-retry-configfrom
exp/a3-openai-is-retryable

Conversation

@cunninghamcard-bit

Copy link
Copy Markdown
Owner

Phase 1A unit A.3 (A9; PHASES 1A). Stacked on #20 (exp/u1R.2-remove-retry-config @ 94ed020), and the PR base is that branch.

  • aimux-providers/tests/openai_upstream_e2e_test.rs:
    • chat_error_response (the 429 case) now also asserts error.is_retryable, right after the status/data assertions (post-R.2 line 196).
    • New chat_error_response_400_is_not_retryable: a 400 invalid_request_error gives ApiCall with status_code == Some(400), and the test asserts !error.is_retryable.
    • Both follow AI SDK api-call-error.ts:28-32.
  • Test-only change. Fixture/cassette diff: zero (only this test file changed).
A.3
cargo test --workspace 2876 / 0 / 7 (one new test; both tests show in the log)
fmt / clippy -D warnings ok / ok
gen_ts_types --check ok
boundary script 0

The bindings were not re-run, since this change only touches tests.

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