- Jan 24, 2018
-
-
- Jan 23, 2018
-
-
Douwe Maan authored
-
- Jan 22, 2018
-
-
-
Alejandro Rodríguez authored
-
Alejandro Rodríguez authored
-
Kim "BKC" Carlbäcker authored
-
Yorick Peterse authored
This fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/38634.
-
- Jan 21, 2018
-
-
Mark Fletcher authored
-
Stan Hu authored
Closes #42249
-
- Jan 19, 2018
-
-
Mark Fletcher authored
-
Kim "BKC" Carlbäcker authored
-
Sean McGivern authored
Gitlab::Profiler.profile takes a URL to profile, and returns the ruby-prof profile result. This is currently only for interactive use (in a console) or from the script runner. Note that when using this interactively, changes to the application within that console session will be used, so this can be used to test proposed performance changes.
-
Kim "BKC" Carlbäcker authored
-
Resolve "Projects API: filter 'with_issues_enabled=true' returns projects with 'issues_enabled=false'"
-
- Jan 18, 2018
-
-
Gregory Stark authored
-
Kim "BKC" Carlbäcker authored
-
Nick Thomas authored
-
Jacob Vosmaer (GitLab) authored
-
-
Yorick Peterse authored
Prior to this commit we would essentially update all rows in a table, even those where the source column (e.g. `issues.closed_at`) was NULL. This in turn could lead to statement timeouts when using the default batch size of 10 000 rows per job. To work around this we don't schedule jobs for rows where the source value is NULL. We also don't update rows where the source column is NULL (as an extra precaution) or the target column already has a non-NULL value. Using this approach it should be possible to update 10 000 rows in the "issues" table in about 7.5 - 8 seconds. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/42158
-
Ben Bodenmiller authored
-
- Jan 17, 2018
-
-
Nick Thomas authored
-
Oswaldo Ferreir authored
-
Rémy Coutable authored
The performance bar is still displayed by default in development. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Jacob Vosmaer (GitLab) authored
-
Jacopo authored
Adds sorting to deployments API through the `order_by` and sort `fields`.
-
Robert Speicher authored
[10.3] Prevent login with disabled OAuth providers See merge request gitlab/gitlabhq!2296 (cherry picked from commit 4936650427ffc88e6ee927aedbb2c724d24b094c) a0f9d222 Prevents login with disabled OAuth providers
-
James Lopez authored
[10.3] Fix RCE via project import mechanism See merge request gitlab/gitlabhq!2294 (cherry picked from commit dcfec507d6f9ee119d65a832393e7c593af1d3b2) 86d75812 Fix RCE via project import mechanism
-
Robert Speicher authored
Merge branch '41293-fix-command-injection-vulnerability-on-system_hook_push-queue-through-web-hook' into 'security-10-3' Don't allow line breaks on HTTP headers See merge request gitlab/gitlabhq!2277 (cherry picked from commit 7fc0a6fc096768a5604d6dd24d7d952e53300c82) 073b8f9c Don't allow line breaks on HTTP headers
-
Douwe Maan authored
[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
-
Robert Speicher authored
[10.3] Fix path traversal in gitlab-ci.yml cache:key See merge request gitlab/gitlabhq!2270 (cherry picked from commit c32d0c6807dfd41d7838a35742e6d0986871b389) df29094a Fix path traversal in gitlab-ci.yml cache:key
-
Robert Speicher authored
[10.3] Fix XSS vulnerability in Pipeline job trace See merge request gitlab/gitlabhq!2258 (cherry picked from commit 44caa80ed9a2514a74a5eeab10ff51849d64851b) 5f86f3ff Fix XSS vulnerability in Pipeline job trace
-
Stan Hu authored
Merge branch 'security-10-3-do-not-expose-passwords-or-tokens-in-service-integrations-api' into 'security-10-3' Filter out sensitive fields from the project services API See merge request gitlab/gitlabhq!2281 (cherry picked from commit 476f2576444632f2a9a61b4cead9c1077f2c81d7) 2bcbbda0 Filter out sensitive fields from the project services API
-
- Jan 16, 2018
-
-
Serdar Dogruyol authored
-
Nick Thomas authored
-
James Edwards-Jones authored
-
Jacopo authored
Enables project milestone deletion via DELETE /projects/:id/milestones/:milestone_id
-
Sean McGivern authored
A file containing /:\d+:/ in its contents would break the search results if those contents were part of the results, because we were splitting on colons, which can't work with untrusted input. Changing to use the null byte as a separator is much safer.
-
Grzegorz Bizon authored
-
- Jan 15, 2018
-
-
Matija Čupić authored
-