)]}'
{
  "commit": "2b790ef78571cd58d29ce909a8d4e3f71cc4c47e",
  "tree": "8f4d0ae5e7ac53df906ea9571a1dcb42ca72a554",
  "parents": [
    "a0e3c40a0ed0cecc58c84e7684d9ce55a54044ee"
  ],
  "author": {
    "name": "chressie",
    "email": "chressie@golang.org",
    "time": "Tue Apr 29 08:43:26 2025"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Apr 29 08:43:26 2025"
  },
  "message": "glog: generate a Fatalf-like error message when writing to logsinks fails (#76)\n\nWriting to logsinks can fail (for example due to \"no space left on device\" or I/O errors). When that happens glog has no reasonable way to continue and causes the program to exit with exit status 2.\n\nPreviously glog reused the metadata of the current call to print an error message, but that was problematic. Depending on the current call\u0027s log severity it\u0027s possible that the program just exited without printing anything. That\u0027s confusing and hard to debug.\n\nTo fix that, glog creates now a new FATAL-level metadata object and prints a clearer error message (with stacks). In most situations this will at least be logged to stderr.\n\nThanks @atetubou for the initial fix!\n\ncl/750790337 (google-internal)\ncl/752634801 (google-internal)",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1b632e077cd48c6b2f043c4ff12b166e1ee65de4",
      "old_mode": 33188,
      "old_path": "glog.go",
      "new_id": "c8bebc3be02fbff0e6bde18b37d6c42af7bed2c5",
      "new_mode": 33188,
      "new_path": "glog.go"
    }
  ]
}