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(*): Bumps krustlet to use the 2021 edition #696
chore(*): Bumps krustlet to use the 2021 edition #696
Conversation
We've been tracking and using most of the latest features anyway, so this seems to make sense Signed-off-by: Taylor Thomas <taylor@oftaylor.com>
NOTE: This cannot be merged until Github actions updates to 1.56 |
been tracking the progress of the 2021 edition for a while. LGTM once it goes live! |
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.
LGTM
@@ -55,6 +55,7 @@ pub async fn pod_exited_successfully(pods: &Api<Pod>, pod_name: &str) -> anyhow: | |||
let pod = pods.get(pod_name).await?; | |||
|
|||
let state = (|| { | |||
let _ = &pod; |
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.
Out of curiosity, what does this do? Does this make the closure capture the entire variable pod
?
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.
cargo fix --edition
did this for me, so I didn't want to mess with it
bd21254
to
ee35809
Compare
Signed-off-by: Taylor Thomas <taylor@oftaylor.com>
ee35809
to
f587034
Compare
Going to merge as windows e2e is broken and the advisories are still known issues |
We've been tracking and using most of the latest rust features anyway, so
this seems to make sense