-
Notifications
You must be signed in to change notification settings - Fork 413
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
invalid argument when using git-sync v4 with GitLab repository #919
Comments
For some more context: we tried to test the same git-sync call (as far as is possible) against a private github repository (access token, using the main branch, same gitsync 4.x etc.), which worked without problem. |
I'm going to need you to post all of the flags that you used to try to reproduce this. We have a battery of end-to-end tests, so you must be doing something that I have not considered before. Ideally, you could run your sink with '-v6' and post the full logs here. That will show me the command line arguments, which commands it executed and what the results of them were. |
Thanks for your answer! This is the command with all the flags we're using right now: git-sync --repo=<GITLAB_REPO_URL> --ref=main --depth=1 --period=20s --link=current --root=/tmp/git --verbose=6 --git-config='safe.directory:/tmp/git,http.sslVerify:false' The corresponding logs are:
We are running git-sync in a sidecar container to our pod. |
It looks.like readlink() is legitimately failing. Can you run |
Can you run it with the container Which exact version of git-sync is this? Are you mounting a volume somewhere? |
We are using git-sync v4.2.1 and are mounting an emptyDir volume on /tmp/git to make the synced files available to another container in our pod. When running the command by hand, it tries multiple times to sync the data. We stopped it after a few tries and it did actually download our data from git successfully. Here are the logs:
|
That log seems to indicate a smashing success. Something has to be different... |
The only way I can reproduce the readlink "invalid argument" error is if I force the symlink to be a non-symlink. There's SOMETHING in that directory that is colliding. |
Any update on this? |
We will be using an older version of git-sync that is working for us as a workaround for now. Thank you anyways for your help |
If I cannot reproduce this and I can't get further information, I am forced to close this. If it is actually a bug in git-sync, you will be stuck on an old version forever, until I can fix it. |
We updated git-sync from v3 to v4. Previously it ran without any issues, however after the update, the git-sync sidecar container of our pod crashes with the following errors:
"command result","stdout":"","stderr":"notice: HEAD points to an unborn branch (git-sync)\nnotice: No default references"
....
"msg":"too many failures, aborting","error":"readlink /tmp/git/current: invalid argument","failCount":1
Authentication is done via an access token (tested in local git). Git-sync does not work either on our commit branch nor on the main branch of the private repo. Do you have any ideas what might be the cause of the issue?
The text was updated successfully, but these errors were encountered: