Juan Fernando Castro 50bcdc9c6c fix: let a revocation be seen by the reads and the nodes that outlive it (#4151) ...

* fix: let a revocation be seen by the reads and the nodes that outlive it

Four places where a revoke lands on the primary and the next reader can
still be told the old answer.

The u2a cache key was dropped but not re-filled, so the next miss read a
replica that may still carry the row and cached it for the TTL -- and a
revoke's own settling pass is usually that miss. It re-fills from the
primary, as the u2u side already does.

A revoked session dropped its keys the same way. It now leaves the
revoked row in the cache, read from the primary, so there is nothing for
a lagging replica to re-introduce.

A link share is its own authority rather than an index over a
permission, so a replica still carrying a withdrawn row answers with it.
For a short window after one is withdrawn, those reads go to the
primary.

Socket eviction rode a local event, so it only reached the node that did
the revoking. It is announced on the fan-out channel too, which is where
the node actually holding the connection hears it.

* refactor: carry the revocation on outer.* instead of outer.pubsub.*

Eviction runs through `io.in(room).disconnectSockets()`, which goes via the
socket.io Redis adapter a cluster shares, so one node handling the event
disconnects that user on every node in it. Fanning out to siblings had each
of them repeat the same cluster-wide disconnect.

The adapter's Redis is per-cluster, so peer clusters still need the hop --
`outer.*` reaches them and skips the sibling fan-out. The local
`auth.sessions.revoked` goes with it: `outer.*` fires on the emitting node
too, and nothing else subscribed.

2026-10-09 16:36:26 -04:00

..

alarm

…

clickhouse

fix: list a link share only while the owner's plan covers it (#3891)

2026-09-16 14:42:52 -07:00

database

Sharing cleanup: bounded outbound listings, and what see does not reach (#4118)

2026-10-09 16:14:23 -04:00

dynamodb

feat(ddb): log the table and key of throttled DynamoDB requests (#4078)

2026-10-05 02:01:38 -07:00

email

fix: address code review on the teams cleanup

2026-10-06 16:22:48 -04:00

event

fix: let a revocation be seen by the reads and the nodes that outlive it (#4151)

2026-10-09 16:36:26 -04:00

events

fix: list a link share only while the owner's plan covers it (#3891)

2026-09-16 14:42:52 -07:00

prelude

…

redis

fix: list a link share only while the owner's plan covers it (#3891)

2026-09-16 14:42:52 -07:00

s3

…

index.ts

feat: background delivery seam, retries, and consent (PUT-1682) (#3684)

2026-09-03 01:39:06 -07:00

types.ts

fix: list a link share only while the owner's plan covers it (#3891)

2026-09-16 14:42:52 -07:00