do not use dedup cache for reprovide queue - #1181
Merged
Merged
Conversation
The legacy reprovide is not the default, and the sweeping provide provides its own deduplication. People should use new sweeping provider, and additional resources should not be devoted to the legacy provider. Closes #1180
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #1181 +/- ##
==========================================
- Coverage 63.67% 63.66% -0.01%
==========================================
Files 268 268
Lines 26984 26984
==========================================
- Hits 17181 17180 -1
+ Misses 8094 8092 -2
- Partials 1709 1712 +3
... and 9 files with indirect coverage changes 🚀 New features to boost your workflow:
|
gammazero
changed the title
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
1 participant
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.
The legacy reprovide is not the default, and the sweeping provide provides its own deduplication. People should use new sweeping provider, and additional resources should not be devoted to the legacy provider.
Closes #1180