-
Notifications
You must be signed in to change notification settings - Fork 7
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
Non-interactive environment #4
Comments
Hmm, I can't say that I didn't have that problem as well at some point, but I can't tell what made it go away or if it completely prevented me from using prisma. I'll have to check if prisma 5.13 got worse in that regard. It'd be interesting what makes prisma think that the environment is non-interactive. If there's something we can do to work around this, then we can keep this issue open. If it's something that can only be solved by fixing prisma, then we should close it. |
keystonejs/keystone#8898 was merged last year. I haven't mapped out enough of Prisma's inner workings to know one way or another. The error certainly originated from JS, so node as opposed to the Rust code, but the "why" is still a mystery to me. I need to setup a Proxmox machine anyway, I'll see if I can come up with a minimal NixOS config + project to repro the issue at least. That might also point me in the right direction of what's causing it. |
Hey @AThilenius — I highly doubt this is related to this flake, this sounds like a bug on our side, especially since you said yourself:
Once you have a reproduction ready, could you please open an issue in https://github.com/prisma/prisma? Thank you 🙏 |
@aqrln Will do. I agree, though it is likely to be specific to Nix, so figured I would start with someone else I know is using Nix. I'll mark this closed and reference it when I have a repro built out. Appreciate the responses! |
Hi @VanCoding, thank you so much for making this! I'm not sure this is the right place for this issue, so feel free to close it, I'm just hooping you've seen this before an possibly have a solution.
On NixOS with this flake (or any other way of installing Prisma) I get the following error when I run any interactive prisma command with
npx prisma ...
:The chunk of code that checks for interactivity is this which happily passes on my system. I switched to standard Bash to make sure it wasn't something to do with NuShell as well. This is on Prisma
5.13.0
which appears to be the latest version.It's a real show-stopper, as the
migrate dev
command seems to have zero way to bypass the non-interactive check, for which both prisma/prisma#4669 and prisma/prisma#7113 exist.Really appreciate your time!
The text was updated successfully, but these errors were encountered: