doc: refine the transaction example in the README

[mmyyrroonn]

I tried the command in the readme and met the following errors during my work

thread 'main' panicked at bin/fuel-core-client/src/main.rs:52:50:
invalid transaction json: Error("missing field `script`", line: 1, column: 133)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I replaced it with the tx from the test file below by using the function to_json()

fuel-core/tests/tests/tx.rs

Lines 155 to 172 in a9e5e89

	let script = [
	op::addi(0x10, RegId::ZERO, 0xca),
	op::addi(0x11, RegId::ZERO, 0xba),
	op::log(0x10, 0x11, RegId::ZERO, RegId::ZERO),
	op::ret(RegId::ONE),
	];
	let script: Vec<u8> = script
	.iter()
	.flat_map(|op| u32::from(*op).to_be_bytes())
	.collect();
	let tx = TransactionBuilder::script(script, vec![])
	.script_gas_limit(gas_limit)
	.maturity(maturity)
	.add_random_fee_input()
	.finalize_as_transaction();
	client.submit_and_await_commit(&tx).await.unwrap();

[CLAassistant]

All committers have signed the CLA.

[MitchTurner]

Thanks for the contribution!

Interesting. I actually get a different error:

thread 'main' panicked at bin/fuel-core-client/src/main.rs:52:50:
invalid transaction json: Error("unrecognized named flag `GasPrice`", line: 1, column: 67)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

However, your change still makes it valid :)

[mmyyrroonn]

Thanks for the contribution!

Interesting. I actually get a different error:

thread 'main' panicked at bin/fuel-core-client/src/main.rs:52:50:
invalid transaction json: Error("unrecognized named flag `GasPrice`", line: 1, column: 67)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

However, your change still makes it valid :)

Yes. You're correct. That's the first error message I met. I changed it to the MaxFee and will meet more errors. I just pick one error message to demonstrate the problem. 😄 I assume the example is out-of-date due to the quick development.

[netrome]

Thanks for the contribution!
Interesting. I actually get a different error:

thread 'main' panicked at bin/fuel-core-client/src/main.rs:52:50:
invalid transaction json: Error("unrecognized named flag `GasPrice`", line: 1, column: 67)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

However, your change still makes it valid :)

Yes. You're correct. That's the first error message I met. I changed it to the MaxFee and will meet more errors. I just pick one error message to demonstrate the problem. 😄 I assume the example is out-of-date due to the quick development.

Nice! I've also tried this now. The updated transaction seems to be valid, but trying to add it to the chain results in the error Transaction is not inserted. UTXO does not exist when running fuel core with ./target/debug/fuel-core run --db-type in-memory. The UTXO validation can be turned off by adding the --debug flag, hence running ./target/debug/fuel-core run --db-type in-memory --debug.

@mmyyrroonn while you're at it, can you add a line to the cURL example explaining to run the node with ./target/debug/fuel-core run --db-type in-memory --debug for the example to be accepted by the node?

[mmyyrroonn]

Thanks for the contribution!
Interesting. I actually get a different error:

thread 'main' panicked at bin/fuel-core-client/src/main.rs:52:50:
invalid transaction json: Error("unrecognized named flag `GasPrice`", line: 1, column: 67)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

However, your change still makes it valid :)

Yes. You're correct. That's the first error message I met. I changed it to the MaxFee and will meet more errors. I just pick one error message to demonstrate the problem. 😄 I assume the example is out-of-date due to the quick development.

Nice! I've also tried this now. The updated transaction seems to be valid, but trying to add it to the chain results in the error Transaction is not inserted. UTXO does not exist when running fuel core with ./target/debug/fuel-core run --db-type in-memory. The UTXO validation can be turned off by adding the --debug flag, hence running ./target/debug/fuel-core run --db-type in-memory --debug.

@mmyyrroonn while you're at it, can you add a line to the cURL example explaining to run the node with ./target/debug/fuel-core run --db-type in-memory --debug for the example to be accepted by the node?

It's a good suggestion. I added one sentence to demonstrate the --debug flag. It's working successfully right now. 😄

[Dentosal]

Related: #1669

[mmyyrroonn]

Should I add a change log for this PR? 😄

[netrome]

Should I add a change log for this PR? 😄

I don't think this needs a change log (@MitchTurner please correct me if I'm mistaken), so you can add the no-changelog label.

[mmyyrroonn]

Should I add a change log for this PR? 😄

I don't think this needs a change log (@MitchTurner please correct me if I'm mistaken), so you can add the no-changelog label.

That's cool. However, it seems that I cannot modify the label of this PR.

[netrome]

That's cool. However, it seems that I cannot modify the label of this PR.

Makes sense, thanks for highlighting. I've added the label for you now instead.