SynapCores v1.14.4 — Every one of these bugs passed its own health check
An operator wrote in with a query that was returning too much:
SELECT * FROM telemetry_events
WHERE received_at > '2026-08-18'
AND event_type = 'installation_created'
Forty rows came back. Ten were correct. No error, no warning — just a wider result set
than the query had asked for. And here is the part that made it genuinely nasty:
COUNT(*) over the identical WHERE clause returned 10. Adding ORDER BY also
returned 10. Only SELECT * was wrong.
That inconsistency is the whole shape of this release. Ten bugs, and not one of them produced a stack trace.
What was happening
The index-scan operator splits a WHERE clause into the conjuncts an index can answer
and the ones it cannot. On the index-hit path it looked up matching row ids, fetched
each row, and handed them to the caller — never evaluating the leftovers.
ORDER BY appeared to fix it because a sort makes the optimizer emit
TableScan → Filter instead, and Filter evaluates the whole conjunction. COUNT(*)
was right for the same reason. So every cross-check an engineer would reach for to
confirm the bug quietly disagreed with it.
Both fallback paths — index empty, index not yet populated — chained the predicates correctly and had been audited a release earlier. The success path never was. The failure mode of a correctness audit is that it stops at the first path that looks right.
Why the index fix ships in the same release
While reproducing that bug, a second one surfaced: CREATE INDEX never reached disk.
Index definitions lived in memory for the life of the process. Every restart discarded
them and silently reverted the instance to full table scans. Answers stayed correct —
a table scan answers the same question — so the only symptom was an index that quietly
stopped working, while CREATE INDEX kept reporting success and SHOW INDEXES never
listed secondary indexes at all.
Everything needed to recover already existed: a persistent catalog that writes definitions to disk, and a boot path that reads them back and rebuilds. It was a complete read path with no writer.
The two bugs are entangled. The residual-predicate bug only bites when an index is live in memory — so restarts kept wiping the evidence, which is why it was so hard to reproduce. Fixing durability makes the wrong-results bug more likely to fire. They had to ship together, and that is worth saying out loud rather than burying in a changelog.
The one that broke first-run
The installer wrote this into every gateway.toml:
[query]
default_timeout_ms = 30000
The engine's own default is 300000 — raised deliberately, years ago, because AI work
runs through the same query path as OLTP SQL. So an install that followed our documented
path got a stricter timeout than an install with no config file at all.
On a CPU-only host a cold GENERATE() takes about 53 seconds. Every LLM-backed
statement — GENERATE, AGENT_RUN, NL2SQL — failed with Operation timeout on a fresh
install. Our own SQL manual had been publishing default_timeout_ms = 300000 the entire
time. The installer contradicted our documentation, and only a canary that boots with
the documented operator config would ever have caught it.