Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: don't create duplicate issues via worker #54049

Open
tatianab opened this issue Jul 25, 2022 · 1 comment
Open

x/vulndb: don't create duplicate issues via worker #54049

tatianab opened this issue Jul 25, 2022 · 1 comment
Assignees
Labels
NeedsFix The path to resolution is known, but the work has not been done. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo

Comments

@tatianab
Copy link

Modify the worker to check if a CVE ID already has a vulndb issue associated with it, and don't create a new one if so

@tatianab tatianab added the NeedsFix The path to resolution is known, but the work has not been done. label Jul 25, 2022
@tatianab tatianab self-assigned this Jul 25, 2022
@gopherbot gopherbot added this to the Unreleased milestone Jul 25, 2022
@julieqiu julieqiu added the vulncheck or vulndb Issues for the x/vuln or x/vulndb repo label Sep 8, 2022
@gopherbot
Copy link

Change https://go.dev/cl/461237 mentions this issue: internal/worker: prevent duplicates for GHSAs

gopherbot pushed a commit to golang/vulndb that referenced this issue Jan 10, 2023
This is a quick fix to prevent the worker from filing issues for
duplicate GHSAs. The check for duplicates should eventually be moved to
the triage stage.

For golang/go#54049

Change-Id: I902c64f032fc66c15b7fe62787ecb0520e446216
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/461237
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Damien Neil <dneil@google.com>
Reviewed-by: Tatiana Bradley <tatiana@golang.org>
Run-TryBot: Tatiana Bradley <tatiana@golang.org>
@julieqiu julieqiu modified the milestones: vuln/2022, vuln/unplanned Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsFix The path to resolution is known, but the work has not been done. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Projects
Status: No status
Development

No branches or pull requests

3 participants