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

supabase / supabase-py / 41855538717
98%

Build:
DEFAULT BRANCH: main
Ran 04 Nov 2026 03:14PM UTC
Jobs 36
Files 100
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

04 Nov 2026 03:13PM UTC coverage: 94.573% (+0.06%) from 94.513%
41855538717

push

github

web-flow
refactor(auth): take refresh timer delays in seconds (#1974)

## What

`_AsyncTimer` and `_SyncTimer` in `supabase_auth/timer.py` named their
delay parameter `seconds` but treated it as milliseconds, dividing by
1000 before sleeping. The millisecond unit came over from gotrue-js.
Python's standard library uses seconds as a `float` (`asyncio.sleep`,
`threading.Timer`), so the timers now take seconds and pass the value
straight through.

Callers in `session.py` change to match:

- `save_session` passes `expire_in - refresh_duration_before_expires`
directly instead of multiplying by 1000.
- `start_auto_refresh_token` takes `seconds`.
- The retry delays are divided by 1000, so retries still wait exactly as
long as before. The retry backoff itself is wrong (it gives 1 ms, 4 ms,
16 ms and so on, while `RETRY_INTERVAL` is commented as deciseconds) and
will be fixed in a separate PR.

Behaviour is unchanged.

## Tests

- `tests/test_timer.py` checks that both timers fire after the given
number of seconds and that `cancel()` stops the callback.
- `test_save_session_schedules_refresh_in_seconds` (async and generated
sync) checks that saving a session that expires in an hour schedules the
refresh about `3600 - EXPIRY_MARGIN` seconds out.

Linear: SDK-1701

8504 of 8992 relevant lines covered (94.57%)

5.75 hits per line

Coverage Regressions

Lines Coverage ∆ File
22
79.58
-0.14% src/supabase_auth/session.py
1
99.55
0.02% tests/_sync/test_gotrue.py
1
99.55
0.02% tests/_async/test_gotrue.py
Jobs
ID Job ID Ran Files Coverage
1 supabase-py3.11-lowest-direct - 41855538717.1 04 Nov 2026 03:14PM UTC 19
92.79
GitHub Action Run
2 auth-py3.12-highest - 41855538717.2 04 Nov 2026 03:15PM UTC 35
91.76
GitHub Action Run
3 functions-py3.11-lowest-direct - 41855538717.3 04 Nov 2026 03:14PM UTC 14
97.45
GitHub Action Run
4 realtime-py3.14-highest - 41855538717.4 04 Nov 2026 03:15PM UTC 8
95.81
GitHub Action Run
5 functions-py3.15-highest - 41855538717.5 04 Nov 2026 03:14PM UTC 14
97.45
GitHub Action Run
6 auth-py3.11-highest - 41855538717.6 04 Nov 2026 03:14PM UTC 35
91.76
GitHub Action Run
7 realtime-py3.11-lowest-direct - 41855538717.7 04 Nov 2026 03:15PM UTC 8
96.51
GitHub Action Run
8 postgrest-py3.13-highest - 41855538717.8 04 Nov 2026 03:15PM UTC 24
97.51
GitHub Action Run
9 functions-py3.11-highest - 41855538717.9 04 Nov 2026 03:14PM UTC 14
97.45
GitHub Action Run
10 supabase-py3.13-highest - 41855538717.10 04 Nov 2026 03:14PM UTC 19
92.79
GitHub Action Run
11 auth-py3.15-highest - 41855538717.11 04 Nov 2026 03:15PM UTC 35
91.73
GitHub Action Run
12 postgrest-py3.15-highest - 41855538717.12 04 Nov 2026 03:15PM UTC 24
97.51
GitHub Action Run
13 supabase-py3.14-highest - 41855538717.13 04 Nov 2026 03:14PM UTC 19
92.76
GitHub Action Run
14 functions-py3.14-highest - 41855538717.14 04 Nov 2026 03:14PM UTC 14
97.45
GitHub Action Run
15 functions-py3.13-highest - 41855538717.15 04 Nov 2026 03:14PM UTC 14
97.45
GitHub Action Run
16 postgrest-py3.12-highest - 41855538717.16 04 Nov 2026 03:15PM UTC 24
97.51
GitHub Action Run
17 auth-py3.11-lowest-direct - 41855538717.17 04 Nov 2026 03:15PM UTC 35
91.76
GitHub Action Run
18 supabase-py3.12-highest - 41855538717.18 04 Nov 2026 03:14PM UTC 19
92.79
GitHub Action Run
19 supabase-py3.15-highest - 41855538717.19 04 Nov 2026 03:15PM UTC 19
92.76
GitHub Action Run
20 realtime-py3.12-highest - 41855538717.20 04 Nov 2026 03:15PM UTC 8
96.37
GitHub Action Run
21 realtime-py3.15-highest - 41855538717.21 04 Nov 2026 03:16PM UTC 8
95.96
GitHub Action Run
22 supabase-py3.11-highest - 41855538717.22 04 Nov 2026 03:14PM UTC 19
92.79
GitHub Action Run
23 functions-py3.12-highest - 41855538717.23 04 Nov 2026 03:14PM UTC 14
97.45
GitHub Action Run
24 storage-py3.11-lowest-direct - 41855538717.24 04 Nov 2026 03:15PM UTC 22
93.24
GitHub Action Run
25 storage-py3.15-highest - 41855538717.25 04 Nov 2026 03:16PM UTC 22
93.21
GitHub Action Run
26 postgrest-py3.14-highest - 41855538717.26 04 Nov 2026 03:15PM UTC 24
97.51
GitHub Action Run
27 postgrest-py3.11-highest - 41855538717.27 04 Nov 2026 03:15PM UTC 24
97.51
GitHub Action Run
28 storage-py3.14-highest - 41855538717.28 04 Nov 2026 03:15PM UTC 22
93.21
GitHub Action Run
29 storage-py3.12-highest - 41855538717.29 04 Nov 2026 03:15PM UTC 22
93.24
GitHub Action Run
30 auth-py3.13-highest - 41855538717.30 04 Nov 2026 03:15PM UTC 35
91.76
GitHub Action Run
31 storage-py3.11-highest - 41855538717.31 04 Nov 2026 03:15PM UTC 22
93.24
GitHub Action Run
32 realtime-py3.13-highest - 41855538717.32 04 Nov 2026 03:15PM UTC 8
96.37
GitHub Action Run
33 realtime-py3.11-highest - 41855538717.33 04 Nov 2026 03:15PM UTC 8
96.37
GitHub Action Run
34 auth-py3.14-highest - 41855538717.34 04 Nov 2026 03:15PM UTC 35
91.73
GitHub Action Run
35 postgrest-py3.11-lowest-direct - 41855538717.35 04 Nov 2026 03:15PM UTC 24
97.51
GitHub Action Run
36 storage-py3.13-highest - 41855538717.36 04 Nov 2026 03:15PM UTC 22
93.24
GitHub Action Run
Source Files on build 41855538717
  • Tree
  • List 100
  • Changed 5
  • Source Changed 0
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #41855538717
  • a5dca02d on github
  • Prev Build on main (#41853071122)
  • Next Build on main (#41857407018)
  • Delete
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