Print some useful diagnostic info in omf doctor
#456
Merged
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
sagebind
force-pushed
the
doctor-info
branch
from
fef336a to
5123aaa
Compare
|
👍 |
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.
Since there are some common things we need to know when troubleshooting OMF, this adds some relevant diagnostic information so far as output to the
omf doctorcommand. We can then recommend users simply paste the output ofomf doctoras long as it is accessible, or literalomf.doctorotherwise.This does not aid troubleshooting the installation process itself. It might be useful to separate the doctor into its own script that can be downloaded and used separately.