Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix CLI pruning params #4836

Merged
merged 2 commits into from
Jun 19, 2024
Merged

Fix CLI pruning params #4836

merged 2 commits into from
Jun 19, 2024

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Jun 19, 2024

ValueEnum is apparently not using the from_str...

Closes: #4828

`ValueEnum` is apparently not using the `from_str`...
@bkchr bkchr added the R0-silent Changes should not be mentioned in any release notes label Jun 19, 2024
@dmitry-markin dmitry-markin requested a review from a team June 19, 2024 14:20
@bkchr bkchr enabled auto-merge June 19, 2024 14:43
@bkchr bkchr added this pull request to the merge queue Jun 19, 2024
Merged via the queue into master with commit 9f09169 Jun 19, 2024
157 checks passed
@bkchr bkchr deleted the bkchr-pruning-params-take-2 branch June 19, 2024 15:37
TarekkMA pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Aug 2, 2024
`ValueEnum` is apparently not using the `from_str`...

Closes: paritytech#4828
sfffaaa pushed a commit to peaqnetwork/polkadot-sdk that referenced this pull request Dec 27, 2024
`ValueEnum` is apparently not using the `from_str`...

Closes: paritytech#4828
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

numerical pruning value fail to parse
4 participants