-
Notifications
You must be signed in to change notification settings - Fork 957
fatxpool
: ChainApi
is now async
#8875
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
Conversation
/cmd prdoc --bump minor --audience node_dev |
…-audience node_dev'
@@ -55,30 +55,30 @@ fn to_tag(nonce: u64, from: AccountId) -> Tag { | |||
data.to_vec() | |||
} | |||
|
|||
#[async_trait] |
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.
DQ: With async traits stabilized, do we even need this?
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.
#[async_trait]
also makes a future Send
. I've just tried removing this and run into some lengthy errors which seems to be related to it.
All GitHub workflows were cancelled due to failure one of the required jobs. |
ChainApi
is nowasync_trait
,validate_transaction
andblock_body
are nowasync
methods. This is just cleanup - migrating from returningFuture
toasync
method