-
Notifications
You must be signed in to change notification settings - Fork 305
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
Deprecated options in cometbft config template #3144
Comments
Good call. I've generated a new default cometbft config via |
Looked into this some more. Turns out we can't perform the rename because |
As of CometBFT v0.37.x, fastsync has been deprecated in favor of blocksync, but v0.38.x will disregard both options. We can't yet update the value since we're on v0.37.x still, but I'm still pulling in the config file changes to comments and explanations created by diffing a newly generated CometBFT config against our TOML template. Refs #3144. Refs #2263.
As of CometBFT v0.37.x, fastsync has been deprecated in favor of blocksync, but v0.38.x will disregard both options. We can't yet update the value since we're on v0.37.x still, but I'm still pulling in the config file changes to comments and explanations created by diffing a newly generated CometBFT config against our TOML template. Refs #3144. Refs #2263.
As of CometBFT v0.37.x, fastsync has been deprecated in favor of blocksync, but v0.38.x will disregard both options. We can't yet update the value since we're on v0.37.x still, but I'm still pulling in the config file changes to comments and explanations created by diffing a newly generated CometBFT config against our TOML template. Refs #3144. Refs #2263.
Describe the bug
Recent smoke test runs showed
This key is generated as part of
pd
's config generation mechanism.The text was updated successfully, but these errors were encountered: