1

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.

Improve this question
4
  • gitlab.com/gitlab-org/omnibus-gitlab/issues/148 Commented Nov 24, 2014 at 16:10
  • Hmm, we've got 3GB RAM. Is that still not enough? It looks like the recommended is 2GB. Is the blame particularly more taxing on memory than anything else? Commented Nov 24, 2014 at 17:00
  • 1
    Please provide more info when reporting bugs or else we won't be able to help. 1) What are the relevant log/production.log lines? 2) Can you reproduce on gitlab.com if you upload the repos there? 3) Does it a happen on every repository or just on the big one? If not, give a minimal test repo. | Blame operations have to browse multiple commits, so if the repo has tons of commits blame might be slow. It blame not slow on your git blame locally? Commented Nov 24, 2014 at 22:36
  • Thank you Ciro. That helped a lot. I did a test with smaller test repos and was able to see the blame functionality working. I then tried with a smaller commit of my own and was able to get a smaller error Too many changes. To preserve performance only 100 of 131 files displayed. It looks like the problem was that the person's changes I was trying to view was using git add . instead of git add -u. Sorry I'm not able to provide a specific error code, but I think that's it. Commented Nov 25, 2014 at 15:04

1 Answer 1

Reset to default
1

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.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.