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
Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-python. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-sql-python) is fixed, then flips green as a tripwire.
Findings
LOGGING-003 [sea]: a kernel-backed session opened while logging is disabled leaves kernel log forwarding off for the whole process: the connector never invalidates pyo3_log's cached effective level, so raising the level and opening a new session delivers no databricks.sql.kernel records (databricks_sql_kernel.reset_logging() restores delivery)
failing test: test_disabled_log_level_leaves_kernel_forwarding_installable (see the coverage PR diff under tests/)
Reproduce & Expected
LOGGING-003 — Opening a kernel-backed session while the driver's log level is disabled/off must not permanently disable kernel log forwarding for the process: no kernel records are emitted while the level is off,…
Reproduce:
First kernel-backed session/record attempt, while logging is disabled.
Second kernel-backed session/record attempt, now at Warn.
Poll the sink for the kernel record with a bounded deadline.
The behavior was first fixed in a DIFFERENT driver — reference PR: feat(kernel): forward logs through shared logger databricks-sql-go#450 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-python; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
Activity
peco-engineer-bot commentedon Aug 24, 2026
🤖 engineer-bot could not complete an automated fix. See the workflow run for details.
vuanhphung commentedon Sep 10, 2026
Closing because this issue was filed by redundant coverage fan-out PRs for Callback logging, and no retained or otherwise-open coverage PR links to it. Coverage is consolidated in https://github.com/databricks/databricks-driver-test/pull/1393.