You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ronag The only two things I could think of are a) process.exit() or equivalents being called or b) blocking JS execution that prevents the nextTick queue from running.
For debugging Node.js core, it’s sometimes a good idea to use process._rawDebug() rather than console.log(), which doesn’t use streams under the hood.
That being said, if I just add the console.log() calls like you did, it does print output for me.
Activity
addaleax commentedon Jan 5, 2020
/cc @ronag
ronag commentedon Jan 5, 2020
ronag commentedon Jan 5, 2020
addaleax commentedon Jan 5, 2020
@ronag The only two things I could think of are a) process.exit() or equivalents being called or b) blocking JS execution that prevents the nextTick queue from running.
For debugging Node.js core, it’s sometimes a good idea to use
process._rawDebug()rather thanconsole.log(), which doesn’t use streams under the hood.That being said, if I just add the
console.log()calls like you did, it does print output for me.ronag commentedon Jan 5, 2020
Oh, thanks for that! I'll keep digging.
stream: sync stream unpipe resume
stream: sync stream unpipe resume
stream: sync stream unpipe resume
stream: sync stream unpipe resume
stream: sync stream unpipe resume