-
Notifications
You must be signed in to change notification settings - Fork 17
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
fix: pin async-process crate #66
Conversation
@frol Ready to be reviewed |
crate/Cargo.toml
Outdated
@@ -10,7 +10,7 @@ Utility library for launching NEAR sandbox environments. | |||
|
|||
[dependencies] | |||
anyhow = "1" | |||
async-process = "1" | |||
async-process = "=1.7.0" |
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.
Please, add a comment here referencing the issue on GitHub, so it is easy to review in the future if this version pinning would be still necessary.
Also, let's use <=1.7.0
to allow a wider range of versions if some other dependency would decide to pin it to <=1.6.0
or =1.6.0
version.
Also, consider reporting an issue to the async-process bug tracker.
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.
I will merge it as a temporary fix, but as we discussed offline, there is no reason to use async-process when we can use tokio with process feature as we use tokio everywhere else.
Yes working on this now! |
There's was a test issue with linux that started after the time
async-process v1.8.0
was released. This PR pins the package to the previous version. The issue concerned is left as a todo for later investigation/work.async-process
Issue: smol-rs/async-process#55