tajniak81andClaude Opus 5.5
487e0f410b
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
Implements PLAN.md Phase 10. Simplified Sliding Sync (MSC4186) is served at the unstable org.matrix.simplified_msc3575 endpoint and advertised in /versions. Lists are sorted by activity and filtered by DM, invite, encryption, room type, space and tag; room subscriptions, required_state with wildcards, $ME and $LAZY, and the to_device, e2ee, account_data, receipts and typing extensions are supported. Per-connection state is kept in memory and an unknown pos answers M_UNKNOWN_POS. Threads and relations: m.relates_to is indexed on roomserver_events (migration 0012), /relations (with recursion) and /threads are served, and every event a timeline read returns carries its m.thread, m.replace and m.reference summaries in unsigned.m.relations. Notifications carry a thread ID (migration 0013): threaded receipts clear only their thread, and sync reports unread_thread_notifications when the filter asks. Spaces: /hierarchy walks a space breadth first, asking other servers about rooms this one is not in through the new federation hierarchy endpoint; room_summary describes one room. /search runs on FTS5 (sqlite, pocketbase) or tsvector (postgres), bounded to what each user may see, with context, profiles, state, grouping and paging. The PocketBase driver is real: the sqlite schema and store on an embedded PocketBase app's database, with media in its filesystem, local or S3 (database.pocketbase.s3). It runs the full storage test suite. Ops: OpenTelemetry tracing over OTLP/HTTP (tracing.*), with server spans per route, component spans, and trace propagation on federation, push and application service calls. New metrics for persisted events, waiting syncs, sliding sync connections and the database pool, with a Grafana dashboard. deploy/ adds a Compose setup (PostgreSQL, Prometheus, Grafana, Jaeger) and a Helm chart; cmd/warp-loadtest loads a server and reports request and delivery latencies. The load tester found a long-standing bug, fixed here: on a server where no account data had been written, every incremental /sync re-sent the push rules and returned at once, and an all-zero token was taken for an initial sync, so long polls became busy loops. The PostgreSQL migrations and search dialect compile but were not run against a live PostgreSQL in this change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
62 lines
3.0 KiB
SQL
62 lines
3.0 KiB
SQL
-- Phase 10: relations (threads, edits, reactions, references) and
|
|
-- full-text search.
|
|
|
|
-- content.m.relates_to of each event, written out so that "the children of
|
|
-- this event" is an index lookup. Both are '' for an event that relates to
|
|
-- nothing, and are cleared when the event is redacted: the redaction
|
|
-- algorithm strips the content they came from.
|
|
ALTER TABLE roomserver_events ADD COLUMN relates_to_id TEXT NOT NULL DEFAULT '';
|
|
ALTER TABLE roomserver_events ADD COLUMN rel_type TEXT NOT NULL DEFAULT '';
|
|
|
|
-- The events already stored. Only a relation with both fields a string
|
|
-- counts, which is the rule the roomserver applies to new events.
|
|
UPDATE roomserver_events SET
|
|
relates_to_id = json_extract(event_json, '$.content."m.relates_to".event_id'),
|
|
rel_type = json_extract(event_json, '$.content."m.relates_to".rel_type')
|
|
WHERE redacted_by = ''
|
|
AND json_type(event_json, '$.content."m.relates_to".event_id') = 'text'
|
|
AND json_type(event_json, '$.content."m.relates_to".rel_type') = 'text';
|
|
|
|
-- /relations, the bundled summaries and /threads all start from a parent
|
|
-- and read its children in stream order.
|
|
CREATE INDEX IF NOT EXISTS roomserver_events_relations_idx
|
|
ON roomserver_events (room_id, relates_to_id, rel_type, stream_ordering);
|
|
|
|
-- The full-text index /search reads: one row per searchable event, keyed by
|
|
-- the event's stream ordering as its rowid, which is unique across the
|
|
-- server and is what a redaction finds the row by. Outliers are not here:
|
|
-- an event joins the index when it joins a timeline.
|
|
--
|
|
-- unicode61 with diacritics removed matches "cafe" against "café", which is
|
|
-- what a user searching a chat history expects.
|
|
CREATE VIRTUAL TABLE IF NOT EXISTS roomserver_event_search USING fts5(
|
|
body,
|
|
room_id UNINDEXED,
|
|
event_id UNINDEXED,
|
|
search_key UNINDEXED,
|
|
sender UNINDEXED,
|
|
event_type UNINDEXED,
|
|
tokenize = 'unicode61 remove_diacritics 2'
|
|
);
|
|
|
|
INSERT INTO roomserver_event_search (rowid, body, room_id, event_id, search_key, sender, event_type)
|
|
SELECT stream_ordering, json_extract(event_json, '$.content.body'), room_id, event_id,
|
|
'content.body', sender, event_type
|
|
FROM roomserver_events
|
|
WHERE event_type = 'm.room.message' AND NOT outlier AND redacted_by = ''
|
|
AND json_type(event_json, '$.content.body') = 'text';
|
|
|
|
INSERT INTO roomserver_event_search (rowid, body, room_id, event_id, search_key, sender, event_type)
|
|
SELECT stream_ordering, json_extract(event_json, '$.content.name'), room_id, event_id,
|
|
'content.name', sender, event_type
|
|
FROM roomserver_events
|
|
WHERE event_type = 'm.room.name' AND NOT outlier AND redacted_by = ''
|
|
AND json_type(event_json, '$.content.name') = 'text';
|
|
|
|
INSERT INTO roomserver_event_search (rowid, body, room_id, event_id, search_key, sender, event_type)
|
|
SELECT stream_ordering, json_extract(event_json, '$.content.topic'), room_id, event_id,
|
|
'content.topic', sender, event_type
|
|
FROM roomserver_events
|
|
WHERE event_type = 'm.room.topic' AND NOT outlier AND redacted_by = ''
|
|
AND json_type(event_json, '$.content.topic') = 'text';
|