mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-06-13 19:51:05 +00:00
frame-benchmarking-cli: Remove native dispatch requirement (#14474)
* frame-benchmarking-cli: Remove native dispatch requirement No need for this, we can just use the `WasmExecutor` directly. * Fixes * Pass benchmarking host functions * Ensure we can pass custom host functions
This commit is contained in:
@@ -19,7 +19,7 @@
|
||||
//!
|
||||
//! Given a committee `A` and an edge weight vector `w`, a balanced solution is one that
|
||||
//!
|
||||
//! 1. it maximizes the sum of member supports, i.e `Argmax { sum(support(c)) }`. for all `c` in
|
||||
//! 1. it maximizes the sum of member supports, i.e `Argmax { sum(support(c)) }`. for all `c` in
|
||||
//! `A`.
|
||||
//! 2. it minimizes the sum of supports squared, i.e `Argmin { sum(support(c).pow(2)) }` for all `c`
|
||||
//! in `A`.
|
||||
|
||||
@@ -343,10 +343,10 @@ impl Response {
|
||||
/// A buffered byte iterator over response body.
|
||||
///
|
||||
/// Note that reading the body may return `None` in following cases:
|
||||
/// 1. Either the deadline you've set is reached (check via `#error`;
|
||||
/// In such case you can resume the reader by setting a new deadline)
|
||||
/// 2. Or because of IOError. In such case the reader is not resumable and will keep
|
||||
/// returning `None`.
|
||||
/// 1. Either the deadline you've set is reached (check via `#error`; In such case you can resume
|
||||
/// the reader by setting a new deadline)
|
||||
/// 2. Or because of IOError. In such case the reader is not resumable and will keep returning
|
||||
/// `None`.
|
||||
/// 3. The body has been returned. The reader will keep returning `None`.
|
||||
#[derive(Clone)]
|
||||
pub struct ResponseBody {
|
||||
|
||||
@@ -220,16 +220,16 @@ pub struct OffenceDetails<Reporter, Offender> {
|
||||
/// for a typical usage scenario:
|
||||
///
|
||||
/// 1. An offence is detected and an evidence is submitted on-chain via the
|
||||
/// [`OffenceReportSystem::publish_evidence`] method. This will construct
|
||||
/// and submit an extrinsic transaction containing the offence evidence.
|
||||
/// [`OffenceReportSystem::publish_evidence`] method. This will construct and submit an extrinsic
|
||||
/// transaction containing the offence evidence.
|
||||
///
|
||||
/// 2. If the extrinsic is unsigned then the transaction receiver may want to
|
||||
/// perform some preliminary checks before further processing. This is a good
|
||||
/// place to call the [`OffenceReportSystem::check_evidence`] method.
|
||||
/// 2. If the extrinsic is unsigned then the transaction receiver may want to perform some
|
||||
/// preliminary checks before further processing. This is a good place to call the
|
||||
/// [`OffenceReportSystem::check_evidence`] method.
|
||||
///
|
||||
/// 3. Finally the report extrinsic is executed on-chain. This is where the user
|
||||
/// calls the [`OffenceReportSystem::process_evidence`] to consume the offence
|
||||
/// report and enact any required action.
|
||||
/// 3. Finally the report extrinsic is executed on-chain. This is where the user calls the
|
||||
/// [`OffenceReportSystem::process_evidence`] to consume the offence report and enact any
|
||||
/// required action.
|
||||
pub trait OffenceReportSystem<Reporter, Evidence> {
|
||||
/// Longevity, in blocks, for the evidence report validity.
|
||||
///
|
||||
|
||||
Reference in New Issue
Block a user