Skip to content

Check for nil user before attempting MR creation in DB seed

What does this MR do and why?

Sporadically, project.members.sample will be nil, causing seeding to crash into a state that requires a complete DB reset to recover from. This change prevents exception-raising conditions to occur, so that seeding can continue (albeit with one less ComplianceViolation record..)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

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.

Merge request reports