-
Notifications
You must be signed in to change notification settings - Fork 280
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
Merged PoolWaitHandles, DbConnectionPoolIdentity, removed DbBuffer #2390
Merged PoolWaitHandles, DbConnectionPoolIdentity, removed DbBuffer #2390
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2390 +/- ##
==========================================
+ Coverage 71.66% 72.04% +0.38%
==========================================
Files 308 305 -3
Lines 62297 61804 -493
==========================================
- Hits 44646 44529 -117
+ Misses 17651 17275 -376
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@edwardneal Can you address the conflicts, please? |
Thanks @DavoudEshtehari. I've handled the merge conflicts, and the test failure seems to be unrelated to me. |
Given these changes, I believe the |
I agree. I've moved the method into DbConnectionPool.cs and guarded it behind |
Contributes to #1261.
This is a little more involved than the previous merges. PoolWaitHandles and DbConnectionPoolIdentity in .NET Framework currently use direct PInvoke to wait on named objects and get the Windows identity details. I've merged these with their .NET Core counterparts, which behave the same way.
Doing so also removes the last reference to DbBuffer, which was only present in the .NET Framework project. With those references gone, I've removed this too. This contributes to three quarters of the deletions - the PR's a fair bit smaller than it looks!