-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Prisma on linux #2
Comments
|
Related: prisma/specs#2 |
@ansarizafar which linux distribution and version are you using? |
I was having this issue previously prisma/migrate#19 but the issue was resolved
|
Thanks a lot! So it sounds like it's solved for you now? |
Closing this issue as it contains multiple issues, all of which are addressed except #157 If there is an issue with your distribution, please create a new issue with the specifics 🙏 |
I'm encountering this on Ubuntu 16. I get the following error on
I followed the instructions here to avoid an earlier related error (it couldn't find
|
Hello, CentOs 7.6.1810 I continued to have problems with glib library 2.18 because on centos there is 2.17 version installed. |
Can you please give us more information about your OS like the version? Output of I'd recommend you to open a new issue with the requested information |
I edited my previous comment with the info. There was on slack. |
* feat(adapter-pg,adapter-neon): Enforce usage of connection pool Adapters don't work with non-pooled `Client` instances. For `pg` and `neon` we enforce it only on type level, so check won't work for JS projects. In this PR, we are checking the passed instance and ensuring it is a `Pool`, similarly to what we already do for `planetscale`. Fix prisma/team-orm#616 * Add test script * Attempt to unify jest configs #2 * Fix couple of problems
* feat(adapter-pg,adapter-neon): Enforce usage of connection pool Adapters don't work with non-pooled `Client` instances. For `pg` and `neon` we enforce it only on type level, so check won't work for JS projects. In this PR, we are checking the passed instance and ensuring it is a `Pool`, similarly to what we already do for `planetscale`. Fix prisma/team-orm#616 * Add test script * Attempt to unify jest configs #2 * Fix couple of problems
…) (#22700) * feat(adapter-pg,adapter-neon): Enforce usage of connection pool Adapters don't work with non-pooled `Client` instances. For `pg` and `neon` we enforce it only on type level, so check won't work for JS projects. In this PR, we are checking the passed instance and ensuring it is a `Pool`, similarly to what we already do for `planetscale`. Fix prisma/team-orm#616 * Add test script * Attempt to unify jest configs #2 * Fix couple of problems
libssl1.1.so is missing
The text was updated successfully, but these errors were encountered: