-
Notifications
You must be signed in to change notification settings - Fork 110
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
Optimized gitrepo cloning broken on win10 #3639
Labels
crippled-filesystems
Issue concerned with operation on crippled filesystems, regardless of OS
platform-windows
Issue concerned with Windows
severity-normal
standard severity
Comments
mih
added a commit
that referenced
this issue
Sep 1, 2019
mih
added a commit
that referenced
this issue
Sep 18, 2019
mih
added a commit
that referenced
this issue
Sep 19, 2019
mih
added a commit
that referenced
this issue
Sep 19, 2019
mih
added a commit
to mih/datalad
that referenced
this issue
Jan 2, 2020
The new 'compatibility' argument of get_local_file_url() is relatively painless and the workaround implementation can be removed (and the argument rendered into a no-op) if there should be a compatibility fix at the git-annex end. Fixes dataladgh-3639
mih
added
severity-normal
standard severity
and removed
platform-windows
Issue concerned with Windows
labels
Jul 15, 2020
This is not just a windows issue, but affects crippled FS as well.
Revealed via gh-4708 |
mih
added
the
crippled-filesystems
Issue concerned with operation on crippled filesystems, regardless of OS
label
Jul 15, 2020
FWIW, on a verge of 2022 we still have that test disabled on windows
so it is 50/50 chance it still exists! ;-) |
Confirm to still be happening on crippled FS. |
Closing this old issue of mine. In three years at has never made a priority level that led to actual fixes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
crippled-filesystems
Issue concerned with operation on crippled filesystems, regardless of OS
platform-windows
Issue concerned with Windows
severity-normal
standard severity
Originally reported in #3635. Making it a separate issue, because the test will be disabled on win in order to make progress on more important issues.
This issue is legit, inodes seem to be reported properly, but do not match.
The text was updated successfully, but these errors were encountered: