Skip to content
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

cargo ledger build failed due to a newer version cargo.lock file #214

Closed
Pana opened this issue Nov 5, 2024 · 1 comment
Closed

cargo ledger build failed due to a newer version cargo.lock file #214

Pana opened this issue Nov 5, 2024 · 1 comment
Assignees

Comments

@Pana
Copy link
Contributor

Pana commented Nov 5, 2024

More and more Rust crates are starting to use version 4 format of Cargo.lock. For example, ethereum-types, a foundational library for Ethereum application development by ParityTech, leads to compilation failures when introduced.

Use Rust nightly toolchain: nightly-2023-11-10
error: failed to parse lock file at: /app/Cargo.lock

Caused by:
  lock file version 4 requires `-Znext-lockfile-bump`
thread 'main' panicked at /opt/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-ledger-1.5.1/src/main.rs:274:41:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Run the building command with one additional option -Znext-lockfile-bump can solve it, but don't know how to set it when using VS code extension.

It's recommend to upgrade the build image's rust version to a newer one to solve it, for example rustc 1.79

@yogh333 yogh333 self-assigned this Nov 5, 2024
@yogh333 yogh333 mentioned this issue Dec 13, 2024
@yogh333
Copy link
Contributor

yogh333 commented Dec 13, 2024

Yes Rust version to be upgraded before EOY 🤞

@Pana Pana closed this as completed Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants