Skip to content

[coverage] Conformance findings: LOGGING-003 #929

Description

@peco-engineer-bot

Summary

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.

Expected (per the shared spec):

  • completes without an exception
  • full assertion contract:
result:
- no_exception: true
- label: level_disabled
  log_sink_contains_kernel_record: false
- label: level_raised
  log_sink_contains_kernel_record: true

Context

Metadata

Metadata

Assignees

No one assigned

    Labels

    engineer-botMaintainer-applied gate: triggers engineer-bot (bug-fix on issue / take-over on PR).

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions