search

phphenrique / egit

Automatically exported from code.google.com/p/egit
0 stars 0 forks source link

EGit repository change scanner locked up workspace after doing a commit externally #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I haven't been able to reproduce this recently, but doing a commit
externally with git-commit at just the right time can cause the repository
scanner to lock the workspace by never completing its job.  The result is
the workspace must be killed externally with `kill -9`.

I didn't get a chance to look at the workspace log from this, to see if
there was an exception or not.  Its possible we caught an exception then
never completed the job.

Original issue reported on code.google.com by shawn.pe...@gmail.com on 25 Aug 2008 at 4:52

GoogleCodeExporter commented 8 years ago

Original comment by shawn.pe...@gmail.com on 25 Aug 2008 at 5:02

GoogleCodeExporter commented 8 years ago 
I can confirm this, but haven't repeated it yet. Not just commits, but a branch 
swich
(and so I assume any ref change) can cause this.

Original comment by robin.ro...@gmail.com on 26 Aug 2008 at 5:36

GoogleCodeExporter commented 8 years ago 
Close as "old"?

Original comment by robin.ro...@gmail.com on 8 Apr 2009 at 3:57

GoogleCodeExporter commented 8 years ago 
Old bug, little information, yea, closed with no action.

Original comment by sop+code@google.com on 8 Apr 2009 at 4:16