binwiederhier 89cee1cd11 Keep a topic's rate visitor for as long as its subscriber is, not its key ...

Stale read the limiter key's last use, which every charged publish refreshes, so a topic kept
a vanished subscriber's limits (and its UnifiedPush subscription) for as long as anyone
published to it. The visitor now carries its own keepalive, set when it is built and by the
subscribe handlers' keepalive loops, like the shared visitor's seen was.

Also from the review: Prune returns and the manager logs the number of forgotten keys, the
unused visitorID wrapper goes, a stale comment and test name are updated, and the release
notes get the #1051 entry.

Claude-Session: https://claude.ai/code/session_01DeXuhSjq5Gta5qPJgSceFe

2026-10-29 03:21:37 +00:00

..

service_test.go

Merge branch 'limit-fixes' into visitor-per-request

2026-10-29 02:30:47 +00:00

service.go

Keep a topic's rate visitor for as long as its subscriber is, not its key

2026-10-29 03:21:37 +00:00

types_test.go

One field per line in multi-field struct literals

2026-10-28 21:35:06 +00:00

types.go

Build the visitor per request instead of sharing it

2026-10-29 01:28:12 +00:00

util_test.go

One limiter model in package limit, replacing the three limiter types in the visitor

2026-10-25 15:50:03 +00:00

util.go

One limiter model in package limit, replacing the three limiter types in the visitor

2026-10-25 15:50:03 +00:00