-
Notifications
You must be signed in to change notification settings - Fork 470
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
warning: use of deprecated item 'ethereum_types::H256::from_slice': unconventional API, replaced by new_from_slice
in version 0.3
#177
Comments
@harishbm34 please update your Rust compiler, to fix |
Yes, after updating the Rust compiler I am not getting any error but still I can see the warnings. Request you to please help me to fix this. Please find the attachment for the Cargo.lock file : |
Seems that That said: the warnings are currently not fixable (see paritytech/parity-common#90). You need to bump |
Your guess is right, I am using ::from_slice inside the "sputnikvm-precompiled-interchaintrx" crate. We need to wait for ethereum-types release, and then I can update web3 --> thanks a lot for your help. I was wondering about the warnings. Now realised, that's not the issue with "rust-web3". Let's wait for ethereum-types crate release. You can proceed to close this issue. |
@harishbm34 ok, cool. Will try to release new web3 as soon as ethereum-types is up on crates.io. Cheers! |
Hi @tomusdrw, ethereum-types is now released on crates.io. Version 0.5.2 that depends on fixed-hash 0.3. Can you please update web3? |
How to resolve this warning ?
I have been using the latest version of the "web3 = "0.5.1" in Cargo.toml.
If I use, "git" path for web3 in the Cargo.toml (web3 = { git = "https://github.com/tomusdrw/rust-web3" }), getting the errors like below:
--> /Users/harisha/.cargo/git/checkouts/rust-web3-ebc1a09fd5a9a2a2/8a2cfff/src/types/traces.rs:4:20
|
4 | use serde_derive::{Deserialize, Serialize};
| ^^^^^^^^^^^ no
Deserialize
in the root. Did you mean to useSerialize
?The text was updated successfully, but these errors were encountered: