fix: hide multivm log warnings and traces #310
Merged
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.
What π»
multivm
from log filterWhy β
=info
log level applied as expected on start-up, so TRACE logs were showing formultivm
target0x function_selector
which is confusing and could have end users believe that something is wrong when there's not0.1.0-alpha.25
todayEvidence π·
Running
era_test_node
now only haveera_test_node=info
logs: