Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Error in migration engine. Reason: [migration-engine/core/src/commands/diff.rs:127:22] internal error: entered unreachable code: no provider, no shadow database url for migrations target #13633

Closed
tomhoule opened this issue Jun 3, 2022 · 0 comments · Fixed by prisma/prisma-engines#2989
Assignees
Labels
bug/1-unconfirmed Bug should have enough information for reproduction, but confirmation has not happened yet. kind/bug A reported bug. team/schema Issue for team Schema. tech/engines/migration engine Issue in the Migration Engine topic: entered unreachable code topic: error reporting Issues created via Prisma's CLI Crash Reporting topic: prisma migrate diff CLI: prisma migrate diff
Milestone

Comments

@tomhoule
Copy link
Contributor

tomhoule commented Jun 3, 2022

We are entering unreachable code, so there is a logic error somewhere.

Command: prisma migrate diff --from-migrations prisma/migrations/ --to-migrations prisma/_migrations --script
Version: 3.14.0
Binary Version: 2b0c12756921c891fec4f68d9444e18c7d5d4a6a
Report: https://prisma-errors.netlify.app/report/14009
OS: x64 linux 5.15.0-33-generic

JS Stacktrace:

Error: Error in migration engine.
Reason: [migration-engine/core/src/commands/diff.rs:127:22] internal error: entered unreachable code: no provider, no shadow database url for migrations target

Please create an issue with your `schema.prisma` at
https://github.com/prisma/prisma/issues/new

    at handlePanic (/tmp/a/node_modules/.pnpm/prisma@3.14.0/node_modules/prisma/build/index.js:112999:25)
    at ChildProcess.<anonymous> (/tmp/a/node_modules/.pnpm/prisma@3.14.0/node_modules/prisma/build/index.js:113008:15)
    at ChildProcess.emit (events.js:400:28)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)

Rust Stacktrace:

Starting migration engine RPC server
[migration-engine/core/src/commands/diff.rs:127:22] internal error: entered unreachable code: no provider, no shadow database url for migrations target
@tomhoule tomhoule added bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. process/candidate tech/engines/migration engine Issue in the Migration Engine topic: error reporting Issues created via Prisma's CLI Crash Reporting team/schema Issue for team Schema. labels Jun 3, 2022
@janpio janpio added topic: prisma migrate diff CLI: prisma migrate diff bug/1-unconfirmed Bug should have enough information for reproduction, but confirmation has not happened yet. and removed process/candidate bug/2-confirmed Bug has been reproduced and confirmed. labels Jun 3, 2022
@tomhoule tomhoule self-assigned this Jun 17, 2022
tomhoule added a commit to prisma/prisma-engines that referenced this issue Jun 17, 2022
The pattern match was not exhaustive where it should have been.

closes prisma/prisma#13633
tomhoule added a commit to prisma/prisma-engines that referenced this issue Jun 17, 2022
The pattern match was not exhaustive where it should have been.

closes prisma/prisma#13633
tomhoule added a commit to prisma/prisma-engines that referenced this issue Jun 17, 2022
The pattern match was not exhaustive where it should have been.

closes prisma/prisma#13633
@janpio janpio added this to the 4.0.x milestone Jun 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/1-unconfirmed Bug should have enough information for reproduction, but confirmation has not happened yet. kind/bug A reported bug. team/schema Issue for team Schema. tech/engines/migration engine Issue in the Migration Engine topic: entered unreachable code topic: error reporting Issues created via Prisma's CLI Crash Reporting topic: prisma migrate diff CLI: prisma migrate diff
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants