-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Check that the event source is enabled before dumping config #34879
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
Conversation
- Make sure the event source is enabled before dumping configuration. - Change the level to log always
noahfalk
left a comment
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.
LGTM : )
|
|
||
| [MethodImpl(MethodImplOptions.NoInlining)] | ||
| [Event(11, Level = EventLevel.Informational)] | ||
| [Event(11, Level = EventLevel.LogAlways)] |
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.
Why LogAlways?
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.
Payload is small enough to not cause any damage and you'll always get it once per attach
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
Using my admin privileges to merge. Builds on this PR have been failing due to unrelated flakiness with the Component tests. Merging to unblock. |
Follow up to #34680