Note that there are some explanatory texts on larger screens.

plurals
  1. POIs git grep buggy - disable parallel search?
    text
    copied!<p>If I run a <code>git grep</code> command n times, I get errors about 0.8 * n times.</p> <pre><code>$ git grep foo_bar_search `git rev-list HEAD` -- dir/subdir &gt;/dev/null fatal: unable to read tree (bc9e3369c6d6f027075e794fa11db02af3f8fb38) $ git grep foo_bar_search `git rev-list HEAD` -- dir/subdir &gt;/dev/null fatal: unable to read tree (473a47dd3895b1db09baf4cf9463f4cbd224d5dd) $ git grep foo_bar_search `git rev-list HEAD` -- dir/subdir &gt;/dev/null $ git grep foo_bar_search `git rev-list HEAD` -- dir/subdir &gt;/dev/null fatal: unable to read tree (b917adbfffd1928c8f6ac0f746a4fdfcf2088029) $ git grep foo_bar_search `git rev-list HEAD` -- dir/subdir &gt;/dev/null fatal: unable to read tree (473a47dd3895b1db09baf4cf9463f4cbd224d5dd) </code></pre> <p>What I've tried</p> <ol> <li>run as superuser to exclude any problems with file protections</li> <li><code>git fsck</code> reports nothing bad just a couple of dangling objects</li> <li>cloned the repo, no errors on cloning, but <code>git grep</code> shows the same behavior in the clone again.</li> <li>look at some of the reported SHA1s using <code>git cat-file</code>, seem to be all fine</li> <li>Googled a bit</li> </ol> <p>The most interesting Google hit was: </p> <p><a href="http://www.spinics.net/lists/git/msg164520.html">http://www.spinics.net/lists/git/msg164520.html</a></p> <p>The message was just 3 hours old. Well, if they have race conditions in <code>git grep</code>, that could explain everything. So do they do search in parallel on several cores? (I have 4 here.) How could I disable that, short of booting the whole machine with only 1 core? </p> <pre><code>$ git --version git version 1.7.3.4 </code></pre> <p>(That's what came with OpenSUSE 11.4)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload