Skip to content

[coverage] Conformance findings: ERRORRECOV-014 #483

Description

@peco-engineer-bot

Summary

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

Findings

  • ERRORRECOV-014 [sea]: SEA: retryDelayMax < retryDelayMin is passed to the kernel unvalidated and trips a Rust assertion failed: min <= max, surfacing as Error: panic in native binding and killing the tokio worker — an inconsistent backoff-bound pair must be corrected (raise max to min) and warn, not take the connection down
    • failing test: Errors — RetryBackoffBounds > retryDelayMax below retryDelayMin — connection opens and the retried query still succeeds [xfail] [sea] (see the coverage PR diff under tests/)

Reproduce & Expected

ERRORRECOV-014 — Validate that a backoff-bound typo — a configured MAXIMUM wait below the configured MINIMUM — does NOT fail the connection.

Reproduce:

SELECT 1 AS test_value

Expected (per the shared spec):

  • completes without an exception
  • result has exactly 1 row(s)
  • full assertion contract:
result:
- connection_not_null: true
  description: "max < min is corrected, not rejected \u2014 the connection opens"
- no_exception: true
- row_count: 1
  description: The retried query still succeeds under the corrected policy
protocol:
  thrift:
  - call_min:
      method: ExecuteStatement
      min: 2
  sea:
  - call_min:
      operation: ExecuteStatement
      min: 2

Context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions