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
  • Merge requests
  • !7332

Merged
Created Jul 18, 2014 by Administrator@rootOwner

Fix timeout error when preparing git graph.

  • Overview 3
  • Commits 1
  • Changes 1

Created by: sugarmo

gitlab_git use 30s as the default timeout limit. But, if Gitlab is running on a slow machine, 30s is still not long enough to load and display large project's graph. (My machine takes 70s to do this)

Changing timeout setting in gitlab.yml doesn't help anying, it's weird. It should change that timeout setting in graph too.

I found that there is already an interface in gitlab_git to change timeout setting, then I use it, then my problem resolved. Why Gitlab did not do this before?

I hope this PR can be merged, this can really help many people.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/sugarmo/fix-graph-log-timeout