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

Doesn't recognize subfolders in vault #11881

Closed
cyberduck opened this issue Oct 22, 2021 · 2 comments · Fixed by #12693
Closed

Doesn't recognize subfolders in vault #11881

cyberduck opened this issue Oct 22, 2021 · 2 comments · Fixed by #12693
Assignees
Labels
bug cli Command Line Interface
Milestone

Comments

@cyberduck
Copy link
Collaborator

d93bd07 created the issue

Hi there,
I have a cryptomator vault folder named "google" on google drive.
and there were some subfolders like "/google/cctv/YYYYMM/"

first of all, duck cli CAN list and upload files in /google/cctv/ folder.
however, duck cli does not recognize /google/cctv/YYYYMM/ folders even with --vault option.

actually, it WORKED months ago. (I don't remember exact date but I'm sure that it worked)
after I updated duck cli recently, it doesn't work anymore.

Full screenshot is attached.
username and authenticating strings are masked.
vault_err.png

ps.
If I access same folder with mountain duck, the absolute path does not match with duck CLI.
I don't know why but it might be one of reason for this bug?
vault_err2.png

Thank you.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone closed

@dkocher dkocher modified the milestones: 8.2, 8.2.1 Dec 6, 2021
dkocher added a commit that referenced this issue Dec 21, 2021
@dkocher
Copy link
Contributor

dkocher commented Dec 21, 2021

Reproduce with S3

duck --vault /test-eu-west-2-cyberduck/vault --upload s3:/test-eu-west-2-cyberduck/vault/11881/ /Users/dkocher/Desktop/cryptomator_256.png --verbose

dkocher added a commit that referenced this issue Dec 21, 2021
dkocher added a commit that referenced this issue Dec 21, 2021
…ey and do not rely on default path which may be inaccessible due to vault. Fix #11881.
@dkocher dkocher linked a pull request Dec 21, 2021 that will close this issue
dkocher added a commit that referenced this issue Dec 22, 2021
dkocher added a commit that referenced this issue Dec 22, 2021
Review default path usage when opening connection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug cli Command Line Interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants