- 25 Aug, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 24 Aug, 2017 4 commits
-
-
Sean McGivern authored
For some old merge requests, we don't have enough information to figure out the old blob and the new blob for the file. This means that we can't highlight the diff correctly, but we can still display it without highlighting.
-
Andrew Newdigate authored
-
Mehdi Lahmam authored
Closes #35994
-
Stan Hu authored
Users of project mirrors would see that the number of branches did not match the number in the branch dropdown because remote branches were counted when Rugged was in use. With Gitaly, only local branches are counted. Closes #36934
-
- 23 Aug, 2017 6 commits
-
-
Douwe Maan authored
Support simple string LDAP attribute specifications, and search for name rather than username attributes
-
Grzegorz Bizon authored
-
Yorick Peterse authored
Every project page displays a navigation menu that in turn displays the number of open issues and merge requests. This means that for every project page we run two COUNT(*) queries, each taking up roughly 30 milliseconds on GitLab.com. By caching these numbers and refreshing them whenever necessary we can reduce loading times of all these pages by up to roughly 60 milliseconds. The number of open issues does not include confidential issues. This is a trade-off to keep the code simple and to ensure refreshing the data only needs 2 COUNT(*) queries instead of 3. A downside is that if a project only has 5 confidential issues the counter will be set to 0. Because we now have 3 similar counting service classes the code previously used in Projects::ForksCountService has mostly been moved to Projects::CountService, which in turn is reused by the various service classes. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36622
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
- Allow imports into nested groups - Make sure it sets the correct visibility level when creating new groups While doing this, I moved the import into a testable class, that made it easier to improve.
-
Zeger-Jan van de Weg authored
It was missing and expected it wouldn't hurt anyone
-
- 22 Aug, 2017 22 commits
-
-
Clement Ho authored
-
Alejandro Rodríguez authored
-
Yorick Peterse authored
This changes the style of push events that remove tags or branches so they don't display the commit details. This prevents displaying commit details such as: 000000 . --broken encoding Instead we now simply display the header such as: Administrator deleted branch example-branch This is displayed in the same style as events for newly created branches/tags. This commit also ensures that if no commit message is present we simply don't display anything, instead of "--broken encoding". Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36685 Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36722
-
Tiago Botelho authored
-
Robert Speicher authored
Add `:broken_storage` metadata to examples to disable this behavior only when necessary.
-
Robert Speicher authored
Prevents these from failing on MySQL. Closes #36811 and #36812.
-
Rubén Dávila authored
-
Sean McGivern authored
We didn't have a fallback case before, because we believed the conditions were exhaustive. They weren't, so we can always fallback to not previewing.
-
Toon Claes authored
There might be some projects where the namespace was removed, but the project wasn't. For these the projects still have a `namespace_id` set. So this adds a post-deploy migration remove all projects that are pending delete, and have a `namespace_id` that is non-existing.
-
Zeger-Jan van de Weg authored
Also includes a change in allowing uploaded files, as there was a mismatch in object_id between classes, disallowing params[:file], which is a UploadedFile, newly loaded. The params checked against the older version. Fixes gitlab-org/gitlab-ce#36519
-
Nick Thomas authored
-
Shinya Maeda authored
-
James Lopez authored
-
James Lopez authored
-
Shinya Maeda authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
Using `extend` dynamically can lead to bad performance as it invalidates the method's cache.
-
Gabriel Mazetto authored
-
- 21 Aug, 2017 7 commits
-
-
Bryce Johnson authored
-
Alejandro Rodríguez authored
-
Yorick Peterse authored
This changes the caching mechanism so we cache both current _and_ future broadcast messages, then manually filter out those we don't want to display. This ensures we don't need any additional queries while still being able to display the right messages at the right time. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36661
-
Tiago Botelho authored
-
James Lopez authored
-
Stan Hu authored
-
Sean McGivern authored
This gem allows Sidekiq jobs to be throttled. Unfortunately, it has a side-effect: when we haven't enabled job throttling, it will still hit Redis a lot (and miss, because nothing is configured). As this setting already required a restart, ensure that the library is only required when it's enabled.
-