Blame results in a 500 due to syntax highlighting

https://sentry.gitlap.com/gitlab/gitlabcom/issues/1181/

cc @rdavila @DouweM

mentioned in issue #13350 (closed)

Reassigned to @rdavila

@rspeicher I'm going to give a look, thanks!

Added regression label

@rspeicher looks like it's an issue related to gitlab_git. Gitlab::Git::Blob#data is returning an incomplete content.

I've tried with the README file from the h5bp/html5-boilerplate project, here is the result:

repo.blob_at(project.commit('HEAD').id, '/README.md')
blob.data
=> "From Root NEW MR.Demo more. Test\n# [HTML5 Boilerplate](https://html5boilerplate.com)\n\n[![Build Status](https://travis-ci.org/h5bp/html5-boilerplate.svg)](https://travis-ci.org/h5bp/html5-boilerplate)\n[![devDependency Status](https://david-dm.org/h5bp/html5-boilerplate/dev-status.svg)](https://david-dm.org/h5bp/html5-boilerplate#info=devDependencies)\n\nHTML5 Boilerplate is a professional front-end template for building\nfast, robust, and adaptable web apps or sites.\n\nThis project is the product of many years of iterative development and\ncombined community knowledge. It does not impose a specific development\nphilosophy or framework, so you're free to architect your code in the\nway that you want.\n\n* Homepage: [https://html5boilerplate.com](https://html5boilerplate.com)\n* Source: [https://github.com/h5bp/html5-boilerplate](https://github.com/h5bp/html5-boilerplate)\n* Twitter: [@h5bp](https://twitter.com/h5bp)\n\n\n## Quick start\n\nChoose one of the following options:\n\n1. Download the latest stable release from\n   [html"

I'm going to check if it was broken by a recent release of gitlab_git

mentioned in merge request !2792 (merged)

Status changed to closed by commit 67fefe0e

mentioned in commit 67fefe0e

mentioned in issue #13413 (closed)

This is closed but I still see an error when showing git-blame in gitlab.com. Is the deploy with the fix still pending? Thanks

@knocte The fix is just waiting to be merged into the stable branch along with all the other regressions issues that we're tackling. Thanks.

mentioned in issue #13483 (closed)