)]}'
{
  "commit": "49ccc1ddebb7654153b0498e9651d8b5d1b11c70",
  "tree": "56f9d25f739e7f217b43ae4bf345dd68f83b91da",
  "parents": [
    "85390ce88465e18c1c5d2f8d7f6ed21f3e8e8678"
  ],
  "author": {
    "name": "David Neil",
    "email": "dvd.neil1@gmail.com",
    "time": "Sun Feb 23 14:32:28 2025 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Feb 23 16:32:28 2025 -0500"
  },
  "message": "Do not mark cache generation as local (#1533)\n\nlocal\u003dTrue marks a repository rule to unconditionally re-execute anytime\nbazel re-evaluates the workspace (almost every invocation) It works well\nfor processes that execute in \u003c10ms, not large ones like the embuilder\ncache generation.\n\nI have tested this locally and it seems to work fine, but I\u0027ll be honest\nthat I don\u0027t understand the nuances of repository rules that well, nor\ndo I know much of anything about emscripten or the circumstances in\nwhich the cache ought to be rebuilt.\n\nI checked the `external/@emscripten_cache.marker` file that Bazel uses\nto store the cache key for if it needs to re-evaluate, and changing any\nof the options passed into register_emscripten_toolchains resulted in\nthe cache key changing, and it correctly resulted in the cache being\nregenerated.\n\nThe big question I don\u0027t have the context to answer: are there files on\ndisk other than these two that need to be watched for changes, so the\nrepository rule should change if they change:\n```\nFILE:@@emscripten_bin_linux//BUILD.bazel\nFILE:@@emsdk//emscripten_toolchain/default_config\n```",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ae71413dfdd9ea4096ecd98a4577cca22e084973",
      "old_mode": 33188,
      "old_path": "bazel/toolchains.bzl",
      "new_id": "caa1ba12676cf38d627fb7d681709902169bb720",
      "new_mode": 33188,
      "new_path": "bazel/toolchains.bzl"
    }
  ]
}