1
84%
main: 84%

Ran 29 Jul 2026 02:20PM UTC

Files 99

Run time 6s

Badge

Embed ▾

Committed 29 Jul 2026 02:09PM UTC coverage: 84.037% (-0.02%) from 84.055%

Job # 30459456649.1

Build Type

push

github

Committed by

web-flow

Commit Message

fix(realtime): resume WebSocket continuations outside the lock (#1156)

Same anti-pattern as the AsyncValueSubject deadlock
(supabase/supabase-swift#1154): `onComplete`, `onWebSocketTaskOpened`,
and `_trigger` resumed/yielded continuations while holding
`mutableState`'s lock. Resuming a continuation can synchronously reach
into the Swift runtime's task status-record lock, which risks a
lock-order inversion if cancellation ever calls back into this lock
(not currently wired up, but the pattern is fragile and one
`withTaskCancellationHandler`/`onTermination` away from reintroducing
the same class of deadlock).

Compute the action under the lock, run it (resume/yield) after
releasing it — mirrors the fix already applied to AsyncValueSubject.

Coverage Stats

8439 of 10042 relevant lines covered (84.04%)

39.54 hits per line

supabase / supabase-swift / 30459456649 / 1
84%
main: 84%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 30459456649.1

supabase / supabase-swift / 30459456649 / 1 84% main: 84%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 30459456649.1

supabase / supabase-swift / 30459456649 / 1
84%
main: 84%

README BADGES
x