Conversation
stiefn
force-pushed
the
no-logs-forge-inspect2
branch
from
1a17cbf to
15e3d2b
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Steps to reproduce:
Have RUST_LOG="debug" in your environment.
Try to initialise a DVF.
Result:
thread 'main' panicked at lib/state/forge_inspect.rs:203:55:
called
Result::unwrap()on anErrvalue: Error("expected value", line: 1, column: 1)Reason:
When RUST_LOG="debug" the forge inspect outputs its logs in the stdout, together with the JSON string requested. The result is that the storage layout JSON string contains output logs and cannot be parsed into an object.
Solution:
Run forge inspect with RUST_LOG="error". We expect forge inspect to only output the JSON result in the stdout or an error, not logs.