)]}'
{
  "commit": "df852fac768772d640a088e95ce938eb6df34d0a",
  "tree": "664dcf7af4a16048f9b82160a7cf40d05cbd43de",
  "parents": [
    "78eb1576f9cf9d1fe97883eb25544a78f0e8f9bb"
  ],
  "author": {
    "name": "Aisha",
    "email": "87562264+aishasalim@users.noreply.github.com",
    "time": "Fri Aug 14 08:11:29 2026 -0500"
  },
  "committer": {
    "name": "Aisha",
    "email": "87562264+aishasalim@users.noreply.github.com",
    "time": "Fri Aug 14 08:11:29 2026 -0500"
  },
  "message": "kythe: Put stdout in binary mode on Windows\n\nThe Windows build failed the new --output_path test. Windows opens stdout\nin text mode, so it turns every \"\\n\" into \"\\r\\n\". The --output_path file is\nopened in binary mode, so the two outputs did not match byte for byte, and\nthe test compares them.\n\nSet stdout to binary mode, the same way verible-verilog-format and\nverible-verilog-obfuscate already do. Kythe facts are data, not text: the\nproto entries are binary, and the JSON modes have to produce the same bytes\non every platform.\n\nThis also repairs --print_kythe_facts\u003dproto to stdout on Windows, which\nwrote \"\\r\" bytes into the proto stream before this change.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f21fdf400b168371b18074993349d7b836706c2c",
      "old_mode": 33188,
      "old_path": "verible/verilog/tools/kythe/verilog-kythe-extractor.cc",
      "new_id": "321db49fa0011b5f47a7be4d2ffd63051dba24a9",
      "new_mode": 33188,
      "new_path": "verible/verilog/tools/kythe/verilog-kythe-extractor.cc"
    }
  ]
}