A b055c0a285 fix: gcp and digitalocean destroy_server silently swallow errors (#1615) ... GCP's destroy_server redirected both stdout and stderr to /dev/null without checking the exit code, so deletion failures were invisible to users. DigitalOcean's destroy_server never checked the API response for error payloads, always reporting success. Both bugs could leave cloud instances running (and charging money) while telling users they were destroyed. Same class of bug fixed for AWS in PR #1606. Agent: code-health Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-02-21 17:08:53 -05:00
..
common.sh	fix: gcp and digitalocean destroy_server silently swallow errors (#1615)	2026-02-21 17:08:53 -05:00