Age | Commit message (Collapse) | Author |
|
See https://gitlab.com/gitlab-org/gitlab-ce/issues/47677 for more information
|
|
'47513-upload-migration-lease-key-is-incorrect-for-non-mounted-uploaders' into 'master'
Resolve "Upload migration lease key is incorrect for non-mounted uploaders"
Closes #47513
See merge request gitlab-org/gitlab-ce!19600
|
|
into 'master'
Resolve "`MigrateUploadsWorker` is doing N+1 queries on migration"
Closes #47408
See merge request gitlab-org/gitlab-ce!19547
|
|
|
|
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.
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Update rspec to 3.7
See merge request gitlab-org/gitlab-ce!19449
|
|
|
|
Customizable favicon
Closes #15661
See merge request gitlab-org/gitlab-ce!14497
|
|
|
|
|
|
|
|
|
|
|
|
Fix Fog mocking
Closes #47300
See merge request gitlab-org/gitlab-ce!19425
|
|
|
|
the initial reason for this change was that graphicsmagick does not
support writing to ico files. this fact lead to a chain of changes:
1. use png instead of ico (browser support is good enough)
2. render the overlays on the client using the canvas API. this way we
only need to store the original favion and generate the overlay versions
dynamically.
this change also enables (next step) to simplify the handling of the
stock favicons as well, as we don't need to generate all the versions
upfront.
|
|
this ways we can keep the `lib/gitlab/ci/status/*` classes to return the
bare favicon name as it was before.
also the favicon uploader versions are now have the same names as the
stock favicons (+ `favicon_` prefix), which makes working with the
status names easier.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
Introduce `direct_upload` option for `uploads` which is gonna set a default storage to Object Storage and use Unicorn to save data
|
|
|
|
|
|
|
|
|
|
|
|
File uploads on objects storage should use hashed storage
Closes #4952
See merge request gitlab-org/gitlab-ee!4597
|
|
|
|
|
|
|
|
|
|
|
|
object-storage-ee-to-ce-backport
|
|
Fix migrate! method (Minimal fix with ExclusiveLock to prevent race conditions)
Closes #4928 and #4980
See merge request gitlab-org/gitlab-ee!4624
|
|
object-storage-ee-to-ce-backport
|
|
|
|
This reverts commit 54a575f1bbba44573ab92dc58a4242f1ee734c5d, reversing
changes made to c63af942e5baf7849a94fa99da8494bcba28e3f8.
|
|
EE: Trace as artifacts (FileStorage and ObjectStorage)
Closes #4171
See merge request gitlab-org/gitlab-ee!4258
|
|
Move uploads to object storage
Closes #4163
See merge request gitlab-org/gitlab-ee!3867
|
|
object-storage-ee-to-ce-backport
|
|
Transfer job archives after creation
See merge request gitlab-org/gitlab-ee!3646
|
|
Multiple artifacts ee
See merge request gitlab-org/gitlab-ee!3276
|