-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
PR decorations not working #243
Comments
Does this fail for every attempt at decoration? The @marvin-w Do you have any ideas on this? I'll add a null check around the variable wrapping in |
@mc1arke I would wrap it with a null check. Unfortunately it hides the real error right now. I personally use Bitbucket Cloud and this error only occurs on Bitbucket Server. The Exception will probably stay even after adding a null check, but at least he/we would then be able to identify the root cause. |
There are situations where Bitbucket server is returning an error during API calls, but has no messages specified in the response body, so is causing a `NullPointerException` to be thrown by the plugin whilst attempting to provide details on the error. Specifically checking for the messages not being present allows for the underlying HTTP status code to be returned in the exception details so the user can get a better understanding of what the issue is.
There are situations where Bitbucket server is returning an error during API calls, but has no messages specified in the response body, so is causing a `NullPointerException` to be thrown by the plugin whilst attempting to provide details on the error. Specifically checking for the messages not being present allows for the underlying HTTP status code to be returned in the exception details so the user can get a better understanding of what the issue is.
Closing since there have been no recent replicate details after the logging was updated. |
Hello,
PR decoration with bitbucket server doesnt work due to below error, I'm using sonarqube 7.9 and plugin version 1.3.2.
The text was updated successfully, but these errors were encountered: