Age | Commit message (Collapse) | Author | |
---|---|---|---|
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-09 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-31 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-15 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-03 | 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-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-04 | Backport EE changes for productivity analytics | Pavel Shutsin | |
Improve diff lines count efficiency | |||
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-07-24 | Add Rugged calls to performance bar | Stan Hu | |
This will help diagnose the source of excessive I/O from Rugged calls. To implement this, we need to obtain the full list of arguments sent to each request method. | |||
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-17 | Added submodule links to Submodule type in GraphQL API | Igor | |
This is part of migration of Folder View to Vue | |||
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-09 | Disabling can_use_disk? temporarily | John Cai | |
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 |