Aladin

For me, it's also happening, but differently and I'm trying everything to work around it. I have a seeder function that populates the db with fake data, here's how we're...

So "creating multiple seeders" just means that I added more "seedXXX" functions. Here's a reproduction repo: https://github.com/aladinflux/prisma-conflit-issue The seeder code is inside `prisma` folder. Just run `npx prisma db seed`...

Also, @janpio , if I remove the `deleteMany` part, then it works unreliably. After multiple times re-running the seeder, it worked. So for every ~20 times running the command, one...

@dpetrick , for the `Int` and `String`, I think it was a typo or something, I didn't pay attention. But the issue with the repo is that it doesn't go...

These WriteConflict errors started happening a lot within our code. It's very difficult to debug or to reproduce in a repo. Currently, they're happening during event handlers. We use a...

I start to suspect it's `Promise.all`. The modified `mitt` package does a `Promise.all(handlers)` which is not running handlers serially and maybe 2 queries fire at the same time.

Alright [dpetrick](https://github.com/dpetrick), so after switching from `Promise.all` to a `for` loop, I didn't get the `WriteConflict` issue. But this is a bug in my opinion. Primsa should be able to...

> For me, it's also happening, but differently and I'm trying everything to work around it. > > I have a seeder function that populates the db with fake data,...

This WriteConflict issue is really hitting us hard. We went to production with Prisma and we keep getting these issues and it's extremely difficult to debug or find out about...

@andrewicarlson , I would love to. The issue is seriously hurting us, all these errors are from the same issue: WriteConflict, happening everywhere in our code: The problem is that...