Will Murphy

This is still a bug even with `--enrich java`. Adding `needs-investigation` so that we can try to understand what's going on here.

Idea for how to investigate: It's possible that because these JARs have a `pom.xml` but not a `pom.properties`, and the Syft cataloger is expecting to find a `pom.properties`?

Posting some thoughts on how this refactor is going to go. This is refactor primarily about what's going on in https://github.com/anchore/grype/blob/main/grype/vulnerability_matcher.go, which has gotten sort of out of control. There...

We'll do this during/after Grype DB Schema v6 #2128

Hi @kevin-niland are you still facing this issue? We currently emit `(devel)` not `v0.0.0` for Go main modules that we can't identify, so we think this is fixed now -...

Hi @zakandrewking, I'm trying to understand exactly what's happening here. Here's what I think is happening: 1. You're starting with Debian 11 bullseye 2. You're adding the ability to install...

Looks like I'll need to also fix the wofli issue in this PR: ``` Running relative comparison... Results used: ├── 5cadc426-434a-4bb4-a832-3f71aaa5b16b : grype[custom-db]@v0.77.4 against cgr.dev/chainguard/wolfi-base@sha256:be3834598c3c4b76ace6a866edcbbe1fa18086f9ee238b57769e4d230cd7d507 └── 1b4d8c15-7c74-43e7-a770-b79f2045544e : [email protected] against...

Hopefully https://github.com/anchore/vunnel/pull/584 has fixed this. Will close if quality gate stays green for a few days.

It seems the two deterministic failures are fixed, so I'm closing this. The SUSE provider still sometimes fails, but that is tracked in #571.

Something isn't working with the Windows validations: ``` sh make test shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'" env: FORCE_COLOR: true bash: line 1: .tool/task: No such file or directory bash:...