Tailscale Traces Database Corruption to 16y/o SQLite WAL-Reset Bug

Aug 12, 2026 · 2:22 PM UTC ·12 min read · 0 reactions · 0 comments · 6 views

#tailscale #traces #database #corruption #sqlite

TL;DR · WeSearch summary

Sorted.","author":[{"@type":"Person","name":"Alex Chan"}],"articleBody":null}Blog|insightsAugust 12, 2026How we tracked down a 16-year-old SQLite bugAt the end of last year, our uptime was pretty shaky. You can see this trend on our status page, and that instability continued into the new year. Many of these outages were caused by a single bug, deep in SQLite.

Key facts

▪Sorted.","author":[{"@type":"Person","name":"Alex Chan"}],"articleBody":null}Blog|insightsAugust 12, 2026How we tracked down a 16-year-old SQLite bugAt the end of last year, our uptime was pretty shaky.
▪You can see this trend on our status page, and that instability continued into the new year.
▪Many of these outages were caused by a single bug, deep in SQLite.

About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,479 of its stories. Top-voted stories on Hacker News.

All Hacker News (Front Page) coverage →

Original article

Tailscale

Read full at Tailscale →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Tailscale
Canonical URL	https://tailscale.com/blog/sqlite-wal-reset-bug
Publication time	Wed, 12 Aug 2026 14:22:30 +0000
Retrieval time	2026-08-12T15:01:37.437Z
Last seen	2026-08-12T15:01:37.437Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	ZiL1vhS7UJHZ · 1 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

{"@context":"https://schema.org","@type":"BlogPosting","image":"https://cdn.sanity.io/images/w77i7m8x/production/6ca0577c6bb689a7af13ec1407ebc8afd2de8136-4608x2372.png","url":"https://tailscale.com/blog/sqlite-wal-reset-bug","headline":"How we tracked down a 16-year-old SQLite bug","datePublished":"2026-08-12T14:00:00.000Z","description":"SQLite corruption? Sorted.","abstract":"SQLite corruption? Sorted.","author":[{"@type":"Person","name":"Alex Chan"}],"articleBody":null}Blog|insightsAugust 12, 2026How we tracked down a 16-year-old SQLite bugAt the end of last year, our uptime was pretty shaky. You can see this trend on our status page, and that instability continued into the new year. Many of these outages were caused by a single bug, deep in SQLite.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Tailscale.

Anonymous · no account needed

Discussion

0 comments