- Feb 14, 2018
-
-
Kamil Trzcińśki authored
-
George Tsiolis authored
-
🙈 jacopo beschi 🙉 authored
-
Robert Schilling authored
-
Jarka Kadlecova authored
-
- Feb 13, 2018
-
-
Filipa Lacerda authored
-
Andreas Brandl authored
Closes #42800.
-
Drew Blessing authored
Constructors shouldn't throw exceptions. We also learned that different LDAP servers behave a bit unexpectedly sometimes - returning attributes we didn't ask for, or returned attributes with language subtypes.
-
Jeff Stubler authored
Closes #26466.
-
Dylan Griffith authored
-
- Feb 12, 2018
-
-
Michael Kozono authored
-
Rubén Dávila authored
This reverts commit a58f8c32, reversing changes made to cd5d75c3.
-
-
Onuwa Nnachi Isaac authored
-
Winnie Hellmann authored
-
George Tsiolis authored
-
- Feb 09, 2018
-
-
Filipa Lacerda authored
-
Robert Speicher authored
-
Kamil Trzcińśki authored
Fix using wildcards in protected tags to expose protected variables
-
[10.4] Fix GH namespace security issue
-
Robert Speicher authored
Restrict Todo API mark_as_done endpoint to the user's todos only
-
Douwe Maan authored
[10.4] Fix stored XSS in code blocks
-
Robert Schilling authored
-
Robert Schilling authored
-
Filipa Lacerda authored
Adds CSS for child envrionments
-
- Feb 08, 2018
-
-
George Tsiolis authored
-
Lin Jen-Shin authored
-
Markus Koller authored
-
Hassan Zamani authored
-
Gregory Stark authored
Artifacts are in the middle of being migrated from ci_builds to ci_job_artifacts. The expiration date is currently visible in both of these tables and the test for whether an expired artifact is present for a job is complex as it requires checking both the of the tables. Add two new indexes, one on ci_builds.artifacts_expire_at and one on ci_job_artifacts.expire_at to enable finding expired artifacts efficiently. And until the migration is finished, replace the SQL for finding expired and non-expired artifacts with a hand-crafted UNION ALL based query instead of using OR. This overcomes a database optimizer limitation that prevents it from using these indexes. When the migration is finished the next version should remove this query and replace it with a much simpler query on just ci_job_artifacts. See https://gitlab.com/gitlab-org/gitlab-ce/issues/42561 for followup.
-
Bob Van Landuyt authored
Since populating the fork networks was scheduled multiple times because of bugs that needed to be fixed: - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15595/ Creating fork networks for projects that were missing the root of the fork network. - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15709 The API allowed creating forked_project_links without fork_network_members. Scheduling this migration multiple times would case it to run concurrently. Which in turn would try to insert the same data into `fork_network_members` causing duplicate key errors. This avoids running the migration multiple times.
-
Shah El-Rahman authored
-
Shah El-Rahman authored
-
- Feb 07, 2018
-
-
Simon Knox authored
-
Oswaldo Ferreir authored
-
Rubén Dávila authored
-
-
Dylan Griffith authored
-
- Feb 06, 2018
-
-
Andreas Brandl authored
Closes #40755.
-