-
Notifications
You must be signed in to change notification settings - Fork 966
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
Bump LiteralAI version #1376
Bump LiteralAI version #1376
Conversation
c9bbd7d
to
bf8ccab
Compare
During manual evaluation, I've been getting:
I'm doing further testing right now. |
I've confirmed that #1370 is present in main. The PaginatedResponse errors do seem to correspond with
|
10090ef
to
0cfa1bf
Compare
…e exceptions. - Create LiteralToChainlitConverter class for handling conversions - Implement methods for converting steps, threads, and attachments - Add support for different Element subclasses based on metadata - Allow manual setting of thread_id and id for Step and Element
Got the following error report: message.txt To reproduce set a literal api key, setup dummy auth like
create a conversation with an image, refresh the page and try to load it from the history |
Just replicated this with a .txt file attachment. With pure text it seems to work fine. |
c2eaf0c
to
7575e98
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested, the attachment bug is fixed!
* Bump LiteralAI dependency, update related imports. * Cleanup and organize imports from SQLAlchemy tests. * Extensive unittest coverage for LiteralDataLayer. * Consistent LiteralAI to Chainlit conversion, resolve PaginatedResponse exceptions. * LiteralToChainlitConverter class for handling conversions, methods for converting steps, threads, and attachments. * Allow manual setting of thread_id and id for Step and Element --------- Co-authored-by: EWouters <[email protected]>
Requires: