You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When integrating a new analyzer report format for this project, we encountered problems:
Severity for all warnings is considered Unspecified
This happens both when parsing the SARIF report (adding Severity is marked as TODO there) and when manually parsing and passing Severity to an object of the Report class.
The link to documentation (helpUri, help fields) is not pulled from the SARIF report.
CodeChecker version
6.24
To Reproduce
Steps to reproduce the behaviour:
Pass the report to the SARIF parser
Get intermediate report
Save the report via CodeChecker store ....
Expected behaviour
Analyzer warnings have Severity and when you view them, help text from SARIF is displayed in place of the checker documentation.
Desktop (please complete the following information)
OS: Ubuntu 22.04.3
Browser: Chrome
Version: 128.0.6613.138
Additional context
The integration of the new analyzer is done in the report-converter from SARIF format as universal for all static analyzers. Below I attach a couple of screenshots of the behavior that is described in this Issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
When integrating a new analyzer report format for this project, we encountered problems:
This happens both when parsing the SARIF report (adding Severity is marked as TODO there) and when manually parsing and passing Severity to an object of the Report class.
CodeChecker version
6.24
To Reproduce
Steps to reproduce the behaviour:
CodeChecker store ...
.Expected behaviour
Analyzer warnings have Severity and when you view them, help text from SARIF is displayed in place of the checker documentation.
Desktop (please complete the following information)
Additional context
The integration of the new analyzer is done in the report-converter from SARIF format as universal for all static analyzers. Below I attach a couple of screenshots of the behavior that is described in this Issue.
The text was updated successfully, but these errors were encountered: