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
2022-12-07Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-10-17Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-08-17Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-04-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-03-08Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-01-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2022-01-26Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-07-23Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2021-06-08Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-03-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-02-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-09Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-17Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-04Avoid calling freeze on already frozen strings in lib/gitlabdineshpanda
2019-08-22Fix frozen string errorsThong Kuah
2019-08-01Add additional paths to clean from backtraceStan Hu
`Gitlab::Profiler` can also be used to profile Sidekiq jobs. Add some call traces that can be omitted from the backtrace.
2019-07-25Enable Rubocop Performance/ReverseEachStan Hu
`Array.reverse_each` is faster than `Array.reverse.each` because: * reverse.each creates a new array then loops each element * reverse_each loops in reverse order (no intermediate array created)
2019-04-27Fix Profiler to work with Ruby 5.1Stan Hu
Ruby 5.1 now requires keyword arguments to pass along parameters and headers for ActionDispatch::Integration::RequestHelpers. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61051
2019-04-17Add backtrace to Gitaly performance barStan Hu
This adds the backtrace to a table to show exactly where the Gitaly call was made to make it easier to understand where the call originated. This change also collapses the details in the same row to improve the usability when there is a backtrace.
2018-11-26Allow profiler to authenticate by stubbing users directlySean McGivern
Previously, we used a personal access token. This had a couple of problems: 1. If the user didn't have a PAT, we couldn't impersonate them. 2. It depended on reading the raw PAT from the database. Instead, we can monkey-patch the authentication methods on ApplicationController (overriding the Devise ones), and remove them once we're done. This does mean that profiles will not profile auth correctly, so for that, use a PAT directly.
2018-10-22Enable frozen string for lib/gitlab/*.rbgfyoung
2018-09-11Disable existing offenses for the CodeReuse copsYorick Peterse
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
2018-07-19Add a Gitlab::Profiler.print_by_total_time convenience methodSean McGivern
This method uses Gitlab::Profiler::TotalTimeFlatPrinter internally, which is the same as RubyProf::FlatPrinter, but the min_percent option (and new max_percent option) applies to the _total_ time, not the _self_ time. This helps us figure out if we're calling a library inefficiently, for instance.
2018-06-15Expose a clean_backtrace method from Gitlab::ProfilerSean McGivern
This method makes it easier for other parts of the app to get clean backtraces, as well as console users.
2018-03-21Add query counts by model to profiler outputSean McGivern
2018-02-16Improve error handling for Gitlab::Profiler and improve doc about providing ↵Dylan Griffith
a user
2018-01-19Add Gitlab::Profiler for profiling from a console or runnerSean McGivern
Gitlab::Profiler.profile takes a URL to profile, and returns the ruby-prof profile result. This is currently only for interactive use (in a console) or from the script runner. Note that when using this interactively, changes to the application within that console session will be used, so this can be used to test proposed performance changes.