summaryrefslogtreecommitdiff
path: root/lib/gitlab/gitaly_client.rb
Commit message (Collapse)AuthorAgeFilesLines
* Log certificate loading errors into sentryAhmad Hassan2018-12-201-4/+8
|
* Followups on reviewAhmad Hassan2018-12-191-17/+13
|
* Deduplicate certificatesAhmad Hassan2018-12-171-3/+13
|
* Merge remote-tracking branch 'origin/master' into support-gitaly-tlsAhmad Hassan2018-12-111-121/+16
|\
| * Rename the correlation field from `correlation_id` to `x-gitlab-correlation-id`Andrew Newdigate2018-12-071-1/+1
| |
| * Revert "Prefer to use correlation-id in logs"Kamil Trzciński2018-12-061-1/+1
| | | | | | | | This reverts commit 3560b11922fd180eea5cafd0e763e0e601c5c4ee.
| * Prefer to use correlation-id in logsKamil Trzciński2018-12-061-1/+1
| | | | | | | | This changes `correlation_id` to be `correlation-id` when passed via jobs
| * Log and pass correlation-id between Unicorn, Sidekiq and GitalyKamil Trzciński2018-12-061-0/+1
| | | | | | | | | | | | | | | | The Correlation ID is taken or generated from received X-Request-ID. Then it is being passed to all executed services (sidekiq workers or gitaly calls). The Correlation ID is logged in all structured logs as `correlation_id`.
| * Fix bug where ID is not setrevert-fd6e3781Zeger-Jan van de Weg2018-11-201-5/+4
| | | | | | | | | | On HEAD~ we remove the ID from the class, which created a bug. Given we don't need the ID anymore, it has been removed and simplified.
| * Revert "Merge branch 'revert-e2aa2177' into 'master'"Zeger-Jan van de Weg2018-11-201-115/+10
| | | | | | This reverts merge request !23229
| * Revert "Merge branch 'zj-improve-gitaly-pb' into 'master'"revert-e2aa2177Sean McGivern2018-11-201-10/+115
| | | | | | This reverts merge request !23140
| * Merge branch 'zj-improve-gitaly-pb' into 'master'Sean McGivern2018-11-201-115/+10
| |\ | | | | | | | | | | | | Show what RPC is called in the performance bar See merge request gitlab-org/gitlab-ce!23140
| | * Show what RPC is called in the performance barZeger-Jan van de Weg2018-11-161-115/+10
| | | | | | | | | | | | | | | Now only the data was shown of the service, which is not valueable at times given some of those expose a lot of RPCs.
| * | Fix typos in libGeorge Tsiolis2018-11-151-1/+1
| |/
* | Rename load_certs and include default cert fileAhmad Hassan2018-12-111-3/+8
| |
* | Manually load the certificatesAhmad Hassan2018-11-271-1/+7
| |
* | Add more specsAhmad Hassan2018-10-311-5/+1
| |
* | Support tls communication in gitalyAhmad Hassan2018-10-301-4/+17
|/
* Enable frozen string for lib/gitlab/*.rbgfyoung2018-10-221-1/+3
|
* Revert "Merge branch 'feature/git-v2-flag' into 'master'"James Lopez2018-10-051-1/+1
| | | This reverts merge request !21520
* Merge branch 'mk/improve-usage-of-request-store' into 'master'Yorick Peterse2018-09-251-24/+24
|\ | | | | | | | | | | | | Resolve "Provide NullStore for RequestStore" Closes #51718 See merge request gitlab-org/gitlab-ce!21848
| * Use `Gitlab::SafeRequestStore` in more placesMichael Kozono2018-09-241-24/+24
| | | | | | | | | | | | Even if it doesn’t save lines of code, since people will tend to use code they’ve seen. And `SafeRequestStore` is safer since you don’t have to remember to check `RequestStore.active?`.
* | Use the new gitaly auth scheme (v2)Alejandro Rodríguez2018-09-201-8/+22
|/
* Add git_v2 flag to GitalyClientJames Lopez2018-09-061-1/+1
|
* Remove timeouts for long running requestsZeger-Jan van de Weg2018-07-241-1/+5
|
* Resolve Naming/UncommunicativeMethodLin Jen-Shin2018-07-091-2/+2
|
* Clean up Gitaly N+1 stack tracesSean McGivern2018-07-041-1/+1
| | | | | We don't need to know the details of every library involved in these calls; they will always originate in the GitLab app itself.
* Deny repository disk access in development and testJacob Vosmaer (GitLab)2018-06-141-6/+8
|
* Rescue from failed feature lookupsJacob Vosmaer2018-06-061-0/+4
|
* Simplify server feature flagsJacob Vosmaer2018-06-061-12/+6
|
* Set Gitaly Server feature flags from RailsZeger-Jan van de Weg2018-06-061-0/+16
| | | | | | | | | | | | | Gitaly itself hold very little state, other than the data on disk. This limits the interfaces to set feature flags. Gitaly now has the ability to interpret the request metadata to check for feature flags. https://gitlab.com/gitlab-org/gitaly/merge_requests/704 This allows clients control on the Gitaly server, and given that Rails has an internal chatops interface to set these values this was chosen as solution. Known limitation right now, is that this package doesn't support the opt out that other Gitaly features do.
* Add "deny disk access" Gitaly feature (tripswitch)Jacob Vosmaer (GitLab)2018-06-011-1/+6
|
* Test if remote repository exists before cloningZeger-Jan van de Weg2018-03-271-0/+4
| | | | | | | | | | | | | | | | When a repository does not exist on a remote, Gitaly won't be able to clone it. This is correct behaviour, but from the clients perspective a change in behaviour. This change implements the client side changes that allows Gitaly to execute a `git ls-remote <remote-url> HEAD`. This way the client has no need to shell out to Git. In the situation where multiple Gitalies are available, one is chosen at random. This commit closes https://gitlab.com/gitlab-org/gitlab-ce/issues/43929, while its also a part of https://gitlab.com/gitlab-org/gitaly/issues/1084
* Capture Gitaly calls that don't go through `migrate`Sean McGivern2018-03-131-10/+19
|
* Add Gitaly call details to the performance barSean McGivern2018-03-131-0/+18
| | | | | The same as the SQL queries, show the details of Gitaly calls in the performance bar, as a modal that can be opened in the same way.
* Restart Unicorn and Sidekiq when GRPC throws 14:Endpoint read failedJacob Vosmaer (GitLab)2018-02-261-0/+23
|
* Rename Concern -> Methods41771-reduce-cardinality-of-metricsPawel Chojnacki2018-01-291-1/+1
|
* Migrate and reduce the buckets of Gitaly metricsPawel Chojnacki2018-01-291-24/+9
| | | | | /cc @bjk-gitlab /cc @zj
* Add a gRPC health check to ensure Gitaly is upsh-add-gitaly-health-checkStan Hu2018-01-241-3/+18
| | | | | | This will enable Geo to skip shards that not operational. Relates to gitlab-org/gitlab-ee#4329
* Move encoding methods to the more general EncodingHelpergitaly-encoding-helpersAlejandro Rodríguez2017-12-281-16/+0
|
* Remove Rugged::Repository#empty?Zeger-Jan van de Weg2017-12-071-1/+1
|
* Prevent dups when using StringIO for binary readsgitaly-prevent-dupJacob Vosmaer2017-12-061-0/+6
|
* Add timeouts for Gitaly callsAndrew Newdigate2017-11-291-4/+39
|
* Add controller#action metrics on GitalyZeger-Jan van de Weg2017-11-281-7/+42
| | | | | | | At this time we had good metrics on what number or requests each GRPC received, but were in the dark what controller#action combination was responsable. Or if Sidekiq was responsable. Now added are call counts per service and rpc matched with controller#action combinations.
* Add FetchSourceBranch Gitaly callJacob Vosmaer (GitLab)2017-11-221-3/+9
|
* Measure Gitaly migration sites against originalZeger-Jan van de Weg2017-11-011-1/+5
| | | | | | | We were missing data for Gitaly migration call sites against the original implementation. This commit adds a histogram with a flag telling us if gitaly received the call or the original implementation did.
* Add Gitaly data to the Peek performance barZeger-Jan van de Weg2017-10-231-0/+9
|
* Fix confusing double usage of 'metadata'Jacob Vosmaer (GitLab)2017-10-161-4/+16
|
* Gitaly feature flag metadataAndrew Newdigate2017-10-061-2/+19
|
* Fix for Gitaly nil encoding issueAndrew Newdigate2017-10-031-0/+2
|