Skip to content

Fix error tracker URL to point to the Python SDK repo#1462

Open
renaudhartert-db wants to merge 1 commit into
mainfrom
fix-error-tracker-url
Open

Fix error tracker URL to point to the Python SDK repo#1462
renaudhartert-db wants to merge 1 commit into
mainfrom
fix-error-tracker-url

Conversation

@renaudhartert-db
Copy link
Copy Markdown
Contributor

@renaudhartert-db renaudhartert-db commented Jun 7, 2026

Summary

The "unable to parse response" fallback error now links to the databricks-sdk-py issue tracker instead of databricks-sdk-go.

Why

That message is only emitted by the Python SDK, but it hard-coded the Go tracker URL, so affected users filed Python issues against the Go repo. Recent reports there (#1703, #1709, #1710) were Python runs that landed in the wrong place for this reason.

How is this tested?

tests/test_errors.py passes; the three cases that asserted the old URL are updated.

NO_CHANGELOG=true

The "unable to parse response" fallback error message directed users to the
databricks-sdk-go issue tracker. Since this message is emitted by the Python
SDK, users hit by an unparseable response were filing Python issues against
the Go repo. Point the link at databricks-sdk-py instead.

Co-authored-by: Isaac
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 7, 2026

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/sdk-py

Inputs:

  • PR number: 1462
  • Commit SHA: a909ab170d482db3cb76af3112c8d8a61eb59a71

Checks will be approved automatically on success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant