| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
endpoints
We can simplify the code quite a bit and improve performance by using
grape-entity merge fields:
https://github.com/ruby-grape/grape-entity/tree/v0.6.0#merge-fields
Relates to #42030
|
| | |
|
| | |
|
| |
|
| |
This reverts merge request !16626
|
| |\
| |
| |
| |
| | |
Use limit for search count queries
See merge request gitlab-org/gitlab-ce!16502
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Search query is especially slow if a user searches a generic string
which matches many records, in such case search can take tens of
seconds or time out. To speed up the search query, we search only for
first 1000 records, if there is >1000 matching records we just display
"1000+" instead of precise total count supposing that with such amount
the exact count is not so important for the user.
Because for issues even limited search was not fast enough, 2-phase
approach is used for issues: first we use simpler/faster query to get
all public issues, if this exceeds the limit, we just return the limit.
If the amount of matching results is lower than limit, we re-run more
complex search query (which includes also confidential issues).
Re-running the complex query should be fast enough in such case because the
amount of matching issues is lower than limit.
Because exact total_count is now limited, this patch also switches to
to "prev/next" pagination.
Related #40540
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Return more consistent values for merge_status on V4 MR APIs
Closes #20639
See merge request gitlab-org/gitlab-ce!16626
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
To make it more clear to developers that the entity exposes the
application secret, define a separate entity that only should be used
when the secret is needed (probably only on creation).
|
| | | | |
|
| | |/
|/| |
|
| |/
|
|
| |
pull
|
| |\
| |
| |
| |
| |
| |
| | |
Resolve "Project/#/Members?query= blank causes 500 error"
Closes #41673
See merge request gitlab-org/gitlab-ce!16235
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'42231-protected-branches-api-route-returns-404-for-branches-with-dots' into 'master'
Resolve "Protected branches API route returns 404 for branches with dots"
Closes #42231
See merge request gitlab-org/gitlab-ce!16591
|
| | |/ |
|
| |/
|
|
| |
with 'issues_enabled=false'"
|
| |\
| |
| |
| |
| | |
System hooks for Merge Requests
See merge request gitlab-org/gitlab-ce!14387
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix the user-agent detail API endpoint for project snippets
Closes #42129
See merge request gitlab-org/gitlab-ce!16521
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Backport 10.3.4 security fixes into master
See merge request gitlab-org/gitlab-ce!16509
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'security-10-3'
[10.3] Migrate `can_push` column from `keys` to `deploy_keys_project`
See merge request gitlab/gitlabhq!2276
(cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c)
1f2bd3c0 Backport to 10.3
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'security-10-3-do-not-expose-passwords-or-tokens-in-service-integrations-api' into 'security-10-3'
Filter out sensitive fields from the project services API
See merge request gitlab/gitlabhq!2281
(cherry picked from commit 476f2576444632f2a9a61b4cead9c1077f2c81d7)
2bcbbda0 Filter out sensitive fields from the project services API
|
| |/ /
| |
| |
| |
| | |
Adds sorting to deployments API through the `order_by` and sort
`fields`.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "N+1 queries with /projects/:project_id/builds API endpoint"
Closes #41957
See merge request gitlab-org/gitlab-ce!16445
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The N+1 issue was caused by loading the job_artifacts_archive for each
job (build) individually. Including that in the builds
AssociationRelation fixed the issue.
|
| | | |
| | |
| | |
| | | |
Enables project milestone deletion via DELETE /projects/:id/milestones/:milestone_id
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
[API] Fix creating issue when assignee_id is empty
See merge request gitlab-org/gitlab-ce!16458
|
| | |/ /
| | |
| | |
| | | |
see https://gitlab.com/gitlab-org/gitlab-ce/issues/42025
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Fix duplication in API::CircuitBreakers
See merge request gitlab-org/gitlab-ce!16456
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove soft removals related code
Closes #37447
See merge request gitlab-org/gitlab-ce!15789
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This removes all usage of soft removals except for the "pending delete"
system implemented for projects. This in turn simplifies all the query
plans of the models that used soft removals. Since we don't really use
soft removals for anything useful there's no point in keeping it around.
This _does_ mean that hard removals of issues (which only admins can do
if I'm not mistaken) can influence the "iid" values, but that code is
broken to begin with. More on this (and how to fix it) can be found in
https://gitlab.com/gitlab-org/gitlab-ce/issues/31114.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add `pipelines` endpoint to merge requests API
Closes #39214
See merge request gitlab-org/gitlab-ce!15454
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Backport authorized_keys
Closes gitlab-ee#3953
See merge request gitlab-org/gitlab-ce!16014
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add find key by base64 key or fingerprint to the internal API
See merge request !250
Squashed changes:
Add unique index to fingerprint
Add new index to schema
Add internal api to get ssh key by fingerprint
Change API endpoint to authorized_keys
Add InsecureKeyFingerprint that calculates the fingerprint without shelling out
Add require for gitlab key fingerprint
Remove uniqueness of fingerprint index
Remove unique option from migration
Fix spec style in fingerprint test
Fix rubocop complain
Extract insecure key fingerprint to separate file
Change migration to support building index concurrently
Remove those hideous tabs
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This will enable admins to identify who actually made the API request.
Relates to #36960
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Expose project_id on /api/v4/pages/domains
See merge request gitlab-org/gitlab-ce!16200
|
