-
Notifications
You must be signed in to change notification settings - Fork 126
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
WithStreamDownloader flag causes some errors to be dropped #974
Comments
hi and thank you for raising this issue with us (and for the suggestion as well!) , we're going to take a look |
PR under review #994 |
Awesome, thank you! |
I checked the commit from this branch out, and I think it ended up causing more bugs.
and now I am seeing this error, which previously was not the case
|
Hello @madisonchamberlain ! I believe this is not related to the stream downloader. It is related to the other fix from yesterday - #993 |
Yes, my mistake I think it was caused by #993 because it worked on sha cf94c15 and stopped working on a4c3557. I will look into a fix for this and file a separate bug, because it seems to break with a lot of queries like |
released with gosnowflake 1.7.2 |
Please answer these questions before submitting your issue.
In order to accurately debug the issue this information is required. Thanks!
What version of GO driver are you using?
1.7.0
What operating system and processor architecture are you using?
mac m1
What version of GO are you using?
run
go version
in your consolego version go1.20.7
5.Server version:* E.g. 1.90.1
NA
I noticed that when the
WithStreamDownloader
flag is set to true, sometimes there will be no result and no error returned. I am using this with row based result (not arrow based), with result type =queryResultType
. I believe this error happens if there is an issue with getting the ChunkDownloader to start.rows.ChunkDownloader.start()
returns an error, but no matter what is returned, the error channel gets nil. Is there any reason not to do something like this?The text was updated successfully, but these errors were encountered: