You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the only interceptor for our gPRC client. When I tested it, I saw the retries happening in handleResponse but the gPRC error was returned before all retries are finished:
console.warn
gRPC connection unavailable, retrying after 1s... (Retry 1 of 5)
92 | }
93 |
> 94 | console.warn(
| ^
95 | `gRPC connection unavailable, retrying after 1s... (Retry ${
96 | retries + 1
97 | } of ${maxRetries})`,
at src/util/retry.ts:94:19
at async Promise.all (index 1)
console.warn
gRPC connection unavailable, retrying after 1s... (Retry 2 of 5)
92 | }
93 |
> 94 | console.warn(
| ^
95 | `gRPC connection unavailable, retrying after 1s... (Retry ${
96 | retries + 1
97 | } of ${maxRetries})`,
at src/util/retry.ts:94:19
at async Promise.all (index 1)
FAIL src/tests/orchestrator.test.ts (7.099 s)
RpcError: 14 UNAVAILABLE: test
at Object.callback (node_modules/@protobuf-ts/grpc-transport/build/commonjs/grpc-transport.js:37:27)
at Object.onReceiveStatus (node_modules/@grpc/grpc-js/src/client.ts:352:26)
at Object.onReceiveStatus (node_modules/@grpc/grpc-js/src/client-interceptors.ts:462:34)
at Object.onReceiveStatus (node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48)
at node_modules/@grpc/grpc-js/src/call-stream.ts:330:24
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 skipped, 2 total
Snapshots: 0 total
Time: 7.194 s
Ran all test suites matching ***[redacted]
console.warn
gRPC connection unavailable, retrying after 1s... (Retry 3 of 5)
92 | }
93 |
> 94 | console.warn(
| ^
95 | `gRPC connection unavailable, retrying after 1s... (Retry ${
96 | retries + 1
97 | } of ${maxRetries})`,
at src/util/retry.ts:94:19
at async Promise.all (index 1)
Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.
console.warn
gRPC connection unavailable, retrying after 1s... (Retry 4 of 5)
92 | }
93 |
> 94 | console.warn(
| ^
95 | `gRPC connection unavailable, retrying after 1s... (Retry ${
96 | retries + 1
97 | } of ${maxRetries})`,
at src/util/retry.ts:94:19
at async Promise.all (index 1)
console.warn
gRPC connection unavailable, retrying after 1s... (Retry 5 of 5)
92 | }
93 |
> 94 | console.warn(
| ^
95 | `gRPC connection unavailable, retrying after 1s... (Retry ${
96 | retries + 1
97 | } of ${maxRetries})`,
at src/util/retry.ts:94:19
at async Promise.all (index 1)
The text was updated successfully, but these errors were encountered:
Hope someone can help me figure out why my interceptor implementation is not working.
I'm trying to add a retry interceptor for our gPRC client. Here's the implementation:
This is the only interceptor for our gPRC client. When I tested it, I saw the retries happening in
handleResponse
but the gPRC error was returned before all retries are finished:The text was updated successfully, but these errors were encountered: