Skip to content
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

Hook up the WIL fallback error tracer in Terminal #7864

Merged
3 commits merged into from
Oct 9, 2020
Merged

Conversation

DHowett
Copy link
Member

@DHowett DHowett commented Oct 8, 2020

This pull request introduces (a very, very stripped-down copy of) the
WIL fallback error reporter.

It emits error records, usually immediately before the application
implodes, into the event stream.

This should improve diagnosability of issues that take Terminal down,
and allow us to give out a .wprp file to gather traces from users.

@DHowett
Copy link
Member Author

DHowett commented Oct 8, 2020

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@metathinker
Copy link
Contributor

metathinker commented Oct 8, 2020

Question: One thing I've never really understood about WIL is this: What's the difference between "telemetry" and "non-telemetry" messages written by the _IF_FAILED error handling macros?

I know that in the Microsoft-internal extension to WIL, only the telemetry messages get written out on the DLL's previously registered TraceLogging ETW path, which this PR emulates, but I don't know how WIL decides on the telemetry versus not distinction in the first place.

@DHowett
Copy link
Member Author

DHowett commented Oct 8, 2020

That's an excellent question. I believe it's telemetry by default unless you use a member on the WIL helper class (the one that the macros emit, and which is elided here!) to set the default reporting type to TraceLogging (only).

@DHowett DHowett requested a review from miniksa October 8, 2020 21:54
@DHowett DHowett added the AutoMerge Marked for automatic merge by the bot when requirements are met label Oct 9, 2020
@ghost
Copy link

ghost commented Oct 9, 2020

Hello @DHowett!

Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost ghost merged commit cd76893 into master Oct 9, 2020
@ghost ghost deleted the dev/duhowett/wil-error branch October 9, 2020 22:25
skyline75489 pushed a commit to skyline75489/terminal that referenced this pull request Oct 10, 2020
This pull request introduces (a very, very stripped-down copy of) the
WIL fallback error reporter.

It emits error records, usually immediately before the application
implodes, into the event stream.

This should improve diagnosability of issues that take Terminal down,
and allow us to give out a .wprp file to gather traces from users.
DHowett added a commit that referenced this pull request Oct 19, 2020
This pull request introduces (a very, very stripped-down copy of) the
WIL fallback error reporter.

It emits error records, usually immediately before the application
implodes, into the event stream.

This should improve diagnosability of issues that take Terminal down,
and allow us to give out a .wprp file to gather traces from users.

(cherry picked from commit cd76893)
@ghost
Copy link

ghost commented Nov 11, 2020

🎉Windows Terminal v1.4.3141.0 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Nov 11, 2020

🎉Windows Terminal Preview v1.5.3142.0 has been released which incorporates this pull request.:tada:

Handy links:

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AutoMerge Marked for automatic merge by the bot when requirements are met
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants