Maurice e132d1529f fix(offline): a tab waits for the flush lock instead of skipping its flush ...

The cross-tab lock was taken with ifAvailable, so a tab that found another
tab replaying returned from flush() at once. Its callers read that as "the
queue is sent": the online trigger then re-seeds every trip from the server
and rehydrates the open ones, and the socket refetches after its pre-reconnect
flush. All tabs see the online event together, so the tabs that lost the race
laid the server's rows from before the replay over the shared Dexie, and over
the optimistic edits still on their way, while the winning tab was mid-flush.

The lock is now requested without ifAvailable. A tab that finds it held waits,
then runs its own pass, which finds nothing or what the holder left behind,
so flush() resolves only after the replay and the re-seed chained onto it
reads the state after it. The holder's requests are bounded by the client
timeout, so the wait is too.

2026-10-08 13:02:58 +02:00

..

environment

Feat/orm : mikroorm (#2416)

2026-10-06 19:27:30 +02:00

helpers

refactor(client): the stop rows move to RoadtripSidebarStopRows and share one badge row

2026-10-08 05:02:47 +00:00

integration

fix(client): the version notice asks about a change during the session only

2026-10-08 00:01:33 +00:00

unit

fix(offline): a tab waits for the flush lock instead of skipping its flush

2026-10-08 13:02:58 +02:00

setup.ts

fix(realtime): open no socket after a logout, and reconnect as soon as the network is back

2026-10-07 16:25:00 +02:00