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

supabase / cli / 39429407361
67%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 20 Oct 2026 01:20PM 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

20 Oct 2026 01:19PM UTC coverage: 66.808%. Remained the same
39429407361

push

github

web-flow
fix(cli): fingerprint stack target-resolution failures by step (#7239)

Stacked on #7211.

## TL;DR

Every experimental stack command reported every target-resolution
failure under one `invalid_config` fingerprint. That covers reading
saved stack state, decoding a saved stack, and resolving the project
root, so telemetry could not tell these causes apart. Each failed step
now has its own fingerprint in every stack command.

## Before

```mermaid
flowchart LR
  A["stack discovery fails"] --> X["<command>:invalid_config"]
  B["stack lookup fails"] --> X
  C["prefix match unreadable"] --> X
  D["project root unresolvable"] --> X
```

## After

```mermaid
flowchart LR
  A["stack discovery fails"] --> A2["<command>:stack_discovery"]
  B["stack lookup fails"] --> B2["<command>:stack_lookup"]
  C["prefix match unreadable"] --> C2["<command>:unreadable_stack"]
  D["project root unresolvable"] --> D2["<command>:project_root"]
```

## Why

Review on #7211 pointed out that the only remaining `invalid_config`
path in `stack start` is target resolution. That path is shared by all
stack commands, so it was left for a follow-up.

## What changed

- `StackTargetError` carries a closed `targetIssue` that the resolver
sets where each failure occurs.
- `mapTargetError` carries it into the start, stop, restart, status,
destroy, prepare, and logs errors. They report `stack_discovery`,
`stack_lookup`, `unreadable_stack`, or `project_root` instead of
`invalid_config`. In `stack start`, a configuration check's own
fingerprint still takes priority.
- prepare, restart, logs, and stop now use the shared `mapTargetError`
instead of local copies that would drop the new field.
- An invalid-config error without a `targetIssue` still reports
`invalid_config`. Error tags, messages, and output are unchanged.

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

---------

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

4110 of 6152 relevant lines covered (66.81%)

7.39 hits per line

Jobs
ID Job ID Ran Files Coverage
1 39429407361.1 20 Oct 2026 01:20PM UTC 79
66.81
GitHub Action Run
Source Files on build 39429407361
  • 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 #39429407361
  • b77a14f4 on github
  • Prev Build on gh-readonly-queue/develop/pr-7211-617be96e84543f5ae64d439467856ca803fc6063 (#39427431431)
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