[coverage] Conformance findings: TELEMETRY-017 #545

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-go. 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-go) is fixed, then flips green as a tripwire.

Findings

• TELEMETRY-017 [sea]: DSN parameter telemetry_flush_interval accepts non-positive durations ("0s", "-1s"): connect succeeds and a session is opened instead of failing client-side with an error naming the option, so an invalid interval reaches the kernel telemetry exporter
  • failing test: TestInvalidTelemetryFlushIntervalRejectedAtConnect (see the coverage PR diff under tests/)

Reproduce & Expected

TELEMETRY-017 — A non-positive telemetry flush interval is a configuration error, not a value to hand to the telemetry exporter.

Expected (per the shared spec):

• [sea] exactly 0 CreateSession call(s)
• full assertion contract:

result:
- label: zero_interval
  error:
    contains:
    - flush_interval
- label: negative_interval
  error:
    contains:
    - flush_interval
protocol:
  sea:
  - call_count:
      operation: CreateSession
      expected: 0
    description: 'The rejection is client-side: no session is opened for either attempt.'

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: fix(kernel): forward telemetry_flush_interval_ms to the kernel databricks-sql-python#1026 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-go; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
• Coverage PR carrying the reproducing xfail test(s): https://github.com/databricks/databricks-driver-test/pull/2012