Bot action parsing fixes #1110
Open
Bot action parsing fixes #1110
Conversation
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
The LLM is returning the bot action inconsistently. When it returns something in a format the system does not expect, a colang parsing error happens and the application errors out.
Some examples of bot actions that were returned to me were:
bot responds with "You can call the number at 123-456-7891"bot says You can call the number at 123-456-7891bot provides information on "You can call the number at 123-456-7891"All of these caused the bot to error out and crash.
These changes ensure that the bot action is a "bot say" in the proper format. There may be some edge cases I am missing but these changes have made my application way more stable. I have been testing my application for the past 30 or so minutes and have yet to see any colang parsing errors.
Related Issue(s)
Checklist