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 3: the roomserver, the room half of storage, the Client-Server room endpoints and the admin room endpoints. A client can now create a room, invite, join, leave, kick, ban, send messages and state, redact, name a room with an alias and find one in the public directory. Nothing talks to another server; every operation that would need to is refused with a message that says so rather than a bare M_FORBIDDEN. roomserver: one input pipeline every event goes through, whatever sent it — validate, authorise, resolve, persist, emit. The rules are not reimplemented here; internal/matrix is pure library code and this is what connects it to a database and to a room's history. The Client-Server handlers do no authorisation of their own, deliberately: whether Alice may kick Bob is a question about the room's power levels, and the one place that is answered correctly is the authorisation rules inside the pipeline. A mutex per room serialises writers. Two events racing into one room would each read the same forward extremities, both become one, and fork the room for no reason — which would then need state resolution to put back together. State resolution is wired in anyway for the multi-extremity case. It is unreachable from outside in this phase, and the alternative is a pipeline that authorises against one arbitrary branch of a fork without saying so. Room versions 3 to 12 all work and are each tested end to end. Version 12 earns that coverage: its room ID is the create event's own ID, its create event carries no room_id, and the create event is excluded from every other event's auth_events — so the state auth.Check is given is the event's auth_events plus the create event, which that version identifies by room ID rather than citing. createRoom sends the spec's events in the spec's order, each authorised against what the ones before it produced. A failure part-way leaves an incomplete room, which is the lesser evil: the alternative is holding every event of a new room in memory and writing them in one transaction, making the pipeline that authorises them a special case. The one failure a second client can cause at any time, an alias clash, takes the room row back out. Redactions stay two decisions, as the spec keeps them. The rules let almost any redaction into the room; whether it applies to its target is a separate test, run inside the same transaction as the redaction itself so that a client holding an event ID can always read the stripped event. storage: events keyed by event ID rather than by a surrogate, since an event ID appears in prev_events, auth_events, state snapshots and client requests alike. Stream ordering comes from a counter row bumped inside the write transaction, because a PostgreSQL sequence is explicitly not transactional and a rolled-back write would leave a hole in the stream that /sync would have to be taught to skip. State snapshots are stored per event and deduplicated by content hash, so the table grows with state changes rather than with traffic — and that is what makes "the state after a forward extremity" answerable at all. The room's listing columns are denormalised onto its row because the public directory orders every published room by member count and pages the result, which cannot be done by reading each room's state in turn. Federation-disabled behaviour from PLAN.md section 3 is enforced here. Restricted joins are the exception that works: the rule needs a signature from the authorising user's server verified, and while federation is off that server is always this one. adminapi: room list and detail, purge, force-leave, and room and event counters on the dashboard. clientapi gains its own rate-limit buckets for createRoom and for joining, both of which write events rather than read them. Tested against the real event core and a real database rather than fakes: what is under test is whether an event this server signs is one the authorisation rules accept, and a fake of either would only prove that the pipeline calls what the fake expects. The storage tests run against both SQL drivers. docs/rooms.md describes the pipeline, the storage decisions and the known gaps — chief among them that history visibility is room-level rather than per-event, and that /sync still reports no rooms, both of which belong with the event stream in Phase 4. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
106 lines
3.4 KiB
Go
106 lines
3.4 KiB
Go
package roomserver
|
|
|
|
import (
|
|
"context"
|
|
|
|
"github.com/dariuszjaniak/warp/server/internal/matrix/event"
|
|
"github.com/dariuszjaniak/warp/server/internal/storage"
|
|
)
|
|
|
|
// RoomDetails is a room as the admin panel shows it: the stored summary
|
|
// plus the things only a count can answer.
|
|
type RoomDetails struct {
|
|
storage.RoomSummary
|
|
|
|
// Members counts every m.room.member event in the current state,
|
|
// whatever the membership — a room with one member and forty bans is
|
|
// not the same room as one with one member.
|
|
Members int
|
|
|
|
// InvitedMembers counts the outstanding invites.
|
|
InvitedMembers int
|
|
|
|
// Aliases are the local aliases pointing at the room.
|
|
Aliases []string
|
|
|
|
// ForwardExtremities are the event IDs the room's DAG currently ends
|
|
// at. There is normally one; more than one means the room has forked,
|
|
// which is worth seeing on an operator's screen.
|
|
ForwardExtremities []string
|
|
}
|
|
|
|
// ListRooms returns a page of every room on this server, for the admin API.
|
|
func (r *API) ListRooms(ctx context.Context, filter storage.RoomFilter) ([]storage.RoomSummary, int, error) {
|
|
return r.store.ListRooms(ctx, filter)
|
|
}
|
|
|
|
// RoomDetails reads one room in full, for the admin API.
|
|
func (r *API) RoomDetails(ctx context.Context, roomID string) (RoomDetails, error) {
|
|
summary, err := r.store.RoomSummary(ctx, roomID)
|
|
if err != nil {
|
|
return RoomDetails{}, err
|
|
}
|
|
|
|
memberships, err := r.store.MembershipEntries(ctx, roomID, nil)
|
|
if err != nil {
|
|
return RoomDetails{}, err
|
|
}
|
|
details := RoomDetails{RoomSummary: summary, Members: len(memberships)}
|
|
for _, m := range memberships {
|
|
if m.Membership == event.MembershipInvite {
|
|
details.InvitedMembers++
|
|
}
|
|
}
|
|
|
|
if details.Aliases, err = r.store.AliasesForRoom(ctx, roomID); err != nil {
|
|
return RoomDetails{}, err
|
|
}
|
|
if details.Aliases == nil {
|
|
details.Aliases = []string{}
|
|
}
|
|
|
|
extremities, err := r.store.Extremities(ctx, roomID)
|
|
if err != nil {
|
|
return RoomDetails{}, err
|
|
}
|
|
details.ForwardExtremities = make([]string, 0, len(extremities))
|
|
for _, e := range extremities {
|
|
details.ForwardExtremities = append(details.ForwardExtremities, e.EventID)
|
|
}
|
|
return details, nil
|
|
}
|
|
|
|
// PurgeRoom deletes a room and everything belonging to it.
|
|
//
|
|
// This is the one operation in the roomserver that destroys history, and it
|
|
// is irreversible: the events are gone, not tombstoned. It exists because a
|
|
// room can become something an operator has to be able to remove — abuse, a
|
|
// room nobody is in any more, a room whose version this build no longer
|
|
// supports — and because the alternative an operator reaches for otherwise
|
|
// is deleting rows by hand.
|
|
//
|
|
// It does not tell the room's members. Nothing can: the room's events are
|
|
// what a membership change would have to be added to.
|
|
func (r *API) PurgeRoom(ctx context.Context, roomID string) error {
|
|
// The lock is taken so that a purge cannot race a send into the same
|
|
// room and leave the event pointing at a room row that is gone.
|
|
mu := r.lock(roomID)
|
|
mu.Lock()
|
|
defer mu.Unlock()
|
|
|
|
if err := r.store.PurgeRoom(ctx, roomID); err != nil {
|
|
return err
|
|
}
|
|
// The lock itself is dropped: a purged room ID will not come back, and
|
|
// keeping its mutex would make the map grow with every purge.
|
|
r.locks.Delete(roomID)
|
|
|
|
r.log.Warn("purged room", "room_id", roomID)
|
|
return nil
|
|
}
|
|
|
|
// Stats returns the aggregate room counts for the admin dashboard.
|
|
func (r *API) Stats(ctx context.Context) (storage.RoomStats, error) {
|
|
return r.store.RoomStats(ctx)
|
|
}
|