- 08 Dec, 2017 2 commits
-
-
Bob Van Landuyt authored
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 Dec, 2017 7 commits
-
-
Achilleas Pipinellis authored
-
Marcia Ramos authored
-
Marcia Ramos authored
-
Marcia Ramos authored
-
Shinya Maeda authored
-
Marcia Ramos authored
-
James Edwards-Jones authored
In EE we now allow individual users/groups to be set on POST, which required some refactoring. See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3516
-
- 06 Dec, 2017 5 commits
-
-
Takuya Noguchi authored
-
Marcia Ramos authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 05 Dec, 2017 4 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Jan Provaznik authored
* new merge request can be created by sending an email to the specific email address (similar to creating issues by email) * for the first iteration, source branch must be specified in the mail subject, other merge request parameters can not be set yet * user should enable "Receive notifications about your own activity" in user settings to receive a notification about created merge request Part of #32878
-
- 04 Dec, 2017 5 commits
-
-
Marcia Ramos authored
- Assign issues and MRs - Label issues and MRs - Reorder a couple of items in the table to go from unchecked to checked - Add/remove spaces so that the dividers stay in the same column in the file
-
Victor Wu authored
-
bikebilly authored
-
Markus Koller authored
-
Annabel Dunstone Gray authored
-
- 03 Dec, 2017 1 commit
-
-
Takuya Noguchi authored
-
- 01 Dec, 2017 3 commits
-
-
Koichiro Mikami authored
-
Achilleas Pipinellis authored
-
Lyle Kozloff authored
-
- 29 Nov, 2017 2 commits
-
-
haseeb authored
-
digitalMoksha authored
(to be consistent)
-
- 28 Nov, 2017 5 commits
-
-
Greg Stark authored
-
Abubakar Ango authored
-
Sean McGivern authored
The st_commits and st_diffs columns on merge_request_diffs historically held the YAML-serialised data for a merge request diff, in a variety of formats. Since 9.5, these have been migrated in the background to two new tables: merge_request_diff_commits and merge_request_diff_files. That has the advantage that we can actually query the data (for instance, to find out how many commits we've stored), and that it can't be in a variety of formats, but must match the new schema. This is the final step of that journey, where we drop those columns and remove all references to them. This is a breaking change to the importer, because we can no longer import diffs created in the old format, and we cannot guarantee the export will be in the new format unless it was generated after this commit.
-
Sean McGivern authored
Sidekiq has to be running too.
- 27 Nov, 2017 3 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
- 25 Nov, 2017 1 commit
-
-
David Muckle authored
-
- 24 Nov, 2017 2 commits
-
-
Christiaan Van den Poel authored
-
James Edwards-Jones authored
Before an access_level was required in EE even when an it had been set for a user/group.
-