-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unexpected Exception when getting issues from server #59
Comments
If I do a call to the URL, this is the response from SonarQube:
|
Yes, the Sonar API has a limit in the number of issues that can be retrieved. So maybe it would be useful to handle this case and to show a more meaningful message to the user. |
Is there a way to get around this limitation? I would like to be able to export all the issues for a language to further categorise them. There are plenty of projects that have more than 10000 issues. |
Hi @astaicu For remote issues, the plugin invokes the REST API provided by the SonarQube Server. I don't know of any workaround for the remote case. In the local analysis with sonar runner these limitation should not exist. |
Hey guys. Facing the same issue here. Not able to get issues beyond 10000. Even the API https://docs.sonarqube.org/pages/viewpage.action?pageId=2392181 says that cannot fetch more than 10000 issues. Is there any other tool that exposes all the issues in the API which I can make use of in my application? |
I have a project that has a lot of sonar bugs, and this results in 20 pages of bugs. When this plugin attempts to load the 21 page, its gets a 400 Bad Request from the Sonar server, and that results in an Unexpected Exception:
This is with SonarQube 6.5, and the 3.0.1 plugin for netbeans.
The text was updated successfully, but these errors were encountered: