)]}'
{
  "commit": "40196fb0fa1daa4a145ed3573e6381a0ea66a060",
  "tree": "ad791b27300774d3fc0ad98dfe264002e2a3094f",
  "parents": [
    "da4295ad1dd83a62bf4acadeec58da06852b19b2"
  ],
  "author": {
    "name": "Sebastian Ullrich",
    "email": "sebasti@nullri.ch",
    "time": "Sun Nov 08 01:27:44 2026 +0000"
  },
  "committer": {
    "name": "Sebastian Ullrich",
    "email": "sebasti@nullri.ch",
    "time": "Sun Nov 08 01:27:44 2026 +0000"
  },
  "message": "fix: report allocation failure when loading an `.olean` after `mmap` fails\n\nWhen mapping an `.olean` fails, `lean_compacted_region_read` falls back to `malloc` but never checked its result, so hitting the memory mapping limit surfaced as a generic \"failed to read file\" error. Now a failed `malloc` reports the size and the `mmap` error, and on Linux an `ENOMEM` from `mmap` points at `vm.max_map_count`. Read failures also include `strerror`.\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e86b9f199ada6b8365530f67782c296274358798",
      "old_mode": 33188,
      "old_path": "src/library/module.cpp",
      "new_id": "3bc0dde6f1adcb367fcc9ea2c2e8880fdeed9c91",
      "new_mode": 33188,
      "new_path": "src/library/module.cpp"
    }
  ]
}
