-
Notifications
You must be signed in to change notification settings - Fork 645
Fixes #310 - install Missing Analysis Tool. Better feedback would be nice #375
Conversation
…a summary of the run (e.g. All success, X failures), and if there are failures, print the errors from those failures.
Hi @benclarkwood, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
@benclarkwood, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR. |
|
||
outputChannel.appendLine(''); // Blank line for spacing. | ||
|
||
Promise.all(missing.map(tool => new Promise<string>((resolve, reject) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing I was meaning to look into/change was running these serially instead of in parallel. I'm pretty sure go get
has issues when multiple gets are run in parallel, and users have reported that the existing extension occasionally runs into errors. Since you are making changes here - may make sense to also just change this to do the gets serially?
This looks great - big improvement! Left a few comments on the code changes. |
I've merged this along with a few additional improvements that address the issues I mentioned in review and fixed a few additional related issues. Thanks again! |
This commit causes goInstallTools to log very differently than present.
Presently, goInstallTools just writes the output of stdout and stderr to the Go outputChannel.
This commit proposes logging much less in the case of success, and only logging the cause of errors.
Let me know what you think @lukehoban.
(A total success)
(A failure)
NOTE: Didn't include every failure's output as they're all the same (no internet connection).