)]}'
{
  "commit": "0dbe72730e67268e1312b4716049704871664d74",
  "tree": "2710199935edfa4138fe1601c000de27815973b5",
  "parents": [
    "01408281e0d4541113cd8c15185d70f30c773b36"
  ],
  "author": {
    "name": "ricea",
    "email": "ricea@google.com",
    "time": "Mon Aug 24 09:29:59 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Aug 24 09:31:55 2026 -0700"
  },
  "message": "Remove QUIC_BUG in when max_datagram_size is 0\n\nIt appears to be possible for a WebTransport server to legitimately create a situation where datagrams are enabled but the max datagram size is 0. See the test `ZeroQuicDatagramLimitReturnsZeroMaxDatagramSize` in https://chromium-review.googlesource.com/c/chromium/src/+/8252325/8/net/quic/dedicated_web_transport_http3_client_test.cc\n\nThat CL contains a Chromium-side workaround to avoid hitting the `QUIC_BUG()`, but it shouldn\u0027t be necessary to work around it in Chromium.\n\nRemove the `QUIC_BUG()` in QUICHE instead.\n\nThis code is not used in the GFE.\n\nPiperOrigin-RevId: 969901058\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "245d6ca1642d424c2e601c95120e1aa8e7b51e68",
      "old_mode": 33188,
      "old_path": "quiche/quic/core/http/quic_spdy_stream.cc",
      "new_id": "90ae1c2c0bb3467fddfb0d1f6171b74c7e06577c",
      "new_mode": 33188,
      "new_path": "quiche/quic/core/http/quic_spdy_stream.cc"
    }
  ]
}