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.

Sign up for GitHub

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

Fix some docs typos #1234

Merged
merged 1 commit into from
Jan 22, 2025
Merged

Fix some docs typos #1234

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/modules/ROOT/pages/ai-services.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ The extension provides a default implementation of `ChatMemoryProvider` which do
[IMPORTANT]
====
The topic of `ChatMemory` cleanup is of paramount importance in order to avoid having the application terminate with `out of memory` errors. For this reason, the extension automatically removes all the `ChatMemory` objects from
the underlying `ChatMemoryStore` when the AI Service goes out of scope (recall from our discussion about <<scope,scope>> that such bean are `@RequestScoped` be default).
the underlying `ChatMemoryStore` when the AI Service goes out of scope (recall from our discussion about <<scope,scope>> that such beans are `@RequestScoped` by default).

However, in cases where more fine-grained control is needed (which is the case when the bean is declared as `@Singleton` or `@ApplicationScoped`) then `io.quarkiverse.langchain4j.ChatMemoryRemover` should be used to manually remove elements.
====
Expand Down
Loading