-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update adapter version messages #10919
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10919 +/- ##
=======================================
Coverage 89.19% 89.19%
=======================================
Files 183 183
Lines 23466 23470 +4
=======================================
+ Hits 20930 20934 +4
Misses 2536 2536
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@@ -130,7 +130,11 @@ def _get_plugin_msg_info( | |||
|
|||
needs_update = False | |||
|
|||
if plugin.major != core.major or plugin.minor != core.minor: | |||
assert plugin.major is not None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
asserts
shouldn't be used in production, see: https://snyk.io/blog/the-dangers-of-assert-in-python/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should actually just rip this version checking logic out 🤔
assert plugin.minor is not None | ||
assert core.major is not None | ||
assert core.minor is not None | ||
if plugin.major != core.major or plugin.minor < core.minor: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I talked with @colin-rogers-dbt + @mikealfare about this. I think we can get safely rid of this check entirely. Basically, we've decoupled the plugin (adapter specific) version and the core version. The majors no longer need to be equal, and the minor can be behind the core minor. The later might not actually be that uncommon.
All of this is the case because PyPI now handles this via dbt-adapters
. Essentially, dbt-core
specifies what dbt-adapters
versions it is compatible with, and each dbt adapter also specifies what dbt-adapters
versions it is compatible with. The result being, you'd have to intentionally force install incompatible versions for this check to be relevant. Thus, this check is unneeded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
even better! you want to do the honors or should i?
Resolves #10230
Problem
The messages in
dbt --version
don't reflect the fact that the minor version of an adapter could be ahead of the minor version of dbt coreSolution
update the semver check in
version.py
!I added the assertions for mypy's sake, but can be convinced to do that a different way
Checklist