)]}'
{
  "commit": "bbb873d19c7b0b981c6d00e78c1d25544835b500",
  "tree": "ee0d0420f53aed79197f35491bc5e72a7d61d0c1",
  "parents": [
    "2a64fff55720780c1702d1013be2a80575d80aa7"
  ],
  "author": {
    "name": "Serge Bazanski",
    "email": "serge@monogon.tech",
    "time": "Fri Jun 24 14:22:39 2022 +0200"
  },
  "committer": {
    "name": "Sergiusz Bazanski",
    "email": "serge@monogon.tech",
    "time": "Tue Jun 28 10:26:11 2022 +0000"
  },
  "message": "m/p/event/etcd: better handle update coalescing\n\nI wasn\u0027t able to replicate this in a test, but sometimes etcd sends\nmultiple events relating to the same key within a single entry in the\nwatch channel. I assume this happens when the etcd watcher client is not\nreading from the server fast enough.\n\nAnyway, when that happened, we\u0027d get a panic about duplicate keys in a\nnon-ranged call because of a logic bug in the entry coalescing (in which\nwe would not coalesce multiple updates to the same key, just updates\nwith the same key and value). Now we coalesce these too, and the bug\nseems to be gone.\n\nChange-Id: I36234cc1104ec96a38ad1566b9df75532df44bba\nReviewed-on: https://review.monogon.dev/c/monogon/+/800\nTested-by: Jenkins CI\nReviewed-by: Leopold Schabel \u003cleo@monogon.tech\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0f7f453cc3ffc1c7b5f1dbfc20bb7eac1a48dc67",
      "old_mode": 33188,
      "old_path": "metropolis/pkg/event/etcd/etcd.go",
      "new_id": "d49a5929580e138081be14676f4598ff4445a263",
      "new_mode": 33188,
      "new_path": "metropolis/pkg/event/etcd/etcd.go"
    },
    {
      "type": "modify",
      "old_id": "2f5e283ac96e25a33059cc5ae79b34818e10d192",
      "old_mode": 33188,
      "old_path": "metropolis/pkg/event/etcd/etcd_test.go",
      "new_id": "13f6ea87f9e9e8d02fdbebede14e82a03cdc128b",
      "new_mode": 33188,
      "new_path": "metropolis/pkg/event/etcd/etcd_test.go"
    }
  ]
}