-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Delegate binary downloading to prisma #22
Comments
The generator process of Prisma CLI Maybe it would also help to describe how you currently handle the engines here (and the CLI as well probably). |
@janpio Thank you! I will definitely make use of that if I start working on this.
I did notice that while reading through some prisma code and added it but don't make use of it: prisma-client-py/src/prisma/jsonrpc.py Line 35 in 33dc2c0
Do you know if prisma passes the resolved engine binary to the generator? |
My current understanding would be that it should pass a path to the engine, yes. But I am not aware of anyone using that, so might also be utterly broken. A quick read through the generator code on Prisma side might give clarity if this can even work. |
You are correct it does pass the engine path to the generator. However even though the native binaries are successfully downloaded, the following error is thrown when running
I can provide a full repro if that would help. |
That would be neat. Are you using |
Yes, I have used This actually uses the exact same CLI binary as the Go Client does and the engine binaries are handled in a similar way (I essentially just rewrote the Go Client's solution in python). Here's a reproduction for the issue, it assumes you have |
Problem
With many possible configurations and settings, binary downloading is complicated, as such we should see if it is possible to delegate this task to the prisma as they already handle all of it for us.
This is an issue as we currently don't respect any binary targets options or http proxy options like prisma does.
We would still have to download the CLI ourselves at the very least first.
The text was updated successfully, but these errors were encountered: