feat(service): get rid of cargo dependency#922
Conversation
|
I have time, so I can do service part 2 as well. |
Sounds good @iamwacko ! Let us know if you need help. We will review this whenever it's ready. |
jonaro00
left a comment
There was a problem hiding this comment.
It's hard to accurately review Rust code without rust-analyzer at hand, but here are some thoughts I had. Don't worry if I'm wrong about something.
|
@iamwacko let me know if you have questions on the changes I proposed and we can set up a call to get through them. The PR is on the right path and we'll just need to polish a bit the code async-wise, while keeping it on par with the old functionality. We have a codebase walkthrough session next Monday (if that helps) and a mentoring session next Wednesday, but feel free to hit me up with qs in private on Discord if you feel stuck. |
jonaro00
left a comment
There was a problem hiding this comment.
I found some more small things.
I read some more about tokio's Command.
It sounds like it is the proper replacement for spawn_blocking + std Command, so that should be fine.
oddgrd
left a comment
There was a problem hiding this comment.
This looks pretty close @iamwacko! I left a few small comments, but I think the main thing we need to fix is sending the build logs to the build_workspace caller, which Iulian pointed out. Let us know if you are stuck on this and need any help!
oddgrd
left a comment
There was a problem hiding this comment.
Nice progress! I took a look at your latest changes and saw what may be an easier way to read the output, let me know if you think it could work!
iulianbarbu
left a comment
There was a problem hiding this comment.
Thanks @iamwacko ! This is great 🥳 .
|
I think there is a regression on |
We must investigate the failing integration test on cargo-shuttle.
|
I see the problem. - gets turned into _ by cargo, but I didn't account for that so it tries to execute hello-world.wasm instead of hello_world.wasm. I also didn't catch it because for a while cargo-shuttle was failing for unrelated reasons. |
|
Now the |
|
Looks like the only test failures I have are #821 |
Description of change
is_next,is_alpha,ensure_bin,ensure_cdylib, andclean_crateno longer requirecargo.partially closes #756, particularly service part 1.
How Has This Been Tested (if applicable)?
I ran
cargo test,cargo fmt, andcargo clippy.