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

Closed
Open
Created Jun 19, 2013 by Administrator@rootOwner

Commit activity mouseover bug

Created by: shawn-sterling

1.Summary:

There is a bug in the commit -> stats, commit activity bar graph window.

2.Steps to reproduce: i) Under a project go Commits -> Stats ii) Move mouse over to 1 bar graph, then back and forth between 2 bar graphs repeatedly (the number will disappear and the background image will keep rising until off screen.)

3.Expected behavior: background image should not move / number should stay visible

4.Observed behavior: background images move up, and the popup number disappears

5.relevant logs / screen shots: if required I can send a screenshot, but this is pretty obvious.

6.Output of checks: not relevant, but ok here ya go:

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.4.0 ? ... OK (1.4.0) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... no <-- is a slightly obtuse check. it's owned by git:nginx (rwxrws--) for us, which is fine. Repo base access is drwxrws---? ... yes post-receive hook up-to-date? ... yes post-receive hooks in repos are links: ... (redacted but all ok) Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

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? ... no <-- using customized init script. not relevant. Projects have satellites? ... (redacted but yes)

Redis version >= 2.0.0? ... yes Your git bin path is "/usr/bin/git" Git version >= 1.7.10 ? ... yes (1.7.11)

Checking GitLab ... Finished

This is version 5.2.1

git log |head -1 commit 26ed59f1

7.Possible fixes: I don't have one.

Assignee
Assign to
Time tracking