🧹 Cleanup removed & legacy chunk config #488
Merged
Conversation
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
Signed-off-by: Niclas Schad <[email protected]>
…tion is blocks Signed-off-by: Niclas Schad <[email protected]>
Signed-off-by: Niclas Schad <[email protected]>
Signed-off-by: Niclas Schad <[email protected]>
nschad
force-pushed
the
cleanup-chunk
branch
from
4b7dd58
to
2075c28
Compare
kd7lxl
approved these changes
Dec 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
purger.enableflag for some components. I think they used to exists for chunk purger.config.storage.enginesinceblocksis the only option that is supported. Since there is nothing to configure, it's better to have no option to configure anything.Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]