-
Notifications
You must be signed in to change notification settings - Fork 1.1k
pallet-revive: eth-rpc improve submit #10328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
eth_sendRawTransaction should only return a tx hash if the transaction is valid. With these udpates, we now listen to the tx event stream and only return when the Ready or Future is emitted.
|
/cmd prdoc --audience runtime_dev --bump patch |
…time_dev --bump patch'
Differential Tests Results (PolkaVM)Specified Tests
Counts
FailuresThe test specifiers seen in this section have the format 'path::case_idx::compilation_mode' and they're compatible with the revive differential tests framework and can be specified to it directly in the same way that they're provided through the The failures are provided in an expandable section to ensure that the PR does not get polluted with information. Please click on the section below for more information Detailed Differential Tests Failure Information
|
Differential Tests Results (REVM)Specified Tests
Counts
FailuresThe test specifiers seen in this section have the format 'path::case_idx::compilation_mode' and they're compatible with the revive differential tests framework and can be specified to it directly in the same way that they're provided through the The failures are provided in an expandable section to ensure that the PR does not get polluted with information. Please click on the section below for more information Detailed Differential Tests Failure Information
|
|
Getting lot of timeout or no responses in some tests, looks like in some case no progress events is emitted |
| log::debug!(target: LOG_TARGET, "Failed to submit transaction: {err:?}"); | ||
| })?; | ||
|
|
||
| tokio::time::timeout(Duration::from_secs(10), async { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Isn't a 10 second timeout too long?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currently there is an issue with the txpool that needs to be resolved before we can merge this.
the TxStatus event are only delivered at the block boundary in manual-seal mode, which make this eth_sendRawTransaction takes too much time. I am waiting for a fix before we can switch to this approach.
Also I think my initial statement is wrong here
"eth_sendRawTransaction" should only return a tx hash if the transaction is valid.
We already do that cause if the transaction is invalid, the submit future should already return an error.
|
🔒 until we can figure out why the tx event only fire at the block boundary when manual-seal is used |
With these udpates, we now listen to the tx event stream and only return when the Ready or Future
is emitted.
Depends on #10332