| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
This reverts the addition of the "goldiloader" Gem and all use of it.
While this Gem is very promising it's causing a variety of problems on
GitLab.com due to it eager-loading too much data in places where we
don't expect/can handle this. At least for the time being this means we
have to go back to manually fixing N+1 query problems, but at least
those should not cause a negative impact on availability.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Goldiloader is great, but has several issues with has_many :through relations:
* https://github.com/salsify/goldiloader/issues/12
* https://github.com/salsify/goldiloader/issues/14
* https://github.com/salsify/goldiloader/issues/18
Rather than try to figure out which applies in each case, we should just do the
drudge work of manually disabling autoloading for all relations of this type. We
can always use regular preloading for specific cases, but this way we avoid
generating invalid queries through Goldiloader's magic.
|
| | |
|
| |
|
|
| |
See merge request gitlab-org/gitlab-ee!4753
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Move uploads to object storage
Closes #4163
See merge request gitlab-org/gitlab-ee!3867
|
| |
|
|
|
|
| |
Transfer job archives after creation
See merge request gitlab-org/gitlab-ee!3646
|
| |\
| |
| |
| | |
object-storage-ee-to-ce-backport
|
| | | |
|
| |/
|
|
|
|
|
|
| |
Can migrate LFS objects to S3 style object storage
Closes #2841
See merge request !2760
|
| |
|
|
|
|
|
|
| |
This is allowed for existing instances so we don't end up 76 offenses
right away, but for new code one should _only_ use this if they _have_
to remove non database data. Even then it's usually better to do this in
a service class as this gives you more control over how to remove the
data (e.g. in bulk).
|
| | |
|
| |
|
|
|
|
|
|
|
| |
In 8278b763d96ef10c6494409b18b7eb541463af29 the default behaviour of annotation
has changes, which was causing a lot of noise in diffs. We decided in #17382
that it is better to get rid of the whole annotate gem, and instead let people
look at schema.rb for the columns in a table.
Fixes: #17382
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
access to the object.
|
| |
|
