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

sync in version 1.10.1 does not work with sub folders #88

Open
2 of 9 tasks
tlamb-hni opened this issue Jun 26, 2024 · 3 comments
Open
2 of 9 tasks

sync in version 1.10.1 does not work with sub folders #88

tlamb-hni opened this issue Jun 26, 2024 · 3 comments

Comments

@tlamb-hni
Copy link

tlamb-hni commented Jun 26, 2024

Describe the bug in a sentence or two.

When using 1.10.1 if your cloudinary path is a sub folder, it will fail not sync the folder. (Note my cloudinary instance is using fixed folder mode, not sure if that matters).

Issue Type (Can be multiple)

  • Build - Cannot install or import the SDK
  • Performance - Performance issues
  • Behaviour - Functions are not working as expected (such as generate URL)
  • Documentation - Inconsistency between the docs and behaviour
  • Other (Specify)

Steps to reproduce

Run something like : cld sync --pull . "My Root Folder/Sub Folder 1" . It will report it fails to find any items in the cloudinary folder. I Rolled back to version 1.10.0 and then it successfully finds the files in the folder.

Operating System

  • Linux
  • Windows
  • macOS
  • All

Environment and Frameworks (fill in the version numbers)

  • Cloudinary CLI version - 1.10.1
  • Cloudinary Python SDK version - 1.40.0
  • Python Version - 3.12.4
@skalahasti-cloudinary
Copy link

Hi @tlamb-hni ,

Thanks for reporting this. I verified in my account too and behaves the same way. I will reach out to the concerned team and keep you posted accordingly.

Thanks,
Sree

@kaestlyn
Copy link

Was this fixed in the 1.10.2 release?

@skalahasti-cloudinary
Copy link

skalahasti-cloudinary commented Jul 17, 2024

Hi @kaestlyn and @tlamb-hni,

Yes. This has been fixed in 1.10.2 Release. Please test now.

Thanks,
Sree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants