Age | Commit message (Collapse) | Author |
|
|
|
Remove code related to object hierarchy and MySQL
Closes #65056 and #65055
See merge request gitlab-org/gitlab-ce!31095
|
|
Fix error rendering submodules in MR diffs when there is no .gitmodules
See merge request gitlab-org/gitlab-ce!31162
|
|
Without this change, we get a NoMethodError on nil
|
|
Logging sidekiq worker class name in SidekiqMemoryKiller
See merge request gitlab-org/gitlab-ce!30996
|
|
Add frozen_string_literal to spec/support
See merge request gitlab-org/gitlab-ce!31132
|
|
Resolve "table_exists? not compatible with Rails 5.1"
Closes #54478
See merge request gitlab-org/gitlab-ce!30832
|
|
Support Docker OCI images
Closes gitlab-ee#12877 and #58685
See merge request gitlab-org/gitlab-ce!31127
|
|
Refactor usage data counters specs
See merge request gitlab-org/gitlab-ce!31013
|
|
This was shown in specs but surely this will be happening in application
code as well if this method is passes a frozen string.
We were also trying to force_encode a OmniAuth::AuthHash which had the
very confusing behaviour of returning nil when it was sent a method that
it did not define. Fix that by only force_encoding a String.
|
|
Docker Distribution v2.7.0 shipped with OCI support, but our container
registry client was not updated to handle the manifest format in the
HTTP `Accept` header. As a result, API calls to retrieve a manifest
would return with an error, "OCI manifest found, but accept header does
not support OCI manifests". This would result in blank fields in the
container registry page and prevent tags from being deleted.
To fix this, we just need to add
`application/vnd.oci.image.manifest.v1+json` to the `Accept` header and
configure Faraday to parse the response as JSON. The response structure
is the same as the standard Docker Distribution V2 manifest.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58685
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/12877
|
|
Currently, SidekiqMemoryKiller does not feed worker class name in the
json structured logging. This commit extends the json parameter.
|
|
These are not required because MySQL is not
supported anymore
|
|
Changes all calls to data_source_exists? to table_exists?
since that is the intent of these calls
|
|
* Limits raw requests to 300 per minute and per raw path.
* Add a new attribute to ApplicationSettings so user can change this
value on their instance.
* Uses Gitlab::ActionRateLimiter to limit the raw requests.
* Add a new method into ActionRateLimiter to log the event into auth.log
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/48717
|
|
Resolves confusion within spec rake tasks.
See merge request gitlab-org/gitlab-ce!31073
|
|
Optimise import performance
Closes #64924
See merge request gitlab-org/gitlab-ce!31045
|
|
Signed-off-by: Istvan szalai <istvan.szalai@savoirfairelinux.com>
|
|
Use a base class for Peek views
See merge request gitlab-org/gitlab-ce!31108
|
|
https://gitlab.com/gitlab-org/gitlab-ce/issues/58792
|
|
Introduce a `DetailedView` base class, which is inherited by
the Gitaly, Redis, and Rugged views. This reduces code duplication.
|
|
- Fix `O(n)` complexity of `append_or_update_attribute`,
we append objects to an array and re-save project
- Remove the usage of `keys.include?` as it performs `O(n)`
search, instead use `.has_key?`
- Remove the usage of `.keys.first` as it performs a copy
of all keys, instead use `.first.first`
|
|
Add Rugged calls to performance bar
See merge request gitlab-org/gitlab-ce!30983
|
|
A project can have the same `LfsObject` linked with up to three
`LfsObjectsProject` records. Each of these records would be for a
different repository, recorded in the `repository_type` property. The
different repositories at time of writing are "project", "wiki", and
"design". See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894
This change exports the list of `repository_type`s as a JSON mapping of
oid => repository_types, which are imported to recreate the correct
`LfsObjectsProject` records.
https://gitlab.com/gitlab-org/gitlab-ee/issues/11090
|
|
Although `flat_map` is equivalent to `map` + `flatten(1)`
(note the level 1) we can apply this same refactoring to all cases.
|
|
|
|
This will help diagnose the source of excessive I/O from Rugged
calls. To implement this, we need to obtain the full list of arguments
sent to each request method.
|
|
|
|
Remove dead mysql code
Closes #63191
See merge request gitlab-org/gitlab-ce!29608
|
|
into 'master'
Adjust group level analytics to accept multiple projects ids
See merge request gitlab-org/gitlab-ce!30744
|
|
None of this code can be reached any more, so it can all be removed
|
|
Extra logging for new live trace architecture
See merge request gitlab-org/gitlab-ce!30892
|
|
Use persistent Redis cluster for Workhorse pub/sub notifications
See merge request gitlab-org/gitlab-ce!30990
|
|
'master'
Add better error message to MembersMapper#ensure_default_member!
See merge request gitlab-org/gitlab-ce!30838
|
|
Often live traces are removed even though the archived trace
doesn't exist. This commit checkes the existence strictly.
|
|
Add cr remarks
Improve specs according to the review
Fix schema
Add cr remarks
Fix naming
Add cr remarks
|
|
To allow project filtering
Prepare summary for accepting multiple groups
Modify deploys group summary class
Add filtering by project name in issues summary
Fix rubocop offences
Add changelog entry
Change name to id in project filtering
Fix rebase problem
Add project extraction
|
|
It seems that we missed the backward compatibility support
for profiles in the existing folder.
This commit also fixes some specs to be idempotent
and work in a temporary directory which not always
seems to be the case.
This commit also brings the profile_spec.rb which seems
to be missing.
|
|
This makes these tests available for other implementations
|
|
Resolve remaining import export differences
See merge request gitlab-org/gitlab-ce!31012
|
|
Previously, in Omnibus, Workhorse expected to listen via the Redis
shared state cluster for the `workhorse:notifications` publish/subscribe
channel, but the Rails code was using the Sidekiq queue cluster for
this. To fix this inconsistency, we make the Rails code use the
persistent cluster, since we don't want Workhorse to be looking at
anything Sidekiq-related.
|
|
This backports remaining import/export spec changes from EE to CE.
|
|
This backports all changes made to an import/export fixture file from EE
to CE.
|
|
This line is already present further down in the YAML file. In EE the
line is already removed.
|
|
PATs are accepted using the OAuth2 compliant header
"Authorization: Bearer {token}" in order to allow for
OAuth requests while 2FA is enabled.
|
|
This adds a counter to count page creation, which is reflected in the
usage-data we collect.
The number created is stored in Redis, avoiding DB access.
|
|
Fix Gitaly auto-detection caching
Closes #64802
See merge request gitlab-org/gitlab-ce!30954
|
|
See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069
|
|
|
|
If `GitalyClient#can_use_disk?` returned `false`, it was never cached
properly and led to excessive number of Gitaly calls. Instead of using
`cached_value.present?`, we need to check `cached_value.nil?`.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64802
|