)]}'
{
  "commit": "41801b1b4b21778c52a93edf6612ea3870d8b711",
  "tree": "6940e499b28d3afb79a7dc029c64fc1583d673e3",
  "parents": [
    "ac027f3065b8dcdf268386040785a5dc759f79a9"
  ],
  "author": {
    "name": "ianswett",
    "email": "ianswett@google.com",
    "time": "Fri Nov 06 07:54:55 2026 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Fri Nov 06 07:55:31 2026 -0800"
  },
  "message": "Move PATH_CHALLENGE new-path handling from UpdatePacketContent into OnPathChallengeFrame.\n\nPreviously, QuicConnection::UpdatePacketContent special-cased PATH_CHALLENGE_FRAME to update alternative_path_ and set the member flag should_proactively_validate_peer_address_on_path_challenge_, which OnPathChallengeFrame then read after UpdatePacketContent returned.\n\nMove that block directly into OnPathChallengeFrame, immediately after the UpdatePacketContent call (preserving execution order), keep UpdatePacketContent focused on probing vs. non-probing frame classification and alternative path byte counting, and replace should_proactively_validate_peer_address_on_path_challenge_ with a local variable.\n\nPiperOrigin-RevId: 1015553094\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "18286b9938f7b766564daaa0b8ede1583551caf4",
      "old_mode": 33188,
      "old_path": "quiche/quic/core/quic_connection.cc",
      "new_id": "9ec9e433a5c4b61417a84a33544d42a9dcc49ffc",
      "new_mode": 33188,
      "new_path": "quiche/quic/core/quic_connection.cc"
    },
    {
      "type": "modify",
      "old_id": "a47fc7463d4bb749cfe0b0169758eab972a0760a",
      "old_mode": 33188,
      "old_path": "quiche/quic/core/quic_connection.h",
      "new_id": "ad1cdd3e10f4b9c5782a59624e57a03a0760860b",
      "new_mode": 33188,
      "new_path": "quiche/quic/core/quic_connection.h"
    }
  ]
}