-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
DatabaseTarget - Enable OptimizeBufferReuse by default #1908
DatabaseTarget - Enable OptimizeBufferReuse by default #1908
Conversation
Seems a fail from a recent change. Is that possible? |
Reviewed 1 of 2 files at r1. src/NLog/Targets/DatabaseTarget.cs, line 93 at r1 (raw file):
what's the use of this? Not enabling in subclasses? src/NLog/Targets/DatabaseTarget.cs, line 662 at r1 (raw file):
behavior change? Comments from Reviewable |
Looks more like a bad unit test. There is no guarantee that the write-events will complete before the flush-event as MyAsyncTarget is using ThreadPool.QueueUserWorkItem. So the the flushHit-event can be triggered before everything is written, thus causing the problem with expecting 19 but only 18 written. Maybe MyAsyncTarget should apply the newly created AsyncOperationCounter :). Like it has been done in AsyncTargetWrapperTests.cs |
6befca7
to
432dd5f
Compare
Codecov Report
@@ Coverage Diff @@
## master #1908 +/- ##
=======================================
+ Coverage 81% 81% +<1%
=======================================
Files 285 285
Lines 19436 19441 +5
Branches 2263 2263
=======================================
+ Hits 15823 15837 +14
- Misses 3060 3066 +6
+ Partials 553 538 -15 |
Reviewed 1 of 2 files at r1. Comments from Reviewable |
@304NotModified Updated documentation: https://github.com/NLog/NLog/wiki/Database-target |
Waiting for NLog ver. 4.5
This change is