- 11 Aug, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 01 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 20 Jul, 2017 1 commit
-
-
Sean McGivern authored
Use uploads/system directory for personal snippets See merge request !2123
-
- 18 Jul, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 12 Jun, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 08 Jun, 2017 3 commits
-
-
Bob Van Landuyt authored
-
DJ Mountney authored
Ran: - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch - git checkout -b 9-2-5-security-patch origin/v9.2.2 - git apply patchfile.patch - git commit - [Got the sha ref for the commit] - git checkout -b upstream-9-2-security master - git cherry-pick <SHA of the patchfile commit> - [Resolved conflicts] - git cherry-pick --continue
-
DJ Mountney authored
Ran: - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch - git checkout -b 9-2-5-security-patch origin/v9.2.2 - git apply patchfile.patch - git commit - [Got the sha ref for the commit] - git checkout -b upstream-9-2-security master - git cherry-pick <SHA of the patchfile commit> - [Resolved conflicts] - git cherry-pick --continue
-
- 07 Jun, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 06 Jun, 2017 1 commit
-
-
Stan Hu authored
Similar to #33218, build artifacts were being uploaded into a CarrierWave temporary directory in the Rails root directory before moved to their final destination, which could cause a copy across filesystems. This merge request refactors the work in !11866 so that any uploader can just override `work_dir` to change the default implementation. Closes #33274
-
- 05 Jun, 2017 1 commit
-
-
Stan Hu authored
The following was happening: 1. Workhorse stores an LFS file in /var/opt/gitlab/gitlab-rails/shared/lfs-objects 2. CarrierWave then renames the file to a temporary directory (e.g. /opt/gitlab/embedded/service/gitlab-rails/tmp) 3. CarrierWave then renames the file to its final location (e.g. /var/opt/gitlab/gitlab-rails/shared/lfs-objects) When the LFS upload path was on a different filesystem than the Rails installation, step 2 could take a longer than 10 seconds, at which point Workhorse would time out with "badgateway: failed after 10s: context canceled". This change makes the work path in the same root as the LFS storage path, preventing moves across filesystems. Closes #33218
-
- 01 Jun, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 31 May, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 02 May, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 09 Apr, 2017 1 commit
-
-
blackst0ne authored
-
- 06 Mar, 2017 2 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
- 24 Feb, 2017 1 commit
-
-
Robert Speicher authored
- Moves a duplicate `file_storage?` definition into the common `GitlabUploader` ancestor. - Get the `uploads` base directory from a class method rather than hard-coding it where it's needed. This will be used in a subsequent MR to store Uploads in the database. - Improves the specs for uploaders.
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 15 Feb, 2017 1 commit
-
-
Robert Speicher authored
Fix for XSS vulnerability in SVG attachments See https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/2059
-
- 03 Jan, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 15 Dec, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 08 Dec, 2016 1 commit
-
-
Andre Guedes authored
-
- 23 Nov, 2016 1 commit
-
-
Yorick Peterse authored
Flushing the events cache worked by updating a recent number of rows in the "events" table. This has the result that on PostgreSQL a lot of dead tuples are produced on a regular basis. This in turn means that PostgreSQL will spend considerable amounts of time vacuuming this table. This in turn can lead to an increase of database load. For GitLab.com we measured the impact of not using events caching and found no measurable increase in response timings. Meanwhile not flushing the events cache lead to the "events" table having no more dead tuples as now rows are only inserted into this table. As a result of this we are hereby removing events caching as it does not appear to help and only increases database load. For more information see the following comment: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
-
- 24 Jul, 2016 1 commit
-
-
winniehell authored
-
- 20 Jul, 2016 1 commit
-
-
Rémy Coutable authored
Handle videos in: - MD preview in notes: commit, issue/MR, MR diff - New notes in: commit, issue/MR, MR diff - Persisted notes in: commit, issue/MR, MR diff Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 19 Jul, 2016 4 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Eric Hayes authored
* Registered video MIME types * Currently supporting browser-supported formats with extensions that match the mime type
-
James Lopez authored
added spec for avatar saver avatar saver! added avatar restorer spec fix spec added avatar restorer class fix export service fix warnings, added changelog fix spec some refactoring based on feedback fixed a few issues after testing i/e avatar
-
- 29 Jun, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 30 Mar, 2016 4 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This attempts to get CarrierWave's uploader - `FileUploader` into test harness using a factory. that makes it easier to build an instance of it. Along with !3435 it may be easier to use uploaders in tests
-
Grzegorz Bizon authored
-
- 15 Mar, 2016 1 commit
-
-
Rémy Coutable authored
This reverts commit 01160fc0, reversing changes made to 4bff9daf.
-
- 18 Feb, 2016 1 commit
-
-
Johann Pardanaud authored
- Avoid multiple calls to `validates` for the avatar attributes. - In a cropping process, don't check if the model inherits `User`, check if it responds to `:avatar_crop_size`.
-
- 17 Feb, 2016 1 commit
-
-
Johann Pardanaud authored
-
- 16 Feb, 2016 1 commit
-
-
Johann Pardanaud authored
- Avoid incomprehensible errors on non-integer cropping values - Set the default cropping area to 80%
-