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