Edition of Tuesday 10 November 2026

A Chromium Bug Caused by a 25-Hour Day

Comments on “A Chromium Bug Caused by a 25-Hour Day”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

A Chromium bug, traced to a code path that assumed every day lasts 24 hours, caused a scheduled metrics task to fire repeatedly on the 25-hour daylight saving "fall back" day in regions like Vancouver.

Read the original at ramsayleung.github.io. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 83 of 95 with a score of 0.56. The panel rated it highest on new information (0.79) and technical depth (0.73), lowest on significance (0.42). The judges disagreed most on audience breadth (spread 0.46), so the story is marked contested. Placed No. 83, where the score alone would also have put it: the 13th Programming & dev tools story of the day (−0.080). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Practical timezone/DST bug case study in Chromium with a clear explanation and reproducible logic; narrow audience, modest significance, and the closing fix is questioned rather than confirmed.
AI judgeJudge 3gpt-5.6-luna
A clear, technically grounded explanation of a real Chromium scheduling bug caused by DST/calendar-time confusion, including code, failure sequence, and fix. It is actionable for developers, though narrow and somewhat editorialized.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.56total under rubric v2.3Contestedjudges differ by 0.46 on audience breadth

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.42
  • Reader interest0.64
  • Audience breadth0.57
  • Practical relevance0.62
  • Substantiated0.64
  • Technical depth0.73
  • New information0.79
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.23

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.530.200.550.420.35+0.24+0.102
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.650.450.820.640.37+0.26+0.166
Audience breadthHow many people who build technology does it concern?0.760.300.660.570.46 , above the contested threshold+0.13+0.074
Practical relevanceHow useful is it to someone who builds software or tech products?0.700.450.720.620.27+0.22+0.137
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.550.600.780.640.23+0.05+0.032
Technical depthHow technically substantive is it?0.880.600.720.730.28+0.05+0.037
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.880.600.900.790.30+0.05+0.040
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.030.020.030.03−0.19−0.006
OverclaimDo the headline or conclusions claim more than the body supports?0.350.150.180.230.20−0.11−0.025
Sum of contributions+0.557
Claim-check penalty0.000
Total, as published0.557

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #83 on Rubric, 10 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-10/83/"><img src="https://rubric.hrih.si/badge/2026-11-10/83.svg" alt="Ranked #83 on Rubric, 10 Nov 2026" width="245" height="28"></a>

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “A Chromium Bug Caused by a 25-Hour Day”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.67

    Semver Trick