Regular Issue with editing json files.

[Andy]

I regularly get crash out errors with Rovodev crashing out when processing json files.

[{'type': 'json_invalid', 'loc': (), 'msg': 'Invalid JSON: EOF while parsing an object at line 1 column 49', 'inp.

╭─ Error ──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Failed to generate an LLM response. │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ To resume your session, restart Rovo Dev CLI with the --restore flag. │
╰──────────────────────────────────────────────────────────────────────

None of my other coding agents have issues with these files,..

[KW Lam]

Hi Andy,

To clarify, the error occurs because Rovodev is unable to process the session's JSON file. I suspect this could be due to either a limitation in the tool or an unexpected response structure from the LLM. Regardless, it’s Rovodev’s responsibility to address the issue.

Here are the key points:

1. The /prune command does not appear to resolve the problem.

2. A proper fix will need to come from the Rovodev team.

In the meantime, I’ve applied a workaround by starting a new session, which resolves the issue. However, the downside is that you won’t be able to resume from the previous (corrupted) session and will need to start over.

[Jovana Dunisijevic]

Hi @Andy 

Thanks for reporting this issue.

The error message suggests that Rovo Dev CLI is encountering problems parsing your JSON files and it may be hitting an unexpected end-of-file or malformed JSON structure. While other coding agents might be more forgiving, Rovo Dev CLI currently requires strict JSON formatting.

A few suggestions:

• Double-check that your JSON files are valid and properly closed (no missing brackets or commas).

• If possible, try running your file through a JSON validator before processing it with Rovo Dev CLI.

• We're aware that this can be frustrating, and your feedback will help us improve error handling and compatibility in future releases.

I share all the feedback with the product team that I hear from the community, so it's always very welcome.

If you can share a sample file (with sensitive info removed), we can help investigate further. 

Thank you!

Kindest regards,

Jovana

[KW Lam]

Hi Jovana,

Unfortunately the error message did not indicate which malform file is the culprit. By any chance if Rovo Dev CLI can be enhanced to inform user the culprit?

[Jovana Dunisijevic]

Hey @KW Lam 

I agree that aspect has to improve! I shared your feedback with the product last week! I expect to see this addressed soon.

We've already implemented a few features that were provided as feedback directly from you, our community members!