claude-code - 💡(How to fix) Fix Monitor tool and run_in_background Bash exit 1 spuriously when polling `gh` in a loop [1 participants]

Error Messages / Logs

TL;DR

The issue can be resolved by wrapping the script in bash -c '...' to ensure consistent shell environment and handling of multibyte characters.

Guidance

• Verify that the issue is indeed caused by the shell environment difference by comparing the output of env command in both interactive and Monitor/background task subprocess sessions.
• Check for any emoji or multibyte characters in the job name or output of gh run view --json jobs that could be causing parsing issues.
• Consider adding error handling to the script to catch and log any errors that may be occurring, such as set -e to exit on error or trap to catch signals.
• Test the workaround with different job names and outputs to ensure it is a robust solution.

Example

bash -c '
  set -e
  while true; do
    out=$(gh run view 12345678 --json status,conclusion 2>/dev/null)
    status=$(echo "$out" | jq -r .status 2>/dev/null)
    echo "status=$status"
    if [ "$status" = "completed" ]; then break; fi
    sleep 30
  done
'

Notes

The issue may be specific to the Claude model or API platform being used, and further investigation may be needed to determine the root cause. Additionally, the workaround may have unintended consequences, such as changing the shell environment or behavior of the script.

Recommendation

Apply the workaround by wrapping the script in bash -c '...' to ensure consistent shell environment and handling of multibyte characters, as it has been shown to resolve the issue in the provided example.