Call config: v0.28 renamed delayed_leave_event_* → delayed_leave.{delay_ms,restart_ms} with no fallback, and its package ships no config.json, so its defaults would be an 18 s delayed leave.
This build ships the Lotus values (60 s / 15 s, element-call lotus #46) as public/element-call/config.json, so the desktop app gets them too. On v0.25 desktop effectively had 18 s.
Web: the deploy never overwrites the server's own file (rsync --exclude config.json). That file has already been updated in production to carry both the old and new keys, so lotus.29 (live now) and v0.28 both read 60 s. A backup is at /root/element-call-config.json.bak-20261024 on LXC 106.
Verified on this exact build (vite preview with a local Synapse + LiveKit + JWT issuer + voice-limit guard):
boot.spec.ts: 7/7, including the bundled Element Call loading in a frame;
two-person E2EE video call: 2 tiles each, and both sides decode the other's video;
call bar: cinny's mic button turns Element Call's mic off and on, and the call state reaches the host;
earlier, on the branch build, mixed versions (v0.28 ↔ lotus.29) worked in both directions, so web users on the new version can call desktop users still on the old one.
Part of #201. Picks up element-call #61: the fork synced to **upstream v0.28.0**.
- `@lotusguild/element-call-embedded` 0.25.0-lotus.29 → **0.28.0-lotus.1**.
- **Call config:** v0.28 renamed `delayed_leave_event_*` → `delayed_leave.{delay_ms,restart_ms}` with no fallback, and its package ships no `config.json`, so its defaults would be an 18 s delayed leave.
- **This build ships the Lotus values** (60 s / 15 s, element-call lotus #46) as `public/element-call/config.json`, so the **desktop app** gets them too. On v0.25 desktop effectively had 18 s.
- **Web:** the deploy never overwrites the server's own file (rsync `--exclude config.json`). **That file has already been updated in production** to carry both the old and new keys, so lotus.29 (live now) and v0.28 both read 60 s. A backup is at `/root/element-call-config.json.bak-20261024` on LXC 106.
**Verified on this exact build** (`vite preview` with a local Synapse + LiveKit + JWT issuer + voice-limit guard):
- `boot.spec.ts`: 7/7, including the bundled Element Call loading in a frame;
- **two-person E2EE video call:** 2 tiles each, and both sides decode the other's video;
- **call bar:** cinny's mic button turns Element Call's mic off and on, and the call state reaches the host;
- earlier, on the branch build, **mixed versions** (v0.28 ↔ lotus.29) worked in both directions, so web users on the new version can call desktop users still on the old one.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
The fork synced to upstream v0.28.0 (element-call #61): matrix-js-sdk
develop with the SDK 44 MatrixRTC changes, delayed-leave delegation.
v0.28 renamed the delayed-leave config keys and its embedded build ships
no config.json (defaults: 18 s). Ship the Lotus values with the build
(build/element-call/config.json -> public/element-call/config.json) so
the desktop app keeps the 60 s grace from element-call lotus #46. The web
deploy keeps the server's own config.json (rsync excludes it); that file
already carries both the old and new keys.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Added a fix for the flaky #212 e2e test, which failed the post-merge run of #447 on lotus: it scrolled during the room's initial jump-to-bottom. It now waits for the timeline to settle and retries the scroll. 10/10 locally.
Added a fix for the flaky #212 e2e test, which failed the post-merge run of #447 on lotus: it scrolled during the room's initial jump-to-bottom. It now waits for the timeline to settle and retries the scroll. 10/10 locally.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The wheel ran as soon as the composer appeared; when it landed during the
room's initial jump-to-bottom it was snapped back and "Jump to Latest"
never showed. Seen ~1 in 5 runs since matrix-js-sdk 44 shifted the load
timing (failed the post-merge e2e run of #447 on lotus). Wait for the
newest message, then retry the scroll until the button appears.
10/10 locally.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
jared
merged commit 88446e8953 into lotus2026-10-24 03:02:12 -04:00
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.
Part of #201. Picks up element-call #61: the fork synced to upstream v0.28.0.
@lotusguild/element-call-embedded0.25.0-lotus.29 → 0.28.0-lotus.1.delayed_leave_event_*→delayed_leave.{delay_ms,restart_ms}with no fallback, and its package ships noconfig.json, so its defaults would be an 18 s delayed leave.public/element-call/config.json, so the desktop app gets them too. On v0.25 desktop effectively had 18 s.--exclude config.json). That file has already been updated in production to carry both the old and new keys, so lotus.29 (live now) and v0.28 both read 60 s. A backup is at/root/element-call-config.json.bak-20261024on LXC 106.Verified on this exact build (
vite previewwith a local Synapse + LiveKit + JWT issuer + voice-limit guard):boot.spec.ts: 7/7, including the bundled Element Call loading in a frame;🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Added a fix for the flaky #212 e2e test, which failed the post-merge run of #447 on lotus: it scrolled during the room's initial jump-to-bottom. It now waits for the timeline to settle and retries the scroll. 10/10 locally.
🤖 Generated with Claude Code