-
Notifications
You must be signed in to change notification settings - Fork 130
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-143538: We keep getting error 402001 - Network error. Could not reach S3/Blob. #85
Comments
Added to the backlog. |
Co-authored-by: Michał Wadas <[email protected]> This attempts to mitigate #85
Co-authored-by: Michał Wadas <[email protected]> This attempts to mitigate #85
Just hit this too Which version will have the fix? |
This is useful to fix error snowflakedb/snowflake-connector-nodejs#85
We are experiencing this problem with version 1.6.14 of the library, i.e. after the fix was implemented. Can you provide any more information about the root cause of the problem to better help us understand how to work around or address it? |
Seeing this intermittently with |
Our workaround was to spin Python process and communicate with it through IPC, as Python driver doesn't have this issue. |
System:
Node v10.18.0
npm v6.13.4
Ubuntu 18.04.3 LTS
[email protected]
What did you do?
We are running code like:
Result set is around 500k rows.
What did you expect to see?
Working properly.
What did you see instead?
We are randomly seeing error:
Unfortunely, there isn't reliable way to trigger it.
How should we debug from this place?
The text was updated successfully, but these errors were encountered: