ACP-77: Reduce block gossip log level #3519
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
StephenButtolph
added
monitoring
marun
approved these changes
Nov 5, 2024
yacovm
approved these changes
Nov 5, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Why this should be merged
After ACP-77, the expected creation flow of new L1s goes:
CreateSubnetTxCreateChainTxConvertSubnetToL1TxThis means that it is expected for an L1 to exist (for a brief time) with no validators. This means that the log about skipping block gossip is no longer unexpected.
How this works
Warn->Debug.How this was tested
N/A
Need to be documented in RELEASES.md?
No.