Improve HTTP response handling and retry logic #17
MichaelGHSegAnnotations
8 errors and 1 warning
|
e2e-tests
Process completed with exit code 1.
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Header Format > uses lowercase header name:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L258
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ src/tests/retry/x-retry-count-header.test.ts:258:30
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Header Format > sends header as integer string, not float:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L234
TypeError: .toMatch() expects to receive a string, but got undefined
❯ src/tests/retry/x-retry-count-header.test.ts:234:28
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Counter Reset > resets counter for new batch after success:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L163
AssertionError: expected -1 to be greater than 0
❯ src/tests/retry/x-retry-count-header.test.ts:163:32
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Retry Counter Increment > increments correctly with mixed error types:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L123
AssertionError: expected undefined to be '0' // Object.is equality
- Expected:
"0"
+ Received:
undefined
❯ src/tests/retry/x-retry-count-header.test.ts:123:59
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Retry Counter Increment > increments X-Retry-Count on each retry attempt:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L98
AssertionError: expected undefined to be '0' // Object.is equality
- Expected:
"0"
+ Received:
undefined
❯ src/tests/retry/x-retry-count-header.test.ts:98:57
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Initial Request > sends X-Retry-Count: 0 even when request fails:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L74
AssertionError: expected undefined to be '0' // Object.is equality
- Expected:
"0"
+ Received:
undefined
❯ src/tests/retry/x-retry-count-header.test.ts:74:53
|
|
src/tests/retry/x-retry-count-header.test.ts > X-Retry-Count Header > Initial Request > sends X-Retry-Count: 0 on first attempt:
sdk-e2e-tests/src/tests/retry/x-retry-count-header.test.ts#L57
AssertionError: expected undefined to be '0' // Object.is equality
- Expected:
"0"
+ Received:
undefined
❯ src/tests/retry/x-retry-count-header.test.ts:57:53
|
|
e2e-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|