Niklas

This has been implemented in #1841. Thanks again, @syalioune! 🚀

Hi @software-testing-professional, thanks for reporting! 👋 Unfortunately I can't reproduce this. Tested with individual and merged SBOMs, but I don't see the behavior you're describing. For reference, I tested with...

Long-term, we should remove the scheduled portfolio metrics calculation. Portfolio metrics will need to be calculated based on which projects a user or team has access to (see #1682), which...

Updated the PR to leverage the event system instead of spawning a temporary `ExecutorService` upon every execution. I used batching in combination with a `CountDownLatch` to apply some sort of...

Upserts are still performed using the JDO API, so the "shared" L2 cache of the `PersistenceManagerFactory` will still be populated upon commit. The L1 cache is bound to `PersistenceManager` instances,...

Thanks @shipko! The PR in itself is pretty much ready and is only awaiting a review. As this refactoring touches a core functionality of DT, it should be reviewed by...

Awesome, thanks for the review. Going to merge this then. 🤞

Hi @elastic-pangolin, are you still interested in getting this merged?

The initial implementation (#2070) will attempt to work around the missing batching functionality by distributing the analysis requests to a configurable amount of threads (fixed-size thread pool shared across analyzer...

Does the notification even make sense anymore? * `NEW_VULNERABILITY` already fires when `NEW_VULNERABLE_DEPENDENCY` would be fired * `NEW_VULNERABLE_DEPENDENCY` includes a list of projects where the dependency was introduced, which, based...