8

We've been seeing a dialog pop up when using SourceTree with a particular Git repository of ours, with the error message:

'Summary' failed with code 128: fatal: unable to read tree 152c27e57424de6ae0df1f0d32feba7beae6e2fb

The error message pops up multiple times per day.

There is no additional information in the log, and we can't reproduce the error message using Git on the command line. When we run a few tests:

Craig@DEMO-PC /d/project (major) $ git cat-file -t 152c27e tree Craig@DEMO-PC /d/project (major) $ git cat-file -p 152c27e 040000 tree 174f073109a9d0721b35e84140d0a7b29dc48ef9 main 040000 tree fb011d0153c1521441d583196a93f945dcb0df1e test 

A run of git ls-tree -r 152c27e spits out all the children of the tree, which confirms it is the src folder of our Java project.

Further, a git fsck --full succeeds without errors. The objects and object directories are 100% in shape, and there are no dangling items. Permissions for the objects seem fine.

Is there anything we can do to double-check the status of our repository, or to attempt to reproduce the error message?

7
  • Have you try git show 152c27e57424de6ae0df1f0d32feba7beae6e2fb? Also it looks like a SourceTree specific problem, you might have more chance to ask their direct support. Commented Sep 30, 2013 at 14:46
  • Yes, a git show just shows three lines: tree 152c273, main/, and test/. The reason I ask here is the error dialog shown is obviously a Git error message, but I don't know if the cause of the message is a Git issue, or a SourceTree issue. I'm just trying to reproduce whatever command they're running that is causing problems. Commented Sep 30, 2013 at 16:46
  • You could try to grep git sources (and SourceTree source code, if available) to find if it is a source of said error message. Commented Oct 1, 2013 at 9:20
  • It may be a issue with embedded git and system git. Try to upgrade in Tools->options menu (Note : Totally untested) Commented Oct 2, 2013 at 4:49
  • Does the same error appear when you git clone the repository and use that with SourceTree? Commented Oct 3, 2013 at 15:13

1 Answer 1

7
+200

It could be possible that it is a permission issue, where:

  • the permission look fine from a current user point of view
  • the permission isn't fine from the account running SourceTree

There was a similar case reported back in February 2013, without any answer.
But it isn't limited to SourceTree:

Wiping out the workspace solves the problem completely.

somehow the private key Redmine uses to authenticate with the git user got renamed within the gitolite config.

So this is generally related to a process accessing data as a different user than the one expected.

Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.