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
Run cargo update #5289
Run cargo update #5289
Conversation
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
✅ Deploy Preview for kubeapps-dev canceled.Built without sensitive environment variables
|
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
cmd/pinniped-proxy/src/pinniped.rs
Outdated
@@ -520,7 +520,7 @@ mZu9A/ivt37pOQXm/HOX6tHB | |||
|
|||
// Without any changes, the make_token_credential_request function | |||
// returns a request with the following hash. | |||
const DEFAULT_TOKEN_CREDENTIAL_REQUEST_HASH: u64 = 2363471629413450951; |
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.
We were getting this error:
thread 'pinniped::tests::test_token_credential_request_hash_identical_with_status_change' panicked at 'assertion failed: `(left == right)`
left: `2671791248625081931`,
right: `2363471629413450951`', src/pinniped.rs:590:9
I'm assuming the upgrades in the dependencies made the initial hash change, hence this change.
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.
The error is transient, which is consistent with what Michael said at #4900.
Perhaps we should just ignore this test case for now.
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.
Reverting this change in the hash in favor of just ignoring the tests.
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> This reverts commit ab2442e.
Description of the change
I've noticed the pinniped-proxy deps were out of sync in some PRs, therefore I'm just running
cargo update
once every dep has been updated.Besides, it defaults the k8s API to 1.24, as subsequent PRs will also update the corresponding go deps.
Benefits
Up to date rust deps.
Possible drawbacks
N/A
Applicable issues
Additional information
N/A