| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit f222e74d455ec9fc10efb783ffe4684836cc1c3b.
|
|
|
|
|
| |
Replace 'chronic_duration' to 'gitlab_chronic_duration', to make
relevant method calls thread-safe.
|
| |
|
|
|
|
| |
Backporting https://github.com/rmosolgo/graphiql-rails/pull/71
|
| |
|
| |
|
| |
|
|
|
|
| |
This class encapsulates our use of the Danger gem.
|
|
|
| |
This reverts merge request !32196
|
| |
|
|
|
|
|
|
| |
- `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
|
|
|
|
| |
See https://gitlab.com/gitlab-org/prometheus-client-mmap/merge_requests/38
|
|
|
|
|
|
|
|
|
| |
- 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
|
|\
| |
| |
| |
| |
| |
| | |
Fix Peek on Puma
Closes #66528
See merge request gitlab-org/gitlab-ce!32213
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| | |
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|/ |
|
|
|
|
|
| |
The `GraphQL::Function` has been deprecated in
favor of resolvers.
|
|\
| |
| |
| |
| | |
Bump ruby-prof to 1.0.0
See merge request gitlab-org/gitlab-ce!29588
|
| |
| |
| |
| |
| | |
This is significant improvement over the previous releases:
https://github.com/ruby-prof/ruby-prof/blob/master/CHANGES
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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
|
|\
| |
| |
| |
| |
| |
| | |
'46548-open-source-alternative-to-recaptcha-for-gitlab-com-registration' into 'master'
Open source alternative to reCAPTCHA for GitLab.com registration
See merge request gitlab-org/gitlab-ce!31625
|
| | |
|
| |
| |
| |
| |
| | |
This introduces several changes, but these are all just ported from the
EE project.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Update gitlab-labkit to 0.4.2
See merge request gitlab-org/gitlab-ce!31685
|
| |/
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
| |
This pulls in fix for CVE-2019-5477, where usage of
Nokogiri::CSS::Tokenizer#load_file leads to potential command injection.
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
Update reliable fetcher
See merge request gitlab-org/gitlab-ce!31416
|
| |
| |
| |
| | |
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.
|
|\
| |
| |
| |
| | |
Have deterministic DNS for specs
See merge request gitlab-org/gitlab-ce!31086
|
| |
| |
| |
| |
| |
| |
| | |
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 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
|