GitLab FOSS issueshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues2024-02-08T07:12:40Zhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/27817Slack commands for creating issue displays error but creates issue2024-02-08T07:12:40ZClement HoSlack commands for creating issue displays error but creates issueEarlier today, I was using slack commands to slackbot to create gitlab issues. I was sending the following:
```
/gitlab-ce issue new Remaining fixes for mattermost and slack command integration page
The following fixes need to be made:
...Earlier today, I was using slack commands to slackbot to create gitlab issues. I was sending the following:
```
/gitlab-ce issue new Remaining fixes for mattermost and slack command integration page
The following fixes need to be made:
- Adding autocomplete off to the token input field
- Updating the help document images to match the latest screenshots
As mentioned in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8491#note_22946084
/assign @lbennett
/label ~Frontend
/label ~Deliverable
/milestone %8.17
```
Slackbot kept saying that the command failed and to contact @ayufan but I was surprised to see the following in the issues page after trying multiple times:
![Screen_Shot_2017-02-07_at_11.26.18_AM](/uploads/9d4e84fe8f66714ddacf5df889cc0559/Screen_Shot_2017-02-07_at_11.26.18_AM.png)Backloghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/23197Friendly message on user creation 422 is not rendered2023-12-18T05:37:06ZJacob Vosmaerjacob@gitlab.comFriendly message on user creation 422 is not renderedWhen I try to create a new GitLab account via e.g. an existing Twitter account it can happen that this fails because my Twitter username is already taken in GitLab. This leads to an unfriendly '422 error' page, which is an old problem. I...When I try to create a new GitLab account via e.g. an existing Twitter account it can happen that this fails because my Twitter username is already taken in GitLab. This leads to an unfriendly '422 error' page, which is an old problem. I noticed today that somebody must have tried to make the user creation 422 more friendly, but the friendly code is not working.
![Screen_Shot_2016-10-11_at_13.12.40](/uploads/2ae096948126485db949264894a4fefe/Screen_Shot_2016-10-11_at_13.12.40.png)
Note how the URL has an `error=foo` query parameter with a friendly message, but this message is not rendered on the page. Looks like a bug to me.Next 4-6 releaseshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/40596Cannot change visibility settings of a private project (that's been forked), ...2023-12-18T05:36:17ZChristoffer FridlundCannot change visibility settings of a private project (that's been forked), made with a private group, after making the group public### Summary
We have trouble changing the visibility of a private project made within a private group, after changing the visibility of the group to public. We think it might be related to the bug described here (fork visibility): https:...### Summary
We have trouble changing the visibility of a private project made within a private group, after changing the visibility of the group to public. We think it might be related to the bug described here (fork visibility): https://gitlab.com/gitlab-org/gitlab-ce/issues/40088
I forked a private project (made with a private group) to my own personal namespace. Obviously the visibility level had to be as strict or stricter than the original project, so the fork was also private. The same rules for visibility are logically inherited in all projects of the group owning the projects. However, after changing the group's visibility to public, I still can't change the visibility of the project. I thought it was connected to the private fork, so I disconnected it from my personal namespace. The visibility of the forked project (now not longer a fork) can be altered, but the main project still have the same issue.
### Steps to reproduce
* Create a private group
* Create a private project in the private group
* Not possible to change visibility of the project, but the dropdown combobox works (alternatives grayed out).
* Create a fork of the project into a personal namespace
* Not possible to change visibility of either of the project references, no dropdown on the combobox.
* Change the visibility to public on the group
* Not possible to change visibility of either of the project references, no dropdown on the combobox.
* Unfork the project from the personal namespace
* Possible to change visibility of forked project, dropdown combobox works.
* Not possible to change visibility of original project, no dropdown on the combobox.
### Example Project
A test project, created with the scheme described above, can be found here:
https://gitlab.com/testing-private-group/testing-private-project
### What is the current *bug* behavior?
When creating a fork of a private project (from a private group), the visibility settings gets disabled for both the original project and the fork. After unlinking the fork, the original project still has disabled visibility settings, while the forked version gets opened. Until doing the private fork, everything works intuitively!
### What is the expected *correct* behavior?
When changing the visibility level of the group owning the project, the visibility of its projects should be adjustable as well.Next 4-6 releaseshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/17276Breakage in displaying SVG in the same repository2023-06-19T16:36:14ZCrunchtime AliBreakage in displaying SVG in the same repositoryI would like to display a SVG file from a repository inside its README but it shows the image not found symbol (despite the link to it being correct)
What can I do about this?
![_docs___GitLab_2016-05-04_17-16-41](/uploads/834664a56823...I would like to display a SVG file from a repository inside its README but it shows the image not found symbol (despite the link to it being correct)
What can I do about this?
![_docs___GitLab_2016-05-04_17-16-41](/uploads/834664a56823aab5ab0a39024797d845/_docs___GitLab_2016-05-04_17-16-41.png)
Example repo:
- https://gitlab.com/issue-reproduce/svg-same-repo/blob/master/README.md12.2Heinrich Lee Yuheinrich@gitlab.comHeinrich Lee Yuheinrich@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/2328Bitbucket import since Gitlab 7.14: Error saving project2023-04-26T17:33:19ZGabriel OstroluckýBitbucket import since Gitlab 7.14: Error saving projectAfter clicking on import button on page https://gitlab.com/import/bitbucket/status, button is replaced by text:
> Error saving project: Name can contain only letters, digits, '_', '.', dash and space. It must start with letter, digit or ...After clicking on import button on page https://gitlab.com/import/bitbucket/status, button is replaced by text:
> Error saving project: Name can contain only letters, digits, '_', '.', dash and space. It must start with letter, digit or '_'.
Repository I'm trying to import is *gadelat/meetnlearn-nette-test* and it's name is *meet'n'learn Nette test*.
Related: #2241Next 4-6 releaseshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/50444Can't correct namespace when importing projects2023-04-26T17:32:52ZAlejandro Rodríguezalejandro@gitlab.comCan't correct namespace when importing projectsWhen listing projects to import, if I click "Import" on one whose path with namespace already exists I get the error "This namespace already been taken! Please choose another one" and the namespace becomes an editable field. However, the...When listing projects to import, if I click "Import" on one whose path with namespace already exists I get the error "This namespace already been taken! Please choose another one" and the namespace becomes an editable field. However, the "Import" button stays disabled.
![Captura_de_pantalla_2016-06-22_a_las_10.40.01_a.m.](/uploads/add32edba5c9a7d514dd147169f9c24a/Captura_de_pantalla_2016-06-22_a_las_10.40.01_a.m..png)
Expected:
I should be able to select another namespace and attempt the import again
Actual:
I'm unable to attempt the import again.
Note:
Also change "This namespace already been taken! Please choose another one" to "This namespace *has* already been taken! Please choose another one"https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41259gitlab-rake gitlab:import:repos create repo in wrong namespace2023-04-26T17:30:54ZAlexander Strachangitlab-rake gitlab:import:repos create repo in wrong namespace### Summary
When using the rake task the repo is imported into the root namespace and not the specified user or group namespace.
### Steps to reproduce
<pre>
#
# Setup
#
create user - testimport
create repo - test-import-001
...### Summary
When using the rake task the repo is imported into the root namespace and not the specified user or group namespace.
### Steps to reproduce
<pre>
#
# Setup
#
create user - testimport
create repo - test-import-001
create file - file001.txt
create branch - br-001
create tag - tag-001
create dir - mkdir -p /var/opt/gitlab/git-data/import-test/testimport
set perms - chown -R git:git /var/opt/gitlab/git-data/import-test
#
# Copy to existing namespace
#
# 10.2.5 - behaviour
# expected: repo to be imported into namespace
# actual: imported into root namespace, existing repos moved to root namespace
create repo to be imported
# cp -rp /var/opt/gitlab/git-data/repositories/testimport/test-import-001.git /var/opt/gitlab/git-data/repositories/testimport/test-import-001-dup.git
import repo
# gitlab-rake --trace gitlab:import:repos['/var/opt/gitlab/git-data/repositories/testimport']
Processing /var/opt/gitlab/git-data/repositories/testimport/test-import-001-dup.git
* Created test-import-001-dup (/test-import-001-dup) ### moved to root namespace
* Skipping repo /var/opt/gitlab/git-data/repositories/testimport/test-import-001.wiki.git
Processing /var/opt/gitlab/git-data/repositories/testimport/test-import-001.git
* Created test-import-001 (/test-import-001) ### moved to root namespace
# ls -l /var/opt/gitlab/git-data/repositories/testimport
total 0
# 10.1.5 - behaviour
# expected: repo to be imported into namespace
# actual: repo imported into namespace
create repo to be imported
# cp -rp /var/opt/gitlab/git-data/repositories/testimport/test-import-001.git /var/opt/gitlab/git-data/repositories/testimport/test-import-001-dup.git
import repo
# gitlab-rake --trace gitlab:import:repos['/var/opt/gitlab/git-data/repositories/testimport']
Processing /var/opt/gitlab/git-data/repositories/testimport/test-import-001-dup.git
* Namespace testimport exists.
* Created test-import-001-dup (testimport/test-import-001-dup) ### not moved
Processing /var/opt/gitlab/git-data/repositories/testimport/test-import-001.git
* test-import-001 (testimport/test-import-001) exists
* Skipping wiki repo
#
# Copy to temporary import directory
#
#
# 10.2.5
#
# ls -l /var/opt/gitlab/git-data/repositories/testimport
total 8
drwxrwx--- 5 git git 4096 Dec 19 19:43 test-import-001.git
drwxrwx--- 5 git git 4096 Dec 19 19:43 test-import-001.wiki.git
# cp -rp /var/opt/gitlab/git-data/repositories/testimport/test-import-001.git /var/opt/gitlab/git-data/import-test/testimport/test-import-001-dup.git
# ls -l /var/opt/gitlab/git-data/import-test/testimport/
drwxrwx--- 5 git git 4096 Dec 19 19:43 test-import-001-dup.git
# gitlab-rake --trace gitlab:import:repos['/var/opt/gitlab/git-data/import-test']
Processing /var/opt/gitlab/git-data/import-test/testimport/test-import-001-dup.git
* Using namespace: testimport
* Created test-import-001-dup (testimport/test-import-001-dup) # says testimport namespace but imports into root
# ls -l /var/opt/gitlab/git-data/import-test/testimport/ # repo is imported and moved
# ls -l /var/opt/gitlab/git-data/repositories/testimport/ ### not here
total 8
drwxrwx--- 5 git git 4096 Dec 19 19:43 test-import-001.git
drwxrwx--- 5 git git 4096 Dec 19 19:43 test-import-001.wiki.git
# ls -l /var/opt/gitlab/git-data/repositories/root ### created here
drwxrwx--- 5 git git 4096 Dec 19 19:43 test-import-001-dup.git
</pre>
### What is the current *bug* behavior?
Repo is imported into root namespace and not the specified user or group namespace.
### What is the expected *correct* behavior?
Repo is imported into specified namespace
### Relevant logs and/or screenshots
see steps above
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
System information
System: Ubuntu 16.04
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.3.5p376
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.1.0
Redis Version: 3.2.5
Git Version: 2.13.6
Sidekiq Version:5.0.4
Go Version: unknown
GitLab information
Version: 10.2.5-ee
Revision: 3ec4b67
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
DB Version: 9.6.5
URL: https://astrachan-latest.asgks.net
HTTP Clone URL: https://astrachan-latest.asgks.net/some-group/some-project.git
SSH Clone URL: git@astrachan-latest.asgks.net:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: saml
GitLab Shell
Version: 5.10.0
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 >= 5.10.0 ? ... OK (5.10.0)
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: ...
...
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 ...
LDAP is disabled in config/gitlab.yml
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: ...
...2/1 ... yes
3/2 ... yes
9/3 ... yes
6/4 ... yes
6/5 ... yes
3/6 ... yes
1/13 ... yes
6/25 ... yes
6/31 ... yes
6/32 ... yes
6/33 ... yes
1/46 ... yes
1/47 ... yes
1/48 ... yes
1/49 ... yes
1/50 ... yes
1/51 ... yes
6/54 ... yes
15/62 ... yes
1/63 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.6)
Git user has default SSH configuration? ... yes
Active users: ... 7
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished
</pre>
</details>
### Possible fixeshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/40379Issues search for non-English language not work2023-03-06T17:34:24ZGavinIssues search for non-English language not workIf I use Chinese key word to search issue, the gitlab return all the issues, not search result. Like following:
![image](/uploads/f35cd235300c61920c648db46188b71a/image.png)
my gitlab version:
![image](/uploads/3ca053bf88378d0e88bbb66...If I use Chinese key word to search issue, the gitlab return all the issues, not search result. Like following:
![image](/uploads/f35cd235300c61920c648db46188b71a/image.png)
my gitlab version:
![image](/uploads/3ca053bf88378d0e88bbb66c918abbe6/image.png)12.1Mario de la OssaMario de la Ossahttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/40264LFS Status in Projectview(admin) differs from General Settings in Project2023-01-09T08:19:28ZThomas SpitzleiLFS Status in Projectview(admin) differs from General Settings in Project### Summary
LFS Status in Projectview(admin) differs from General Settings in Project.
### Steps to reproduce
Create a new Project. Open the Project in Adminview. You will find:
![lfs1](/uploads/741c0b020650bf67f128252a97a0488f/lfs1....### Summary
LFS Status in Projectview(admin) differs from General Settings in Project.
### Steps to reproduce
Create a new Project. Open the Project in Adminview. You will find:
![lfs1](/uploads/741c0b020650bf67f128252a97a0488f/lfs1.png)
Then open the Project, go to Settings -> General -> Expand Permissions and you will find this:
![lfs2](/uploads/d4dd6be3a8d5a28f1f00dfa63c851164/lfs2.png)
LFS is already working, even if it is not shown correctly in Project Settings. If I "enable" it there, nothing changes, if I disable it there, it gets disabled in the Adminview, too.
### What is the current *bug* behavior?
The button in Project Settings shows not the correct initial state of LFS.
### What is the expected *correct* behavior?
If LFS is initially enabled, the Button should indicate it.
### 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>
System information
System: Debian 8.9
Current User: git
Using RVM: no
Ruby Version: 2.3.5p376
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.1.0
Redis Version: 3.2.5
Git Version: 2.13.6
Sidekiq Version:5.0.4
Go Version: unknown
GitLab information
Version: 10.1.4
Revision: c887c03
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://***
HTTP Clone URL: https://***/some-group/some-project.git
SSH Clone URL: git@***:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.9.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
</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 >= 5.9.3 ? ... OK (5.9.3)
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: ...
128/2 ... ok
115/7 ... ok
120/15 ... ok
118/17 ... ok
113/18 ... ok
117/19 ... ok
117/20 ... ok
117/21 ... ok
117/22 ... ok
117/23 ... ok
117/24 ... ok
117/25 ... ok
117/26 ... ok
117/27 ... ok
117/28 ... ok
117/29 ... ok
127/31 ... ok
125/32 ... ok
124/33 ... ok
125/34 ... ok
15/35 ... ok
15/36 ... ok
15/38 ... ok
15/39 ... ok
15/40 ... ok
15/41 ... ok
15/42 ... ok
10/43 ... ok
125/47 ... ok
10/48 ... ok
21/49 ... ok
21/50 ... ok
125/51 ... ok
117/53 ... ok
126/54 ... ok
124/55 ... ok
124/56 ... ok
7/57 ... ok
6/58 ... ok
127/59 ... ok
127/60 ... ok
126/61 ... ok
127/63 ... ok
13/64 ... ok
131/65 ... ok
6/66 ... ok
8/67 ... ok
125/68 ... ok
126/70 ... ok
124/71 ... ok
124/72 ... ok
21/74 ... ok
8/75 ... ok
131/77 ... ok
115/78 ... ok
117/80 ... ok
115/81 ... ok
115/82 ... ok
24/83 ... ok
128/85 ... ok
23/87 ... ok
115/88 ... ok
23/89 ... ok
23/90 ... ok
127/91 ... ok
127/92 ... ok
126/93 ... ok
64/94 ... repository is empty
6/95 ... ok
23/96 ... ok
127/97 ... ok
21/98 ... ok
127/99 ... ok
127/100 ... ok
124/101 ... ok
125/102 ... ok
5/103 ... ok
124/106 ... ok
127/107 ... ok
126/108 ... ok
126/109 ... ok
117/110 ... ok
23/111 ... ok
127/112 ... ok
21/113 ... ok
10/115 ... ok
10/116 ... ok
126/117 ... ok
115/118 ... ok
128/119 ... ok
6/121 ... ok
5/125 ... ok
14/126 ... ok
125/127 ... ok
124/128 ... ok
125/129 ... ok
125/130 ... ok
124/131 ... ok
125/132 ... ok
125/133 ... ok
125/134 ... ok
5/135 ... ok
8/136 ... ok
128/137 ... ok
124/138 ... ok
124/139 ... ok
23/140 ... ok
125/141 ... ok
14/142 ... ok
115/143 ... ok
23/144 ... ok
126/145 ... ok
124/146 ... ok
124/147 ... ok
5/148 ... ok
115/149 ... ok
126/150 ... ok
129/151 ... ok
129/152 ... ok
129/153 ... ok
129/154 ... ok
129/155 ... ok
129/156 ... ok
129/157 ... ok
129/158 ... ok
23/161 ... ok
5/162 ... ok
128/163 ... ok
129/164 ... ok
124/165 ... ok
124/166 ... ok
124/167 ... ok
124/168 ... ok
125/169 ... ok
125/170 ... ok
36/172 ... ok
126/173 ... ok
36/174 ... ok
36/175 ... ok
36/176 ... ok
36/177 ... ok
6/178 ... ok
124/179 ... ok
124/180 ... ok
124/181 ... ok
128/182 ... ok
8/183 ... ok
80/186 ... ok
128/187 ... ok
124/188 ... ok
124/189 ... ok
13/190 ... ok
129/192 ... ok
126/193 ... ok
79/194 ... ok
117/195 ... ok
10/196 ... ok
121/197 ... ok
23/198 ... ok
8/199 ... ok
10/200 ... ok
10/202 ... ok
127/203 ... ok
126/204 ... ok
127/205 ... ok
13/206 ... ok
15/207 ... ok
127/209 ... repository is empty
124/210 ... ok
117/211 ... ok
125/212 ... ok
5/213 ... ok
125/214 ... ok
23/215 ... ok
126/216 ... ok
115/219 ... ok
6/220 ... ok
10/222 ... ok
10/223 ... ok
131/227 ... ok
115/228 ... ok
10/229 ... ok
5/230 ... ok
115/231 ... repository is empty
129/234 ... ok
21/236 ... ok
8/238 ... ok
55/239 ... ok
55/240 ... ok
6/242 ... ok
8/245 ... ok
6/248 ... ok
10/249 ... ok
115/250 ... ok
23/251 ... ok
129/252 ... ok
6/254 ... ok
6/255 ... ok
10/256 ... ok
8/258 ... ok
124/260 ... ok
10/263 ... ok
117/265 ... ok
5/267 ... ok
129/269 ... ok
129/270 ... ok
103/272 ... ok
6/273 ... ok
114/274 ... ok
124/275 ... ok
128/276 ... ok
124/277 ... ok
140/278 ... ok
130/279 ... ok
127/280 ... ok
139/281 ... ok
10/282 ... ok
10/283 ... ok
8/284 ... ok
6/285 ... ok
10/286 ... ok
127/287 ... ok
140/288 ... ok
10/289 ... ok
142/290 ... repository is empty
143/291 ... ok
115/292 ... ok
134/293 ... ok
125/294 ... ok
115/295 ... ok
10/296 ... ok
125/297 ... ok
126/298 ... ok
126/299 ... ok
126/301 ... ok
114/304 ... ok
127/305 ... ok
124/306 ... ok
6/307 ... ok
131/308 ... ok
124/309 ... ok
127/310 ... ok
127/311 ... ok
15/312 ... ok
127/313 ... ok
106/314 ... ok
129/315 ... ok
129/316 ... ok
10/317 ... ok
115/318 ... ok
126/319 ... ok
113/320 ... ok
124/321 ... ok
151/322 ... ok
8/323 ... ok
115/325 ... ok
144/326 ... ok
145/327 ... ok
142/328 ... ok
127/329 ... ok
99/331 ... ok
5/332 ... ok
132/333 ... ok
124/334 ... ok
23/335 ... repository is empty
114/336 ... ok
115/338 ... ok
125/339 ... ok
142/340 ... ok
127/342 ... ok
106/343 ... ok
23/344 ... ok
13/345 ... ok
158/346 ... ok
127/347 ... ok
127/348 ... ok
126/349 ... ok
126/350 ... ok
126/351 ... ok
115/352 ... ok
127/353 ... ok
55/354 ... ok
115/355 ... ok
160/356 ... ok
161/358 ... ok
128/359 ... ok
126/360 ... ok
161/362 ... ok
164/363 ... ok
164/364 ... ok
164/365 ... ok
163/366 ... ok
163/367 ... ok
163/368 ... ok
163/370 ... ok
163/371 ... ok
163/372 ... ok
163/373 ... ok
163/374 ... ok
163/375 ... ok
163/376 ... ok
163/377 ... ok
163/378 ... ok
163/379 ... ok
163/380 ... ok
163/381 ... ok
163/382 ... ok
165/383 ... ok
165/384 ... ok
165/385 ... ok
165/386 ... ok
8/387 ... ok
167/388 ... ok
166/389 ... ok
178/390 ... ok
177/391 ... ok
177/392 ... ok
177/393 ... ok
176/394 ... ok
176/395 ... repository is empty
175/396 ... ok
175/397 ... ok
175/398 ... ok
167/399 ... ok
175/400 ... ok
167/401 ... ok
175/402 ... ok
167/403 ... ok
175/404 ... ok
175/405 ... ok
167/406 ... ok
175/407 ... ok
175/408 ... ok
175/409 ... ok
175/410 ... ok
167/411 ... ok
175/412 ... ok
167/413 ... ok
175/414 ... ok
167/415 ... ok
175/416 ... ok
167/417 ... ok
175/418 ... ok
175/419 ... ok
167/420 ... ok
175/421 ... ok
167/422 ... ok
167/423 ... ok
167/424 ... ok
167/425 ... ok
167/426 ... ok
167/427 ... ok
174/428 ... ok
174/429 ... ok
167/430 ... ok
203/431 ... ok
175/432 ... ok
175/433 ... ok
175/434 ... ok
175/435 ... ok
175/436 ... ok
203/437 ... ok
124/438 ... ok
139/441 ... ok
106/443 ... ok
115/444 ... ok
175/445 ... ok
175/446 ... ok
175/447 ... ok
175/448 ... ok
161/449 ... ok
10/450 ... ok
139/451 ... ok
106/452 ... ok
137/453 ... ok
146/454 ... ok
146/455 ... ok
10/456 ... ok
10/457 ... ok
10/458 ... ok
10/459 ... ok
10/460 ... ok
80/461 ... ok
124/462 ... ok
80/463 ... repository is empty
189/464 ... ok
161/465 ... repository is empty
124/466 ... ok
124/467 ... ok
125/468 ... ok
7/469 ... ok
13/470 ... ok
186/471 ... ok
167/473 ... ok
177/474 ... ok
177/475 ... ok
183/476 ... ok
167/477 ... ok
15/478 ... ok
1/479 ... ok
125/481 ... ok
125/482 ... ok
177/483 ... ok
177/484 ... ok
177/485 ... ok
175/486 ... ok
177/487 ... ok
177/488 ... ok
177/489 ... ok
177/490 ... ok
177/491 ... ok
175/492 ... ok
6/493 ... ok
36/494 ... ok
163/495 ... ok
194/498 ... ok
161/501 ... ok
115/502 ... repository is empty
106/503 ... ok
142/504 ... ok
200/505 ... ok
207/506 ... ok
206/507 ... ok
206/508 ... ok
206/509 ... ok
206/510 ... ok
206/511 ... ok
206/512 ... ok
206/513 ... ok
206/514 ... ok
206/515 ... ok
206/516 ... ok
206/517 ... ok
175/518 ... ok
183/519 ... ok
10/520 ... ok
7/521 ... ok
18/522 ... ok
209/523 ... ok
209/524 ... repository is empty
209/525 ... ok
115/527 ... ok
129/529 ... ok
209/530 ... ok
203/531 ... ok
203/532 ... 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 ...
LDAP is disabled in config/gitlab.yml
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: ...
128/2 ... yes
115/7 ... yes
120/15 ... yes
118/17 ... yes
113/18 ... yes
117/19 ... yes
117/20 ... yes
117/21 ... yes
117/22 ... yes
117/23 ... yes
117/24 ... yes
117/25 ... yes
117/26 ... yes
117/27 ... yes
117/28 ... yes
117/29 ... yes
127/31 ... yes
125/32 ... yes
124/33 ... yes
125/34 ... yes
15/35 ... yes
15/36 ... yes
15/38 ... yes
15/39 ... yes
15/40 ... yes
15/41 ... yes
15/42 ... yes
10/43 ... yes
125/47 ... yes
10/48 ... yes
21/49 ... yes
21/50 ... yes
125/51 ... yes
117/53 ... yes
126/54 ... yes
124/55 ... yes
124/56 ... yes
7/57 ... yes
6/58 ... yes
127/59 ... yes
127/60 ... yes
126/61 ... yes
127/63 ... yes
13/64 ... yes
131/65 ... yes
6/66 ... yes
8/67 ... yes
125/68 ... yes
126/70 ... yes
124/71 ... yes
124/72 ... yes
21/74 ... yes
8/75 ... yes
131/77 ... yes
115/78 ... yes
117/80 ... yes
115/81 ... yes
115/82 ... yes
24/83 ... yes
128/85 ... yes
23/87 ... yes
115/88 ... yes
23/89 ... yes
23/90 ... yes
127/91 ... yes
127/92 ... yes
126/93 ... yes
64/94 ... yes
6/95 ... yes
23/96 ... yes
127/97 ... yes
21/98 ... yes
127/99 ... yes
127/100 ... yes
124/101 ... yes
125/102 ... yes
5/103 ... yes
124/106 ... yes
127/107 ... yes
126/108 ... yes
126/109 ... yes
117/110 ... yes
23/111 ... yes
127/112 ... yes
21/113 ... yes
10/115 ... yes
10/116 ... yes
126/117 ... yes
115/118 ... yes
128/119 ... yes
6/121 ... yes
5/125 ... yes
14/126 ... yes
125/127 ... yes
124/128 ... yes
125/129 ... yes
125/130 ... yes
124/131 ... yes
125/132 ... yes
125/133 ... yes
125/134 ... yes
5/135 ... yes
8/136 ... yes
128/137 ... yes
124/138 ... yes
124/139 ... yes
23/140 ... yes
125/141 ... yes
14/142 ... yes
115/143 ... yes
23/144 ... yes
126/145 ... yes
124/146 ... yes
124/147 ... yes
5/148 ... yes
115/149 ... yes
126/150 ... yes
129/151 ... yes
129/152 ... yes
129/153 ... yes
129/154 ... yes
129/155 ... yes
129/156 ... yes
129/157 ... yes
129/158 ... yes
23/161 ... yes
5/162 ... yes
128/163 ... yes
129/164 ... yes
124/165 ... yes
124/166 ... yes
124/167 ... yes
124/168 ... yes
125/169 ... yes
125/170 ... yes
36/172 ... yes
126/173 ... yes
36/174 ... yes
36/175 ... yes
36/176 ... yes
36/177 ... yes
6/178 ... yes
124/179 ... yes
124/180 ... yes
124/181 ... yes
128/182 ... yes
8/183 ... yes
80/186 ... yes
128/187 ... yes
124/188 ... yes
124/189 ... yes
13/190 ... yes
129/192 ... yes
126/193 ... yes
79/194 ... yes
117/195 ... yes
10/196 ... yes
121/197 ... yes
23/198 ... yes
8/199 ... yes
10/200 ... yes
10/202 ... yes
127/203 ... yes
126/204 ... yes
127/205 ... yes
13/206 ... yes
15/207 ... yes
127/209 ... yes
124/210 ... yes
117/211 ... yes
125/212 ... yes
5/213 ... yes
125/214 ... yes
23/215 ... yes
126/216 ... yes
115/219 ... yes
6/220 ... yes
10/222 ... yes
10/223 ... yes
131/227 ... yes
115/228 ... yes
10/229 ... yes
5/230 ... yes
115/231 ... yes
129/234 ... yes
21/236 ... yes
8/238 ... yes
55/239 ... yes
55/240 ... yes
6/242 ... yes
8/245 ... yes
6/248 ... yes
10/249 ... yes
115/250 ... yes
23/251 ... yes
129/252 ... yes
6/254 ... yes
6/255 ... yes
10/256 ... yes
8/258 ... yes
124/260 ... yes
10/263 ... yes
117/265 ... yes
5/267 ... yes
129/269 ... yes
129/270 ... yes
103/272 ... yes
6/273 ... yes
114/274 ... yes
124/275 ... yes
128/276 ... yes
124/277 ... yes
140/278 ... yes
130/279 ... yes
127/280 ... yes
139/281 ... yes
10/282 ... yes
10/283 ... yes
8/284 ... yes
6/285 ... yes
10/286 ... yes
127/287 ... yes
140/288 ... yes
10/289 ... yes
142/290 ... yes
143/291 ... yes
115/292 ... yes
134/293 ... yes
125/294 ... yes
115/295 ... yes
10/296 ... yes
125/297 ... yes
126/298 ... yes
126/299 ... yes
126/301 ... yes
114/304 ... yes
127/305 ... yes
124/306 ... yes
6/307 ... yes
131/308 ... yes
124/309 ... yes
127/310 ... yes
127/311 ... yes
15/312 ... yes
127/313 ... yes
106/314 ... yes
129/315 ... yes
129/316 ... yes
10/317 ... yes
115/318 ... yes
126/319 ... yes
113/320 ... yes
124/321 ... yes
151/322 ... yes
8/323 ... yes
115/325 ... yes
144/326 ... yes
145/327 ... yes
142/328 ... yes
127/329 ... yes
99/331 ... yes
5/332 ... yes
132/333 ... yes
124/334 ... yes
23/335 ... yes
114/336 ... yes
115/338 ... yes
125/339 ... yes
142/340 ... yes
127/342 ... yes
106/343 ... yes
23/344 ... yes
13/345 ... yes
158/346 ... yes
127/347 ... yes
127/348 ... yes
126/349 ... yes
126/350 ... yes
126/351 ... yes
115/352 ... yes
127/353 ... yes
55/354 ... yes
115/355 ... yes
160/356 ... yes
161/358 ... yes
128/359 ... yes
126/360 ... yes
161/362 ... yes
164/363 ... yes
164/364 ... yes
164/365 ... yes
163/366 ... yes
163/367 ... yes
163/368 ... yes
163/370 ... yes
163/371 ... yes
163/372 ... yes
163/373 ... yes
163/374 ... yes
163/375 ... yes
163/376 ... yes
163/377 ... yes
163/378 ... yes
163/379 ... yes
163/380 ... yes
163/381 ... yes
163/382 ... yes
165/383 ... yes
165/384 ... yes
165/385 ... yes
165/386 ... yes
8/387 ... yes
167/388 ... yes
166/389 ... yes
178/390 ... yes
177/391 ... yes
177/392 ... yes
177/393 ... yes
176/394 ... yes
176/395 ... yes
175/396 ... yes
175/397 ... yes
175/398 ... yes
167/399 ... yes
175/400 ... yes
167/401 ... yes
175/402 ... yes
167/403 ... yes
175/404 ... yes
175/405 ... yes
167/406 ... yes
175/407 ... yes
175/408 ... yes
175/409 ... yes
175/410 ... yes
167/411 ... yes
175/412 ... yes
167/413 ... yes
175/414 ... yes
167/415 ... yes
175/416 ... yes
167/417 ... yes
175/418 ... yes
175/419 ... yes
167/420 ... yes
175/421 ... yes
167/422 ... yes
167/423 ... yes
167/424 ... yes
167/425 ... yes
167/426 ... yes
167/427 ... yes
174/428 ... yes
174/429 ... yes
167/430 ... yes
203/431 ... yes
175/432 ... yes
175/433 ... yes
175/434 ... yes
175/435 ... yes
175/436 ... yes
203/437 ... yes
124/438 ... yes
139/441 ... yes
106/443 ... yes
115/444 ... yes
175/445 ... yes
175/446 ... yes
175/447 ... yes
175/448 ... yes
161/449 ... yes
10/450 ... yes
139/451 ... yes
106/452 ... yes
137/453 ... yes
146/454 ... yes
146/455 ... yes
10/456 ... yes
10/457 ... yes
10/458 ... yes
10/459 ... yes
10/460 ... yes
80/461 ... yes
124/462 ... yes
80/463 ... yes
189/464 ... yes
161/465 ... yes
124/466 ... yes
124/467 ... yes
125/468 ... yes
7/469 ... yes
13/470 ... yes
186/471 ... yes
167/473 ... yes
177/474 ... yes
177/475 ... yes
183/476 ... yes
167/477 ... yes
15/478 ... yes
1/479 ... yes
125/481 ... yes
125/482 ... yes
177/483 ... yes
177/484 ... yes
177/485 ... yes
175/486 ... yes
177/487 ... yes
177/488 ... yes
177/489 ... yes
177/490 ... yes
177/491 ... yes
175/492 ... yes
6/493 ... yes
36/494 ... yes
163/495 ... yes
194/498 ... yes
161/501 ... yes
115/502 ... yes
106/503 ... yes
142/504 ... yes
200/505 ... yes
207/506 ... yes
206/507 ... yes
206/508 ... yes
206/509 ... yes
206/510 ... yes
206/511 ... yes
206/512 ... yes
206/513 ... yes
206/514 ... yes
206/515 ... yes
206/516 ... yes
206/517 ... yes
175/518 ... yes
183/519 ... yes
10/520 ... yes
7/521 ... yes
18/522 ... yes
209/523 ... yes
209/524 ... yes
209/525 ... yes
115/527 ... yes
129/529 ... yes
209/530 ... yes
203/531 ... yes
203/532 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.6)
Git user has default SSH configuration? ... yes
Active users: ... 149
Checking GitLab ... Finished
</pre>
</details>
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)Backloghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/27457Message "Fork Error - The project is still being deleted" still appears after...2022-12-08T15:50:39ZTobias FischerMessage "Fork Error - The project is still being deleted" still appears after 24 hours### Summary
I forked a repo, did some changes, merged the forked changes back to origin and deleted my fork.
If I need to contribute new changes, I fork the repo again and start over.
This saves me pulling in the changes from upstream...### Summary
I forked a repo, did some changes, merged the forked changes back to origin and deleted my fork.
If I need to contribute new changes, I fork the repo again and start over.
This saves me pulling in the changes from upstream and maintaining my fork.
However, I cannot fork the same repository again because it will fail with the message below.
### Steps to reproduce
1. create repository fork
2. work on it
3. delete the fork
4. wait 24h
5. try to fork the origin repo again to the same namespace
### Expected behavior
I should be able to fork the repo again.
### Actual behavior
```
Fork Error!
You tried to fork {namespace} / {repo} but it failed for the following reason:
– The project is still being deleted. Please try again later.
```
### Relevant logs and/or screenshots
```
Started POST "/{namespace}/{repo}/forks?namespace_key=[FILTERED]" for {IP-ADDRESS} at 2017-01-30 13:26:41 +0100
Processing by Projects::ForksController#create as HTML
Parameters: {"authenticity_token"=>"{token}", "namespace_key"=>"[FILTERED]", "namespace_id"=>"{namespace}", "project_id"=>"{repo}"}
Unable to save project. Error: The project is still being deleted. Please try again later.
Error setting import status to failed: cannot update a new record. Original error: Unable to save project. Error: The project is still being deleted. Please try again later.
Completed 200 OK in 213ms (Views: 67.5ms | ActiveRecord: 21.6ms)
```
### Output of checks
#### Results of GitLab application Check
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)
```
root@zelos:~# sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 4.1.1 ? ... OK (4.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
2/3 ... ok
2/4 ... ok
3/6 ... ok
17/7 ... ok
17/8 ... ok
2/9 ... ok
17/10 ... ok
2/11 ... ok
3/12 ... ok
2/13 ... ok
2/14 ... ok
2/15 ... ok
2/16 ... ok
2/17 ... ok
2/18 ... ok
3/19 ... ok
2/20 ... ok
2/21 ... ok
3/22 ... ok
2/25 ... ok
8/26 ... ok
19/27 ... ok
19/28 ... ok
19/29 ... ok
31/30 ... ok
17/31 ... ok
31/32 ... ok
10/33 ... ok
31/34 ... ok
3/35 ... ok
3/36 ... ok
1/37 ... ok
32/38 ... ok
32/39 ... ok
1/40 ... ok
32/41 ... ok
17/42 ... ok
17/43 ... ok
3/44 ... ok
36/46 ... ok
17/48 ... ok
2/51 ... ok
26/52 ... repository is empty
27/57 ... ok
27/58 ... ok
27/60 ... ok
27/61 ... ok
28/63 ... ok
28/64 ... ok
28/66 ... ok
28/69 ... ok
29/70 ... ok
28/72 ... ok
3/73 ... ok
3/74 ... ok
2/75 ... ok
28/76 ... ok
29/77 ... ok
10/78 ... ok
17/79 ... ok
10/80 ... ok
3/81 ... ok
3/82 ... ok
10/83 ... ok
36/84 ... ok
30/85 ... ok
26/86 ... ok
34/90 ... ok
3/91 ... ok
9/92 ... ok
10/95 ... repository is empty
36/96 ... ok
32/97 ... ok
10/98 ... ok
19/99 ... ok
36/100 ... ok
3/101 ... ok
3/102 ... ok
17/103 ... ok
3/105 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... no
Try fixing it:
sudo chown -R git /var/opt/gitlab/gitlab-rails/uploads
sudo find /var/opt/gitlab/gitlab-rails/uploads -type f -exec chmod 0644 {} \;
sudo find /var/opt/gitlab/gitlab-rails/uploads -type d -not -path /var/opt/gitlab/gitlab-rails/uploads -exec chmod 0700 {} \;
For more information see:
doc/install/installation.md in section "GitLab"
Please fix the error above and rerun the checks.
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: ...
2/3 ... yes
2/4 ... yes
3/6 ... yes
17/7 ... yes
17/8 ... yes
2/9 ... yes
17/10 ... yes
2/11 ... yes
3/12 ... yes
2/13 ... yes
2/14 ... yes
2/15 ... yes
2/16 ... yes
2/17 ... yes
2/18 ... yes
3/19 ... yes
2/20 ... yes
2/21 ... yes
3/22 ... yes
2/25 ... yes
8/26 ... yes
19/27 ... yes
19/28 ... yes
19/29 ... yes
31/30 ... yes
17/31 ... yes
31/32 ... yes
10/33 ... yes
31/34 ... yes
3/35 ... yes
3/36 ... yes
1/37 ... yes
32/38 ... yes
32/39 ... yes
1/40 ... yes
32/41 ... yes
17/42 ... yes
17/43 ... yes
3/44 ... yes
36/46 ... yes
17/48 ... yes
2/51 ... yes
26/52 ... yes
27/57 ... yes
27/58 ... yes
27/60 ... yes
27/61 ... yes
28/63 ... yes
28/64 ... yes
28/66 ... yes
28/69 ... yes
29/70 ... yes
28/72 ... yes
3/73 ... yes
3/74 ... yes
2/75 ... yes
28/76 ... yes
29/77 ... yes
10/78 ... yes
17/79 ... yes
10/80 ... yes
3/81 ... yes
3/82 ... yes
10/83 ... yes
36/84 ... yes
30/85 ... yes
26/86 ... yes
34/90 ... yes
3/91 ... yes
9/92 ... yes
10/95 ... yes
36/96 ... yes
32/97 ... yes
10/98 ... yes
19/99 ... yes
36/100 ... yes
3/101 ... yes
3/102 ... yes
17/103 ... yes
3/105 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.10.2)
Active users: 21
Checking GitLab ... Finished
```
#### Results of GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)
```
root@zelos:~# sudo gitlab-rake gitlab:env:info
System information
System: Ubuntu 16.04
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.6.6
Bundler Version:1.13.7
Rake Version: 10.5.0
Sidekiq Version:4.2.7
GitLab information
Version: 8.16.3
Revision: d225908
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://host.tld
HTTP Clone URL: https://host.tld/some-group/some-project.git
SSH Clone URL: git@host.tld:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: github
GitLab Shell
Version: 4.1.1
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
Git: /opt/gitlab/embedded/bin/git
```https://gitlab.com/gitlab-org/gitlab-foss/-/issues/4052Handle Net::ReadTimeout in ProjectWebHookWorker2022-11-24T18:27:56ZKelvin MutumaHandle Net::ReadTimeout in ProjectWebHookWorkerDev: https://dev.gitlab.org/gitlab/gitlabhq/issues/2450
https://rpm.newrelic.com/accounts/543063/applications/4968123/traced_errors/6fb7da-650d3f0b-1e7b-11e5-93a1-f8bc12425d4c
120 times in 24 hours
```
Error message
Net::ReadTimeout: ...Dev: https://dev.gitlab.org/gitlab/gitlabhq/issues/2450
https://rpm.newrelic.com/accounts/543063/applications/4968123/traced_errors/6fb7da-650d3f0b-1e7b-11e5-93a1-f8bc12425d4c
120 times in 24 hours
```
Error message
Net::ReadTimeout: Net::ReadTimeout
Stack trace (show Rails)
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ protocol.rb: 158:in `rescue in rbuf_fill'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ protocol.rb: 152:in `rbuf_fill'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ protocol.rb: 134:in `readuntil'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ protocol.rb: 144:in `readline'
…pt/gitlab/embedded/lib/ruby/2.1.0/net/http/ response.rb: 39:in `read_status_line'
…pt/gitlab/embedded/lib/ruby/2.1.0/net/http/ response.rb: 28:in `read_new'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb:1414:in `block in transport_request'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb:1411:in `catch'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb:1411:in `transport_request'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb:1384:in `request'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb:1377:in `block in request'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb: 853:in `start'
/opt/gitlab/embedded/lib/ruby/2.1.0/net/ http.rb:1375:in `request'
…uby/2.1.0/gems/httparty-0.13.3/lib/httparty/ request.rb: 98:in `perform'
…ce/gem/ruby/2.1.0/gems/httparty-0.13.3/lib/ httparty.rb: 539:in `perform_request'
…ce/gem/ruby/2.1.0/gems/httparty-0.13.3/lib/ httparty.rb: 491:in `post'
…dded/service/gitlab-rails/app/models/hooks/ web_hook.rb: 38:in `execute'
…ce/gitlab-rails/app/workers/ project_web_hook_worker.rb: 8:in `perform'
…ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/ processor.rb: 75:in `execute_job'
…ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/ processor.rb: 52:in `block (2 levels) in process'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 127:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 127:in `block in invoke'
…b-rails/lib/gitlab/sidekiq_middleware/ memory_killer.rb: 17:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…ails/lib/gitlab/sidekiq_middleware/ arguments_logger.rb: 6:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…0/gems/sidetiq-0.6.3/lib/sidetiq/middleware/ history.rb: 8:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…q-3.3.0/lib/sidekiq/middleware/server/ active_record.rb: 6:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…ekiq-3.3.0/lib/sidekiq/middleware/server/ retry_jobs.rb: 74:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…sidekiq-3.3.0/lib/sidekiq/middleware/server/ logging.rb: 11:in `block in call'
…m/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/ logging.rb: 22:in `with_context'
…sidekiq-3.3.0/lib/sidekiq/middleware/server/ logging.rb: 7:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 129:in `block in invoke'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 132:in `call'
…1.0/gems/sidekiq-3.3.0/lib/sidekiq/middleware/ chain.rb: 132:in `invoke'
…ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/ processor.rb: 51:in `block in process'
…ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/ processor.rb: 98:in `stats'
…ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/ processor.rb: 50:in `process'
…uby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ calls.rb: 26:in `public_send'
…uby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ calls.rb: 26:in `dispatch'
…uby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ calls.rb: 122:in `dispatch'
…ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ cell.rb: 60:in `block in invoke'
…ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ cell.rb: 71:in `block in task'
…uby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ actor.rb: 357:in `block in task'
…uby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/ tasks.rb: 57:in `block in initialize'
…ems/celluloid-0.16.0/lib/celluloid/tasks/ task_fiber.rb: 15:in `block in create'
```
cc/ @jacobvosmaerhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/32584line-number anchor lost in sign-in redirect2022-08-05T15:02:02ZAlexander Bürgerline-number anchor lost in sign-in redirect### Summary
Links to a specific line in a file lose their line-number anchor after the user has been redirected to the sign in page.
### Steps to reproduce
Take a link to a line in some file contained in a password-protected repo: htt...### Summary
Links to a specific line in a file lose their line-number anchor after the user has been redirected to the sign in page.
### Steps to reproduce
Take a link to a line in some file contained in a password-protected repo: https://my.gitlab.site/bad/example/blob/master/myfile#L1234 (This exact example does not work, of course. I am not sure how to give an example with a password-protected repo accessible to everybody.)
Steps to reproduce the problem(s):
1. sign out from my.gitlab.site
2. paste link in address bar
3. gitlab redirects to https://my.gitlab.site/users/sign_in#L1234
4. sign in
5. gitlab redirects to myfile, but the line number anchor is lost
### What is the current *bug* behavior?
* in step 3 the anchor is used in the sign in page, where it is useless
* in step 5 the anchor is lost after the sign in is completed
### What is the expected *correct* behavior?
* in step 3 the anchor is stored as redirect-after login target, but not used on the sign-in page itself
* in step 5 the anchor is included in the redirect
#### Results of GitLab environment info
Sorry, I cannot give more details than that the site with the problem uses GitLab Community Edition 9.1.4 fed799a and ldap login.https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45279Auto DevOps fails with Unable to select a buildpack2022-04-27T19:21:36ZmadflowAuto DevOps fails with Unable to select a buildpack## Todos
- [ ] Mention language detection for buildpacks to work https://gitlab.com/gitlab-org/gitlab-ce/issues/45279#note_68050366
## Original description
Auto DevOps fails with "Unable to select a buildpack"
This is a Bug report - ...## Todos
- [ ] Mention language detection for buildpacks to work https://gitlab.com/gitlab-org/gitlab-ce/issues/45279#note_68050366
## Original description
Auto DevOps fails with "Unable to select a buildpack"
This is a Bug report - however when I failed to configure something then I am welcome to know.
* gitlab-ce on a DO Doclet (Ubuntu 16.04).
* gitlab-runner on a DO Doclet (Ubuntu 16.04)
* docker executor
* PHP Project with composer.json
* Testet with our without BUILDPACK_URL
* Maybe related upstream issue:
https://github.com/gliderlabs/herokuish/issues/205
* /etc/gitlab-runner/config.toml
```YML
concurrent = 1
check_interval = 0
[[runners]]
name = "gitlab-runner"
url = "https://gitlab.priotas.eu/"
token = "05bbaf38d1a79816893bcb7e0f3c0c"
executor = "docker"
[runners.docker]
tls_verify = false
image = "ubuntu:16.04"
privileged = true
disable_cache = true
cache_dir = "cache"
volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/cache"]
shm_size = 0
[runners.cache]
```
The Build fails with:
```
Running with gitlab-ci-multi-runner 9.5.1 (96b34cc)
on gitlab-runner (05bbaf38)
Using Docker executor with image docker:git ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image docker:dind ID=sha256:b12c0db765b447f4f912cffc2a372466b4af1c9c9b1c57aea364df5ee61afc0c for docker service...
Waiting for services to be up and running...
Using docker image sha256:90f541dced7813ef8051ed12e562a328a4c4d35a89f529b5b023eb655391f211 for predefined container...
Pulling docker image docker:git ...
Using docker image docker:git ID=sha256:4d76de70e898910d9fcb67a1153d9446a5e576fa9c36c6b5d0a8ccd82cb92142 for build container...
Running on runner-05bbaf38-project-5-concurrent-0 via gitlab-runner...
Cloning repository...
Cloning into '/builds/xxx'...
Checking out f4432fa2 as gitlab...
Skipping Git submodules setup
$ # Auto DevOps variables and functions # collapsed multi-line command
$ setup_docker
$ build
Building Heroku-based application using gliderlabs/herokuish docker image...
-----> Unable to select a buildpack
ERROR: Job failed: exit code 1
```11.7Achilleas PipinellisAchilleas Pipinellishttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/21581Issue Boards: Can't move issues between labels in Chrome2021-11-08T16:46:38ZMatt KendallIssue Boards: Can't move issues between labels in ChromeI am unable to move issues from the backlog into a label in Chrome (version 52.0.2743.116 m). Yet I can in Edge or Firefox. When I try and drag an issue I get the hand icon but it doesn't move!I am unable to move issues from the backlog into a label in Chrome (version 52.0.2743.116 m). Yet I can in Edge or Firefox. When I try and drag an issue I get the hand icon but it doesn't move!12.0Fatih AcetFatih Acethttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/39848New Group Milestone shows empty dashboard2021-11-08T16:22:27ZMichael BisbjergNew Group Milestone shows empty dashboard### Summary
We've previously created project milestones, and "promoted" them to Group Milestones (iirc). Just now, however, I created a Group Milestone "first", but am unable to see anything in it. I can attach project-level issues an M...### Summary
We've previously created project milestones, and "promoted" them to Group Milestones (iirc). Just now, however, I created a Group Milestone "first", but am unable to see anything in it. I can attach project-level issues an MR's just fine (and see the numbers in the group dashboard), but not the projects or anything like other group dashboards.
### Steps to reproduce
* Create Group milestone
* In group project, attach issue / MR's to new group milestone
* Observe empty group milestone dashboard
### Example Project
I have reproduced on Gitlab.com, in the following public Group / Project:
* https://gitlab.com/groups/MiketestGroup01/milestones/1
### What is the current *bug* behavior?
The group milestone dashboard is empty. Observe the counts on the right side are correct (also on our local instance) - they show the correct number of issues etc.
This only happens on new Group Milestones. New Project Milestones behave as expected.
![image](/uploads/8a7a2a430da2b32a1de556ff8629f131/image.png)
### What is the expected *correct* behavior?
This is a screenshot from an older Milestone we had. A newly created milestone on our Gitlab-CE 10.1.0 installation exhibits the same behaviour as seen on Gitlab.com.
I expected to see the individual projects, and an issue dashboard.
![image](/uploads/a3fd201012e8197e6e7834fd2217e51d/image.png)
### Relevant logs and/or screenshots
Seen above.
### Output of checks
N/A
#### Results of GitLab environment info
N/A
#### Results of GitLab application Check
N/A
### Possible fixes
N/Ahttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/41233Issue Board URLs without filters have an unwanted `?=` at the end2021-11-08T16:21:46ZBalasankar 'Balu' CIssue Board URLs without filters have an unwanted `?=` at the endUpon visiting any issue board URL, like https://gitlab.com/gitlab-org/omnibus-gitlab/boards/289804 , a `?=` gets appended to the URL. As per my understanding, it is used to specify GET parameters so as to filter the issues based on autho...Upon visiting any issue board URL, like https://gitlab.com/gitlab-org/omnibus-gitlab/boards/289804 , a `?=` gets appended to the URL. As per my understanding, it is used to specify GET parameters so as to filter the issues based on author, milestone etc. For non-filtered scenarios, which is the default when we navigate to the issue board from sidebar, we should not be adding them.
We probably missed to add a check for nulls before generating the URL.
/cc @smcgivernSimon KnoxSimon Knoxhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/41738Sorting of Issues is wrong in lists with pagination2021-11-08T16:20:40ZDavid KuriSorting of Issues is wrong in lists with pagination### Summary
On the issue board, the order of a list with too many issues to be loaded at once (in my case, 45) can be wrong.
### Steps to reproduce
1. On the issue board, remove all lists.
2. Create an issue that you move to the very ...### Summary
On the issue board, the order of a list with too many issues to be loaded at once (in my case, 45) can be wrong.
### Steps to reproduce
1. On the issue board, remove all lists.
2. Create an issue that you move to the very last position. Call it "Debug - Last Issue". If you can, check the database to verify that this issue actually has the highest value of `relative_position`:
`sudo gitlab-rails dbconsole`
`SELECT id, title FROM issues ORDER BY relative_position DESC LIMIT 1;`
3. Create a list with 45 issues, including the last one.
4. Open the issue page through the menu, and scroll down in the list. "Debug - Last Issue" will not be at the bottom.
5. Having scrolled down, refresh the page and scroll down again. Now "Debug - Last Issue" is at the bottom.
### Example Project
### What is the current *bug* behavior?
The order of issues is different (wrong order) when the page is initially loaded and when the page is refreshed after you scroll all the way down (right order).
### What is the expected *correct* behavior?
The order is always right, according to `relative_position` in the database.
### Relevant logs and/or screenshots
Side-by-side comparison of the wrong and right behavior, achieved using the steps described above:
![issues-wrong](/uploads/f8e03eac66423893b25357ca60c25d06/issues-wrong.jpg)
![issues-right](/uploads/18307a6ba7c26ef4793a4e22be0fece8/issues-right.jpg)
### Output of checks
#### Results of GitLab environment info
#### Results of GitLab application Check
### Possible fixes
Definitely a frontend issue.
The problem could be here:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/assets/javascripts/boards/components/board_list.js#L63
Pages are loaded in order, but may be finished in a different order. If the issues are not resorted after they are received, this might be the root of the problem.
![image](/uploads/c5bff7d0308f43296a9eafab5f705f77/image.png)https://gitlab.com/gitlab-org/gitlab-foss/-/issues/38495User contributions in the profile are displayed in wrong timezone2020-12-28T02:31:00ZHaydenUser contributions in the profile are displayed in wrong timezoneUnder "Contributions for Sep 30, 2017" the times appear in UTC despite changing the `time_zone` setting.
```
gitlab_rails['time_zone'] = 'Australia/Adelaide'
```
First observed in 10.0
![Screen_Shot_2017-09-30_at_8.42.51_am](/uploads/...Under "Contributions for Sep 30, 2017" the times appear in UTC despite changing the `time_zone` setting.
```
gitlab_rails['time_zone'] = 'Australia/Adelaide'
```
First observed in 10.0
![Screen_Shot_2017-09-30_at_8.42.51_am](/uploads/a32de4a59b359e14e7eb13cd28b44ed5/Screen_Shot_2017-09-30_at_8.42.51_am.png)
It says an issue was opened at 11:11pm but it was opened at 8:41am on 30 Sephttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/22163wiki over git push suggest to create merge request2020-12-12T15:40:21Zsashkwiki over git push suggest to create merge request### Summary
When I push into master branch of wiki repository, I get suggestion to create merge request. This is erroneous message, as there is no such thing as merge request for wiki repostiory.
### Steps to reproduce
1. Clone wiki ...### Summary
When I push into master branch of wiki repository, I get suggestion to create merge request. This is erroneous message, as there is no such thing as merge request for wiki repostiory.
### Steps to reproduce
1. Clone wiki repository.
2. Make changes and commit them.
3. Push the changes back to Gitlab. You will get message:
```
$ ggpush
Counting objects: 2, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 354 bytes | 0 bytes/s, done.
Total 2 (delta 1), reused 0 (delta 0)
remote:
remote: Create merge request for master:
remote: https://gitlab.url/group/project/merge_requests/new?merge_request%5Bsource_branch%5D=master
remote:
To gitlab.url:group/project.wiki.git
bb5dfca..5f68a4b master -> master
```
### Expected behavior
No create merge request message should be displayed.
### Actual behavior
Create merge request message shown.https://gitlab.com/gitlab-org/gitlab-foss/-/issues/37087Commit message of new wiki page doesn't get stored2020-12-12T15:40:13Zblackst0neblackst0ne.ru@gmail.comCommit message of new wiki page doesn't get stored### Summary
A commit message is not stored when a user creates a new wiki page.
### Steps to reproduce
1. Open wikis.
2. Click to the `New page` button.
3. Type any slug in popped up window and click to the `Create page` button.
4. Wh...### Summary
A commit message is not stored when a user creates a new wiki page.
### Steps to reproduce
1. Open wikis.
2. Click to the `New page` button.
3. Type any slug in popped up window and click to the `Create page` button.
4. When an edit page is loaded, fill in content and type any custom message in the `Commit message` field.
5. Click to the `Create page` button.
6. When a page is loaded, you can see a wrong commit message in the history page.
Instead of the custom message, you will see the `USERNAME created page: PAGE TITLE` commit message.
Commits on page update get stored correctly.
### What is the current *bug* behavior?
A custom commit message on creating wiki page is not stored.
### What is the expected *correct* behavior?
A custom commit message on creating wiki page has to be stored.
### Output of checks
This bug happens on GitLab.com