-
Notifications
You must be signed in to change notification settings - Fork 75
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
Upgrade dependencies and remove deprecated failure
, which causes GitHub security alerts
#208
Conversation
- Update most dependencies to recent versions - Migrate from r#try! macro to ? operator - Fix warnings
Looks great. Really appreciate your help. Qutex is published. Thanks again and let me know if anything else needs my attention. |
amazing, thank you very much! If you could just replace |
also sorry I missed, PR #179 can also be closed, it's included here as well |
Done. Thanks again! |
Also one more thing, it looks like the Sorry to bother you like that but it would be really nice to also update |
@c0gent any news on releasing the updated |
Sorry for the delay. Published! |
Thank you very much! Now everything is looking good 👍 |
failure
tothiserror
r#try!
macro to?
operatorThere were also security alerts for crossbeam 0.7 used by
qutex
. I see that dependency was updated on git, but not published to crates.io, so I used git dependency in Cargo.toml. It would be great if you can publish updatedqutex
so we can just use the new version here.One last dependency that was not updated is
futures 0.1
. There were many changes in the API and I also seequtex
can use 0.3 beta. I think we can separate this one for now - update all other dependencies, and take care offutures
inocl
andqutex
separately.This PR also includes changes from #201 and #199 as they were dependency updates too, as well as #183, #170, #171 for warnings. Also after this PR is merged #178 can be closed.
It would be great if you could merge this PR, it causes GitHub Security alerts on dependent projects.