-
Notifications
You must be signed in to change notification settings - Fork 7
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
Manually escaping --target-path for network share on Windows. #249
Comments
Maybe it gets confused since you don’t provide a drive letter on the target path? |
It's a network share and doesn't have a drive letter. |
Ok, I will have a look, it probably gets confused trying to find the root folder. |
Noticed similar issue on other commands where it also works if I put in 4 backslashes:
Using only 2 backslashes like
|
- **FIXED** Networks share paths that starts with \\ no longer need to be manually escaped (fixes #249) - **UPDATED** Update longtaillib to v0.4.2
Hello,
I just tried out this cool tool after a friend recommended it. On my first test run I think I ran in to a bug. Here is the command I ran:
longtail upsync --log-level=debug --source-path="C:\musik" --target-path="\\vault\backup\longtail\index\2024-02-26.lvi" --storage-uri="\\vault\backup\longtail\store"
The command succeded and it filled the store with files, but the index file
2024-02-26.lvi
never ended up on that path. Even though the debug showed this:I managed to make it work by manually escaping every backslash in the
--target-path
.:longtail upsync --log-level=debug --source-path="C:\musik" --target-path="\\\\vault\\backup\\longtail\\index\\2024-02-26.lvi" --storage-uri="\\vault\backup\longtail\store"
So only manually escaping the path for the
--target-path
, but not for the store. I think the scary part is that it silently succeded. This workaround works for me but I wanted to report it anyway.Thank you!
The text was updated successfully, but these errors were encountered: