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

Keys of Anchore entities need to be encoded #1023

Closed
fniessink opened this issue Feb 18, 2020 · 0 comments · Fixed by #1029
Closed

Keys of Anchore entities need to be encoded #1023

fniessink opened this issue Feb 18, 2020 · 0 comments · Fixed by #1029
Labels
Bug Something isn't working

Comments

@fniessink
Copy link
Member

For example, http://www.quality-time.example.org/api/v2/measurement/{id}/source/{id}/entity/CVE-2016-8660:linux-libc-dev-4.19.98-1/status leads to an internal server error:

image
@fniessink fniessink added the Bug Something isn't working label Feb 18, 2020
fniessink added a commit that referenced this issue Feb 18, 2020
@fniessink
Anchore vulnerability keys are not always valid as JSON key, causing …
23e83fb 
…exceptions when the user tries to make changes to vulnerabilities. Hashing the keys prevents this issue. Fixes #1023.
@fniessink fniessink mentioned this issue Feb 18, 2020
Merged
fniessink added a commit that referenced this issue Feb 18, 2020
@fniessink
Anchore vulnerability keys are not always valid as JSON key, causing …
d9ab65f 
…exceptions when the user tries to make changes to vulnerabilities. Hashing the keys prevents this issue. Fixes #1023. (#1029)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Anchore vulnerability keys are not always valid as JSON key, causing … ICTU/quality-time
1 participant
@fniessink