Error when trying to run migrations on Linux

[solucaodev]

When trying to "run migration:run" using NodeJS on Linux, the framework is unable to check which migrations have already been applied before, so it tries to apply everything again.

When running "migration:status", I get a table with all migrations with "corrupt" status.

I didn't find any documentation about the problem.

Grateful for the attention!

[guntribam]

please share more details: env variables, db used, logs, etc

[solucaodev]

Hi! I rule out that there is a configuration problem, since, when running the migrations on Windows, everything works.

On Linux, the only thing that doesn't work is migrations. The connection to the database is normal and working.

See a screenshot comparing running migration:status on Windows and Ubuntu:

Steps:
1 - Create any migration
2 - Using a Windows Machine, run migrations
3 - Using a Linux Machine, run migrations <---- BUG

[guntribam]

the directory structure on linux is using backslash? \

[guntribam]

sorry that i can't help more than this, but i would do this:
1 - create a slim project npm init adonis-ts-app@latest connection-test on linux(without any \ / mumbo jumbo, create exclusive for linux)
2 - install and configure lucid for mssql npm i @adonisjs/lucid && node ace configure @adonisjs/lucid
3 - create a simple migration that create a table TEST node ace make:migration test
4 - run the migration and check

[guntribam]

if you think the problem is in the configuration, try to check in knex github issues.

[solucaodev]

The whole problem is running the migrations using Windows, and later trying to run it again using Linux. See the image below.

I opened an ISSUE for them to verify this: adonisjs/lucid#799

Thank you for your attention.

[solucaodev]

Analyzing via DEBUG, I found that, when using mixed environments, the bug occurs.

If you create and run migrations on Linux only, everything is fine. The same is true when you create and run migrations on Windows only. Now, when trying to run migrations that have already been run on another platform, the code fails.

See the screenshot below for an example. There is a difference in the PATHS, more precisely in the slashes from "" to "/".