Skip to content
PR

feat: Add built-in retry util into into async utils #184

Sign in to view logs

feat: Add built-in retry util into into async utils

feat: Add built-in retry util into into async utils #184

Triggered via pull request August 15, 2025 00:36
@autofix-ciautofix-ci[bot]
synchronize #54
retry
Status Failure
Total duration 3m 50s
Artifacts –

pr.yml

on: pull_request
Test
3m 35s
Test
Preview
1m 23s
Preview
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Test
Parameter 'error' implicitly has an 'any' type.
Test
Parameter 'error' implicitly has an 'any' type.
Test
Parameter 'attempt' implicitly has an 'any' type.
Test
Cannot find module '@tanstack/react-pacer/async-retryer' or its corresponding type declarations.
tests/async-rate-limiter.test.ts > AsyncRateLimiter > Edge Cases > should handle rapid async executions with sliding window: packages/pacer/tests/async-rate-limiter.test.ts#L618
AssertionError: expected [ 'result' ] to have a length of 3 but got 1 - Expected + Received - 3 + 1 ❯ tests/async-rate-limiter.test.ts:618:53
tests/async-rate-limiter.test.ts > AsyncRateLimiter > Edge Cases > should handle long-running executions correctly: packages/pacer/tests/async-rate-limiter.test.ts#L567
AssertionError: expected undefined to be 'result' // Object.is equality - Expected: "result" + Received: undefined ❯ tests/async-rate-limiter.test.ts:567:23
tests/async-rate-limiter.test.ts > AsyncRateLimiter > Edge Cases > should handle concurrent executions properly: packages/pacer/tests/async-rate-limiter.test.ts#L541
AssertionError: expected [ 'result' ] to have a length of 2 but got 1 - Expected + Received - 2 + 1 ❯ tests/async-rate-limiter.test.ts:541:53
tests/async-batcher.test.ts > AsyncBatcher > State Management > should track execution state during async processing: packages/pacer/tests/async-batcher.test.ts#L88
AssertionError: expected true to be false // Object.is equality - Expected + Received - false + true ❯ tests/async-batcher.test.ts:88:47
Unhandled error: packages/pacer/tests/async-retryer.test.ts#L278
Error: Test error ❯ tests/async-retryer.test.ts:278:21 ❯ ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 ❯ runWithTimeout ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1863:10 ❯ runTest ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1574:12 ❯ runSuite ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1729:8 ❯ runSuite ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1729:8 ❯ runSuite ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1729:8 This error originated in "tests/async-retryer.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw after retries when throwOnError is true". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: packages/pacer/tests/async-retryer.test.ts#L163
Error: Persistent failure ❯ tests/async-retryer.test.ts:163:21 ❯ ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 ❯ runWithTimeout ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1863:10 ❯ runTest ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1574:12 ❯ runSuite ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1729:8 ❯ runSuite ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1729:8 ❯ runSuite ../../node_modules/.pnpm/@vitest+runner@3.2.4/node_modules/@vitest/runner/dist/chunk-hooks.js:1729:8 This error originated in "tests/async-retryer.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should fail after exhausting all retries". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.