process.stdout/.stderr might loose data when calling process.exit()

this won't work reliable (but it should according to the docs):

  var empty = new Buffer(0)
  process.stdout.write(empty, function() { 
    process.stderr.write(empty, function() { 
       process.exit(code);
    });
  });

Not all data is flushed when node.js ends and thus another process using its output will not get all written data.

It also doesn't help to use something like

stream.pipe(process.stdout);
stream.push(null);

That .end() throws and an finish is never emitted makes using process.stdout/.stderr something like lottery.

Also trying to workaround via

fs.createWritableStream(null, {fd:1});

leads to another bunch of problems like EAGAIN errors.

I would suggest to implement .end() and finish events so that both process.stdout and .stderr behave like any other stream.

Please see #3170 -- the docs are incorrect but the situation is complex.

I recommend you avoid using process.exit() whenever possible.

Please also see #2972 (comment)

(Oh dear, this again.)

Yes, this again. And shame on me that I thought node.js could be used to write a unix like tool without looking on the CLOSED issues. The "issue" thing here works as reliable as process.stdout/.stderr ...

Set exit code variable without calling process.exit

See #6456 for the latest.

Rearrange logic in output_mapping

fix(cli): set stdout/stderr handles blocking on entry (#134)

Navigation Menu

Repository navigation

process.stdout/.stderr might loose data when calling process.exit() #3669

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

process.stdout/.stderr might loose data when calling process.exit() #3669

Description

Activity

Fishrock123 commented on Nov 5, 2015

Fishrock123 commented on Nov 5, 2015

minesworld commented on Nov 5, 2015

mikemaccana commented on May 17, 2016

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions