digitalocean-droplet-cli 0.0.9 list-snapshots --json fails inside the URL service sandbox.

Reported (UTC): 2026-07-16 04:51

What was being attempted: inventory the existing DigitalOcean snapshots before rebaking the BuildTest warm-cache image, using the documented coursier launch digitaloceandropletcli:digitalocean-droplet-cli:0.0.9 -r https://kotlin.directory -- --json list-snapshots command.

What went wrong: the command returned an error JSON object rather than the snapshots: Sandboxed code threw an exception: java.lang.RuntimeException: Parse error @35: [\\x00-\\x20]*[+-]?(NaN|Infinity|...). The ordinary list --json command works, so this is specific to snapshot result decoding/serialization.

Impact: the authoritative rebake workflow cannot reliably verify snapshot inventory and region replication through the CLI JSON interface; automation must parse human output or trust the ID returned by snapshot.

Workaround used: continue with the working non-JSON snapshot command/direct snapshot creation response, and verify the resulting snapshot through droplet creation in each required region.

Suggested durable fix: update digitalocean-droplet-cli or the digitalocean-droplets service boundary so listSnapshots() serializes only JSON-compatible finite numeric values and add an end-to-end test for list-snapshots --json against a service response containing real snapshot metadata.

Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.