ort: Analyzer reports issues and returns exit code 2 but no issues are visible

I am running the analyzer against the the master branch of Flasky (https://github.com/miguelgrinberg/flasky) and the analyzer reports that there are issues in the output file. Indeed, the analyzer-result.yml contains the has_issues: true but there are no additional details. The debug log does not provide any information either, or at least I don’t see it.

analyzer-result.zip

log.log

Can we make the analyzer to produce more information about the actual issues either in the logs or the results file?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 19 (16 by maintainers)

Commits related to this issue

Most upvoted comments

So, does that mean we agree on removing collectIssues() from CuratedPackage?

From my side yes. @mnonnenmacher , agree as well?

fviernau, could you simply contribute your existing implementation to examples/rules.kts?

yes.

edit: Seems I already contributed that in 5543aed5c67750cbeadf69c51457e8d17513af24