add a very verbose -vv flag to lotus and lotus-miner. #6888
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
jennijuju
previously approved these changes
Jul 27, 2021
|
missing |
|
id suggest to have a separate cli, like |
|
@jennijuju I've thought this as a general CLI diagnostics flag. Right now we're printing API endpoints, but we can print other things, like file/directory paths, polling intervals, counts, etc. For the API endpoint tracing, I don't think putting it behind a command is the right call, because we want to trace what's being used in the command we are running right now. |
ZenGround0
approved these changes
Jul 27, 2021
raulk
force-pushed
the
feat/cli-super-verbose
branch
from
56f13a5
to
b04fb75
Compare
|
@ZenGround0 agree. Changed the terminology. |
raulk
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
This helps debug issues like the Miner Runtime Architecture segregation issues reported here: #6861, where there might be a mix up of environment variables, repos, etc. leading to the wrong API endpoints being used.