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
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
No response
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
I'm seeing this uncaught exception in our production services - it looks like something an exception isn't being handled as expected?
Error: Cannot pipe to a closed or destroyed stream
at pipelineImpl (node:internal/streams/pipeline:264:15)
at pipeline (node:internal/streams/pipeline:183:10)
at PassThrough. (/usr/app/node_modules/.pnpm/teeny-request@9.0.0/node_modules/teeny-request/src/index.ts:269:19)
at Object.onceWrapper (node:events:628:26)
at PassThrough.emit (node:events:525:35)
at /usr/app/node_modules/.pnpm/teeny-request@9.0.0/node_modules/teeny-request/src/index.ts:286:23
at processTicksAndRejections (node:internal/process/task_queues:105:5)
Node version: v23.4.0
Its not clear to me which downstream service this is requesting to. We use GCS + pubsub in our service, but there is no obvious traces around which of these is failing, or what is causing the destroyed stream. I'm not sure how to reproduce.
A clear and concise description of what the bug is, and what you expected to happen.
The bug is an uncaught exception - I would expect all exceptions to be caught
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
No response
The text was updated successfully, but these errors were encountered:
Issue was opened with an invalid reproduction link. Please make sure the repository is a valid, publicly-accessible github repository, and make sure the url is complete (example: https://github.com/googleapis/google-cloud-node)
Please make sure you have searched for information in the following guides.
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
No response
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
I'm seeing this uncaught exception in our production services - it looks like something an exception isn't being handled as expected?
Error: Cannot pipe to a closed or destroyed stream
at pipelineImpl (node:internal/streams/pipeline:264:15)
at pipeline (node:internal/streams/pipeline:183:10)
at PassThrough. (/usr/app/node_modules/.pnpm/teeny-request@9.0.0/node_modules/teeny-request/src/index.ts:269:19)
at Object.onceWrapper (node:events:628:26)
at PassThrough.emit (node:events:525:35)
at /usr/app/node_modules/.pnpm/teeny-request@9.0.0/node_modules/teeny-request/src/index.ts:286:23
at processTicksAndRejections (node:internal/process/task_queues:105:5)
Node version: v23.4.0
Its not clear to me which downstream service this is requesting to. We use GCS + pubsub in our service, but there is no obvious traces around which of these is failing, or what is causing the destroyed stream. I'm not sure how to reproduce.
A clear and concise description of what the bug is, and what you expected to happen.
The bug is an uncaught exception - I would expect all exceptions to be caught
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
No response
The text was updated successfully, but these errors were encountered: