-
Notifications
You must be signed in to change notification settings - Fork 459
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
Refactor azure storage with crate updates #644
Conversation
Hi @roeap you can remove |
Thanks @Blajda - always happy to be able to slim down dependencies 😆 |
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 is a great cleanup! LGTM.
@wjones127 - we saw failing CI due to windows runners running out of disk space. Based on pola-rs/polars#3122 (comment) I switched to using Swatinem/rust-cache, which seems to do some nice things around managing cache size and utilization. Right now builds are passing again, but this could just be related to using a "fresh" cache, we'll have to keep an eye on it. Could you have another look? |
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 like it helped Polars and they are still using it, so should be good. I'll keep on eye on that CI job.
Description
With the latest version of the azure SDKs some annoyances got fixed. specifically, list now returns something
Send
able, which allows us to significantly simplify thelist_objs
method. Secondly the errors are no longer a deeply nested nightmare 😆.Also added a test for validating that service principal access works (#609) - currently i am guessing the issues encountered there are more related to #643
Related Issue(s)
validate the SP access works for #609
Documentation