96 fix cache invalidation #110
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #110 +/- ##
==========================================
+ Coverage 95.43% 96.08% +0.65%
==========================================
Files 12 12
Lines 394 409 +15
Branches 64 70 +6
==========================================
+ Hits 376 393 +17
+ Misses 13 11 -2
Partials 5 5 ☔ View full report in Codecov by Sentry. |
adilhussain540
force-pushed
the
96-fix-cache-invalidation
branch
from
bbbc594
to
e3d4781
Compare
sergei-maertens
requested changes
Dec 7, 2023
adilhussain540
force-pushed
the
96-fix-cache-invalidation
branch
from
93abd02
to
3d53512
Compare
sergei-maertens
approved these changes
Dec 8, 2023
Closed
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.
Description
This PR addresses the cache invalidation-related bugs pointed out in #96