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

Host errors and trace should be improved #42607

Closed
richlander opened this issue Sep 23, 2020 · 2 comments
Closed

Host errors and trace should be improved #42607

richlander opened this issue Sep 23, 2020 · 2 comments
Milestone

Comments

@richlander
Copy link
Member

I recently ran into an unsupported scenario, per #42478. Per the advice of the team, I enabled host tracing. It sadly did not give me more information than the cryptic error that was already available at the commandline. That was disappointing for an enormous trace file.

In the specific example, the application was attempting to use an assembly/binary that was unsupported. It should have been included in trace. It would also have been good to have a hint as to why that binary was unsupported, if known.

One imagines that there are other known cases where apps will fail to load for known reasons that are not captured in the log.

I'd propose that we add more logging and then look at opportunities to improve the console error messages. It would be really good if we could generate links to help, as well.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Host untriaged New issue has not been triaged by the area owner labels Sep 23, 2020
@ghost
Copy link

ghost commented Sep 23, 2020

Tagging subscribers to this area: @vitek-karas, @agocke
See info in area-owners.md if you want to be subscribed.

@richlander richlander added this to the 6.0.0 milestone Sep 23, 2020
@jeffschwMSFT jeffschwMSFT removed the untriaged New issue has not been triaged by the area owner label Sep 23, 2020
@agocke agocke modified the milestones: 6.0.0, 7.0.0 Aug 9, 2021
@agocke
Copy link
Member

agocke commented Jul 13, 2022

I feel as though we have a lot of concrete issues on this topic, and this one is somewhat vague. I'm going to close it in favor of the others, but happy to re-open if we want to be more specific in direction.

@agocke agocke closed this as completed Jul 13, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Aug 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

4 participants