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

Minor post-transfer changes #1

Merged
merged 3 commits into from
Dec 3, 2018
Merged

Minor post-transfer changes #1

merged 3 commits into from
Dec 3, 2018

Conversation

newpavlov
Copy link
Member

@newpavlov newpavlov commented Dec 3, 2018

Not sure about the minimum supported Rust version for CI, for now it's 1.27.

Copy link
Member

@dignifiedquire dignifiedquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@newpavlov
Copy link
Member Author

If you would like to continue being the main maintainer (and developer) of this crate, then I think the one to merge PRs (including this one) should be you. What do you think?

@dignifiedquire
Copy link
Member

If you would like to continue being the main maintainer (and developer) of this crate, then I think the one to merge PRs (including this one) should be you. What do you think?

Makes sense, will merge once CI is happy and publish an initial version to crates.io later today

@newpavlov
Copy link
Member Author

key::tests::key_generation_128 has failed with "unwrap() on None". I've restarted the test and it got "fixed". IIUC you have non-determinism in your tests and implementation has a bug.

Ideally we should be able to use deterministic RNG source for tests and OS RNG for everything else, but unfortunately it's not that easy right now.

@newpavlov
Copy link
Member Author

BTW it would be nice to also add fuzzing testing, see cargo-fuzz.

@dignifiedquire dignifiedquire mentioned this pull request Dec 3, 2018
@dignifiedquire
Copy link
Member

key::tests::key_generation_128 has failed with "unwrap() on None". I've restarted the test and it got "fixed". IIUC you have non-determinism in your tests and implementation has a bug.

Argh :/ I saw this once before in a project that uses this, but didn't realize it comes from here.

Created an issue #2

BTW it would be nice to also add fuzzing testing, see cargo-fuzz.

Yes, definitely need this #3

@dignifiedquire dignifiedquire merged commit d3e5d89 into master Dec 3, 2018
@newpavlov newpavlov deleted the transfer branch December 13, 2018 09:50
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