36743071712
67%
develop: 67%

Ran 30 Sep 2026 04:18PM UTC

Jobs 1

Files 79

Run time 1min

Badge

Embed ▾

Committed 30 Sep 2026 04:16PM UTC coverage: 66.737%. Remained the same

Build # 36743071712

Build Type

push

github

Committed by

web-flow

Commit Message

chore(stack): log lazy wakes instead of bounding them in the proxy (#6909)

## Summary

When a lazy member's wake stalled behind a TCP endpoint, a client saw an
accepted connection that never answered until its own timeout fired, and
whole-stack e2e failure diagnostics only showed child-service output, so
nothing said where the wake stopped. This surfaced as a rare `PgClient:
Connection timed out` against the pooler after a stack reopen in the
native lifecycle e2e.

- The orchestrator logs when a wake is requested, with the service and
trigger, and when the member is ready, started without awaiting
readiness, or fails to wake.
- The TCP proxy logs an error naming the endpoint when waking or
connecting to its target fails. Transport resets after a successful
connect are not logged as failures.
- Whole-stack failure diagnostics include the tail of the stack owner's
log.

The proxies still wait for a wake without a bound of their own: a wake
includes preparation (image pulls) and prerequisite startup, which
already have their own budgets, and a single proxy-side timeout could
interrupt a legitimate cold start.

Coverage Stats

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	36743071712.1	30 Sep 2026 04:18PM UTC	79	66.74	GitHub Action Run

supabase / cli / 36743071712
67%
develop: 67%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 36743071712

supabase / cli / 36743071712 67% develop: 67%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 36743071712

supabase / cli / 36743071712
67%
develop: 67%

README BADGES
x