Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Improve the implementor's guide section on the Scheduler module #1168

Merged
gavofyork merged 10 commits into from
May 29, 2020
Merged

Improve the implementor's guide section on the Scheduler module #1168

Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
90ad2b0
remove redundant resize instruction from guide
rphmeier May 28, 2020
eba1f59
amend past code pruning to fully cover acceptance period
rphmeier May 27, 2020
77838c8
update guide again
rphmeier May 27, 2020
1375b8a
note on return value of `validation_code_at`
rphmeier May 27, 2020
d214e65
rename execution cores to availability cores
rphmeier May 28, 2020
22f7dd9
clarify terminology
rphmeier May 28, 2020
9f84990
add ReplacementTimes to the guide
rphmeier May 28, 2020
fb5cd55
fully decouple inclusion and scheduler
rphmeier May 28, 2020
9386a34
clarify parathread scheduling substantially
rphmeier May 29, 2020
e877ecf
clarify validator group selection
rphmeier May 29, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
amend past code pruning to fully cover acceptance period
  • Loading branch information
@rphmeier
rphmeier committed May 28, 2020
commit eba1f59d3472bfec7e31ed0b5700a90b0d75051a
6 changes: 4 additions & 2 deletions roadmap/implementors-guide/guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -513,9 +513,11 @@ PastCode: map (ParaId, BlockNumber) => Option<ValidationCode>;
/// but we also keep their code on-chain for the same amount of time as outdated code
/// to keep it available for secondary checkers.
PastCodeMeta: map ParaId => ParaPastCodeMeta;
/// Which paras have past code that needs pruning and the relay-chain block in which context the code was replaced.
/// Which paras have past code that needs pruning and the relay-chain block in which context the code was replaced. The second block number is the block number at which the parachain block was actually included.
/// This is to ensure the entire acceptance period is covered, not an offset acceptance period starting
/// from the time at which the parachain perceives a code upgrade as having occurred.
/// Multiple entries for a single para are permitted. Ordered ascending by block number.
PastCodePruning: Vec<(ParaId, BlockNumber)>;
PastCodePruning: Vec<(ParaId, BlockNumber, BlockNumber)>;
/// The block number at which the planned code change is expected for a para.
/// The change will be applied after the first parablock for this ID included which executes
/// in the context of a relay chain block with a number >= `expected_at`.
Expand Down