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

[BUG]: Unusable for me. Something about prisma client. #931

Closed
nmcbride opened this issue Mar 19, 2024 · 2 comments
Closed

[BUG]: Unusable for me. Something about prisma client. #931

nmcbride opened this issue Mar 19, 2024 · 2 comments
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.

Comments

@nmcbride
Copy link

How are you running AnythingLLM?

Docker (local)

What happened?

Downloaded the appimage, tried to run it.

Selected lmstudio and the included embedder.

Would not create a workspace just kept saying undefined.
Could not close it because it opens full screen with no controls. Had to force close it.

Re-opening it showed what I can only assume was the main window. Tried to create a workspace again but it errored.

I see this error:

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-3.0.x".
Add "rhel-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "rhel-openssl-3.0.x"]
}

The following locations have been searched:
  /tmp/.mount_gearle8zoSqp/resources/backend/node_modules/.prisma/client
  /tmp/.mount_gearle8zoSqp/resources/backend/node_modules/@prisma/client
  /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client
  /tmp/prisma-engines
  /tmp/.mount_gearle8zoSqp/resources/backend/prisma

Are there known steps to reproduce?

No response

@nmcbride nmcbride added the possible bug Bug was reported but is not confirmed or is unable to be replicated. label Mar 19, 2024
@timothycarambat
Copy link
Member

Duplicate of #898

The solution is in there. Basically need to unbundle app image, run a command, and it will work. Has to do with a build issue on bundling. It is being working on in that issue.

@nmcbride
Copy link
Author

Gotcha thanks. I'll just use a different solution for now until there is a non-broken build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.
Projects
None yet
Development

No branches or pull requests

2 participants