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.

Sign up for GitHub

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

Jump to bottom

Get/downsync target path does not support windows extended length paths #213

Closed
AOOSG opened this issue Jun 18, 2022 · 2 comments · Fixed by #214
Closed

Get/downsync target path does not support windows extended length paths #213

AOOSG opened this issue Jun 18, 2022 · 2 comments · Fixed by #214
Labels
bug Something isn't working

Comments

@AOOSG
Copy link

AOOSG commented Jun 18, 2022

It looks like using a windows extended path prefix \\?\ is not supported for the target path when using the get or downsync command.

Example: get/downsync ... --target-path "\\?\D:\SomePath" throws an error similar to this:

get: downsync: GetFolderIndex: open \\?\D:\SomePath/.longtail.index.cache.lvi: The filename, directory name, or volume label syntax is incorrect.

No errors is reported if using --target-path "D:\SomePath"
@DanEngelbrecht DanEngelbrecht added the bug Something isn't working label Jun 19, 2022
@DanEngelbrecht DanEngelbrecht mentioned this issue Jun 19, 2022
Merged
@DanEngelbrecht
Copy link
Owner

@AOOSG Please try out https://github.com/DanEngelbrecht/golongtail/releases/tag/v0.3.6-pre0 and see if that helps.

@AOOSG
Copy link
Author

AOOSG commented Jun 26, 2022

Thanks, will do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

UNC path may not contain forward slashes DanEngelbrecht/golongtail
2 participants
@DanEngelbrecht @AOOSG