DEPRECATION WARNING: The success? predicate is deprecated and will be
removed in Rails 6.0. Please use successful? ...

This allows the chaos endpoints to be invoked in Sidekiq so that this
environment can be tested for resilience.

This improves the `add_timestamps_with_timezone` helper by allowing the
column names to be configured. This has the advantage that unnecessary
columns can be avoided, saving space.

A helper for removing the columns is also provided, to be used in the
`down` method of migrations.

Use relative worker identifier for metrics (instead of Process.pid) and
identify when Unicorn/Puma/Sidekiq is used.
Previously, it was assumed that all metrics are gathered from Unicorn
due to hardcoded implementation which was incorrect.

This adds `rugged_duration_ms` and `rugged_calls` fields to
`api_json.log` and `production_json.log`. This will make it easier to
identify performance issues caused by excessive I/O.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64676

Extend the support for "X-Profile-Token: <token>" to have an additional
header that defines type of profile we are looking for, like:
  X-Profile-Mode: execution
  X-Profile-Mode: memory

The call to init had the side effect of starting another Gitaly process,
and didn't actually correctly delete the test repositories.

Previously `start_sha` was intercepted on the frontend to create the
correct branch in a separate API call. Now that the commits API supports
the `start_sha` parameter directly this workaround is not needed
anymore.

When passing start_branch on committing from the WebIDE, it's possible
that the branch has changed since editing started, which results in the
change being applied on top of the latest commit in the branch and
overwriting the new changes.

By passing the start_sha instead we can make sure that the change is
applied on top of the commit which the user started editing from.

This MR refactor RedisCounter and WebIdeCommitsCounter
to be reused by other components.

peek-redis resets its counters at the start of an ActionController
notification (`start_processing.action_controller`), which causes it to
miss some Redis queries that precede it, such as the database load
balancer and Rack Attack queries. This produces inconsistencies in the
performance bar between the number of calls and their durations with the
actual calls in the detailed view.

We fix this by getting rid of peek-redis in favor of consolidating all
logic into the `RedisDetailed` view, which tracks Redis queries using
`RequestStore`. This has the nice property of removing thread-specific
counters as well.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64707

(cherry picked from commit a82e4d57a6fbba840a8a944e372b80866a1e48cc)

Ensure correct behaviour when deploy tokens have the same username or
deploy token and user have the same username.

Pages access level currently depends on project visibilty
which is ignored by factory, this commit fixes that

Moved the block that fails tests on unmocked axios requests from
test_setup to its own mock, and added a jQuery mock that fails
tests if they use unmocked $.ajax().

This is part of migration of Folder View to Vue

- Set access level in before_validation hook
- Add post migration for updating existing project_features

By doing smaller mget calls to Redis, it can better schedule the
workload. Currently a single mget with a lot of keys can keep Redis busy
for long, while nothing in its queue gets processed.

This has been enabled on production without issue

https://gitlab.com/gitlab-org/gitlab-ce/issues/64259

EE MR: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14598

Fetch latest link in the description for zoom link, add more tests and remove frontend spec unnecessary tests

Whenever we use the rugged implementation, we are going straight to disk
so we want to bypass the disk access check.

This change adds the ability to read and
write admin notes for a user via the
USER API

Instead return error objects.

Change small things for better readability

- Set as uninstallable app
- Update docs
- Adjust specs

This reverts merge request !28545

It adds  a hash response which includes
the count, success state and the moved
issues itself so the caller has additional
information about the result of the
process.