fix: reuse ecosyste.ms cache across SBOM enrichments #125
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, each SBOM enrichment created a new cache instance, causing repeated API calls for the same packages (including 404s for non-existent packages). This change introduces a global cache singleton that persists for the lifetime of the process, reducing unnecessary API calls to ecosyste.ms.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: I used claude code to generate this as I'm not experienced with Go, feel free to edit or completely rewrite if you wish. I noticed that there's a lot of repeated 404 requests from parlay within the same time period in the ecosyste.ms logs, I sent claude to investigate and this is what it came up with.
Previously, each SBOM enrichment created a new cache instance, causing repeated API calls for the same packages (including 404s for non-existent packages). This change introduces a global cache singleton that persists for the lifetime of the process, reducing unnecessary API calls to ecosyste.ms.