-
Notifications
You must be signed in to change notification settings - Fork 406
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: fix many warnings across the codebase #2955
Conversation
…lic methods that weren't being used anywhere Signed-off-by: Stephen Carman <[email protected]>
Signed-off-by: Stephen Carman <[email protected]>
946a6c4
to
84cf623
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2955 +/- ##
==========================================
- Coverage 72.26% 72.21% -0.05%
==========================================
Files 131 128 -3
Lines 40660 40329 -331
Branches 40660 40329 -331
==========================================
- Hits 29382 29124 -258
+ Misses 9394 9348 -46
+ Partials 1884 1857 -27 ☔ View full report in Codecov by Sentry. |
crates/aws/src/constants.rs
Outdated
AWS_S3_ASSUME_ROLE_ARN, | ||
AWS_S3_ROLE_SESSION_NAME, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mentioned to @hntd187 in Slack that I would like to avoid removing these deprecation warnings until we have a few more releases which is print deprecation warnings for people
Signed-off-by: Stephen Carman <[email protected]>
Description
Fixed a lot of warnings across the codebase according to clippy and
cargo check
the S3 options one is the only one I am not 100% sure is correct, but @rtyler maybe you can comment on if it's a good idea to remove the deprecated key usages. Otherwise I can revert those.Related Issue(s)
Closes my own internal OCD about warnings (despite there still being one)