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

supabase / supabase-swift / 37503336118
95%

Build:
DEFAULT BRANCH: main
Ran 06 Oct 2026 05:30PM UTC
Jobs 1
Files 149
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

06 Oct 2026 05:24PM UTC coverage: 90.165% (+0.03%) from 90.132%
37503336118

push

github

web-flow
test(postgrest): close the access-token race + register compliance (#1418)

* test(postgrest): close the access-token race with a concurrent in-flight test

PostgrestClient.Configuration.accessToken (SDK-1571 / stage-2 plan Task 9)
already resolves the token fresh per request and fixes it into that
request's own local value before the transport call, so a later token
mutation cannot reach a request already in flight. The existing tests only
asserted sequential resolution, which is not the race the issue describes.

Add a test that starts a request, blocks it inside the transport (after it
has already resolved and set its own Authorization header), mutates the
token, runs a second request to completion, and only then releases the
first — asserting the first request still used the token it resolved
before the mutation.

* chore(compliance): register database.configuration.access_token

Move PostgrestClient.Configuration.accessToken out of the catch-all
supporting_symbols list (it is not a structural/shared member like the
PostgrestExecutableBuilder/Phase markers it sat next to) and attribute it
to its own feature, database.configuration.access_token.

Marked partially_implemented: the callback-based token, resolved fresh per
request, is in place, but the spec's 401-renewal behavior (re-invoking the
callback and resending the request, capped by auto_retry) is not — a 401
or a throwing callback just fails the request today. That renewal loop is
a separate, larger piece of work than sourcing the token from a provider.

* chore(compliance): mark database.configuration.access_token implemented

Renewal on a 401 is optional in the spec ("the SDK may ask the function
for a new token"), so its absence does not make the feature partial.

10809 of 11988 relevant lines covered (90.17%)

895805.68 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37503336118.1 06 Oct 2026 05:30PM UTC 149
90.17
GitHub Action Run
Source Files on build 37503336118
  • Tree
  • List 149
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #37503336118
  • 6bb55dec on github
  • Prev Build on main (#37469822501)
  • Next Build on main (#37525749602)
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