- 05 6月, 2018 18 次提交
-
-
由 Kamil Trzciński 提交于
-
由 Jacob Vosmaer (GitLab) 提交于
-
由 Grzegorz Bizon 提交于
-
由 André Luís 提交于
-
由 Kamil Trzciński 提交于
-
由 Jose Ivan Vargas 提交于
-
由 Lin Jen-Shin 提交于
Since extending a class means including on the singleton class of the class, this should now complain this: ``` ruby module M extend Gitlab::Utils::Override override :f def f super.succ end end class C extend M def self.f 0 end end ``` It should complain because `C.f` wasn't calling `M#f`. This should pass verification: ``` ruby module M extend Gitlab::Utils::Override override :f def f super.succ end end class B def self.f 0 end end class C < B extend M end ``` Because `C.f` would now call `M#f`, and `M#f` does override something.
-
由 Oswaldo Ferreira 提交于
This currently causes 500's errors when loading the MR page (Discussion) in a few scenarios. We were not considering detailed diff headers such as "--- a/doc/update/mysql_to_postgresql.md\n+++ b/doc/update/mysql_to_postgresql.md" to crop the diff. In order to address it, we're now using Gitlab::Diff::Parser, clean the diffs and builds Gitlab::Diff::Line objects we can iterate and filter on.
-
由 Clement Ho 提交于
-
由 Stan Hu 提交于
-
由 Stan Hu 提交于
This was being masked by the statement cache because only one author was used per issue in the test.. Also adds support for an Rspec matcher `exceed_all_query_limit`.
-
由 Stan Hu 提交于
This was being masked by the statement cache because only one author was used per issue in the test.. Also adds support for an Rspec matcher `exceed_all_query_limit`.
-
由 Jose 提交于
-
由 Kamil Trzciński 提交于
-
由 Kamil Trzciński 提交于
-
由 Yorick Peterse 提交于
When importing a GitHub pull request we would perform all work in a single database transaction. This is less than ideal, because we perform various slow Git operations when creating a merge request. This in turn can lead to many DB connections being used, while just waiting for an IO operation to complete. To work around this, we now move most of the heavy lifting out of the database transaction. Some extra error handling is added to ensure we can resume importing a partially imported pull request, instead of just throwing an error. This commit also changes the specs for IssueImporter so they don't rely on deprecated RSpec methods.
-
由 Jarka Kadlecová 提交于
-
由 Jarka Kadlecová 提交于
-
- 04 6月, 2018 8 次提交
-
-
由 Bob Van Landuyt 提交于
Since we don't show the archived projects, we shouldnot load them and pass them to the fronted to be filtered out again.
-
由 Francisco Javier López 提交于
-
由 Kamil Trzciński 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
- 03 6月, 2018 3 次提交
-
-
由 Takuya Noguchi 提交于
-
由 Takuya Noguchi 提交于
This reverts commit 517598ba.
-
由 Stan Hu 提交于
There was a race condition in the spec where if the commit is created on disk within a second of the frozen `Timecop` time, the test fails. Closes #43981
-
- 02 6月, 2018 3 次提交
-
-
由 Shinya Maeda 提交于
-
由 Clement Ho 提交于
This reverts merge request !19304
-
由 Paul Slaughter 提交于
-
- 01 6月, 2018 8 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 🙈 jacopo beschi 🙉 提交于
-
由 Tiago Botelho 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Caching the attributes as JSON and manually instantiating the record ended-up very complex since the edge-cases such as upload fields, serialized fields, and fields with custom accessors had to be handled. To ensure 3 points out of 4 are checked from https://gitlab.com/gitlab-org/gitlab-ce/issues/45175 we now include the Rails version in the cache key. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Jacob Vosmaer (GitLab) 提交于
-
由 Jacob Vosmaer 提交于
-
由 Francisco Javier López 提交于
-