Fix snowflake provider installs picking an unimportable pyOpenSSL - #71145
Merged
jason810496 merged 1 commit intoAug 5, 2026
Merged
Conversation
boring-cyborg
Bot
added
area:providers
kind:documentation
provider:snowflake
1 task
jason810496
approved these changes
Aug 5, 2026
jason810496
left a comment
jason810496
left a comment
Member
There was a problem hiding this comment.
Thanks.
The only CI failure should be resolved in #71140. The CI should come back to green after rebasing.
snowflake-connector-python below 4.4.0 caps pyOpenSSL under 26.0.0, and pyOpenSSL 22.0.0 and older declare no upper bound on cryptography. Where nothing else pins cryptography — the provider compatibility jobs install the freshly built distributions without constraints — the resolver satisfies the newest cryptography with that ancient pyOpenSSL and backtracks the connector to 4.0.0. The environment installs cleanly and then dies on import with "module 'lib' has no attribute 'GEN_EMAIL'".
jason810496
force-pushed
the
fix-snowflake-pyopenssl-resolver-window
branch
from
August 5, 2026 08:29
1773f85 to
a1cfd6c
Compare
Contributor
|
Taking a look. |
amoghrajesh
marked this pull request as ready for review
August 5, 2026 08:34
amoghrajesh
added
the
full tests needed
amoghrajesh
approved these changes
Aug 5, 2026
Contributor
There was a problem hiding this comment.
LGTM, created an issue to track this: snowflakedb/snowflake-connector-python#2990
FrankYang0529
approved these changes
Aug 5, 2026
Lee-W
approved these changes
Aug 5, 2026
aaron-y-chen
approved these changes
Aug 5, 2026
aaron-y-chen
left a comment
aaron-y-chen
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the fix, my PR also encountered these failures.
1 task
Member
|
Nice! |
1 task
5 tasks
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
6 participants
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
Compat 2.11.1,Compat 3.0.6andCompat 3.1.8provider jobs fail collection on main withAttributeError: module 'lib' has no attribute 'GEN_EMAIL'; 3.2.2 and 3.3.0 are unaffected.Those jobs resolve the freshly built distributions unpinned (
--providers-skip-constraints), and with the apache/beam provider suspended nothing in the set capscryptographyany more, so it goes to the newest release.snowflake-connector-pythonbelow 4.4.0 requirespyOpenSSL<26.0.0, and the only candidate in that window claiming compatibility with a current cryptography is 22.0.0 — which declarescryptography>=35.0with no upper bound at all. The resolver takes it, backtracks the connector to 4.0.0 to match, and lands on an environment that installs cleanly and then dies the moment anything importsurllib3.contrib.pyopenssl.22.1.0 is the first pyOpenSSL release that bounds cryptography honestly, so the floor drops exactly the releases that lie and nothing else. Raising
snowflake-connector-pythonto>=4.4.0— the release that dropped the cap — would be the tidier fix but requirescryptography>=46.0.5, unsatisfiable against the constraints of every Airflow version these jobs cover.Tests
Resolving main's full provider dependency set for Python 3.10: unpinned now selects connector 4.7.1 with pyOpenSSL 26.3.0, and pinning cryptography to each value the released constraint files carry (41.0.7 / 42.0.8 / 44.0.3 / 45.0.7) still yields an importable pair.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines