| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Signed-off-by: Korijn van Golen <k.vangolen@mapiq.com>
|
Is anyone available for reviewing this PR and kicking off the CI workflows? |
Sorry, something went wrong.
|
@Korijn Looks like some unrelated tests are failling. I think something is broken on main branch. Will raise with concerned person to fix it |
Sorry, something went wrong.
|
The tests are fixed on main. Please merge main into this branch |
Sorry, something went wrong.
Done |
Sorry, something went wrong.
|
when will this be reviewed? |
Sorry, something went wrong.
|
This PR makes me feel like Dependabot! 😁 |
Sorry, something went wrong.
|
bump? |
Sorry, something went wrong.
|
Done |
Sorry, something went wrong.
…776) The _extract_versions_from_specifier function stripped a single `~` character from constraint strings, which corrupted PEP 440 compatible release syntax (`~=`) by leaving a stray `=`. For example, `thrift = "~=0.22.0"` produced the invalid constraint `thrift>==0.22.0,<=0.23.0`, breaking every PR's "Unit Tests (min deps)" job since #733 was merged. Add an explicit branch for `~=` that strips both characters before extracting the minimum version. The Poetry-style single `~` branch is preserved for backward compatibility. Co-authored-by: Isaac Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>
| Back | FazBrowse Home | New Git URL |
What type of PR is this?
Description
Thrift v0.22.0 has addressed this warning which is constantly being emitted when using dbt-databricks:
WARNING:thrift.transport.sslcompat:using legacy validation callback
How is this tested?
Related Tickets & Documents
Closes #695