Urgent.News

What's breaking now, across thousands of outlets.

Tech

All 23 of my line-number citations were wrong, and the coverage check could not notice

A table in my spec cited a source file by line number, 23 rows of it. Every one was off by one or two. The coverage check next to it had been green the whole time. The check was green because of how it counted: covered = total_rows - uncited_rows - vessel_rows = 24 - 23 - 1 = 0 uncovered # green Coverage was arithmetic. It counted how many rows carried a citation, never whether any citation…

The article discusses a critical flaw in a coverage check system that relied on line numbers for citations. The system incorrectly counted rows without verifying if the citations pointed to the correct location. This oversight resulted in undetected errors, as the coverage check only looked at the number of rows with citations, not whether the citations were valid.

The issue arose because line numbers could drift due to edits in other parts of the file, causing the citations to become inaccurate. The author highlights the need for a more robust system that uses unique identifiers rather than position-based references, allowing for accurate identification and handling of moved citations. This change would enable the system to produce actionable feedback when a citation is moved or a source changes, rather than merely counting the rows.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Prompt injection is a permissions problem

The moment you connect an AI assistant to your filesystem, the threat model changes in a way that most people set up the connection without noticing.

  • Prompt injection is a permissions issue
  • Model can be manipulated by document content
  • External layer needed to enforce permissions

Remote Chat Failover Needs a Tab-Stop Origin Banner, Not a Skeleton Overlay

I was halfway through a keyboard-only pass on a streaming chat when the local path died. A skeleton overlay covered the composer, my focus jumped, and tokens started arriving from somewhere else.

  • Remote chat failover needs clear origin label, not blank overlay
  • Author built chat shell with retry helper causing UI issues
  • Three mistakes: streaming flag, focus-stealing overlay, missing live region

More from Saturday 12 September →