- Sep 04, 2019
-
-
- Apr 30, 2019
-
-
Heinrich Lee Yu authored
Prepares us for upgrade to Rails 5.2
-
- Mar 30, 2019
-
-
Bastian Blank authored
Set ACL of uploaded objects to not-public (fog-aws) or no ACL at all (fog-google). Value is ignored by other supported backends (fog-aliyun, fog-openstack, fog-rackspace) This allows uploads to GCS with ACL support disabled.
-
- Jul 05, 2018
-
-
gfyoung authored
Partially addresses #47424.
-
- Jun 13, 2018
-
-
Jan Provaznik authored
-
- Jun 12, 2018
-
-
Micael Bergeron authored
-
Jan Provaznik authored
-
Jan Provaznik authored
For FileUploaders it's possible that a model has many uploads and if lease key is created only from model id, it causes that the model's uploads can not be migrated in parallel because the exclusive lease key would be same for all uploads of the model.
-
- Jun 11, 2018
-
-
Lin Jen-Shin authored
-
- Jun 08, 2018
-
-
Micael Bergeron authored
-
- Jun 07, 2018
-
-
Micael Bergeron authored
-
Micael Bergeron authored
-
- Jun 06, 2018
-
-
Micael Bergeron authored
-
- Jun 05, 2018
-
-
Sean McGivern authored
This is tricky: the query was being run in `ObjectStorage::Extension::RecordsUploads#retrieve_from_store!`, but we can't just add batch loading there, because the `#upload=` method there would use the result immediately, making the batch only have one item. Instead, we can pre-emptively add an item to the batch whenever an avatarable object is initialized, and then reuse that batch item in `#retrieve_from_store!`. However, this also has problems: 1. There is a lot of logic in `Avatarable#retrieve_upload_from_batch`. 2. Some of that logic constructs a 'fake' model for the batch key. This should be fine, because of ActiveRecord's override of `#==`, but it relies on that staying the same.
-
- Jun 04, 2018
-
-
Kamil Trzcińśki authored
-
- May 29, 2018
-
-
Alessio Caiazza authored
-
- May 28, 2018
-
-
Shinya Maeda authored
-
- May 23, 2018
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Apr 19, 2018
-
-
Kamil Trzcińśki authored
Old records have a null value of file_store column. This causes the problems with current direct_upload implementation, as this makes it to choose Store::REMOTE instead of Store::LOCAL. This change moves the store save when change saving the object.
-
- Apr 05, 2018
-
-
Kamil Trzcińśki authored
-
- Apr 04, 2018
-
-
Kamil Trzcińśki authored
Introduce `direct_upload` option for `uploads` which is gonna set a default storage to Object Storage and use Unicorn to save data
-
- Mar 29, 2018
-
-
Alessio Caiazza authored
-
- Mar 27, 2018
-
-
Alessio Caiazza authored
-
- Mar 26, 2018
-
-
Micael Bergeron authored
-
- Mar 09, 2018
-
-
Micael Bergeron authored
-
- Mar 01, 2018
-
-
Micael Bergeron authored
Fix migrate! method (Minimal fix with ExclusiveLock to prevent race conditions) Closes #4928 and #4980 See merge request gitlab-org/gitlab-ee!4624
-
Micael Bergeron authored
-
Micael Bergeron authored
-
Micael Bergeron authored
-
- Feb 28, 2018
-
-
Kamil Trzcińśki authored
Fix migrate! method (Minimal fix with ExclusiveLock to prevent race conditions) Closes #4928 and #4980 See merge request gitlab-org/gitlab-ee!4624
-
Sean McGivern authored
Move uploads to object storage Closes #4163 See merge request gitlab-org/gitlab-ee!3867
-