{
  "id": 20891459,
  "title": "The count that refused to say zero",
  "url": "https://urgent.news/2026/11/20/the-count-that-refused-to-say-zero",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-20T11:29:51.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ilya_mozerov_867dbdd91feb/the-count-that-refused-to-say-zero-m8h"
  },
  "original_language": "en",
  "account": "A delivery report tracks how often a new build goes live while a worker is still pointing at the old one. This number is crucial: if it rises, the delivery mechanism must be rolled back. However, two bugs caused the number to be inaccurate, hiding failures that occurred and inventing a zero that hadn't been measured. When a promotion fails due to a worker on the wrong build, the system attempts a rollback and checks if it worked. The check has two results: success, labeled as \"rolled back,\" and failure, remaining \"UNKNOWN\" as the rollback's success cannot be guaranteed. The old report tracked only the first outcome, and this oversight needed correction. The revised report counts by cause, making both phases of the same cause visible, such as two wrong-pin failures in a recent 72-hour window, one rolled back cleanly and one with an UNKNOWN phase. This approach ensured that even if a failure is unknown, it's still counted. The report also identifies unreadable records separately, printing the window total as \"UNKNOWN\" accompanied by the count of unreadable records. Additionally, the system must not erase readable data when declaring the total UNKNOWN. The fix includes tests that confirm this behavior, including cases with malformed record shapes and mixed results. The rule is to count by cause when the decision is about a cause, ensuring honesty about incomplete totals.",
  "summary": "A delivery report counts the times a new build became live while a worker was still pointing at the old build. That number matters: a rising count is the trigger to roll the delivery mechanism back. Two separate bugs made the number lie in opposite directions. One hid failures that had happened. The other invented a zero that had not been measured. Counting the outcome instead of the cause When a…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}