-
Notifications
You must be signed in to change notification settings - Fork 311
New License: libpng-1.6.35 #2729
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
base: main
Are you sure you want to change the base?
Conversation
It seems ok to me. But
fails. This is what GH actions runs. But
success. @goneall ideas? |
I'm taking a look at this to try to figure out what's going on with the failing test. Often, when Looking at the failing test error message, I see:
Digging into the latest LicenseListPublisher code, I see that this appears to be getting triggered from https://github.com/spdx/LicenseListPublisher/blob/14e017edbb5eb5fa1f6eaf43a4725e45addb6dfd/src/org/spdx/licenselistpublisher/LicenseRDFAGenerator.java#L386, based on the "Unhandled exception generating html" line. There's a lot happening in the
I also see
I've been staring at this for a while and will continue to see if I can sort out anything for why this is failing. Just posting this here to track what I'm seeing so far. |
New theory -- I'm noting the following timeline:
I see that the new publisher version (3.1.1) is running in the GitHub Actions check. But not sure whether something has gotten out of sync due to the publisher change since then. I'm going to suggest re-opening a new PR with the same content of these XML and test text files, to see whether it passes then. I'll likely try that myself in a bit just to see if that resolves things. |
Note that there were some changes made to the crossref code in the license list publisher to improve performance. From what is posted above, my guess is those changes may be causing the issue. What is confusing me is I ran a full set of tests against the license list XML source before submitting the changes and the CI for the updated license list publisher should do the same. Not sure why it didn't fail earlier. |
I'm able to duplicate the problem on my local machine. If I get some more time today, I'll try to determine the cause. In any case, there is definitely an issue with the license list publisher - specifically the license matching code in the SPDX Java Library - since an NPE should never be thrown. |
I think I found the issue. The source of the issue is the license XML for the libpng-2.0 license. The XML has a nested "rule" - an I don't think this was introduced with the last license list publisher - this is likely showed up now since this license is close to the libpng-2.0 license and hit that piece of matching code. I didn't see any restrictions on the license XML on embedded If we do want to carry forward the restriction, we should update the XML schema to reflect the restriction. This will also catch this earlier with a better error message when submitting new licenses. There is also an issue in the license list publisher in that it should be able to handle this situation more gracefully. |
Thank you @goneall for taking the time to dig into this! I note that that optional / alt tag in libpng-2.0 is for a line of hyphens. Now that we've changed the matching guidelines in recent years to make standalone hyphen lines like this ignoreable, we could probably just take that optional / alt tags out entirely. I'll take a closer look again and then I'll submit a PR to remove those tags. Will also skim the rest of the license to see if any similar issues jump out. |
@swinslow - You'll probably need to combine the updated libpng-2.0 XML with this one since the license list publisher checks for duplicates against the published license list unless the license XML is included in the same PR. |
Signed-off-by: Steve Winslow <[email protected]>
fixes #2591
Signed-off-by: Jilayne Lovejoy