• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 38390656970
67%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 13 Oct 2026 11:31AM UTC
Jobs 1
Files 79
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

13 Oct 2026 11:29AM UTC coverage: 66.737%. Remained the same
38390656970

push

github

web-flow
fix(cli): name the failing engine operation in stack telemetry (#7113)

## Summary

**TL;DR** When the new local stack fails because a container engine
command failed, telemetry now says which step failed (create, start,
inspect, engine target lookup, remove, or wait) instead of one shared
`engine_command` fingerprint. Recent prereleases surface
`engine_command` as the main cause of Docker `start` failures on Linux,
but not which Docker call breaks, so the failure couldn't be narrowed
down further.

### Before

```mermaid
flowchart LR
  A["docker create / start / rm / ..."] -->|fails| B["ContainerError<br/>operation"]
  B --> C["kind engine-command"]
  C --> D["…:engine_command"]
```

### After

```mermaid
flowchart LR
  A["docker create / start / rm / ..."] -->|fails| B["ContainerError<br/>operation"]
  B --> C["kind engine-create,<br/>engine-start, …"]
  C --> D["…:engine_command_create,<br/>…:engine_command_start, …"]
```

### What changed

- `@supabase/stack` classifies a `ContainerError` with no finer cause by
its engine operation:
  - `engine-create` ← `create`
  - `engine-start` ← `start`
  - `engine-inspect` ← `inspect`, `image`, `ps`
- `engine-target` ← `info`, `system`, `context`, identity and connection
checks
  - `engine-remove` ← `rm`, `stop`, `kill`, cleanup
  - `engine-wait` ← `wait`

  Any other operation stays `engine-command`.
- The CLI maps each new kind to an `engine_command_<step>` fingerprint
suffix. The category stays `runtime_crash`, so category-level grouping
is unchanged.
- The kind already travels as an open string on every owner/client
boundary, so there is no wire or schema change. A client that doesn't
know a new kind reports it as unclassified, as it does today for any
unknown kind.

## Linked issue

None. Telemetry follow-up to the stack failure classification in #7044.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38390656970.1 13 Oct 2026 11:31AM UTC 79
66.74
GitHub Action Run
Source Files on build 38390656970
  • Tree
  • List 79
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #38390656970
  • 5f4ac9c9 on github
  • Prev Build on gh-readonly-queue/develop/pr-7114-6cc6ae2895bbaafa73d08273c1724438b8f05d7c (#38390587456)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc