)]}'
{
  "commit": "cc819ee19cadcf1653f827447ed3f02edbe70a55",
  "tree": "0aceb1eb0a409d2a00eed0026c702d5ef44f495d",
  "parents": [
    "81e0d62a2401a6d27afa5959ea88d7a93c39c73b"
  ],
  "author": {
    "name": "Sutou Kouhei",
    "email": "kou@clear-code.com",
    "time": "Mon Nov 16 20:59:38 2026 +0900"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Nov 16 20:59:38 2026 +0900"
  },
  "message": "Fix a bug that the server process may call kill(-1, SIGUSR1) (#229)\n\nCloses GH-228\n\n`kill(-1, ...)` sends the signal to all processes that the calling\nprocess has permission to send signals to. So tests were sometimes\nkilled by `SIGUSR1`.\n\nThe server process copies `session-\u003eexecutorPID` to\n`localSession-\u003epeerPID` when `session-\u003einitialized` is `true`. But\n`session-\u003eexecutorPID` was set only by the main process after\n`WaitForBackgroundWorkerStartup()`. If the executor process set\n`session-\u003einitialized \u003d true` before it, the server process copied\n`InvalidPid` (`-1`) and used it for `kill()`.\n\nThe executor process sets `session-\u003eexecutorPID` by itself before it\nsets `session-\u003einitialized \u003d true` with this change.\n\nThis also adds `Processor::signal_process()` that does nothing for\n`InvalidPid` and uses it for `kill()` calls that didn\u0027t check\n`InvalidPid`.\n\nCo-authored-by: Claude Fable 5.2 \u003cnoreply@anthropic.com\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "db83d8fcc3889ba0920e30b2528dd50224ed37d2",
      "old_mode": 33188,
      "old_path": "src/afs.cc",
      "new_id": "c2fd6718f66d4d76957d9b8fddab2d1569dce631",
      "new_mode": 33188,
      "new_path": "src/afs.cc"
    }
  ]
}
