You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2020. It is now read-only.
If we have a Google Drive file called https://a/b/c/boardingpass.pdf when we pull we get a directory called https:, then a directory called a, then b, etc. till we get a boardingpass.pdf file, and not a file called https://a/b/c/boardingpass.pdf.
It might seem like an obscure issue, but Google's own "save to drive" and all the extensions that save to drive might create such a file name.
The text was updated successfully, but these errors were encountered:
In deed it is an issue even on other *NIX derived OS-es. Previously the escape route was just doing a mkdir -p equivalent since you cannot ordinarily create a file with the standard path separators in its path. I have a working prototype to address this and will get it up in a bit.
mdp
pushed a commit
to mdp/drive
that referenced
this issue
Feb 4, 2019
This is true for Linux:
If we have a Google Drive file called
https://a/b/c/boardingpass.pdf
when we pull we get a directory calledhttps:
, then a directory calleda
, thenb
, etc. till we get aboardingpass.pdf
file, and not a file calledhttps://a/b/c/boardingpass.pdf
.It might seem like an obscure issue, but Google's own "save to drive" and all the extensions that save to drive might create such a file name.
The text was updated successfully, but these errors were encountered: