-
Notifications
You must be signed in to change notification settings - Fork 84
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 changes for kani release #380
Conversation
@micolous We're gonna need to do something to get away from the git rev versions here so we can do releases in future I think. |
I'd like @micolous input before I proceed on this :) |
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.
Actually, this breaks on CI
fido-key-manager/src/main.rs
Outdated
@@ -13,7 +13,7 @@ use std::time::Duration; | |||
use tokio_stream::StreamExt; | |||
#[cfg(feature = "solokey")] | |||
use webauthn_authenticator_rs::ctap2::SoloKeyAuthenticator; | |||
use webauthn_authenticator_rs::prelude::WebauthnCError; | |||
// use webauthn_authenticator_rs::prelude::WebauthnCError; |
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.
This should be gated on #[cfg(feature = "solokey")]
to fix the warning and not break when that feature is enabled.
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.
K
@micolous We had a bunch of issues generally, because we can't use git versions of things on crates.io, which meant btleplug was problematic. So we probably generally have a bunch of cleanup to get to a releasable state, which I want to do "sooner than later" |
7a2761c
to
a380f08
Compare
I dunno what I just did, but I think I cooked this PR 🤣 I think I close it in favour of another attempt |
No description provided.