Error during loading issues in UI

SonarQube Cloud
1
  • ALM used: GitHub
  • CI system used: Jenkins
  • Languages of the repository: Java, JS, TS
  • Error observed
    Invalid rule key: ‘>’ or ‘=’ after attribute name (at ")
  • Steps to reproduce
    Load issues for our project. Filter by rules, entered whitespace after into the filter to find out the Checkstyle rule violations; Pressed Show more when 60 out of 95 items are shown.
2

Hi,

Could we have a screenshot of this? And do you see any errors in your browser’s console?

 
Thx,
Ann

3

image
image1598×748 66.4 KB

Errors in the browser console

utils-CQ4x7iaS.js:2 
 GET https://sonarcloud.io/api/issues/search?componentKeys=<hidden>…es=OPEN%2CCONFIRMED&ps=1&organization=<hidden>&additionalFields=_all 400 (Bad Request)

/ld-stream/eval/66e1…TkyMGUwNDM5YyJ9fQ:1 
 Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERRO
4

Hi,

Thanks for the screenshot & error. From that screenshot, I see you were trying to ‘load more’ issues when you’d basically already hit bottom. The rule keys shown in your screenshot already had 0 issues attached, so the only thing you might have gotten was more 0-issue rule keys. Nonetheless, it shouldn’t give you this error, so I’m going to flag this for the team.

 
Ann

6

I believe I didn’t hit the bottom, just 60 out of 95 items were shown.

7

Hi,

You’ve gone past the bottom of the issues. That rule list is sorted by issue count, so anything that was added to the list would just be more issue-less rules. But either you shouldn’t get an error, or you shouldn’t be offered the ‘more’ option. Either way, I’ve flagged this for the devs.

 
Ann

8

ok let’s wait for the team analysis.

13

Hi,

Just FYI, we’ve started digging into this and have identified the problem. Hopefully we’ll be able to deploy a fix soon.

 
Ann

19

Hello @ganncamp. Thanks to this post SonarCommunity Roundup, April 11 - 17 I found out the issue was created Jira .

What I’d like to add is that:

  1. We don’t use Ruby in our project so this is unlikely a cause of the UI issue I reported

  2. However we do use import of 3’d party rules like ESLint/Stylelint which may contribute values that are currently not processed well by UI.

Should this issue be fixed on UI instead of fixing the Ruby analyzer to cover wider set of cases?

20

Hi,

It looks like I picked up the wrong ticket. :sweat_smile:

There’s also an internal ticket to fix rule key filtering when keys contain commas.

 
Ann