)]}'
{
  "commit": "d5ee8b074530f291e1173f8e79f7fcdb4d972cc5",
  "tree": "3c50665241a44ec5ff806deffeed512760a31f4b",
  "parents": [
    "68ffcf060d8ab341ad5d7e6e3eef0a3961073ab0"
  ],
  "author": {
    "name": "Keegan Carruthers-Smith",
    "email": "keegan.csmith@gmail.com",
    "time": "Wed May 26 16:43:26 2021 +0200"
  },
  "committer": {
    "name": "Keegan Carruthers-Smith",
    "email": "keegan.csmith@gmail.com",
    "time": "Tue Jul 13 10:59:34 2021 +0200"
  },
  "message": "index: read in ngrams in own function\n\nOur heap profiles are dominated by readIndexData. By moving some of the\nwork into its own functions, the heap profiles will tell us where in\nparticular data is allocated from. We suspect most data is from\nreadNgrams, but want to confirm emperically.\n\nCo-authored-by: Stefan Hengl \u003cstefan@sourcegraph.com\u003e\nChange-Id: I85cb05f27ac2c2d9135c816173a8a97cea6a706b\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f8d07ab4d8c07f083b51fa4f0857959e627b6a37",
      "old_mode": 33188,
      "old_path": "read.go",
      "new_id": "ec54223f4d9c2a8b75d9b0f9ca76ecddd7bb96dd",
      "new_mode": 33188,
      "new_path": "read.go"
    }
  ]
}