When the homeserver hangs (it accepts connections but never answers, like the out-of-memory stall on 2026-09-29), sync stays SYNCING for up to 110 s: the 30 s pollTimeout plus the SDK's 80 s buffer. So no strip showed, and Kuma was never asked early.
Change
New useHomeserverStall watchdog. It checks every 10 s; if /sync is more than 45 s overdue, it probes GET /_matrix/client/versions with a 5 s timeout.
No answer → a Warning strip: "Lotus Chat's server isn't responding. Messages will send when it's back. Still trying…". The strip takes priority over "Connecting…".
ServerStatusFeature treats a stall like a lost sync, so Kuma is polled straight away and the "server is down" banner can take over.
The next sync clears it.
Verified by freezing the local Synapse with SIGSTOP for 90 s:
Before: no strip at any point in the 90 s.
After: the strip appears at 50 s and is gone 15 s after SIGCONT.
Unit test for the overdue rule. tsc clean · unit tests pass · ESLint clean.
Fixes #317.
When the homeserver hangs (it accepts connections but never answers, like the out-of-memory stall on 2026-09-29), sync stays `SYNCING` for up to **110 s**: the 30 s `pollTimeout` plus the SDK's 80 s buffer. So no strip showed, and Kuma was never asked early.
**Change**
- New `useHomeserverStall` watchdog. It checks every 10 s; if `/sync` is more than 45 s overdue, it probes `GET /_matrix/client/versions` with a 5 s timeout.
- No answer → a Warning strip: "Lotus Chat's server isn't responding. Messages will send when it's back. Still trying…". The strip takes priority over "Connecting…".
- `ServerStatusFeature` treats a stall like a lost sync, so Kuma is polled straight away and the "server is down" banner can take over.
- The next sync clears it.
**Verified** by freezing the local Synapse with `SIGSTOP` for 90 s:
- **Before:** no strip at any point in the 90 s.
- **After:** the strip appears at **50 s** and is gone 15 s after `SIGCONT`.
Unit test for the overdue rule. `tsc` clean · unit tests pass · ESLint clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
A hung Synapse (accepts connections, never answers) kept sync SYNCING
for up to 110 s (pollTimeout 30 s + the SDK's 80 s buffer), so no strip
showed and Kuma was never asked. A watchdog now notices a /sync overdue
by 45 s, confirms with a 5 s GET /_matrix/client/versions, then shows
"Lotus Chat's server isn't responding…" and polls Kuma at once.
Fixes#317
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #317.
When the homeserver hangs (it accepts connections but never answers, like the out-of-memory stall on 2026-09-29), sync stays
SYNCINGfor up to 110 s: the 30 spollTimeoutplus the SDK's 80 s buffer. So no strip showed, and Kuma was never asked early.Change
useHomeserverStallwatchdog. It checks every 10 s; if/syncis more than 45 s overdue, it probesGET /_matrix/client/versionswith a 5 s timeout.ServerStatusFeaturetreats a stall like a lost sync, so Kuma is polled straight away and the "server is down" banner can take over.Verified by freezing the local Synapse with
SIGSTOPfor 90 s:SIGCONT.Unit test for the overdue rule.
tscclean · unit tests pass · ESLint clean.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5