- 03 2月, 2018 1 次提交
-
-
由 Matija Čupić 提交于
-
- 02 2月, 2018 5 次提交
-
-
由 James Lopez 提交于
-
由 Andreas Brandl 提交于
-
由 Matija Čupić 提交于
-
由 Micaël Bergeron 提交于
-
由 Micaël Bergeron 提交于
-
- 01 2月, 2018 1 次提交
-
-
由 Yorick Peterse 提交于
In the event of Sidekiq jobs getting lost there may be some rows left to migrate. This migration ensures any remaining jobs are completed and that all data has been migrated. This fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/41595
-
- 27 1月, 2018 1 次提交
-
-
由 Matija Čupić 提交于
-
- 24 1月, 2018 1 次提交
-
-
由 Jan Provaznik 提交于
Search query is especially slow if a user searches a generic string which matches many records, in such case search can take tens of seconds or time out. To speed up the search query, we search only for first 1000 records, if there is >1000 matching records we just display "1000+" instead of precise total count supposing that with such amount the exact count is not so important for the user. Because for issues even limited search was not fast enough, 2-phase approach is used for issues: first we use simpler/faster query to get all public issues, if this exceeds the limit, we just return the limit. If the amount of matching results is lower than limit, we re-run more complex search query (which includes also confidential issues). Re-running the complex query should be fast enough in such case because the amount of matching issues is lower than limit. Because exact total_count is now limited, this patch also switches to to "prev/next" pagination. Related #40540
-
- 19 1月, 2018 1 次提交
-
-
由 Greg Stark 提交于
-
- 17 1月, 2018 2 次提交
-
-
由 Stan Hu 提交于
-
由 Douwe Maan 提交于
[10.3] Migrate `can_push` column from `keys` to `deploy_keys_project` See merge request gitlab/gitlabhq!2276 (cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c) 1f2bd3c0 Backport to 10.3
-
- 16 1月, 2018 1 次提交
-
-
由 Drew Blessing 提交于
Previously, the last push widget would only show when the branch never had a merge request associated with it - even merged or closed ones. Now the widget will disregard merge requests that are merged or closed.
-
- 13 1月, 2018 1 次提交
-
-
由 Hiroyuki Sato 提交于
-
- 11 1月, 2018 1 次提交
-
-
由 Jan Provaznik 提交于
For each MR diff an extra 'SELECT COUNT()' is executed to get number of commits for the diff. Overall time to get counts for all MR diffs may be quite expensive. To speed up loading of MR info, information about number of commits is stored in a MR diff's extra column. Closes #38068
-
- 09 1月, 2018 3 次提交
-
-
由 Michael Kozono 提交于
Originally from branch 'fix-authorized-keys-enabled-default-2738' via merge request https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2240 Removed background migrations which were intended to fix state after using Gitlab without a default having been set Squashed commits: Locally, if Spring was not restarted, `current_application_settings` was still cached, which prevented the migration from editing the file. This will also ensure that any app server somehow hitting old cache data will properly default this setting regardless. Retroactively fix migration This allows us to identify customers who ran the broken migration. Their `authorized_keys_enabled` column does not have a default at this point. We will fix the column after we fix the `authorized_keys` file. Fix authorized_keys file if needed Add default to authorized_keys_enabled setting Reminder: The original migration was fixed retroactively a few commits ago, so people who did not ever run GitLab 9.3.0 already have a column that defaults to true and disallows nulls. I have tested on PostgreSQL and MySQL that it is safe to run this migration regardless. Affected customers who did run 9.3.0 are the ones who need this migration to fix the authorized_keys_enabled column. The reason for the retroactive fix plus this migration is that it allows us to run a migration in between to fix the authorized_keys file only for those who ran 9.3.0. Tweaks to address feedback Extract work into background migration Move batch-add-logic to background migration Do the work synchronously to avoid multiple workers attempting to add batches of keys at the same time. Also, make the delete portion wait until after adding is done. Do read and delete work in background migration Fix Rubocop offenses Add changelog entry Inform the user of actions taken or not taken Prevent unnecessary `select`s and `remove_key`s Add logs for action taken Fix optimization Reuse `Gitlab::ShellAdapter` Guarantee the earliest key Fix migration spec for MySQL
-
由 Michael Kozono 提交于
Originally branch 'mk-toggle-writing-to-auth-keys-1631' See merge request !2004 Squashed commits: Add authorized_keys_enabled to Application Settings Ensure default settings are exposed in UI Without this change, `authorized_keys_enabled` is unchecked when it is nil, even if it should be checked by default. Add “Speed up SSH operations” documentation Clarify the reasons for disabling writes Add "How to go back" section Tweak copy Update Application Setting screenshot
-
由 Yorick Peterse 提交于
This removes all usage of soft removals except for the "pending delete" system implemented for projects. This in turn simplifies all the query plans of the models that used soft removals. Since we don't really use soft removals for anything useful there's no point in keeping it around. This _does_ mean that hard removals of issues (which only admins can do if I'm not mistaken) can influence the "iid" values, but that code is broken to begin with. More on this (and how to fix it) can be found in https://gitlab.com/gitlab-org/gitlab-ce/issues/31114. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447
-
- 05 1月, 2018 2 次提交
-
-
由 Jan Provaznik 提交于
When a project uses fast-forward merging strategy user has to rebase MRs to target branch before it can be merged. Now user can do rebase in UI by clicking 'Rebase' button instead of doing rebase locally. This feature was already present in EE, this is only backport of the feature to CE. Couple of changes: * removed rebase license check * renamed migration (changed timestamp) Closes #40301
-
由 Matija Čupić 提交于
-
- 03 1月, 2018 2 次提交
-
-
由 Yorick Peterse 提交于
In a previous attempt (rolled back in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16021) we tried to migrate `issues.closed_at` from timestamp to timestamptz using a regular migration. This has a bad impact on GitLab.com and as such was rolled back. This commit re-implements the original migrations using generic background migrations, allowing us to still migrate the data in a single release but without a negative impact on availability. To ensure the database schema is up to date the background migrations are performed inline in development and test environments. We also make sure to not migrate that that doesn't need migrating in the first place or has already been migrated.
-
由 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
-
- 23 12月, 2017 3 次提交
-
-
由 Matija Čupić 提交于
-
由 Matija Čupić 提交于
-
由 Mayra Cabrera 提交于
-
- 22 12月, 2017 1 次提交
-
-
由 Greg Stark 提交于
-
- 21 12月, 2017 1 次提交
-
-
由 Francisco Javier López 提交于
-
- 13 12月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 11 12月, 2017 1 次提交
-
-
由 Valery Sizov 提交于
-
- 09 12月, 2017 1 次提交
-
-
由 Mayra Cabrera 提交于
-
- 08 12月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
Moving the check out of the general requests, makes sure we don't have any slowdown in the regular requests. To keep the process performing this checks small, the check is still performed inside a unicorn. But that is called from a process running on the same server. Because the checks are now done outside normal request, we can have a simpler failure strategy: The check is now performed in the background every `circuitbreaker_check_interval`. Failures are logged in redis. The failures are reset when the check succeeds. Per check we will try `circuitbreaker_access_retries` times within `circuitbreaker_storage_timeout` seconds. When the number of failures exceeds `circuitbreaker_failure_count_threshold`, we will block access to the storage. After `failure_reset_time` of no checks, we will clear the stored failures. This could happen when the process that performs the checks is not running.
-
- 07 12月, 2017 2 次提交
-
-
由 James Edwards-Jones 提交于
-
由 Francisco Javier López 提交于
-
- 05 12月, 2017 4 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Markus Koller 提交于
-
- 03 12月, 2017 1 次提交
-
-
由 Kamil Trzcinski 提交于
-