-
Notifications
You must be signed in to change notification settings - Fork 304
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
Remove open_async usage in put raw data #2998
Conversation
Signed-off-by: Yee Hing Tong <[email protected]>
git push Signed-off-by: Yee Hing Tong <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks reasonable.
I don't understand the integration test failures. This change shouldn't have any impact in the minio credentials. Any idea what's going on there?
nope... |
Signed-off-by: Yee Hing Tong <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2998 +/- ##
===========================================
+ Coverage 51.08% 76.86% +25.78%
===========================================
Files 201 204 +3
Lines 21231 21406 +175
Branches 2731 2726 -5
===========================================
+ Hits 10846 16454 +5608
+ Misses 9787 4201 -5586
- Partials 598 751 +153 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Yee Hing Tong <[email protected]>
Signed-off-by: Yee Hing Tong <[email protected]>
Signed-off-by: Yee Hing Tong <[email protected]>
Why are the changes needed?
Syntax was always wrong. This is not how open_async is used.
See fsspec/s3fs#871, which may be resolved here.
Polars
This also affected polars. In testing, noticed part of the logic was incorrect - updated and added a test to exercise.
What changes were proposed in this pull request?
Replace with a normal call - this means that writes for bytes and bytes-like objects will be blocking. Given this seems to be fundamentally missing from fsspec at this time I think it's okay.
How was this patch tested?
Unit tested and local sandbox.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link