From 7a81d338ba646250227aa69715fed0c1d4331597 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9F=AF=E7=91=8B=E5=AE=B8?= Date: Tue, 14 Jul 2026 02:43:25 +0800 Subject: [PATCH 1/3] Fix dashboard release selection, pin Plotly, support detected-event annotations - load_release_data picked releases_info[-1] as mostRecentRelease, but releases.json is ordered newest-first, so the oldest release (41.0.0) was pinned and the last week / last months time filters anchored to the wrong revision. Now select the release with the latest git_revision_timestamp among those present in the loaded data, falling back to releases_info[0]. - Pin the Plotly CDN script to 2.35.2 instead of plotly-latest, so a future Plotly major release cannot break the published dashboard. - Merge nightly/out/detected_events.json (written by the new regression detector) into the chart annotations: rendered orange dash-dot with their own 'Show detected changes' toggle, deduplicated by revision with hand-curated events.json taking precedence. A missing or corrupt file degrades to no detected annotations instead of failing the report. --- docs/index.html | 38 ++++++++++-- report.py | 151 +++++++++++++++++++++++++++++++++++++++++++++++- 2 files changed, 182 insertions(+), 7 deletions(-) diff --git a/docs/index.html b/docs/index.html index 36b95f1..1170b80 100644 --- a/docs/index.html +++ b/docs/index.html @@ -4,7 +4,7 @@ DataFusion ClickBench Performance Analysis - +