A module for scheduling dispatches.
This module exposes capabilities for scheduling dispatches to occur at a specified block number or at a specified period. These scheduled dispatches may be named or anonymous and may be canceled.
NOTE: The scheduled calls will be dispatched with the default filter
for the origin: namely
fabric_system::Config::BaseCallFilter for all origin
except root which will get no filter. And not the filter contained in origin
use to call
If a call is scheduled using proxy or whatever mecanism which adds filter, then those filter will not be used when dispatching the schedule call.
schedule- schedule a dispatch, which may be periodic, to occur at a specified block and with a specified priority.
cancel- cancel a scheduled dispatch, specified by block number and index.
schedule_named- augments the
scheduleinterface with an additional
Vec<u8>parameter that can be used for identification.
cancel_named- the named complement to the cancel function.
Weights for noble_scheduler THIS FILE WAS AUTO-GENERATED USING THE TETCORE BENCHMARK CLI VERSION 2.0.0 DATE: 2020-10-27, STEPS: [50, ], REPEAT: 20, LOW RANGE: , HIGH RANGE:  EXECUTION: Some(Wasm), WASM-EXECUTION: Compiled, CHAIN: Some(“dev”), DB CACHE: 128
Items to be executed, indexed by the block number that they should be executed on.
Genesis config for the module, allow to build genesis storage.
Scheduler module declaration.
Information regarding an item to be executed in the future.
Events for this module.
Our noble’s configuration trait. All our types and constants go in here. If the noble is dependent on specific other nobles, then their configuration traits should be added to our implied traits list.
Just a simple index for naming period tasks.
The current version of Scheduled struct.
The location of a scheduled task that can be used to remove it.