tree ee0d0420f53aed79197f35491bc5e72a7d61d0c1
parent 2a64fff55720780c1702d1013be2a80575d80aa7
author Serge Bazanski <serge@monogon.tech> 1656073359 +0200
committer Sergiusz Bazanski <serge@monogon.tech> 1656411971 +0000

m/p/event/etcd: better handle update coalescing

I wasn't able to replicate this in a test, but sometimes etcd sends
multiple events relating to the same key within a single entry in the
watch channel. I assume this happens when the etcd watcher client is not
reading from the server fast enough.

Anyway, when that happened, we'd get a panic about duplicate keys in a
non-ranged call because of a logic bug in the entry coalescing (in which
we would not coalesce multiple updates to the same key, just updates
with the same key and value). Now we coalesce these too, and the bug
seems to be gone.

Change-Id: I36234cc1104ec96a38ad1566b9df75532df44bba
Reviewed-on: https://review.monogon.dev/c/monogon/+/800
Tested-by: Jenkins CI
Reviewed-by: Leopold Schabel <leo@monogon.tech>