fix: configurable watchdog timeout #93
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
alfetopito
approved these changes
Oct 5, 2023
mfw78
force-pushed
the
fix-watch-dog-timeout
branch
from
30c8d59 to
f994854
Compare
anxolin
reviewed
Oct 6, 2023
mfw78
force-pushed
the
fix-watch-dog-timeout
branch
from
f994854 to
88b4088
Compare
anxolin
approved these changes
Oct 6, 2023
mfw78
force-pushed
the
fix-watch-dog-timeout
branch
from
cc5126c to
ea88ecc
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Some chains aren't created equal, so having a constant watch dog timeout for the block watcher isn't suitable.
Changes
How to test
--watchdog-timeoutflag set to non-default value, such as 120, and observe block watcher running with a 120s timeout.Related Issues
Fixes #85