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
  • #5964

Closed
Open
Created Dec 31, 2013 by Administrator@rootOwner

Branch number not updated is some UI component

Created by: damko

Summary

After a commit of a new branch I get misleading information about the amount of branches present on the remote repo.

I can browse http://domain/user/project/commits/new_branch so everything is fine but, as you can see in the screenshots, several UI components are not updated.

Steps to reproduce

Possible duplicate of #4100 (closed) but I see it's close. "Steps to reproduce" is the same as #4100 (closed)

Expected behavior

Possible duplicate of #4100 (closed) but I see it's close. Expected behavior" is the same as #4100 (closed)

Observed behavior

  • Cleaned browser cache
  • Login and logout

Relevant logs and/or screenshots

bug_gitlab_631_a

bug_gitlab_631_b

Output of checks

sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

System information System: Debian 7.2 Current User: git Using RVM: no Ruby Version: 1.9.3p194 Gem Version: 1.8.23 Bundler Version:1.3.5 Rake Version: 10.1.0

GitLab information Version: 6.3.1 Revision: 779b4dc Directory: /home/git/gitlab DB Adapter: mysql2 Using LDAP: no Using Omniauth: no

GitLab Shell Version: 1.7.9 Repositories: /home/git/repositories/ Hooks: /home/git/gitlab-shell/hooks/ Git: /usr/bin/git


sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

Checking Environment ...

Git configured for git user? ... yes Has python2? ... yes python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.7.9 ? ... OK (1.7.9) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes update hook up-to-date? ... yes update hooks in repos are links: ... damko / mcbsb ... ok damko / gists ... ok Running /home/git/gitlab-shell/bin/check Check GitLab API access: OK Check directories and files: /home/git/repositories: OK /home/git/.ssh/authorized_keys: OK /usr/bin/redis-cli: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes Database is SQLite ... no All migrations up? ... yes GitLab config exists? ... yes GitLab config outdated? ... no Log directory writable? ... yes Tmp directory writable? ... yes Init script exists? ... yes Init script up-to-date? ... yes projects have namespace: ... damko / mcbsb ... yes damko / gists ... yes Projects have satellites? ... damko / mcbsb ... yes damko / gists ... yes Redis version >= 2.0.0? ... yes Your git bin path is "/usr/bin/git" Git version >= 1.7.10 ? ... yes (1.7.10)

Checking GitLab ... Finished

Assignee
Assign to
Time tracking