Skip to content
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

Expired reason iota fix #255

Merged
merged 7 commits into from
Jan 18, 2022

Conversation

jgheewala
Copy link
Contributor

No description provided.

jgheewala and others added 6 commits October 8, 2019 21:41
@jgheewala
Copy link
Contributor Author

rebasing #181 to versions/v3-prep

@codecov-io
Copy link

codecov-io commented Nov 17, 2020

Codecov Report

Merging #255 (83cd9cd) into versions/v3-prep (92a824f) will increase coverage by 0.45%.
The diff coverage is n/a.

Impacted file tree graph

@@                 Coverage Diff                  @@
##           versions/v3-prep     #255      +/-   ##
====================================================
+ Coverage             86.56%   87.01%   +0.45%     
====================================================
  Files                    15       15              
  Lines                   640      647       +7     
====================================================
+ Hits                    554      563       +9     
+ Misses                   71       68       -3     
- Partials                 15       16       +1     
Impacted Files Coverage Δ
bigcache.go 98.79% <ø> (ø)
queue/bytes_queue.go 87.82% <0.00%> (-1.07%) ⬇️
shard.go 86.75% <0.00%> (+1.82%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92a824f...83cd9cd. Read the comment docs.

@janisz
Copy link
Collaborator

janisz commented Nov 17, 2020

What exactly does it fix? Can you provide a failing test that is fixed by this change?

@jgheewala
Copy link
Contributor Author

@janisz this PR is mainly moving #181 to "v3-prep" branch. All the discussion can be found in original PR..

I can certainly add test case for this scenario.

Currently all const for RemovedReason are explicitly
set to avoid any breaking changes. For v3 migrating the reasons
to iota makes code readability and managing addition of more reasons
easier in the future.

Test: Validated all test cases run successfully.
@jgheewala
Copy link
Contributor Author

@janisz i already wrote test case back TestBigCache_GetWithInfo and that tests this scenario..

Let me know if you need more testing on top of that.

Also #216 adjusted the values for const.

My changes are just adding iota for better code readability and removing the explicit values.

@jgheewala
Copy link
Contributor Author

@mxplusb will this make cut for v3 ?

@janisz janisz merged commit 4854511 into allegro:versions/v3-prep Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants