| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Is it possible to add a regression test? |
Sorry, something went wrong.
There was a problem hiding this comment.
Thank you for catching this!
Sorry, something went wrong.
|
@cjihrig I will try to do that later this week, but I don't think that it is required in order to do a revert. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
This reverts commit 7fa5f54. The reverted commit breaks the logic behind --trace-sync-io, it should be enabled only at a certain point in time, while that commit enables it from the very start, causing warnings be printed for all sync io instead of sync io after the first tick of the event loop as documented. Fixes: nodejs#28913 Refs: nodejs#22726 Refs: https://nodejs.org/api/cli.html#cli_trace_sync_io PR-URL: nodejs#28926
|
Force-push just now does not change the code, just altered the commit message to add an explanation and refs. |
Sorry, something went wrong.
Sorry, something went wrong.
This reverts commit 7fa5f54. The reverted commit breaks the logic behind --trace-sync-io, it should be enabled only at a certain point in time, while that commit enables it from the very start, causing warnings be printed for all sync io instead of sync io after the first tick of the event loop as documented. Fixes: nodejs#28913 Refs: nodejs#22726 Refs: https://nodejs.org/api/cli.html#cli_trace_sync_io PR-URL: nodejs#28926 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This reverts commit 7fa5f54. The reverted commit breaks the logic behind --trace-sync-io, it should be enabled only at a certain point in time, while that commit enables it from the very start, causing warnings be printed for all sync io instead of sync io after the first tick of the event loop as documented. Fixes: #28913 Refs: #22726 Refs: https://nodejs.org/api/cli.html#cli_trace_sync_io PR-URL: #28926 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
This reverts commit 7fa5f54.
Fixes: #28913
7fa5f54 breaks the logic behind --trace-sync-io, it should be enabled only at a certain point in time, while that commit enables it from the very start, causing the issue linked above.
Or am I missing something?
Refs: https://nodejs.org/api/cli.html#cli_trace_sync_io
Refs: #22726
Checklist