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.

Sign up for GitHub

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

Jump to bottom

bug: /api/v2/purl/{purl} doesn't always return the correct purl #1158

Open
jcrossley3 opened this issue Jan 17, 2025 · 1 comment · May be fixed by #1159
Open

bug: /api/v2/purl/{purl} doesn't always return the correct purl #1158

jcrossley3 opened this issue Jan 17, 2025 · 1 comment · May be fixed by #1159
Assignees
@jcrossley3
Labels
bug Something isn't working

Comments

@jcrossley3
Copy link
Contributor

It seems to ignore the qualifiers, e.g. if I request a purl qualified by arch=src, I may get one qualified by arch=x86_64 because it's just returning the first one (of possibly many) it finds.
@jcrossley3 jcrossley3 self-assigned this Jan 17, 2025
@jcrossley3
Copy link
Contributor Author

Weirdly, we actually have a test that affirms the bug. Note that it requests arch=s390x and expects arch=ppc64le. wtf? 😄

jcrossley3 added a commit to jcrossley3/trustify that referenced this issue Jan 17, 2025
@jcrossley3
fix: /api/v2/purl/{purl} now honors qualifiers, or lack thereof
242f091 
Fixes trustification#1158

Signed-off-by: Jim Crossley <[email protected]>
@jcrossley3 jcrossley3 linked a pull request Jan 17, 2025 that will close this issue
Open
@jcrossley3 jcrossley3 added the bug Something isn't working label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcrossley3 jcrossley3

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: /api/v2/purl/{purl} now honors qualifiers, or lack thereof jcrossley3/trustify
1 participant
@jcrossley3