An error occurred fetching the project authors.
- 25 Mar, 2021 1 commit
-
-
Lee Tickett authored
-
- 17 Feb, 2021 1 commit
-
-
Heinrich Lee Yu authored
When allowing git disk access, we call Gitlab::GitalyClient::StorageSettings.allow_disk_access which tracks this using a class instance variable. When classes are unloaded by Spring, we still keep a stale instance of Gitlab::GitalyClient::StorageSettings in Gitlab.config. And when self.class.disk_access_denied? is called on that instance, it was checking the class instance variable of the stale class. We fix this by using Gitlab::GitalyClient::StorageSettings.disk_access_denied? so that both of them use the same class instance variable.
-
- 16 Feb, 2021 1 commit
-
-
Zeger-Jan van de Weg authored
Introduced in 189342fc, its not clear why. This feature flag hasn't been used d505f2a8, which is a year before it got introduced.
-
- 07 Oct, 2019 1 commit
-
-
nnelson authored
The `Gitlab::GitalyClient::StorageSettings#gitaly_address` currently fails, because the GitLab configuration in production defines the gitaly address entry for each node using a string key, and the method actually tries to fetch the value based on a symbolic key. Interestingly enough, the `config/gitlab.yml.example` uses a symbolic key. Use `with_indifferent_access` instead of fallback. Add spec tests and fix fall-back settings fetch.
-
- 18 Jun, 2019 1 commit
-
-
Zeger-Jan van de Weg authored
The feature flag has been introduced an was turned off by default, now the it will default to be turned on. That change would still allow users to turn this feature off by leveraging the Rails console by running: `Feature.disable("gitaly_catfile-cache")` Another option is to manage the number of items the LRU cache will contain, by updating the `config.toml` for Gitaly. This would be the `catfile_cache_size`: https://gitlab.com/gitlab-org/gitaly/blob/0dcb5c579e63754f557aef91a4fa7a00e5b8b127/config.toml.example#L27 Closes: https://gitlab.com/gitlab-org/gitaly/issues/1712
-
- 01 Mar, 2019 1 commit
-
-
Stan Hu authored
This brings back some of the changes in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20339. For users using Gitaly on top of NFS, accessing the Git data directly via Rugged is more performant than Gitaly. This merge request introduces the feature flag `rugged_find_commit` to activate Rugged paths. There are also Rake tasks `gitlab:features:enable_rugged` and `gitlab:features:disable_rugged` to enable/disable these feature flags altogether. Part of four Rugged changes identified in https://gitlab.com/gitlab-org/gitlab-ce/issues/57317.
-
- 13 Nov, 2018 1 commit
-
-
gfyoung authored
Enables frozen string for the following: * lib/gitlab/fogbugz_import/**/*.rb * lib/gitlab/gfm/**/*.rb * lib/gitlab/git/**/*.rb * lib/gitlab/gitaly_client/**/*.rb * lib/gitlab/gitlab_import/**/*.rb * lib/gitlab/google_code_import/**/*.rb * lib/gitlab/gpg/**/*.rb * lib/gitlab/grape_logging/**/*.rb * lib/gitlab/graphql/**/*.rb * lib/gitlab/graphs/**/*.rb * lib/gitlab/hashed_storage/**/*.rb * lib/gitlab/health_checks/**/*.rb Partially address gitlab-org/gitlab-ce#47424.
-
- 21 Sep, 2018 2 commits
-
-
Marcel Amirault authored
-
Marcel Amirault authored
-
- 09 Jul, 2018 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 01 Jun, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 11 May, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
Given the settings initializer creates Gitaly Storage Settings objects already, the calls to path can be moved to that initializer.
-
- 23 Mar, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 21 Mar, 2018 1 commit
-
-
Jacob Vosmaer authored
-