mattermost-mobile-upstream/docs
vish9812 13ef2cc5a1
make an incremental timeline event merge atomic and bound what it stores
Three problems in the merge added by the previous commit, found in review.

Applying an incremental update is a read-merge-write spanning several awaits, and
the handler is dispatched fire-and-forget, so two payloads for the same run could
both read the pre-commit event list and the later write would drop the earlier
one's event. A full run fetch is gated on lastFetchAt, so the loss was permanent
and the affected task's chip stayed wrong. Queue applications per run id. The
accompanying test fails without the queue, losing the first of two interleaved
events.

Only task_state_modified events are read, but the column stored the whole run
timeline — status updates, participant changes, property changes — in one JSON
blob rewritten on every incremental update and handed to every checklist row.
Drop unconsumed event types in the sanitizer so every write path is bounded, not
just this one.

Guard the delta and the delete list with Array.isArray. They come straight off
the wire, and a non-array would throw inside a handler nobody awaits, so the
failure would be silent.
2026-08-25 22:43:25 +05:30
..
database make an incremental timeline event merge atomic and bound what it stores 2026-08-25 22:43:25 +05:30
architecture-diagram.monopic include EMM/MDM integration in the arch diagram (#8327) 2024-11-16 06:53:36 +08:00
architecture-diagram.png include EMM/MDM integration in the arch diagram (#8327) 2024-11-16 06:53:36 +08:00
base_configs.md Barebones code for v2 2020-11-17 14:20:58 -03:00
testing_guide.md Add date/datetime field support with timezone features for Apps Forms (#9521) 2026-07-16 08:09:47 -06:00