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

Uncaught Exception: Cannot pipe to a closed or destroyed stream #351

Closed
7 tasks done
brent-statsig opened this issue Dec 19, 2024 · 1 comment
Closed
7 tasks done

Comments

@brent-statsig
Copy link

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

Copy link

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)

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