Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356764 - improve usability of lock failure
Summary: improve usability of lock failure
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-06 03:33 EDT by Maxime Jeanmart CLA
Modified: 2015-03-27 05:00 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Jeanmart CLA 2011-09-06 03:33:07 EDT 
Build Identifier: 1.0.0.201106090707-r

Trying to access a repository whose lock wasn't released fails with the following message using eGit: 
"Exception caught during execution of merge command. java.io.IOException: Cannot lock D:\Personal Folder\My Documents\git\source\types\.git\index
Exception caught during execution of merge command. java.io.IOException: Cannot lock D:\Personal Folder\My Documents\git\source\types\.git\index"

Not knowing what to do, I decided to try using Tortoise GIT. This tool gave me a much better message: 
"fatal: Unable to create 'd:/Personal Folder/My Documents/git/source/types/.git/index.lock': File exists.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue."

Now I know what to do. Could you please improve the message by telling the user how to solve the issue? Thanks

Reproducible: Always

Steps to Reproduce:
1.create index.lock file in the .git folder of a repository
2.try to pull
Comment 1 Philip Langer CLA 2015-03-27 05:00:27 EDT 
Sounds like a dupe of bug 339781