Admin dashboard statistics Forks negative number

Summary

In my test instance, the Admin Dashboard Statistics shows: "Forks -1".

It's not a big issue, but I think that the number can never be negative. As I haven't found a way to find more useful information about the apparent number of forks in the Gitlab UI and why it reports "-1", I wonder if it is relevant information for an administrator. In my production instance, the number of Forks = 5. But I can't find any information about the apparent forks (which repositories are forked into which repositories), unless I go to a repository which I know was forked and click on the number of forks in the UI.

Steps to reproduce

I don't know how to reproduce this. I Just noticed it after upgrading the test instance. It could have been present before the upgrade.

Example Project

NA, this appears in a local Gitlab-EE test instance.

What is the current bug behavior?

Number of forks is "-1".

What is the expected correct behavior?

The actual number of forks or "0".

Relevant logs and/or screenshots

Output of checks

NA

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.6.3p62
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.2
Redis Version:  3.2.12
Git Version:    2.22.0
Sidekiq Version:5.2.7
Go Version:     unknown
GitLab information
Version:        12.2.1-ee
Revision:       e4a8b6c773a
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     10.9
URL:            https://test-gitlab.mydomain.local
HTTP Clone URL: https://test-gitlab.mydomain.local/some-group/some-project.git
SSH Clone URL:  git@test-gitlab.mydomain.local:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version:        9.3.0
Repository storage paths:

• default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

root@gitlab-ce-test:/data/docker/cm-gitlab-ee# docker exec cm-gitlab-ee gitlab-rake gitlab:check SANITIZE=true
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes
not verifying SSL hostname of LDAPS server 'xxxx.mydomain.local:389'
not verifying SSL hostname of LDAPS server 'yyyy.myotherdomain.local:389'
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 100 users of 100 limit.
Server: ldapsecondary
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 26 users of 100 limit.
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
38/1 ... yes
37/4 ... yes
37/5 ... yes
37/6 ... yes
37/7 ... yes
37/8 ... yes
71/10 ... yes
37/11 ... yes
71/12 ... yes
71/13 ... yes
69/14 ... yes
70/15 ... yes
71/16 ... yes
71/17 ... yes
37/18 ... yes
71/19 ... yes
37/20 ... yes
71/21 ... yes
71/22 ... yes
71/23 ... yes
37/24 ... yes
37/25 ... yes
37/26 ... yes
37/27 ... yes
37/28 ... yes
37/29 ... yes
37/33 ... yes
38/38 ... yes
38/39 ... yes
38/40 ... yes
38/41 ... yes
53/45 ... yes
70/54 ... yes
37/55 ... yes
71/57 ... yes
44/58 ... yes
38/59 ... yes
70/61 ... yes
53/62 ... yes
67/64 ... yes
69/65 ... yes
38/66 ... yes
69/67 ... yes
44/68 ... yes
78/69 ... yes
74/70 ... yes
38/71 ... yes
69/72 ... yes
69/73 ... yes
69/74 ... yes
38/75 ... yes
69/76 ... yes
38/79 ... yes
78/81 ... yes
69/85 ... yes
69/89 ... yes
100/90 ... yes
70/92 ... yes
69/93 ... yes
95/94 ... yes
93/96 ... yes
100/97 ... yes
38/98 ... yes
38/99 ... yes
95/100 ... yes
70/101 ... yes
96/102 ... yes
96/103 ... yes
34/105 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.22.0 ? ... yes (2.22.0)
Git user has default SSH configuration? ... yes
Active users: ... 47
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)