)]}'
{
  "commit": "1af892192c15bf23dc8946547c4326ff5397027d",
  "tree": "21d6d9fd162b48e7c9461ed9cc9ae20356157d10",
  "parents": [
    "8b43ff0f72137b31b23d482f0b2344186d797b03"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Jul 09 23:58:32 2026 -0400"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Mon Jul 13 06:09:46 2026 -0700"
  },
  "message": "Use the error queue a bit more consistently in CBB functions\n\nWe missed a few spots in\nhttps://boringssl-review.googlesource.com/c/boringssl/+/57046. In\ngeneral, it\u0027s troublesome when functions inconsistently use the error\nqueue. A function should either always write to the error queue on\nerror, or never do it. CBB (and really anything that calls\nOPENSSL_malloc) has since morphed into using it, but we missed a few\ncases.\n\nChange-Id: Ifedf7cbf7a77a8048380c3beb7d6defb5628dbfa\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/98727\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nPresubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com \u003cboringssl-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\nCommit-Queue: Lily Chen \u003cchlily@google.com\u003e\nReviewed-by: Lily Chen \u003cchlily@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1809e65537fc665e1dbc934a007e91c1d9ce3867",
      "old_mode": 33188,
      "old_path": "crypto/bytestring/cbb.cc",
      "new_id": "f8d1b5ccc6aeecb333463d9c91784095adc664f9",
      "new_mode": 33188,
      "new_path": "crypto/bytestring/cbb.cc"
    }
  ]
}