Better error messages on ErgoTree evaluation #2247
ci.yml
on: pull_request
Build without default features
3m 6s
Code coverage in tests
4m 22s
Clippy (linter)
3m 51s
Run JS tests and publish alpha versions
3m 38s
Code formatting (rustfmt)
20s
Check intra-documentation links
3m 24s
Test Swift(iOS) bindings
2m 30s
Test JNI(Android) bindings
13m 17s
Matrix: test
Annotations
29 errors and 51 warnings
Code formatting (rustfmt)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 1
|
Test Swift(iOS) bindings
Process completed with exit code 1.
|
Build without default features:
ergotree-ir/src/mir/constant.rs#L170
the method `fmt` exists for reference `&Box<SigmaProp>`, but its trait bounds were not satisfied
|
Build without default features:
ergotree-ir/src/mir/constant.rs#L171
the method `fmt` exists for reference `&Box<EcPoint>`, but its trait bounds were not satisfied
|
Build without default features:
ergotree-ir/src/mir/constant.rs#L172
the method `fmt` exists for reference `&Box<AvlTreeData>`, but its trait bounds were not satisfied
|
Build without default features:
ergotree-ir/src/mir/constant.rs#L173
the method `fmt` exists for reference `&Arc<ErgoBox>`, but its trait bounds were not satisfied
|
Build without default features
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Tests on ubuntu-latest:
ergotree-ir/src/mir/constant.rs#L170
the method `fmt` exists for reference `&Box<sigma_boolean::SigmaProp>`, but its trait bounds were not satisfied
|
Tests on ubuntu-latest:
ergotree-ir/src/mir/constant.rs#L171
the method `fmt` exists for reference `&Box<ergo_chain_types::EcPoint>`, but its trait bounds were not satisfied
|
Tests on ubuntu-latest:
ergotree-ir/src/mir/constant.rs#L172
the method `fmt` exists for reference `&Box<avl_tree_data::AvlTreeData>`, but its trait bounds were not satisfied
|
Tests on ubuntu-latest:
ergotree-ir/src/mir/constant.rs#L173
the method `fmt` exists for reference `&Arc<chain::ergo_box::ErgoBox>`, but its trait bounds were not satisfied
|
Tests on ubuntu-latest
could not compile `ergotree-ir` due to 4 previous errors
|
Tests on ubuntu-latest
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Tests on macOS-latest
The operation was canceled.
|
Tests on windows-latest
The operation was canceled.
|
Check intra-documentation links:
ergotree-ir/src/mir/constant.rs#L170
the method `fmt` exists for reference `&Box<sigma_boolean::SigmaProp>`, but its trait bounds were not satisfied
|
Check intra-documentation links:
ergotree-ir/src/mir/constant.rs#L171
the method `fmt` exists for reference `&Box<ergo_chain_types::EcPoint>`, but its trait bounds were not satisfied
|
Check intra-documentation links:
ergotree-ir/src/mir/constant.rs#L172
the method `fmt` exists for reference `&Box<avl_tree_data::AvlTreeData>`, but its trait bounds were not satisfied
|
Check intra-documentation links:
ergotree-ir/src/mir/constant.rs#L173
the method `fmt` exists for reference `&Arc<chain::ergo_box::ErgoBox>`, but its trait bounds were not satisfied
|
Check intra-documentation links
could not compile `ergotree-ir` due to 4 previous errors
|
Check intra-documentation links
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Run JS tests and publish alpha versions
Process completed with exit code 1.
|
the method `fmt` exists for reference `&std::sync::Arc<chain::ergo_box::ErgoBox>`, but its trait bounds were not satisfied:
ergotree-ir/src/mir/constant.rs#L173
error[E0599]: the method `fmt` exists for reference `&std::sync::Arc<chain::ergo_box::ErgoBox>`, but its trait bounds were not satisfied
--> ergotree-ir/src/mir/constant.rs:173:35
|
173 | Literal::CBox(v) => v.fmt(f),
| ^^^ method cannot be called on `&std::sync::Arc<chain::ergo_box::ErgoBox>` due to unsatisfied trait bounds
|
::: ergotree-ir/src/chain/ergo_box.rs:60:1
|
60 | pub struct ErgoBox {
| ------------------ doesn't satisfy `chain::ergo_box::ErgoBox: std::fmt::Display`
|
= note: the following trait bounds were not satisfied:
`chain::ergo_box::ErgoBox: std::fmt::Display`
which is required by `std::sync::Arc<chain::ergo_box::ErgoBox>: std::fmt::Display`
`std::sync::Arc<chain::ergo_box::ErgoBox>: std::fmt::Display`
which is required by `&std::sync::Arc<chain::ergo_box::ErgoBox>: std::fmt::Display`
note: the following trait must be implemented
= help: items from traits can only be used if the trait is in scope
help: the following traits are implemented but not in scope; perhaps add a `use` for one of them:
|
3 | use crate::chain::address::_::_serde::de::Expected;
|
3 | use std::fmt::Binary;
|
3 | use std::fmt::Debug;
|
3 | use std::fmt::Display;
|
and 6 other candidates
|
the method `fmt` exists for reference `&std::boxed::Box<mir::avl_tree_data::AvlTreeData>`, but its trait bounds were not satisfied:
ergotree-ir/src/mir/constant.rs#L172
error[E0599]: the method `fmt` exists for reference `&std::boxed::Box<mir::avl_tree_data::AvlTreeData>`, but its trait bounds were not satisfied
--> ergotree-ir/src/mir/constant.rs:172:38
|
172 | Literal::AvlTree(v) => v.fmt(f),
| ^^^ method cannot be called on `&std::boxed::Box<mir::avl_tree_data::AvlTreeData>` due to unsatisfied trait bounds
|
::: ergotree-ir/src/mir/avl_tree_data.rs:59:1
|
59 | pub struct AvlTreeData {
| ---------------------- doesn't satisfy `mir::avl_tree_data::AvlTreeData: std::fmt::Display`
|
= note: the following trait bounds were not satisfied:
`mir::avl_tree_data::AvlTreeData: std::fmt::Display`
which is required by `std::boxed::Box<mir::avl_tree_data::AvlTreeData>: std::fmt::Display`
`std::boxed::Box<mir::avl_tree_data::AvlTreeData>: std::fmt::Display`
which is required by `&std::boxed::Box<mir::avl_tree_data::AvlTreeData>: std::fmt::Display`
note: the following trait must be implemented
= help: items from traits can only be used if the trait is in scope
help: the following traits are implemented but not in scope; perhaps add a `use` for one of them:
|
3 | use crate::chain::address::_::_serde::de::Expected;
|
3 | use std::fmt::Binary;
|
3 | use std::fmt::Debug;
|
3 | use std::fmt::Display;
|
and 6 other candidates
|
the method `fmt` exists for reference `&std::boxed::Box<ergo_chain_types::EcPoint>`, but its trait bounds were not satisfied:
ergotree-ir/src/mir/constant.rs#L171
error[E0599]: the method `fmt` exists for reference `&std::boxed::Box<ergo_chain_types::EcPoint>`, but its trait bounds were not satisfied
--> ergotree-ir/src/mir/constant.rs:171:43
|
171 | Literal::GroupElement(v) => v.fmt(f),
| ^^^ method cannot be called on `&std::boxed::Box<ergo_chain_types::EcPoint>` due to unsatisfied trait bounds
|
::: /home/runner/work/sigma-rust/sigma-rust/ergo-chain-types/src/ec_point.rs:18:1
|
18 | pub struct EcPoint(ProjectivePoint);
| ------------------ doesn't satisfy `ergo_chain_types::EcPoint: std::fmt::Display`
|
= note: the following trait bounds were not satisfied:
`ergo_chain_types::EcPoint: std::fmt::Display`
which is required by `std::boxed::Box<ergo_chain_types::EcPoint>: std::fmt::Display`
`std::boxed::Box<ergo_chain_types::EcPoint>: std::fmt::Display`
which is required by `&std::boxed::Box<ergo_chain_types::EcPoint>: std::fmt::Display`
= help: items from traits can only be used if the trait is in scope
help: the following traits are implemented but not in scope; perhaps add a `use` for one of them:
|
3 | use crate::chain::address::_::_serde::de::Expected;
|
3 | use std::fmt::Binary;
|
3 | use std::fmt::Debug;
|
3 | use std::fmt::Display;
|
and 6 other candidates
|
the method `fmt` exists for reference `&std::boxed::Box<sigma_protocol::sigma_boolean::SigmaProp>`, but its trait bounds were not satisfied:
ergotree-ir/src/mir/constant.rs#L170
error[E0599]: the method `fmt` exists for reference `&std::boxed::Box<sigma_protocol::sigma_boolean::SigmaProp>`, but its trait bounds were not satisfied
--> ergotree-ir/src/mir/constant.rs:170:40
|
170 | Literal::SigmaProp(v) => v.fmt(f),
| ^^^ method cannot be called on `&std::boxed::Box<sigma_protocol::sigma_boolean::SigmaProp>` due to unsatisfied trait bounds
|
::: ergotree-ir/src/sigma_protocol/sigma_boolean.rs:251:1
|
251 | pub struct SigmaProp(SigmaBoolean);
| -------------------- doesn't satisfy `_: std::fmt::Display`
|
= note: the following trait bounds were not satisfied:
`sigma_protocol::sigma_boolean::SigmaProp: std::fmt::Display`
which is required by `std::boxed::Box<sigma_protocol::sigma_boolean::SigmaProp>: std::fmt::Display`
`std::boxed::Box<sigma_protocol::sigma_boolean::SigmaProp>: std::fmt::Display`
which is required by `&std::boxed::Box<sigma_protocol::sigma_boolean::SigmaProp>: std::fmt::Display`
note: the following trait must be implemented
= help: items from traits can only be used if the trait is in scope
help: the following traits are implemented but not in scope; perhaps add a `use` for one of them:
|
3 | use crate::chain::address::_::_serde::de::Expected;
|
3 | use std::fmt::Binary;
|
3 | use std::fmt::Debug;
|
3 | use std::fmt::Display;
|
and 6 other candidates
|
Clippy (linter)
Clippy had exited with the 101 exit code
|
Code coverage in tests
Process completed with exit code 1.
|
Test JNI(Android) bindings
The process '/bin/sh' failed with exit code 1
|
Code formatting (rustfmt)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Code formatting (rustfmt)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Code formatting (rustfmt)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Code formatting (rustfmt)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Code formatting (rustfmt)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test Swift(iOS) bindings
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Test Swift(iOS) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test Swift(iOS) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test Swift(iOS) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test Swift(iOS) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Build without default features
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build without default features
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Build without default features
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Build without default features
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Build without default features
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on macOS-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Tests on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Tests on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Check intra-documentation links
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Check intra-documentation links
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Check intra-documentation links
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Check intra-documentation links
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Check intra-documentation links
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run JS tests and publish alpha versions
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Run JS tests and publish alpha versions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run JS tests and publish alpha versions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run JS tests and publish alpha versions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run JS tests and publish alpha versions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Clippy (linter)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Clippy (linter)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Clippy (linter)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Clippy (linter)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Clippy (linter)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Code coverage in tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Test JNI(Android) bindings
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Test JNI(Android) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test JNI(Android) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test JNI(Android) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test JNI(Android) bindings
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|