delta/gitlab/gitlab-ce.git/spec/controllers/concerns, branch docs-avoid-CephFS-GlusterFS gitlab.com: gitlab-org/gitlab-ce.git Bump fog-aws to 3.3.0 and associated dependencies 2019-03-01T06:51:03+00:00 Stan Hu stanhu@gmail.com 2019-01-24T06:17:31+00:00 4193e3d47543abfd533f5bc73753a2d31ab9eb22 Fixes issue with AWS V4 signatures not working with Ceph S3: https://github.com/fog/fog-aws/issues/462 
Fixes issue with AWS V4 signatures not working with Ceph S3:
https://github.com/fog/fog-aws/issues/462
Merge branch 'filter-confidential-issues' into 'master' 2019-02-26T11:24:39+00:00 Kamil Trzciński ayufan@ayufan.eu 2019-02-25T11:00:24+00:00 a555a227dd7a846e5b8e8c84839120d40f9d1090 Ability to filter confidential issues Closes #50747 See merge request gitlab-org/gitlab-ce!24960 
Ability to filter confidential issues

Closes #50747

See merge request gitlab-org/gitlab-ce!24960
 Revert "Merge branch 'filter-confidential-issues' into 'master'" 2019-02-25T20:42:34+00:00 Michael Kozono mkozono@gmail.com 2019-02-25T20:42:34+00:00 e95b88a06d673ff95792d5c7d3934c88051691d9 This reverts commit d133bf84c668df3dfc9938bb04150754cb873c8b, reversing changes made to 7981c0292b07a0138b096fa082341fcb13e9ce2b. 
This reverts commit d133bf84c668df3dfc9938bb04150754cb873c8b, reversing
changes made to 7981c0292b07a0138b096fa082341fcb13e9ce2b.
Only use boolean parameters internally 2019-02-22T13:55:07+00:00 Robert Schilling rschilling@student.tugraz.at 2019-02-22T09:19:25+00:00 bf7846bec07157a8023770d03854834cceb69e3d Use internally only boolean params. 
Use internally only boolean params.
Ability to filter confidential issues 2019-02-21T13:02:38+00:00 Robert Schilling rschilling@student.tugraz.at 2019-02-06T12:31:56+00:00 bd9ae901ec0bc0f9d1060e9128ecd5f8d8127671 Add a new search bar filter for confidential issues. Add filtering support to the IssuesFinder. 
Add a new search bar filter for confidential issues. Add filtering
support to the IssuesFinder.
Fix Content-Disposition hard-coded to attachments 2019-02-13T19:09:52+00:00 Stan Hu stanhu@gmail.com 2019-02-13T18:46:14+00:00 134420f2eff904f9e40165751fcd8700b0770157 Due to a regression in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24919, Content-Disposition is hard-coded to `attachment` instead of `inline`. We now use the argument `disposition` to fix that problem. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57660 
Due to a regression in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24919,
Content-Disposition is hard-coded to `attachment` instead of `inline`.
We now use the argument `disposition` to fix that problem.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57660
Encode Content-Disposition filenames 2019-02-05T07:12:44+00:00 Stan Hu stanhu@gmail.com 2019-02-05T01:27:22+00:00 41b51c065604091579a2308adc527fe5bb187abe Users downloading non-ASCII attachments would see garbled characters. When used with object storage, AWS S3 would return an InvalidArgument error: Header value cannot be represented using ISO-8859-1. Per RFC 5987 and RFC 6266, Content-Disposition should be encoded properly. This commit takes the Rails 6 implementation of ActiveSuppport::Http::ContentDisposition (https://github.com/rails/rails/pull/33829) and ports it here. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/47673 
Users downloading non-ASCII attachments would see garbled characters.
When used with object storage, AWS S3 would return an InvalidArgument
error: Header value cannot be represented using ISO-8859-1.

Per RFC 5987 and RFC 6266, Content-Disposition should be encoded
properly. This commit takes the Rails 6 implementation of
ActiveSuppport::Http::ContentDisposition
(https://github.com/rails/rails/pull/33829) and ports it here.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/47673
Save sorting preference for Issues/MRs in BE 2019-01-28T18:48:05+00:00 Mario de la Ossa mariodelaossa@gmail.com 2019-01-07T00:00:48+00:00 49c74068ae7f0017ebeb8e7daa2c556fef3124e3 In order to let users' sorting preferences transfer between devices, we save the preference for issues and MRs (one preference for issues, one for MRs) in the backend inside the UserPreference object 
In order to let users' sorting preferences transfer between devices, we
save the preference for issues and MRs (one preference for issues, one
for MRs) in the backend inside the UserPreference object
Enable the Layout/ExtraSpacing cop 2019-01-24T12:05:45+00:00 Rémy Coutable remy@rymai.me 2019-01-16T12:09:29+00:00 3a2abc1d50b419a353edb7f7cf68f3894dfdeeef Signed-off-by: Rémy Coutable <remy@rymai.me> 
Signed-off-by: Rémy Coutable <remy@rymai.me>
Update specs to rails5 format 2018-12-18T23:04:31+00:00 blackst0ne blackst0ne.ru@gmail.com 2018-12-17T22:52:17+00:00 b44a2c801a64fb282cea794871fcfcf81e4ec539 Updates specs to use new rails5 format. The old format: `get :show, { some: params }, { some: headers }` The new format: `get :show, params: { some: params }, headers: { some: headers }` 
Updates specs to use new rails5 format.

The old format:
`get :show, { some: params }, { some: headers }`

The new format:
`get :show, params: { some: params }, headers: { some: headers }`