… message

thread: #7672 (comment)

…letion

Adopts the native "dict" type available since Python 3.9.

thread: #7672 (comment)

…of event handlers

thread: #7672 (comment)

…potence

Most applications return the original result for subsequent calls to an
idempotent operation.  In our case, we just have to indicate that we've
already processed the event, since (a) the client already knows the
expected result of the operation and can apply it locally, and (b) in
the event of any conflict or drift it should catch up to the server
within the same (or at worst one additional) sync period.

…s-journalist collisions/leakage

Journalists are trusted users, but there's no reason to allow either
collisions or leakage in a global Event.id namespace (as opposed to
global ordering).

thread: #7672 (comment)

The original comment came verbatim from journalist_app.utils.

Co-authored-by: Kunal Mehta <[email protected]>

thread: #7672 (comment)

…ric ValueError

thread: #7672 (comment)

Co-authored-by: Kunal Mehta <[email protected]>

This lets us (a) guarantee we have an Event.id to order on, (b) narrow
EventHandler.process() to take only Event objects instead of
dictionaries, and (c) short-circuit all processing if any event is
invalid.

thread: #7672 (comment)

…nt races as well as enforce idempotence

thread: #7672 (comment)

As a side effect, processing of the entire BatchRequest short-circuits
on any failure of validation, not just deserialization.

thread: #7672 (comment)

…tion

The tests.utils.ascii_armor() helper function is courtesy of ChatGPT.

`/api/v2/data`: handle batched events from clients