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
Currently crisis invariant checks look like:
7:47AM INF asserting crisis invariants inv=0/11 module=x/crisis 7:47AM INF asserting crisis invariants inv=1/11 module=x/crisis 7:47AM INF asserting crisis invariants inv=2/11 module=x/crisis 7:47AM INF asserting crisis invariants inv=3/11 module=x/crisis 7:47AM INF asserting crisis invariants inv=4/11 module=x/crisis
It would be nice if there could also be a human friendly name printed out for what the invariant being checked is.
Improves understandability of logs, and helps node operators learn what the invariants being checked are.
Use the existing name field associated with every invariant, and print them in the crisis invariant log line as:
7:47AM INF asserting crisis invariants inv=2/11 name=$INVARIANT_NAME module=x/crisis
The text was updated successfully, but these errors were encountered:
tac0turtle
Successfully merging a pull request may close this issue.
Summary
Currently crisis invariant checks look like:
It would be nice if there could also be a human friendly name printed out for what the invariant being checked is.
Problem Definition
Improves understandability of logs, and helps node operators learn what the invariants being checked are.
Proposal
Use the existing name field associated with every invariant, and print them in the crisis invariant log line as:
7:47AM INF asserting crisis invariants inv=2/11 name=$INVARIANT_NAME module=x/crisis
For Admin Use
The text was updated successfully, but these errors were encountered: