-
Notifications
You must be signed in to change notification settings - Fork 317
QoL | Improve build/debugging experience #3575
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
This handles cases where OnEventCommand runs during the constructor of SqlClientEventSource.
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Lots of errors from the package-based tests:
Maybe these UDTs need a package reference or two? |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3575 +/- ##
==========================================
+ Coverage 59.44% 64.00% +4.56%
==========================================
Files 268 268
Lines 62160 62167 +7
==========================================
+ Hits 36950 39792 +2842
+ Misses 25210 22375 -2835
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I see what you mean! I've just added the correct handling of |
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.
The ReferenceType
build property causes me headaches. I think with the move to true unit and integration tests, we won't need it for much longer.
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Description
These are two minor QoL changes which I've had running locally for a little while to make debugging a little easier and to speed up local builds.
OnEventCommand
is called before the SqlClientEventSource constructor finishes, and by that point theMetrics
property is still null. We now handle this case, making sure that if this happens the metrics start in an enabled state.Issues
None.
Testing
No automated tests cover this, but manual testing confirms that the build process continues to work and that I no longer receive the NullReferenceException when debugging is enabled.