A data shred cannot be LAST_SHRED_IN_SLOT if not also DATA_COMPLETE_SHRED. So LAST_SHRED_IN_SLOT should also imply DATA_COMPLETE_SHRED: https://github.com/solana-labs/solana/blob/74b586ae7/ledger/src/shredder.rs#L116-L117 https://github.com/solana-labs/solana/blob/74b586ae7/core/src/broadcast_stage/standard_broadcast_run.rs#L80-L81 However current shred constructs allow specifying a shred which is LAST_SHRED_IN_SLOT but not DATA_COMPLETE_SHRED: https://github.com/solana-labs/solana/blob/74b586ae7/ledger/src/shred.rs#L117-L118 https://github.com/solana-labs/solana/blob/74b586ae7/ledger/src/shred.rs#L272-L273 The commit updates ShredFlags so that if a shred is not DATA_COMPLETE_SHRED it cannot be LAST_SHRED_IN_SLOT either. |
||
---|---|---|
.. | ||
benches | ||
src | ||
tests | ||
.gitignore | ||
Cargo.toml | ||
build.rs |