You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6ab901f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(workspace): materialisation is owned by the engine's client; an unreadable link is unknown, not unbound
- Engine tools are recognised by the MCP client that served them, not by the
`datamate_` prefix alone: `MCP.tools()` stamps every entry with its client,
and another server named e.g. `datamate_snowflake` flattens to the same key
shape. Such keys confer no precedence and are reported once per session.
- The binding is read through the strict reader: a cache or credentials file
that is present but unreadable settles `binding-unreadable`, which `check()`
reports as undetermined with the reason, and which invalidates a routed
snapshot for that reason rather than as a re-link.
- A derivation that throws settles `derive-failed` — local execution with a
stated reason — instead of failing the turn's tool resolution.
- The re-link guard runs only when a redirect is about to be returned; a call
that runs locally regardless does not pay for the binding read.
- A superseded dbt-adapter attempt returns its result but no longer publishes
it over the newer attempt's cache, and `tryExecuteViaDbt` executes on the
adapter it was handed rather than re-reading the mutable global.
- The drift warning covers every warehouse capability shape, not only execute.
- `schema_inspect` validates its inputs before consulting precedence, as
`sql_explain` does, through a shared `input-validation` module.
- The guard-order test restores `ALTIMATE_INTEGRATIONS` it deletes.
0 commit comments