Conversation
|
@jsumners can you have a look here? |
|
@mcollina I don't think this is affected by the extreme mode buffer flushing. |
|
@jsumners the problem is that |
|
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. |
|
The original issue: The content of console.log(process.stderr)As you see, it's our old friend |
|
I see. I'll dig into it soon and see what I can figure out. |
|
@jsumners this is already passing, just check if it's ok for you. |
|
Yep. The tests pass and the following does what you'd expect: var pino = require('./')
var log = pino(process.stderr)
log.info(process.stderr) |
|
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. |
Fixes #85.
Please review, cc @krazylek