aem-core-cif-components icon indicating copy to clipboard operation
aem-core-cif-components copied to clipboard

Not able to clone repo in windows

Open nishneo opened this issue 3 years ago • 3 comments

Expected Behaviour

Should be able to clone repo.

Actual Behaviour

Not able to clone due to Filename too long.

Steps to Reproduce

  1. Go to https://github.com/adobe/aem-core-cif-components
  2. Click on Clone button and select Open with GitHub Desktop

Platform and Version

Windows

Logs taken while reproducing problem

Cloning into 'C:\Users\aswaroop\Documents\GitHub\aem-core-cif-components4'... remote: Enumerating objects: 30846, done. remote: Counting objects: 100% (1989/1989), done. remote: Compressing objects: 100% (977/977), done. remote: Total 30846 (delta 722), reused 1466 (delta 496), pack-reused 28857 Receiving objects: 100% (30846/30846), 15.75 MiB | 3.98 MiB/s, done. Resolving deltas: 100% (13159/13159), done. warning: unable to access 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png.dir/.gitattributes': Filename too long error: unable to create file examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png.dir/.content.xml: Filename too long warning: unable to access 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.319.319.png.dir/.gitattributes': Filename too long error: unable to create file examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.319.319.png.dir/.content.xml: Filename too long warning: unable to access 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.48.48.png.dir/.gitattributes': Filename too long error: unable to create file examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-sample-assets/catalog/product/bolo-sport-watch/wg01-bk-0.jpg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png: Filename too long fatal: cannot create directory at 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-sample-assets/catalog/product/bolo-sport-watch/wg01-bk-0.jpg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png.dir': Filename too long warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry with 'git restore --source=HEAD :/'

Workaound

Can set longpaths in git configs but not all developers/qa have admin access to do the changes.

nishneo avatar Apr 07 '22 12:04 nishneo

In order to workaround the issue for users that don't have permissions to update the system or global git configuration, longpaths can also be enabled in the local repository:

git config core.longpaths true

afterwards retry according to the above message

git restore --source=HEAD :/

Does that work for you?

buuhuu avatar Apr 07 '22 12:04 buuhuu

Thanks, @Buuhuu, it works.

del27634 avatar Apr 07 '22 12:04 del27634

Thanks, we should anyhow verify if we need those paths (the renditions) or if we can remove them.

buuhuu avatar Apr 07 '22 13:04 buuhuu