google-github-actions / google-github-actions/run-gemini-cli
Output real error instead of generic ` Gemini CLI stderr was not valid JSON`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 285
- Avg merge
- 8h 8m
- Merged PRs (30d)
- 1
Description
TL;DR
when Gemini API or anything else fails error is generic and not user friendly
Warning: Gemini CLI stderr was not valid JSON
Warning: Gemini CLI stdout was not valid JSON
would be great to see real stderr/stdout instead of generic errors
while there is possible to enable debugging, but with large logs over 30MB (zipped) github doesn't allow to download them (fails in middle)
Detailed design
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the action's handling of Gemini CLI stderr and stdout, especially where non-JSON output produces the two generic warnings. Verify the behavior against an API or CLI failure that emits invalid JSON, then confirm the resulting logs expose the real output without relying on downloadable debug artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100