`just update-lock-files` hangs

[tcharding]

Probably because of #147. We shouldn't use all features but probably just cd into each crate and build as appropriate.

FTR to update the lock files I built node using cargo check --features=v29_0

[0xZaddyy]

so Instead of using --all-features globally, we should just build each crate individually?
i should prepare a diff to update the lock file process accordingly.

[tcharding]

Get at it! Thanks

[jamillambert]

I can't reproduce this. I tried updating the client, types and node versions to 0.9.0 in the Cargo.toml files and then running just update-lock-files, and it runs fine and produces the correct new minimal and recent lock files?

[tcharding]

Oh interesting, well that is good at least, if its just something in my environment.

[tcharding]

I think I worked out why you couldn't reproduce. If node does not need building (already previously built) then cargo check --all-features at the repo root will succeed. If you run cargo clean first then I think you'll see it hang.

[jamillambert]

I still don't see it. What I did:
Fetch master
New edit on master
cargo clean
cargo check --all-features at the repo root
node compiles fine

Also mirrored the version updates in the cargo.toml files ran cargo clean then just update-lock-files, no problems, lock files created as expected.

[tcharding]

ooph, no clue then.