gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2021-08-19	Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.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

2020-01-29	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-09-04	Avoid calling freeze on already frozen strings in lib/gitlab	dineshpanda

2018-11-20	Enable even more frozen string for lib/gitlab	gfyoung
	Enables frozen string for the following: * lib/gitlab/patch/*/.rb * lib/gitlab/popen/*/.rb * lib/gitlab/profiler/*/.rb * lib/gitlab/project_authorizations/*/.rb * lib/gitlab/prometheus/*/.rb * lib/gitlab/query_limiting/*/.rb * lib/gitlab/quick_actions/*/.rb * lib/gitlab/redis/*/.rb * lib/gitlab/request_profiler/*/.rb * lib/gitlab/search/*/.rb * lib/gitlab/sherlock/*/.rb * lib/gitlab/sidekiq_middleware/*/.rb * lib/gitlab/slash_commands/*/.rb * lib/gitlab/sql/*/.rb * lib/gitlab/template/*/.rb * lib/gitlab/testing/*/.rb * lib/gitlab/utils/*/.rb * lib/gitlab/webpack/*/.rb Partially addresses gitlab-org/gitlab-ce#47424.
2018-05-31	Make ActiveRecordSubscriber rails 5 compatible	Jarka Kadlecová

2018-02-21	Do not count rails sql cache as queries in query limiting	Dylan Griffith

2018-02-13	Remove Sentry reporting for query limiting	Yorick Peterse
	Using Sentry, while useful, poses two problems you have to choose from: 1. All errors are reported separately, making it easy to create issues but also making it next to impossible to see other errors (due to the sheer volume of threshold errors). 2. Errors can be grouped or merged together, reducing the noise. This however also means it's (as far as I can tell) much harder to automatically create GitLab issues from Sentry for the offending controllers. Since both solutions are terrible I decided to go with a third option: not using Sentry for this at all. Instead we'll investigate using Prometheus alerts and Grafana dashboards for this, which has the added benefit of being able to more accurately measure the behaviour over time. Note that throwing errors in test environments is still enabled, and whitelisting is still necessary to prevent that from happening (and that in turn still requires that developers create issues).
2018-02-01	Track and act upon the number of executed queries	Yorick Peterse
	This ensures that we have more visibility in the number of SQL queries that are executed in web requests. The current threshold is hardcoded to 100 as we will rarely (maybe once or twice) change it. In production and development we use Sentry if enabled, in the test environment we raise an error. This feature is also only enabled in production/staging when running on GitLab.com as it's not very useful to other users.