-
Notifications
You must be signed in to change notification settings - Fork 124
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
SNOW-874337: move from current version of urllib
(v2)
#590
Comments
urllib
(v2)urllib
(v2)
Hey there, is there any target date for this fix? |
yes, apologies for missing it out from the original post. I now added it there, and adding it here too: latest target date is end of Q3 (October). Being a high priority item, we aim for a quicker implementation but that's the current timing. |
Are you planning to replace urllib with Node-native APIs? |
as far as I know, there might be multiple approaches on the table still. I'll keep this Issue updated with the details as they become available to the public. |
after all, as a result of a long consideration and multiple internal discussions, we decided to go with It will be part of the next upcoming release towards end of September. |
fix is now out with release 1.9.0 , available on npm as well |
Raising this issue to give a more transparent way to track the internal effort of addressing the current challenges around
urllib
v2.Background:
There already a couple of issues of various severity, stemming from
urllib
v2 (2.40.0) and its direct/indirect dependencies, whichurllib
version is currently in use by the Snowflake Node.JS driver, some examples:(et al)
We cannot just take the
urllib
dependency and bump to the most recent (v3) versions, becauseurllib
v3.0.0 introduced a breaking change as is't been rebased to undici and that version is incompatible withsnowflake-sdk
implementation today.As
urllib
provides a core functionality tosnowflake-sdk
(sending HTTP requests to the Snowflake engine) , appropriate care needs to be taken in refactoring the solution.This Issue is here to track the progress. Current aim is to implement and release the changes by end of Q3 2023
The text was updated successfully, but these errors were encountered: