-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Failed to execute git command: exit status 128 #3294
Comments
I figured out the |
Please show gogs log as required. |
I created another test in order to provide the full sequence along with the corresponding log statements:
I then ran Here's the part of the log that corresponds to the transaction:
|
Please dump logs in |
This is the
And just in case ...this is the
|
Gogs version? |
0.8.42.0222 |
I'm assuming that's the version. I got it from running
|
Your Gogs version is far too old, please upgrade. |
Yup - I just realized that it did not pull the upgrade the first time I attempted it. I just did a fresh image pull and I still get this error:
|
You can only go git push/pull after web UI is available to visit, from the log does not seem so, the migration is not finished. |
Yes it did finish. I created the repository |
I guess it might be problem with volumed directory. cc @0rax |
It seems like it's a protocol issue. If I do
|
Hi there, I have multiple question for you as I am not able to reproduce even the clone via 'git@realm:orax/repo'. Using just this url will ask me for a password, using Via What is your local I am really wondering how it is registered in your side via git / why you are able to clone without specifying the Can you give us the output of Also can you check your Thanks :) |
Hi Jean,
Gogs version from logs:
Git config:
So now I'll visit my gogs URL (203.0.113.1:3000) and create a repo:
Then clone it, etc:
FAILURE:
SUCCESS:
|
Thanks that's perfect, I will try to reproduce this with those exact version & git configuration ! Will keep you informed here ! |
Cool thanks - let me know if you need anything else 👍 I am using an SSH key which I'm sure you already guessed. |
Just run this test in a ubuntu:14.04 container and on my Mac. Which contains the same version of git as you. Note that I have my ssh port set to 2222 on my instance of Gogs, thus requiring me to create an ssh_config telling git & ssh to use port 2222 by default as the syntax you are using to clone does not accept a port. An alternative scp-like syntax may also be used with the ssh protocol:
o [user@]host.xz:path/to/repo.git/
This syntax is only recognized if there are no slashes before the first colon. This helps
differentiate a local path that contains a colon. For example the local path foo:bar could be
specified as an absolute path or ./foo:bar to avoid being misinterpreted as an ssh url. Ubuntu 14.04
OSX$ git config --global push.default matching
$ git version
git version 2.9.0
$ echo -e "Host gogs.my.fqdn\n\tport 2222" >> ~/.ssh/config
$ git clone [email protected]:/orax/test-repo.git /tmp/test-repo
Cloning into '/tmp/test-repo'...
warning: You appear to have cloned an empty repository.
Checking connectivity... done.
$ cd /tmp/test-repo
$ echo '# Test-Repo' >> README.md
$ git add README.md; git commit -m 'README'
[master (root-commit) 0a666c2] README
1 file changed, 1 insertion(+)
create mode 100644 README.md
$ git push
No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
Gogs: Internal error
Failed to execute git command: exit status 128
error: failed to push some refs to '[email protected]:/orax/test-repo.git'
$ git config --global push.default current
$ git push
Counting objects: 3, done.
Writing objects: 100% (3/3), 229 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To [email protected]:/orax/test-repo.git
* [new branch] master -> master ConclusionThis problem seems to happen with the EDIT: I stand corrected, this also happen with the standard |
Sorry for the delayed response. Great work BTW. Definitely hit the bullseye. I tested this out with the latest container and the |
This is still a bug in gogs_v0.9.48_linux_amd64.tar.gz
|
@olafure: so this is also happening on non Docker distribution right ? I might have expected that but wasn't sure as I did not have any time to setup a barebone gogs instances. |
I recently upgraded to the most recent docker build. Now when I clone and push to a new repository I get this when running
git push
:This is only when using the
git
protocol. If I use thehttp
protocol I can clone and push, but when pushing I have to specifyorigin master
like thisgit push origin master
. I can't just writegit push
, which I think used to work before.The text was updated successfully, but these errors were encountered: