Migrate: Lift is freezing with Postgres when non standard port is used

[pantharshit00]

Backtrace, after waiting a while:

Error: Error in lift engine for rpc listMigrations:
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ConnectionError(Error(Some("error connecting to server: Connection refused (os error 61)"))

stack backtrace:
   0: backtrace::backtrace::trace::h862903ac52cf58ce (0x10e5cd8ae)
   1: backtrace::capture::Backtrace::new_unresolved::hb838890310508129 (0x10e5cca78)
   2: failure::backtrace::internal::InternalBacktrace::new::hbdea59428e164bec (0x10e5cc419)
   3: <failure::backtrace::Backtrace as core::default::Default>::default::h9577f3a4e995077c (0x10e5cc605)
   4: <failure::error::error_impl::ErrorImpl as core::convert::From<F>>::from::h4d07df56971b73db (0x10e1c772d)
   5: prisma_query::connector::postgres::PostgreSql::new::h413358e50dc533a4 (0x10e1e2fba)
   6: sql_migration_connector::SqlMigrationConnector::postgres_helper::hb687846233117d88 (0x10e1662a0)
   7: sql_migration_connector::SqlMigrationConnector::exists::hcbffc19b3c042435 (0x10e1653ef)
   8: migration_core::connector_loader::load_connector::hcd8a949dd5611bbb (0x10e076249)
   9: migration_core::migration_engine::MigrationEngine::init::h5a6429317c6e4260 (0x10e06b778)
  10: <F as jsonrpc_core::calls::RpcMethodSimple>::call::h6e069197e6f3babd (0x10e0b1ad8)
  11: <F as jsonrpc_core::calls::RpcMethod<T>>::call::h8b6fef1ab8ef20ba (0x10e057b9c)
  12: <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll::h5ef5874cf77881d7 (0x10e06a982)
  13: <futures::future::then::Then<A, B, F> as futures::future::Future>::poll::h80fed1dfafe2a57a (0x10e058360)
  14: <futures::future::map::Map<A, F> as futures::future::Future>::poll::he446a6b868c6556a (0x10e073c9f)
  15: <futures::future::either::Either<A, B> as futures::future::Future>::poll::he5d0fb6984529d00 (0x10e06ac10)
  16: futures::task_impl::std::set::h372284ab71bba6f7 (0x10e0a816f)
  17: <std::thread::local::LocalKey<T>>::with::h5153996dbd9d4602 (0x10e0aad16)
  18: futures::future::Future::wait::hff1c28893df49fb7 (0x10e0737ea)
  19: <jsonrpc_core::io::IoHandler<M>>::handle_request_sync::h91d7fd7e20b983ba (0x10e054d3f)
  20: migration_core::rpc_api::RpcApi::handle::h77f23d4b4ddc65ed (0x10e0b717b)
  21: migration_engine::main::h431600cedbc9116a (0x10e02eb3d)
  22: std::rt::lang_start::{{closure}}::h7cf2cabe6e9ed7ab (0x10e02e926)
  23: std::panicking::try::do_call::h20c95c457c762d5f (0x10e5e57d8)
  24: ___rust_maybe_catch_panic (0x10e5e947f)
  25: std::rt::lang_start_internal::he82d111f45e8971a (0x10e5e62be)
  26: _main (0x10e02eb99))', src/libcore/result.rs:997:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::result::unwrap_failed
   9: sql_migration_connector::SqlMigrationConnector::postgres_helper
  10: sql_migration_connector::SqlMigrationConnector::exists
  11: migration_core::connector_loader::load_connector
  12: migration_core::migration_engine::MigrationEngine::init
  13: <F as jsonrpc_core::calls::RpcMethodSimple>::call
  14: <F as jsonrpc_core::calls::RpcMethod<T>>::call
  15: <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll
  16: <futures::future::then::Then<A, B, F> as futures::future::Future>::poll
  17: <futures::future::map::Map<A, F> as futures::future::Future>::poll
  18: <futures::future::either::Either<A, B> as futures::future::Future>::poll
  19: futures::task_impl::std::set
  20: <std::thread::local::LocalKey<T>>::with
  21: futures::future::Future::wait
  22: <jsonrpc_core::io::IoHandler<M>>::handle_request_sync
  23: migration_core::rpc_api::RpcApi::handle
  24: migration_engine::main
  25: std::rt::lang_start::{{closure}}
  26: std::panicking::try::do_call
  27: __rust_maybe_catch_panic
  28: std::rt::lang_start_internal
  29: main

[pantharshit00]

Also, postgres is running locally on port 5431

[mavilein]

Fixed in: https://github.com/prisma/prisma/commit/9bcad048f26c23f5f23f73c4680cb56be05a4925
This will ship with preview3.

[pantharshit00]

Fix is also available in the current alpha

[herbertpimentel]

@mavilein I still have problem even using [email protected], binary version: 4f33077038a490e4b2c1c260f109309e4a447181

at first I was trying to using a existing db with tables in different schemas and the I get this error Cannot read property 'fields' of undefined

So I created a entire blank db with only one simple table and then still have the problem "Error in lift engine"

There's some other information I can provide to help identify it ?!

I am running it on macOSX with "PostgreSQL 10.5+tjap-20180921 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-16), 64-bit"

iMac-de-Herbert:prisma2 herbertpimentel$ prisma2 init app
✔ Connected to database
✔ Connected to database

Select the schema you want to introspect
──────────────────────────────────────────────────

◉ public 1 tables, 16.384 KB

New schema Or enter a name for a new schema

──────────────────────────────────────────────────

❯ Introspect Error in lift engine:
❮ Back (Database credentials)

[timsuchanek]

@herbertpimentel thanks a lot for letting is know! Can you turn the env var DEBUG=* and report the output in a separate issue? That would help us a lot!

[timsuchanek]

Fixed in latest version. We still have this issue in Photon, we track it here https://github.com/prisma/photonjs/issues/156