-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
8
-
False
-
-
False
-
-
-
DEVAI Sprint 3262, DEVAI Sprint 3263
Story (Required)
basic implementation of history persistence to store under local environment or memory
be able to read & write from local environment or buffer to save & restore the chat history.
in memory: https://js.langchain.com/v0.2/docs/integrations/vectorstores/memory/
This issue includes API implementation, and for load history will need to follow: https://docs.google.com/document/d/1nzW-crxBZoayWDWlZbtk0q6bmWFPy9qJ8Yun_zNOvRk/edit#heading=h.hvqemp7hyojv
upon chat completion request, it will also write to history.
This issue also will includes test automation for the new API
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
_no database required for this issue, will be included in https://issues.redhat.com/browse/DEVHAS-761 & https://issues.redhat.com/browse/DEVHAS-762_
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Required)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
documentation updates (design docs, release notes etc)
demo needed
SOP required
education module update (Filled by DEVHAS team only)
R&D label required (Filled by DEVHAS team only)
Done Checklist
Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well
- blocks
-
RHIDP-10263 API for UI to load the chat session with history
-
- Closed
-
-
RHIDP-10265 API to load all available session for a particular user
-
- Closed
-
-
RHIDP-10493 API for UI to delete the chat session
-
- Closed
-
- is cloned by
-
RHIDP-9967 Persistent storage for the chat history
-
- Refinement
-
- links to