diff options
| author | Anna Henningsen <anna@addaleax.net> | 2018-05-09 20:42:31 +0200 |
|---|---|---|
| committer | Rich Trott <rtrott@gmail.com> | 2018-12-04 13:08:54 -0800 |
| commit | ab6c09b177eca67755a4c1f1d4d35fab9d2bb5d4 (patch) | |
| tree | 9086836cb18a09beeacc663387ab2c30b649824d /doc | |
| parent | 54f8453ea1211e1a11280e337ffdfdb7bc8f4ff1 (diff) | |
| download | android-node-v8-ab6c09b177eca67755a4c1f1d4d35fab9d2bb5d4.tar.gz android-node-v8-ab6c09b177eca67755a4c1f1d4d35fab9d2bb5d4.tar.bz2 android-node-v8-ab6c09b177eca67755a4c1f1d4d35fab9d2bb5d4.zip | |
process: provide dummy stdio for non-console Windows apps
The only known condition where we could not provide appropriate
stdio streams so far were non-console Windows applications.
Since this issue has come up a few times in our issue tracker now,
switch to providing dummy streams for these cases instead.
If there are other valid cases in which `uv_guess_handle` fails,
and where there is a more sensible way to provide stdio,
we’ll probably still find out because the streams don’t work
properly either way.
Refs: https://github.com/nodejs/help/issues/1251
PR-URL: https://github.com/nodejs/node/pull/20640
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/api/errors.md | 36 |
1 files changed, 22 insertions, 14 deletions
diff --git a/doc/api/errors.md b/doc/api/errors.md index 3b4ea6156f..a766999e43 100644 --- a/doc/api/errors.md +++ b/doc/api/errors.md @@ -1795,20 +1795,6 @@ An attempt was made to load a module with an unknown or unsupported format. An invalid or unknown process signal was passed to an API expecting a valid signal (such as [`subprocess.kill()`][]). -<a id="ERR_UNKNOWN_STDIN_TYPE"></a> -### ERR_UNKNOWN_STDIN_TYPE - -An attempt was made to launch a Node.js process with an unknown `stdin` file -type. This error is usually an indication of a bug within Node.js itself, -although it is possible for user code to trigger it. - -<a id="ERR_UNKNOWN_STREAM_TYPE"></a> -### ERR_UNKNOWN_STREAM_TYPE - -An attempt was made to launch a Node.js process with an unknown `stdout` or -`stderr` file type. This error is usually an indication of a bug within Node.js -itself, although it is possible for user code to trigger it. - <a id="ERR_V8BREAKITERATOR"></a> ### ERR_V8BREAKITERATOR @@ -2065,6 +2051,28 @@ kind of internal Node.js error that should not typically be triggered by user code. Instances of this error point to an internal bug within the Node.js binary itself. +<a id="ERR_UNKNOWN_STDIN_TYPE"></a> +### ERR_UNKNOWN_STDIN_TYPE +<!-- YAML +added: v8.0.0 +removed: REPLACEME +--> + +An attempt was made to launch a Node.js process with an unknown `stdin` file +type. This error is usually an indication of a bug within Node.js itself, +although it is possible for user code to trigger it. + +<a id="ERR_UNKNOWN_STREAM_TYPE"></a> +### ERR_UNKNOWN_STREAM_TYPE +<!-- YAML +added: v8.0.0 +removed: REPLACEME +--> + +An attempt was made to launch a Node.js process with an unknown `stdout` or +`stderr` file type. This error is usually an indication of a bug within Node.js +itself, although it is possible for user code to trigger it. + <a id="ERR_VALUE_OUT_OF_RANGE"></a> ### ERR_VALUE_OUT_OF_RANGE <!-- YAML |