This website requires JavaScript.
Explore
Help
Sign In
starred
/
warmbly
Watch
1
Star
0
Fork
0
mirror of
https://github.com/warmbly/warmbly.git
synced
2026-11-17 16:19:13 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
0885efeb653a1617c19f3e2b3d1b21935b4011b2
warmbly
/
realtime
/
test
T
History
Matthew Meszaros
f38b2a1c31
feat: align realtime loopback HTTP socket family while preserving configured transport settings
2026-11-01 10:09:23 +01:00
..
realtime
feat: align realtime loopback HTTP socket family while preserving configured transport settings
2026-11-01 10:09:23 +01:00
realtime_web
feat: load the mailbox through the organization-scoped repository before reading its seed scope when starting or resuming warmup, and add cross-workspace tests for CRM, segments, templates, teams, webhooks, automations, export archives, agent sessions, public object prefixes, node and edge token separation and realtime channel joins
2026-10-26 06:25:04 +01:00
support
feat: bind each realtime ws ticket to the session that minted it and accept it once while that session is live, require a second-factor session to join admin:platform, confine API key and OAuth sockets to their own workspace with member permissions narrowed to their read scopes, and refuse those credentials in the socket URL unless REALTIME_ALLOW_QUERY_CREDENTIALS=true
2026-10-23 15:48:00 +02:00
test_helper.exs
feat: make the realtime service survive a client that spams channel joins, and stop both clients from being that client: ws_join is now spent per phx_join in a shared RealtimeWeb.ChannelGuard that every channel runs BEFORE its Auth lookup (it was only ever spent on the socket handshake, so an established socket could issue unlimited joins and each one cost a Postgres query), handshakes move to their own ws_connect bucket so a reconnect storm cannot eat the budget a client needs to rejoin with, the retry_after_ms hint now points at the next window instead of shrinking as overage grew, every channel's join rejection carries the numeric code the API reference already promised (plus 4005 for a malformed topic), BulkChannel only pushes an event to the user who owns the operation instead of to anyone who guesses the id, and the web and admin clients treat a rate_limited join as transient (wait out the hint, keep the socket) while backing off per-channel rejoins on a decaying schedule rather than reconnecting on the 120ms floor forever; adds an ExUnit suite for realtime and a vitest suite for admin, both wired into CI
2026-08-26 21:14:34 -07:00