Repository navigation
fix: detect silent failures in gemini-cli by checking for invalid JSO… - #406
Merged
Merged
Conversation
megha1188
requested review from
R2wenD2,
gsquared94,
joshualitt and
verbanicm
December 3, 2025 09:53
MJjainam
approved these changes
Dec 3, 2025
Merged
parthasaradhie
pushed a commit
that referenced
this pull request
Dec 16, 2025
## What's Changed * fix #371 use JSON output of gemini cli by @gsehgal in #402 * fix: detect silent failures in gemini-cli by checking for invalid JSO… by @megha1188 in #406 * chore: Add Prettier and pre-commit hook for consistent formatting, applying initial format fixes across documentation and examples. by @parthasaradhie in #409 * Rename `DEBUG` input to `GEMINI_DEBUG` and pass `--debug` flag to CLI. by @parthasaradhie in #407 * ci: auto update GitHub Actions using dependabot by @JamBalaya56562 in #398 * Add job summary for Gemini CLI execution by @megha1188 in #423 ## New Contributors * @megha1188 made their first contribution in #406 * @parthasaradhie made their first contribution in #409 **Full Changelog**: v0.1.16...v0.1.17
parthasaradhie
added a commit
to parthasaradhie/run-gemini-cli
that referenced
this pull request
Dec 16, 2025
…alid JSO… (google-github-actions#406)" This reverts commit ad893a2.
parthasaradhie
added a commit
that referenced
this pull request
Dec 16, 2025
…alid JSON (#406)" (#426) This reverts commit ad893a2. Reverting this as its breaking v0.1.17 build <!-- Thank you for proposing a pull request! Please note that SOME TESTS WILL LIKELY FAIL due to how GitHub exposes secrets in Pull Requests from forks. Someone from the team will review your Pull Request and respond. Please describe your change and any implementation details below. -->
Merged
google-github-actions-bot
added a commit
that referenced
this pull request
Dec 16, 2025
## What's Changed * Revert "fix: detect silent failures in gemini-cli by checking for invalid JSON (#406)" by @parthasaradhie in #426 **Full Changelog**: v0.1.17...v0.2.0 --------- Signed-off-by: partha saradhi <[email protected]> Co-authored-by: partha saradhi <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I have updated the run-gemini-cli action to detect silent failures where the gemini CLI command produces no output (or invalid JSON) but exits with success (0). This typically happens when API resource limits are exceeded in non-interactive mode.
Verification Results
Automated Verification
I created a reproduction script >_reproduce_issue.sh that tested two scenarios:
This confirms that the action now correctly catches the silent failure mode without introducing false positives for normal success cases where stderr is empty.
Fixes #1088