UnhandledPromiseRejectionWarning: Error: Deadline exceeded
See original GitHub issueEnvironment details
- OS: macOS 10.14.5
- Node.js version: v10.16.0
- npm version: 6.9.0
@google-cloud/pubsub
version: “^0.30.1”,
Steps to reproduce
- download this repo as zip
- cd samples, npm i
- node subscriptions.js list
(node:88354) UnhandledPromiseRejectionWarning: Error: Deadline exceeded
at Http2CallStream.call.on (/Users/mj/Downloads/nodejs-pubsub-master/samples/node_modules/@grpc/grpc-js/build/src/client.js:101:45)
at Http2CallStream.emit (events.js:203:15)
at process.nextTick (/Users/mj/Downloads/nodejs-pubsub-master/samples/node_modules/@grpc/grpc-js/build/src/call-stream.js:71:22)
at process._tickCallback (internal/process/next_tick.js:61:11)
(node:88354) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:88354) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
followed this guide to config auth, tried at least 3 times.
I’m sure GOOGLE_APPLICATION_CREDENTIALS and service_account are properly configured. because cloud-pubsub go examples works on my local laptop.
none of examples work at all. always got “Deadline exceeded”
btw, copied some code, deploy to cloud functions, can publish message to cloud pubsub
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:24 (9 by maintainers)
Top Results From Across the Web
Error: 4 DEADLINE_EXCEEDED: Deadline Exceeded at ...
I am trying to create a google cloud task from one of my Google Cloud Functions. This function gets triggered when a new...
Read more >[Firestore] Error: 4 DEADLINE_EXCEEDED: Deadline exceeded
A common reason for this to happen is when you don't await on an async function or forget to return a promise to...
Read more >Troubleshooting DEADLINE_EXCEEDED errors on Cloud ...
A Deadline Exceeded error may occur for several different reasons, such as overloaded Cloud Spanner instances, unoptimized schemas, or ...
Read more >Why am I getting a DEADLINE_EXCEEDED error?
This error is caused by a communication failure on the server side. This error is returned in a HTTP message with a 500...
Read more >Error: fetching abi for eosio: deadline exceeded by xx us
You can fix this by starting nodeos while setting. --abi-serializer-max-time-ms. to 50000 or so. I'm not sure if there's such an option in ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bcoe Thanks for your reply. Yes I’m running behind a proxy. Actually, this exception makes the app in a state of not receiving messages at all.
Here the exception I got:
ackIds: [ 0: "TgQhIT4wPkVTRFAGFixdRkhRNxkIaFEOT14jPzUgKEUSAAdnfjkORhoLazNcdQdRDRh0KWZza1sRVFMUWX9XWxENQGx-SgBVDR1ydGlybF8WBgFDU1bM4eqNyKT3RB1tNaO89r1ASpvFk7V0Zhs9WhJLLD5-MilFQV5AEkw5HERJUytDCypYEQ" ] code: 4 details: "Deadline exceeded"
The real issue is that this becomes an UnhandledPromiseException. Sure, errors happen, but they should not go unhandled. This completely breaks our logging solution. Any errors we catch we tag with the service and the right teams get notified. This error completely side-tracks the logs as it is send to stdout!
Please fix this!