Skip to content

fix: improve install and add error messages for pre-release drivers#338

Merged
zeroshade merged 2 commits intocolumnar-tech:mainfrom
amoeba:fix/better-pre-release-error
Apr 2, 2026
Merged

fix: improve install and add error messages for pre-release drivers#338
zeroshade merged 2 commits intocolumnar-tech:mainfrom
amoeba:fix/better-pre-release-error

Conversation

@amoeba
Copy link
Copy Markdown
Member

@amoeba amoeba commented Apr 1, 2026

Updates dbc install and dbc add to provide command suggestions for pre-release drivers.

For example: Currently, if I try to dbc install a driver that only has a pre-release available, I get an error message that isn't that helpful,

$ dbc install fakedriver
Error: driver `fakedriver` not found (but prerelease versions filtered out)

This PR updates the error so it recommends the user try --pre:

$ dbc install fakedriver
Error: driver `fakedriver` not found (but prerelease versions filtered out); try: dbc install --pre fakedriver

This error only happens if the driver only has pre-release versions and the user doesn't specify --pre. It's not a perfect heuristic but I think it'll work well.

@amoeba amoeba requested review from ianmcook and zeroshade April 1, 2026 19:52
@ianmcook
Copy link
Copy Markdown
Member

ianmcook commented Apr 1, 2026

Thanks for doing this!

@amoeba amoeba changed the title fix: improve dbc install error message for pre-release drivers fix: improve install and add error messages for pre-release drivers Apr 1, 2026
@amoeba
Copy link
Copy Markdown
Member Author

amoeba commented Apr 1, 2026

Updated PR to include coverage for dbc add as well.

@ianmcook
Copy link
Copy Markdown
Member

ianmcook commented Apr 2, 2026

What about the case when only pre-release versions are available on the registry, and you already have a pre-release version installed?

For example, what should happen when you do:

dbc install --pre singlestore
dbc install singlestore

@zeroshade zeroshade merged commit 2f0f546 into columnar-tech:main Apr 2, 2026
12 checks passed
@zeroshade
Copy link
Copy Markdown
Member

Bah, i missed @ianmcook's question.

@amoeba can you still answer the question there and determine if we need a follow-up PR?

@amoeba
Copy link
Copy Markdown
Member Author

amoeba commented Apr 2, 2026

I don't think that behavior is changed by this PR so I'll create a new issue.

@amoeba
Copy link
Copy Markdown
Member Author

amoeba commented Apr 2, 2026

#340

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.

3 participants