Log stacktrace for repositoryAccessFailed at debug level, not warn #811
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
timtebeek
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.
What's changed?
Hide stack trace by default, but log it at debug level such that it is accessible when troubleshooting through
-X.What's your motivation?
Folks were alarmed by the full stack trace, incorrectly concluding that recipes aren't running. As per
SSLHandshakeExceptionstacktrace frommaven.java.netnot actionable, possibly should not have been attempted rewrite#4101Have you considered any alternatives or workarounds?
Will still see if we can not contact failing repositories unnecessarily to really fix openrewrite/rewrite#4101