'StringIO' object has no attribute <some-attribute>

[vesely-david]

Describe the bug

I believe there is a bug in RagasOutputParser when OutputParserException is raised.

While we try to generate new prompt, we forget to parse the output again..

Specificaly in

class RagasOutputParser(PydanticOutputParser[OutputModel]):
    async def parse_output_string(
        self,
        output_string: str,
        prompt_value: PromptValue,
        llm: BaseRagasLLM,
        callbacks: Callbacks,
        retries_left: int = 1,
    ):
        callbacks = callbacks or []
        try:
            jsonstr = extract_json(output_string)
            result = super().parse(jsonstr)
        except OutputParserException:
            if retries_left != 0:
                retry_rm, retry_cb = new_group(
                    name="fix_output_format",
                    inputs={"output_string": output_string},
                    callbacks=callbacks,
                )
                fixed_output_string = await fix_output_format_prompt.generate(
                    llm=llm,
                    data=OutputStringAndPrompt(
                        output_string=output_string,
                        prompt_value=prompt_value.to_string(),
                    ),
                    callbacks=retry_cb,
                    retries_left=retries_left - 1,
                )
                retry_rm.on_chain_end({"fixed_output_string": fixed_output_string})
                result = fixed_output_string
            else:
                raise RagasOutputParserException()
        return result

my chain of thoughts:

• the OutputModel of fix_output_format_prompt is StringIO
  => fixed_output_string will be of type StringIO
  => given result = fixed_output_string, the result will be of type StringIO no matter of what the original OutputModel is

Ragas version: 0.2.10
Python version: 3.10.13

---

I believe this issue, may be related

[tim-hilde]

I encounter the same error on my end!

[andreped]

Ugh. Encountering it myself right now. This worked fine a while back. I dont recall ever changing the ragas version, so it is likely coming from some hidden dependency, or similar.