mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-05-31 05:11:02 +00:00
Fix nothing scheduled on session boundary (#1403)
* Fix scheduled state at session boundaries. * Cleanup + better docs. * More cleanup and fixes. * Remove 12s hack. * Add dep. * Make clippy happy --------- Co-authored-by: eskimor <eskimor@no-such-url.com>
This commit is contained in:
@@ -190,11 +190,20 @@ pub struct HostConfiguration<BlockNumber> {
|
||||
///
|
||||
/// Must be non-zero.
|
||||
pub group_rotation_frequency: BlockNumber,
|
||||
/// The availability period, in blocks. This is the amount of blocks
|
||||
/// after inclusion that validators have to make the block available and signal its
|
||||
/// availability to the chain.
|
||||
/// The minimum availability period, in blocks.
|
||||
///
|
||||
/// Must be at least 1.
|
||||
/// This is the minimum amount of blocks after a core became occupied that validators have time
|
||||
/// to make the block available.
|
||||
///
|
||||
/// This value only has effect on group rotations. If backers backed something at the end of
|
||||
/// their rotation, the occupied core affects the backing group that comes afterwards. We limit
|
||||
/// the effect one backing group can have on the next to `paras_availability_period` blocks.
|
||||
///
|
||||
/// Within a group rotation there is no timeout as backers are only affecting themselves.
|
||||
///
|
||||
/// Must be at least 1. With a value of 1, the previous group will not be able to negatively
|
||||
/// affect the following group at the expense of a tight availability timeline at group
|
||||
/// rotation boundaries.
|
||||
pub paras_availability_period: BlockNumber,
|
||||
/// The amount of blocks ahead to schedule paras.
|
||||
pub scheduling_lookahead: u32,
|
||||
|
||||
Reference in New Issue
Block a user