)]}'
{
  "commit": "442e2a007406f2bb161e9b589079a665ec8fb10a",
  "tree": "68238298c350aeb5c638b1dad2a2783abde6596c",
  "parents": [
    "f916dbc5b9b50863d3247619070590b1573005ed"
  ],
  "author": {
    "name": "Mike Frysinger",
    "email": "vapier@chromium.org",
    "time": "Tue Jul 14 10:25:54 2026"
  },
  "committer": {
    "name": "Mike Frysinger",
    "email": "vapier@chromium.org",
    "time": "Fri Jul 24 21:06:38 2026"
  },
  "message": "libdot: test: fix chai test detection\n\nBoth lib.assert \u0026 nassh/js/nasftp_cli.js use chai in the global namespace\nto detect whether we\u0027re running unittests or production code.  This broke\na year ago when we upgraded to chai v5 which switched from global imports\nto ES6 modules.  The nasftp code wasn\u0027t logging as verbosely during tests\n(which isn\u0027t a big deal), and all of our libdot-based asserts were skipped\nduring tests.  The latter is not good, but since we haven\u0027t broken any of\nthe tests, it\u0027s OK to re-enable so the asserts actually assert.\n\nChange-Id: I0ddb5d3d14c3d5bbd8ee455911e9d321a249d541\nReviewed-on: https://chromium-review.googlesource.com/c/apps/libapps/+/8086814\nTested-by: kokoro \u003cnoreply+kokoro@google.com\u003e\nReviewed-by: Joel Hockey \u003cjoelhockey@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d278d90b4d89248645023ed0627982f2717554d8",
      "old_mode": 33188,
      "old_path": "libdot/js/lib_test_util.js",
      "new_id": "91dc165ce515189bf6eb384fabfe2ad0183ff86d",
      "new_mode": 33188,
      "new_path": "libdot/js/lib_test_util.js"
    }
  ]
}