Skip to content

fix: detect silent failures in gemini-cli by checking for invalid JSO… #406

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MJjainam merged 1 commit into from
Dec 3, 2025
Merged

fix: detect silent failures in gemini-cli by checking for invalid JSO… #406

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -326,8 +326,13 @@ runs:
if jq -e . "${TEMP_STDERR}" >/dev/null 2>&1; then
ERROR_JSON=$(jq -c '.error // empty' "${TEMP_STDERR}")
fi
if ! { jq -e . "${TEMP_STDERR}" >/dev/null 2>&1 && jq -e . "${TEMP_STDOUT}" >/dev/null 2>&1; }; then
if ! jq -e . "${TEMP_STDOUT}" >/dev/null 2>&1; then
echo "::warning::Gemini CLI output was not valid JSON"
# If we failed to parse JSON and the command didn't fail, this is likely a silent failure (e.g. resource limit)
if [[ "${FAILED}" == "false" ]]; then
echo "::error title=Gemini CLI execution failed::Gemini CLI produced invalid or empty JSON output, which usually indicates a silent failure."
FAILED=true
fi
fi


Expand Down
Loading