Do not throw when MR summary is empty
What does this MR do and why?
Do not throw when MR summary is empty
This prevents creating a DiffLlmSummary
when the content would be
empty.
We get a few hundred failing jobs per week due to this. Example: https://log.gprd.gitlab.net/app/discover#/doc/AWNABDRwNDuQHTm2tH6l/pubsub-sidekiq-inf-gprd-003664?id=QHBe9ooBSBzdJ8RWDmaN
I am not sure though why we have an empty response as we unfortunately can't track the response from Vertex :/ An example MR where it happened: !133008 (merged)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.