Skip to content

[pull] main from databricks:main#248

Merged
pull[bot] merged 1 commit into
Future-Outlier:mainfrom
databricks:main
Jun 8, 2026
Merged

[pull] main from databricks:main#248
pull[bot] merged 1 commit into
Future-Outlier:mainfrom
databricks:main

Conversation

@pull

@pull pull Bot commented Jun 8, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## 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
@pull pull Bot locked and limited conversation to collaborators Jun 8, 2026
@pull pull Bot added the ⤵️ pull label Jun 8, 2026
@pull pull Bot merged commit fef9b73 into Future-Outlier:main Jun 8, 2026
@pull pull Bot had a problem deploying to test-trigger-is June 8, 2026 09:18 Failure
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant