The Fix
pip install pydantic==1.10.18
Based on closed pydantic/pydantic issue #10079 · PR/commit linked
@@ -134,6 +134,7 @@
'MariaDBDsn',
'ClickHouseDsn',
+ 'SnowflakeDsn',
'validate_email',
# root_model
engine = create_engine(
'snowflake://{user}:{password}@{account_identifier}/'.format(
user='<user_login_name>',
password='<password>',
account_identifier='<account_identifier>',
)
)
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
Option A — Upgrade to fixed release\npip install pydantic==1.10.18\nWhen NOT to use: Do not use this fix if your application does not require Snowflake DSN support.\n\n
Why This Fix Works in Production
- Trigger: It seems like this is something that is straightforward to define within my project, so if this doesn't make sense to add to Pydantic I have no concerns - I…
- Mechanism: Missing DSN type for Snowflake in Pydantic's network types
- Why the fix works: Adds support for the Snowflake DSN format to Pydantic's network types. (first fixed release: 1.10.18).
Why This Breaks in Prod
- Missing DSN type for Snowflake in Pydantic's network types
- Production symptom (often without a traceback): It seems like this is something that is straightforward to define within my project, so if this doesn't make sense to add to Pydantic I have no concerns - I assume I would start from something like this:
Proof / Evidence
- GitHub issue: #10079
- Fix PR: https://github.com/pydantic/pydantic/pull/10128
- First fixed release: 1.10.18
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.85
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.64
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“@sydney-runkle if no one is working on it, Could you please assign this to me ?”
“Hi @aditkumar72 are you still working on it? i have my PR ready if youre not then let me know thanks.”
“@Vasanth-96, go ahead and submit your PR, I can review tomorrow :)”
Failure Signature (Search String)
- It seems like this is something that is straightforward to define within my project, so if this doesn't make sense to add to Pydantic I have no concerns - I assume I would start
- - [ ] [Compatibility between releases](https://docs.pydantic.dev/changelog/)
Copy-friendly signature
Failure Signature
-----------------
It seems like this is something that is straightforward to define within my project, so if this doesn't make sense to add to Pydantic I have no concerns - I assume I would start from something like this:
- [ ] [Compatibility between releases](https://docs.pydantic.dev/changelog/)
Error Message
Signature-only (no traceback captured)
Error Message
-------------
It seems like this is something that is straightforward to define within my project, so if this doesn't make sense to add to Pydantic I have no concerns - I assume I would start from something like this:
- [ ] [Compatibility between releases](https://docs.pydantic.dev/changelog/)
Minimal Reproduction
engine = create_engine(
'snowflake://{user}:{password}@{account_identifier}/'.format(
user='<user_login_name>',
password='<password>',
account_identifier='<account_identifier>',
)
)
What Broke
Users cannot validate or parse Snowflake DSN formats, leading to integration issues.
Why It Broke
Missing DSN type for Snowflake in Pydantic's network types
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install pydantic==1.10.18
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/pydantic/pydantic/pull/10128
First fixed release: 1.10.18
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- Do not use this fix if your application does not require Snowflake DSN support.
Verify Fix
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
Did This Fix Work in Your Case?
Quick signal helps us prioritize which fixes to verify and improve.
Prevention
- Add a CI check that diffs key outputs after upgrades (OpenAPI schema snapshots, JSON payload shapes, CLI output).
- Upgrade behind a canary and run integration tests against the canary before 100% rollout.
Version Compatibility Table
| Version | Status |
|---|---|
| 1.10.18 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.