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

CV2-5789 dont send null values out to presto from check-api #2155

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

DGaffney
Copy link
Contributor

@DGaffney DGaffney commented Dec 13, 2024

Description

We have a minor, persistent Sentry error where we are sending null items from Check API to Alegre (and eventually Presto) to match them for similarity. This ticket skips those cases, as it ought to, to stop unnecessary work and stop the minor error stream.

References: CV2-5789

How has this been tested?

I added a PR and deployed for Presto to get more instrumentation with regards to the origin of null vectorization requests. They came through as vanilla requests for encoding against original_title and original_description fields as we do in these lines. This is likely the predominant candidate for where this happens. I tried to look for a more "unified" approach but couldn't quite come up with some generic preflight check that didn't end up just adding more complexity than was warranted.

Things to pay attention to during code review

Any other candidates? I'm of the opinion that we solve these ones and see if we see more cases rather than hunt them all down pre-emptively but I can be persuaded!

Checklist

  • I have performed a self-review of my own code
  • I have added unit and feature tests, if the PR implements a new feature or otherwise would benefit from additional testing
  • I have added regression tests, if the PR fixes a bug
  • I have added logging, exception reporting, and custom tracing with any additional information required for debugging
  • I considered secure coding practices when writing this code. Any security concerns are noted above.
  • I have commented my code in hard-to-understand areas, if any
  • I have made needed changes to the README
  • My changes generate no new warnings
  • If I added a third party module, I included a rationale for doing so and followed our current guidelines

Copy link

codeclimate bot commented Dec 14, 2024

Code Climate has analyzed commit d28c184 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 99.9% (0.0% change).

View more on Code Climate.

@DGaffney DGaffney merged commit eaa870f into develop Dec 16, 2024
16 checks passed
@DGaffney DGaffney deleted the cv2-5789-dont-send-nulls branch December 16, 2024 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants