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

prisma2 init flow is throwing "File name too long" #904

Closed
pantharshit00 opened this issue Nov 8, 2019 · 5 comments
Closed

prisma2 init flow is throwing "File name too long" #904

pantharshit00 opened this issue Nov 8, 2019 · 5 comments
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/regression A reported bug in functionality that used to work before.
Milestone

Comments

@pantharshit00
Copy link
Contributor

pantharshit00 commented Nov 8, 2019

After installing preview 16, after following the following init flow:

  1. prisma2 init
  2. Blank project
  3. SQLite
  4. Selecting both Photon and Lift > Confirm
  5. Typescript
  6. Demo script

It is throwing the this Rust panic:
image

My suspicion is that this is caused by #841 so I am going to classify this as a regression. I use that init flow a lot to reproduce issues, so I will appreciate this being fixed relatively quickly.

@pantharshit00 pantharshit00 added bug/2-confirmed Bug has been reproduced and confirmed. kind/regression A reported bug in functionality that used to work before. process/candidate labels Nov 8, 2019
@pantharshit00
Copy link
Contributor Author

Version: prisma2@2.0.0-preview016, binary version: 377e2db71bae5da19d0090558c8819ff57dfdfc6

@homoky
Copy link

homoky commented Nov 8, 2019

Same here.

@nikolasburk
Copy link
Member

Also just ran into this when trying with:

  1. prisma2 init
  2. Starter Kit
  3. TypeScript
  4. GraphQL API

Here's the output:

$ prisma2 init gqltest

Preparing your starter kit: GraphQL API

✔  Downloading the starter kit from GitHub ...
⠹  Extracting content to gqltest ...
3  Installing dependencies with: `npm install` ...
4  Preparing your database ...
5  Seeding your database with: `npm run seed` ...
 ERROR  Error during command execution

DMMF To DML thread 'main' panicked at 'File should open read only: Os { code: 63, kind: Other, message: "File name too long" }', src/libcore/re
sult.rs:1165:5
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::default_hook
   5: std::panicking::rust_panic_with_hook
   6: std::panicking::continue_panic_fmt
   7: rust_begin_unwind
   8: core::panicking::panic_fmt
   9: core::result::unwrap_failed
  10: prisma::cli::CliCommand::new
  11: <std::future::GenFuture<T> as core::future::future::Future>::poll
  12: tokio_executor::enter::Enter::block_on
  13: tracing_core::dispatcher::with_default
  14: std::thread::local::LocalKey<T>::with
  15: tokio::runtime::threadpool::Runtime::block_on
  16: prisma::main
  17: std::rt::lang_start::{{closure}}
  18: std::panicking::try::do_call
  19: __rust_maybe_catch_panic
  20: std::rt::lang_start_internal
  21: main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
$ prisma2 -v
prisma2@2.0.0-preview016, binary version: 377e2db71bae5da19d0090558c8819ff57dfdfc6

@janpio
Copy link
Member

janpio commented Nov 8, 2019

We are looking into this right now and working on finding a fix.

@timsuchanek
Copy link
Contributor

Thanks for reporting! We just released a patch release to hot fix this!
https://github.com/prisma/prisma2/releases/tag/2.0.0-preview016.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/regression A reported bug in functionality that used to work before.
Projects
None yet
Development

No branches or pull requests

5 participants