SShortSingh.
Back to feed

Bulk comment cleanup deleted 51 load-bearing proof annotations across 12 workers

0
·62 views

A software project undertaking a bulk comment-removal effort deployed twelve parallel workers to strip over 1,900 comment blocks from source files and relocate them to an evidence ledger. All twelve workers passed a control check confirming every removed line was a comment, but the check did not verify whether any comments were actively consumed by other tools. Fifty-one removed lines were docstrings in proof files that a parser relied on to map theorems to stated requirements; without them, the requirement-coverage system reported failures even though the underlying proofs still compiled. The issue was caught one commit after the worker landed, when the docstring reader flagged orphaned requirement rows. Both affected files were fully restored, and the project now maintains a declared list of files whose comments are parsed by tools, excluding them from bulk removal by configuration rather than relying on individual worker caution.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Codeberg.org Reported Unreachable, Status Update Posted on Mastodon

Codeberg.org, a nonprofit code-hosting platform, was reported as unreachable by users on Hacker News. The reports link to a status update from the Codeberg status account on the Mastodon instance social.anoxinon.de. The linked source does not include details in the provided text about the cause or duration of the outage. The story gained traction on Hacker News with 58 points and 16 comments.

0
ProgrammingDEV Community ·

Čo je llms.txt a či ho váš web potrebuje

llms.txt je navrhovaný štandard, ide o jednoduchý textový súbor umiestnený v koreni webu, ktorý pomáha jazykovým modelom a AI agentom pochopiť, čím sa web zaoberá. Namiesto navigácie, skriptov a štýlov ponúka čistý prehľad v Markdowne so základným popisom, zoznamom dôležitých stránok a kontaktnými údajmi. Niektoré AI nástroje ho čítajú, no žiadny veľký vyhľadávač zatiaľ nepotvrdil, že ho využíva na hodnotenie stránok. Vytvorenie súboru je lacné a jednoduché, no nenahrádza kvalitný obsah ani SEO. Existenciu súboru možno overiť priamo v prehliadači alebo bezplatným skenom.

0
ProgrammingDEV Community ·

How OpenAI runs PostgreSQL for 800 million users without sharding

OpenAI serves ChatGPT from one PostgreSQL primary that handles all writes, supported by nearly 50 read replicas spread across regions. Rather than sharding its existing Postgres deployment, which would require changing hundreds of application endpoints, the company keeps load off the primary by routing reads to replicas and moving shardable, write-heavy workloads to systems like Azure Cosmos DB. It has also stopped adding new tables to this Postgres deployment and applies strict limits at every layer to prevent a single load spike from causing a wider outage. The article, drawing on OpenAI's January 2026 engineering post, describes how outages typically start with a sudden surge that triggers retries and cascading failures. Practical lessons include adding cache-miss locking, setting lock timeouts on migrations, and auditing write queries with pg_stat_statements.

0
ProgrammingDEV Community ·

Cuenta de pruebas conserva permisos de producción meses después del lanzamiento

Un equipo que probó una integración con una cuenta temporal recibió permisos amplios para consultar pedidos reales. Tras un lanzamiento exitoso, la cuenta siguió activa meses después, sin que nadie recordara quién custodiaba su clave ni qué proceso la usaba. El problema radica en que la fecha de retirada nunca se incluyó en el plan, de modo que desactivarla de golpe podría romper procesos y mantenerla deja un acceso sin responsable claro. El artículo propone registrar para cada acceso de prueba quién lo solicitó, qué permisos tiene, cuándo caduca y cómo verificar su retirada. Además, recomienda validar con permisos mínimos definitivos antes de cerrar el proyecto, ya que un despliegue no está completo mientras sus accesos temporales sigan siendo permanentes.