| Age | Commit message (Collapse) | Author |
|---|
|
|
|
git-user-related local test failures
See merge request gitlab-org/gitlab-ce!31437
|
|
Utilize the auto repair functionality of system checks.
|
|
|
|
This check is being removed from gitlab-shell as the file
is now being managed by gitlab-rails.
|
|
|
|
Simplify internal post receive messages
Closes #59808
See merge request gitlab-org/gitlab-ce!31640
|
|
Add warnings to performance bar response
See merge request gitlab-org/gitlab-ce!31054
|
|
Instead of sending varied data to Gitaly, and making Gitaly construct
various messages, build the messages first and have Gitaly print
either basic messages or alert messages, in the order they come.
Depends on https://gitlab.com/gitlab-org/gitaly/merge_requests/1410
|
|
Persists if a board list is collapsed for each user.
|
|
|
|
This key is useful to reduce the amount of logic needed on the frontend:
if `has_warnings` is true, then the frontend knows that the request in
question has warnings for some metric.
|
|
For each DetailedView subclass, we add a `warnings` array to:
1. The top-level response.
2. Each individual call under the `details` key.
We use the `.thresholds` hash on the DetailedView to determine what's a
warning. If that hash is empty (the default), then the warnings array
will always be empty.
|
|
Fix moving issues API failing when text includes commit URLs
Closes #66666
See merge request gitlab-org/gitlab-ce!32317
|
|
When a issue is moved from one project to another, all associated
Markdown text is rewritten in the context of the new project. If the
note contained a link to a commit URL, `CommitRewriter#rewrite` would
fail because `Commit#link_reference_pattern` would match `nil` `commit`
values in the HTML generated from the Markdown. These `nil` values were
passed along to `Project#commits_by` because `Commit#reference_valid?`
was always returning `true`.
To prevent this issue from happening, we tighten up the check for
`Commit#reference_valid?` to look for valid SHA values.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66666
|
|
This also restructures how and where the configuration for
Snowplow lives.
|
|
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
'65312-use-group-labels-instead-of-legacy-team-labels-for-danger-picking-test-reviewers' into 'master'
Detect the new stage labels in `Gitlab::Danger::Teammate`
Closes #65312
See merge request gitlab-org/gitlab-ce!32261
|
|
Add nil check for Gitlab.config.prometheus
Closes #13806
See merge request gitlab-org/gitlab-ce!32201
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
allow_bypass_two_factor configration dose not work with saml provider
|
|
This reverts merge request !31826
|
|
This also restructures how and where the configuration for
Snowplow lives.
|
|
The `GraphQL::Function` has been deprecated in
favor of resolvers.
|
|
|
|
Code Review Usage Ping for Create SMAU
|
|
DB Load Balancing: Support SRV lookups
See merge request gitlab-org/gitlab-ce!32135
|
|
|
|
- Also add helper to undo rename_column_concurrently.
|
|
- When renaming a column concurrently, drop any existing trigger before
attempting to create a new one.
When running migration specs multiple times (as it happens during
local development), the down method of previous migrations are called.
If any of the called methods contains a call to
rename_column_concurrently, a trigger will be created and not removed.
So, the next time a migration spec is run, if the same down method is
executed again, it will cause an error when attempting to create the
trigger (since it already exists). Dropping the trigger if it already
exists will prevent this problem.
|
|
Add to the service and migration both.
|
|
- Introducting StageEvents to define the available events
- Define the event pairing rules, since some events are not compatible
- Express default Cycle Analytics stages with the event structure
|
|
Add specs for new parameter and updated documentation as well.
|
|
|
|
Add frozen_string_literal to lib part 2
See merge request gitlab-org/gitlab-ce!32094
|
|
|
|
|
|
Root namespaces have storage statistics.
This commit allows namespace owners to get those stats via GraphQL
queries like the following one
{
namespace(fullPath: "a_namespace_path") {
rootStorageStatistics {
storageSize
repositorySize
lfsObjectsSize
buildArtifactsSize
packagesSize
wikiSize
}
}
}
|
|
|
|
|
|
feat: smime signed notification emails
See merge request gitlab-org/gitlab-ce!30644
|
|
Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
|
|
Put cancelled job in DeadSet
See merge request gitlab-org/gitlab-ce!32070
|
|
This replicates Sidekiq behavior
of pushing dead job into DeadSet.
|
|
Ensure the evaluation of right-hand side expression always
results in the returning of an object or an empty String
|
|
Transform `CancelledError` into `JobRetry::Skip`
|
|
- Retry connection when it fails
- Properly shutdown daemon
- Stop monitor if the Exception is raised
- Properly guard exception handling
|
|
If we process message that is not designated to us
previously we would fire a separate Thread for that.
We don't need to do it. We can cheaply check if thread
is available, if it is, we can perform expensive operation
then.
|
|
This makes:
- very shallow `Middleware::Monitor` to only request tracking
of sidekiq jobs,
- `SidekiqStatus::Monitor` to be responsible to maintain persistent
connection to receive messages,
- `SidekiqStatus::Monitor` to always use structured logging
and instance variables
|
