Skip to content

feat(integrations/dagster): thread --check through doctor()#229

Merged
hugocorreia90 merged 1 commit intomainfrom
feat/dagster-doctor-check-filter
Apr 22, 2026
Merged

feat(integrations/dagster): thread --check through doctor()#229
hugocorreia90 merged 1 commit intomainfrom
feat/dagster-doctor-check-filter

Conversation

@hugocorreia90
Copy link
Copy Markdown
Contributor

Summary

  • Add optional check: str | None kwarg to RockyResource.doctor() that forwards --check <id> to the CLI, and switch state_health()'s state_rw probe to doctor(check="state_rw") — cutting the probe cost from a full doctor suite to a single sub-second probe_state_backend round-trip.
  • Pure Python argv change: no engine change, no codegen, DoctorOutput schema unchanged (filtered output is the same shape with fewer entries in checks).
  • Client-side check-id validation is deliberately omitted — the engine owns the valid set; duplicating it in Python would drift.

Test plan

  • uv run pytest tests/test_resource.py tests/test_state_health.py -x -q (85 passed — includes 4 new tests)
  • Full suite: uv run pytest tests/ -x -q (374 passed, no regressions)
  • uv run ruff check . (all checks passed)
  • uv run ruff format --check . (46 files already formatted)
  • doctor() without check kwarg still emits ["doctor"] — back-compat for existing callers
  • doctor(check="state_rw") emits ["doctor", "--check", "state_rw"]
  • state_health(probe_write=True) calls doctor(check="state_rw") (spy assertion)

Adds an optional `check` kwarg to RockyResource.doctor() that forwards
`--check <id>` to the CLI, and switches state_health()'s state_rw probe
to call doctor(check="state_rw"). The engine already scoped `--check` to
a single check; the Python wrapper was running the full doctor suite on
every probe, turning state_health(probe_write=True) into a
multi-second call instead of the sub-second round-trip the
probe_state_backend helper runs in.

Client-side check-id validation is deliberately omitted — the engine
owns the set of valid ids, and duplicating it in Python would drift.

Pure Python argv change: no engine change, no codegen, DoctorOutput
schema unchanged (filtered output is the same shape with fewer
entries in `checks`).
@hugocorreia90 hugocorreia90 merged commit afc411a into main Apr 22, 2026
8 checks passed
@hugocorreia90 hugocorreia90 deleted the feat/dagster-doctor-check-filter branch April 22, 2026 16:55
hugocorreia90 added a commit that referenced this pull request Apr 22, 2026
* chore: release engine-v1.14.0 + dagster-v1.10.0 + vscode-v1.6.4

Bumps all three artifacts to cover the 16-PR cascade since engine-v1.13.0
/ dagster-v1.9.0 / vscode-v1.6.3. Details in each CHANGELOG.

Engine headlines (12 PRs):
- Arc 7 wave 2 wave-2 complete — cached DESCRIBE end-to-end
  (#223 infra, #228 reads, #230 write tap, #231 discover warm-up,
  #232 state controls + --cache-ttl override)
- Arc 2 wave 3 complete — bytes_scanned / bytes_written on
  MaterializationOutput (#219 BQ, #221 Databricks, #220 Snowflake
  deferred doc, #222 docstring cascade). Real $ on rocky cost for
  BQ + Databricks
- FR-005 Unity Catalog workspace-binding reconcile (#226)
- FR-002 Fivetran connector metadata via SourceOutput.metadata (#225)
- Housekeeping: compute_backoff dedup into rocky_core::retry (#217)

Dagster headlines (4 PRs):
- FR-001 RockyComponent Pipes execution mode + FR-006 strict doctor
  on RockyResource startup (#224)
- FR-003 RockyResource.state_health() (#227) + FR follow-up threading
  doctor(check=state_rw) for sub-second probes (#229)
- RockyResource.cost() wiring + fixture (#218)

VS Code: regenerated TS bindings for engine 1.14.0 type additions.
No extension feature changes.

* chore(integrations/dagster): regenerate test fixtures for engine 1.14.0

36 fixtures picked up the new engine version string in their top-level
"version" field. No schema changes — just the version bump.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant