)]}'
{
  "commit": "114cebdacb57c71c3c22cd559d4465fb766fbf23",
  "tree": "d00923fcecb560c78d1d583e5f0473ea09c14020",
  "parents": [
    "b52cbd2466bc1cc4d3f00d33dcac74a4372f9469"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Fri Nov 01 20:59:54 2024 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Nov 12 16:21:36 2024 +0000"
  },
  "message": "runner: ACK flights in DTLS 1.3 by default\n\nTests can override this behavior if they want. This required fixing up\nsome logic around tracking lastRecordInFlight. We implicitly assumed\nthat, by the time we\u0027re ready to write, there\u0027s nothing more to read in\nthe current record. But BoringSSL currently sends a single record with\ntwo NewSessionTickets in it, even though they\u0027re nominally two flights.\n\nInstead, only wipe the state if the packet is empty. There\u0027s probably a\nbetter way to process this, but this will do.\n\nBug: 42290594\nChange-Id: Ib22d575777eb6866dbc02b9ba3b74e8d61a74b6c\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72847\nReviewed-by: Nick Harper \u003cnharper@chromium.org\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cef30912f9f422908183ae3abb74938e45ec8c30",
      "old_mode": 33188,
      "old_path": "ssl/test/runner/conn.go",
      "new_id": "7f6ea6496990b07a5a027f53c26014cffe55f967",
      "new_mode": 33188,
      "new_path": "ssl/test/runner/conn.go"
    },
    {
      "type": "modify",
      "old_id": "f360e3812a0002e8076b7d0ca6f6b372b4d154d9",
      "old_mode": 33188,
      "old_path": "ssl/test/runner/dtls.go",
      "new_id": "e2c4871476bfa21de4f828cef23335231896c967",
      "new_mode": 33188,
      "new_path": "ssl/test/runner/dtls.go"
    }
  ]
}