Missing credentials in Postgres URL: Got invalid RPC response without .result property

Schema

datasource db {
  provider = "postgresql"
  url      = "postgresql://localhost:5432/bother?schema=public"
}

generator photonjs {
  provider = "photonjs"
}

model Post {
  id       String    @id @default(cuid())
  body     String
  comments Comment[]
  location Float[]
  rating   Int
  ratings  Rating[]
  user     User
  created  DateTime  @default(now())
}

model Rating {
  id        String   @id @default(cuid())
  direction Int
  post      Post
  user      User
  created   DateTime @default(now())
  updated   DateTime @default(now())
}

model Comment {
  id      String   @id @default(cuid())
  body    String
  post    Post
  user    User
  created DateTime @default(now())
}

model User {
  id            String   @id @default(cuid())
  notifications Boolean
  platform      String
  posts         Post[]
  push_token    String
  created       DateTime @default(now())
  updated       DateTime @default(now())
}

Versions

macOS 10.14.5 (18F132)
Prisma prisma2@2.0.0-preview-7, binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054
PostgreSQL psql (PostgreSQL) 11.4

@pantharshit00 I’m not using embeds or dashes in my schema name. VSCode Prisma extension clears my schema, too. Any help?

[pantharshit00]

Thanks, I was able to reproduce this now 🎉

Reproduction steps:

1. Create a new postgres instance on Heroku
2. Initialise a new project using prisma2 init flow and the credentials obtained from above(remember that SSL is required)
3. Run `prisma2 lift save --name ‘init’
4. See the error.

Version: prisma2@2.0.0-preview-7, binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054

Rust backtrace:

LiftEngine:stderr thread 'main' panicked at 'Box<Any>', migration-engine/core/src/main.rs:57:23 +0ms
  LiftEngine:stderr stack backtrace: +29ms
  LiftEngine:stderr    0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace +1ms
  LiftEngine:stderr    1: std::sys_common::backtrace::_print +0ms
  LiftEngine:stderr    2: std::panicking::default_hook::{{closure}} +0ms
  LiftEngine:stderr    3: std::panicking::default_hook +0ms
  LiftEngine:stderr    4: std::panicking::rust_panic_with_hook +0ms
  LiftEngine:stderr    5: std::panicking::begin_panic +0ms
  LiftEngine:stderr    6: migration_engine::main +0ms
  LiftEngine:stderr    7: std::rt::lang_start::{{closure}} +0ms
  LiftEngine:stderr    8: std::panicking::try::do_call +0ms
  LiftEngine:stderr    9: __rust_maybe_catch_panic +0ms
  LiftEngine:stderr   10: std::rt::lang_start_internal +0ms
  LiftEngine:stderr   11: main +0ms

[divyenduz]

This is not reproducible anymore with

divyendusingh [p2-pg]$ prisma2 --version
prisma2@2.0.0-preview-9.1, binary version: bbbeff6f84b408e534ebd866bfd378748e6d6611

I tried these situations (wrong user, missing port, local or remote pg, missing env, wrong env).

I am closing this one, if you still run into this issue, please create a new GH issue possibly with a minimal reproduction and tag me there 🙌