-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fails to build with rust 1.77.0 #4137
Comments
Hey @MikaelUrankar, thanks for reporting this. I suspected that the package ID format being stabilized would affect us when I read the Rust 1.77.0 pre-release testing blog post and landed on rust-lang/cargo#12914, but hadn't tried building on Rust 1.77. Appreciate you taking the time to build and report it, I will have this fixed. Until then, could you build with the latest stable Rust toolchain (1.76 as of now)? You can try that with a command like so: |
hyperswitch builds fine with rust 1.76.0. I am preparing the update to rust 1.77.0 (I am the FreeBSD rust maintainer) and encounter this error. |
Thanks again for reporting, I've opened #4139 to address this. |
Bug Description
I have the following error with rust 1.77.0:
The format of ids in 'cargo metadata' has changed with cargo 1.77, it's documented here: rust-lang/cargo#13528
Expected Behavior
It should build.
Actual Behavior
It fails to build.
Steps To Reproduce
exec
cargo build
with rust 1.77.0Context For The Bug
Environment
If not (or if building/running locally), please provide the following details:
rustc --version
):rustc 1.77.0 (aedd173a2 2024-03-17) (built from a source tarball) binary: rustc commit-hash: aedd173a2c086e558c2b66d3743b344f977621a7 commit-date: 2024-03-17 host: x86_64-unknown-freebsd release: 1.77.0 LLVM version: 17.0.6
cargo r --features vergen -- --version
): ``Have you spent some time checking if this bug has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: