Maurice 39c8a22352 fix(offline): replay queued writes an interrupted flush left behind ...

A flush marks each row 'syncing' before it sends, and only ever picks up
rows that are 'pending'. Kill the tab mid-request - the OS evicting a PWA
does exactly this - and the row stays 'syncing' forever: it keeps counting
towards the pending badge, but nothing ever retries it, fails it or shows
it as a conflict. Anything queued behind it that depends on it later fails
with 'unresolved temp id'.

Stamp the row when it goes in flight and reclaim it on the next flush. The
axios instance times out at 8s, so a minute is well past anything that
could still be running, and the mutation id doubles as the idempotency key,
so replaying a write the server already applied is answered from its cache.

2026-08-23 11:59:12 +02:00

..

environment

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00

helpers

fix(planner): let a route choice survive the map, and keep new items on their day

2026-08-21 13:27:27 +02:00

integration

feat(dayplan): choose the travel mode per segment (#1281) (#1651)

2026-07-21 23:36:53 +02:00

unit

fix(offline): replay queued writes an interrupted flush left behind

2026-08-23 11:59:12 +02:00

setup.ts

test: give async assertions a realistic budget on CI

2026-07-29 11:55:31 +02:00