)]}'
{
  "commit": "f76d643702a30fbffecdfe50831e11881c96ceb3",
  "tree": "2088aeed7dbfcaf7b8a79f3db396c4dc82d9a25c",
  "parents": [
    "3ec0642a7fb6488f65b06f9040adc67e3990296a"
  ],
  "author": {
    "name": "Aaron Lehmann",
    "email": "aaron.lehmann@docker.com",
    "time": "Wed Sep 28 11:55:00 2016 +0100"
  },
  "committer": {
    "name": "Aaron Lehmann",
    "email": "aaron.lehmann@docker.com",
    "time": "Wed Sep 28 13:48:28 2016 +0100"
  },
  "message": "Fix formatting of wrapped errors when colors are used\n\nThere are two different code paths for rendering a key/value pair. The\nnon-color version uses a type switch that handles specific types such as\n\"error\", and the color version uses the %+v printf format specifier.\nThis causes an inconsistency between the two formats. In particular,\nerrors created using the github.com/pkg/errors package will include a\nstack trace of where the error was created when printed to the terminal,\nbut not to a file. Printing the stack trace as part of the log field is\nprobably not the right behavior.\n\nThe output is also inconsistent between the two forms because strings\nare not quoted/escaped when colors are used. This can make log output\nunparseable.\n\nFix this by making both code paths use the type switch and escaping\nrules. Fix the escaping code to pass the error value to Fprintf, not the\nerror itself, which seems to be necessary to avoid blank output with\nerrors created by github.com/pkg/errors.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cce61f2a0e58583446bf408589abd41fb1f0988e",
      "old_mode": 33188,
      "old_path": "text_formatter.go",
      "new_id": "9114b3ca478a8a246f9fe1e92f9a70d031300fab",
      "new_mode": 33188,
      "new_path": "text_formatter.go"
    }
  ]
}