Closed adambhere closed 2 years ago
Looks like this is related to @fviernau's removal of project excludes in https://github.com/heremaps/oss-review-toolkit/pull/1639.
This should be the relevant line by now:
But I'm wondering whether throwing an exception isn't the right thing to do on a corrupted / invalid repository configuration file. Or should be just create an OrtIssue
/ analyzer error instead, @oss-review-toolkit/core-devs?
Ping again @oss-review-toolkit/core-devs, and esp. @fviernau and @adambhere! Is this relevant?
In my opinion ORT behavior is good as-is. I've fixed a bunch of issues for such exceptions, and IIRC I was always able to identify the root cause quickly based on the exception message.
Besides that, behavior IIRC is consistent with how serialization issues of package configurations and curations or other configurations files are handled.
Agreed, so let's close this.
ORT's analyzer crashes on .ort.yml with invalid fields or an incorrectly specified --repository-configuration-file.
The expected behaviour would an analyzer error in the report and ORT should carry on.
Only a fatal error that makes it impossible for the analyzer (or ORT as a whole) to produce meaningful results should terminate execution.