GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||
GeezerVison is showing github.com — lib: support `FORCE_COLOR` for non TTY streams by MoLow · Pull Request #48034 · nodejs/node Conversation
|
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
tests did not play well when running in parallel. used node:test to run them sequentially
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
/CC @nodejs/util @nodejs/console |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Antoine du Hamel <[email protected]>
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #48034 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
|
This broke tests when pulling into v18, so it needs a backport. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@danielleadams It seems |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@danielleadams cherry-picking this sequence of commits lands clearly with no conflicts and all tests pass, so I assume the staging branch is missing many many more parts 334bb17 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Talked to @MoLow offline, but staging branch is ready for backport now. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: nodejs#48034 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: nodejs#48034 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
PR-URL: #48034 Backport-PR-URL: #48684 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
|
@MoLow Small heads up, this seems to have broken |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@addaleax I am not able to reproduce this: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@MoLow Yeah, |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
This was historically done to make `console.log()` have colors. However, this makes any other code that checks `process.stdout.isTTY` incorrectly assume real TTY support. Node18 and Node20 now respect `FORCE_COLOR=1` in console, so our default behavior of forcing colors in the worker process just works out of the box. See nodejs/node#48034.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.