Fix error tracker URL to point to the Python SDK repo#1462
Open
renaudhartert-db wants to merge 1 commit into
Open
Fix error tracker URL to point to the Python SDK repo#1462renaudhartert-db wants to merge 1 commit into
renaudhartert-db wants to merge 1 commit into
Conversation
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
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The "unable to parse response" fallback error now links to the
databricks-sdk-pyissue tracker instead ofdatabricks-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.pypasses; the three cases that asserted the old URL are updated.NO_CHANGELOG=true