Invalid `prisma.user.create()` invocation with v5.15.4

[tryallthethings]

Invalid `prisma.user.create()` invocation with v5.15.4

[bjarneo]

Do this happen only for the newest version?

[tryallthethings]

I was running the exact same configuration with the previous release and didn't see this issue there.

[bjarneo]

I am quite not sure why this is happening to you. Tried to upgrade my own instance to the latest release without any issue, 🤔

[tryallthethings]

But did you have the same env variables for creating the root user as well?

[bjarneo]

Yes, I never change those. But that user will only be created on the first run. Not each time you restart / start the container. As long as the database is mounted correctly

[tryallthethings]

I can pretty much force the error by adding the env values back and restart the container. Can we get additional logs to debug this?

[bjarneo]

Sure. Can you open a PR and add the logs you need?

[tryallthethings]

I have no clue how to debug this. I was asking if we can enable some additional logging, so one of the devs can look into it.

[bjarneo]

There are no more logs to enable. It has to be manually added to the code. What devs? This is an open source tool mainly maintained by me. Occasionally people are contributing to the project.

[bjarneo]

Did you try to move the database and let the instance create a fresh one? To verify if that solves the issue. This seems to be not related to the application itself, but the data saved to the database.

[bjarneo]

I managed to reproduce this when testing locally:

1. I was signed in with the default user and password
2. I fetched the production database (which does not contain that user)
3. Tried to create a secret.

What happens on 3. is that when you try to create a secret, and you are signed in with a user that does not exist in the database, then it tries to attach your user to the secret -> to the database. The matching will fail.

[tryallthethings]

I just tested it with the latest version and the issue is gone now. You might be correct with your assumption, as I had trouble with the database and kept recreating it while still being signed in with the old version. Good catch and thanks!