| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Without downtime, so we need the symlinks
|
|
'master'
Add a foreign key to `merge_requests.head_pipeline_id`
Closes #34065
See merge request !12837
|
|
Add RequestCache to cache via RequestStore
See merge request !12920
|
|
|
|
Protect manual actions against protected tag too
Closes #34927
See merge request !12908
|
|
|
|
|
|
|
|
fix transient rspec failure due to Poll.js race condition
Closes #35225
See merge request !12930
|
|
|
|
|
|
|
|
don't treat aborted requests as failures, they are often triggered during unload (e.g after clicking a link)
|
|
|
|
We also try to use instance variable to cache the result if
RequestStore is not available, so we could keep the same logic,
using the same cache key. Also introduce a way to specify method
specific cache key
|
|
I don't like the idea of `RequestStore` at all, because it's just a
global state which shouldn't be used at all. But we have a number of
places calling `ProtectedBranch.protected?` and `ProtectedTag.protected?`
in a loop for the same user, project, and ref whenever we're checking
against if the jobs for a given pipeline is accessible for a given user.
This means we're effectively making N queries for the same thing over
and over.
To properly fix this, we need to change how we check the permission,
and that could be a huge work. To solve this quickly, adding a cache
layer for the given request would be quite simple to do.
We're already doing this in Commit#author, and this is extending that
idea and make it generalized.
|
|
Promote visibility level helpers from Group to Namespace
Closes gitlab-ee#2950
See merge request !12910
|
|
Process scheduled background migrations as well
Closes #34951
See merge request !12787
|
|
Simply re-raise an exception when it occurs, but guarantee that no
background migration is lost in the process.
|
|
Added cop to blacklist the use of hash indexes
See merge request !12869
|
|
Remove Repository#search_files
See merge request !12879
|
|
Fix label creation from new list for subgroup projects
Closes #35181
See merge request !12906
|
|
In EE, we make use of `namespace#public?` in projects. When the project is in a
personal namespace, this breaks as the `public?` helper isn't present.
|
|
Branch and tag refactors for Gitaly
See merge request !12872
|
|
Introduce have_gitlab_http_status
Closes #34964
See merge request !12883
|
|
|
|
|
|
It also makes it possible to gracefully retry a migration in order to
avoid problems like deadlocks.
|
|
|
|
Update metric names to match Prometheus guidelines.
Closes #35031
See merge request !12812
|
|
So that whenever this failed:
expect(response).to have_gitlab_http_status(200)
We see what's the response there. Here's an example:
```
1) API::Settings Settings PUT /application/settings custom repository storage type set in the config updates application settings
Failure/Error: expect(response).to have_gitlab_http_status(200)
expected the response to have status code 200 but it was 400. The response was: {"error":"password_authentication_enabled, signin_enabled are mutually exclusive"}
```
|
|
'fix-exact-matches-of-username-and-email-on-top-of-the-user-search' into 'master'
Fixes the user order being overriden in the autocomplete controller
See merge request !12868
|
|
Pass before_script and script as-is preserving arrays
See merge request !12680
|
|
|
|
real-time content
|
|
|
|
into 'master'
Recover from renaming project that has container images
Closes #23019
See merge request !12840
|
|
|
|
'fix/sm/32032-remove-the-rest-of-trigger_schedule-related-codes' into 'master'
Remove the rest of `trigger_schedule` related codes
Closes #32032
See merge request !12839
|
|
Remove Inactive Personal Access Tokens list from Access Tokens page
Closes #19629
See merge request !12866
|
|
|
|
|
|
|
|
|
|
This reverts merge request !12633
|
|
These indexes are not recorded in the WAL (at least until PostgreSQL
10) and this isn't worth the minor performance improvement over btree
indexes.
|
|
Gitlab::Git shuffling and Gitaly annotations
See merge request !12849
|
|
We first pop a job from the Sidekiq queue / scheduled set and only if
this has been successfully deleted we process the job. This makes it
possible to minimize a possibility of a race condition happening.
|
