New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"failed to request component-reports" should include the failure #205
Comments
I'd start by enabling debug logging. There is an issue with the stack traces sometimes with gradle that we are working on. However, enabling debug logging will get you the info you need as the actual exception is logged: |
Hmm, that shows throwing an With current versions of Java it's possible to attach multiple causes to an exception via |
Culprit: Code here could possibly put the first exception in the list as the cause and then the rest as suppressed exceptions, so we'd get all the stack traces. |
See the discussion here: jeremylong/DependencyCheck#2416 |
Ack, at the very least my issue is a duplicate of that one so I'll close this one I guess, and watch that one. |
I have a number of PRs blocked by this:
But it doesn't include the actual exception, so it's impossible to act on the error.
The actual cause for an exception should always be included when throwing your own exception.
Versions:
The text was updated successfully, but these errors were encountered: