Update databrickslabs/sandbox requirement to acceptance/v0.2.1#5
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Updates the requirements on [databrickslabs/sandbox](https://github.com/databrickslabs/sandbox) to permit the latest version. - [Release notes](https://github.com/databrickslabs/sandbox/releases) - [Changelog](https://github.com/databrickslabs/sandbox/blob/main/CHANGELOG.md) - [Commits](https://github.com/databrickslabs/sandbox/commits/acceptance/v0.2.1) --- updated-dependencies: - dependency-name: databrickslabs/sandbox dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
|
@dependabot ignore this minor version |
Author
|
OK, I won't notify you about version 0.2.x again, unless you re-open this PR. |
dependabot
Bot
deleted the
dependabot/github_actions/databrickslabs/sandbox-acceptance/v0.2.1
branch
April 23, 2024 19:19
8 tasks
vb-dbrks
added a commit
that referenced
this pull request
Jul 3, 2026
…ecret Addresses Marcin's review comments on the MCP server plus a round of Genie feedback from driving the tools end to end. Write governance (#1-#3): the persisting tools no longer take a caller-supplied destination. save_checks / apply_checks_and_save_to_table now take a bare output name and the runner writes it into the caller's own SP-owned per-user schema (dqx_mcp_<user>), granting only that caller access. This lets me delete the OBO write pre-check entirely - it checked the caller's perms while the SP did the write (false assurance), rejected MODIFY-granted non-owners, and classified UC errors by string-matching. The SP now only ever writes where it owns. Runner robustness (#5, #6): save_checks applies write mode via config.replace() instead of attribute assignment (which silently no-op'd on file backends), with an up-front append/overwrite whitelist; generate_rules validates each profile and raises a clear InvalidParameterError on a missing name/column instead of a KeyError deep in the runner. Correctness & CI (#4, #7, #8): execute_sql follows next_chunk_index so wide schemas and the temp-view sweep aren't silently truncated to the first chunk; added basedpyright (make mcp-check, wired into push.yml) and fixed the type errors it surfaced; pointed the integration-coverage source at the MCP packages rather than the DQX library. Docs (#9): moved deploy/prerequisites into the installation page and linked back. Genie feedback (MCP-side wrappers): generate_rules_from_contract now accepts inline contract_content (or a file), reads it as the caller and stages a copy to a runner-readable volume - so a Workspace-file contract works even though the runner SP has no access to it; list_available_checks takes a filter substring so agents can search instead of scanning every entry; generate_rules flags that its bounds are data-derived and should be reviewed. Dropped the catalog secret: a UC catalog name isn't sensitive (access is governed by UC grants, not by hiding the name), so the app reads DQX_CATALOG as a plain config value set from the catalog_name deploy var (inline app config, no app.yaml) - nothing to create or manage out of band. Also fixed make mcp-integration for local runs (absolute UV_BUILD_CONSTRAINT, mirroring mcp-deploy) and updated the integration test + fixture for the new tool shapes. Extracted the runner's pure naming/validation helpers into naming.py so they're unit-tested without Spark.
fedeflowers
added a commit
to fedeflowers/dqx
that referenced
this pull request
Jul 4, 2026
…gle validation boundary Move all check validation onto the CheckSpec Pydantic model via a model_validator so Pydantic is the single typed validation boundary (the maintainer's headline request), and resolve the ranked findings: - Native validation (meta): criticality value, function resolution, and signature/argument validation now run in CheckSpec._validate_semantics (model_validator). ChecksValidator becomes a thin layer that calls model_validate per check and translates ValidationError to DQX messages. - #1 user_metadata regression: widen to dict[str, Any] on CheckSpec, DQRule, and DQForEachColRule so non-string values (e.g. {"confidence": 0.95}) load as they did pre-migration; add a regression test. - databrickslabs#2/databrickslabs#3 double validation & discarded spec: _validate_and_parse returns the parsed specs; ChecksDeserializer.deserialize reuses them instead of re-parsing the raw dict, giving a single typed pass. - databrickslabs#4 error-shim fragility: add a test pinning the Pydantic error-type codes the translator branches on so a rename fails loudly (pydantic<3 already caps the major version). - databrickslabs#6 loader divergence: route the Delta from_dataframe path through the same project_to_check_schema allow-list as the Lakebase path; add a guard test. - databrickslabs#7 docstrings: replace double-backticks with italics per AGENTS.md. databrickslabs#5 (extra="forbid") confirmed safe with no code change: all *ChecksStorageConfig construction sites use explicit kwargs and the behavior is already locked by existing config tests (test_storage_config_rejects_unknown_kwarg).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on databrickslabs/sandbox to permit the latest version.
Changelog
Sourced from databrickslabs/sandbox's changelog.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)