Cannot release db lock on migration

[kovachevx]

Hi there,

We've recently upgraded to v6 but we are unable to deploy our app as we're always getting the "Migration completed, but unable to release database lock" exception. Occasionally, we'd hit it locally as well. We used to run into the same issue in v5, but it would only happen from time to time. We were hoping that this would be resolved with v6, but on the contrary, we're always hitting this error.

We're using the latest versions of Lucid and pg, we've tried using the --disable-locks flag, and we've also squashed our files to reduce to the total number of migrations, all to no avail.

We've came across this post in Discord, but the issue seems to remain unresolved.

We also found this issue, suggesting that truncating may be causing this. However, we aren't truncating anything anywhere. We use the defer method on several occasions (not sure if this could be related, but we do have a couple of materliazed views).

Any suggestions as to how to fix or identify the issue would be greatly appreciated!

[thetutlage]

It's really hard to know or tell anything without looking at any code. Maybe, you can create a small reproduction and share that with us.

[kovachevx]

Thank you for the quick response! I created a minimal reproducible version of our app, but from a business perspective I’ve given access only to you. You should have received an invite for the adonis-migration-db-lock-reproducible repository. Let me know if there's absolutely anything else I could provide that might be helpful.

[kovachevx]

@thetutlage Please let us know if we should give access to somebody else as well.

[thetutlage]

Hello @kovachevx

Setting up full blown apps is not possible for me, as it requires spending too much time. Please help us reproduce this issue in isolation with a new app

[kovachevx]

We've got smaller Adonis projects but haven't faced this issue there. We are uncertain what exactly causes it as it appears only on our large-scale projects. We've removed everything unnecessary from the codebase we shared with you, but I am afraid we are unable to isolate it further. We've provided steps to set up and reproduce the issue within the repository in an endeavour make the process easier.