You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When scanning a file of PURLs or a single PURL and setting output format to json, Grype panics.
What you expected to happen:
Grype does not panic and creates the outputs.
How to reproduce it (as minimally and precisely as possible):
podman run --rm --name Grype -v grypedb:/.cache/grype docker.io/anchore/grype:v0.86.1 'pkg:deb/debian/[email protected]?arch=amd64&distro=debian-12' -o json=/dev/stdout
[0000] WARN unable to determine GOPATH or user home dir: %!w(string=exec: "getent": executable file not found in $PATH)
[0000] ERROR 1 error occurred:
* unable to write result: unable to encode result: unsupported source: pkg.PURLLiteralMetadata
Anything else we need to know?:
This is a regression in 0.86.1, because version 0.86.0 is not affected. Most probably a result of fixing #2324. I wish there was a testing infrastructure that runs some basic checks like this one in Docker to catch these regressions.
Environment:
Output of grype version: 0.86.1
OS (e.g: cat /etc/os-release or similar):
The text was updated successfully, but these errors were encountered:
What happened:
When scanning a file of PURLs or a single PURL and setting output format to
json
, Grype panics.What you expected to happen:
Grype does not panic and creates the outputs.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
This is a regression in
0.86.1
, because version0.86.0
is not affected. Most probably a result of fixing #2324. I wish there was a testing infrastructure that runs some basic checks like this one in Docker to catch these regressions.Environment:
grype version
: 0.86.1cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: