Comments (3)
As a workaround you can use older casper-node
version (=1.4.8).
Edit: It seems that execution engine should be updated:
from casper-client-rs.
Full compilation error below:
error[E0308]: arguments to this function are incorrect
--> lib/deploy.rs:235:22
|
235 | let deploy = Deploy::new(
| ^^^^^^^^^^^
...
241 | payment,
| ------- expected enum `casper_execution_engine::core::engine_state::executable_deploy_item::ExecutableDeployItem`, found enum `ExecutableDeployItem`
242 | session,
| ------- expected enum `casper_execution_engine::core::engine_state::executable_deploy_item::ExecutableDeployItem`, found enum `ExecutableDeployItem`
|
= note: enum `ExecutableDeployItem` and enum `casper_execution_engine::core::engine_state::executable_deploy_item::ExecutableDeployItem` have similar names, but are actually distinct types
note: enum `ExecutableDeployItem` is defined in crate `casper_execution_engine`
--> /home/andrew/.cargo/registry/src/github.com-1ecc6299db9ec823/casper-execution-engine-2.0.1/src/core/engine_state/executable_deploy_item.rs:111:1
|
111 | pub enum ExecutableDeployItem {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: enum `casper_execution_engine::core::engine_state::executable_deploy_item::ExecutableDeployItem` is defined in crate `casper_execution_engine`
--> /home/andrew/.cargo/registry/src/github.com-1ecc6299db9ec823/casper-execution-engine-3.0.0/src/core/engine_state/executable_deploy_item.rs:111:1
|
111 | pub enum ExecutableDeployItem {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: perhaps two different versions of crate `casper_execution_engine` are being used?
= note: enum `ExecutableDeployItem` and enum `casper_execution_engine::core::engine_state::executable_deploy_item::ExecutableDeployItem` have similar names, but are actually distinct types
note: enum `ExecutableDeployItem` is defined in crate `casper_execution_engine`
--> /home/andrew/.cargo/registry/src/github.com-1ecc6299db9ec823/casper-execution-engine-2.0.1/src/core/engine_state/executable_deploy_item.rs:111:1
|
111 | pub enum ExecutableDeployItem {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: enum `casper_execution_engine::core::engine_state::executable_deploy_item::ExecutableDeployItem` is defined in crate `casper_execution_engine`
--> /home/andrew/.cargo/registry/src/github.com-1ecc6299db9ec823/casper-execution-engine-3.0.0/src/core/engine_state/executable_deploy_item.rs:111:1
|
111 | pub enum ExecutableDeployItem {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: perhaps two different versions of crate `casper_execution_engine` are being used?
note: associated function defined here
--> /home/andrew/.cargo/registry/src/github.com-1ecc6299db9ec823/casper-node-1.4.13/src/types/deploy.rs:647:12
|
647 | pub fn new(
| ^^^
For more information about this error, try `rustc --explain E0308`.
error: could not compile `casper-client` due to previous error
There is suggestion about two different versions of crate casper_execution_engine
being used, so let us check Cargo.lock
:
[[package]]
name = "casper-client"
version = "1.5.0"
dependencies = [
...
"casper-execution-engine 2.0.1",
]
...
[[package]]
name = "casper-node"
version = "1.4.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "055ec2b61e829acf813fdda0b5ebd82c40b3f46800fc9098f6fa78a103845108"
dependencies = [
...
"casper-execution-engine 3.0.0",
]
That is right! Rust ❤️.
from casper-client-rs.
It was fixed in e421e81, which is part of the newly released v1.5.1
.
from casper-client-rs.
Related Issues (20)
- Client Update - RPC Endpoints - get_dictionary_item
- Client Support - RPC Endpoints - get_account
- Client Support -RPC Endpoints - get_auction_info
- Fix 'GetBlockResult' not mirroring the information returned by the node
- Client does not respect chainspec `deploys.max_deploy_size`
- Transaction Type Migration
- Research Spike
- Parsing and Building Transactions in the client
- Client Command Updates 1 of 3
- Sign Transaction command
- Client send-transaction command and backend fixes
- Client Library Updates 1 of 3
- Merge `get-transaction` command
- Add the ability to set gas prices in legacy deploys
- Add infrastructure to craft transactions into the casper-client.
- Add clap command for put-transaction RPC method
- Client Library Updates 2 of 3
- Client Library Updates 3 of 3
- Allow `CLType::Any` as session args.
- Remove args_complex from the client
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from casper-client-rs.