| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
TBH, it seems kind of pointless to me - most child processes will simply ignore it - and it's already perfectly possible to set an environment variable. I don't really see why this should be in core. |
Sorry, something went wrong.
|
Fair enough. What do you think about the docs change, however? |
Sorry, something went wrong.
|
The change to the documentation LGTM if you remove the reference to NODE_CHILD_MAX_BUFFER. |
Sorry, something went wrong.
|
@bnoordhuis ... updated so that it's just the documentation changes. Also cleaned up some errant line-wrapping issues and end-of-line-whitespace. PTAL |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
Clarify caveats on `maxBuffer` with regards to Unicode output. Refs: nodejs#1901
|
+1
|
Sorry, something went wrong.
|
@jasnell not landing cleanly, would you like to backport? |
Sorry, something went wrong.
|
will do |
Sorry, something went wrong.
|
Thanks for the reminder, will do this week. |
Sorry, something went wrong.
|
@jasnell added don't land. Feel free to still open a backport PR |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Pull Request check-list
this change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
Affected core subsystem(s)
doc
Description of change
Clarify caveats on maxBuffer with regards to Unicode output.
Refs: #1901