diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/administration/gitaly/praefect.md | 2 | ||||
| -rw-r--r-- | doc/administration/postgresql/replication_and_failover.md | 4 | ||||
| -rw-r--r-- | doc/api/graphql/reference/index.md | 10 | ||||
| -rw-r--r-- | doc/api/packages.md | 4 | ||||
| -rw-r--r-- | doc/ci/runners/runners_scope.md | 2 | ||||
| -rw-r--r-- | doc/ci/secrets/index.md | 2 | ||||
| -rw-r--r-- | doc/development/sidekiq/limited_capacity_worker.md | 5 | ||||
| -rw-r--r-- | doc/development/sidekiq/worker_attributes.md | 41 | ||||
| -rw-r--r-- | doc/user/ai_features.md | 4 | ||||
| -rw-r--r-- | doc/user/group/settings/group_access_tokens.md | 2 | ||||
| -rw-r--r-- | doc/user/packages/generic_packages/index.md | 2 | ||||
| -rw-r--r-- | doc/user/project/merge_requests/ai_in_merge_requests.md | 28 |
12 files changed, 65 insertions, 41 deletions
diff --git a/doc/administration/gitaly/praefect.md b/doc/administration/gitaly/praefect.md index 112c441164d..53ec384ad0c 100644 --- a/doc/administration/gitaly/praefect.md +++ b/doc/administration/gitaly/praefect.md @@ -376,7 +376,7 @@ You should use PgBouncer with `session` pool mode. You can use the The following example uses the bundled PgBouncer and sets up two separate connection pools on PostgreSQL host, one in `session` pool mode and the other in `transaction` pool mode. For this example to work, -you need to prepare PostgreSQL server as documented in [in the setup instructions](#manual-database-setup): +you need to prepare PostgreSQL server as documented in [the setup instructions](#manual-database-setup): ```ruby pgbouncer['databases'] = { diff --git a/doc/administration/postgresql/replication_and_failover.md b/doc/administration/postgresql/replication_and_failover.md index e93dfc8336e..573110d7f57 100644 --- a/doc/administration/postgresql/replication_and_failover.md +++ b/doc/administration/postgresql/replication_and_failover.md @@ -428,8 +428,8 @@ authentication mode (`patroni['tls_client_mode']`), must each have the same valu # START user configuration # Set the real values as explained in Required Information section - # Replace CONSUL_PASSWORD_HASH with with a generated md5 value - # Replace PGBOUNCER_PASSWORD_HASH with with a generated md5 value + # Replace CONSUL_PASSWORD_HASH with a generated md5 value + # Replace PGBOUNCER_PASSWORD_HASH with a generated md5 value pgbouncer['users'] = { 'gitlab-consul': { password: 'CONSUL_PASSWORD_HASH' diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md index a8a29e2f01c..426d0b87bbb 100644 --- a/doc/api/graphql/reference/index.md +++ b/doc/api/graphql/reference/index.md @@ -1384,7 +1384,6 @@ Input type: `AiActionInput` | <a id="mutationaiactionfillinmergerequesttemplate"></a>`fillInMergeRequestTemplate` | [`AiFillInMergeRequestTemplateInput`](#aifillinmergerequesttemplateinput) | Input for fill_in_merge_request_template AI action. | | <a id="mutationaiactiongeneratecommitmessage"></a>`generateCommitMessage` | [`AiGenerateCommitMessageInput`](#aigeneratecommitmessageinput) | Input for generate_commit_message AI action. | | <a id="mutationaiactiongeneratedescription"></a>`generateDescription` | [`AiGenerateDescriptionInput`](#aigeneratedescriptioninput) | Input for generate_description AI action. | -| <a id="mutationaiactiongeneratetestfile"></a>`generateTestFile` | [`GenerateTestFileInput`](#generatetestfileinput) | Input for generate_test_file AI action. | | <a id="mutationaiactionresolvevulnerability"></a>`resolveVulnerability` | [`AiResolveVulnerabilityInput`](#airesolvevulnerabilityinput) | Input for resolve_vulnerability AI action. | | <a id="mutationaiactionsummarizecomments"></a>`summarizeComments` | [`AiSummarizeCommentsInput`](#aisummarizecommentsinput) | Input for summarize_comments AI action. | | <a id="mutationaiactionsummarizereview"></a>`summarizeReview` | [`AiSummarizeReviewInput`](#aisummarizereviewinput) | Input for summarize_review AI action. | @@ -34334,15 +34333,6 @@ Represents an escalation rule. | <a id="escalationruleinputstatus"></a>`status` | [`EscalationRuleStatus!`](#escalationrulestatus) | Status required to prevent the rule from activating. | | <a id="escalationruleinputusername"></a>`username` | [`String`](#string) | Username of the user to notify. | -### `GenerateTestFileInput` - -#### Arguments - -| Name | Type | Description | -| ---- | ---- | ----------- | -| <a id="generatetestfileinputfilepath"></a>`filePath` | [`String!`](#string) | File path to generate test files for. | -| <a id="generatetestfileinputresourceid"></a>`resourceId` | [`AiModelID!`](#aimodelid) | Global ID of the resource to mutate. | - ### `JiraUsersMappingInputType` #### Arguments diff --git a/doc/api/packages.md b/doc/api/packages.md index 0d69078d1a1..3d2e8e5bfbf 100644 --- a/doc/api/packages.md +++ b/doc/api/packages.md @@ -32,7 +32,7 @@ GET /projects/:id/packages | `package_name` | string | no | Filter the project packages with a fuzzy search by name. | | `package_version` | string | no | Filter the project packages by version. If used in combination with `include_versionless`, then no versionless packages are returned. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349065) in GitLab 16.6. | | `include_versionless` | boolean | no | When set to true, versionless packages are included in the response. | -| `status` | string | no | Filter the returned packages by status. One of `default` (default), `hidden`, `processing`, `error`, or `pending_destruction`. | +| `status` | string | no | Filter the returned packages by status. One of `default`, `hidden`, `processing`, `error`, or `pending_destruction`. | ```shell curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/:id/packages" @@ -98,7 +98,7 @@ GET /groups/:id/packages | `package_name` | string | no | Filter the project packages with a fuzzy search by name. | | `package_version` | string | no | Filter the returned packages by version. If used in combination with `include_versionless`, then no versionless packages are returned. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349065) in GitLab 16.6. | | `include_versionless` | boolean | no | When set to true, versionless packages are included in the response. | -| `status` | string | no | Filter the returned packages by status. One of `default` (default), `hidden`, `processing`, `error`, or `pending_destruction`. | +| `status` | string | no | Filter the returned packages by status. One of `default`, `hidden`, `processing`, `error`, or `pending_destruction`. | ```shell curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/groups/:id/packages?exclude_subgroups=false" diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md index d6a556ffd9b..230c5510111 100644 --- a/doc/ci/runners/runners_scope.md +++ b/doc/ci/runners/runners_scope.md @@ -641,7 +641,7 @@ To determine the IP address of a shared runner: ### Determine the IP address of a project runner -To can find the IP address of a runner for a project project, +To can find the IP address of a runner for a project, you must have the Owner role for the project. diff --git a/doc/ci/secrets/index.md b/doc/ci/secrets/index.md index 96b9709bdef..96a35703f1f 100644 --- a/doc/ci/secrets/index.md +++ b/doc/ci/secrets/index.md @@ -33,7 +33,7 @@ The [Authenticating and Reading Secrets With HashiCorp Vault](../examples/authen tutorial has more details about authenticating with ID tokens. You must [configure your Vault server](#configure-your-vault-server) before you -can use [use Vault secrets in a CI job](#use-vault-secrets-in-a-ci-job). +can [use Vault secrets in a CI job](#use-vault-secrets-in-a-ci-job). The flow for using GitLab with HashiCorp Vault is summarized by this diagram: diff --git a/doc/development/sidekiq/limited_capacity_worker.md b/doc/development/sidekiq/limited_capacity_worker.md index e8561cb936d..ff8728f3751 100644 --- a/doc/development/sidekiq/limited_capacity_worker.md +++ b/doc/development/sidekiq/limited_capacity_worker.md @@ -94,3 +94,8 @@ name as label: - `limited_capacity_worker_running_jobs` - `limited_capacity_worker_max_running_jobs` - `limited_capacity_worker_remaining_work_count` + +## Alternatives + +If limited capacity worker doesn't fit your architecture, there's also a [concurrency limit](worker_attributes.md#concurrency-limit) +attribute that can be used to restrict concurrency of a Sidekiq worker. diff --git a/doc/development/sidekiq/worker_attributes.md b/doc/development/sidekiq/worker_attributes.md index 016bf0b6634..072f34f0c96 100644 --- a/doc/development/sidekiq/worker_attributes.md +++ b/doc/development/sidekiq/worker_attributes.md @@ -365,3 +365,44 @@ class PausedWorker # ... end ``` + +## Concurrency limit + +With the `concurrency_limit` property, you can limit the worker's concurrency. It will put the jobs that are over this limit in +a separate `LIST` and re-enqueued when it falls under the limit. `ConcurrencyLimit::ResumeWorker` is a cron +worker that checks if any throttled jobs should be re-enqueued. + +The first job that crosses the defined concurency limit initiates the throttling process for all other jobs of this class. +Until this happens, jobs are scheduled and executed as usual. + +When the throttling starts, newly scheduled and executed jobs will be added to the end of the `LIST` to ensure that +the execution order is preserved. As soon as the `LIST` is empty again, the throttling process ends. + +WARNING: +If there is a sustained workload over the limit, the `LIST` is going to grow until the limit is disabled or +the workload drops under the limit. + +FLAG: +The feature is currently behind a default-disabled feature flag `sidekiq_concurrency_limit_middleware`. + +You should use a lambda to define the limit. If it returns `nil`, `0`, or a negative value, the limit won't be applied. + +```ruby +class LimitedWorker + include ApplicationWorker + + concurrency_limit -> { 60 } + + # ... +end +``` + +```ruby +class LimitedWorker + include ApplicationWorker + + concurrency_limit -> { ApplicationSetting.current.elasticsearch_concurrent_sidekiq_jobs } + + # ... +end +``` diff --git a/doc/user/ai_features.md b/doc/user/ai_features.md index 931876682e0..0659f39564c 100644 --- a/doc/user/ai_features.md +++ b/doc/user/ai_features.md @@ -18,7 +18,7 @@ GitLab is creating AI-assisted features across our DevSecOps platform. These fea | Assists with quickly getting everyone up to speed on lengthy conversations to help ensure you are all on the same page. | [Discussion summary](#summarize-issue-discussions-with-discussion-summary) | **(ULTIMATE SAAS EXPERIMENT)** | | Generates issue descriptions. | [Issue description generation](#summarize-an-issue-with-issue-description-generation) | **(ULTIMATE SAAS EXPERIMENT)** | | Helps you write code more efficiently by viewing code suggestions as you type. <br><br><i class="fa fa-youtube-play youtube" aria-hidden="true"></i> [Watch overview](https://www.youtube.com/watch?v=hCAyCTacdAQ) | [Code Suggestions](project/repository/code_suggestions/index.md) | For SaaS: **(FREE)**<br><br> For self-managed: **(PREMIUM)** | -| Automates repetitive tasks and helps catch bugs early. | [Test generation](project/merge_requests/ai_in_merge_requests.md#generate-suggested-tests-in-merge-requests) | **(ULTIMATE SAAS EXPERIMENT)** | +| Automates repetitive tasks and helps catch bugs early. | [Test generation](gitlab_duo_chat.md#write-tests-in-the-ide) | **(ULTIMATE SAAS EXPERIMENT)** | | Generates a description for the merge request based on the contents of the template. | [Merge request template population](project/merge_requests/ai_in_merge_requests.md#fill-in-merge-request-templates) | **(ULTIMATE SAAS EXPERIMENT)** | | Assists in creating faster and higher-quality reviews by automatically suggesting reviewers for your merge request. <br><br><i class="fa fa-youtube-play youtube" aria-hidden="true"></i> [Watch overview](https://www.youtube.com/watch?v=ivwZQgh4Rxw) | [Suggested Reviewers](project/merge_requests/reviews/index.md#gitlab-duo-suggested-reviewers) | **(ULTIMATE SAAS)** | | Efficiently communicates the impact of your merge request changes. | [Merge request summary](project/merge_requests/ai_in_merge_requests.md#summarize-merge-request-changes) | **(ULTIMATE SAAS EXPERIMENT)** | @@ -194,7 +194,7 @@ For details about this Beta feature, see [GitLab Duo Chat](gitlab_duo_chat.md). | [Discussion summary](#summarize-issue-discussions-with-discussion-summary) | Vertex AI Codey [`text-bison`](https://cloud.google.com/vertex-ai/docs/generative-ai/model-reference/text) | | [Issue description generation](#summarize-an-issue-with-issue-description-generation) | Anthropic [`Claude-2`](https://docs.anthropic.com/claude/reference/selecting-a-model) | | [Code Suggestions](project/repository/code_suggestions/index.md) | For Code Completion: Vertex AI Codey [`code-gecko`](https://cloud.google.com/vertex-ai/docs/generative-ai/model-reference/code-completion) For Code Generation: Anthropic [`Claude-2`](https://docs.anthropic.com/claude/reference/selecting-a-model) | -| [Test generation](project/merge_requests/ai_in_merge_requests.md#generate-suggested-tests-in-merge-requests) | Vertex AI Codey [`text-bison`](https://cloud.google.com/vertex-ai/docs/generative-ai/model-reference/text) | +| [Test generation](gitlab_duo_chat.md#write-tests-in-the-ide) | Vertex AI Codey [`text-bison`](https://cloud.google.com/vertex-ai/docs/generative-ai/model-reference/text) | | [Merge request template population](project/merge_requests/ai_in_merge_requests.md#fill-in-merge-request-templates) | Vertex AI Codey [`text-bison`](https://cloud.google.com/vertex-ai/docs/generative-ai/model-reference/text) | | [Suggested Reviewers](project/merge_requests/reviews/index.md#gitlab-duo-suggested-reviewers) | GitLab creates a machine learning model for each project, which is used to generate reviewers [View the issue](https://gitlab.com/gitlab-org/modelops/applied-ml/applied-ml-updates/-/issues/10) | | [Merge request summary](project/merge_requests/ai_in_merge_requests.md#summarize-merge-request-changes) | Vertex AI Codey [`text-bison`](https://cloud.google.com/vertex-ai/docs/generative-ai/model-reference/text) | diff --git a/doc/user/group/settings/group_access_tokens.md b/doc/user/group/settings/group_access_tokens.md index 5b3f962061e..a8633c0cbbe 100644 --- a/doc/user/group/settings/group_access_tokens.md +++ b/doc/user/group/settings/group_access_tokens.md @@ -82,7 +82,7 @@ or API. However, administrators can use a workaround: # Set the GitLab administration user to use. If user ID 1 is not available or is not an administrator, use 'admin = User.admins.first' instead to select an administrator. admin = User.find(1) - # Set the group group you want to create a token for. For example, group with ID 109. + # Set the group you want to create a token for. For example, group with ID 109. group = Group.find(109) # Create the group bot user. For further group access tokens, the username should be `group_{group_id}_bot_{random_string}` and email address `group_{group_id}_bot_{random_string}@noreply.{Gitlab.config.gitlab.host}`. diff --git a/doc/user/packages/generic_packages/index.md b/doc/user/packages/generic_packages/index.md index 188b634af0a..6348a8b9da7 100644 --- a/doc/user/packages/generic_packages/index.md +++ b/doc/user/packages/generic_packages/index.md @@ -50,7 +50,7 @@ PUT /projects/:id/packages/generic/:package_name/:package_version/:file_name?sta | `package_name` | string | yes | The package name. It can contain only lowercase letters (`a-z`), uppercase letter (`A-Z`), numbers (`0-9`), dots (`.`), hyphens (`-`), or underscores (`_`). | `package_version` | string | yes | The package version. The following regex validates this: `\A(\.?[\w\+-]+\.?)+\z`. You can test your version strings on [Rubular](https://rubular.com/r/aNCV0wG5K14uq8). | `file_name` | string | yes | The filename. It can contain only lowercase letters (`a-z`), uppercase letter (`A-Z`), numbers (`0-9`), dots (`.`), hyphens (`-`), or underscores (`_`). -| `status` | string | no | The package status. It can be `default` (default) or `hidden`. Hidden packages do not appear in the UI or [package API list endpoints](../../../api/packages.md). +| `status` | string | no | The package status. It can be `default` or `hidden`. Hidden packages do not appear in the UI or [package API list endpoints](../../../api/packages.md). | `select` | string | no | The response payload. By default, the response is empty. Valid values are: `package_file`. `package_file` returns details of the package file record created by this request. Provide the file context in the request body. diff --git a/doc/user/project/merge_requests/ai_in_merge_requests.md b/doc/user/project/merge_requests/ai_in_merge_requests.md index daddf5477ca..8be2d45f06b 100644 --- a/doc/user/project/merge_requests/ai_in_merge_requests.md +++ b/doc/user/project/merge_requests/ai_in_merge_requests.md @@ -94,27 +94,15 @@ Provide feedback on this experimental feature in [issue 408994](https://gitlab.c - Contents of the file - The file name -## Generate suggested tests in merge requests - -> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/10366) in GitLab 16.0 as an [Experiment](../../../policy/experiment-beta-support.md#experiment). - -This feature is an [Experiment](../../../policy/experiment-beta-support.md) on GitLab.com. - -Use GitLab Duo Test generation in a merge request to see a list of suggested tests for the file you are reviewing. This functionality can help determine if appropriate test coverage has been provided, or if you need more coverage for your project. - -View a [click-through demo](https://go.gitlab.com/Xfp0l4). +<!--- start_remove The following content will be removed on remove_date: '2024-04-12' --> -To generate a test suggestion: - -1. In a merge request, select the **Changes** tab. -1. On the header for the file, in the upper-right corner, select **Options** (**{ellipsis_v}**). -1. Select **Suggest test cases**. - -The test suggestion is generated in a sidebar. You can copy the suggestion to your editor and use it as the start of your tests. +## Generate suggested tests in merge requests -Feedback on this experimental feature can be provided in [issue 408995](https://gitlab.com/gitlab-org/gitlab/-/issues/408995). +> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/10366) in GitLab 16.0 as an [Experiment](../../../policy/experiment-beta-support.md#experiment). +> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/141086) to GitLab Duo Chat in GitLab 16.8. -**Data usage**: When you use this feature, the following data is sent to the large language model referenced above: +This feature was [moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/141086) +into GitLab Duo Chat in GitLab 16.8. Find more information in +[Write tests in the IDE](../../gitlab_duo_chat.md#write-tests-in-the-ide). -- Contents of the file -- The file name +<!--- end_remove --> |