-
Notifications
You must be signed in to change notification settings - Fork 276
feat: Add related computation to cron
#4704
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
base: master
Are you sure you want to change the base?
The head ref may contain hidden characters: "\u{1F46A}"
Conversation
go/cmd/relations/related.go
Outdated
| // We want to prevent withdrawn vulns from being added to related groups. | ||
| // But if a non-withdrawn vuln has a withdrawn vuln as a related id, we want to add it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be worded a bit differently
We want to prevent withdrawn vulns IDs from being added to related groups, if the withdrawn vuln itself references other non-withdrawn vulns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe give some examples here as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Make
relatedvulns be regularly recomputed, so whenAupdates to related toB,Bwill get updated to relate toA.A withdrawn vuln will have non-withdrawn vulns added to its related field, but it will not add it's ID to the related fields of its own related vulns.
(i.e. if
Ais withdrawn and hasrelated: ["C"],Cwill not getAadded to its related field. If non-withdrawnBhasrelated: ["A"],Awill end up withrelated: ["B", "C"])