)]}'
{
  "commit": "c31628a3b8f02701bc4ac66adf86e4ec21ffa119",
  "tree": "843f40fc30566bb26cf601c5ed7bc79c2597a99e",
  "parents": [
    "228602ef47936e3ebd351a451f36a87e2275f1b7"
  ],
  "author": {
    "name": "nharper",
    "email": "nharper@google.com",
    "time": "Thu Feb 06 03:17:13 2020 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Feb 06 03:17:47 2020 -0800"
  },
  "message": "Fix connection close check in quic_client_interop_test_bin\n\nThe current connection close check only works if the server sends a\nconnection close in response to ours. The transport draft doesn\u0027t require\nthat a peer send a connection close in response to a connection close\n(though it is the only frame type that can be sent once a connection enters\nthe closing state). It seems perfectly reasonable to declare the connection\nclose procedure has completed with a zero error code if we send a\nconnection close with a zero error code.\n\ngfe-relnote: n/a (test-only tool change)\nPiperOrigin-RevId: 293557827\nChange-Id: I1fe90fd65703f061e7d920fb7f20380c0ed38162\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0ea2c7ce4d63a1ecaae090d0ef59e77bbb5a343c",
      "old_mode": 33188,
      "old_path": "quic/tools/quic_client_interop_test_bin.cc",
      "new_id": "e3abbd1b9136c5ad8feff8647362aa14f11d9087",
      "new_mode": 33188,
      "new_path": "quic/tools/quic_client_interop_test_bin.cc"
    }
  ]
}