)]}'
{
  "commit": "90315e8698e0d2290a8a0fdfe96318ebb1a210a7",
  "tree": "70a07547ebcc2ebe7533acb11932ed6381e800f3",
  "parents": [
    "7c0ef5f55e38c17cb5d181f8ca74e2925602c78c"
  ],
  "author": {
    "name": "danzh",
    "email": "danzh@google.com",
    "time": "Thu Jun 08 14:09:49 2023 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Jun 08 14:10:36 2023 -0700"
  },
  "message": "When a QUIC client probes from a new socket via a new writer or respond to peer\u0027s probing on a new socket, check if the socket is write blocked.\n\nCurrently QuicConnetion blindly write packets to the new socket, and let the platform to decide how to handle socket blockage case. It is okay if the platform silently drop the probing packet in this case. But Chrome added CHECKs to disallow QUIC to write to socket which is already blocked: https://bugs.chromium.org/p/chromium/issues/detail?id\u003d1376754#c10. So this change is to address the CHECK violation there and unblock their further debugging on the original issue.\n\nPiperOrigin-RevId: 538886916\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f22f9b0e0ae23a458fc816fe89a7d8273b887f20",
      "old_mode": 33188,
      "old_path": "quiche/quic/core/quic_connection.cc",
      "new_id": "80945f6df9a942aaa1a86d73dfad151282d7762b",
      "new_mode": 33188,
      "new_path": "quiche/quic/core/quic_connection.cc"
    },
    {
      "type": "modify",
      "old_id": "a26731f18d52b35a384d3f1d09e70f9a9a6f4068",
      "old_mode": 33188,
      "old_path": "quiche/quic/core/quic_connection_test.cc",
      "new_id": "0d48535f9458e4227b7a1d6bf43a292f42ae0392",
      "new_mode": 33188,
      "new_path": "quiche/quic/core/quic_connection_test.cc"
    }
  ]
}