This reverts commit f222e74d455ec9fc10efb783ffe4684836cc1c3b.

Replace 'chronic_duration' to 'gitlab_chronic_duration', to make
relevant method calls thread-safe.

Alessio Caiazza authored 5 years ago and Mayra Cabrera committed 5 years ago

Backporting https://github.com/rmosolgo/graphiql-rails/pull/71

This class encapsulates our use of the Danger gem.

This reverts merge request !32196

Brett Walker authored 5 years ago and Mayra Cabrera committed 5 years ago

- `edge_nodes` needs to get called on the object
- added `include GlobalID::Identification` in a couple places
- renamed `object` to `item` in spec due to conflict

Andrew Newdigate authored 5 years ago and Mayra Cabrera committed 5 years ago

See https://gitlab.com/gitlab-org/prometheus-client-mmap/merge_requests/38

Brett Walker authored 5 years ago and Mayra Cabrera committed 5 years ago

- Due to https://github.com/exAspArk/batch-loader/pull/32,
we  changed BatchLoader.for into BatchLoader::GraphQL.for
- since our results are wrapped in a BatchLoader::GraphQL,
calling `sync` during authorization is required to get real object
- `graphql` now has it's own authorization system.  Our
`authorized?` method conflicted and required renaming

This is used by the Jira integration in EE

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Peek's `Peek.request_id` method doesn't work well with a multi-threaded
server and concurrent requests, because requests can 'steal' another
request's ID, or unset it before it was due.

The upstream change resolves this; the commit here is just to ensure
that GitLab works with that upstream change, mostly by not using
`Peek.request_id` any more (as the method doesn't exist).

Brett Walker authored 5 years ago and Mayra Cabrera committed 5 years ago

The `GraphQL::Function` has been deprecated in
favor of resolvers.

This is significant improvement over the previous releases:
https://github.com/ruby-prof/ruby-prof/blob/master/CHANGES

Andrew Newdigate authored 5 years ago and Nick Thomas committed 5 years ago

This change adds Distributed Tracing support for two new types of events

1. Redis Calls
1. ActiveSupport (Rails) Caching Operations

The intention is to help application developers and infrastructure
SREs to understand the pressure that caching operations can have on
the application when running at scale.

The Redis and Caching spans can be viewed in the Jaeger UI by clicking
the "Trace" link in the performance bar when running on GDK.

Peter Leitzen authored 5 years ago and Thong Kuah committed 5 years ago

The virtus project has been discontinued:

https://github.com/solnic/virtus/commit/a6f896984

We don't need this since this is already the default
behavior of Rails since 5.1

Jeremy Jackson authored 5 years ago and Mayra Cabrera committed 5 years ago

This introduces several changes, but these are all just ported from the
EE project.

This pulls in fix for CVE-2019-5477, where usage of
Nokogiri::CSS::Tokenizer#load_file leads to potential command injection.

This relaxes the gRPC version so that it can be updated. Also adds
cache support for distributed tracing.

Full release notes:
https://gitlab.com/gitlab-org/labkit-ruby/-/tags

These were disabled in production mode, but that also broke the rest of
the performance bar. As they were only enabled in development mode, we
can just remove them for now.

We added retry_count increment when job is recovered

This is the first step in providing a fault-tolerant and distributed
Redis caching store. We disable compression to avoid introducing a
change that could have an adverse effect in production.

Note that we won't be able to take advantage of the fault-tolerance and
distributed features yet until we solve
https://gitlab.com/gitlab-org/gitlab-ce/issues/64829.

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

1. The output isn't great. It can be hard to find hotspots and, even
   when you do find them, to find why those are hotspots.
2. It uses some jQuery-specific frontend code which we can remove now
   that we don't have this any more.
3. It's only possible to profile the initial request, not any subsequent
   AJAX requests.

This adds support for a number of new languages (e.g. Ada)
and fixes a number of lexers:
https://github.com/rouge-ruby/rouge/compare/v3.5.1..v3.7.0

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

This means we have one less Net::HTTP monkeypatch.

sham_rack cannot handle IPv6 addresses which means it breaks Net::HTTP
connections because it monkey-patches Net::HTTP

This uses an ActiveRecord subscriber to get queries and calculate the
total query time from that. This means that the total will always be
consistent with the queries in the table. It does however mean that we
could potentially miss some queries that don't go through ActiveRecord.

Making this change also allows us to unify the response JSON a little
bit, making the frontend slightly simpler as a result.

None of this code can be reached any more, so it can all be removed