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

Compilation Broke on Nightly #532

Closed
HTGAzureX1212 opened this issue Jan 10, 2023 · 7 comments
Closed

Compilation Broke on Nightly #532

HTGAzureX1212 opened this issue Jan 10, 2023 · 7 comments

Comments

@HTGAzureX1212
Copy link

With the latest nightly build, the compilation fails with the following errors:

error: Expected literal
   --> /home/REDACTED/.cargo/registry/src/gh.neting.cc-1ecc6299db9ec823/rdkafka-sys-4.3.0+1.9.2/src/bindings.rs:182:32
    |
182 |     RD_KAFKA_RESP_ERR__BEGIN = -200,
    |                                ^^^^

error[E0277]: the trait bound `rd_kafka_resp_err_t: From<i32>` is not satisfied
   --> /home/REDACTED/.cargo/registry/src/gh.neting.cc-1ecc6299db9ec823/rdkafka-sys-4.3.0+1.9.2/src/types.rs:455:58
    |
455 |         let description = match RDKafkaRespErr::try_from(*self as i32) {
    |                                 ------------------------ ^^^^^^^^^^^^ the trait `From<i32>` is not implemented for `rd_kafka_resp_err_t`
    |                                 |
    |                                 required by a bound introduced by this call
    |
    = note: required for `i32` to implement `Into<rd_kafka_resp_err_t>`
    = note: required for `rd_kafka_resp_err_t` to implement `TryFrom<i32>`

error[E0277]: the trait bound `rd_kafka_resp_err_t: From<i32>` is not satisfied
   --> /home/REDACTED/.cargo/registry/src/gh.neting.cc-1ecc6299db9ec823/rdkafka-sys-4.3.0+1.9.2/src/types.rs:455:33
    |
455 |         let description = match RDKafkaRespErr::try_from(*self as i32) {
    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^ the trait `From<i32>` is not implemented for `rd_kafka_resp_err_t`
    |
    = note: required for `i32` to implement `Into<rd_kafka_resp_err_t>`
    = note: required for `rd_kafka_resp_err_t` to implement `TryFrom<i32>`

Toolchain Metadata

rustc 1.68.0-nightly (3020239de 2023-01-09)
binary: rustc
commit-hash: 3020239de947ec52677e9b4e853a6a9fc073d1f9
commit-date: 2023-01-09
host: x86_64-unknown-linux-gnu
release: 1.68.0-nightly
LLVM version: 15.0.6
@Dhghomon
Copy link

Dhghomon commented Jan 10, 2023

I've been getting the same thing on stable (stable-x86_64-pc-windows-msvc) as of a few hours ago. Looks like I'm not alone!

@jaudiger
Copy link

I also got this error this morning on Rust 1.66.0 after having updated my dependencies, it was the delta (not sure if it can help):

    Updating crates.io index
    Updating axum v0.6.1 -> v0.6.2
    Updating axum-core v0.3.0 -> v0.3.1
    Updating num_enum v0.5.7 -> v0.5.8
    Updating num_enum_derive v0.5.7 -> v0.5.8
    Updating regex v1.7.0 -> v1.7.1
    Updating schannel v0.1.20 -> v0.1.21
    Removing windows-sys v0.36.1
    Removing windows_aarch64_msvc v0.36.1
    Removing windows_i686_gnu v0.36.1
    Removing windows_i686_msvc v0.36.1
    Removing windows_x86_64_gnu v0.36.1
    Removing windows_x86_64_msvc v0.36.1

@sirius1223
Copy link

same issue happed on linux and macos

@SergeStrashko
Copy link

its because of num_enum pin it to 0.5.0 and be happy.

@Degete
Copy link

Degete commented Jan 10, 2023

Exactly, the new update for the num_enum package is causing the issue, which was release 5h ago, around when everyone started to have issues.
illicitonion/num_enum@7acc582

As a temporary measure, you can just pin the version in your Cargo.toml until they release a new version fixing it:
num_enum = "=0.5.0"

If your Cargo.lock is already updated and still have issues, you might want to pin as well:
num_enum_derive =“=0.5.0"

@jaudiger
Copy link

jaudiger commented Jan 10, 2023

The num_enum crate version responsible for this build failure has been yanked. The problem should now be solved.

@HTGAzureX1212
Copy link
Author

Closing as solved.

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

6 participants