dosubot[bot]
commented
1 year ago 🤖
Hello,
Thank you for bringing this issue to our attention. The error you're encountering seems to be due to the llm_output parameter of the default_output_processor function being a string of query instructions or the final response from the engine, rather than the expected JSON Path.
To resolve this issue, you could modify the default_output_processor function to check if the llm_output is a valid JSON Path before attempting to parse it. If it's not, the function could return an error message or handle the situation in a way that suits your application.
Here's a modified version of the default_output_processor function that includes this check:
def default_output_processor(llm_output: str, json_value: JSONType) -> JSONType:
"""Default output processor that executes the JSON Path query."""
try:
from jsonpath_ng.ext import parse
from jsonpath_ng.jsonpath import DatumInContext
except ImportError as exc:
raise ImportError(IMPORT_ERROR_MSG) from exc
# Check if llm_output is a valid JSON Path
if not isinstance(llm_output, str) or not llm_output.startswith('$'):
raise ValueError("Invalid JSON Path: llm_output should be a string starting with '$'")
datum: List[DatumInContext] = parse(llm_output).find(json_value)
return [d.value for d in datum]This version of the function raises a ValueError if llm_output is not a string starting with '$', which is a common starting point for JSON Path expressions. You can adjust this check to suit the specific format of JSON Path expressions used in your application.
Please note that this is a workaround and might not cover all edge cases. If the issue persists, please provide more details about the specific queries that are causing the problem.
Best, Dosu
Sources
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
wodka
Bug Description
The parameter
llm_outputof functiondefault_output_processorcan be a string of:Exception:
jsonpath_ng: Exception: Parse error at 1:5 near token task (ID)Version
0.8.14
Steps to Reproduce
.query()The bug doesn't occur often, so that it might take some time. Pay attention to the llm_output of
default_output_processorNote: I have to use a custom output processor that mimics the default function to see the issue.
Relevant Logs/Tracbacks