This was a case of me keeping a Prisma transaction open for the lifetime of several S3 requests. I've pulled out the S3 logic to run in a separate task that won't block the DB work.
Haven't written tests for this since I can't think of a reliable way to E2E test this and we'll test it out on staging tonight.
Closes #998
Checks
[x] !! DONT IGNORE ME !! I have ran nx run db:create-migration <name> and committed the migration if I've made DB schema changes
[x] I have included/updated tests where applicable (see Testing)
This was a case of me keeping a Prisma transaction open for the lifetime of several S3 requests. I've pulled out the S3 logic to run in a separate task that won't block the DB work.
Haven't written tests for this since I can't think of a reliable way to E2E test this and we'll test it out on staging tonight.
Closes #998
Checks
nx run db:create-migration <name>and committed the migration if I've made DB schema changesfeat: Add foo,chore: Update bar, etc...fixuped into my original commits