-
Notifications
You must be signed in to change notification settings - Fork 471
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
Fix: Disable LRU flushPendingWrite
warning if disabled
#5184
Fix: Disable LRU flushPendingWrite
warning if disabled
#5184
Conversation
… comments in consensus.go
Codecov Report
@@ Coverage Diff @@
## master #5184 +/- ##
==========================================
- Coverage 53.51% 53.50% -0.01%
==========================================
Files 439 439
Lines 54985 54985
==========================================
- Hits 29423 29422 -1
- Misses 23271 23274 +3
+ Partials 2291 2289 -2
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
agreement/types.go
Outdated
@@ -68,9 +68,9 @@ const ( | |||
) |
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.
this file should not be changed in this PR
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.
ok, reverting this and separate out for another PR then
flushPendingWrite
warning if disabled, update some comments in agreementflushPendingWrite
warning if disabled
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.
I would rather see the calls that initiialise the caches in disabled mode, which currently look like this:
au.baseAccounts.init(au.log, 0, 0)
au.baseResources.init(au.log, 0, 0)
au.baseKVs.init(au.log, 0, 0)
changed to
au.baseAccounts.init(au.log, 0, 1)
au.baseResources.init(au.log, 0, 1)
au.baseKVs.init(au.log, 0, 1)
which implicitly turns off the warning, since the threshold is higher than the size.
That avoids the extra test all the time.
yea, that's fair, I will flip the change asap. |
flushPendingWrite
warning if disabledflushPendingWrite
warning if disabled
Summary
Per Pavel's request, disable
flushPendingWrite
warning if LRU cache is disabled.