refactor: improve logs and add exception stack trace for YarnAuditAnalyzer#7694
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description of Change
The purpose of this PR is to change 2 identical log messages to help understand what actually happened when an issue is encountered by a user. DependencyCheck will now display the exit value when receiving a non-zero exit value from Yarn. In case an
InitializationExceptionis encountered when initializing theYarnAuditAnalyzer,NodeAuditAnalyzer,NodePackageAnalyzeror thePnpmAuditAnalyzer, this exception stack trace will be printed at debug level.Related issues
Have test cases been added to cover the new functionality?
no