I am using the latest version of the github desktop app(3.0.4) on a windows 10 machine. Recently, I am not being able to make commits. When trying to commit, the app goes to "committing" mode(loading..) and then nothing happens. It does not work when I try to commit a single file also.
I wrote to the GitHub team and this is what they had to say.
It looks like you're running into an out of memory exception:
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
Unfortunately GitHub Desktop does have some edge cases that can cause an OoM -- mainly when working with a large amounts of commits or larger files. We're working on fixing performance to reduce these edges cases, but in the meantime I would try committing directly from the Git Shell:
Hit ~ to open up the repository in the Git Shell
Run 'git add -A' to stage the changes
Run 'git commit -m "your commit message here"' to commit the changes
I haven't faced the problem again after I updated the desktop app(3.0.9.0 now).
I am seeing something similar when I "push" the changes to the remote (GitHub) after I upgraded to Windows 10 it seems to hang. It is like the "GitHub Desktop" application never comes back to confirm the push, but if I close the application and then open it again I can see that the "push" did happen at the time when I pressed the Sync button.
When I use the GitBash it works fine and fast. If I had the GitHub Desktop application running while doing this push from GitBash and now do a Sync the changes show up fast in the GitHub Desktop application but it keeps "Syncing" forever.
Related
Getting this issue in spring tool suit while fetching/pull latest changes from remote branch. i don't have git bash on my local previously it was working fine right now i am getting below mention issue.
Couldn't lock local tracking ref for update
I also encountered same problem
But I removed this problem using GITHUB Desktop tool.
Once I executed pull from STS, its showed the dialog box with error as shown above. and a up arrow got appended showing there are some commit to be pushed,
though I had not made any commits before this pull. The changes from pull were not added to my local project.
I checked on Github Desktop, and it also showed same arrow.
I pushed it from tool, and it was resolved. The changes from pull got added to local project.
While you don't have git bash, Eclipse is using its own JGit (java-based implementation of Git)
As recommended in "egit lock fail eclipse", do check if you have any "<refname>.lock" file under .git/refs/". (howlger refers to eclipse issue 417860:
I checked in jgit and egit sources and found that the only occurrence of the text "[lock fail]" is used when fetch fails to update a remote tracking branch.
This can happen if a previous crash didn't cleanup a "<refname>.lock" file which git creates as a lock to guard the ref against concurrent updates.
git remote prune origin
solved same problem for me
I used Github Desktop to perform a complex merge and now I've noticed that my terminal is not picking up any changes when I run:
git status
I need to first push the code up to origin using Github Desktop, then pull down in my terminal in order for the changes to take place.
Has anyone seen this before?
It appears that github desktop somehow made a clone of the repo in a new location which is why my terminal wasn't locating the file changes. The github desktop repo was located at: /Users/NAME/Documents/GitHub/repo-name. I'm sure this is something I screwed up during setup but figured I'd throw this out there in case it helps anyone!
I recently created a website using blogdown and now hosting it on a GitHub repository and netlify to deploy. When I set it up, I followed the directions to clone my GitHub repository to be able to commit files using the git version control. So making changes within Rmarkdown and then committing them to my GitHub repository was easy.
However, when I connect to the project now, the window where I can commit changes does not appear. That is, I no longer have the option to commit changes within R studio. My guess is that the connection between the terminal and GitHub was changed/removed? Does anyone know how to re-establish this? I've looked up the syntax to use in the terminal, but I couldn't find a similar problem - that is, re-establish the connection between my GitHub with an already existing project already on my desktop.
Posting an answer to this question in the case others have a problem. It was an issue with MojaveOS. You have to re-install command line tools in the terminal.
xcode-select --install
Doing this, the version control now works to commit files to my github repository.
I have been forced to use other apps, and the command line since Github for Windows is not allowing me to commit changes. I would like to understand what's the problem, but I simply get a prompt with this message:
Commit failed
Failed to create new commit
Then, it gives me the option of go to the Git Shell or to cancel. While I am not an expert with the terminal, I am able to make commits when I choose to go to the Git Shell (or to any other application for that matter).
I am using Github 2.0.5 on Windows 7.
After an exchange with the Github for Windows developers, the issue has something to do with Windows inability to work with paths when they're too long. The node_modules folders generated by Node.js is the culprit of this issue in my particular case.
However, the node_modules folders in my repository are gitignored. The fact that even when gitignored they create a problem in Github for Windows means the developers have to address the situation.
I expect a response or a patch from the developers soon. They have been very helpful. In the meantime, I am using SourceTree as my Windows Git GUI.
I'm trying to clone a remote repository via SSH using EGit.
I've made some progress by setting http.sslverify to false and turning up the remote connection timeout.
Now the cloning makes progress, through "resolving deltas", but then hangs Eclipse with a full "loading" bar. There is no label on the bar and no apparent way to cancel the operation without force-quitting Eclipse.
I'm running Eclipse 3.7.0 and Mac OS 10.5.8.
Any ideas? I'm not sure what to do because I have no error message -- just no progress.
(BTW, I originally posted this as an "answer" in another thread. My post was deleted. I apologize for the breach of etiquette and can only say that I'm new here. I'm a bit perplexed that I didn't get any notification that my post had been deleted; I had to search again to find the thread and scroll down to see the message.)
Peter, just curious as to where you host your repository? If you had a timeout issue, it's possible the host has even more issues.
Have you tried running the git clone from the command line and use EGit only for the "mundane" tasks? It's not ideal, but being able to do it from the command line usually saves a lot of trouble, and if it fails the error messages are very clear about why.
I've used EGit a while, but went back to just opening a terminal and doing the sacro-sanct
git commit -a
git fetch origin/master (or whatever your branch is)
git merge
git push
EGit tends to fail for weird reasons. And when using with Github it becomes a nightmare to set it up to use SSH keys.