Add latest changes from gitlab-org/gitlab@master

GITLAB_ELASTICSEARCH_INDEXER_VERSION

@@ -1 +1 @@
-5.5.1
+5.6.0

config/feature_flags/wip/group_owner_placeholder_confirmation_bypass.yml

@@ -1,10 +0,0 @@
----
-name: group_owner_placeholder_confirmation_bypass
-description: 'Enables ability for owners of top-level enterprise groups to skip placeholder user confirmation during direct transfer'
-feature_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/544024
-introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/189546
-rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/548946
-milestone: '18.1'
-group: group::import
-type: wip
-default_enabled: false

config/sidekiq_queues.yml

@@ -895,6 +895,10 @@
   - 1
 - - security_analyzers_status_process_deleted_events
   - 1
+- - security_analyzers_status_process_group_transfer_events
+  - 1
+- - security_analyzers_status_process_project_transfer_events
+  - 1
 - - security_configuration_set_group_secret_push_protection
   - 1
 - - security_create_security_policy_project

doc/update/_index.md

@@ -29,7 +29,7 @@ Make sure to read the whole page as it contains information related to every upg
 To upgrade GitLab:
 
 1. Create an [upgrade plan](plan_your_upgrade.md) to document your upgrade steps.
-1. Familiarize yourself with the [maintenance policy documentation](../policy/maintenance.md) and the [currently maintained versions](https://about.gitlab.com/releases/#currently-maintained-versions).
+1. Familiarize yourself with the [maintenance policy documentation](../policy/maintenance.md) and the [currently maintained versions](../policy/maintenance.md#maintained-versions).
 1. Read the [release posts](https://about.gitlab.com/releases/categories/releases/) for versions you're passing over.
    In particular, deprecations, removals, and important notes on upgrading.
 1. Using the [upgrade path tool](upgrade_paths.md#upgrade-path-tool), determine what [upgrade path](upgrade_paths.md) you should take.

doc/user/gitlab_duo/feature_summary.md

@@ -20,6 +20,7 @@ They require a Premium or Ultimate subscription and one of the available add-ons
 | [Test Generation](../gitlab_duo_chat/examples.md#write-tests-in-the-ide) in IDEs | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
 | [GitLab Duo Chat](../gitlab_duo_chat/_index.md) in GitLab UI | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
 | [Code Explanation](../project/repository/code_explain.md) in GitLab UI | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
+| [Code Review](../project/merge_requests/duo_in_merge_requests.md#have-gitlab-duo-review-your-code) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
 | [Discussion Summary](../discussions/_index.md#summarize-issue-discussions-with-duo-chat) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
 | [GitLab Duo for the CLI](../../editor_extensions/gitlab_cli/_index.md#gitlab-duo-for-the-cli) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
 | [Merge Commit Message Generation](../project/merge_requests/duo_in_merge_requests.md#generate-a-merge-commit-message) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
@@ -50,7 +51,6 @@ They require a Premium or Ultimate subscription and one of the available add-ons
 |---------|----------|---------|----------------|-----------|-------------|-----------|------------------------|
 | [Code Review Summary](../project/merge_requests/duo_in_merge_requests.md#summarize-a-code-review) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes | Experiment | Experiment | {{< icon name="dash-circle" >}} No | Experiment |
 | [Issue Description Generation](../project/issues/managing_issues.md#populate-an-issue-with-issue-description-generation) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes | Experiment | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | N/A |
-| [Code Review](../project/merge_requests/duo_in_merge_requests.md#have-gitlab-duo-review-your-code) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes | Beta | Beta | Beta | N/A |
 | [Merge Request Summary](../project/merge_requests/duo_in_merge_requests.md#generate-a-description-by-summarizing-code-changes) | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes | Beta | Beta | {{< icon name="dash-circle" >}} No | Beta |
 
 [GitLab Duo Workflow](../duo_workflow/_index.md) is in private beta, does not require an add-on, and is not supported for GitLab Duo Self-Hosted.

doc/user/gitlab_duo_chat/_index.md

@@ -47,6 +47,7 @@ You can use GitLab Duo Chat in:
 - [The GitLab Web IDE (VS Code in the cloud)](../project/web_ide/_index.md)
 - VS Code, with the [GitLab Workflow extension for VS Code](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow)
 - JetBrains IDEs, with the [GitLab Duo Plugin for JetBrains](https://plugins.jetbrains.com/plugin/22325-gitlab-duo)
+- Eclipse, with the [GitLab for Eclipse extension](https://marketplace.eclipse.org/content/gitlab-eclipse)
 - Visual Studio for Windows, with the [GitLab Extension for Visual Studio](https://marketplace.visualstudio.com/items?itemName=GitLab.GitLabExtensionForVisualStudio)
 
 {{< alert type="note" >}}
@@ -335,7 +336,7 @@ To open GitLab Duo Chat Quick Chat in the editor window, use any of these method
 - From a keyboard shortcut, by pressing:
   - MacOS: <kbd>Option</kbd> + <kbd>c</kbd>
   - Windows and Linux: <kbd>ALT</kbd> + <kbd>c</kbd>
-- In the currently open file in your IDE, by selecting some code,
+- In an open file in your IDE, by selecting some code,
   then, in the floating toolbar, selecting **GitLab Duo Quick Chat** ({{< icon name="tanuki-ai" >}}).
 - Right-clicking, then selecting **GitLab Duo Chat > Open Quick Chat**.
 
@@ -356,6 +357,26 @@ After Quick Chat opens:
 </figure>
 <!-- Video published on 2024-10-15 -->
 
+## Use GitLab Duo Chat in Eclipse
+
+{{< history >}}
+
+- [Changed](https://gitlab.com/gitlab-org/editor-extensions/gitlab-eclipse-plugin/-/issues/163) from experiment to beta in GitLab 17.11.
+
+{{< /history >}}
+
+Prerequisites:
+
+- You've [installed and configured the GitLab Eclipse Plugin](../../editor_extensions/eclipse/setup.md).
+
+To use GitLab Duo Chat in the GitLab Eclipse Plugin:
+
+1. Open a project in Eclipse.
+1. To open the chat window, select **GitLab Duo Chat** ({{< icon name="duo-chat" >}}), or use the keyboard shortcut:
+   - Windows and Linux: <kbd>ALT</kbd> + <kbd>d</kbd> on Windows and Linux
+   - MacOS: <kbd>Option</kbd> + <kbd>d</kbd>
+1. In the message box, enter your question and press **Enter** or select **Send**.
+
 ## Watch a demo and get tips
 
 <div class="video-fallback">

doc/user/project/codeowners/troubleshooting.md

@@ -17,6 +17,41 @@ When working with Code Owners, you might encounter the following issues.
 
 For more information about how the Code Owners feature handles errors, see [Error handling](advanced.md#error-handling).
 
+## Validate your CODEOWNERS file
+
+{{< history >}}
+
+- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/15598) in GitLab 17.11 [with a flag](../../../administration/feature_flags.md) named `accessible_code_owners_validation`. Disabled by default.
+- [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/524437) in GitLab 18.1.
+
+{{< /history >}}
+
+{{< alert type="flag" >}}
+
+The availability of this feature is controlled by a feature flag.
+For more information, see the history.
+
+{{< /alert >}}
+
+When viewing a [`CODEOWNERS` file](_index.md#codeowners-file), GitLab runs
+validations to help you find syntax and permission issues. If no syntax issues
+are found, GitLab:
+
+- Does not run more validators against the file.
+- Runs more permissions validations against the first 200 unique user and group references found in the file.
+
+How this works:
+
+1. Find all references that can access the project. If a user or group reference is
+   added, but does not have project access, show an error.
+1. For each valid user reference, check that the user has permission to approve
+   merge requests in the project. If the user does not have that permission, show an error.
+1. For each valid group reference, check that the maximum role value is Developer or higher.
+   For each group reference that has a value lower than Developer, show an error.
+1. For each valid group reference, check that they group contains at least one user with
+   permission to approve merge requests. For any group reference containing zero users with
+   permission to approve merge requests, show an error.
+
 ## Approvals do not show
 
 The [`CODEOWNERS` file](_index.md#codeowners-file) must be present in the target branch before the

doc/user/project/members/_index.md

@@ -81,24 +81,24 @@ In the previous example:
 
 ## Security considerations
 
-Before adding members to your project, it's important to understand the security implications.
-Git is a distributed version control system (DVCS). This means that everyone who works with the
-source code has a local copy of the complete repository.
+Git is a distributed version control system (DVCS).
+Everyone who works with the source code has a local copy of the complete repository.
 
 In GitLab, every project member with the Reporter role or higher can clone the repository to create
-a local copy. After obtaining a local copy, users can upload the full repository anywhere, including:
+a local copy.
+Users can upload the full repository anywhere after they obtain a local copy, including:
 
 - Another project under their control.
 - A different server.
 - External hosting services.
 
-Access controls cannot prevent the intentional sharing of source code by users who already have access
-to the repository. It is an inherent feature of a DVCS and applies to all Git management platforms.
+Access controls cannot prevent the intentional sharing of source code by users who already have
+access to the repository.
+All Git management platforms have this inherent characteristic of distributed version control
+systems.
 
-### Mitigate risks
-
-While you cannot prevent intentional sharing by authorized users, you can take steps to prevent
-unintentional sharing and information destruction:
+While you cannot prevent intentional sharing by authorized users, you can take the following steps
+to prevent unintentional sharing and information destruction:
 
 - Control who can [add users to a project](#add-users-to-a-project).
 - Use [protected branches](../repository/branches/protected.md) to prevent unauthorized force pushes.

doc/user/project/merge_requests/duo_in_merge_requests.md

@@ -57,7 +57,6 @@ Data usage: The diff of changes between the source branch's head and the target
 - Tier: Premium, Ultimate
 - Add-on: GitLab Duo Enterprise
 - Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
-- Status: Beta
 - LLM: Anthropic [Claude 3.7 Sonnet](https://console.cloud.google.com/vertex-ai/publishers/anthropic/model-garden/claude-3-7-sonnet)
 
 {{< /details >}}
@@ -68,18 +67,12 @@ Data usage: The diff of changes between the source branch's head and the target
 - Feature flags [`ai_review_merge_request`](https://gitlab.com/gitlab-org/gitlab/-/issues/456106) and [`duo_code_review_chat`](https://gitlab.com/gitlab-org/gitlab/-/issues/508632) enabled by default on GitLab.com, GitLab Self-Managed, and GitLab Dedicated in 17.10.
 - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/516234) to beta in GitLab 17.10.
 - Changed to include Premium in GitLab 18.0.
-- Feature flag `ai_review_merge_request` [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/190639) in GitLab 18.1. 
+- Feature flag `ai_review_merge_request` [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/190639) in GitLab 18.1.
 - Feature flag `duo_code_review_chat` [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/190640) in GitLab 18.1.
+- Generally available in GitLab 18.1.
 
 {{< /history >}}
 
-{{< alert type="flag" >}}
-
-The availability of this feature is controlled by two feature flags.
-For more information, see the history.
-
-{{< /alert >}}
-
 When your merge request is ready to be reviewed, use GitLab Duo Code Review to perform an initial review:
 
 1. On the left sidebar, select **Search or go to** and find your project.

lib/gitlab/event_store/subscriber.rb

@@ -36,6 +36,10 @@ module Gitlab
         end
       end
 
+      def handle_event_in(delay, event)
+        self.class.perform_in(delay, event.class.name, event.data)
+      end
+
       def handle_event(event)
         raise NotImplementedError, 'you must implement this methods in order to handle events'
       end

spec/lib/gitlab/event_store/store_spec.rb

@@ -365,5 +365,15 @@ RSpec.describe Gitlab::EventStore::Store, feature_category: :shared do
         subject
       end
     end
+
+    context 'when using handle_event_in' do
+      it 'schedules the event with correct parameters' do
+        constructed_event = event_klass.new(data: event_data)
+
+        expect(worker).to receive(:perform_in).with(5.minutes, event_name, event_data)
+
+        worker_instance.handle_event_in(5.minutes, constructed_event)
+      end
+    end
   end
 end