Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-01-23Clarify source of gitaly-ruby errors in logsWill Chandler
For admins new to GitLab it can be difficult to tell when an error was triggered by gitaly vs gitaly-ruby. This changes updates errors to explicitly mentions gitaly-ruby.
2019-11-27Generalize internal gitaly socket dirJohn Cai
Both gitaly-ruby and gitaly hooks will need the gitaly internal socket directory, so we can pull it out into the config package. Also this change starts an internal gitaly socket that listens for connections.
2019-11-21Replace depracated grpc.WithDialerMateusz Nowotynski
Signed-off-by: Mateusz Nowotyński <maxmati4@gmail.com>
2019-11-19Allow socket dir for Gitaly-Ruby to be configuredZeger-Jan van de Weg
In case the `/tmp` directory can't be used for security reasons, this can be configured. The default behaviour as in production right now will remain. So if nothing is set, `/tmp` will be reused.
2019-10-31Adding sentry config to praefectJohn Cai
Refactored configs so that both praefect and gitaly can share logging and sentry config structs
2019-10-09Upgrade GRPC to 1.24.0John Cai
2019-10-02Rename git_config_search_path -> rugged_git_config_search_pathStan Hu
2019-10-02Support configurable Git config search path for RuggedStan Hu
This commit adds an optional `git_config_search_path` parameter for gitaly-ruby. By default, Rugged searches inside `/etc/gitconfig` instead of `/opt/gitlab/embedded/etc/gitconfig` for system-wide options unless the `Rugged::Settings['search_path_system']` is set. This means that important options such as `core.fsyncObjectFiles` are not propagated to gitaly-ruby, which can result in data loss after servers are rebooted. The command-line `git` doesn't have this issue because it uses the `prefix` compile-time option, but this isn't available in Rugged. With this new parameter, package managers (e.g. Omnibus) can specify where the system `gitconfig` file should be. Closes https://gitlab.com/gitlab-org/gitaly/issues/2051
2019-10-01Migrate hooks to use go binaryJohn Cai
2019-09-03main: start ruby server after opening network listenersJacob Vosmaer
2019-07-31Use embedded Go stubs for gitaly-protoJacob Vosmaer
2019-06-27Pass down log config through env varsJohn Cai
2019-06-04Make catfile cache size configurableJacob Vosmaer
2019-05-02feat: add sentry environmentRoger Meier
2019-02-28Try to resolve flaky TestRemoval balancer testJacob Vosmaer
2019-02-14Bring back a custom dialler for Gitaly RubyAndrew Newdigate
This is a second fix for the GRPC bug related to using unix sockets alongside unix sockets. Previously we fixed incoming clients. This change fixes the connection between Gitaly and Gitaly-Ruby, which always relies on unix sockets, and which currently fail when http proxies are setup. A (too) long history of this change: * Unix sockets have never been officially supported by gRPC * Originally unix sockets didn't work at all, and you had to use a dialer * Attempted to upgrade from gRPC 1.9 to 1.16 and found that our dialer broke connectivity: https://gitlab.com/gitlab-org/gitaly/merge_requests/972 * Isolated the problem to this commit: https://github.com/grpc/grpc-go/commit/90dca43332f6cc944c37e16f32a82c41639e7705 * Fixed the problem by switching to the default dialer for unix: URLs * (note that it's still not officially supported, but without integration tests with proxy configurations, it seems to work) * In #1447, discovered that the default dialer breaks if one has http proxies configured (there was a also a second failure in https://gitlab.com/gitlab-org/gitaly/merge_requests/1032 which involved clients talking to Gitaly) * This change partially reverts https://gitlab.com/gitlab-org/gitaly/merge_requests/972 while keeping the fix for the original connectivity issue
2019-01-14Replace net/context with context packageZeger-Jan van de Weg
Leveraging `go fix` these changes were made, I only applied some regexp to get the import grouping correct. The old package can't be removed from vendor directory yet, as other dependencies depend on it.
2019-01-11Add distributed tracing support with LabKitAndrew Newdigate
2018-12-04Update to latest goimports formattingJacob Vosmaer
2018-11-22Propagate correlation-ids in from upstream services and out to Gitaly-RubyAndrew Newdigate
2018-11-16Upgrade grpc-go from v1.9.1 to v1.16.0 in preparation for correlation idsAndrew Newdigate
2018-10-24Make git hooks self healingZeger-Jan van de Weg
If the git hooks aren't symlinked properly, GitLab authentication and authorization is skipped completely. So on most Git operations, if these hooks are missing this commit will try to repair them when triggering an upload-pack, or receive-pack git action. This change also allows the Gitaly team to change the hooks in following releases to any new ones. And allowing for absorbing the gitlab-shell hooks into this project. Previously attempted in: https://gitlab.com/gitlab-org/gitaly/commit/87198d32837, which ran into race conditions. This approach does not Part of https://gitlab.com/gitlab-org/gitaly/issues/1226
2018-10-16Standardize git command invocationAlejandro Rodríguez
This propagates our git.GitEnv variables properly, plus DRYes the code
2018-10-15Fix formattingAlejandro Rodríguez
2018-10-11Force english output on git commandsAlejandro Rodríguez
For some reason my git got localized in spanish, and we had some tests failing because they relied on error messages being on english, as well as some code failing if the text wasn't ASCII-8BIT compatible. These changes fix those issues.
2018-10-04Rename gitaly proto import to gitalypbZeger-Jan van de Weg
This change the result of a grep + sed, to move away from pb, and use gitalypb instead. The gitalypb points to a vendorred directory that has the same name. This would fix the use of goimports. See also: https://gitlab.com/gitlab-org/gitaly-proto/merge_requests/213
2018-06-08Try to fix flaky rubyserver.TestRemovals testJacob Vosmaer (GitLab)
2018-06-05Simplify and rename AssertGrpcErrorJacob Vosmaer (GitLab)
2018-05-16Use round robin load balancing instead of 'pick first' for gitaly-rubyJacob Vosmaer (GitLab)
2018-05-09Remove ruby concurrency limiterJacob Vosmaer (GitLab)
2018-04-30Limit concurrent gitaly-ruby requests from the client sideJacob Vosmaer
2018-04-23Extend startup timeout for ping testJacob Vosmaer
2018-04-23Stop worker monitors in testJacob Vosmaer (GitLab)
2018-04-19Add health checks for gitaly-rubyJacob Vosmaer (GitLab)
2018-04-06Send gitaly-ruby exceptions to their own DSNJacob Vosmaer (GitLab)
2018-03-29Add handling for large commit and tag messagesAhmad Sherif
2018-03-05Use only 1 gitaly-ruby process in testJacob Vosmaer (GitLab)
2018-02-22Send gitaly-ruby exceptions to SentryAhmad Sherif
Closes #988
2018-01-29Wait between ruby worker removal from pool and graceful shutdownJacob Vosmaer (GitLab)
2018-01-18Implement GetLFSPointers RPCAhmad Sherif
Closes #922
2018-01-12Check repo existence before passing to gitaly-rubyJacob Vosmaer (GitLab)
2017-12-20Merge branch ↵Alejandro Rodríguez
'840-make-gitlab-git-gitlabprojects-not-work-with-storage-paths' into 'master' Stop using deprecated gitlab-projects command Closes #840 See merge request gitlab-org/gitaly!495
2017-12-15Incorporate RemoteServiceAlejandro Rodríguez
2017-12-15Pass storage_path to gitaly-rubyAlejandro Rodríguez
2017-12-08Incorporate ConflictsServiceAlejandro Rodríguez
2017-12-07Restart gitaly-ruby when it uses too much memoryJacob Vosmaer (GitLab)
2017-12-06Increase default gitaly-ruby connection timeout to 40sAlejandro Rodríguez
2017-11-21Run gitaly-ruby in the same directory as gitalyJacob Vosmaer (GitLab)
2017-11-14Track gitaly-sidecar connections in prometheusKim "BKC" Carlbäcker
2017-11-13Implement RepositoryService::FetchSourceBranchJacob Vosmaer (GitLab)