Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Git file history for binary files #10999

Closed
dadlerj opened this issue May 26, 2020 · 5 comments · Fixed by #11034
Closed

No Git file history for binary files #10999

dadlerj opened this issue May 26, 2020 · 5 comments · Fixed by #11034
Assignees
Labels
bug An error, flaw or fault that produces an incorrect or unexpected result, or behavior.
Milestone

Comments

@dadlerj
Copy link
Member

dadlerj commented May 26, 2020

Requested by https://app.hubspot.com/contacts/2762526/company/578600789

Sourcegraph doesn't render binary files (#8387), but apparently it also isn't able to show Git history:

image

Related:

Not urgent, but if a quick fix, would be a nice customer win!

@dadlerj dadlerj added bug An error, flaw or fault that produces an incorrect or unexpected result, or behavior. team/core-services labels May 26, 2020
@tsenart
Copy link
Contributor

tsenart commented May 27, 2020

@keegancsmith: Before I dive in, any clue where the root cause may be?

@tsenart tsenart added this to the 3.17 milestone May 27, 2020
@keegancsmith
Copy link
Member

No idea. Maybe our parsing of git log fails with binary files? Not sure why it would care about contents of files for log (except for detecting renames, but even then I don't see why log would change).

That would be my best guess. In fact @eseliger is adding support for binary files in our diff parser 1. This may be a hint towards the issue.

@tsenart
Copy link
Contributor

tsenart commented May 27, 2020

@eseliger: Could you perhaps take a brief look at this as part of #10998? cc @mrnugget

@eseliger
Copy link
Member

eseliger commented May 27, 2020

The cause is that the request fails with an error, because highlighting doesn't work. I think the proper fix is making highlight nullable in graphql and in the frontend don't fail if it's only that error. Want me to do a fix here or will someone else take it?

Found a much simpler fix, sorry for confusion. I'll push it soon

eseliger added a commit that referenced this issue May 27, 2020
This caused #10999 where no git history would show up, because the
request for the highlighted content fails, as the file is binary.
@eseliger
Copy link
Member

Fix is here: #11034

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error, flaw or fault that produces an incorrect or unexpected result, or behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants