Niklas

So, any idea why this would happen? I'd expect the container runtime to ensure that health check processes are properly terminated. The command we use has a timeout of 3s,...

> You see this zombie process in your environment too? Nope. My production systems run in k8s which invokes health checks from outside the container. I am also not seeing...

> You should increase the values or make this configurable in docker-compose. It already is configurable: https://docs.docker.com/compose/compose-file/compose-file-v3/#healthcheck > Not everyone has an Threadripper. ;) Neither do I :)

It's still unclear to me what the root cause is. Anyone willing to raise a PR with a proposed fix?

This might be a bit more nuanced: * If the finding is currently suppressed with a date and a client switches it back from suppressed to unsuppressed, the date should...

@SaberStrat FYI the build failures should be fixed by #469, I am currently waiting for a review on that. Once merged, you can rebase your branch and the build will...

> @taleodor "Latest" release is frequently not clearly defined, i.e. may a "pre-release" be considered latest? I would suggest to not try to infer "latest" somehow - this is bound...

> GitHub Releases has no concept of latest, I demonstrated this on one of the calls, can repeat today. Essentially, it may have releases from different streams all mashed together...

> In the practical sense of this PR, it means that if a user searches for TEI without version, this leads to a Product that lists all available versions and...

I agree that refactoring the model would make the most sense long-term. I'd also love the refactoring to consider #2130 (cc @msymons). Slightly related: In Hyades we implemented [expression conditions](https://dependencytrack.github.io/hyades/latest/usage/policy-compliance/expressions/),...