forked from paritytech/polkadot-sdk
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow to disable gap creation during block import (paritytech#5343)
This feature is helpful for us with custom sync protocol that is similar to Warp sync except we do not ever sync the gap and don't want it to exist in the first place (see paritytech#5333 and its references for motivation). Otherwise we had to resort to this: d537512 --------- Co-authored-by: Davide Galassi <[email protected]> (cherry picked from commit 030cb4a)
- Loading branch information
Showing
6 changed files
with
39 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
title: Allow to disable gap creation during block import | ||
|
||
doc: | ||
- audience: Node Dev | ||
description: | | ||
New property `BlockImportParams::create_gap` allows to change whether to create block gap in case block | ||
has no parent (defaults to `true` keeping existing behavior), which is helpful for sync protocols that do not need | ||
to sync the gap after this happens. `BlockImportOperation::create_gap()` method was also introduced, though in | ||
most cases `BlockImportParams::create_gap` will be used. | ||
|
||
crates: | ||
- name: sc-client-api | ||
bump: major | ||
- name: sc-consensus | ||
bump: minor | ||
- name: sc-client-db | ||
bump: minor | ||
- name: sc-service | ||
bump: minor |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters