git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lucas Araki <lucas.t.araki@gmail.com>
To: git@vger.kernel.org
Subject: Error: error converting ".git" to absolute: EvalSymlinks: too many links
Date: Thu, 9 Sep 2021 14:31:34 -0400	[thread overview]
Message-ID: <CALM-bLiWrJQnU3M5ToQo+72hvToHRknfvH5RVy2zHUgnnsdpXg@mail.gmail.com> (raw)

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
Attempted push operation

What did you expect to happen? (Expected behavior)
push operation success, no error message

What happened instead? (Actual behavior)
Push operation failed with error message:
Error: error converting ".git" to absolute: EvalSymlinks: too many links
ref feature/feature_name:: EvalSymlinks: too many links
error: failed to push some refs to 'https://my_server_name/my_project.git'

In addition, lfs/ directory was created in project folder instead of
.git folder.

What's different between what you expected and what actually happened?
Did not expect lfs/ directory to be created in project folder.
Don't expect error on push operation.

Anything else you want to add:
After reading issues #4050 and #4012, attempted:
`git lfs env` and got output:
git-lfs/2.13.3 (GitHub; windows amd64; go 1.16.2; git a5e65851)
git version 2.33.0.windows.2

Error: error converting ".git" to absolute: EvalSymlinks: too many links
Endpoint=https://my_server_name/my_project.git/info/lfs (auth=basic)
LocalWorkingDir=
LocalGitDir=
LocalGitStorageDir=
LocalMediaDir=lfs\objects
LocalReferenceDirs=
TempDir=lfs\tmp
ConcurrentTransfers=8
TusTransfers=false
BasicTransfersOnly=false
SkipDownloadErrors=false
FetchRecentAlways=false
FetchRecentRefsDays=7
FetchRecentCommitsDays=0
FetchRecentRefsIncludeRemotes=true
PruneOffsetDays=3
PruneVerifyRemoteAlways=false
PruneRemoteName=origin
LfsStorageDir=lfs
AccessDownload=basic
AccessUpload=basic
DownloadTransfers=basic,lfs-standalone-file
UploadTransfers=basic,lfs-standalone-file
GIT_EXEC_PATH=C:/Program Files/Git/mingw64/libexec/git-core
git config filter.lfs.process = "git-lfs filter-process"
git config filter.lfs.smudge = "git-lfs smudge -- %f"
git config filter.lfs.clean = "git-lfs clean -- %f"


Realized that project was in Box drive folder, set to keep local copy,
but based on issues #4050 and #4012, decided to try moving project to
a different local location.
I copied entire project directory our of Box folder, then re-ran `git
lfs env` and got output:
git-lfs/2.13.3 (GitHub; windows amd64; go 1.16.2; git a5e65851)
git version 2.33.0.windows.2

Endpoint=https://git.elsys.gtri.org/scm/tads/tads-suite-test-plan.git/info/lfs
(auth=basic)
LocalWorkingDir=C:\Users\username\myProject
LocalGitDir=C:\Users\username\myProject\.git
LocalGitStorageDir=C:\Users\username\myProject\.git
LocalMediaDir=C:\Users\username\myProject\.git\lfs\objects
LocalReferenceDirs=
TempDir=C:\Users\username\myProject\.git\lfs\tmp
ConcurrentTransfers=8
TusTransfers=false
BasicTransfersOnly=false
SkipDownloadErrors=false
FetchRecentAlways=false
FetchRecentRefsDays=7
FetchRecentCommitsDays=0
FetchRecentRefsIncludeRemotes=true
PruneOffsetDays=3
PruneVerifyRemoteAlways=false
PruneRemoteName=origin
LfsStorageDir=C:\Users\username\myProject\.git\lfs
AccessDownload=basic
AccessUpload=basic
DownloadTransfers=basic,lfs-standalone-file
UploadTransfers=basic,lfs-standalone-file
GIT_EXEC_PATH=C:/Program Files/Git/mingw64/libexec/git-core
git config filter.lfs.process = "git-lfs filter-process"
git config filter.lfs.smudge = "git-lfs smudge -- %f"
git config filter.lfs.clean = "git-lfs clean -- %f"

Noticed that LocalGitDir looked correct and was no longer blank.
Re-tried `git push` from new project location and push operation succeeded.

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.33.0.windows.2
cpu: x86_64
built from commit: 8735530946cced809cc6cc4c2ca3b078cdb3dfc8
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19042
compiler info: gnuc: 10.3
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>


[Enabled Hooks]
post-commit
post-checkout
post-merge
pre-push

             reply	other threads:[~2021-09-09 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 18:31 Lucas Araki [this message]
2021-09-10 11:11 ` Error: error converting ".git" to absolute: EvalSymlinks: too many links Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALM-bLiWrJQnU3M5ToQo+72hvToHRknfvH5RVy2zHUgnnsdpXg@mail.gmail.com \
    --to=lucas.t.araki@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).