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

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-09-19Add latest changes from gitlab-org/gitlab@13-4-stable-eeGitLab Bot
2020-08-20Add latest changes from gitlab-org/gitlab@13-3-stable-eeGitLab Bot
2020-07-20Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot
2020-06-18Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot
2020-05-20Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot
2020-04-09Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-04-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-04-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-20Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-20Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-08Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-07Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-06Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-16Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-24Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-07Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-03Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-21Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-21Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-15Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-03Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-17Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-04Backport EE changes for productivity analyticsPavel Shutsin
Improve diff lines count efficiency
2019-08-28Make performance bar enabled checks consistentSean 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-24Add Rugged calls to performance barStan 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-18Merge 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-17Added submodule links to Submodule type in GraphQL APIIgor
This is part of migration of Folder View to Vue
2019-07-16Wrap rugged calls with access disk blockJohn Cai
Whenever we use the rugged implementation, we are going straight to disk so we want to bypass the disk access check.
2019-07-09Disabling can_use_disk? temporarilyJohn Cai
2019-07-05Use Rugged if we detect storage is NFS and we can access the diskJohn Cai
Add a module we use as a singleton to determine whether or not rails is able to access the disk