| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Uses Rails transactional tests instead of DatabaseCleaner
transaction strategy because that doesn't work with JS tests
|
| |\
| |
| |
| |
| | |
Remove setImmediate polyfill from production assets
See merge request gitlab-org/gitlab-ce!30591
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Add `db_spin` and refactor ChaosController
Closes #64425
See merge request gitlab-org/gitlab-ce!30559
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add endpoint to move issues in boards
See merge request gitlab-org/gitlab-ce!30216
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add specs for new endpoint to move multiple issues.
Add changelog entry
Just check the first issue for the ability to move / update
Add specs for exceeding limits and malformed requests
Changed name of shared examples
Change title of changelog entry
Use %i instead of %w
Check permission to update issue on project instead of board
Use admin_issue permission to check for issue move ability
Changed variable name to avoid shadow issue_params method
Rename route to bulk_move
Change route definition
Check permissions for each issue
Combine methods for parameters permit check
Remove extra context
Change description of context
Check param for type Array
Add unit tests to MoveService
Use before_action for permission check
Use set instead of let!
Use let's instead of set
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Enable puma by default in GDK
Closes gitlab-development-kit#490
See merge request gitlab-org/gitlab-ce!30285
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two changes:
1. Move bin/web to bin/web_unicorn(removed PUMA switching logic)
Introduce new shadow script bin/web. Now we have 3 scripts working
together: bin/web, bin/web_puma, bin/web_unicorn
In bin/web, it checks ENV['USE_WEB_SERVER']:
- if value is 'puma' or value is not set, call bin/web_puma
- if value is 'unicorn', call bin/web_unicorn
- report error if other values given
2. Gitlab rails allow ENV setting to override timeout
- ENV['GITLAB_RAILS_RACK_TIMEOUT'] for service_timeout
- ENV['GITLAB_RAILS_WAIT_TIMEOUT'] for wait_timeout
|
| | |/
|/|
| |
| |
| |
| | |
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
| | |
| |
| |
| | |
These aren't used in CE, but it's safe to include them.
|
| | |
| |
| |
| |
| | |
This copies over EE-specific changes to shared configuration files in
CE.
|
| |\ \
| | |
| | |
| | |
| | | |
CE-EE parity for config/initializers
See merge request gitlab-org/gitlab-ce!30484
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We use the `Gitlab.ee` and `.ee?` methods in several initializers now.
|
| | | | |
|
| | |/
| |
| |
| |
| | |
These files are only used by EE, and are now wrapped in `Gitlab.ee`
blocks for file parity.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Remove `FeatureConstrainer` call wrapping api endpoint
- Remove `Feature.enabled?(:graphql)` conditionals in back and frontend
- Modify graphql test to be graphql flag agnostic
- Remove api routing spec
- Remove frontend feature flag via `gon`
|
| |/
|
|
|
|
|
|
| |
rack.attack.match_discriminator is only return on
throttle_authenticated_api or throttle_authenticated_web requests, so
we're avoiding logging user_id on blacklist requests
Follow up of https://gitlab.com/gitlab-org/gitlab-ce/issues/62756
|
| |
|
|
|
|
|
|
|
| |
This has the benefit that CE bundles will remove dead code in CE only
builds.
We have a follow-up issue to get rid of this completely:
https://gitlab.com/gitlab-org/gitlab-ce/issues/64173
|
| |\
| |
| |
| |
| |
| |
| | |
Fix race in forbid_sidekiq_in_transactions.rb
Closes #64088
See merge request gitlab-org/gitlab-ce!30359
|
| | |
| |
| |
| |
| |
| | |
Current code uses module attribute which stores value
global instead of locally (thread locally). This results
in concurrent accesses to overwrite the each other values
|
| |\ \
| | |
| | |
| | |
| | | |
Remove empty lines in config/README.md
See merge request gitlab-org/gitlab-ce!30346
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, we label items to be done as "Todo." This is grammatically
incorrect and (therefore) confusing—especially to our Spanish-speaking
users for whom "todo" has a specific and unrelated meaning.
We should use "To Do" and always use it as singular (not "To Dos").
Updates to wording in a few places per MR (ee) discussion
Updating locale/gitlab.pot
Updates to wording in a few places per MR (ee) discussion
Updating locale/gitlab.pot
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'63869-store-prometheus-metrics-in-separate-dirs-in-test-and-prod' into 'master'
Use separate Prometheus metrics dirs in dev/test
Closes #63869
See merge request gitlab-org/gitlab-ce!30253
|
| | | |
| | |
| | |
| | |
| | | |
Store Sidekiq and Web server metrics from Prometheus in separate
directories in `development` and `test` environments.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Fetches user based on the value of 'rack.attack.match_discriminator'
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/62756
|
| | |/
| |
| |
| |
| | |
Using `on_master_start` assures that the sampler is started in
master process and not in worker processes.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Add two new ActiveRecord models:
- RootNamespaceStoragestatistics will persist root namespace statistics
- NamespaceAggregationSchedule will save information when a new update
to the namespace statistics needs to be scheduled
- Inject into UpdateProjectStatistics concern a new callback that will
call an async job to insert a new row onto NamespaceAggregationSchedule
table
- When a new row is inserted a new job is scheduled. This job will
update call an specific service to update the statistics and after that
it will delete thee aggregated scheduled row
- The RefresherServices makes heavy use of arel to build composable
queries to update Namespace::RootStorageStatistics attributes.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Loading `ApplicationSetting` from Redis was responsible for at least 50%
of the CPU load of the Redis cluster on GitLab.com. Since these values
generally don't change very much, we can load this from the database and
cache it in memory, skipping Redis altogther. We use
`ActiveSupport::Cache::MemoryStore` as a drop-in replacement for
`RedisCacheStore` even though we probably don't need synchronized access
within `Thread.current`.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63977
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want to call master_restart callback on start too - this callback
is used for cleaning up prometheus files. It has been added to
Omnibus already:
https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3350
So make sure that Unicorn example configs are up-to-date and that
the same callback is called for Puma too.
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | | |
Get memory data after booting app in production
Closes #62722
See merge request gitlab-org/gitlab-ce!30185
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Preload the app in `production` env, hit it with a single request, and
gather total gem memory consumption data using `derailed exec perf:mem`
from `derailed_benchmarks`. Present the result as MR metrics.
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Remove ignored circuit_breaker columns
See merge request gitlab-org/gitlab-ce!30159
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The circuit breaker itself got removed a while ago, when that happened
some parts got left behind. Using grep old stale settings and
validations were found and are now removed.
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add endpoint for fetching diverging commit counts
See merge request gitlab-org/gitlab-ce!29802
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Extract diverging_commit_counts into a service class
|
| | |\ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
Copy Settings initializer from EE
See merge request gitlab-org/gitlab-ce!30140
|
| | | | | | |
|
| | | | |/
| | |/|
| | | |
| | | | |
This brings parity between the two versions.
|
| | | | |
| | | |
| | | | |
This reverts merge request !30031
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Monitor database transaction activity for Rails
See merge request gitlab-org/gitlab-ce!29928
|
| | | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently we don't have good insight into the affect of Rails
transaction blocks on the application. If these blocks are held open for
extended periods, they can have detrimental effects on the application.
This change will allow us to track these transactions, with the aim
of reducing their duration.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Preload the app in `production` env, hit it with a single request, and
gather total gem memory consumption data using `derailed exec perf:mem`
from `derailed_benchmarks`. Present the result as MR metrics.
|
| | |\ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
Extract MR's widget into a separate request
Closes #62723
See merge request gitlab-org/gitlab-ce!29979
|
| | | |/
| | |
| | |
| | |
| | |
| | | |
This commits extracts /merge_requests/1.json?serializer=widget
Into a separate /merge_requests/1/widget.json endpoint
This will allow to use caching for this request
|
