Skip to content
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

Quick fix for dir_path and getsize for Azure Blob #1

Closed
wants to merge 13 commits into from
Closed

Quick fix for dir_path and getsize for Azure Blob #1

wants to merge 13 commits into from

Conversation

mzjp2
Copy link

@mzjp2 mzjp2 commented Aug 2, 2018

Fixed the join problem in dir_path, specified prefix arguent in rmdir and fixed getsize.

@tjcrone
Copy link
Owner

tjcrone commented Aug 2, 2018

Thanks for this PR @mzjp2. We are in a bit of a tough spot because I am in a fork chain w/ @friedrichknuth, and because this branch includes @rabernat's GCSStore, which I don't think we should include in an upstream PR. For this reason I am going to do a little clean up by rebranching from upstream master, cherry pick most of the commits from this branch, and at that point we can merge your PR, and then do an upstream PR. Sorry this is so complicated, but I think we can make it happen.

@mzjp2
Copy link
Author

mzjp2 commented Aug 2, 2018

Ah yes, I did notice the slightly convoluted fork chain. Glad to know we can make it happen. If I can assist with the cleanup in any way, please let me know, I'd be happy to help!

@tjcrone
Copy link
Owner

tjcrone commented Aug 2, 2018

@mzjp2, I did some maintenance on the fork chain and the commits to this branch. Unfortunately this required a rewrite of history on this fork and on the immediate upstream fork. I am sorry about this. However I was able to add a doc string, remove the GCSStore MutableMapping, and rebase the entire abs_store branch onto the upstream (upstream) master. So if you are okay with this, I'm guessing that the best way forward is for you to either refork, or you to clean up on your side with a fetch/rebase, and then we can add your PR. At that point I think we can do a PR all the way upstream, get this into at least a branch on the main repo, and we can get out of this fork chain difficulty. Does this sound like a good idea to you?

@mzjp2 mzjp2 closed this Aug 2, 2018
@mzjp2
Copy link
Author

mzjp2 commented Aug 2, 2018

No worries @tjcrone, I went for the easier option (as my changes were relatively minor) and just reforked. Thanks for your work on the maintenance of the fork chain 👍

@dazzag24
Copy link

dazzag24 commented Aug 3, 2018

Thanks @tjcrone and @mzjp2. Taking a slightly higher level view for a moment, what we really need in order to continue with out testing is a code base that combines the abbstore work AND the combined metadata work (zarr-developers#268). Given the state of the various forks, what is the best way to achieve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants