-
Notifications
You must be signed in to change notification settings - Fork 12k
Closed
Labels
❗️ migrationscontains migration filescontains migration files🐛 bugSomething isn't workingSomething isn't working
Description
Bug Report: Prisma migrate command fails in non-interactive environments when running yarn dx
Issue Summary
The yarn dx command fails when executed in non-interactive environments (such as CI/CD, Docker containers, or automated scripts) due to Prisma migrate attempting to run prisma migrate dev which requires interactive input for migration name confirmation.
Steps to Reproduce
- Run
yarn dxin a non-interactive environment (CI/CD, Docker, automated script) - The command attempts to execute Prisma database migration
- Prisma migrate dev command fails with "command finished with error: command exited (1)"
Actual Results
- The
@calcom/prisma#db-migratetask fails duringyarn dxexecution - Error message:
ERROR: command finished with error: command (/home/user/cal.com/packages/prisma) yarn run db-migrate exited (1) - The entire
yarn dxworkflow stops and fails - Development environment setup is blocked
Expected Results
yarn dxshould successfully complete database setup in non-interactive environments- Database migrations should run without requiring user input
- Development environment should be ready for use after running
yarn dx
Technical Details
Root Cause Analysis:
- The issue occurs in
turbo.jsonpipeline configuration @calcom/prisma#db-seeddepends on@calcom/prisma#db-migratedb-migraterunsprisma migrate devwhich requires interactive input- In non-interactive environments, this command fails
Current Turbo Configuration:
"@calcom/prisma#db-seed": {
"cache": false,
"dependsOn": ["@calcom/prisma#db-migrate"]
}Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
❗️ migrationscontains migration filescontains migration files🐛 bugSomething isn't workingSomething isn't working