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

Analyzer fails with: Option path is required but not set. #9342

Closed
dimitris-iliou opened this issue Oct 25, 2024 · 4 comments
Closed

Analyzer fails with: Option path is required but not set. #9342

dimitris-iliou opened this issue Oct 25, 2024 · 4 comments
Labels
configuration About configuration topics question An issue that is actually a question

Comments

@dimitris-iliou
Copy link

Describe the bug

Looking for ORT configuration in the following file:
        /builds/oss/oss-review-toolkit/ort-gitlab-ci/config.yml
Looking for analyzer-specific configuration in the following files and directories:
        /builds/oss/oss-review-toolkit/ort-gitlab-ci/project/.ort.yml (does not exist)
        /builds/oss/oss-review-toolkit/ort-gitlab-ci/ort-configuration/resolutions.yml
The following 25 package manager(s) are enabled:
        Bazel, Bower, Bundler, Cargo, Carthage, CocoaPods, Composer, Conan, GoMod, Gradle, Maven, NPM, NuGet, PIP, Pipenv, PNPM, Poetry, Pub, SBT, SpdxDocumentFile, Stack, SwiftPM, Unmanaged, Yarn, Yarn2
Exception in thread "main" java.lang.IllegalStateException: Option path is required but not set.
	at org.ossreviewtoolkit.plugins.packagecurationproviders.file.FilePackageCurationProviderFactory.create(FilePackageCurationProviderFactory.kt:14)
	at org.ossreviewtoolkit.plugins.packagecurationproviders.file.FilePackageCurationProviderFactory.create(FilePackageCurationProviderFactory.kt:9)
	at org.ossreviewtoolkit.plugins.packagecurationproviders.api.PackageCurationProviderFactory$Companion.create(PackageCurationProviderFactory.kt:51)
	at org.ossreviewtoolkit.plugins.commands.analyzer.AnalyzerCommand.run(AnalyzerCommand.kt:167)
	at com.github.ajalt.clikt.core.CoreCliktCommandKt.parse(CoreCliktCommand.kt:107)
	at com.github.ajalt.clikt.core.CoreCliktCommandKt.main(CoreCliktCommand.kt:78)
	at com.github.ajalt.clikt.core.CoreCliktCommandKt.main(CoreCliktCommand.kt:90)
	at org.ossreviewtoolkit.cli.OrtMainKt.main(OrtMain.kt:87)
  • ORT version: [e.g. 37.0.0]
  • Java version: [e.g. 21]
  • OS: [e.g. Linux]

The error appeared after building latest ORT version, I am not sure how to proceed with this

@dimitris-iliou dimitris-iliou added bug Issues that are considered to be bugs to triage Issues that need triaging labels Oct 25, 2024
@sschuberth
Copy link
Member

Does this occur when using https://github.com/oss-review-toolkit/ort-ci-gitlab? If so, please file the issue over there.

@sschuberth
Copy link
Member

The error appeared after building latest ORT version, I am not sure how to proceed with this

Anyway, as the error message says, "Option path is required but not set". So no path is set for your FilePackageCurationProvider. Which probably is because you're using an outdated key name for the parent node: Use "options" instead of "config".

@sschuberth sschuberth added question An issue that is actually a question configuration About configuration topics and removed bug Issues that are considered to be bugs to triage Issues that need triaging labels Oct 25, 2024
@dimitris-iliou
Copy link
Author

Great, I resolved the issue! I’m using this filter to track breaking changes, but this one wasn’t included. Are there any additional filters I should consider adding?

@sschuberth
Copy link
Member

Great, I resolved the issue!

Good, then let's close the issue.

Are there any additional filters I should consider adding?

No. We somewhat deprecated the use of PR labels for breaking changes in favor of listing them in the release notes on a per-commit basis. I'd recommend to watch the release notes instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration About configuration topics question An issue that is actually a question
Projects
None yet
Development

No branches or pull requests

2 participants