EBADF with streams and pipeline
See original GitHub issueSee https://github.com/raszi/node-tmp/issues/260
to address the comments: no you cannot catch the error using .catch
or try/catch
that was the point of this answer https://github.com/raszi/node-tmp/issues/260#issuecomment-719573863
Basically (I realise there is a language barrier) you cannot catch the error, at least nothing I did could.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
What's the difference between .pipe and pipeline on streams
pipe() is a method of Readable , while pipeline is a module method of stream that accepts streams to pipe. pipeline() method provide...
Read more >pipeline causes script to silently crash #38539 - nodejs/node
stream.pipeline() leaves dangling event listeners on the streams after the callback has been invoked. ... [Error: EBADF: bad file descriptor, write] {
Read more >6.2.2 Creating Pipes in C
Creating ``pipelines'' with the C programming language can be a bit more ... The child can then exec() another program, which inherits the...
Read more >Node.js Stream.pipeline() Method - GeeksforGeeks
The stream.pipeline() method is a module method that is used to the pipe by linking the streams passing on errors and accurately cleaning...
Read more >Using pipes as file streams, fdopen() - C code example
Computer Programming - C Programming Language - Using pipes as file streams, ... EBADF. fildes is not a valid open file descriptor, or...
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
detachDescriptor will cause tmp to not try to close the already closed file.
thats exactly it, I think
node-tmp
is not propagating it correctly, I’ll make a reproducible exampleOn Sun, 17 Jan 2021 at 12:29, Benjamin Gruenbaum notifications@github.com wrote: