)]}'
{
  "commit": "ebf55e4c2b39b3016a3c52e9a76c9c7be6954dcb",
  "tree": "c768f079555175ccf0720bb532a2a346bcee82c5",
  "parents": [
    "732ac38504efe2952f2471e0685546a749045499"
  ],
  "author": {
    "name": "dschinazi",
    "email": "dschinazi@google.com",
    "time": "Wed May 20 12:55:08 2020 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed May 20 12:55:51 2020 -0700"
  },
  "message": "Compute maximum transport parameter size upfront\n\nBefore this change, we used to pick 4096 as our transport parameter size, and hope it would fit. This CL looks at the contents of the transport parameters we are about to send, and programmatically computes the required size. This will ensure that we don\u0027t arbitrary fail in the presence of long custom transport parameters.\n\nThis CL also tweaks our logging code to truncate overly long custom parameters from the logs.\n\nEvery write call in this file will trigger a QUIC_BUG if we run out of space, therefore we are confident that this change will not impact existing behavior, and is therefore not flag-protected.\n\nRefactor, not flag protected.\n\nPiperOrigin-RevId: 312537871\nChange-Id: Ia8f2e6c7335f11133545c87173e6a2fc6552161a\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3e286adc84bcd1d975339758dbdc657eecbf3a57",
      "old_mode": 33188,
      "old_path": "quic/core/crypto/transport_parameters.cc",
      "new_id": "72e83a1f87ceda98150032e8cd79acd5a154bd20",
      "new_mode": 33188,
      "new_path": "quic/core/crypto/transport_parameters.cc"
    },
    {
      "type": "modify",
      "old_id": "1fc1f5c5c933fad5175ec10c9f9e18218080e0d4",
      "old_mode": 33188,
      "old_path": "quic/core/crypto/transport_parameters_test.cc",
      "new_id": "6b024117f84ef381e7efc1d1be8c341679a35449",
      "new_mode": 33188,
      "new_path": "quic/core/crypto/transport_parameters_test.cc"
    }
  ]
}