Repository navigation
Tracking issue: stdio problems #6980
Description
Activity
You can add this one to the list:
#6867 Missing or truncated error message
It's a variation of the
process.exit()stdio truncating problem but with uncaught exceptions.Edit: reproduced on node 5.x on Linux. Same issue likely exists on node 4.x.
Reacted by Jeremiah SenkpielNo guarantees on v5.x since it's now in critical-maintinence-only mode, but we'll try to get in v4.x soon.
RC for #6895 building at https://ci-release.nodejs.org/job/iojs+release/921/ (Updated: new ci (2))
I have an RC up at https://nodejs.org/download/rc/v6.2.1-rc.1/ that should fix the OS X problems.
Please test.cc-ing the people from other threads: @isaacs, @nodejs/npm, @Qix-, @eljefedelrodeodeljefe, @bcoe, @mikemaccana, @mgol
Qix- is missing the Overall/Read permission
@Qix- Are you getting that attempting to access the directory, or the files themselves?
(or is node making that error?)
@Fishrock123 Works now, not sure what changed. :) I'll give it a try.
46 remaining items
- added 8 commits that reference this issue
on Jul 11, 2016 ref: #12970
Closing as it's not clear if at all if there's anything remaining to do here and there's been zero activity since may
This is a meta-issue for tracking multiple related but distinct stderr/stdout issues.
Below are checklists indicating the progress of these issues & pull requests.
A checkmark indicates it is resolved (or merged).
This issue encompasses the following issues:
And the following pull requests:
process.exit()process: flush stdout/stderr uponprocess.exit()#6773The current item in focus is:
n/a
The TTY (Terminal) issues have been resolved. Pipes still remain a problem.
This pr was a result of the discussion in #6968 to better track all the efforts going on here.
[EDIT by @Trott: Did some edits around the 6773 PR checklist item, but undid them]