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

Fix caching after migration to Niquests #135

Merged
merged 2 commits into from
Mar 31, 2024
Merged

Fix caching after migration to Niquests #135

merged 2 commits into from
Mar 31, 2024

Conversation

amotl
Copy link
Contributor

@amotl amotl commented Mar 31, 2024

That other patch did not get everything right wrt. proper caching. This one fixes it, applying suggestions by @Ousret. Thanks!

Copy link

codecov bot commented Mar 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.17%. Comparing base (5eabef0) to head (3818da8).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #135      +/-   ##
==========================================
- Coverage   87.24%   87.17%   -0.08%     
==========================================
  Files           9        9              
  Lines        1082     1076       -6     
==========================================
- Hits          944      938       -6     
  Misses        138      138              
Flag Coverage Δ
unittests 87.17% <100.00%> (-0.08%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@amotl amotl marked this pull request as ready for review March 31, 2024 14:30
@amotl amotl merged commit ae04c96 into main Mar 31, 2024
14 checks passed
@amotl amotl deleted the amo/fix-caching branch March 31, 2024 14:30
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.

None yet

1 participant