The API eth_getTransactionCount(..., "pending") is not synchronous with the API eth_sendRawTransaction.

[yangby-cryptape]

Description

• Write a script with your favorite language.

  • Get the nonce M with pending transactions for a sender through the JSON-RPC.
  • Construct a transaction.
  • Send the transaction.
  • Get the nonce N with pending transactions for a sender through the JSON-RPC immediately, do NOT wait for the transaction to be mined.
  • Check if M is equal to N.

• Start a Ethereum dev chain with Geth and parameters --dev --dev.period 3.

  • Run the script.

• Start a Axon dev chain with default configuration [params.consensus_config] interval = 3000.

  • Run the script.

• Compare the results of above tests:

  • No failed tests on Ethereum.
  • More than 50% tests on Axon are failed.

• Base on the previous fact, on Axon, transactions could NOT be sent one by one immediately, because the API eth_getTransactionNonce(..., "pending") is not synchronous with the API eth_sendRawTransaction.

[yangby-cryptape]

Even we try to fix it with a tricky way as following:

axon/core/api/src/jsonrpc/impl/web3.rs

Lines 228 to 230 in 7610890

	// TODO `eth_getTransactionCount(..., "pending")` should be synchronous with
	// `eth_sendRawTransaction`. Temporary solution for axonweb3/axon#1544.
	sleep(Duration::from_millis(MEMPOOL_REFRESH_TIMEOUT)).await;

But it isn't fixed completely, just increased the chance for success.

I do the test as the issue described again, the result is:

• For Axon: Total: 100, passed: 65, failed: 35.
• For Geth: Total: 100, passed: 100, failed: 0.

That's why some CI checks failed randomly.

[Flouse]

That's why some CI checks failed randomly.

• Do you mean Sometimes the test eth_getCode › eth_getCode_9 failed by accident #1579 ?

[yangby-cryptape]

That's why some CI checks failed randomly.

* Do you mean [Sometimes the test `eth_getCode › eth_getCode_9` failed by accident #1579](https://github.com/axonweb3/axon/issues/1579) ?

No, I just guess it is related to "v3_core_test" timeout or some other timeouts.

I didn't check #1579.

[Flouse]

No, I just guess it is related to "v3_core_test" timeout or some other timeouts.

The v3-core-test (ubuntu-22.04) action has timed out.
cc @sunchengzhu