Upgrade log level to Error when losing connection to L1 for too long #1783
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
cla-bot
bot
added
the
s
joshuacolvin0
approved these changes
Sep 28, 2023
util/headerreader/header_reader.go
Outdated
| "l1Timestamp", l1Timetamp, "age", headerTime, | ||
| ) | ||
| // Upgrade the log level from warn to error when losing connection to L1 for too long | ||
| if headerTime >= DefaultConfig.OldHeaderTimeout { |
There was a problem hiding this comment.
DefaultConfig.OldHeaderTimeout defaults to 5 minutes and s.config().OldHeaderTimeout is almost always the default, so no need to do if/else. Only change needed is go from Warn to Error
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.
No description provided.