-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Improve logging from agent #43672
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
Improve logging from agent #43672
Conversation
Thanks for your PR, @tmat. |
{ | ||
var metadataUpdater = Type.GetType("System.Reflection.Metadata.MetadataUpdater, System.Runtime.Loader", throwOnError: false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to GetUpdaterMethods.
|
||
internal sealed class UpdateHandlerActions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to MetadataUpdateHandlerInvoker.
/// <summary> | ||
/// Internal for testing. | ||
/// </summary> | ||
internal RegisteredActions GetMetadataUpdateHandlerActions(IEnumerable<Type> handlerTypes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just moved and refactored.
@phil-allen-msft PTAL |
Currently the agent only logs to std out, which is redirected by apps (e.g. asp.net). It also doesn't consider output verbosity of dotnet-watch.
Instead of logging via stdout we now send log messages back to the dotnet-watch pipe, so that dotnet-watch can report them in the same way it does other messages.
Also refactors and cleans up the agent implementation.
Implements #43323.