Ruben FiszelandClaude Opus 5 8ca5837dcc fix: report a warehouse-lookup failure as the failure it is, and correct the boundary ...

`dbt_warehouse_exists` fails three ways — no such warehouse, the query itself,
and a setting with no `resource_path` — and all three became a 400 blaming the
user's warehouse name. A pool timeout mid-deploy told a retrying sync that a
transient server error was a permanent client one. Only `NotFound` is the
annotation's fault now.

The known-boundary paragraph claimed a flow-runner run still cascades. It does
not: it is routed by `flow_step_id`, which `is_eligible_kind` rejects, as
`asset_trigger_dispatch.rs` pins. Recording and cascading are decided separately,
so the paragraph now names all three routes rather than merging two of them — and
the row it omitted, an ordinary flow step, which records and never cascades.

E2E item 7 said "deployable" where the rule is "wakeable": with only the dbt
project reading the relation the producer set is empty, which deploys fine.

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

2026-09-05 10:42:42 +02:00

..

src

fix: report a warehouse-lookup failure as the failure it is, and correct the boundary

2026-09-05 10:42:42 +02:00

Cargo.toml

fix: keep native triggers attached when a runnable is renamed (#10432)

2026-07-31 23:44:25 +02:00