-
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
easy-rag blowing up if not using websockets #642
Labels
duplicate
This issue or pull request already exists
Comments
Adding a dependency exclusion seems to solve the problem for my app: <dependency>
<groupId>io.quarkiverse.langchain4j</groupId>
<artifactId>quarkus-langchain4j-easy-rag</artifactId>
<exclusions>
<exclusion>
<groupId>io.quarkiverse.langchain4j</groupId>
<artifactId>quarkus-langchain4j-parsers-base</artifactId>
</exclusion>
</exclusions>
</dependency> |
geoand
added a commit
that referenced
this issue
May 31, 2024
Ouch... #645 fixes the problem |
This is also a duplicate of #636 and since that one was opened first, I'll close this in favor of that one |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I want to use the easy-rag extension in an app that is not a websocket app (just a simple REST app), the application blows up when the rest endpoint is hit, I think because of https://github.com/quarkiverse/quarkus-langchain4j/blob/main/rag/parsers-base/runtime/src/main/resources/META-INF/services/io.quarkiverse.langchain4j.spi.DefaultMemoryIdProvider
The text was updated successfully, but these errors were encountered: