This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
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 does this do / why do we need it?
This proposes some additional verbose logging for
init
. It fills in some of the downtime before the solver starts logging.Example output (with fancy diff highlighting I just discovered):
What should your reviewer look out for in this PR?
Better log message/format ideas. Should we consider logging incrementally while scanning the directories as well?
Which issue(s) does this PR fix?
I didn't see an issue for
init -v
, but #1008 coveringstatus -v
is related