Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[backend] - Firebase connectivity session isn't renewed after network glitches #716

Open
mur-me opened this issue Dec 12, 2024 · 0 comments

Comments

@mur-me
Copy link
Contributor

mur-me commented Dec 12, 2024

Steps to reproduce:

  1. Somehow limit connectivity to the Firebase - turn off WIFI/Ethernet network
  2. You will get the connectivity issues in the logs like error in processValidatorInfoData: Error: 13 INTERNAL: Failed to start HTTP/2 stream
  3. restore the WIFI/Ethernet network

Result: even after restored connectivity error in processValidatorInfoData: Error: 13 INTERNAL: Failed to start HTTP/2 stream are still here.

Expected result: backend should recreate the connectivity session after restoring the network.

Full issue stacktrace:

error in processValidatorInfoData: Error: 13 INTERNAL: Failed to start HTTP/2 stream
    at Object.callErrorFromStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/call.js:30:26)
    at Object.onReceiveStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/client.js:175:52)
    at Object.onReceiveStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:341:141)
    at Object.onReceiveStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:304:181)
    at Http2CallStream.outputStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/call-stream.js:116:74)
    at Http2CallStream.maybeOutputStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/call-stream.js:155:22)
    at Http2CallStream.endCall (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/call-stream.js:141:18)
    at Http2CallStream.cancelWithStatus (staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/call-stream.js:457:14)
    at staking-dashboard/appengine/node_modules/@grpc/grpc-js/build/src/channel.js:209:48
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Caused by: Error
    at WriteBatch.commit (staking-dashboard/appengine/node_modules/@google-cloud/firestore/build/src/write-batch.js:415:23)
    at DocumentReference.set (staking-dashboard/appengine/node_modules/@google-cloud/firestore/build/src/reference.js:341:14)
    at DBService.updateDocument (staking-dashboard/appengine/dist/services/database.js:17:67)
    at ValidatorsInfoService.processValidatorInfoData (staking-dashboard/appengine/dist/services/sync/validators-info.js:133:36)
    at staking-dashboard/appengine/dist/services/sync/validators-info.js:66:40
    at Array.forEach (<anonymous>)
    at ValidatorsInfoService.processValidatorWithPage (staking-dashboard/appengine/dist/services/sync/validators-info.js:64:37)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ValidatorsInfoService.getAllValidatorsInfo (staking-dashboard/appengine/dist/services/sync/validators-info.js:195:31)
    at async SyncService.update (staking-dashboard/appengine/dist/services/sync/index.js:22:17) {
  code: 13,
  details: 'Failed to start HTTP/2 stream',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  note: 'Exception occurred in retry method that was not classified as transient'
}
@mur-me mur-me changed the title [backend] - Firebase gRPC connectivity session isn't renewed after network glitches [backend] - Firebase connectivity session isn't renewed after network glitches Dec 12, 2024
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

No branches or pull requests

1 participant