Ruben FiszelandClaude Opus 5 addcb4c525 fix: review round 1 — dbt-script materialize, set-form rule, doc ...

- Refuse `// materialize` on a dbt script, the producer half of the rule the
  trigger loop already applies to `// on`: the graph ingest republishes that
  path's asset rows wholesale, so a declared write is wiped by the deploy that
  accepted it while its runs keep stamping the relation.
- `dormant_dbt_subscriptions` now spells the same predicate its singular sibling
  does: the producer set has to be non-empty (nothing produces it yet is deploy
  order, not a dormant edge) and excludes the subscriber's own path (a script
  never wakes itself). Both divergences are pinned by tests.
- The docs no longer claim the dbt deploy log covers a native producer that drops
  its `// materialize`; it does not, and nothing else reports that case.
- An integration test over the deploy contract, since only a real deploy proves
  the handler feeds `sole_dbt_producer` the canonical key `asset.path` holds —
  the spelling that has to agree across the materialize target, the `// on` ref
  and the refusal that joins them.

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

2026-09-04 17:55:51 +02:00

..

examples

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

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

src

fix: review round 1 — dbt-script materialize, set-form rule, doc

2026-09-04 17:55:51 +02:00

tests

fix: review round 1 — dbt-script materialize, set-form rule, doc

2026-09-04 17:55:51 +02:00

Cargo.toml

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

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