)]}'
{
  "commit": "ad8140e0aa2ec41b37ea478b4525a423bcc21af9",
  "tree": "1ef834d6adb54bdf342f0a46b4f00403cf555fe7",
  "parents": [
    "23ee2efe81a3ff183b4eca46c42f749af7efca45"
  ],
  "author": {
    "name": "Nicholas S. Husin",
    "email": "nsh@golang.org",
    "time": "Fri May 08 01:00:52 2026 -0400"
  },
  "committer": {
    "name": "Nicholas Husin",
    "email": "nsh@golang.org",
    "time": "Fri May 08 19:22:15 2026 -0700"
  },
  "message": "quic: fix buffer slicing when handling overlapping stream data\n\nWhen processing a STREAM frame that overlaps with already received data,\nour slicing calculation is wrong. As a result, upon receiving duplicate\ndata, such as when packets are retransmitted, we end up writing the same\ndata multiple times rather than deduplicating them. This seems to have\nresulted in spurious FINAL_SIZE_ERROR in our tests.\n\nFor golang/go#78737\n\nChange-Id: I0c6d34d7f7f376310dad43983cbdf32b6a6a6964\nReviewed-on: https://go-review.googlesource.com/c/net/+/776080\nReviewed-by: Damien Neil \u003cdneil@google.com\u003e\nLUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com \u003cgolang-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\nReviewed-by: Nicholas Husin \u003chusin@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ee7c569459c579f5b3b25e3af77fed631703c22d",
      "old_mode": 33188,
      "old_path": "quic/stream.go",
      "new_id": "9d6ec46ad81710ee85538479a9f0667fa5d3a75e",
      "new_mode": 33188,
      "new_path": "quic/stream.go"
    },
    {
      "type": "modify",
      "old_id": "0a51f1dbcd02ff9abdb50ff185ad332d38491cd2",
      "old_mode": 33188,
      "old_path": "quic/stream_test.go",
      "new_id": "b626b6601343a75a1b8d9ae5cab001f4f1bae595",
      "new_mode": 33188,
      "new_path": "quic/stream_test.go"
    }
  ]
}
