orama

mirror of https://github.com/DeBrosOfficial/orama.git synced 2026-08-06 16:29:26 +00:00

History

anonpenguin23 2e44a22a3b fix(push): evict by id (recency), not rowid; retry token_fp backfill (#981 )

Live verification on anchat-test caught two real bugs the sqlite3 unit tests
missed:

1. Eviction ordered by SQLite rowid (insertion order) was WRONG: when an
   existing account RE-registers its token (a CONFLICT/UPDATE), its row keeps its
   original low rowid, so 'DELETE ... rowid < keeperRowid' evicted only
   older-inserted rows and missed newer-inserted stale duplicates. Observed live:
   11 accounts on one device token, 0 evictions fired. Fix: evict every OTHER
   same-token row in the namespace (id != keeperId) so the just-registered owner
   always wins — the ticket's 'one physical token -> one active owner'.
   Registrations for a token are serial (one device, one active account, one
   in-flight request; a retry CONFLICTs onto the same row), so the naive-delete
   concurrency concern that motivated rowid can't occur, and would self-heal.
   Adds a regression test seeding pre-existing duplicates + re-registering.

2. The token_fp backfill raced migration 033 at gateway startup ('no such
   column') and failed permanently. Retry until the migration applies.

2026-06-22 16:30:00 +03:00

credentials

feat(#72 ): full-privacy push — self-hosted ntfy + APNs-direct provider

2026-05-14 10:48:00 +03:00

providers

feat(push): collapse identifier (apns-collapse-id / Expo collapseId) from message_id (#833 )

2026-06-19 10:45:17 +03:00

config_store.go

feat(gateway): implement self-service tenant push notifications

2026-05-08 11:23:53 +03:00

device_store_rqlite.go

fix(push): evict by id (recency), not rowid; retry token_fp backfill (#981 )