-
Notifications
You must be signed in to change notification settings - Fork 647
Closed
Labels
api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
We've been seeing this in our logs several times a day:
TypeError: requestStream.end is not a function
at resetStreams (/app/node_modules/retry-request/index.js:79:23)
at retryAfterDelay (/app/node_modules/retry-request/index.js:103:7)
at ClientReadableStream.onResponse (/app/node_modules/retry-request/index.js:115:9)
at emitOne (events.js:96:13)
at ClientReadableStream.emit (events.js:191:7)
at ClientReadableStream._emitStatusIfDone (/app/node_modules/grpc/src/node/src/client.js:204:12)
at ClientReadableStream._receiveStatus (/app/node_modules/grpc/src/node/src/client.js:180:8)
at /app/node_modules/grpc/src/node/src/client.js:592:14
I'm not sure what triggers the underlying stream error, but emitting an error in _emitStatusIfDone does trigger it consistently.
Environment details
- Node.js version: 7.9
- pubsub-version: 0.11.0
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.