Error in migration engine - no current timer when using prisma2 migrate

[AlexanderProd]

I'm using the latest release 2.0.0-preview020 and I'm getting the following error when running prisma2 migrate save --experimental .

Error in migration engine.
Reason: [src/libcore/option.rs:1185:5] no current timer

Report id 1254

[tarazena]

Same in here.

[andresggarcia]

Having exact same issue just after upgrading to 2.0.0-preview020. Previous version with lift command worked just fine.

[naveen-bharathi]

same here. Is there any temporary solution or workaround?

I need to migrate to a new data model. But just don't know how to do it with this error

[andresggarcia]

As a workaround, you could use the previous API for migrations as follows:
npx prisma2@2.0.0-preview019 lift save
npx prisma2@2.0.0-preview019 lift up

[tomhoule]

I can't reproduce the issue - what operating system and what database are you using? It would also be helpful to have a sample schema where this happens.

[AlexanderProd]

@tomhoule I'm on macOS and using a MySQL database.

this is the schema I'm using.

datasource mysql {
  url      = "mysql://****:*****@*****/*****"
  provider = "mysql"
}

generator client {
  provider = "prisma-client-js"
}

model User {
  id        String   @id @default(cuid())
  createdAt DateTime @default(now())
  email     String   @unique
  name      String?
  phone     String?
  role      Role     @default(USER)
  posts     Post[]
}

model Post {
  id         String     @id @default(cuid())
  createdAt  DateTime   @default(now())
  updatedAt  DateTime   @updatedAt
  author     User
  title      String
  categories Category[]
  published  Boolean    @default(false)
}

model Category {
  id    String  @id @default(cuid())
  name  String
}

enum Role {
  USER
  ADMIN
}

[tomhoule]

Thanks a lot :) still investigating

[tomhoule]

Ok I managed to reproduce the crash, will post an update here as soon as it's fixed.

[tomhoule]

I have a fix - PR: prisma/prisma-engines#405

Will keep updating this issue until the fix is released.

[tomhoule]

preview 20.1 is being released right now - I will close this issue, thanks for reporting the bug and please continue giving feedback when things don't work :)

[yovanoc]

The new preview fix this issue but let us with a new one ^^

[PhilippSpo]

@yovanoc Yup I have the same issue.

[AlexanderProd]

Same here.

[AlexanderProd]

opened #1419