-
Notifications
You must be signed in to change notification settings - Fork 315
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
Ensure ORT to handle the output format 3 of the ScanCode 32 series #6617
Comments
My experienced behavior (not ran on my machine, but I did remote debugging):
|
The issue is caused by this line
The reason is that the Scancode output format has changed from
To:
|
While parsing newer output format versions might not throw exceptions, results may be incomplete (see #6617 for the context). Avoid confusion by warning in that case. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While parsing newer output format versions might not throw exceptions, results may be incomplete (see [1] for the context). Avoid confusion by warning in that case. [1]: #6617 Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While parsing newer output format versions might not throw exceptions, results may be incomplete (see [1] for the context). Avoid confusion by warning in that case. [1]: #6617 Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While parsing newer output format versions might not throw exceptions, results may be incomplete (see [1] for the context). Avoid confusion by warning in that case. [1]: #6617 Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While parsing newer output format versions might not throw exceptions, results may be incomplete (see [1] for the context). Avoid confusion by warning in that case. [1]: #6617 Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
Work for this has been started in the scancode-format-3 branch. |
The implementation is ready, but its merge is currently blocked by the discussion in #7300. |
While in previous outputs formats the primary elements for license entries were single license keys (which needed to be grouped to expressions), starting with output format version 3 the primary license entries are expressions. Resolves #6617. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While in previous outputs formats the primary elements for license entries were single license keys (which needed to be grouped to expressions), starting with output format version 3 the primary license entries are expressions. Resolves #6617. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While in previous outputs formats the primary elements for license entries were single license keys (which needed to be grouped to expressions), starting with output format version 3 the primary license entries are expressions. Resolves #6617. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While in previous outputs formats the primary elements for license entries were single license keys (which needed to be grouped to expressions), starting with output format version 3 the primary license entries are expressions. Resolves #6617. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While in previous output formats the primary elements for license entries were single license keys (which needed to be grouped to expressions), starting with output format version 3 the primary license entries are expressions. Resolves #6617. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
Ping @maxhbr who I believe was experiencing something similar with the latest ScanCode pre-release. I'll create a new issue.
Originally posted by @sschuberth in #6585 (comment)
The text was updated successfully, but these errors were encountered: