Skip to content
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

Problems with integration new analyzer by SARIF report #4348

Open
feeelin opened this issue Sep 16, 2024 · 0 comments
Open

Problems with integration new analyzer by SARIF report #4348

feeelin opened this issue Sep 16, 2024 · 0 comments

Comments

@feeelin
Copy link
Contributor

feeelin commented Sep 16, 2024

Describe the bug
When integrating a new analyzer report format for this project, we encountered problems:

  1. 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.
  2. 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:

  1. Pass the report to the SARIF parser
  2. Get intermediate report
  3. 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.

image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant