)]}'
{
  "commit": "d124996d2257ef9acf0b689dc1b189855006de8b",
  "tree": "22dfa2e92d568ddf04e5c443d4a7e51fa37cc7bc",
  "parents": [
    "5a3395a07659d202cc44d6276d5861fda2d59e14"
  ],
  "author": {
    "name": "Sergey Shevchenko",
    "email": "sergeygs@google.com",
    "time": "Tue Apr 09 18:48:17 2024"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Tue Apr 09 18:49:04 2024"
  },
  "message": "#Centipede Fix interaction between --stop_at / --stop_after / --config / --save_config\n\n`--stop_after` used to reset `--stop_at` in its `OnUpdate` handler. This created a usability problem: a command line\n\n```\ncentipede --stop_after\u003d6h --save_config\u003dcentipede.cfg\n```\n\nwould set both flags in centipede.cfg, not just `--stop_after`. The flags in centipede.cfg are alphabetically sorted, so in a subsequent run:\n\n```\ncentipede --config\u003dcentipede.cfg\n```\n\nthe value of `--stop_at` would win, resulting in a fixed termination time, possibly in the past.\n\nPiperOrigin-RevId: 623236580\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "576e57960bbb3814aae1240a2bfa5974b8ab3a60",
      "old_mode": 33188,
      "old_path": "centipede/environment_flags.cc",
      "new_id": "7e925a816a19420a57f2efa6f1d83b2585f98f1f",
      "new_mode": 33188,
      "new_path": "centipede/environment_flags.cc"
    }
  ]
}