-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Conversation
Also, I think we might need something like Alternatively, there's no explicit reason to not just wrap a |
The SpawnNamed trait provides you with a function for spawning blocking tasks. (I did not looked at the pr on how you solved this now) |
@bkchr OK, we need to add that to the |
Final sign-off? |
roadmap/implementers-guide/src/node/utility/candidate-validation.md
Outdated
Show resolved
Hide resolved
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.
A few smaller nitpicks, but looks very good overall
Thanks for the review @drahnr |
bot merge |
Waiting for commit status. |
Checks failed; merge aborted. |
bot merge |
Trying merge. |
* master: Candidate Validation Subsystem (#1432) reduce slash defer durations (#1504) Implement the Runtime API subsystem (#1494) Companion for #6610 (Balances Weight Trait) (#1425) [CI] Publish draft release redux (#1493) Update README docs related to local build (#1479) Add a default trie-memory-tracker feature to the cli (#1502) Companion PR for `Add a `DefaultQueue` type alias to remove the need to use `sp_api::TransactionFor`` (#1499) Fix bitfield signing (#1466) Update Substrate, bump versions, clean up sort (#1496) Bump Substrate
Closes #1241
This is a very basic implementation; it doesn't do jobs or results-caching or anything like that. It simply wraps a pool of processes used for candidate validation (a utility we had already implemented for v0) and forwards all validation requests to it.
Still TODO: