[coverage] Conformance findings: SESSION-010

Open
#883 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
api, backend

Research direction

Start by locating user_friendly_error_message() and _extract_error_message_from_headers(), then inspect the expected-failure test for SESSION-010 from the coverage fan-out. Done means the session-open auth failure preserves the server detail and HTTP 401 status in the surfaced RequestError instead of returning only the generic message.

Written by the indexing model from the issue text.

Description

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-python.

Each is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT behavior and stays red until this driver is fixed.

  • SESSION-010: Thrift session-open auth failure discards the server's detail: an HTTP 401 with "Token has expired" in the body surfaces as a bare RequestError("Error during request to server. "), dropping both the server text and the 401 status, so callers cannot distinguish an expired token from a bad warehouse or a network fault. user_friendly_error_message() appends only header-sourced detail (_extract_error_message_from_headers) and never the HTTP status.

Reference driver PR: https://github.com/databricks/databricks-jdbc/pull/1587
Coverage PR (reproducing xfail tests): https://github.com/databricks/databricks-driver-test/pull/974

Dominant language
Python
Stars
233
Forks
152
Avg merge
21h 5m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-sql-python

All issues in databricks/databricks-sql-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.