root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2024-06-14 00:26:38 +00:00
parent a836c8e526
commit c4a01e9c6e
17 changed files with 180 additions and 67 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Gemfile
View File

@ -456,7 +456,7 @@ group :development, :test do
gem 'deprecation_toolkit', '~> 1.5.1', require: false # rubocop:todo Gemfile/MissingFeatureCategory
gem 'bullet', '~> 7.1.2' # rubocop:todo Gemfile/MissingFeatureCategory
# Locked on 3.3.0.5 until inspec-core is updated in Omnibus: https://github.com/inspec/inspec/pull/7030
gem 'parser', '= 3.3.3.0', feature_category: :shared
gem 'parser', '= 3.3.0.5', feature_category: :shared
gem 'pry-byebug' # rubocop:todo Gemfile/MissingFeatureCategory
gem 'pry-rails', '~> 0.3.9' # rubocop:todo Gemfile/MissingFeatureCategory
gem 'pry-shell', '~> 0.6.4' # rubocop:todo Gemfile/MissingFeatureCategory

2
Gemfile.checksum
View File

@ -482,7 +482,7 @@
{"name":"pact-mock_service","version":"3.11.2","platform":"ruby","checksum":"42d9e54546a10229d7915da5383daeb322764c2876a84b4ea521f53c6f1fba51"},
{"name":"pact-support","version":"1.20.0","platform":"ruby","checksum":"41c343a3124fb379684b9ad9f1a0766c5fa18d3b78d433a52e5552d8b9475871"},
{"name":"parallel","version":"1.24.0","platform":"ruby","checksum":"5bf38efb9b37865f8e93d7a762727f8c5fc5deb19949f4040c76481d5eee9397"},
{"name":"parser","version":"3.3.3.0","platform":"ruby","checksum":"a2e23c90918d9b7e866b18dca2b6835f227769dd2fa8e59c5841f3389cf53eeb"},
{"name":"parser","version":"3.3.0.5","platform":"ruby","checksum":"7748313e505ca87045dc0465c776c802043f777581796eb79b1654c5d19d2687"},
{"name":"parslet","version":"1.8.2","platform":"ruby","checksum":"08d1ab3721cd3f175bfbee8788b2ddff71f92038f2d69bd65454c22bb9fbd98a"},
{"name":"pastel","version":"0.8.0","platform":"ruby","checksum":"481da9fb7d2f6e6b1a08faf11fa10363172dc40fd47848f096ae21209f805a75"},
{"name":"peek","version":"1.1.0","platform":"ruby","checksum":"d6501ead8cde46d8d8ed0d59eb6f0ba713d0a41c11a2c4a81447b2dce37b3ecc"},

4
Gemfile.lock
View File

@ -1355,7 +1355,7 @@ GEM
expgen (~> 0.1)
rainbow (~> 3.1.1)
parallel (1.24.0)
parser (3.3.3.0)
parser (3.3.0.5)
ast (~> 2.4.1)
racc
parslet (1.8.2)
@ -2148,7 +2148,7 @@ DEPENDENCIES
os (~> 1.1, >= 1.1.4)
pact (~> 1.64)
parallel (~> 1.19)
parser (= 3.3.3.0)
parser (= 3.3.0.5)
parslet (~> 1.8)
peek (~> 1.1)
pg (~> 1.5.6)

4
doc/ci/jobs/job_artifacts.md
View File

@ -248,8 +248,8 @@ For example:
Files returned by this endpoint always have the `plain/text` content type.
In both examples, replace `<project-id>` with a valid project ID. You can find the project ID on the,
[project overview page](../../user/project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
In both examples, replace `<project-id>` with a valid project ID. You can find the project ID on the
[project overview page](../../user/project/working_with_projects.md#access-a-project-by-using-the-project-id).
Artifacts for [parent and child pipelines](../pipelines/downstream_pipelines.md#parent-child-pipelines)
are searched in hierarchical order from parent to child. For example, if both parent and

2
doc/ci/secrets/gcp_secret_manager.md
View File

@ -71,7 +71,7 @@ After setting up WIF, you must grant the WIF principal access to the secrets in
[Project's dashboard](https://console.cloud.google.com/home/dashboard).
- `POOL_ID`: The ID (not name) of the Workload Identity Pool created in the first section,
for example `gitlab-pool`.
- `GITLAB_PROJECT_ID`: The GitLab project ID found on the [project overview page](../../user/project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- `GITLAB_PROJECT_ID`: The GitLab project ID found on the [project overview page](../../user/project/working_with_projects.md#access-a-project-by-using-the-project-id).
1. Assign the role **Secret Manager Secret Accessor**.

6
doc/ci/triggers/index.md
View File

@ -84,7 +84,7 @@ In each example, replace:
- `<token>` with your trigger token.
- `<ref_name>` with a branch or tag name, like `main`.
- `<project_id>` with your project ID, like `123456`. The project ID is displayed
on the [project overview page](../../user/project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
on the [project overview page](../../user/project/working_with_projects.md#access-a-project-by-using-the-project-id).
### Use a CI/CD job
@ -107,7 +107,7 @@ trigger_pipeline:
In this example:
- `1234` is the project ID for `project-B`. The project ID is displayed on the
[project overview page](../../user/project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
[project overview page](../../user/project/working_with_projects.md#access-a-project-by-using-the-project-id).
- The [`rules`](../yaml/index.md#rules) cause the job to run every time a tag is added to `project-A`.
- `MY_TRIGGER_TOKEN` is a [masked CI/CD variables](../variables/index.md#mask-a-cicd-variable)
that contains the trigger token.
@ -125,7 +125,7 @@ Replace:
- The URL with `https://gitlab.com` or the URL of your instance.
- `<project_id>` with your project ID, like `123456`. The project ID is displayed
on the [project overview page](../../user/project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
on the [project overview page](../../user/project/working_with_projects.md#access-a-project-by-using-the-project-id).
- `<ref_name>` with a branch or tag name, like `main`. This value takes precedence over the `ref_name` in the webhook payload.
The payload's `ref` is the branch that fired the trigger in the source repository.
You must URL-encode the `ref_name` if it contains slashes.

2
doc/operations/integrated_error_tracking.md
View File

@ -124,7 +124,7 @@ Don't expose it to the public. If it is leaked or exposed, rotate the Sentry DSN
Prerequisites:
- You need the numeric [project ID](../user/project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id)
- You need the numeric [project ID](../user/project/working_with_projects.md#access-a-project-by-using-the-project-id)
for your project.
To rotate the Sentry DSN:

2
doc/user/packages/composer_repository/index.md
View File

@ -40,7 +40,7 @@ Prerequisites:
error (`Validation failed: Version is invalid`) occurs when you publish.
- A valid `composer.json` file at the project root directory.
- The Packages feature is enabled in a GitLab repository.
- The project ID, which is displayed on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- The project ID, which is displayed on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
- One of the following token types:
- A [personal access token](../../../user/profile/personal_access_tokens.md) with the scope set to `api`.
- A [deploy token](../../project/deploy_tokens/index.md)

2
doc/user/packages/conan_repository/index.md
View File

@ -185,7 +185,7 @@ Prerequisites:
- A local [Conan package](https://docs.conan.io/en/latest/creating_packages/getting_started.html)
must exist.
- For an instance remote, the package must meet the [naming convention](#package-recipe-naming-convention-for-instance-remotes).
- You must have the project ID, which is displayed on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- You must have the project ID, which is displayed on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
To publish the package, use the `conan upload` command:

2
doc/user/packages/maven_repository/index.md
View File

@ -293,7 +293,7 @@ For the instance-level endpoint, ensure the relevant section of your `pom.xml` i
| Endpoint | Endpoint URL for `pom.xml` | Additional information |
|----------|--------------------------------------------------------------------------|------------------------|
| Project | `https://gitlab.example.com/api/v4/projects/<project_id>/packages/maven` | Replace `gitlab.example.com` with your domain name. Replace `<project_id>` with your project ID, found on your [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id). |
| Project | `https://gitlab.example.com/api/v4/projects/<project_id>/packages/maven` | Replace `gitlab.example.com` with your domain name. Replace `<project_id>` with your project ID, found on your [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id). |
| Group | `https://gitlab.example.com/api/v4/groups/<group_id>/-/packages/maven` | Replace `gitlab.example.com` with your domain name. Replace `<group_id>` with your group ID, found on your group's homepage. |
| Instance | `https://gitlab.example.com/api/v4/packages/maven` | Replace `gitlab.example.com` with your domain name. |

6
doc/user/packages/npm_registry/index.md
View File

@ -70,7 +70,7 @@ Create or edit the `.npmrc` file in the same directory as your `package.json`. I
- Replace `@scope` with the [root level group](#naming-convention) of the project you're publishing to the package to.
- Replace `your_domain_name` with your domain name, for example, `gitlab.com`.
- Replace `your_project_id` is your project ID, found on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Replace `your_project_id` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
- `"${NPM_TOKEN}"` is associated with the token you created later in the process.
WARNING:
@ -166,7 +166,7 @@ In these examples:
- Replace `your_domain_name` with your domain name, for example, `gitlab.com`.
- Replace `your_group_id` with your group ID, found on the group's home page.
- Replace `your_project_id` is your project ID, found on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Replace `your_project_id` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
- Replace `your_token` with a deploy token, group access token, project access token, or personal access token.
NOTE:
@ -232,7 +232,7 @@ To install a package from the instance level, the package must have been publish
- Replace `@scope` with the [root level group](#naming-convention) of the project you're installing to the package from.
- Replace `your_domain_name` with your domain name, for example, `gitlab.com`.
- Replace `your_project_id` is your project ID, found on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Replace `your_project_id` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
1. Install the package

2
doc/user/packages/nuget_repository/index.md
View File

@ -59,7 +59,7 @@ Prerequisites:
both.
- A name for your source.
- Depending on the [endpoint level](#use-the-gitlab-endpoint-for-nuget-packages) you use, either:
- Your project ID, which is found on your [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Your project ID, which is found on your [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
- Your group ID, which is found on your group's home page.
You can now add a new source to NuGet with:

2
doc/user/packages/rubygems_registry/index.md
View File

@ -74,7 +74,7 @@ https://gitlab.example.com/api/v4/projects/<project_id>/packages/rubygems: '<you
```
- `<your token>` must be the token value of either your personal access token or deploy token.
- Your project ID is displayed on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Your project ID is displayed on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
### Authenticate with a CI job token

6
doc/user/packages/yarn_repository/index.md
View File

@ -48,7 +48,7 @@ In this configuration:
- Replace `<my-org>` with your organization scope, exclude the `@` symbol.
- Replace `<your_domain>` with your domain name.
- Replace `<your_project_id>` with your project's ID, which you can find on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Replace `<your_project_id>` with your project's ID, which you can find on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
- Replace `<your_token>` with a deployment token, group access token, project access token, or personal access token.
Scoped registry does not work in Yarn Classic in `package.json` file, based on
@ -251,7 +251,7 @@ Use these steps for each project in the `.yarnrc.yml` file:
- Replace `<my-org>` with the root level group of the project you're installing to the package from excluding the `@` symbol.
- Replace `<your_domain_name>` with your domain name, for example, `gitlab.com`.
- Replace `<your_project_id>` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Replace `<your_project_id>` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
#### Set the registry (project level)
@ -266,7 +266,7 @@ npmRegistries:
- Replace `<your_domain_name>` with your domain name, for example, `gitlab.com`.
- Replace `<your_token>` with a deployment token (recommended), group access token, project access token, or personal access token.
- Replace `<your_project_id>` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-the-project-overview-page-by-using-the-project-id).
- Replace `<your_project_id>` with your project ID, found on the [project overview page](../../project/working_with_projects.md#access-a-project-by-using-the-project-id).
### Install the package

100
doc/user/project/ml/model_registry/index.md
View File

@ -19,12 +19,16 @@ Model registry is in [beta](../../../../policy/experiment-beta-support.md). [Pro
Model registry allows data scientists and developers to manage their machine learning
models, along with all metadata associated with their creation: parameters, performance
metrics, artifacts, logs and more. For the full list of currently supported features,
metrics, artifacts, logs, and more. For the full list of supported features,
see [epic 9423](https://gitlab.com/groups/gitlab-org/-/epics/9423).
## Access the model registry
To set the model registry [visibility level](../../../public_access.md) to public, private or disabled:
To access the model registry, on the left sidebar, select **Deploy > Model registry**.
If **Model registry** is not available, ensure that it has been enabled.
To enable the model registry or set the [visibility level](../../../public_access.md) to public or private:
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Settings > General**.
@ -35,16 +39,92 @@ at least the [Reporter role](../../../permissions.md#roles) to modify or delete
## Exploring models, model versions and model candidates
To access the model registry, from the left sidebar, select **Deploy > Model registry**.
To access the model registry, on the left sidebar, select **Deploy > Model registry**.
## Creating machine learning models and model versions
This list shows all models. Select one to see its versions.
## Create machine learning models and model versions by using the UI
To create a new machine learning model and model version by using the GitLab UI:
1. On the left sidebar, select **Deploy > Model registry**.
1. On the **Model registry** page, select **Create Model**.
1. Complete the fields:
- Enter a unique name for your model name.
- Optional. Provide a description for the model.
- Optional. Create a version for the model along with a version description.
- Upload any files, logs, metrics, or parameters associated with the model.
1. Select **Create**.
You can now view the newly created model in the model registry.
To create a new model version:
1. On the model details page, select **Create model version**.
1. Complete the fields:
- Enter a unique version number following semantic versioning.
- Optional. Provide a description for the model version.
- Upload any files, logs, metrics, or parameters associated with the model version.
1. Select on **Create & import**.
The new model version is now available in the model registry.
### Delete a model
To delete a model and all its associated versions:
1. On the left sidebar, select **Deploy > Model registry**.
1. Find the model you want to delete.
1. Select the model name to view its details.
1. Select the vertical ellipsis (**{ellipsis_v}**) and **Delete model**.
1. Confirm the deletion.
### Delete a model version
To delete a model version:
1. On the left sidebar, select **Deploy > Model registry**.
1. Find the model with a version you want to delete.
1. Select the model name to view its details.
1. Select the **Versions** tab.
1. Select the version name to view its details.
1. Select the vertical ellipsis (**{ellipsis_v}**) and **Delete model version**.
1. Confirm the deletion.
### Updating a model or model version
To add artifacts to a model version:
1. On the left sidebar, select **Deploy > Model registry**.
1. Find the model.
1. Select the model name to view its details.
1. Select the **Versions** tab.
1. Select the version name to view its details.
1. Optional. Specify a path for the files to be uploaded to. For example `config`.
1. Use **select** to choose the files to upload.
1. Select **Upload**.
Alternatively, you can drag and drop files in the drop area. They will be automatically uploaded.
To delete artifacts of a version:
1. On the left sidebar, select **Deploy > Model registry**.
1. Find the model.
1. Select the model name to view its details.
1. Select the **Versions** tab.
1. Select the version name to view its details.
1. Select the box next to each artifact you want to delete.
1. Select **Delete**.
1. Confirm the deletion.
## Create machine learning models and model versions by using MLFlow
Models and model versions can be created using the [MLflow](https://www.mlflow.org/docs/latest/tracking.html) client compatibility.
For more information about how to create and manage models and model versions, see [MLflow client compatibility](../experiment_tracking/mlflow_client.md#model-registry).
You can also create models directly on GitLab by selecting **Create Model**
on the Model registry page.
## Upload files, log metrics, log parameters to a model version
### Add artifacts, metrics, and parameters to a model version by using MLFlow
Files can either be uploaded to a model version using:
@ -56,7 +136,7 @@ Users can log metrics and a parameters of a model version through the MLflow cli
## Link a model version to a CI/CD job
When creating a model version through a GitLab CI/CD job, you can link the model
version to the job, giving easy access to the job's logs, merge request, and pipeline.
version to the job, giving convenient access to the job's logs, merge request, and pipeline.
This can be done through the MLflow client compatibility. [View details](../experiment_tracking/mlflow_client.md#linking-a-model-version-to-a-cicd-job).
## Model versions and semantic versioning
@ -74,7 +154,7 @@ if a new version can be deployed without changes to the application:
consumer can safely use the new version without breaking, although the consumer might
need to be updated to use its new functionality. For example, adding a non-mandatory
feature column with a default value to the model is a minor bump, because when a value for
the added column is not passed, inference will still work.
the added column is not passed, inference still works.
- **Patch (integer):** A change in the patch component means that a new version is out that does not
require any action by the application. For example, a daily retrain of the
@ -86,13 +166,13 @@ if a new version can be deployed without changes to the application:
### Model version examples
- Initial Release: 1.0.0 - This is the first release of the model, with no changes or patches.
- Initial Release: 1.0.0 - The first release of the model, with no changes or patches.
- New Feature: 1.1.0 - A new non-breaking feature has been added to the model, incrementing the minor version.
- Bug Fix: 1.1.1 - A bug has been fixed in the model, incrementing the patch version.
- Breaking Change: 2.0.0 - A breaking change has been made to the model, incrementing the major version.
- Patch Release: 2.0.1 - A bug has been fixed in the model, incrementing the patch version.
- Prerelease: 2.0.1-alpha1 - This is a prerelease version of the model, with an alpha release.
- Prerelease: 2.0.1-rc2 - This is a release candidate version of the model.
- Prerelease: 2.0.1-alpha1 - A prerelease version of the model, with an alpha release.
- Prerelease: 2.0.1-rc2 - A release candidate version of the model.
- New Feature: 2.1.0 - A new feature has been added to the model, so the minor version is incremented.
## Related topics

86
doc/user/project/working_with_projects.md
View File

@ -13,6 +13,58 @@ DETAILS:
Most work in GitLab is done in a [project](../../user/project/index.md). Files and
code are saved in projects, and most features are in the scope of projects.
## Project overview
> - Project creation date [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/19452) in GitLab 16.10.
When you select a project, the **Project overview** page shows the project contents:
- Files in the repository
- Project information (description)
- Topics
- Badges
- Number of stars, forks, commits, branches, tags, releases, and environments in the project
- Project storage size
- Optional files and configurations
- `README` or index file
- Wiki page
- License
- Changelog
- Contributing guidelines
- Kubernetes cluster
- CI/CD configuration
- Integrations
- GitLab Pages
- Creation date
For public projects, and members of internal and private projects
with [permissions to view the project's code](../permissions.md#project-members-permissions),
the project overview page shows:
- A [`README` or index file](repository/files/index.md#readme-and-index-files).
- A list of directories in the project's repository.
For users without permission to view the project's code, the overview page shows:
- The wiki homepage.
- The list of issues in the project.
### Access a project by using the project ID
> - Project ID [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/431539) to the Actions menu in GitLab 16.7.
You can access a project by using its ID instead of its name at `https://gitlab.example.com/projects/<id>`.
For example, if in your personal namespace `alex` you have a project `my-project` with the ID `123456`,
you can access the project either at `https://gitlab.example.com/alex/my-project` or `https://gitlab.example.com/projects/123456`.
You might also need the project ID if you want to interact with the project using the [GitLab API](../../api/index.md).
To copy the project ID:
1. On the left sidebar, select **Search or go to** and find your project.
1. On the project overview page, in the upper-right corner, select **Actions** (**{ellipsis_v}**).
1. Select **Copy project ID**.
## View all projects for the instance
To view all projects for the GitLab instance:
@ -316,40 +368,6 @@ To rename a repository:
1. In the **Change path** text box, edit the path.
1. Select **Change path**.
## Access the project overview page by using the project ID
> - Project ID [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/431539) to the Actions menu in GitLab 16.7.
To access a project by using the project ID instead of its name,
go to `https://gitlab.example.com/projects/<id>`.
To copy the project ID:
1. On the left sidebar, select **Search or go to** and find your project.
1. On the project overview page, in the upper-right corner, select **Actions** (**{ellipsis_v}**).
1. Select **Copy project ID**.
For example, if in your personal namespace `alex` you have a project `my-project` with the ID `123456`, you can access the project
either at `https://gitlab.example.com/alex/my-project` or `https://gitlab.example.com/projects/123456`.
You might also need the project ID if you want to interact with it using the [GitLab API](../../api/index.md).
## Who can view the Project overview page
When you select a project, the **Project overview** page shows the project contents.
For public projects, and members of internal and private projects
with [permissions to view the project's code](../permissions.md#project-members-permissions),
the project landing page shows:
- A [`README` or index file](repository/files/index.md#readme-and-index-files).
- A list of directories in the project's repository.
For users without permission to view the project's code, the landing page shows:
- The wiki homepage.
- The list of issues in the project.
## Leave a project
> - The button to leave a project [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/431539) to the Actions menu in GitLab 16.7.

17
locale/gitlab.pot
View File

@ -3348,6 +3348,9 @@ msgstr ""
msgid "Added %{label_references} %{label_text}."
msgstr ""
msgid "Added %{timeAgo} by"
msgstr ""
msgid "Added a to do."
msgstr ""
@ -38557,7 +38560,13 @@ msgstr ""
msgid "Pipelines|%{counterLabel} more downstream pipelines"
msgstr ""
msgid "Pipelines|Active train"
msgid "Pipelines|Active"
msgstr ""
msgid "Pipelines|An error occurred while trying to fetch the active merge train."
msgstr ""
msgid "Pipelines|An error occurred while trying to fetch the completed merge train."
msgstr ""
msgid "Pipelines|An error occurred while updating the trigger token. Please try again."
@ -38608,6 +38617,9 @@ msgstr ""
msgid "Pipelines|Failed to update. Please reload page to update the list of artifacts."
msgstr ""
msgid "Pipelines|Filter by target branch"
msgstr ""
msgid "Pipelines|Full configuration"
msgstr ""
@ -53348,6 +53360,9 @@ msgstr ""
msgid "There are no matching files"
msgstr ""
msgid "There are no merge trains to show."
msgstr ""
msgid "There are no open epics"
msgstr ""