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

Support writing the logs to stderr when i/o is redirected #86

Merged
merged 1 commit into from
Sep 13, 2016
Merged

Conversation

mcollina
Copy link
Member

@mcollina mcollina commented Sep 11, 2016

Fixes #85.

Please review, cc @krazylek

@mcollina
Copy link
Member Author

@jsumners can you have a look here?

@jsumners
Copy link
Member

@mcollina I don't think this is affected by the extreme mode buffer flushing. _writableState doesn't track whether or not the backing file descriptor is blockable. Indeed, I pulled this patch into my feature branch and ran the tests. Everything is checking out just fine.

@mcollina
Copy link
Member Author

@jsumners the problem is that stderr do not have a _writableState, because it inherits directly from Stream.

@jsumners
Copy link
Member

It looks to have one to me:

> process.stderr
WriteStream {
  // *snip*
  _writableState:
   WritableState {
     objectMode: false,
     highWaterMark: 16384,
     needDrain: false,
     ending: false,
     ended: false,
     finished: false,
     decodeStrings: false,
     defaultEncoding: 'utf8',
     length: 0,
     writing: false,
     corked: 0,
     sync: true,
     bufferProcessing: false,
     onwrite: [Function],
     writecb: null,
     writelen: 0,
     bufferedRequest: null,
     lastBufferedRequest: null,
     pendingcb: 0,
     prefinished: false,
     errorEmitted: false,
     bufferedRequestCount: 0,
     corkedRequestsFree: CorkedRequest { next: null, entry: null, finish: [Function] } },
  writable: true,
  allowHalfOpen: false,
  destroyed: false,
  _bytesDispatched: 0,
  _sockname: null,
  _writev: null,
  _pendingData: null,
  _pendingEncoding: '',
  server: null,
  _server: null,
  columns: 130,
  rows: 50,
  _type: 'tty',
  fd: 2,
  _isStdio: true,
  destroySoon: [Function],
  destroy: [Function] }

I'm not clear what you want me to investigate here.

@mcollina
Copy link
Member Author

The original issue:

$ node a.js 2> out
SyncWriteStream {
  domain: null,
  _events: {},
  _eventsCount: 0,
  _maxListeners: undefined,
  fd: 2,
  writable: true,
  readable: false,
  autoClose: false,
  _type: 'fs',
  _isStdio: true,
  destroySoon: [Function],
  destroy: [Function] }

The content of a.js:

console.log(process.stderr)

As you see, it's our old friend SyncWriteStream.

@mcollina mcollina changed the title Support writing the logs to stderr Support writing the logs to stderr when i/o is redirected Sep 13, 2016
@jsumners
Copy link
Member

I see. I'll dig into it soon and see what I can figure out.

@mcollina
Copy link
Member Author

@jsumners this is already passing, just check if it's ok for you.

@jsumners
Copy link
Member

Yep. The tests pass and the following does what you'd expect:

var pino = require('./')
var log = pino(process.stderr)
log.info(process.stderr)

@github-actions
Copy link

github-actions bot commented Feb 9, 2022

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't log to stderr in tricky case
2 participants