Reduce the number of LLM parsing error with conversational chats #7575
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.
A lot of times, when the LLM responses a Final Answer with markdown in the answer text (e.g. asking the LLM to write some code), the parser raises an OutputParserException("Could not parse LLM output: ..."), when the answer from the LLM is totally acceptable.
This change should reduce the number of such occurances.
For example, this response from gpt-turbo-3.5 for "How to convert a list of dict to a JSON in Python" seems totally acceptable as the final answer, but will raise the OutputParserException, even with
handle_parsing_errors=True
. This PR fixes it.