"Predicate data" tutorial from The Fuel Rust SDK Book doesn't work

fuel · March 13, 2023, 12:30pm

Hi guys
Following this tutorial Predicate data - The Fuel Rust SDK I inserted the code into my code editor and it gives me that error

if I’m trying to run it I have this output

Executing task: cargo test --package predicates-test --test integration_tests -- just_test --exact --nocapture 

   Compiling predicates-test v0.1.0 (/Users/alexey/projects/fuel/predicates-test)
error[E0061]: this method takes 0 arguments but 1 argument was supplied
  --> tests/harness.rs:62:45
   |
62 |     let predicate_data: Vec<u8> = predicate.encode_data(42_u64);
   |                                             ^^^^^^^^^^^ ------ argument of type `u64` unexpected
   |
note: associated function defined here
  --> tests/harness.rs:7:1
   |
7  | / abigen!(Predicate(
8  | |     name = "Predicate",
9  | |     abi = "out/debug/predicates-test-abi.json"
10 | | ));
   | |__^
   = note: this error originates in the macro `abigen` (in Nightly builds, run with -Z macro-backtrace for more info)
help: remove the extra argument
   |
62 |     let predicate_data: Vec<u8> = predicate.encode_data();
   |                                                        ~~

error[E0308]: mismatched types
  --> tests/harness.rs:62:35
   |
62 |     let predicate_data: Vec<u8> = predicate.encode_data(42_u64);
   |                         -------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Vec<u8>`, found `Predicate`
   |                         |
   |                         expected due to this
   |
   = note: expected struct `Vec<u8>`
              found struct `Predicate`

error[E0308]: mismatched types
   --> tests/harness.rs:73:13
    |
67  |         .spend_predicate(
    |          --------------- arguments to this method are incorrect
...
73  |             Some(predicate_data),
    |             ^^^^^^^^^^^^^^^^^^^^ expected `UnresolvedBytes`, found `Option<Vec<u8>>`
    |
    = note: expected struct `UnresolvedBytes`
                 found enum `Option<Vec<u8>>`
note: associated function defined here
   --> /Users/alexey/.cargo/registry/src/github.com-1ecc6299db9ec823/fuels-signers-0.37.1/src/wallet.rs:552:18
    |
552 |     pub async fn spend_predicate(
    |                  ^^^^^^^^^^^^^^^

Some errors have detailed explanations: E0061, E0308.
For more information about an error, try `rustc --explain E0061`.
error: could not compile `predicates-test` due to 3 previous errors

 *  The terminal process "cargo 'test', '--package', 'predicates-test', '--test', 'integration_tests', '--', 'just_test', '--exact', '--nocapture'" terminated with exit code: 101. 
 *  Terminal will be reused by tasks, press any key to close it.

Thats my toolchain

Default host: aarch64-apple-darwin
fuelup home: /Users/alexey/.fuelup

installed toolchains
--------------------
beta-2-aarch64-apple-darwin (default)
beta-3-aarch64-apple-darwin
latest-aarch64-apple-darwin
latest-2023-02-18-aarch64-apple-darwin

active toolchain
-----------------
beta-2-aarch64-apple-darwin (default)
  forc : 0.31.1
    - forc-client
      - forc-deploy : 0.31.1
      - forc-run : 0.31.1
    - forc-doc : 0.31.1
    - forc-explore : 0.28.1
    - forc-fmt : 0.31.1
    - forc-index : 0.1.13
    - forc-lsp : 0.31.1
    - forc-tx - not found
    - forc-wallet : 0.1.2
  fuel-core : 0.15.3
  fuel-indexer : 0.1.13

I’m tried on force version 0.35 and 0.37
And result is the same

furnic · March 13, 2023, 4:58pm

Check out the updated tutorial, your link was for v0.33
https://rust.fuel.network/v0.37.0/predicates/predicate-data.html#predicate-data

fuel · March 14, 2023, 11:38am

Thanks
Also in the example, we have a lot of signs like “?” but my compiler doesn’t like that too much. How to allow to use of “?” characters?

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:33:75
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
33 |     let predicate = Predicate::load_from( "out/debug/predicates-test.bin")?;
   |                                                                           ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::types::errors::Error>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:46:15
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
46 |         .await?;
   |               ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::types::errors::Error>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:50:24
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
50 |         .get_provider()?
   |                        ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::signers::wallet::WalletError>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:52:15
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
52 |         .await?;
   |               ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::signers::provider::ProviderError>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:59:64
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
59 |     let predicate_data: Vec<u8> = predicate.encode_data(42_u64)?;
   |                                                                ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<_>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:73:15
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
73 |         .await?;
   |               ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::types::errors::Error>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:77:24
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
77 |         .get_provider()?
   |                        ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::signers::wallet::WalletError>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:79:15
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
79 |         .await?;
   |               ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::signers::provider::ProviderError>>` is not implemented for `()`

error[E0277]: the `?` operator can only be used in an async block that returns `Result` or `Option` (or another type that implements `FromResidual`)
  --> tests/harness.rs:84:77
   |
11 | #[tokio::test]
   | -------------- this function should return `Result` or `Option` to accept `?`
...
84 |     let balance = second_wallet.get_asset_balance(&AssetId::default()).await?;
   |                                                                             ^ cannot use the `?` operator in an async block that returns `()`
   |
   = help: the trait `FromResidual<Result<Infallible, fuels::types::errors::Error>>` is not implemented for `()`

Some errors have detailed explanations: E0061, E0277, E0308.
For more information about an error, try `rustc --explain E0061`.
error: could not compile `predicates-test` due to 12 previous errors

fuel · March 14, 2023, 11:44am

And also in the example, I have an error like

He wants to see 2 arguments right here, but if I provide 2 arguments I have the same error as in my first try

@furnic
Check it, please

Full code you can find here

furnic · March 14, 2023, 2:52pm

The ? operator in Rust can only be used in a function which returns a Result type.
You can either change your test function signature to return a result, or replace usage of ? with .unwrap();

furnic · March 14, 2023, 3:08pm

The api for working with predicates has changed. Following along with the most recent docs, we can see that:

Sending funds to the predicate is now done via predicate.receive, i.e:
predicate.receive(first_wallet, 500, asset_id, None).await?;
Encoding data and spending funds is done like this:

         predicate
            .encode_data(4096, 4096)
            .spend(second_wallet, amount_to_unlock, asset_id, None)
            .await?;

Full example here: Predicate data - The Fuel Rust SDK
You can also read the release notes for Fuels v0.34.0 on this page: Releases · FuelLabs/fuels-rs · GitHub

fuel · March 14, 2023, 3:21pm

I’m just copying and pasting the example, and I having this error

sarah · March 14, 2023, 3:29pm

You can see the full context for the example from the docs in this file: fuels-rs/lib.rs at master · FuelLabs/fuels-rs · GitHub .

The examples that use ? instead of unwrap won’t work if you copy and paste outside of a function that returns a Result type.

fuel · March 14, 2023, 3:32pm

Yes, but somehow that doesn’t work for me

github.com

FuelLabs/fuels-rs/blob/14f4c5f459d8aa50a61b30abcc65af7663473a44/examples/predicates/src/lib.rs#L55


      
          [&mut wallet, &mut wallet2, &mut wallet3, &mut receiver]
              .iter_mut()
              .for_each(|wallet| wallet.set_provider(provider.clone()));
          // ANCHOR_END: predicate_coins
          
          
// ANCHOR: predicate_load
          abigen!(Predicate(name="MyPredicate", abi="packages/fuels/tests/predicates/predicate_signatures/out/debug/predicate_signatures-abi.json"));
          
          
let predicate = MyPredicate::load_from(
              "../../packages/fuels/tests/predicates/predicate_signatures/out/debug/predicate_signatures.bin",
          )?;
          // ANCHOR_END: predicate_load
          
          
// ANCHOR: predicate_receive
          let amount_to_predicate = 512;
          
          
predicate
              .receive(&wallet, amount_to_predicate, asset_id, None)
              .await?;
          
          
let predicate_balance = provider

fuel · March 14, 2023, 3:36pm

After this fixed code became valid, there is no warnings or errors but when I’m running the code I have this error

running 1 test
thread 'just_test' panicked at 'called `Result::unwrap()` on an `Err` value: ProviderError("Response errors; Invalid transaction: The transaction contains a predicate which failed to validate: TransactionId(0xbb4b81fe6e74a6823fbd0d0a239a0890f99ff177a8baacb3a69c68dac986e277)")', tests/harness.rs:55:10

I have tried to change encode_data(4096, 4096) to encode_data(4096_u32, 4096_u64) but result is the same

The code is here

furnic · March 14, 2023, 3:50pm

I would try modifying your predicate to take 2 params of the same type, otherwise I would expect the comparison with == to fail…

fuel · March 14, 2023, 4:08pm

Remade the predicate the following code

And added types on the predicate call

github.com

chlenc/predicates-test/blob/9bba865a907fff088294d4ca603977c8c2c411b6/tests/harness.rs#L51


      
              .await
              .unwrap();
          
          
assert_eq!(balance, 500);
          
          
// We use the Predicate's `encode_data()` to encode the data we want to
          // send to the predicate. This is a builder pattern and the function
          // returns a new predicate.
          let amount_to_unlock = 500;
          
          
predicate
              .encode_data(4096_u64, 4096_u64)
              .spend(second_wallet, amount_to_unlock, asset_id, None)
              .await
              .unwrap();
          
          
// Predicate balance is zero.
          let balance = first_wallet
              .get_provider()
              .unwrap()
              .get_asset_balance(predicate.address(), AssetId::default())

After the rebuild of the predicate, I have this output

  Compiled library "core".
  Compiled library "std".
  Compiled predicate "predicates-test".
  Bytecode size is 44 bytes.
  Predicate root: 0x4189b4e1542f0fc48595b3e009bc18f2151be7af29a2def960263d67d287d326

And the error is still the same

^^/p/f/predicates-test >>> cargo test                                                                                    (master+4) 16:07:49 
    Finished test [unoptimized + debuginfo] target(s) in 0.35s
     Running tests/harness.rs (target/debug/deps/integration_tests-235965a24c31f178)

running 1 test
test just_test ... FAILED

failures:

---- just_test stdout ----
thread 'just_test' panicked at 'called `Result::unwrap()` on an `Err` value: ProviderError("Response errors; Invalid transaction: The transaction contains a predicate which failed to validate: TransactionId(0xe078c783fed0be84cdc178493e707051d1134a07919613e0a61a3e16057f32d0)")', tests/harness.rs:55:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    just_test

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.21s

error: test failed, to rerun pass `--test integration_tests`

furnic · March 14, 2023, 5:13pm

I would try increasing the tx gas limit as the next step in debugging.

mujkica · March 14, 2023, 5:22pm

I’ve tried running the example from your repo and had no problems. Have you updated your toolchain since the initial post?

For reference, I’ve managed to run it with the following:

forc : 0.35.0
fuel-core : 0.17.0

fuel · March 16, 2023, 8:18am

That works on testnet beta-3, thanks!

svntnthree · March 17, 2023, 8:58am

thank you for tutorial

fuel · March 17, 2023, 11:35am

I will make an article about predicates after eth porto
You can see more tutorials here

system · April 7, 2023, 7:36am

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Cant create predicate instance following Use type tutorial in ts sdk TypeScript SDK testnet	6	255	May 5, 2023
How to create predicate instance by Vec<u8> code using fuels-rs v0.39? Rust SDK	0	153	April 7, 2023
AssetId being generated by abigen and causing type mismatch with fuels-rs General	2	171	October 6, 2023
How can I use a configurable block in the latest version of Predicate? Rust SDK	5	213	May 16, 2023
Incorrect Input and Output types after fuels version update to v0.39 Rust SDK	6	202	April 24, 2023

"Predicate data" tutorial from The Fuel Rust SDK Book doesn't work

Related Topics