Fix error where config.Shards = 0 causes "index out of range"#280
Merged
cristaloleg merged 2 commits intoallegro:masterfrom Jun 8, 2021
KDAWS-com:master
Merged
Fix error where config.Shards = 0 causes "index out of range"#280cristaloleg merged 2 commits intoallegro:masterfrom KDAWS-com:master
cristaloleg merged 2 commits intoallegro:masterfrom
KDAWS-com:master
Conversation
…ex out of range errors
Collaborator
|
Looks like |
Codecov Report
@@ Coverage Diff @@
## master #280 +/- ##
=======================================
Coverage 86.52% 86.52%
=======================================
Files 15 15
Lines 638 638
=======================================
Hits 552 552
Misses 71 71
Partials 15 15
Continue to review full report at Codecov.
|
cristaloleg
approved these changes
Jun 8, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Fixed:
If config.Shards is set to 0 then an "index out of range" error will be generated by bigcache.GetShard() at bigcache.go:220
func (c *BigCache) getShard(hashedKey uint64) (shard *cacheShard) { return c.shards[hashedKey&c.shardMask] }As the isPowerofTwo() check considers 0 a power of two.
Test:
TestClosing (bicache_test.go) failed because it didn't specify a number of Shards in its config.
All tests pass with the minor change to TestClosing.