Hi, unfortunately I cannot provide any screenshots or examples as it happens only with our real data files that I cannot share...
Unfortunately we have some huge xml files (280k+ lines) with a lot of commits (4k+)... Doing a git blame on them often only shows a part, like first ~60k lines missing, last 10k lines missing... or starting with line 1 but 110k lines missing...
I have checked the git command that is started every time, when doing it on the console it returns the complete history.
The only thing odd I did notice is that in the GUI the SHA is displayed with 6 hex digits, while the "Navigate to" mouse over text mentions 7 hex digits (and git log --pretty='%h' uses 9 due to the size of the repo, they calculate that depending on the number of objects in the repo ).
There are about a dozen cases where there are two commits starting with the same 6 hex digits. Could that have anything to do with it?
PS: Btw. what about a cache for the blame? That would speed up things for me tremendously...
Hi, unfortunately I cannot provide any screenshots or examples as it happens only with our real data files that I cannot share...
Unfortunately we have some huge xml files (280k+ lines) with a lot of commits (4k+)... Doing a git blame on them often only shows a part, like first ~60k lines missing, last 10k lines missing... or starting with line 1 but 110k lines missing...
I have checked the git command that is started every time, when doing it on the console it returns the complete history.
The only thing odd I did notice is that in the GUI the SHA is displayed with 6 hex digits, while the "Navigate to" mouse over text mentions 7 hex digits (and git log --pretty='%h' uses 9 due to the size of the repo, they calculate that depending on the number of objects in the repo ).
There are about a dozen cases where there are two commits starting with the same 6 hex digits. Could that have anything to do with it?
PS: Btw. what about a cache for the blame? That would speed up things for me tremendously...