Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-07-20 | Add latest changes from gitlab-org/gitlab@15-2-stable-eev15.2.0-rc42 | GitLab Bot | |
2022-03-18 | Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42 | GitLab Bot | |
2022-02-08 | Add latest changes from gitlab-org/gitlab@14-7-stable-ee | GitLab Bot | |
2021-11-18 | Add latest changes from gitlab-org/gitlab@14-5-stable-eev14.5.0-rc42 | GitLab Bot | |
2021-07-20 | Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42 | GitLab Bot | |
2021-04-21 | Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43 | GitLab Bot | |
2021-03-16 | Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40 | GitLab Bot | |
2021-02-18 | Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42 | GitLab Bot | |
2021-01-20 | Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42 | Robert Speicher | |
2020-09-19 | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | |
2020-08-20 | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | |
2020-07-20 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-06-18 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-05-20 | Add latest changes from gitlab-org/gitlab@13-0-stable-ee | GitLab Bot | |
2020-04-20 | Add latest changes from gitlab-org/gitlab@12-10-stable-ee | GitLab Bot | |
2020-03-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-16 | Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898 | GitLab Bot | |
2019-12-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-26 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-02 | Merge branch 'fix-peek-on-puma' into 'master' | Rémy Coutable | |
Fix Peek on Puma Closes #66528 See merge request gitlab-org/gitlab-ce!32213 | |||
2019-08-28 | Rename Labkit::Tracing::GRPCInterceptor to GRPC::ClientInterceptor | Andrew Newdigate | |
The original name has been deprecated | |||
2019-08-28 | Make performance bar enabled checks consistent | Sean McGivern | |
Previously, we called the `peek_enabled?` method like so: prepend_before_action :set_peek_request_id, if: :peek_enabled? Now we don't have a `set_peek_request_id` method, so we don't need that line. However, the `peek_enabled?` part had a side-effect: it would also populate the request store cache for whether the performance bar was enabled for the current request or not. This commit makes that side-effect explicit, and replaces all uses of `peek_enabled?` with the more explicit `Gitlab::PerformanceBar.enabled_for_request?`. There is one spec that still sets `SafeRequestStore[:peek_enabled]` directly, because it is contrasting behaviour with and without a request store enabled. The upshot is: 1. We still set the value in one place. We make it more explicit that that's what we're doing. 2. Reading that value uses a consistent method so it's easier to find in future. | |||
2019-08-23 | Handle when server info doesn't have the storage in question | John Cai | |
2019-08-09 | Add Gitaly and Rugged call timing in Sidekiq logs | Stan Hu | |
This will help identify Sidekiq jobs that invoke excessive number of filesystem access. The timing data is stored in `RequestStore`, but this is only active within the middleware and is not directly accessible to the Sidekiq logger. However, it is possible for the middleware to modify the job hash to pass this data along to the logger. | |||
2019-07-30 | Fix exception handling in Gitaly autodetection | Stan Hu | |
In SELinux, the file cannot be written, and `Errno::EACCES`, not `Errno::ACCESS` is thrown. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65328 | |||
2019-07-19 | Fix Gitaly auto-detection caching | Stan Hu | |
If `GitalyClient#can_use_disk?` returned `false`, it was never cached properly and led to excessive number of Gitaly calls. Instead of using `cached_value.present?`, we need to check `cached_value.nil?`. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64802 | |||
2019-07-18 | Merge branch 'jc-wrap-rugged-calls-with-disk-access' into 'master' | Stan Hu | |
Wrap rugged calls with access disk block See merge request gitlab-org/gitlab-ce!30592 | |||
2019-07-16 | Wrap rugged calls with access disk block | John Cai | |
Whenever we use the rugged implementation, we are going straight to disk so we want to bypass the disk access check. | |||
2019-07-15 | Remove catfile cache feature flag | John Cai | |
2019-07-10 | Add a rubocop for Rails.logger | Mayra Cabrera | |
Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102 | |||
2019-07-09 | Disabling can_use_disk? temporarily | John Cai | |
2019-07-08 | Merge branch 'jc-detect-nfs-for-rugged' into 'master' | Dmitriy Zaporozhets | |
Use Rugged if we detect storage is NFS and we can access the disk See merge request gitlab-org/gitlab-ce!29725 | |||
2019-07-05 | Use Rugged if we detect storage is NFS and we can access the disk | John Cai | |
Add a module we use as a singleton to determine whether or not rails is able to access the disk | |||
2019-07-05 | Remove high cardinality Prometheus metric | Zeger-Jan van de Weg | |
The metric was used to correlate Gitaly requests to the Rails controller and action combination. However, Kibana provides better observability in this specific metric, and can handle hig cardinality much better. There's no dashboard in Grafana that currently depends on this metric being exposed. | |||
2019-06-18 | Turn on Cat-File cache by default | Zeger-Jan van de Weg | |
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 | |||
2019-06-18 | Move Gitaly feature flag logic to Feature::Gitaly | Zeger-Jan van de Weg | |
The GitalyClient held a lot of logic which was all very tightly coupled. In this instance the feature logic was extracted to make it do just a little less and create a bit more focus in the GitalyClient's responsibilies. | |||
2019-06-03 | Remove delta island feature flag | Zeger-Jan van de Weg | |
Delta islands were implemented last released in: https://gitlab.com/gitlab-org/gitaly/merge_requests/1110. It's been enabled on production and works as expected. | |||
2019-05-07 | Register "gitaly_delta_islands" feature flag | Jacob Vosmaer | |
2019-05-05 | Run rubocop -a on CE files | Stan Hu | |