-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
etw: fix descriptors of events 9 and 23 #5742
etw: fix descriptors of events 9 and 23 #5742
Conversation
LGTM |
LGTM if CI is green: https://ci.nodejs.org/job/node-test-pull-request/1991/ |
@joaocgreis is this appropriate for v4? |
@joaocgreis .. SGTM. After you land in v4.x-staging, please remove the lts-watch label and add the land-on-v4 label. Thank you! |
@joaocgreis can you hold off on landing on v4.x-staging until after the release of v4.4.1 (which should be tomorrow) |
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 CI for |
Closed since it landed in master. Still need to get it landed in v4.x-staging tho. CI looks good. Failure there appears unrelated. |
Landed on Thanks! |
I have opted to back this out of Will re apply when it has time to mature in v5 |
+1 |
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 |
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
Pull Request check-list
make -j8 test
(UNIX) orvcbuild test nosign
(Windows) pass withthis 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 theEventData
(under the Details tab), having instead aProcessingErrorData
section with the data in raw hexadecimal. This happens because the events are not generated correctly.template
attribute), but is generated from node with a dummy integer descriptor, always equal to 0.There are two commits for easy review, I plan to squash and use the following commit message:
cc @nodejs/platform-windows