| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
LGTM if CI is green: https://ci.nodejs.org/job/node-test-pull-request/1991/ |
Sorry, something went wrong.
|
@joaocgreis .. SGTM. After you land in v4.x-staging, please remove the lts-watch label and add the land-on-v4 label. Thank you! |
Sorry, something went wrong.
|
@joaocgreis can you hold off on landing on v4.x-staging until after the release of v4.4.1 (which should be tomorrow) |
Sorry, something went wrong.
Event 9 must include the string terminator in the last descriptor. Event 23 must be published with no descriptors, in accordance with the manifest. PR-URL: #5742 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Event 9 must include the string terminator in the last descriptor. Event 23 must be published with no descriptors, in accordance with the manifest. PR-URL: nodejs#5742 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed on master in: 387b6b4 CI for v4.x-staging: https://ci.nodejs.org/job/node-test-commit/2668/ |
Sorry, something went wrong.
|
Closed since it landed in master. Still need to get it landed in v4.x-staging tho. CI looks good. Failure there appears unrelated. |
Sorry, something went wrong.
|
Landed on v4.x-staging in: e7e5af9 Thanks! |
Sorry, something went wrong.
|
I have opted to back this out of v4.x-staging due to the sentiment expressed by the working group in nodejs/Release#90 Will re apply when it has time to mature in v5 |
Sorry, something went wrong.
|
+1 |
Sorry, something went wrong.
Event 9 must include the string terminator in the last descriptor. Event 23 must be published with no descriptors, in accordance with the manifest. PR-URL: #5742 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Event 9 must include the string terminator in the last descriptor. Event 23 must be published with no descriptors, in accordance with the manifest. PR-URL: #5742 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Event 9 must include the string terminator in the last descriptor. Event 23 must be published with no descriptors, in accordance with the manifest. PR-URL: #5742 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
|
This is now back in v4.x-staging |
Sorry, something went wrong.
Notable Changes:
deps:
- Fix `--gdbjit` for embedders. Backported from v8 upstream.
(Ben Noordhuis) #5577
etw:
- Correctly display descriptors for ETW events 9 and 23 on the
windows platform.
(João Reis) #5742
querystring:
- Restore throw when attempting to stringify bad surrogate pair.
(Brian White) #5858
Notable Changes:
deps:
- Fix `--gdbjit` for embedders. Backported from v8 upstream.
(Ben Noordhuis) #5577
etw:
- Correctly display descriptors for ETW events 9 and 23 on the
windows platform.
(João Reis) #5742
querystring:
- Restore throw when attempting to stringify bad surrogate pair.
(Brian White) #5858
| Back | FazBrowse Home | New Git URL |
Pull Request check-list
this change (including linting)?
test (or a benchmark) included?
Affected core subsystem(s)
ETW
Description of change
A log of ETW events can be produced with:
The resulting etl file can be open in Event Viewer. However, ETW events 9 and 23 fail to display the EventData (under the Details tab), having instead a ProcessingErrorData section with the data in raw hexadecimal. This happens because the events are not generated correctly.
There are two commits for easy review, I plan to squash and use the following commit message:
cc @nodejs/platform-windows