-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix: No history while use openai chat #4148
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
There are several concerns and minor optimizations in your code:
Duplicate UUID Generation: The code generates a new UUID each time
generate_chatis called, even if a chat ID was provided. This can lead to inefficiency when creating many chats.Lazy Loading of Cache: If multiple instances request the same chat info without caching it explicitly, it could still be retrieved from the cache on subsequent requests. Consider using memoization or explicit caching mechanisms.
Serialization Logic: The serialization logic within
get_cacheseems redundant with how you handle cases where no chat_info exists in the database. You might want to simplify this part.ChatInfo Initialization: The way
set_cacheandre_open_chatare used indicates that they have internal state management that's not well-integrated intoget_cache. It may make sense to ensure these methods work correctly together without redundancy or overhead.This revised version should fix the issues mentioned above. It now properly handles lazy loading/cache retrieval, optimizes serializing/chat creation process, ensures proper separation between data fetching strategies, and provides more comprehensive exception handling around serialization errors.