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-20Add latest changes from gitlab-org/gitlab@12-10-stable-eeGitLab Bot
2020-04-14Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-04-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-26Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-17Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-09Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-02Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-05Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-04Add 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-24Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-16Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-03Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-16Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898GitLab Bot
2019-11-22Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-05Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-22Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-10Change Sidekiq monitor namespaceQingyu Zhao
Move Gitlab::SidekiqMonitor to namespace Gitlab::SidekiqDaemon::Monitor - Class name and file name change - File path change to lib/gitlab/sidekiq_daemon/monitor.rb - Update class usage/reference in other files, including documentation
2019-08-30Fix for histogram corruption in SidekiqAndrew Newdigate
This fixes a bug in which sidekiq histograms contain invalid labels. See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/7729 for more details.
2019-08-22Add frozen_string_literal to lib part 2Thong Kuah
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
2019-08-21Put cancelled job in DeadSetKamil Trzciński
This replicates Sidekiq behavior of pushing dead job into DeadSet.
2019-08-21Properly handle `sidekiq` skipKamil Trzciński
Transform `CancelledError` into `JobRetry::Skip`
2019-08-21Rework `Sidekiq::JobsThreads` into `Monitor`Kamil Trzciński
This makes: - very shallow `Middleware::Monitor` to only request tracking of sidekiq jobs, - `SidekiqStatus::Monitor` to be responsible to maintain persistent connection to receive messages, - `SidekiqStatus::Monitor` to always use structured logging and instance variables
2019-08-21Allow to interrupt running jobsKamil Trzciński
This adds a middleware to track all threads for running jobs. This makes sidekiq to watch for redis-delivered notifications. This makes be able to send notification to interrupt running sidekiq jobs. This does not take into account any native code, as `Thread.raise` generates exception once the control gets back to Ruby. The separate measure should be taken to interrupt gRPC, shellouts, or anything else that escapes Ruby.
2019-08-20Allow measurement for Sidekiq jobs taking > 2.5sAndrew Newdigate
Fix for https://gitlab.com/gitlab-org/gitlab-ce/issues/66319.
2019-07-30Fix sidekiq memory killer warning messageShinya Maeda
2019-07-29Adds direct monitoring for sidekiq metricsRyan Cobb
This adds diirect monitoring for sidekiq metrics. This is done via sidekiq middleware and a sampler to pull from sidekiqs api.
2019-07-25Logging sidekiq worker class name in SidekiqMemoryKillerShinya Maeda
Currently, SidekiqMemoryKiller does not feed worker class name in the json structured logging. This commit extends the json parameter.
2019-04-18Migrate correlation and tracing code to LabKitAndrew Newdigate
This change is a fairly straightforward refactor to extract the tracing and correlation-id code from the gitlab rails codebase into the new LabKit-Ruby project. The corresponding import into LabKit-Ruby was in https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1 The code itself remains very similar for now. Extracting it allows us to reuse it in other projects, such as Gitaly-Ruby. This will give us the advantages of correlation-ids and distributed tracing in that project too.
2019-03-09Fix the last-ditch memory killer pgroup SIGKILLNick Thomas
2019-03-04sidekiq: terminate child processes at shutdownNick Thomas
Sidekiq jobs frequently spawn long-lived child processes to do work. In some circumstances, these can be reparented to init when sidekiq is terminated, leading to duplication of work and strange concurrency problems. This commit changes sidekiq so that, if run as a process group leader, it will forward `INT` and `TERM` signals to the whole process group. If the memory killer is active, it will also use the process group when resorting to `kill -9` to shut down. These changes mean that a naive `kill <pid-of-sidekiq>` will now do the right thing, killing any child processes spawned by sidekiq, as long as the process supervisor placed it in its own process group. If sidekiq isn't a process group leader, this new code is skipped.
2019-03-01SIGSTP should be SIGTSTPNick Thomas