We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Logs like aztec:sequencer [INFO] Can propose block 3 at slot 5 are too verbose currently.
aztec:sequencer [INFO] Can propose block 3 at slot 5
Need to drop visibility of this one, since we are emitting it all the time.
There is a separate piece of work, which this issue will not fix: we ought not be checking multiple times per second that we can in fact propose.
The text was updated successfully, but these errors were encountered:
chore: drop info to verbose in sequencer hot loop (#9983)
beed293
fixes: #9978
Successfully merging a pull request may close this issue.
Logs like
aztec:sequencer [INFO] Can propose block 3 at slot 5are too verbose currently.Need to drop visibility of this one, since we are emitting it all the time.
There is a separate piece of work, which this issue will not fix: we ought not be checking multiple times per second that we can in fact propose.
The text was updated successfully, but these errors were encountered: