GitLab issueshttps://gitlab.com/gitlab-org/gitlab/-/issues2019-11-05T18:32:16Zhttps://gitlab.com/gitlab-org/gitlab/-/issues/27032Closing of an ISSUE2019-11-05T18:32:16ZAndreaClosing of an ISSUEIf I close an ISSUE from the Board of Gitlab the label "In progess" or "to do" will be removed.
If I close an ISSUE from Sourcetree or from Gitlab with the button "Close issue" the issue will not be removed and you must remove by hand....If I close an ISSUE from the Board of Gitlab the label "In progess" or "to do" will be removed.
If I close an ISSUE from Sourcetree or from Gitlab with the button "Close issue" the issue will not be removed and you must remove by hand....https://gitlab.com/gitlab-org/gitlab/-/issues/27029Gitlab-ce 10.7.3 upgarde fails during reconfigure2019-11-05T18:32:17ZPrashantha KumariGitlab-ce 10.7.3 upgarde fails during reconfigureHello Team,
We are testing Gitlab-ce upgradation from 9.2.5 to 10.7.3. We are seeing below error. After this we manually run gitlab-ctl reconfigure it got completed successfully. Please let me know what is the issue How to res...Hello Team,
We are testing Gitlab-ce upgradation from 9.2.5 to 10.7.3. We are seeing below error. After this we manually run gitlab-ctl reconfigure it got completed successfully. Please let me know what is the issue How to resolve this issue?
If reconfigure completes without issue, we can consider it has upgradation is completed successfull? Please suggest how to resolve this issue?
PopulateMergeRequestsLatestMergeRequestDiffIdTakeTwo: migrating
== 20171115164540 PopulateMergeRequestsLatestMergeRequestDiffIdTakeTwo: migrated (7.2619s)
================================================================================
Error executing action `run` on resource 'bash[migrate gitlab-rails database]'
================================================================================
Mixlib::ShellOut::CommandTimeout
--------------------------------
Command timed out after 3600s:
Command exceeded allowed execution time, process terminated
---- Begin output of "bash" "/tmp/chef-script20190227-5855-vkk2gk" ----
STDOUT: == 20141126120926 AddMergeRequestRebaseEnabledToProjects: migrating ===========
-- transaction_open?()
-> 0.0000s
-- execute("SET statement_timeout TO 0")
Recipe: gitlab::gitlab-rails
* execute[clear the gitlab-rails cache] action run
- execute /opt/gitlab/bin/gitlab-rake cache:clear
Running handlers:
There was an error running gitlab-ctl reconfigure:
bash[migrate gitlab-rails database] (gitlab::database_migrations line 49) had an error: Mixlib::ShellOut::CommandTimeout: Command timed out after 3600s:
Command exceeded allowed execution time, process terminated
---- Begin output of "bash" "/tmp/chef-script20190227-5855-vkk2gk" ----
STDOUT: == 20141126120926 AddMergeRequestRebaseEnabledToProjects: migrating ===========
-- transaction_open?()
-> 0.0000s
-- execute("SET statement_timeout TO 0")
-> 0.0005s
Thanks,
Prashanthihttps://gitlab.com/gitlab-org/gitlab/-/issues/27018pipeline schedule not working2020-09-02T14:42:30ZGhost Userpipeline schedule not working### Summary
When creating a new a new pipeline Schedule it's never been run.
Looking at the /var/log/gitlab/sidekiq/current log file I don't see the Schedule it's been creating.
### Steps to reproduce
Creating a new a new pipeline Sch...### Summary
When creating a new a new pipeline Schedule it's never been run.
Looking at the /var/log/gitlab/sidekiq/current log file I don't see the Schedule it's been creating.
### Steps to reproduce
Creating a new a new pipeline Schedule
### What is the current *bug* behavior?
The pipeline Schedule is not creating a pipeline
### What is the expected *correct* behavior?
The pipeline Schedule need to create a pipeline
### Relevant logs and/or screenshots
2019-02-27_05:56:07.96667 2019-02-27T05:56:07.965Z 8180 TID-outyq6spk UpdateMergeRequestsWorker JID-15e5271fcf4f9d16d0e860cb INFO: done: 0.053 sec
2019-02-27_05:56:07.98863 2019-02-27T05:56:07.988Z 8180 TID-outyq6tjo DetectRepositoryLanguagesWorker JID-877bac09d2ffb0dd06295daa INFO: start
2019-02-27_05:56:07.99069 2019-02-27T05:56:07.990Z 8180 TID-outyq6sv8 ProjectCacheWorker JID-cd159c75385640176df35206 INFO: start
2019-02-27_05:56:08.00274 2019-02-27T05:56:08.001Z 8180 TID-outyq6te0 CreateGpgSignatureWorker JID-059e7098be1cafd7e552c3ec INFO: start
2019-02-27_05:56:08.02333 2019-02-27T05:56:08.022Z 8180 TID-outyq6te0 CreateGpgSignatureWorker JID-059e7098be1cafd7e552c3ec INFO: done: 0.021 sec
2019-02-27_05:56:08.02722 2019-02-27T05:56:08.026Z 8180 TID-outyq6twc PostReceive JID-23cc0dfc61e2eec81755ffa3 INFO: done: 0.14 sec
2019-02-27_05:56:08.21616 2019-02-27T05:56:08.215Z 8180 TID-outyq6sv8 ProjectCacheWorker JID-cd159c75385640176df35206 INFO: done: 0.226 sec
2019-02-27_05:56:11.12368 2019-02-27T05:56:11.122Z 8180 TID-outyq6tjo DetectRepositoryLanguagesWorker JID-877bac09d2ffb0dd06295daa INFO: done: 3.134 sec
2019-02-27_05:57:30.57724 2019-02-27T05:57:30.576Z 8180 TID-outyq79fk PipelineScheduleWorker JID-af51b99cc3d4d14482345f85 INFO: start
2019-02-27_05:57:30.61765 2019-02-27T05:57:30.617Z 8180 TID-outyq79fk PipelineScheduleWorker JID-af51b99cc3d4d14482345f85 INFO: done: 0.041 sec
2019-02-27_05:58:09.84656 2019-02-27T05:58:09.846Z 8180 TID-outyq6te0 PipelineScheduleWorker JID-278421dd7c27175d7bad5dca INFO: start
2019-02-27_05:58:09.89404 2019-02-27T05:58:09.892Z 8180 TID-outyq6te0 PipelineScheduleWorker JID-278421dd7c27175d7bad5dca INFO: done: 0.047 sec
2019-02-27_05:59:12.54756 2019-02-27T05:59:12.547Z 8180 TID-outyq6tjo PipelineScheduleWorker JID-932ff89cbf46eb4da007dfab INFO: start
2019-02-27_05:59:12.59732 2019-02-27T05:59:12.596Z 8180 TID-outyq6tjo PipelineScheduleWorker JID-932ff89cbf46eb4da007dfab INFO: done: 0.049 sec
2019-02-27_06:00:12.80121 2019-02-27T06:00:12.801Z 8180 TID-outyq6ric PagesDomainVerificationCronWorker JID-2cdbfe839b39012cc7e95425 INFO: start
2019-02-27_06:00:12.80883 2019-02-27T06:00:12.808Z 8180 TID-outyq6t7w PipelineScheduleWorker JID-92fabd2976c23dcc4d8c6ff7 INFO: start
2019-02-27_06:00:12.81417 2019-02-27T06:00:12.814Z 8180 TID-outyq79m4 PruneWebHookLogsWorker JID-4f323a931d542736bdbb65eb INFO: start
2019-02-27_06:00:12.83187 2019-02-27T06:00:12.814Z 8180 TID-outyq6sjg PruneOldEventsWorker JID-d5bca8b94bf08b57580ad5ca INFO: start
2019-02-27_06:00:12.83371 2019-02-27T06:00:12.833Z 8180 TID-outyq6rog StuckMergeJobsWorker JID-f981569778f4034acff4dae9 INFO: start
2019-02-27_06:00:12.84181 2019-02-27T06:00:12.841Z 8180 TID-outyq6ric PagesDomainVerificationCronWorker JID-2cdbfe839b39012cc7e95425 INFO: done: 0.04 sec
2019-02-27_06:00:12.86372 2019-02-27T06:00:12.863Z 8180 TID-outyq79m4 PruneWebHookLogsWorker JID-4f323a931d542736bdbb65eb INFO: done: 0.049 sec
2019-02-27_06:00:12.86513 2019-02-27T06:00:12.865Z 8180 TID-outyq6rog StuckMergeJobsWorker JID-f981569778f4034acff4dae9 INFO: done: 0.032 sec
2019-02-27_06:00:12.86576 2019-02-27T06:00:12.865Z 8180 TID-outyq79s8 StuckCiJobsWorker JID-ee397b82f9a602dbca7f4ec9 INFO: start
2019-02-27_06:00:12.86664 2019-02-27T06:00:12.866Z 8180 TID-outyq6sjg PruneOldEventsWorker JID-d5bca8b94bf08b57580ad5ca INFO: done: 0.052 sec
2019-02-27_06:00:12.88322 2019-02-27T06:00:12.883Z 8180 TID-outyq6r6k RepositoryArchiveCacheWorker JID-641590a55d71902a0122ca0a INFO: start
2019-02-27_06:00:13.07040 2019-02-27T06:00:13.070Z 8180 TID-outyq78r4 ImportExportProjectCleanupWorker JID-438b5a6f37f2573207a501c1 INFO: start
2019-02-27_06:00:13.08506 2019-02-27T06:00:13.084Z 8180 TID-outyq79s8 StuckCiJobsWorker JID-ee397b82f9a602dbca7f4ec9 INFO: done: 0.219 sec
2019-02-27_06:00:13.08927 2019-02-27T06:00:13.089Z 8180 TID-outyq6r6k RepositoryArchiveCacheWorker JID-641590a55d71902a0122ca0a INFO: done: 0.206 sec
2019-02-27_06:00:13.10568 2019-02-27T06:00:13.104Z 8180 TID-outyq78r4 ImportExportProjectCleanupWorker JID-438b5a6f37f2573207a501c1 INFO: done: 0.035 sec
2019-02-27_06:00:13.14469 2019-02-27T06:00:13.143Z 8180 TID-outyq6t7w PipelineScheduleWorker JID-92fabd2976c23dcc4d8c6ff7 INFO: done: 0.335 sec
#### Results of GitLab environment info
<details>
<summary>
GitLab version: 11.8.0 (gitlab-ce@ce13864265ed3b3f7be6437921bb9773a0cf2fa2
Install: Omnibus CE
</summary>
<pre>
System information
System:
Current User: git
Using RVM: no
Ruby Version: 2.5.3p105
Gem Version: 2.7.6
Bundler Version:1.16.6
Rake Version: 12.3.2
Redis Version: 3.2.12
Git Version: 2.18.1
Sidekiq Version:5.2.5
Go Version: unknown
GitLab information
Version: 11.8.0
Revision: ce13864
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://.com
HTTP Clone URL: https://.com/some-group/some-project.git
SSH Clone URL: git@.com:some-group/some-project.git
Using LDAP: yes
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version: 8.4.4
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
</pre>
</details>Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/26995SVG images not displayed in issues2022-05-18T10:13:38ZJohan leroySVG images not displayed in issues### Summary
Issues containing an SVG image will no longer display the SVG image.
### Steps to reproduce
Create issue add SVG image. The image is not displayed in preview nor the final view
### What is the current *bug* behavior?
SVG...### Summary
Issues containing an SVG image will no longer display the SVG image.
### Steps to reproduce
Create issue add SVG image. The image is not displayed in preview nor the final view
### What is the current *bug* behavior?
SVG images not displayed
### What is the expected *correct* behavior?
SVG images should be displayed. Same as the wiki behaviorhttps://gitlab.com/gitlab-org/gitlab/-/issues/26992CI-CD on Group with SubGroup2019-11-05T18:32:21ZBenjaminCI-CD on Group with SubGroupHi,
When we try to access to CI-CD settings page on a group with subgroups, gitlab return " 422
The change you requested was rejected."
When looking the logs :
```
Started GET "/groups/GHOST/-/settings/ci_cd" for 127.0.0.1 at 2019-02-2...Hi,
When we try to access to CI-CD settings page on a group with subgroups, gitlab return " 422
The change you requested was rejected."
When looking the logs :
```
Started GET "/groups/GHOST/-/settings/ci_cd" for 127.0.0.1 at 2019-02-26 14:36:35 +0100
Processing by Groups::Settings::CiCdController#show as HTML
Parameters: {"group_id"=>"GHOST"}
Completed 500 Internal Server Error in 48ms (ActiveRecord: 7.7ms)
ActiveRecord::RecordInvalid (Validation failed: Group URL has already been taken):
app/models/concerns/token_authenticatable_strategies/base.rb:39:in `reset_token!'
app/models/concerns/token_authenticatable_strategies/base.rb:32:in `ensure_token!'
app/models/concerns/token_authenticatable.rb:43:in `block in add_authentication_token_field'
app/models/group.rb:397:in `runners_token'
app/views/groups/runners/_group_runners.html.haml:13:in `_app_views_groups_runners__group_runners_html_haml___4058086953679540608_69945604649540'
app/views/groups/runners/_index.html.haml:9:in `_app_views_groups_runners__index_html_haml___1373496603181019659_69945604925940'
app/views/groups/settings/ci_cd/show.html.haml:21:in `_app_views_groups_settings_ci_cd_show_html_haml__1854020797277551962_69945898193000'
app/controllers/application_controller.rb:113:in `render'
lib/gitlab/i18n.rb:55:in `with_locale'
lib/gitlab/i18n.rb:61:in `with_user_locale'
app/controllers/application_controller.rb:417:in `set_locale'
lib/gitlab/middleware/rails_queue_duration.rb:24:in `call'
lib/gitlab/metrics/rack_middleware.rb:17:in `block in call'
lib/gitlab/metrics/transaction.rb:55:in `run'
lib/gitlab/metrics/rack_middleware.rb:17:in `call'
lib/gitlab/middleware/multipart.rb:103:in `call'
lib/gitlab/request_profiler/middleware.rb:16:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/correlation_id.rb:16:in `block in call'
lib/gitlab/correlation_id.rb:15:in `use_id'
lib/gitlab/middleware/correlation_id.rb:15:in `call'
lib/gitlab/middleware/read_only/controller.rb:40:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:20:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:29:in `call'
lib/gitlab/middleware/release_env.rb:13:in `call'
```
Best regards,https://gitlab.com/gitlab-org/gitlab/-/issues/26964Milestone is not linked on boards page.2019-11-05T18:32:23ZChris EatonMilestone is not linked on boards page.### Summary
The milestone text is no longer linked when viewed in the board.
### Steps to reproduce
[issue]
1. Go to a project board .../boards
2. Click a card so the sidebar appears.
3. Attempt to click the milestone, notice nothing ...### Summary
The milestone text is no longer linked when viewed in the board.
### Steps to reproduce
[issue]
1. Go to a project board .../boards
2. Click a card so the sidebar appears.
3. Attempt to click the milestone, notice nothing happens and the text is not a link.
[expected similar behavior]
1. Now click the issue to go to the issue page.
2. Attempt to click the milestone.
3. Notice it is properly linked.
### What is the current *bug* behavior?
Milestone is not linked properly.
### What is the expected *correct* behavior?
The Milestone should be linked.
### Relevant logs and/or screenshots
On the boards page.
![image](/uploads/bc7c660fbd466c7d79006963fa74296e/image.png)
### Environment
Chrome 72.0.3626.109
RHEL Linux
### Possible fixes
Update the template to link the text.https://gitlab.com/gitlab-org/gitlab/-/issues/26915unable to schedule pipeline for every 5 minutes2023-08-05T08:19:16ZSagar Chavanunable to schedule pipeline for every 5 minutesI have scheduled a job to run at every 5 minutes but it showing 30 minute to next run
Scheduled Cron: */5 * * * *
It seems like a bug, please provide resolution.I have scheduled a job to run at every 5 minutes but it showing 30 minute to next run
Scheduled Cron: */5 * * * *
It seems like a bug, please provide resolution.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/26880Steps to take to register Group Runner are not in GitLab2019-11-05T18:32:30ZQuinten KrijgerSteps to take to register Group Runner are not in GitLabhttps://docs.gitlab.com/ee/ci/runners/#registering-a-group-runner says
> ... To create a group Runner visit the group you want to make the Runner work for in GitLab:
>
> 1. Go to Settings > CI/CD to obtain the token
but under the gro...https://docs.gitlab.com/ee/ci/runners/#registering-a-group-runner says
> ... To create a group Runner visit the group you want to make the Runner work for in GitLab:
>
> 1. Go to Settings > CI/CD to obtain the token
but under the group no Settings exist
<!-- Don't edit below this line -->https://gitlab.com/gitlab-org/gitlab/-/issues/26872Add single branch from multiple AOSP repos2019-11-05T18:32:32ZoliverAdd single branch from multiple AOSP reposAdd single branch from multiple AOSP repos
<!-- Don't edit below this line -->Add single branch from multiple AOSP repos
<!-- Don't edit below this line -->https://gitlab.com/gitlab-org/gitlab/-/issues/26871Some users receive 500 when logging in the the web qui2019-11-05T18:32:33Zken-hanSome users receive 500 when logging in the the web qui### Summary
We are using GitLab Community Edition 10.8.0.
Yesterday some users are experiencing issues when logging in the web gui. They receive the following error:
![image](/uploads/6046852c618a59801153efed52ce4da2/image.png)
This ...### Summary
We are using GitLab Community Edition 10.8.0.
Yesterday some users are experiencing issues when logging in the web gui. They receive the following error:
![image](/uploads/6046852c618a59801153efed52ce4da2/image.png)
This only happens to a few users (ldap and standard users). This started happening yesterday, we have no idea what caused this. Nobody has updated gitlab, or change
### Steps to reproduce
We have no idea what caused this bug to happen.
### What is the current *bug* behavior?
When logging in the web gui some users receive an error 500. NOTE: they can still push and pull using git commands.
### Relevant logs and/or screenshots
`==> /var/log/gitlab/gitlab-rails/production_json.log <==
{"method":"GET","path":"/","format":"html","controller":"RootController","action":"index","status":500,"error":"ActionView::Template::Error: failed to parse loose object: invalid header","duration":81.11,"view":0.0,"db":13.88,"time":"2019-02-21T08:26:37.815Z","params":[],"remote_ip":"10.1.252.152","user_id":1,"username":"root","gitaly_calls":3}
==> /var/log/gitlab/gitlab-rails/production.log <==
ActionView::Template::Error (failed to parse loose object: invalid header):
19: - if project.creator && use_creator_avatar
20: = image_tag avatar_icon_for_user(project.creator, 40), class: "avatar s40", alt:''
21: - else
22: = project_icon(project, alt: '', class: 'avatar project-avatar s40')
23: .project-details
24: %h3.prepend-top-0.append-bottom-0
25: = link_to project_path(project), class: 'text-plain' do
lib/gitlab/git/repository.rb:1756:in `target'
lib/gitlab/git/repository.rb:1756:in `block in branches_filter'
lib/gitlab/git/repository.rb:1754:in `each'
lib/gitlab/git/repository.rb:1754:in `each'
lib/gitlab/git/repository.rb:1754:in `map'
lib/gitlab/git/repository.rb:1754:in `branches_filter'
lib/gitlab/git/repository.rb:170:in `block in branches'
lib/gitlab/gitaly_client.rb:268:in `block (2 levels) in migrate'
lib/gitlab/gitaly_client.rb:312:in `allow_n_plus_1_calls'
lib/gitlab/gitaly_client.rb:261:in `block in migrate'
lib/gitlab/metrics/influx_db.rb:98:in `measure'
lib/gitlab/gitaly_client.rb:259:in `migrate'
lib/gitlab/git/repository.rb:1448:in `gitaly_migrate'
lib/gitlab/git/repository.rb:166:in `branches'
lib/gitlab/git/repository.rb:159:in `block in branch_names'
lib/gitlab/gitaly_client.rb:268:in `block (2 levels) in migrate'
lib/gitlab/gitaly_client.rb:312:in `allow_n_plus_1_calls'
lib/gitlab/gitaly_client.rb:261:in `block in migrate'
lib/gitlab/metrics/influx_db.rb:98:in `measure'
lib/gitlab/gitaly_client.rb:259:in `migrate'
lib/gitlab/git/repository.rb:1448:in `gitaly_migrate'
lib/gitlab/git/repository.rb:155:in `branch_names'
lib/gitlab/git/repository.rb:373:in `discover_default_branch'
lib/gitlab/git/repository.rb:127:in `block in root_ref'
lib/gitlab/gitaly_client.rb:268:in `block (2 levels) in migrate'
lib/gitlab/gitaly_client.rb:312:in `allow_n_plus_1_calls'
lib/gitlab/gitaly_client.rb:261:in `block in migrate'
lib/gitlab/metrics/influx_db.rb:98:in `measure'
lib/gitlab/gitaly_client.rb:259:in `migrate'
lib/gitlab/git/repository.rb:1448:in `gitaly_migrate'
lib/gitlab/git/repository.rb:123:in `root_ref'
app/models/repository.rb:473:in `root_ref'
lib/gitlab/repository_cache_adapter.rb:17:in `block (2 levels) in cache_method'
lib/gitlab/repository_cache.rb:22:in `fetch'
lib/gitlab/repository_cache_adapter.rb:54:in `cache_method_output'
lib/gitlab/repository_cache_adapter.rb:16:in `block in cache_method'
app/models/repository.rb:598:in `head_commit'
app/models/repository.rb:609:in `tree'
app/models/repository.rb:918:in `file_on_head'
app/models/repository.rb:525:in `block in avatar'
lib/gitlab/gitaly_client.rb:312:in `allow_n_plus_1_calls'
app/models/repository.rb:524:in `avatar'
lib/gitlab/repository_cache_adapter.rb:17:in `block (2 levels) in cache_method'
lib/gitlab/repository_cache.rb:22:in `fetch'
lib/gitlab/repository_cache_adapter.rb:54:in `cache_method_output'
lib/gitlab/repository_cache_adapter.rb:16:in `block in cache_method'
app/models/project.rb:1055:in `avatar_in_git'
app/models/project.rb:1059:in `avatar_url'
app/models/concerns/avatarable.rb:19:in `avatar_url'
app/helpers/avatars_helper.rb:10:in `project_icon'
app/views/shared/projects/_project.html.haml:22:in `block (2 levels) in _app_views_shared_projects__project_html_haml___4062744266700254789_70145133190960'
app/views/shared/projects/_project.html.haml:18:in `block in _app_views_shared_projects__project_html_haml___4062744266700254789_70145133190960'
app/views/shared/projects/_project.html.haml:15:in `_app_views_shared_projects__project_html_haml___4062744266700254789_70145133190960'
app/views/shared/projects/_list.html.haml:19:in `block in _app_views_shared_projects__list_html_haml___1856520940860420376_70145130694780'
app/views/shared/projects/_list.html.haml:17:in `_app_views_shared_projects__list_html_haml___1856520940860420376_70145130694780'
app/views/dashboard/projects/_projects.html.haml:1:in `_app_views_dashboard_projects__projects_html_haml___833249871689411572_70145130918900'
app/views/dashboard/projects/index.html.haml:15:in `_app_views_dashboard_projects_index_html_haml___2714526613580750767_70145117346600'
app/controllers/dashboard/projects_controller.rb:12:in `index'
app/controllers/root_controller.rb:18:in `block in index'
lib/gitlab/gitaly_client.rb:312:in `allow_n_plus_1_calls'
app/controllers/root_controller.rb:17:in `index'
lib/gitlab/i18n.rb:50:in `with_locale'
lib/gitlab/i18n.rb:56:in `with_user_locale'
app/controllers/application_controller.rb:350:in `set_locale'
lib/gitlab/middleware/multipart.rb:95:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:17:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/read_only/controller.rb:28:in `call'
lib/gitlab/middleware/read_only.rb:16:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
lib/gitlab/middleware/release_env.rb:10:in `call'
`
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
** Invoke gitlab:env:info (first_time)
** Invoke gitlab_environment (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute gitlab_environment
** Execute gitlab:env:info
System information
System: Ubuntu 14.04
Current User: git
Using RVM: no
Ruby Version: 2.3.7p456
Gem Version: 2.6.14
Bundler Version:1.13.7
Rake Version: 12.3.1
Redis Version: 3.2.11
Git Version: 2.16.3
Sidekiq Version:5.0.5
Go Version: unknown
GitLab information
Version: 10.8.0
Revision: 55e4a0b
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: http://git0301.priv.vangenechten.com
HTTP Clone URL: http://git0301.priv.vangenechten.com/some-group/some-project.git
SSH Clone URL: git@git0301.priv.vangenechten.com:some-group/some-project.git
Using LDAP: yes
Using Omniauth: no
GitLab Shell
Version: 7.1.2
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
Checking GitLab Shell ...
GitLab Shell version >= 7.1.2 ? ... OK (7.1.2)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
3/7 ... ok
3/8 ... ok
17/9 ... ok
20/10 ... ok
3/13 ... ok
3/14 ... ok
17/15 ... ok
24/16 ... ok
24/17 ... ok
28/18 ... ok
28/19 ... ok
28/20 ... ok
28/21 ... ok
31/22 ... ok
3/23 ... ok
31/24 ... ok
20/44 ... ok
32/94 ... ok
32/95 ... ok
32/96 ... ok
32/97 ... ok
36/98 ... ok
36/99 ... ok
36/100 ... ok
36/101 ... ok
36/102 ... ok
36/103 ... ok
36/104 ... ok
36/108 ... ok
32/109 ... ok
36/110 ... ok
32/127 ... ok
47/128 ... ok
47/129 ... ok
44/154 ... ok
46/188 ... ok
44/189 ... ok
32/190 ... ok
46/191 ... ok
44/192 ... ok
46/193 ... ok
44/194 ... ok
46/195 ... ok
44/196 ... ok
32/197 ... ok
32/198 ... ok
32/199 ... ok
48/202 ... ok
32/203 ... ok
32/204 ... ok
36/205 ... ok
3/206 ... ok
3/207 ... ok
32/208 ... ok
3/209 ... ok
3/210 ... ok
28/211 ... ok
32/212 ... ok
48/215 ... ok
48/216 ... ok
52/217 ... ok
49/220 ... ok
36/221 ... ok
17/222 ... ok
36/223 ... ok
55/225 ... ok
55/226 ... ok
55/227 ... ok
57/228 ... ok
28/230 ... ok
58/235 ... ok
58/237 ... ok
58/242 ... ok
59/243 ... ok
59/244 ... ok
59/245 ... ok
59/246 ... ok
59/247 ... ok
59/249 ... ok
58/250 ... ok
60/251 ... ok
59/252 ... ok
58/254 ... ok
59/255 ... ok
59/256 ... ok
59/257 ... ok
20/258 ... ok
58/259 ... ok
3/260 ... ok
3/264 ... ok
3/265 ... ok
3/266 ... ok
3/267 ... ok
3/268 ... ok
58/269 ... ok
55/270 ... ok
59/273 ... ok
3/274 ... ok
3/275 ... ok
59/276 ... ok
59/277 ... ok
55/278 ... ok
55/279 ... ok
58/280 ... ok
55/281 ... ok
58/282 ... ok
58/283 ... ok
3/284 ... ok
58/285 ... ok
58/286 ... ok
3/287 ... ok
66/288 ... ok
67/289 ... ok
67/290 ... repository is empty
36/291 ... ok
36/292 ... ok
67/293 ... ok
3/295 ... ok
58/296 ... ok
51/297 ... ok
3/298 ... ok
3/301 ... ok
55/302 ... ok
3/304 ... ok
3/305 ... ok
3/307 ... ok
55/308 ... ok
55/309 ... ok
32/310 ... repository is empty
3/311 ... ok
59/312 ... ok
59/313 ... ok
3/314 ... ok
3/317 ... ok
32/318 ... ok
32/319 ... ok
36/320 ... ok
57/321 ... ok
71/323 ... ok
30/324 ... ok
57/326 ... ok
29/327 ... ok
1/328 ... repository is empty
32/330 ... ok
32/331 ... ok
32/332 ... ok
32/333 ... ok
32/334 ... ok
32/335 ... ok
32/337 ... ok
32/338 ... ok
32/339 ... ok
32/340 ... ok
32/341 ... ok
32/342 ... ok
32/343 ... ok
32/344 ... ok
32/346 ... ok
32/348 ... ok
32/349 ... ok
32/352 ... ok
32/353 ... ok
32/354 ... ok
32/355 ... ok
32/356 ... ok
32/357 ... ok
32/358 ... ok
32/359 ... ok
32/360 ... ok
32/361 ... ok
32/362 ... ok
32/363 ... ok
32/364 ... ok
32/365 ... ok
32/366 ... ok
32/367 ... ok
32/368 ... ok
32/369 ... ok
32/370 ... ok
32/371 ... ok
32/372 ... ok
32/373 ... ok
32/374 ... ok
32/375 ... ok
32/376 ... ok
32/377 ... ok
32/378 ... ok
32/379 ... ok
32/380 ... ok
32/381 ... ok
32/382 ... ok
32/383 ... ok
32/384 ... ok
32/385 ... ok
32/386 ... ok
32/387 ... ok
32/388 ... ok
32/389 ... ok
32/390 ... ok
32/391 ... ok
32/392 ... ok
32/393 ... ok
32/394 ... ok
32/395 ... ok
32/396 ... ok
32/397 ... ok
32/398 ... ok
32/399 ... ok
32/400 ... ok
32/401 ... ok
32/402 ... ok
32/403 ... ok
32/404 ... ok
32/405 ... ok
32/406 ... ok
32/407 ... ok
32/408 ... ok
32/409 ... ok
32/410 ... ok
32/411 ... ok
32/412 ... ok
32/413 ... ok
32/414 ... ok
32/415 ... ok
32/416 ... ok
32/417 ... ok
32/418 ... ok
32/419 ... ok
32/420 ... ok
32/421 ... ok
32/422 ... ok
32/423 ... ok
32/424 ... ok
32/425 ... ok
32/426 ... ok
32/427 ... ok
32/428 ... ok
32/429 ... ok
32/430 ... ok
32/431 ... ok
32/432 ... ok
32/433 ... ok
32/434 ... ok
32/435 ... ok
32/436 ... ok
32/437 ... ok
32/438 ... ok
32/439 ... ok
32/440 ... ok
32/441 ... ok
32/442 ... ok
32/443 ... ok
32/444 ... ok
32/445 ... ok
32/446 ... ok
32/447 ... ok
32/448 ... ok
32/449 ... ok
32/450 ... ok
32/451 ... ok
32/452 ... ok
32/453 ... ok
32/454 ... ok
32/455 ... ok
32/456 ... ok
32/457 ... ok
32/458 ... ok
32/459 ... ok
32/460 ... ok
32/461 ... repository is empty
59/462 ... ok
32/463 ... ok
20/464 ... ok
30/465 ... ok
59/466 ... ok
55/471 ... ok
32/472 ... ok
30/473 ... ok
32/474 ... ok
20/475 ... ok
20/476 ... ok
32/477 ... ok
55/478 ... ok
55/479 ... ok
55/480 ... ok
55/481 ... ok
3/482 ... ok
29/483 ... ok
55/484 ... repository is empty
73/486 ... ok
29/487 ... ok
32/489 ... ok
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 Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml
Checking LDAP ...
Server: ldapmain
not verifying SSL hostname of LDAPS server 'ldap.priv.vangenechten.com:636'
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
DN: cn=0001102r2,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001102r2
DN: cn=0001106pr1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001106pr1
DN: cn=0001106pr2,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001106pr2
DN: cn=0001142er1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001142er1
DN: cn=0001145pr1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001145pr1
DN: cn=0001145pr2,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001145pr2
DN: cn=000114cmi1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 000114cmi1
DN: cn=000114cr2,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 000114cr2
DN: cn=000114mi3,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 000114mi3
DN: cn=0001769r1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001769r1
DN: cn=0001769r2,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001769r2
DN: cn=0001837r1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001837r1
DN: cn=000186kba1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 000186kba1
DN: cn=0001agasi1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001agasi1
DN: cn=0001agsto1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001agsto1
DN: cn=0001cel2,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001cel2
DN: cn=0001cel3,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001cel3
DN: cn=0001clam3,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001clam3
DN: cn=0001clam4,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001clam4
DN: cn=0001clam7,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001clam7
DN: cn=0001dx135,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001dx135
DN: cn=0001gor3,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001gor3
DN: cn=0001gor4,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001gor4
DN: cn=0001h145xl,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001h145xl
DN: cn=0001mfoil1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001mfoil1
DN: cn=0001om145,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001om145
DN: cn=0001pl145,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pl145
DN: cn=0001pla11,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pla11
DN: cn=0001pla13,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pla13
DN: cn=0001plcc1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001plcc1
DN: cn=0001pld11,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pld11
DN: cn=0001pld13,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pld13
DN: cn=0001pld14,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pld14
DN: cn=0001pld15,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pld15
DN: cn=0001pld5,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001pld5
DN: cn=0001shuf1,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001shuf1
DN: cn=0001snijp3,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001snijp3
DN: cn=0001temc,ou=ltspfenics,ou=prg,ou=vgb,o=vgg uid: 0001temc
DN: cn=0006-zwst,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006-zwst
DN: cn=0006104er1,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006104er1
DN: cn=0006104er2,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006104er2
DN: cn=0006142cr1,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006142cr1
DN: cn=000676kba1,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 000676kba1
DN: cn=0006837u1,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006837u1
DN: cn=0006brek,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006brek
DN: cn=0006di1040,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006di1040
DN: cn=0006diaspr,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006diaspr
DN: cn=0006nomach,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006nomach
DN: cn=0006pldi10,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006pldi10
DN: cn=0006pldo90,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006pldo90
DN: cn=0006sort3,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006sort3
DN: cn=0006strap,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006strap
DN: cn=0006zwst,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006zwst
DN: cn=0006zwst2,ou=ltspfenics,ou=prg,ou=gmey,o=vgg uid: 0006zwst2
DN: cn=0031asitr1,ou=ltspfenics,ou=prg,ou=vgkh,o=vgg uid: 0031asitr1
DN: cn=aandrusans,ou=vgkri,o=vgg uid: aandrusans
DN: cn=ababin,ou=vgcm,o=vgg uid: ababin
DN: cn=abakos,ou=vgkh,o=vgg uid: abakos
DN: cn=abara,ou=vgpch,o=vgg uid: abara
DN: cn=aboeyen,ou=vgnke,o=vgg uid: aboeyen
DN: cn=aborgosz,ou=vgpch,o=vgg uid: aborgosz
DN: cn=aborisov,ou=vgopm,o=vgg uid: aborisov
DN: cn=aborowczyk,ou=vgpch,o=vgg uid: aborowczyk
DN: cn=abrendler,ou=vgnke,o=vgg uid: abrendler
DN: cn=abuisseret,ou=vgb,o=vgg uid: abuisseret
DN: cn=aclemencin,ou=gmey,o=vgg uid: aclemencin
DN: cn=adelomme,ou=gang,o=vgg uid: adelomme
DN: cn=ademoulin,ou=vgb,o=vgg uid: ademoulin
DN: cn=adesandi,ou=gmey,o=vgg uid: adesandi
DN: cn=adloniak,ou=vgb,o=vgg uid: adloniak
DN: cn=admin,o=vgg uid: Admin
DN: cn=admin1,ou=srv,ou=vgb,o=vgg uid: admin1
DN: cn=admin10,ou=srv,ou=vgnko,o=vgg uid: admin10
DN: cn=admin11,ou=srv,ou=vgpch,o=vgg uid: admin11
DN: cn=admin13,ou=srv,ou=apri,o=vgg uid: admin13
DN: cn=admin14,ou=srv,ou=vgcm,o=vgg uid: admin14
DN: cn=admin18,ou=srv,ou=vgnke,o=vgg uid: admin18
DN: cn=admin21,ou=srv,ou=vgkri,o=vgg uid: admin21
DN: cn=admin29,ou=srv,ou=vgopm,o=vgg uid: admin29
DN: cn=admin31,ou=srv,ou=vgkh,o=vgg uid: admin31
DN: cn=admin4,ou=srv,ou=ep,o=vgg uid: admin4
DN: cn=admin6,ou=srv,ou=gmey,o=vgg uid: admin6
DN: cn=admin7,ou=srv,ou=gang,o=vgg uid: admin7
DN: cn=admin9,ou=srv,ou=vgnke,o=vgg uid: admin9
DN: cn=afptest0101,ou=afp,ou=prg,ou=vgb,o=vgg uid: afptest0101
DN: cn=afptest0301,ou=afp,ou=prg,ou=ict,o=vgg uid: afptest0301
DN: cn=afptest0401,ou=afp,ou=prg,ou=ep,o=vgg uid: afptest0401
DN: cn=afptest0601,ou=afp,ou=prg,ou=gmey,o=vgg uid: afptest0601
DN: cn=afptest0701,ou=afp,ou=prg,ou=gang,o=vgg uid: afptest0701
DN: cn=afptest0901,ou=afp,ou=prg,ou=vgnke,o=vgg uid: afptest0901
DN: cn=afptest1001,ou=afp,ou=prg,ou=vgnko,o=vgg uid: afptest1001
DN: cn=afptest1101,ou=afp,ou=prg,ou=vgpch,o=vgg uid: afptest1101
DN: cn=afptest1301,ou=afp,ou=prg,ou=apri,o=vgg uid: afptest1301
DN: cn=afptest1401,ou=afp,ou=prg,ou=vgcm,o=vgg uid: afptest1401
DN: cn=afptest2101,ou=afp,ou=prg,ou=vgkri,o=vgg uid: afptest2101
DN: cn=afptest2901,ou=afp,ou=prg,ou=vgopm,o=vgg uid: afptest2901
DN: cn=afptest3101,ou=afp,ou=prg,ou=vgkh,o=vgg uid: afptest3101
DN: cn=afriemert,ou=vgnko,o=vgg uid: afriemert
DN: cn=afwerk,ou=vgb,o=vgg uid: afwerk
DN: cn=agve1,ou=vgb,o=vgg uid: AGVE1
Checking LDAP ... Finished
Checking GitLab ...
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: ...
3/7 ... yes
3/8 ... yes
17/9 ... yes
20/10 ... yes
3/13 ... yes
3/14 ... yes
17/15 ... yes
24/16 ... yes
24/17 ... yes
28/18 ... yes
28/19 ... yes
28/20 ... yes
28/21 ... yes
31/22 ... yes
3/23 ... yes
31/24 ... yes
20/44 ... yes
32/94 ... yes
32/95 ... yes
32/96 ... yes
32/97 ... yes
36/98 ... yes
36/99 ... yes
36/100 ... yes
36/101 ... yes
36/102 ... yes
36/103 ... yes
36/104 ... yes
36/108 ... yes
32/109 ... yes
36/110 ... yes
32/127 ... yes
47/128 ... yes
47/129 ... yes
44/154 ... yes
46/188 ... yes
44/189 ... yes
32/190 ... yes
46/191 ... yes
44/192 ... yes
46/193 ... yes
44/194 ... yes
46/195 ... yes
44/196 ... yes
32/197 ... yes
32/198 ... yes
32/199 ... yes
48/202 ... yes
32/203 ... yes
32/204 ... yes
36/205 ... yes
3/206 ... yes
3/207 ... yes
32/208 ... yes
3/209 ... yes
3/210 ... yes
28/211 ... yes
32/212 ... yes
48/215 ... yes
48/216 ... yes
52/217 ... yes
49/220 ... yes
36/221 ... yes
17/222 ... yes
36/223 ... yes
55/225 ... yes
55/226 ... yes
55/227 ... yes
57/228 ... yes
28/230 ... yes
58/235 ... yes
58/237 ... yes
58/242 ... yes
59/243 ... yes
59/244 ... yes
59/245 ... yes
59/246 ... yes
59/247 ... yes
59/249 ... yes
58/250 ... yes
60/251 ... yes
59/252 ... yes
58/254 ... yes
59/255 ... yes
59/256 ... yes
59/257 ... yes
20/258 ... yes
58/259 ... yes
3/260 ... yes
3/264 ... yes
3/265 ... yes
3/266 ... yes
3/267 ... yes
3/268 ... yes
58/269 ... yes
55/270 ... yes
59/273 ... yes
3/274 ... yes
3/275 ... yes
59/276 ... yes
59/277 ... yes
55/278 ... yes
55/279 ... yes
58/280 ... yes
55/281 ... yes
58/282 ... yes
58/283 ... yes
3/284 ... yes
58/285 ... yes
58/286 ... yes
3/287 ... yes
66/288 ... yes
67/289 ... yes
67/290 ... yes
36/291 ... yes
36/292 ... yes
67/293 ... yes
3/295 ... yes
58/296 ... yes
51/297 ... yes
3/298 ... yes
3/301 ... yes
55/302 ... yes
3/304 ... yes
3/305 ... yes
3/307 ... yes
55/308 ... yes
55/309 ... yes
32/310 ... yes
3/311 ... yes
59/312 ... yes
59/313 ... yes
3/314 ... yes
3/317 ... yes
32/318 ... yes
32/319 ... yes
36/320 ... yes
57/321 ... yes
71/323 ... yes
30/324 ... yes
57/326 ... yes
29/327 ... yes
1/328 ... yes
32/330 ... yes
32/331 ... yes
32/332 ... yes
32/333 ... yes
32/334 ... yes
32/335 ... yes
32/337 ... yes
32/338 ... yes
32/339 ... yes
32/340 ... yes
32/341 ... yes
32/342 ... yes
32/343 ... yes
32/344 ... yes
32/346 ... yes
32/348 ... yes
32/349 ... yes
32/352 ... yes
32/353 ... yes
32/354 ... yes
32/355 ... yes
32/356 ... yes
32/357 ... yes
32/358 ... yes
32/359 ... yes
32/360 ... yes
32/361 ... yes
32/362 ... yes
32/363 ... yes
32/364 ... yes
32/365 ... yes
32/366 ... yes
32/367 ... yes
32/368 ... yes
32/369 ... yes
32/370 ... yes
32/371 ... yes
32/372 ... yes
32/373 ... yes
32/374 ... yes
32/375 ... yes
32/376 ... yes
32/377 ... yes
32/378 ... yes
32/379 ... yes
32/380 ... yes
32/381 ... yes
32/382 ... yes
32/383 ... yes
32/384 ... yes
32/385 ... yes
32/386 ... yes
32/387 ... yes
32/388 ... yes
32/389 ... yes
32/390 ... yes
32/391 ... yes
32/392 ... yes
32/393 ... yes
32/394 ... yes
32/395 ... yes
32/396 ... yes
32/397 ... yes
32/398 ... yes
32/399 ... yes
32/400 ... yes
32/401 ... yes
32/402 ... yes
32/403 ... yes
32/404 ... yes
32/405 ... yes
32/406 ... yes
32/407 ... yes
32/408 ... yes
32/409 ... yes
32/410 ... yes
32/411 ... yes
32/412 ... yes
32/413 ... yes
32/414 ... yes
32/415 ... yes
32/416 ... yes
32/417 ... yes
32/418 ... yes
32/419 ... yes
32/420 ... yes
32/421 ... yes
32/422 ... yes
32/423 ... yes
32/424 ... yes
32/425 ... yes
32/426 ... yes
32/427 ... yes
32/428 ... yes
32/429 ... yes
32/430 ... yes
32/431 ... yes
32/432 ... yes
32/433 ... yes
32/434 ... yes
32/435 ... yes
32/436 ... yes
32/437 ... yes
32/438 ... yes
32/439 ... yes
32/440 ... yes
32/441 ... yes
32/442 ... yes
32/443 ... yes
32/444 ... yes
32/445 ... yes
32/446 ... yes
32/447 ... yes
32/448 ... yes
32/449 ... yes
32/450 ... yes
32/451 ... yes
32/452 ... yes
32/453 ... yes
32/454 ... yes
32/455 ... yes
32/456 ... yes
32/457 ... yes
32/458 ... yes
32/459 ... yes
32/460 ... yes
32/461 ... yes
59/462 ... yes
32/463 ... yes
20/464 ... yes
30/465 ... yes
59/466 ... yes
55/471 ... yes
32/472 ... yes
30/473 ... yes
32/474 ... yes
20/475 ... yes
20/476 ... yes
32/477 ... yes
55/478 ... yes
55/479 ... yes
55/480 ... yes
55/481 ... yes
3/482 ... yes
29/483 ... yes
55/484 ... yes
73/486 ... yes
29/487 ... yes
32/489 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.7)
Git version >= 2.9.5 ? ... yes (2.16.3)
Git user has default SSH configuration? ... yes
Active users: ... 48
Checking GitLab ... Finished
</pre>
</details>https://gitlab.com/gitlab-org/gitlab/-/issues/26846list of all merge requests on my projects2023-01-01T06:21:17ZDavid Griffithdave@661.orglist of all merge requests on my projectsIt would seem to me that the "Merge Requests" button should easily allow one to see all the merge requests on all of one's projects, even if they're not assigned to the owner and have a count of them show up on the button. I thought tha...It would seem to me that the "Merge Requests" button should easily allow one to see all the merge requests on all of one's projects, even if they're not assigned to the owner and have a count of them show up on the button. I thought that a search parameter like "Owner:@username" would do something, but I get back nothing.https://gitlab.com/gitlab-org/gitlab/-/issues/26843Bug in the Web IDE in custom port2023-04-26T10:15:22ZSergio QuiƱonezsergio_quinonez@rolige.comBug in the Web IDE in custom port<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
For the Enterprise Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
There is a bug in the Web IDE when using a custom port.
### Steps to reproduce
Just create an installation of GitLab CE with a different port to the default, which is 80, and go to the Web IDE.
### What is the current *bug* behavior?
If you set a different port to the default, the tree files in the Web IDE never load.
### Relevant logs and/or screenshots
![image](/uploads/385f7720b1594fc35c504986881330be/image.png)
### Output of checks
Detected in a custom installation with Docker of GitLab CEhttps://gitlab.com/gitlab-org/gitlab/-/issues/26840tries to fetch pipeline status but no CI was setup and merge button is red2019-11-05T18:32:35ZMarco Wlotzkatries to fetch pipeline status but no CI was setup and merge button is redSometimes we have issues with merge requests with projects where no Gitlab CI was setup but it tries to fetch a pipeline status and renders the merge button red:
![image](/uploads/80465ca1d88cd92610843a03b49d9e22/image.png)
We're using ...Sometimes we have issues with merge requests with projects where no Gitlab CI was setup but it tries to fetch a pipeline status and renders the merge button red:
![image](/uploads/80465ca1d88cd92610843a03b49d9e22/image.png)
We're using a hosted instance.
```
System information
System: Debian 9.7
Current User: git
Using RVM: no
Ruby Version: 2.5.3p105
Gem Version: 2.7.6
Bundler Version:1.16.6
Rake Version: 12.3.2
Redis Version: 3.2.12
Git Version: 2.18.1
Sidekiq Version:5.2.3
Go Version: unknown
GitLab information
Version: 11.7.0
Revision: 1d9280e
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://git.d-velop.de
HTTP Clone URL: https://git.d-velop.de/some-group/some-project.git
SSH Clone URL: git@git.d-velop.de:some-group/some-project.git
Using LDAP: yes
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version: 8.4.4
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
root@gitsrv03:~# clear
root@gitsrv03:~# gitlab-rake gitlab:env:info
System information
System: Debian 9.7
Current User: git
Using RVM: no
Ruby Version: 2.5.3p105
Gem Version: 2.7.6
Bundler Version:1.16.6
Rake Version: 12.3.2
Redis Version: 3.2.12
Git Version: 2.18.1
Sidekiq Version:5.2.3
Go Version: unknown
GitLab information
Version: 11.7.0
Revision: 1d9280e
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://git.d-velop.de
HTTP Clone URL: https://git.d-velop.de/some-group/some-project.git
SSH Clone URL: git@git.d-velop.de:some-group/some-project.git
Using LDAP: yes
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version: 8.4.4
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
```
```
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 8.4.4 ? ... OK (8.4.4)
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
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)
...
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: ...
(everything yes)
13/3508 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.5.3)
Git version >= 2.18.0 ? ... yes (2.18.1)
Git user has default SSH configuration? ... yes
Active users: ... 351
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
```https://gitlab.com/gitlab-org/gitlab/-/issues/26827Docs feedback - feature proposal (code review): support for comments on the f...2019-11-05T18:32:36ZVitalii LysovDocs feedback - feature proposal (code review): support for comments on the file level### Problem to solve
<!--- What problem do we solve? -->
During code reviews a possibility to add some information on the file level. If some file is renamed, it is not possible to add any comment to it.
### Further details
My collea...### Problem to solve
<!--- What problem do we solve? -->
During code reviews a possibility to add some information on the file level. If some file is renamed, it is not possible to add any comment to it.
### Further details
My colleague renamed a file and had a double extension (e.g. file1.json.json). Right now it is not possible to add a comment during code review to the file without changes (also not on the file level). So I had to use less specific general merge request discussion.
Another use cases:
* file becomes obsolete and should be removed altogether (so the comment is not related to any line in the file)
* file should be moved or renamed
### Proposal
Add possibility to submit a comment for the file (e.g. a renamed one, which was renamed incorrectly).
### What does success look like, and how can we measure that?
Comment appears not for some specific line, but for the whole file.
### Links / referenceshttps://gitlab.com/gitlab-org/gitlab/-/issues/26810GitLab issue during invite members2019-11-05T18:32:43ZPriyaGitLab issue during invite members<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
For the Enterprise Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
(Summarize the bug encountered concisely)
### Steps to reproduce
(How one can reproduce the issue - this is very important)
### Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
### What is the current *bug* behavior?
(What actually happens)
### What is the expected *correct* behavior?
(What you should see instead)
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
</pre>
</details>
#### Results of GitLab application Check![gitLab_issue](/uploads/d6042f5fabf74624664162f33d251cf9/gitLab_issue.PNG)
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
(we will only investigate if the tests are passing)
</pre>
</details>
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)https://gitlab.com/gitlab-org/gitlab/-/issues/26753No Pipeline creation on webhook trigger2023-04-26T00:57:54ZthorNo Pipeline creation on webhook trigger### Summary
When we setup an integration by webhook on push events or Tag push or whatever and we trigger the webhook no pipeline are created in CI/CD Pipelines.
### Steps to reproduce
I pulled the latest docker gitlab image.
Then ru...### Summary
When we setup an integration by webhook on push events or Tag push or whatever and we trigger the webhook no pipeline are created in CI/CD Pipelines.
### Steps to reproduce
I pulled the latest docker gitlab image.
Then run
```shell
docker run --detach \
--hostname gitlab.dev.com \
--publish 443:443 --publish 11080:80 --publish 11022:22 \
--name gitlab \
--volume /srv/gitlab/config:/etc/gitlab \
--volume /srv/gitlab/logs:/var/log/gitlab \
--volume /srv/gitlab/data:/var/opt/gitlab \
gitlab/gitlab-ce:latest
```
Connect to the root account. Create a project with public visibility. In the admin panel enable the Network , Outbound requests
to "Allow requests to the local network from hooks and services". In the project go to setting integration create a webhook integration
with a jenkins project url, a Secret Token and check the push events and tag push events boxes.
> Be sure to disable auto devops for the project
Now that integration is setup go to your project create a readme and push something in it.
The job should be trigger as we have a webhook for me the CI/CD page stay blank.
### Example Project
https://gitlab.com/Shawcs/test
In this integration configuration information for server and token are false but it's not the important part. CI/CD pipelines is
still empty even after my push.
### What is the current *bug* behavior?
No Pipeline information in CI/CD. See screen below.
### What is the expected *correct* behavior?
Pipeline should appear in CI/CD interface. At least in fail status. See screen below.
### Relevant logs and/or screenshots
non working behavior:
![new_git_CICD](/uploads/ae8e34790433dbfc7ffb6b3b56832aec/new_git_CICD.PNG)
Workin behavior:
![old_git](/uploads/c388d6607b04cd744eff5d05ab847559/old_git.PNG)
result of gitlab-rake gitlab:env:info
```shell
System information
System:
Current User: git
Using RVM: no
Ruby Version: 2.5.3p105
Gem Version: 2.7.6
Bundler Version:1.16.6
Rake Version: 12.3.1
Redis Version: 3.2.12
Git Version: 2.18.1
Sidekiq Version:5.2.3
Go Version: unknown
GitLab information
Version: 11.6.1
Revision: 598c5a7
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://xxxxxx
HTTP Clone URL: https://xxxxxxx/some-group/some-project.git
SSH Clone URL: git@xxxxx.com:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: cas3
GitLab Shell
Version: 8.4.3
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
```Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/26736Docs feedback: Time Tracking not show on side bar2019-11-05T18:32:51ZWayne HuangDocs feedback: Time Tracking not show on side barI followed the doc to set estimated time but time tracking now show on side bar.
<!-- Don't edit below this line -->I followed the doc to set estimated time but time tracking now show on side bar.
<!-- Don't edit below this line -->https://gitlab.com/gitlab-org/gitlab/-/issues/26665Group membership does not expire, cannot remove user manually2019-11-05T18:32:56ZRobert HanuschkeGroup membership does not expire, cannot remove user manually<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
For the Enterprise Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Group membership given with expire date does not expire, GitLab GUI offers no way to remove the user from the group. API results in "403 forbidden".
### Steps to reproduce
1. Give user role in group (happened for "Owner" rights for me)
2. Set expire date
3. Wait for expire date to pass
4. See that user still has permission although expire date is shown in the past
5. Be unable to remove permission via GUI or API
### Example Project
### What is the current *bug* behavior?
On Feb 8, 2019 I gave my account Owner rights in a group I needed to move some projects to. I set the expire date to Feb 9, 2019 to not have to care about removing the permission again when I'm done.
Today (Feb 11, 2019) the permission is still there, still showing to expire on Feb 9, 2019 which for some reason GitLab interprets to be "in 2 days". The system time of the GitLab server is correct though.
There is no way for me to remove my user from the group any more. A button to remove myself is missing from the GUI and using the API results in 403: forbidden
### What is the expected *correct* behavior?
Expiration should work and remove permission at the specified date.
### Relevant logs and/or screenshots
Answer of DELETE call to api/v4/groups/:group_id/members/:user_id authorized as root
```
{
"message": "403 Forbidden"
}
```
Expired user shown even after expire date is over (date output from GitLab server shell)
![expire_display](/uploads/8fa4b92535faa61fde9d38dc3bc2f8e8/expire_display.png)
### Output of checks
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
gitlab-rake gitlab:env:info
System information
System:
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.5.3p105
Gem Version: 2.7.6
Bundler Version:1.16.6
Rake Version: 12.3.2
Redis Version: 3.2.12
Git Version: 2.18.1
Sidekiq Version:5.2.3
Go Version: unknown
GitLab information
Version: 11.7.5-ee
Revision: ed04633
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
DB Version: 9.6.8
URL: https://gitlab.[redacted by submitter]
HTTP Clone URL: https://gitlab.[redacted by submitter]/some-group/some-project.git
SSH Clone URL: git@gitlab.[redacted by submitter]:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: no
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version: 8.4.4
Repository storage paths:
- default: /gitlab-data/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
gitlab-rake gitlab:check SANITIZE=true
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 8.4.4 ? ... OK (8.4.4)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK
Access to /gitlab-data/home/.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
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: ... LDAP is disabled in config/gitlab.yml
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: ...
20/5 ... yes
22/7 ... yes
20/9 ... yes
20/10 ... yes
30/11 ... yes
45/12 ... yes
30/13 ... yes
30/15 ... yes
19/16 ... yes
14/17 ... yes
43/18 ... yes
17/19 ... yes
65/21 ... yes
68/22 ... yes
68/23 ... yes
45/24 ... yes
30/25 ... yes
45/26 ... yes
46/27 ... yes
101/28 ... yes
101/30 ... yes
68/34 ... yes
68/35 ... yes
68/36 ... yes
68/37 ... yes
68/38 ... yes
68/39 ... yes
68/41 ... yes
120/42 ... yes
60/45 ... yes
115/46 ... yes
68/47 ... yes
115/48 ... yes
121/49 ... yes
60/50 ... yes
68/51 ... yes
106/52 ... yes
47/54 ... yes
86/55 ... yes
79/56 ... yes
115/57 ... yes
46/58 ... yes
122/59 ... yes
123/61 ... yes
68/63 ... yes
106/64 ... yes
9/65 ... yes
9/66 ... yes
8/67 ... yes
106/68 ... yes
8/69 ... yes
47/70 ... yes
46/71 ... yes
60/72 ... yes
60/73 ... yes
60/74 ... yes
8/75 ... yes
8/76 ... yes
78/77 ... yes
8/79 ... yes
8/80 ... yes
8/81 ... yes
8/82 ... yes
8/83 ... yes
8/84 ... yes
8/85 ... yes
8/86 ... yes
8/87 ... yes
8/88 ... yes
32/89 ... yes
68/90 ... yes
47/91 ... yes
68/92 ... yes
139/93 ... yes
93/95 ... yes
78/96 ... yes
68/97 ... yes
78/98 ... yes
39/99 ... yes
46/100 ... yes
45/101 ... yes
29/103 ... yes
20/104 ... yes
30/105 ... yes
8/106 ... yes
9/107 ... yes
9/108 ... yes
101/111 ... yes
79/113 ... yes
79/114 ... yes
79/115 ... yes
79/116 ... yes
79/117 ... yes
86/118 ... yes
9/119 ... yes
60/120 ... yes
60/121 ... yes
158/122 ... yes
9/123 ... yes
9/124 ... yes
180/125 ... yes
9/126 ... yes
192/127 ... yes
75/128 ... yes
192/129 ... yes
9/131 ... yes
46/132 ... yes
176/133 ... yes
180/134 ... yes
187/135 ... yes
187/136 ... yes
9/137 ... yes
141/138 ... yes
30/139 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.5.3)
Git version >= 2.18.0 ? ... yes (2.18.1)
Git user has default SSH configuration? ... yes
Active users: ... [redacted by submitter]
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
</pre>
</details>
### Possible fixes
unknownhttps://gitlab.com/gitlab-org/gitlab/-/issues/26663Error Code 500 when trying to open any project or profile settings2019-11-05T18:32:57ZVoevodin VadimError Code 500 when trying to open any project or profile settings<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label.
For the Community Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
For the Enterprise Edition issue tracker:
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Log shows this error
```
ActionView::Template::Error (super: no superclass method `commit_email_hostname' for #<ApplicationSetting:0x000000001367d870>):
12: %li.commit.flex-row.js-toggle-container{ id: "commit-#{commit.short_id}" }
13:
14: .avatar-cell.d-none.d-sm-block
15: = author_avatar(commit, size: 36, has_tooltip: false)
16:
17: .commit-detail.flex-list
18: .commit-content.qa-commit-content
```
### Steps to reproduce
Don't know, maybe my own only. Unicorn and nginx from gitlab is disabled.
### What is the current *bug* behavior?
I see internal server error code 500 from browser
### What is the expected *correct* behavior?
No errors
### Relevant logs and/or screenshots
```
=> /var/log/gitlab/gitlab-rails/production.log <==
Started GET "/audition2revival/dancegame" for 88.206.14.127 at 2019-02-10 11:33:53 +0100
Processing by ProjectsController#show as HTML
Parameters: {"namespace_id"=>"audition2revival", "id"=>"dancegame"}
Completed 500 Internal Server Error in 146ms (ActiveRecord: 12.3ms)
ActionView::Template::Error (super: no superclass method `commit_email_hostname' for #<ApplicationSetting:0x000000001367d870>):
12: %li.commit.flex-row.js-toggle-container{ id: "commit-#{commit.short_id}" }
13:
14: .avatar-cell.d-none.d-sm-block
15: = author_avatar(commit, size: 36, has_tooltip: false)
16:
17: .commit-detail.flex-list
18: .commit-content.qa-commit-content
app/models/application_setting.rb:370:in `commit_email_hostname'
lib/gitlab/private_commit_email.rb:9:in `regex'
lib/gitlab/private_commit_email.rb:15:in `user_id_for_email'
lib/gitlab/private_commit_email.rb:22:in `block in user_ids_for_emails'
lib/gitlab/private_commit_email.rb:22:in `map'
lib/gitlab/private_commit_email.rb:22:in `user_ids_for_emails'
app/models/user.rb:371:in `by_any_email'
app/models/commit.rb:236:in `block in lazy_author'
app/models/commit.rb:250:in `author'
lib/gitlab/cache/request_cache.rb:43:in `block (3 levels) in request_cache'
lib/gitlab/cache/request_cache.rb:43:in `block (2 levels) in request_cache'
app/helpers/avatars_helper.rb:52:in `author_avatar'
app/views/projects/commits/_commit.html.haml:15:in `_app_views_projects_commits__commit_html_haml__2599431056254577917_173131020'
app/views/shared/_commit_well.html.haml:4:in `_app_views_shared__commit_well_html_haml__101539621414542804_173212020'
app/views/projects/_files.html.haml:13:in `_app_views_projects__files_html_haml___61749361132074815_177261620'
app/views/projects/show.html.haml:34:in `_app_views_projects_show_html_haml___4069087294578226380_149270200'
app/controllers/application_controller.rb:113:in `render'
lib/gitlab/i18n.rb:55:in `with_locale'
lib/gitlab/i18n.rb:61:in `with_user_locale'
app/controllers/application_controller.rb:417:in `set_locale'
lib/gitlab/middleware/multipart.rb:103:in `call'
lib/gitlab/request_profiler/middleware.rb:16:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/correlation_id.rb:16:in `block in call'
lib/gitlab/correlation_id.rb:15:in `use_id'
lib/gitlab/middleware/correlation_id.rb:15:in `call'
lib/gitlab/middleware/read_only/controller.rb:40:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:20:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:29:in `call'
lib/gitlab/middleware/release_env.rb:13:in `call'
Started GET "/favicon.ico" for 88.206.14.127 at 2019-02-10 11:33:53 +0100
==> /var/log/gitlab/gitlab-rails/production_json.log <==
{"method":"GET","path":"/audition2revival/dancegame","format":"html","controller":"ProjectsController","action":"show","status":500,"error":"ActionView::Template::Error: super: no superclass method `commit_email_hostname' for #<ApplicationSetting:0x000000001367d870>","duration":146.62,"view":0.0,"db":12.33,"time":"2019-02-10T10:33:53.667Z","params":[{"key":"namespace_id","value":"audition2revival"},{"key":"id","value":"dancegame"}],"remote_ip":"88.206.14.127","user_id":2,"username":"Wadimich","ua":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.96 Safari/537.36","gitaly_calls":7,"correlation_id":"3ece1d8b-9397-403f-aa10-6d08d7fa44d4"}
```
### Output of checks
This bug is on community edition
#### Results of GitLab environment info
```
System information
System: Ubuntu 16.04
Current User: git
Using RVM: no
Ruby Version: 2.5.3p105
Gem Version: 2.7.6
Bundler Version:1.16.6
Rake Version: 12.3.2
Redis Version: 3.2.12
Git Version: 2.18.1
Sidekiq Version:5.2.3
Go Version: unknown
GitLab information
Version: 11.7.5
Revision: c5b5b18
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: http://gitlab.wadimich.ru
HTTP Clone URL: http://gitlab.wadimich.ru/some-group/some-project.git
SSH Clone URL: git@gitlab.wadimich.ru:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version: 8.4.4
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
```
#### Results of GitLab application Check
```
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 8.4.4 ? ... OK (8.4.4)
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
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: ... LDAP is disabled in config/gitlab.yml
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? ... skipped (no tmp uploads folder yet)
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: ...
4/1 ... yes
4/2 ... yes
4/3 ... yes
4/5 ... yes
2/6 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.5.3)
Git version >= 2.18.0 ? ... yes (2.18.1)
Git user has default SSH configuration? ... yes
Active users: ... 3
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
```https://gitlab.com/gitlab-org/gitlab/-/issues/26661ANT ReplaceRegexp not able to make changes to files in Gitlab2019-11-05T18:32:57ZAshraf KhanANT ReplaceRegexp not able to make changes to files in GitlabI am trying to remove a few lines from a file in the src folder before deploying the changes to the target Org. I am using ReplaceRegexp to achieve this
**Build.xml: below is the part of code added.**
`<target name="removeUserPermi...I am trying to remove a few lines from a file in the src folder before deploying the changes to the target Org. I am using ReplaceRegexp to achieve this
**Build.xml: below is the part of code added.**
`<target name="removeUserPermissions">
<replaceregexp byline="true">
<regexp pattern="<fields>"/>
<substitution expression="<REMOVED>"/>
<fileset dir="src/objects">
</fileset>
</replaceregexp>
</target>`
**Pipeline : The pipeline says that the changes have been made and the file updated**
removeUserPermissions:
[replaceregexp] Replacing pattern `'<fields>'` with `'<REMOVED>'` in '/builds/myProject/src/objects/Medi.object' by line.
[replaceregexp] File has changed; saving the updated file
[replaceregexp] Replacing pattern `'<fields>'` with `'<REMOVED>'` in '/builds/myProject/src/objects/Medi1.object' by line.
[replaceregexp] File has changed; saving the updated file
[replaceregexp] Replacing pattern `'<fields>'` with `'<REMOVED>'` in '/builds/myProject/src/objects/Medi2.object' by line.
[replaceregexp] File has changed; saving the updated file
**But the actual files in the Git repository have not been changed or updated.**
Any reasons why this is happening?