Offline queue: no way to group writes, so a multi-call action cannot be atomic #182
Labels
No labels
adr
android
area/calendar
area/design-system
area/i18n
area/jobs
area/offline
area/server
area/testing
bug
ci
duplicate
enhancement
help wanted
invalid
notifications
question
reliability
security
severity/low
severity/medium
tracking
web
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
eagraiclainne/app#182
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OpSpec(web/src/queue/registry.ts:20-34) describes one RPC per entry, drained FIFO, with idempotency classes for create and delete. There is no grouping, no transaction and no rollback.That is fine for every action shipped today, and it already carries a minted uid through a chained create. It is not enough for an action that is only correct as a set. The first one the jobs redesign needs is
Make it part of another job, which clears the repeat rule, clears the deadline and then moves the job. A partial flush strips a job of its date and its rule for nothing.Two ways out: a grouped-op primitive in the queue, where the entries flush together and fail together; or the affordance stays unavailable while offline. The second is cheap and honest, and it is what the design assumes until this lands.