Skip to content

fix(trigger-coolify-deploy): guard status-poll curl against transient exit 22 - #13

Merged
Andreas-Garcia merged 1 commit into
mainfrom
fix/polling-status-curl-guard
Sep 15, 2026
Merged

Andreas-Garcia merged 1 commit into
mainfrom
fix/polling-status-curl-guard

Conversation

@Andreas-Garcia

Copy link
Copy Markdown
Member

Summary

Second instance of the exit-22 bug class fixed in v4.3.2 (#12): the deployment status polling loop's curl -sf | jq call was unguarded under set -euo pipefail. Observed live on PR #253's preview deploy — the very first poll iteration hit a transient non-2xx response and hard-failed the whole action instead of retrying.

Changes

  • Wrap the polling loop's status=$(curl -sf ...) with set +e/exit-status capture, matching the existing cancel_phantom_builds() and mine_status guard pattern.
  • On query failure, log a warning and retry on the next poll interval (respecting the existing overall POLL_TIMEOUT_SECONDS) instead of aborting immediately.

Test plan

  • Will re-verify against PR #253's "Deploy API (preview)" / "Deploy showcase" checks once released and the consumer pin is bumped.

🤖 Generated with Claude Code

… exit 22

The deployment status polling loop's curl -sf | jq call was unguarded
under set -euo pipefail, same class of bug as the mine_status check
fixed in v4.3.2. A single non-2xx response (observed on the very first
poll iteration in PR #253's preview deploy) hard-failed the whole
action instead of retrying.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@Andreas-Garcia
Andreas-Garcia merged commit ae0771c into main Sep 15, 2026
1 check passed
@Andreas-Garcia
Andreas-Garcia deleted the fix/polling-status-curl-guard branch September 15, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant