I hit the same issue. Here is the diff (RB 2.5.4, git 2.7.3):

# diff -u git.py.orig git.py 
--- git.py.orig 2016-08-23 12:56:07.375683157 +0200 
+++ git.py 2016-08-23 12:57:24.079225312 +0200 
@@ -634,6 +634,8 @@ 
         if failure: 
             if errmsg.startswith("fatal: Not a valid object name"): 
                 raise FileNotFoundError(commit) 
+            elif errmsg.startswith("fatal: git cat-file: could not get 
object info"): 
+                raise FileNotFoundError(commit) 
             else: 
                 raise SCMError(errmsg)



понедельник, 8 августа 2016 г., 21:06:19 UTC+3 пользователь David 
Trowbridge написал:
>
> Oh, OK, I see what you mean now. Can you either create a patch to handle 
> the new error message coming from git or file a bug about this?
>
> -David
>
> On Mon, Aug 8, 2016 at 2:32 AM fluzz <degrand...@orange.fr <javascript:>> 
> wrote:
>
>>
>>
>> Le dimanche 7 août 2016 20:02:06 UTC+2, David Trowbridge a écrit :
>>>
>>> It actually looks like the locally synchronized copy on the review board 
>>> server has some corruption (the "bad file"). I'd suggest doing a new full 
>>> clone.
>>>
>>> -David
>>>
>>>
>> I tried this simple test on a fresh new empty repository:
>>
>>     mkdir t1
>>     cd t1
>>     git init .
>>
>>     echo "1st line" > test.t
>>     git add test.t
>>     git commit -m "Add test.t"
>>
>>     echo "2nd line" >> test.t
>>     git add test.t
>>     git commit -m "Add second line"
>>
>>     cd ..
>>     cp -R t1 t2
>>
>>     cd t1
>>
>>     echo "3rd line" >> test.t
>>     git add test.t
>>     git commit -m "Add third line"
>>       --> commit is f7822b0ead90833f1a337b3003d6b0b0ba5d70d1
>>     git diff-tree f7822b0ead90833f1a337b3003d6b0b0ba5d70d1
>>       --> :100644 100644 7d91453217afc429984c4706e8df22aaac47c9ce 
>> 6da4d3e0a797240aefaa9c8009e49c57ded3b59e M    test.t
>>
>>     git cat-file -t 6da4d3e0a797240aefaa9c8009e49c57ded3b59e
>>       --> blob
>>
>>     cd ../t2
>>
>>     git cat-file -t 6da4d3e0a797240aefaa9c8009e49c57ded3b59e
>>       --> fatal: git cat-file 6da4d3e0a797240aefaa9c8009e49c57ded3b59e: 
>> bad file    (this is with a recent git version)
>>
>>     git cat-file -t 6da4d3e0a797240
>>       --> fatal: Not a valid object name 6da4d3e0a797240
>>
>> So, same result than the one that I already reported...
>>
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to