CODEWITHSUNDEEP
gitgitlab
cchapman
cchapman

Reputation: 3367

Gitlab blame functionality not working: 502 error

We've installed our own private Gitlab server, and everything seems to be working fine. Except when I try to do a 'blame' on any file, it will time out with the error

502

GitLab is not responding.

Please contact your GitLab administrator if this problem persists.

It is a pretty big repository (~7Gb) but I don't think that should matter on a per-file basis, though, should it?

Does this ever happen on Github as well? Is there anything specific in the configuration that might be causing this.

Upvotes: 1

Views: 674

Answers (1)

VonC
VonC

Reputation: 1329242

Note that the GitLab Web UI is no longer the only possibility to trigger a blame.

There is now (August 2019, GitLab 12.2) a GitLab blame API (from Oleg Zubchenko)

In GitLab 12.2, the new Blame API allows this information to be retrieved directly from GitLab, without needing to checkout the repository.
This is helpful for scripting and automation, based on the people who’ve recently changed the file.

See documentation and issue.

I suspect this will have the same limits you have seen with your large repository, though.

You can see "git blame" with GitLab 14.7 (January 2022), but only for code search results, in the non-free tiers:

Go to Git blame from code search results

Users often want to understand more about code search results, such as when was a file changed or by whom.

With GitLab 14.7, users can easily answer these questions with fewer clicks by using the View blame link in Global Search results.
This change adds another link next to lines of code when hovering over results from a code search.

https://about.gitlab.com/images/14_7/go_directly_to_git_blame_from_global_search.png -- Go to Git blame from code search results

See Documentation and Issue.

GitLab 16.8 (January 2024) adds:

View blame information directly in the file page

In previous versions of GitLab, viewing file blame required you to access a different page. Now you can view the file blame information directly from the file page.

https://about.gitlab.com/images/16_8/blame-in-file-page.png -- View blame information directly in the file page

See Documentation and Epic.

Upvotes: 1

Related Questions