git завершил выполнение некорректно код завершения 128
Как разрешить ошибку» git не вышел чисто (код выхода 128) » на TortoiseGit? [закрытый]
Я столкнулся с этой серьезной ошибкой при совершении, и создал отчет об ошибке.
Я продолжаю получать эту ошибку на операциях TortoiseGit:
git не вышел чисто (код выхода 128)
14 ответов:
Это, вероятно, потому, что ваш SSH ключ был скомпрометирован. Сделайте новый и добавьте его в свою учетную запись GitHub.
для меня я просто должен был добавить настроить имя пользователя Git и электронной почте с помощью следующей команды:
отчеты git-bash фатально: невозможно создать ‘/.git / index.замок’: файл существует.
удаление индекса.блокировка делает ошибку уйти.
в моем случае причиной сбоя стала папка в моем каталоге, названная git-репозиторием на сервере.
удалить, и ошибка 128 уходит. Удивительно, что tortoisegit не дает такого простого объяснения.
удаление индекса.замок работал на меня
в моем случае, это из-за прокси. Прокси-сервер был необходим в корпоративной сети, и TortoiseGit / Git, похоже, не автоматически получает информацию из настроек Windows internet. Настройка адреса прокси-сервера решила проблему.
для меня, я попытался проверить SVN-проект с TortoiseGit. Он работал нормально, если я использовал TortoiseSVN, хотя. (Может показаться очевидным, но новички могут наткнуться на это)
в моем случае я забыл добавить git к имени respository в конце.
Я сделал git revert несколько раз, и это сработало для меня убедитесь, что вы не проверяете файлы при возврате вам нужны изменения. Спрячьте свои изменения и потяните снова.
У меня была эта же проблема и я решил ее следующим образом.
У меня установлен NVIDIA «Tegra Android Development Pack», и, похоже, у него также есть версия mysysgit.exe с ним. TortoiseGit автоматически нашел это место установки (вместо стандартной установки git) и автоматически заполнил его в меню настроек.
быстрым решением было бы создать новый локальный каталог, например c:\git_2014, в этом каталоге щелкните правой кнопкой мыши и выберите git Clone
убедитесь, что имя пользователя и адрес электронной почты не пустой в файле config. и попробуйте клонировать в пустой каталог. эти шаги сработали для меня.
How to resolve «git did not exit cleanly (exit code 128)» error on TortoiseGit? [closed]
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
I’ve run into this serious error while committing, and created a bug report.
I keep getting this error on TortoiseGit operations:
git did not exit cleanly (exit code 128)
14 Answers 14
It’s probably because your SSH key has been removed/revoked. Make a new one and add it to your GitHub account.
for me I simply had to add configure my git username and email with the following commands:
git-bash reports fatal: Unable to create
/.git/index.lock : File exists.
Deleting index.lock makes the error go away.
If you’re running windows 7:
I was trying to decide the best way to do this securely, but the lazy way is :
I realize this might circumvent windows «security» features, but it gets the job done.
In my case a folder in my directory named as the git-repository on the server caused the failure.
Deleting index.lock worked for me
delete, and error 128 goes away. It surprises that tortoisegit doesn’t give such an easy explanation.
In my case, it was because of the proxy. A proxy was needed in the corporate network and TortoiseGit / Git does not seems to automatically get information from Windows internet settings. Setting up the proxy address solved the issue.
For me, I tried to check out a SVN-project with TortoiseGit. It worked fine if I used TortoiseSVN though. (May seem obvious, but newcomers may stumble on this one)
In my case, I forgot to add git to the respository name at the end.
I was having this same issue and I resolved it in the following way.
Git завершил выполнение некорректно код завершения 128
Problem Description:
A new space after local git repository, intends to abnormal, specific abnormality as follows when the remote repository to local code Pull:
git did not exit cleanly (exit code 128) (4469 ms @ 2018-07-01 11:13:35)
Solution:
On this issue, approximate solutions, core solutions on a problem encountered in the content are the same»Git did not exit cleanly (exit code 1) solution.»。
1, according to error contents suggest that we need to remove the first local git repository configuration files out to form an empty folder, everything git folders do not appear, and then directly from the remote repository «Git Clone» to project, As shown below:
2, directly from the Clone remote GitHub project, found the Clone successful, as shown below:
3, after Clone project down from the remote, as shown below:
Well, the solution with regard to git did not exit cleanly (exit code 1) would be written here, if you have any questions or encounter any questions please scan code to ask questions, you can give me a message oh, I will be 11 in detail the answer.
Twisters: «common learning and common progress,» I hope you lot of attention CSND the IT community.
TortoiseGit-git did not exit cleanly (exit code 1)
I got this message when i tried to create repository by using Git clone.
21 Answers 21
Try these two commands in git bash:
Right from my experience, I most often get this when I have locally changed files that will be over ridden by the pull, you need to stash or move the files before you can pull it.
Right-click folder -> TortiseGit -> push-> choose unknown changes 》
Actually, this error message just says that there is some problem but no specifications of the problem. So, in my case, it was a pending pull request. I pulled the changes into my repo, and then pushed it again and it worked. Moreover, if there is an error on tortoisegit, I prefer to do the same on console. Console gives more detail error message
Following this guide I had the same issue. To expand on Eric Moore’s ridiculously vague answer,
Right click > TortoiseGit > Settings > Network
Down the bottom in the «SSH» section, hit Browse and find your TortoiseGit\bin\TortoisePlink.exe file. In my case the path was under Programs as opposed to Program Files
None of the above solutions worked for me but this one did.
I ran into the same issue after upgrading Git. Turns out I switched from 32-bit to 64-bit Git and I didn’t realize it. TortoiseGit was still looking for «C:\Program Files (x86)\Git\bin», which didn’t exist. Right-click the folder, go to Tortoise Git > Settings > General and update the Git.exe path.
This is Just because you have made changes on your remote repository which was not pulled on your local repository.
To resolve simply 1. Pull from remote repository to local repository. It will not undo any changes locally. It will just update local repository. 2. Now push the changes to remote repository. It will work
For My case i did 3 steps to achieve the sucessful build.
revert all the local changes if any (or just keep a copy of it in case you need it for future use)
Do a git clean up, do a pull and check the logs for error
For example if the error was something like **
**error: cannot lock ref ‘refs/remotes/origin/EXMPLEISSUE/EXAMPLE-1011_DEMO_web_interface_DOES_NOT_GET_GIT_UPDATE’:
How to resolve “git did not exit cleanly (exit code 1)” error on TortoiseGit? #8
Comments
yapingxin commented Oct 5, 2017
The text was updated successfully, but these errors were encountered:
kaline commented Jan 17, 2018
Did you find a solution? I have an saved user
The same problem here:
Verriva commented Aug 6, 2018
yapingxin commented Aug 10, 2018 •
In my blog, I mentioned that:
oneday, i executed commit & push command through TortoiseGit, but always meed the ‘git did not exit cleanly’ issue.
Usually, I did ‘git cleanup’ to resolve this issue. But that time, the ‘git cleanup’ can not resolve anything. So, I executed ‘git push’ command in git bash shell so that I can get more detailed information. Then, i got the following error message:
fatal: unable to access ‘https://github.com/yapingxin/yapingxin.github.io.git/’: Unknown SSL protocol error in connection to github.com:443
I looked through the internet for the resolution of this issue, then, I found a post in the following URL:
someone said that: It’s probably because your SSH key has been compromised. Make a new one and add it to your GitHub account.
Then, I use ‘git config’ command to re-config my git client account settings. After doing that, my issue gets resolved.
I know you maybe not understanding the Chinese words, but you can read my screenshot, and you can understand what i mean.