)]}'
{
  "commit": "3e1696be3d2503d96dcaa3391d57e8ee72750915",
  "tree": "15c61225b9eaeddf90fd03dae47b545ec7e26e0f",
  "parents": [
    "71ae0b300e19fb954e739ac179681110598399d2"
  ],
  "author": {
    "name": "Dirk Pranke",
    "email": "dpranke@chromium.org",
    "time": "Thu Jul 04 19:08:17 2019 -0700"
  },
  "committer": {
    "name": "Dirk Pranke",
    "email": "dpranke@chromium.org",
    "time": "Thu Jul 04 19:08:17 2019 -0700"
  },
  "message": "Fix bad error reporting on partial matches.\n\nThis patch addresses an error reported in\nhttps://github.com/dpranke/pyjson5/issues/26, where calling\n`json.loads(\u0027[ ,]\u0027) would report an error on column 4, not column 3.\n\nThe reason for this had to do with the way the optional whitespace (sp*)\nrule was coded in the grammar, and a bug in the underlying parser generator\n(glop), where if you had a rule like (a ?())* and you matched a and not b,\nthe errposition wouldn\u0027t be properly rolled back before the conditional\nexpression. That bug was fixed in glop v0.6.2; this CL regenerates the\nJSON5 parser with that version of the parser generator, and then adds\njson5-specific tests to check for the correct position reporting.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f5db6592a3f6d40d24c733f5741fd7ede71b5e3d",
      "old_mode": 33188,
      "old_path": "json5/parser.py",
      "new_id": "a2a0039c4bf9c2764e244e03bd07a1efab5efd60",
      "new_mode": 33188,
      "new_path": "json5/parser.py"
    },
    {
      "type": "modify",
      "old_id": "9fc59fa9dcc2fcef89aba58ec3c189ac8fabe43c",
      "old_mode": 33188,
      "old_path": "tests/lib_test.py",
      "new_id": "e981919d77b0ba0efeb3236360f43db9e5d12ff0",
      "new_mode": 33188,
      "new_path": "tests/lib_test.py"
    }
  ]
}