[coverage] Conformance findings: ERRORRECOV-013
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing ExecuteStatement and the nonRetryableClientMethods retry configuration in the Go driver. Use the ERRORRECOV-013 expected-failure test from the referenced coverage PR to reproduce the force-closed connection case; done means the transient transport error is retried and ExecuteStatement recovers instead of failing after one attempt.
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-go.
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.
- ERRORRECOV-013: driver does not retry transient transport-level errors on ExecuteStatement (nonRetryableClientMethods); a force-closed connection surfaces the transport error verbatim (request error after 1 attempt) instead of retrying and recovering
Reference driver PR: https://github.com/adbc-drivers/databricks/pull/373
Coverage PR (reproducing xfail tests): https://github.com/databricks/databricks-driver-test/pull/895
- Dominant language
- Go
- Stars
- 53
- Forks
- 67
- Avg merge
- 21h 29m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/databricks-sql-go
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
databricks/databricks-sql-go#476 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 64/100
databricks/databricks-sql-go#490 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
databricks/databricks-sql-go#481 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
databricks/databricks-sql-go#480 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
databricks/databricks-sql-go#475 · 1 comment ·
Maintainers usually reply within 1 day
All issues in databricks/databricks-sql-go
Similar issues
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
needs-triage sig/api-machinery
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes/kubernetes#142651 · 1 comment ·
Maintainers usually reply within 1 day
-
component/mesheryctl kind/bug language/go
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
meshery/meshery#22221 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
resend/resend-skills#144 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100