85% of `gitlabcom` Sentry errors are caused by `SemverDialects::InvalidConstraintError: invalid constraint`

Problem

While investigating errors for Category:Code Review Workflow in Sentry, I noticed that the vast majority of errors were all SemverDialects::InvalidConstraintError: invalid constraint. Zooming out to all errors reported under gitlabcom, it appears this accounts for 85% of errors emitted.

This seems very noisy and makes Sentry difficult to navigate when exploring data.

Should we stop sending this error to Sentry? Can the error be fixed?

Data

https://new-sentry.gitlab.net/organizations/gitlab/dashboard/10/?project=3&query=%5Bobject+Object%5D&statsPeriod=30d

As shown in the report, 93% of the errors reported are not associated with the software_composition_analysis feature category but rather with code_review_workflow. These errors come mainly from the ReactiveCachingWorker which is used when displaying the MR page, and the License Scanning MR widget is computing the reports comparison (between source and target branch reports).

By dropping the sentry alerting in the context of SBOM input parsing we'll get rid of 92% of the errors.

Proposal

• Remove sentry tracking for parsing errors coming form SBOM data
• Add an OPS flag for the other use cases to further reduce the noise and follow this workflow:
  • FF is ON
  • identify errors and log issues for them
  • FF is OFF
  • issues are completed
  • FF is ON
  • repeat...