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

chore: Allow backoff to be used in the cargo-deny config #4242

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

poljar
Copy link
Contributor

@poljar poljar commented Nov 11, 2024

Backoff seems to be unmaintained, there's no drop-in replacement so let's silence the warning for now.

Backoff seems to be unmaintained, there's no drop-in replacement so
let's silence the warning for now.
@poljar poljar requested a review from a team as a code owner November 11, 2024 09:12
@poljar poljar requested review from andybalaam and removed request for a team November 11, 2024 09:12
Copy link

codecov bot commented Nov 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.86%. Comparing base (204e6e4) to head (f27ea07).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4242      +/-   ##
==========================================
- Coverage   84.87%   84.86%   -0.02%     
==========================================
  Files         274      274              
  Lines       29719    29719              
==========================================
- Hits        25225    25222       -3     
- Misses       4494     4497       +3     

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

@poljar poljar merged commit f483f35 into main Nov 11, 2024
40 checks passed
@poljar poljar deleted the poljar/backoff-deny-exception branch November 11, 2024 12:16
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.

2 participants