fix: Fix long message response error#2051
Merged
Merged
Conversation
csunny
approved these changes
Oct 16, 2024
Collaborator
csunny
left a comment
There was a problem hiding this comment.
@noahc1510 thank you for your contribution, it's useful.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
When I chat with a large database, the LLM will response a large content. The pymysql will feedback this error message: Data too long for column 'message_detail' at row 1.
This PR change the type of message_detail from text to longtext.
How Has This Been Tested?
Reproduct that case I wrote before, the bug has been fix.
Snapshots:
Checklist: