-
Notifications
You must be signed in to change notification settings - Fork 608
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
Revert "Commit timeout (#2057)" #2759
Conversation
This reverts commit 701b391.
Interesting! What's the thought here? |
Hey @faddat, sorry this was a last minute change from a discussion this morning. The change in its previous form would force all validators to run with the 2 second timeout. We instead thought it would be best to simply set the default to 2, and allow validators to change this at their desire. |
yeah this should have been default config only. Overriding the config at start is undesirable imo |
This reverts commit 701b391.
Closes: #XXX
What is the purpose of the change
The PR from #2057 reduced time timeout to two seconds for all nodes, regardless of config settings. After discussion, we decided this is not desirable. I did leave the change to init.go so that any future nodes initialized will default to 2 (but can overwrite via their config file)
Testing and Verifying
This change is already covered by existing tests
Documentation and Release Note
Unreleased
section inCHANGELOG.md
? no