You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See a warning about a "yanked" registry. I do not know what this means, but stack overflow suggests
It means that the package has been marked as "yanked". This is usually done when the authors of have package have a very compelling reason that a certain version of a package should not be used at all, and to very strongly suggest that the package should not be used. You can ignore yanks with --force to force yanked packages to be used, but that is usually a bad idea: packages were usually yanked for a good reason.
error[E0308]: `?` operator has incompatible types
--> /home/wfey/.cargo/git/checkouts/mev-rs-343d0d727dac77aa/921fa3f/mev-build-rs/src/blinded_block_provider/api/client.rs:68:49
|
68 | let response: Value<ExecutionPayload> = self
| _________________________________________________^
69 | | .api
70 | | .post("/eth/v1/builder/blinded_blocks", signed_block)
71 | | .await?;
| |___________________^ expected struct `beacon_api_client::Value`, found `()`
|
= note: `?` operator cannot convert from `()` to `beacon_api_client::Value<ethereum_consensus::bellatrix::ExecutionPayload<256_usize, 32_usize, 1073741824_usize, 1048576_usize>>`
= note: expected struct `beacon_api_client::Value<ethereum_consensus::bellatrix::ExecutionPayload<256_usize, 32_usize, 1073741824_usize, 1048576_usize>>`
found unit type `()`
error[E0061]: this function takes 3 arguments but 1 argument was supplied
--> /home/wfey/.cargo/git/checkouts/mev-rs-343d0d727dac77aa/921fa3f/mev-build-rs/src/signing.rs:28:18
|
28 | let domain = compute_builder_domain(context)?;
| ^^^^^^^^^^^^^^^^^^^^^^--------- two arguments of type `std::option::Option<[u8; 4]>` and `std::option::Option<Node>` are missing
|
note: function defined here
--> /home/wfey/.cargo/git/checkouts/ethereum-consensus-930744fc44a7f50d/fa9c4e6/src/builder/mod.rs:27:8
|
27 | pub fn compute_builder_domain(
| ^^^^^^^^^^^^^^^^^^^^^^
help: provide the arguments
|
28 | let domain = compute_builder_domain(context, /* std::option::Option<[u8; 4]> */, /* std::option::Option<Node> */)?;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error[E0061]: this function takes 3 arguments but 1 argument was supplied
--> /home/wfey/.cargo/git/checkouts/mev-rs-343d0d727dac77aa/921fa3f/mev-build-rs/src/signing.rs:38:18
|
38 | let domain = compute_builder_domain(context)?;
| ^^^^^^^^^^^^^^^^^^^^^^--------- two arguments of type `std::option::Option<[u8; 4]>` and `std::option::Option<Node>` are missing
|
note: function defined here
--> /home/wfey/.cargo/git/checkouts/ethereum-consensus-930744fc44a7f50d/fa9c4e6/src/builder/mod.rs:27:8
|
27 | pub fn compute_builder_domain(
| ^^^^^^^^^^^^^^^^^^^^^^
help: provide the arguments
|
38 | let domain = compute_builder_domain(context, /* std::option::Option<[u8; 4]> */, /* std::option::Option<Node> */)?;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Some errors have detailed explanations: E0061, E0308.
For more information about an error, try `rustc --explain E0061`.
error: could not compile `mev-build-rs` due to 3 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `lighthouse v3.1.0 (/home/wfey/lighthouse/lighthouse)`, intermediate artifacts can be found at `/home/wfey/lighthouse/target`
make: *** [Makefile:28: install] Error 101
The text was updated successfully, but these errors were encountered:
Description
Saw the following warning during compile and didn't see anything in the issues
Version
Present Behaviour
See a warning about a "yanked" registry. I do not know what this means, but stack overflow suggests
https://stackoverflow.com/questions/68509895/what-does-package-foo-in-cargo-lock-is-yanked-in-registry-mean#:~:text=It%20means%20that%20the%20package,package%20should%20not%20be%20used.
Expected Behaviour
No yanked warnings.
Steps to resolve
Ran
cargo update
and saw errors during buildThe text was updated successfully, but these errors were encountered: