Community
Participate
Working Groups
Build Identifier: Helios (20100617-1415), JGit 0.9.0.201007291517 While merging from origin/master into my master branch, I happened to get the following Exception: org.eclipse.jgit.api.ConcurrentRefUpdateException: Could not lock HEAD. RefUpdate return code was: LOCK_FAILURE at org.eclipse.jgit.api.MergeCommand.updateHead(MergeCommand.java:201) at org.eclipse.jgit.api.MergeCommand.call(MergeCommand.java:144) at org.eclipse.egit.core.op.MergeOperation$1.run(MergeOperation.java:103) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957) at org.eclipse.egit.core.op.MergeOperation.execute(MergeOperation.java:124) at org.eclipse.egit.ui.internal.repository.tree.command.MergeCommand$1.run(MergeCommand.java:90) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) As a result my master branch is not visible anymore (neither in msysgit nor in egit) and gitk complains about "unknown revision HEAD", so apparently this reference is lost as well. Whatever caused this concurrent access, I wasn't using anything else than egit (i.e. not command line tools in parallel etc.). Reproducible: Couldn't Reproduce Steps to Reproduce: In EGit: 1. checkout master 2. fetch origin 3. merge from origin/master into master
just another detail that might be helpful: the .git/refs/heads/master file got lost. The .git/HEAD file still exists and is pointing to refs/heads/master
Simon: is this one still valid? We talked about one bug but I don't think that is this one.
Indeed, it's not the one we talked about. This one isn't reproducible, so I cannot really tell if it's still valid. It didn't happen again, so it doesn't really bother me.