)]}'
{
  "commit": "777a239175c26fcaa4c6c2049fedc90e859bd9b6",
  "tree": "44434a56a0fc3f171dcda8bae32520375ee89c00",
  "parents": [
    "7540cc2ec0a5c29306ed852483f833c61eddf133"
  ],
  "author": {
    "name": "Steven Valdez",
    "email": "svaldez@google.com",
    "time": "Thu Feb 21 11:30:47 2019 -0500"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Tue Apr 23 19:16:23 2019 +0000"
  },
  "message": "Hold off flushing NewSessionTicket until write.\n\nIn TLS 1.3, if the client doesn\u0027t read from the server, the server might hang\nfrom a filled buffer while waiting for the client to read. Instead we avoid\nflushing the NewSessionTicket until there is a write from the server.\n\nUpdate-Note: This delays the flushing of the NewSessionTicket until the first\nwrite. Consumers may need to force an empty write to send the tickets if they\naren\u0027t writing any data to the client.\n\nChange-Id: Iec92043567e9a68c0a250533b7745eddeeae2341\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/34948\nCommit-Queue: Steven Valdez \u003csvaldez@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0ff1867103df310c4439217ef93b01de26f02078",
      "old_mode": 33188,
      "old_path": "ssl/ssl_test.cc",
      "new_id": "755510d4ddef0b081372f3ae9f6bf4cd3988204d",
      "new_mode": 33188,
      "new_path": "ssl/ssl_test.cc"
    },
    {
      "type": "modify",
      "old_id": "caaf0c7484cf21c60cc3addcdf9b120205193522",
      "old_mode": 33188,
      "old_path": "ssl/tls13_server.cc",
      "new_id": "13a89c0cf0983259e76942dd70a95dc74b7f38db",
      "new_mode": 33188,
      "new_path": "ssl/tls13_server.cc"
    }
  ]
}