- 21 May, 2017 1 commit
-
-
Horatiu Eugen Vlad authored
Fixes #32598
-
- 18 May, 2017 4 commits
-
-
Douwe Maan authored
-
Bob Van Landuyt authored
-
Ruben Davila authored
This query was timing out and is blocking the sync of usage data for GitLab.com
-
Luke "Jared" Bennett authored
-
- 17 May, 2017 4 commits
-
-
Alejandro Rodríguez authored
-
Robert Speicher authored
-
Douwe Maan authored
-
Alejandro Rodríguez authored
This solves a problem where commits populated with Gitaly were not equal to commits populated with Rugged. This is because Gitaly may not return all fields of a commit for optimizations purposes, which resulted in false negatives when comparing the same commit (commits with the same sha) with different sources.
-
- 16 May, 2017 4 commits
-
-
Clement Ho authored
-
Alejandro Rodríguez authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Luke "Jared" Bennett authored
-
- 15 May, 2017 2 commits
-
-
Douwe Maan authored
-
Jacob Vosmaer authored
It seems that bad things happen when two gRPC stubs share one gRPC channel so let's stop doing that. The downside of this is that we create more gRPC connections; one per stub.
-
- 13 May, 2017 4 commits
-
-
Luke "Jared" Bennett authored
-
Ahmad Sherif authored
Closes gitaly#199
-
Adam Niedzielski authored
Closes #24438
-
Douwe Maan authored
-
- 12 May, 2017 9 commits
-
-
Gabriel Mazetto authored
-
Stan Hu authored
-
Sean McGivern authored
I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
-
James Lopez authored
-
Bob Van Landuyt authored
For exact matches, not namespaces that end with an invalid path
-
Douwe Maan authored
-
Yorick Peterse authored
By adding the default value _after_ adding the column we avoid updating all rows in a table, saving a lot of time and unnecessary work in the process.
-
Pawel Chojnacki authored
-
Valery Sizov authored
-
- 11 May, 2017 6 commits
-
-
Pawel Chojnacki authored
- Tests for prometheus queries - fix rubocop warnings - Remove unused method. Add more queries to deployment queries. - Wrap BaseQuery in module hierarchy Renname Prometheus class to PrometheusClient
-
Alejandro Rodríguez authored
-
Bob Van Landuyt authored
MySQL doesn't allow us to create a trigger for a column that doesn't exist yet. Failing with this error: ``` Mysql2::Error: Unknown column 'build_events' in 'NEW': CREATE TRIGGER trigger_6a80c097c862_insert BEFORE INSERT ON `services` FOR EACH ROW SET NEW.`build_events` = NEW.`job_events` ``` Creating the new column before creating the trigger avoids this.
-
Jacob Vosmaer authored
-
Sean McGivern authored
-
Douwe Maan authored
-
- 10 May, 2017 6 commits
-
-
David Turner authored
Signed-off-by: David Turner <novalis@novalis.org>
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Dosuken shinya authored
-
Douwe Maan authored
Respect project features in wiki and blob search See merge request !2089
-
Robert Speicher authored
(security-9-1) Render asciidoc & other markup using banzai in a pipeline See merge request !2098
-