Truncate description to max length and store the results

What does this MR do and why?

  1. This is an iteration to !210107 (merged) where we increased the column length to 100,000 characters.
  2. To avoid errors while storing the analysis sent by the workflow to the database we would truncate and store the first 100,000 characters from the response.
  3. This is done to prevent cases where we completely reject and don't store the result in the database in case it is longer that the max length.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading