| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This is a small change to move AfterCommitQueue.inside_transaction?
to Gitlab::Database.inside_transaction? Since this change is required
by different changes which may not arrive in sequence, it's easier
to extract this change out on it's own.
|
| |
|
|
|
|
|
|
| |
Add index for pages domain ssl auto renewal
Add PagesDomain.needs_ssl_renewal scope
Add cron worker for ssl renewal
Add worker for ssl renewal
Add pages ssl renewal worker queues settings
|
| |\
| |
| |
| |
| | |
Backport changes made by EE to various YAML configuration files
See merge request gitlab-org/gitlab-ce!29606
|
| | |
| |
| |
| |
| |
| |
| |
| | |
To make this happen, we need to conditionally add the group_saml
strategy when running tests, but only on EE. This requires some changes
to Gitlab.ee? so that it can be used before/without loading the Rails
environment. We also have to change how we require a few files, so this
can run outside of Rails.
|
| |/
|
|
| |
MySQL support has been removed
|
| | |
|
| |
|
|
|
| |
Because there will be similar observer for PumaWorkerKiller,
it makes sense to keep both on better place.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Gitlab::HTTP now resolves the hostname only once, verifies the IP is not
blocked, and then uses the same IP to perform the actual request, while
passing the original hostname in the `Host` header and SSL SNI field.
|
| | |
| |
| |
| |
| |
| |
| | |
It assures that requests are aborted after 60 seconds, otherwise
an exception is raised. This exception is logged by Sentry, also
there is a Prometheus counter for measuring number of requests in each
state.
|
| |/
|
|
|
| |
This sampler gathers Puma-specific metrics which can be used by
Prometheus then.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Storing this key in secrets.yml was a bad idea,
it would require users using HA setups to manually
replicate secrets across nodes during update,
it also needed support from omnibus package
* Revert "Generate Let's Encrypt private key"
This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976.
* Add Let's Encrypt private key to settings
as encrypted attribute
* Generate Let's Encrypt private key
in database migration
|
| |
|
|
|
|
|
|
| |
Creates a new filename to register auth logs.
This change should allow SRE's queries to make better queries
through logging infrastructure.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54528
|
| |
|
|
| |
Signed-off-by: Utkarsh Gupta <guptautkarsh2102@gmail.com>
|
| | |
|
| |\
| |
| |
| |
| | |
Add EE fixtures to SeedFu fixture paths
See merge request gitlab-org/gitlab-ce!28241
|
| | |
| |
| |
| | |
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
|
| |/
|
|
| |
[ci skip]
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the UI sends a string value for lock_version (e.g. "0"), then the
previous monkey patch did not properly handle that properly. This
commit casts the value to an integer to determine whether to look for
NULL lock_versions.
For merge requests, GitLab sends a POST request to
`namespace/project/merge_requests/:iid` with the
`merge_request[lock_version]` parameter with a string `0`. The string
value comes from the form field, which explains why
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28145 wasn't
sufficient.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Rails 5.1's `exec_no_cache` doesn't call `async_exec` any more, but
`exec_params`: https://github.com/rails/rails/pull/33188
This means that the DB summary in the performance bar was wrong. The
individual query details were still correct (we subscribe to
ActiveRecord events for those).
We can remove this once the upstream PR to peek-pg is in a release and
we update to use that release.
|
| | |
|
| |\
| |
| |
| |
| | |
feat: add option to define the Sentry Environment
See merge request gitlab-org/gitlab-ce!27091
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'master'
Resolve "Referencing issues or epics by URL fails with 404"
Closes #61099 and #60965
See merge request gitlab-org/gitlab-ce!27827
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will fail in a few ways:
1. We might end up having a path (not a URL) starting with `//`, which
will be interpreted by browsers as a protocol-relative URL.
2. Issue, MR, snippet, etc. reference parsing will look for URLs at
`http://gitlab.example.com//project/...`, with the double slash
preventing single slashes from working.
In general, it doesn't seem like there's a valid case for this.
|
| |/
|
|
|
| |
Domain will be removed by verification worker after 1 week
of being disabled
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Removes unneeded patches
|
| |
|
|
| |
Model.new.attributes now also returns encrypted attributes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is a fairly straightforward refactor to extract the tracing
and correlation-id code from the gitlab rails codebase into the new
LabKit-Ruby project.
The corresponding import into LabKit-Ruby was in
https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1
The code itself remains very similar for now.
Extracting it allows us to reuse it in other projects, such as
Gitaly-Ruby. This will give us the advantages of correlation-ids and
distributed tracing in that project too.
|
| |\
| |
| |
| |
| |
| |
| | |
Revert "Remove HipChat integration from GitLab"
Closes #60042
See merge request gitlab-org/gitlab-ce!27172
|
| | | |
|
| | |
| |
| |
| | |
This reverts commit a5378665a1dc0b9c8dc3a4fa279a0eb78aac5aac.
|
| |/
|
|
|
|
|
|
|
| |
When there a large number of discussions on diffs, the instrumentation
has a significant impact on performance since it's often run in a tight
loop for line position calculation etc. We should disable this since
there are other ways to benchmark performance.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/52898
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add columns to store project creation settings
Add project creation level column in groups
and default project creation column in application settings
Remove obsolete line from schema
Update migration with project_creation_level column existence check
Rename migrations to avoid conflicts
Update migration methods
Update migration method
|
| |\
| |
| |
| |
| |
| |
| | |
GraphQL Type authorization
Closes #54417
See merge request gitlab-org/gitlab-ce!25724
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Enables authorizations to be defined on GraphQL Types.
module Types
class ProjectType < BaseObject
authorize :read_project
end
end
If a field has authorizations defined on it, and the return type of the
field also has authorizations defined on it. then all of the combined
permissions in the authorizations will be checked and must pass.
Connection fields are checked by "digging" to find the type class of the
"node" field in the expected location of edges->node.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54417
|
| |/
|
|
| |
This prevents `&mdash` in our templates being change to `-`
|
| |
|
|
|
| |
Loads 'Gitlab::Jira::Middleware' only if it exists
so this initializer can be backported to CE.
|
| |\
| |
| |
| |
| |
| |
| | |
Allow external diffs to be used conditionally
Closes #54670
See merge request gitlab-org/gitlab-ce!25432
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since external diffs are likely to be a bit slower than in-database
ones, add a mode that makes diffs external after they've been obsoleted
by events. This should strike a balance between performance and disk
space.
A background cron drives the majority of migrations, since diffs become
outdated through user actions.
|
| |/
|
|
|
|
|
| |
This makes it easier to debug Gitaly performance issues in the field.
This commit also makes the tracking of query time thread-safe via
RequestStore.
|
| | |
|
| |\
| |
| |
| |
| | |
Send schema cache to Sentry on MissingAttributeError
See merge request gitlab-org/gitlab-ce!26331
|
