Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6449

Closed
Open
Created Mar 02, 2014 by Administrator@rootOwner

6.7 and also previous: "Loading commit data..." hanging forever with one repo

Created by: oscx

After upgrades, I always run the full checks and each of them has been successfull. No error notice on install or upgrade.

However, there is one project (it's one of our most important repos) in gitlabhq, which is hanging and broken with several issues.

Most obvious: "Loading commit data..." instead of the file list is showing forever. This started with 6.4 and still appears in 6.5 and 6.6. The list for the project files and all subdirectories and branches does not show up.

Furthermore, the gitlab issue are "frozen". I can show/read, but not re-assign any of them and not comment. When commenting or reassigning, nothing happens. In Chrome browser network view, this shows an error with no response (not even a http status code in response) for e.g.

/adf/mw/notes?target_id=173&target_type=issue /adf/mw/issues/4

Btw. the production.log/application.log do not log any error for this. It seems like the server did not even notice about the problem!

With the other gitlab projects, there is no problem; only this one is damaged.

Where does this come from; any other log could help? Again, the checks after upgrade did not notice any issue. They mark the project as status "OK". What else can I do to finally repair/fix?

Assignee
Assign to
Time tracking