)]}'
{
  "commit": "cee470942402d608b42971a1671827fb798eda4f",
  "tree": "b002e6045f3a9754204c2777c7401f26d9d9ea2d",
  "parents": [
    "0206e17accc6c5ef1f070e61727f3825dc9a645a"
  ],
  "author": {
    "name": "Primiano Tucci",
    "email": "primiano@google.com",
    "time": "Thu May 21 20:34:21 2026 +0100"
  },
  "committer": {
    "name": "Primiano Tucci",
    "email": "primiano@google.com",
    "time": "Thu May 21 20:34:21 2026 +0100"
  },
  "message": "ui: avoid negative-duration visible window from reliable-range zoom\n\nWhen the \"Enable Chrome reliable range zoom\" experimental flag is on,\ncomputeVisibleTime() moved visibleStart forward to the Chrome reliable\nrange start without checking that it stays \u003c\u003d visibleEnd. On traces\nwhere chrome_reliable_range reports a start at (or past) the visible\nwindow end - e.g. because a process is missing data and the metric\nreturns trace_end - the resulting TimeSpan asserted with:\n\n  Span start [...] cannot be greater than end [...]\n\nand the UI failed to load the trace.\n\nMirror the safety check already done in the metadata block: only apply\nthe reliable-range adjustment when it would leave a non-empty window.\nThe ftrace adjustment that runs afterwards already clamps to\nvisibleEnd, so this is the last unguarded path.\n\nRepro trace: chrome_reliable_range.start \u003d\u003d trace_bounds.end_ts,\nftrace_event empty, flag enabled -\u003e crash on load.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b3f8cf8b582de8cdfb79307ac50b43b9ea310eb1",
      "old_mode": 33188,
      "old_path": "ui/src/core/load_trace.ts",
      "new_id": "8079efb1de78f6b49792005cbffb4f9a91edb1e1",
      "new_mode": 33188,
      "new_path": "ui/src/core/load_trace.ts"
    }
  ]
}