git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [JGIT PATCH] On error in DirCache.lock, do not leave the index locked.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Aug 18, 2008, 05:46 UTC
Message-ID
<20080818054600.GA7376@spearce.org>
In-Reply-To
<1218922587.30527.2.camel@isidore.myhome.westell.com>
"John J. Franey" <jjfraney@gmail.com> wrote:
Show 5 quoted lines
> After using C git on the same repository, the jgit cache read
> threw an EOFException, and left the index lock file.
> The repository is still valid according to C git, but
> unreachable by C git because it honors the lock file
> left behind by jgit.
Urgh.  Thanks for the patch.
 
>  The reason for the EOFException is beyond me right now.  It
>  reported "Short read of block."  However, I'm pretty sure
>  leaving the lock file in place is an error.
If you can reproduce it, I'd like to see a copy of the index file
if that is possible.  I was pretty certain DirCache honors the
index file format properly, but a short read of a block suggests
we misread a length field somewhere.
 
-- 
Shawn.
Previous: John J. Franey
Message 2 of 2 in “On error in DirCache.lock, do not leave the index locked.”
  1. On error in DirCache.lock, do not leave the index locked.John J. Franey, Aug 16, 2008
  2. Shawn O. PearceAug 18, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.