)]}'
{
  "commit": "11907853e6b1d728ff8f40f9aa9b0a4f975f54c7",
  "tree": "932c425ba7a854f878fb34fe884303a7019b7d6a",
  "parents": [
    "e3f2f7bd0dddec518b59fed97a3a6d48cbbd1f59"
  ],
  "author": {
    "name": "bnc",
    "email": "bnc@google.com",
    "time": "Fri Sep 20 05:26:08 2019 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Tue Sep 24 08:30:44 2019 -0700"
  },
  "message": "Use QuicTextUtils::HexDecode() in HttpDecoderTests.\n\nUsing the syntax std::string(\"\\x02\\x02\") for strings non containing 0-bytes and\nstd::string(\"\\x00\\x00\", 2) for strings containing 0-byte has pitfalls: it has\nhappened to me too many times that I added a 0-byte but forgot to add the\nexplicit length argument, or changed the length of the string but forgot to\nupdate the length argument, and wasted time investigating why the results are\nnot what I expected.  HexDecode() should eliminate this difficulty entirely.\n\nThis happened most recently while working on https://crbug.com/1001823, but with\nall the activity around PRIORITY frame I expect we\u0027ll spend more time adding\nHttpDecoderTests in the future.\n\ngfe-relnote: n/a, test-only change.\nPiperOrigin-RevId: 270248919\nChange-Id: I8675befae7e8c22ae26871ff2ed9df6ac686c31d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0323319d3b595cc92f21d590c245966e9ee930f9",
      "old_mode": 33188,
      "old_path": "quic/core/http/http_decoder_test.cc",
      "new_id": "6847ecbf82b6975c288e8ed6b75f4d8a28f9a67b",
      "new_mode": 33188,
      "new_path": "quic/core/http/http_decoder_test.cc"
    }
  ]
}