Guilhem LemouelandClaude Opus 5 d964dfe7f6 fix(backend): say what is missing when a $res: or $var: reference does not resolve ...

Both interpolations fetched with fetch_one and mapped the error through to_anyhow, so a
reference to something deleted surfaced as "no rows returned by a query that expected to
return at least one row @workspaces.rs:2169". It names neither the kind of thing that was
missing nor its path, and it is what a data table pointing at a deleted resource reports.

They now fetch_optional and return NotFound naming the path, and datatable resolution adds
the data table on the way out: the caller asked for one by name, and a bare "resource
f/x/y does not exist" leaves them to work out which of them points at it. The health probe
is new, so this string had only just become something users read.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-11 13:36:39 +02:00

..

examples

fix: enrich OTEL log records with per-request LogContext (#8812)

2026-04-13 21:50:50 +00:00

src

fix(backend): say what is missing when a $res: or $var: reference does not resolve

2026-08-11 13:36:39 +02:00

tests

feat: give dbt its own editor with an explicitly refreshed model graph (#10448)

2026-08-03 03:32:08 +02:00

Cargo.toml

fix: datatable full schema hangs behind a transaction-pooling postgres proxy (#10352)

2026-07-27 12:32:44 +02:00