- 05 1月, 2018 1 次提交
-
-
由 Mayra Cabrera 提交于
-
- 04 1月, 2018 7 次提交
-
-
由 Yorick Peterse 提交于
This ensures that the "author" association of an event's "target" association is eager loaded whenever the "target" association defines an "author" association. This in turn solves the N+1 query problem we first tried to solve in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15788 but caused problems when displaying milestones as those don't define an "author" association. The approach in this commit does mean that the authors are _always_ eager loaded since this takes place in the "belongs_to" block. This however shouldn't pose too much of a problem, and as far as I can tell there's no real way around this unfortunately.
-
由 Mayra Cabrera 提交于
-
-
-
-
-
-
- 03 1月, 2018 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 02 1月, 2018 1 次提交
-
-
由 Francisco Javier López 提交于
-
- 31 12月, 2017 1 次提交
-
-
由 Mario de la Ossa 提交于
This change is required because otherwise if a user is created with a value for `projects_limit` that matches the DB default, it gets overwritten by `current_application_settings.default_projects_limit`. By removing the default we once again can allow a user to be created with a limit of 10 projects without the risk that it'll change to 10000
-
- 29 12月, 2017 1 次提交
-
-
由 Jarka Kadlecová 提交于
-
- 23 12月, 2017 2 次提交
-
-
由 Mayra Cabrera 提交于
-
由 Douwe Maan 提交于
Improve performance of DiffDiscussion#truncated_diff_lines and DiffNote#diff_line by removing expensive diff position calculation and comparison
-
- 22 12月, 2017 1 次提交
-
-
由 blackst0ne 提交于
-
- 21 12月, 2017 2 次提交
-
-
由 Francisco Javier López 提交于
-
由 Kim Carlbäcker 提交于
This reverts merge request !15712
-
- 20 12月, 2017 4 次提交
-
-
由 Robert Speicher 提交于
-
由 Robert Speicher 提交于
Previously, this would include the entire User record in the update hash, which was rendered in the response using `to_json`, erroneously exposing every attribute of that record, including their (now removed) private token. Now we only include the user ID, and perform the lookup on-demand.
-
由 Robert Speicher 提交于
-
由 Robert Speicher 提交于
-
- 19 12月, 2017 3 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Uses `list_commits_by_oid` on the CommitService, to request the needed commits for pipelines. These commits are needed to display the user that created the commit and the commit title. This includes fixes for tests failing that depended on the commit being `nil`. However, now these are batch loaded, this doesn't happen anymore and the commits are an instance of BatchLoader.
-
由 Mario de la Ossa 提交于
-
由 Mario de la Ossa 提交于
-
- 18 12月, 2017 2 次提交
-
-
由 Stanislaw Wozniak 提交于
-
由 Christiaan Van den Poel 提交于
-
- 14 12月, 2017 8 次提交
-
-
由 Rémy Coutable 提交于
I've followed the [upgrade guide](https://github.com/thoughtbot/factory_bot/blob/4-9-0-stable/UPGRADE_FROM_FACTORY_GIRL.md) and ran these two commands: ``` grep -e FactoryGirl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|FactoryGirl|FactoryBot|" grep -e factory_girl **/*.rake **/*.rb -s -l | xargs sed -i "" "s|factory_girl|factory_bot|" ``` Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 haseeb 提交于
-
由 Zeger-Jan van de Weg 提交于
The hook ordering influenced the diffs being generated as these used values from before the update due to the memoization still being in place. This commit reorders them and tests against this behaviour.
-
由 Shinya Maeda 提交于
-
由 Toon Claes 提交于
When a note is part of a discussion, the email sent out will be `In-Reply-To` the previous note in that discussion. It also `References` all the previous notes in that discussion, and the original issue. Closes gitlab-org/gitlab-ce#36054.
-
由 Toon Claes 提交于
When a note is part of a discussion, the email sent out should be `In-Reply-To` the previous note in that discussion. Closes gitlab-org/gitlab-ce#36054
-
由 Jacopo 提交于
Allows ordering in GET api/v4/projects/:project_id/repository/contributors through `order_by` and `sort` params. The available `order_by` options are: name|email|commits. The available `sort` options are: asc|desc.
-
由 Ahmad Sherif 提交于
Closes gitaly#808
-
- 13 12月, 2017 2 次提交
-
-
由 Felipe Artur 提交于
-
由 Stan Hu 提交于
-
- 12 12月, 2017 3 次提交
-
-
由 Zeger-Jan van de Weg 提交于
The Gitaly CommitService is being hammered by n + 1 calls, mostly when finding commits. This leads to this gRPC being turned of on production: https://gitlab.com/gitlab-org/gitaly/issues/514#note_48991378 Hunting down where it came from, most of them were due to MergeRequest#show. To prove this, I set a script to request the MergeRequest#show page 50 times. The GDK was being scraped by Prometheus, where we have metrics on controller#action and their Gitaly calls performed. On both occations I've restarted the full GDK so all caches had to be rebuild. Current master, 806a68a8, needed 435 requests After this commit, 154 requests
-
由 Kim "BKC" Carlbäcker 提交于
-
由 Greg Stark 提交于
Treat empty markdown and html strings as valid cached text, not missing cache that needs to be updated
-
- 11 12月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-