Getting error while clonnig branch

0
Hi Everyone, I am getting below error while clonning branch :   Failed to checkout remote repository. LibGit2Sharp.NameConflictException: 'C:/Users/******/Mendix/EAM-App (Elektronik Anlaufmanagement)-vwits-204_Himanshi' exists and is not an empty directory   at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 155   at LibGit2Sharp.Core.Ensure.ZeroResult(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 173   at LibGit2Sharp.Core.Proxy.git_clone(String url, String workdir, GitCloneOptions& opts) in /_/LibGit2Sharp/Core/Proxy.cs:line 278   at LibGit2Sharp.Repository.Clone(String sourceUrl, String workdirPath, CloneOptions options, ProxyOptions proxy) in /_/LibGit2Sharp/Repository.cs:line 854   at Mendix.Modeler.VersionControl.Actions.Git.Requests.Clone.GitCloneLibGitRequest.ExecuteRequest() in Mendix.Modeler.VersionControl.Git\Actions\Requests\Clone\GitCloneLibGitRequest.cs:line 56
asked
2 answers
0

The error is about a directory that already exists and is not empty, so make sure that you really are cloning to a new folder.

 

However, by looking at the folder I think the folder may simply be too long.

I use C:\Mendix to place my Mendix projects in. So each Mendix app in its own folder under C:\Mendix

Also, when cloning the app you could leave out the ' (Elektronik Anlaufmanagement)' part in your local folder name. You can change that, it is not part of the changes you sync to the repo

 

Another issue with using your profile folder for Mendix projects is that the folder may be synced if you have a roaming profile or your profile data is included in OneDrive sync. 

Mendix really does not work well under these conditions. Your work gets committed to a repository, your local clone should not be included in some cloud sync or backup tool.

I can't tell whether that is the case in your setup but I have seen many issues coming from using a folder in your Windows profile for Mendix apps

answered
0

The solution to this issue is different.

 

The issue is with long file paths in the git cloning and rebasing process. That is not something which can be fully avoided.  For e.g. the node_modules folder structure. This may not be in your project because of something you created but it is there because the buildpack for styling modules in Mendix uses it.

 

a simple fix is by setting a global git config.

 

git config --global core.longpaths true

 

The above command ensures that long paths are handled correctly.

answered