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

Getting strange error regarding subchannels #1250

Closed
schmidt-sebastian opened this issue Feb 4, 2020 · 2 comments · Fixed by #1251
Closed

Getting strange error regarding subchannels #1250

schmidt-sebastian opened this issue Feb 4, 2020 · 2 comments · Fixed by #1251

Comments

@schmidt-sebastian
Copy link

Manual copy of: googleapis/nodejs-firestore#890

Environment details

  • OS: Mac OS 10.15 Beta (19A573a)
  • Node.js version: v12.10.0
  • npm version: 6.10.3
  • @google-cloud/firestore version: 3.3.4

Steps to reproduce

I am unsure how to reproduce as there doesn't seem to be much indication in my logs.
The problem I have is that I keep getting this error popping up:

(node:33) UnhandledPromiseRejectionWarning: Error: 14 UNAVAILABLE: Failed to start call on picked subchannel
    at Object.callErrorFromStatus (/api/node_modules/@grpc/grpc-js/src/call.ts:79:24)
    at Http2CallStream.<anonymous> (/api/node_modules/@grpc/grpc-js/src/client.ts:155:18)
    at Http2CallStream.emit (events.js:333:22)
    at Http2CallStream.EventEmitter.emit (domain.js:485:12)
    at /api/node_modules/@grpc/grpc-js/src/call-stream.ts:183:14
    at processTicksAndRejections (internal/process/task_queues.js:79:11)
@schmidt-sebastian
Copy link
Author

CC @jakeleventhal

@murgatroid99
Copy link
Member

I have published grpc-js version 0.6.16 with a fix for this, but in some cases you will just see a different error with the same error code.

@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants