- 05 10月, 2017 4 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
Additionally we're delegating missing method calls on GpgKeySubkey to GpgKey since most of the info required when verifying a signature is found on GpgKey which is the parent of GpgKeySubkey
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
- 04 10月, 2017 2 次提交
-
-
由 Valery Sizov 提交于
-
由 Valery Sizov 提交于
-
- 03 10月, 2017 2 次提交
-
-
由 Greg Stark 提交于
-
由 Greg Stark 提交于
-
- 30 9月, 2017 1 次提交
-
-
由 Valery Sizov 提交于
-
- 29 9月, 2017 3 次提交
-
-
由 Lin Jen-Shin (godfat) 提交于
-
由 Sean McGivern 提交于
The first attempt didn't migrate all rows on GitLab.com, due to a couple of issues: 1. Some rows in merge_request_diffs had truly huge numbers of commits and diffs serialised - one in particular had 26,000 commits! 2. The jobs were sometimes on Sidekiq hosts with frequent OOM errors, leading to the job being lost. The previous commit adds more logging, and a more robust insertion method. This commit reschedules the jobs, with a generous pause between each.
-
由 Markus Koller 提交于
-
- 28 9月, 2017 2 次提交
-
-
由 Gabriel Mazetto 提交于
This is used in EE for the storage migration, and we want to use this in CE as well to be able to migrate projects to hashed_storage.
-
由 Yorick Peterse 提交于
This is a composite index on (target_project_id, merge_commit_sha, id) that allows queries such as the following to use a full backwards index scan: SELECT "merge_requests".* FROM "merge_requests" WHERE "merge_requests"."deleted_at" IS NULL AND "merge_requests"."target_project_id" = 13083 AND "merge_requests"."merge_commit_sha" = 'e80a893f' ORDER BY "merge_requests"."id" DESC LIMIT 1; Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/38507
-
- 26 9月, 2017 1 次提交
-
-
由 Greg Stark 提交于
Migration 20170919211300_remove_temporary_ci_builds_index.rb created a temporary partial index and tried to drop it at the end of the migration. In some circumstances apparently it failed to drop the index and it ended up in our schema.rb. This accidentally failed to fail due to a bug in the regular expression for partial indexes which caused the index creation in schema.rb to be ignored. Now that that's fixed we could be resurrecting this zombie index from the past in some but not all databases. Add a migration to drop this index if it's present to reconcile this discrepancy.
-
- 25 9月, 2017 1 次提交
-
-
由 Stan Hu 提交于
Missing parens prevented this migration from working in some cases. Closes #38246
-
- 23 9月, 2017 7 次提交
-
-
由 Brett Walker 提交于
-
由 Brett Walker 提交于
This reverts commit 9f186db09d7f380cfbde4c0061be77c272518547.
-
由 Brett Walker 提交于
-
由 Brett Walker 提交于
-
由 Brett Walker 提交于
-
由 Brett Walker 提交于
Send a confirmation email when the user adds a secondary email address. Utilizes the Devise `confirmable` capabilities. Issue #37385
-
由 Stan Hu 提交于
`email_provider` by default is NULL, and if a user had not logged the value would remain NULL. Upgrading to GitLab 10.0 would lead to a PG::UniqueViolation because the post-deploy migration would attempt to reinsert the entry because the NULL comparison between `users.email_provider` and `user_synced_attributes_metadata.email_provider` would never match. Closes #38246
-
- 21 9月, 2017 1 次提交
-
-
由 Nick Thomas 提交于
-
- 20 9月, 2017 2 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Valery Sizov 提交于
-
- 19 9月, 2017 2 次提交
-
-
由 Greg Stark 提交于
-
由 Yorick Peterse 提交于
This removes the need for a default scope that adds a "WHERE project_id = X" clause. This commit also includes an additional index for Environment#last_deployment, ensuring this query uses just an index scan instead of also applying a Filter. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36877
-
- 18 9月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 16 9月, 2017 1 次提交
-
-
由 Felipe Artur 提交于
-
- 15 9月, 2017 6 次提交
-
-
由 Michael Kozono 提交于
…to stay within our query timeout of 60s. Also reduce the job interval to keep the same overall migration time of ~3.3 days.
-
由 Michael Kozono 提交于
-
由 Michael Kozono 提交于
-
由 Michael Kozono 提交于
-
由 Michael Kozono 提交于
-
由 Yorick Peterse 提交于
This index is required to allow fast retrieval of recent push events without merge requests. Without this index in place the query would lead to PostgreSQL scanning over 150 000 index entries all the time, easily taking up between 200 and 500 milliseconds. This index reduces the time spent in this process to around 40 milliseconds on GitLab.com.
-
- 13 9月, 2017 3 次提交
-
-
由 Robert Speicher 提交于
This reverts merge request !14240
-
由 Yorick Peterse 提交于
-
由 Robert Speicher 提交于
This file is a duplicate of a post-deploy migration and appears to have been left in by mistake. Looping through the Users table in a foreground migration would've been a bad idea. [ci skip]
-