-
Notifications
You must be signed in to change notification settings - Fork 255
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
Bump curve25519-dalek from 3.2.1 to 4.1.2 #513
Bump curve25519-dalek from 3.2.1 to 4.1.2 #513
Conversation
7c2ed90
to
d0f663d
Compare
d0f663d
to
42dfe87
Compare
42dfe87
to
7a92b06
Compare
7a92b06
to
a1632c1
Compare
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.
Thanks for the contribution! Everything looks good to me overall! Let's just fix the CI issues 🙏 . Can you rebase?
.map(|slice| { | ||
CompressedRistretto::from_slice(slice).expect("Input slice should have a length of 32") | ||
}) |
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.
.map(|slice| { | |
CompressedRistretto::from_slice(slice).expect("Input slice should have a length of 32") | |
}) | |
.and_then(|slice| CompressedRistretto::from_slice(slice).ok()) |
Since we are returning None
if the input is wrong length, it seems like we can just add .ok()
here and remove the line above that does the length check.
@andreisilviudragnea, I was wondering if you still had plans to update this PR? It is completely fine if not since we have another community PR that does the same: #946. If you are still willing to work on this PR, please let me know by tomorrow 🙏 since we do need to bump the dalek crate. |
I can update it in a few minutes if it's ok |
0498cfe
to
2e91035
Compare
2e91035
to
a0c0ac9
Compare
@samkim-crypto There are a few problems to fix on CI, but let's handle them one by one. First of all, all errors in CI related to So the first step is to create a CI image with a newer Rust Nightly version than 23.02.2024. I see @brooksprumo last updated the CI image in solana-labs#34673, so they should know how to update it to a newer Rust Nightly than 23.02.2024. |
3b9f06c
to
1dbcef9
Compare
@andreisilviudragnea sorry for the late. we have merged the bumping PR! you can rebase and continue with this one! |
008bdab
to
5277b7f
Compare
e02c90c
to
45307f3
Compare
looks like we run into some other issues 🫠 If you don't mind, I can take this one over. I will make sure to credit you and keep your name! |
@yihau Hello, ok, thank you, as I am quite crowded these days. |
when will this be merged ? |
3c1d750
to
d7b2313
Compare
@yihau I wanna try to fix this this weekend. |
Fix bump rand to 0.8.5
Hello. First of all, I don't know why the latest CI trigger did not run the
comes from the fact that both solana-program-library repo started depending on I suggest re-exporting After merging #1657, I will create a PR in |
d7b2313
to
a147075
Compare
we also need to fix this one: https://buildkite.com/anza/agave/builds/5647 |
@andreisilviudragnea sorry, I think I will try to split/clean this commit bd41d6a into smaller pieces. it do too many things together. btw, I will commit them to here. I want your name can be kept in the git history! updated: I think I will keep you code but overwrite with mine. |
moved to #1693 |
Superseded by #1693. |
curve25519-dalek
from 3.2.1 to 4.1.2sha3
version mismatchrand
to 0.8.5 in build(deps): bump rand from 0.7.3 to 0.8.5 #36Problem
Dependabot tried to bump
rand
to 0.8.5 in #36, but failed to do so.Summary of Changes
I updated the necessary dependencies together for
rand
update to succeed:curve25519-dalek
sha3
rand
Fixes #36