cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v21.4.3.21-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Correctly check structure of async distributed blocks. (). Backported in : Fix very rare bug when quorum insert with `quorum_parallel=1` is not really "quorum" because of deduplication. (). Backported in : Check if table function view is used as a column. This complements https://github.com/ClickHouse/ClickHouse/pull/20350. (). Backported in : Follow-up fix for . Also fixes . (). Backported in : Fix usage of function `map` in distributed queries. (). Backported in : Fix wait for mutations on several replicas for ReplicatedMergeTree table engines. Previously, mutation/alter query may finish before mutation actually executed on other replicas. (). Backported in : Fix possible hangs in zk requests in case of OOM exception. Fixes . (). Backported in : Fix approx total rows accounting for reverse reading from MergeTree. (). Backported in : Fix pushdown of `HAVING` in case, when filter column is used in aggregation. (). Backported in : LIVE VIEW (experimental feature). Fix possible hanging in concurrent DROP/CREATE of TEMPORARY LIVE VIEW in `TemporaryLiveViewCleaner`, see https://gist.github.com/vzakaznikov/0c03195960fc86b56bfe2bc73a90019e. (). Backported in : Fixed a crash when using `mannWhitneyUTest` and `rankCorr` with window functions. This fixes . (). Backported in : Fix usage of constant columns of type `Map` with nullable values. (). FileDictionarySource fix absolute file path ().
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: 2.12.0.md

lagoon lagoon-ui lagoon-build-deploy lagoon-core chart Ensure you have a local backup of the api-db and keycloak-db before you commence this update. The update of these databases from MariaDB 10.4 to 10.6 should update seamlessly. In the event it does not go smoothly, the image cannot be rolled back owing to incompatible storage engines. You will need to drop the db and restore the backup to get running again. The minimum supported version of Kubernetes is 1.21 as of this release. There are no required actions or considerations with this release
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-image.1.md

% podman-image 1 podman\-image - Manage images podman image subcommand The image command allows the management of images | Command | Man Page | Description | | -- | | -- | | build | | Build a container using a Dockerfile. | | diff | | Inspect changes on an image's filesystem. | | exists | | Check if an image exists in local storage. | | history | | Show the history of an image. | | import | | Import a tarball and save it as a filesystem image. | | inspect | | Display an image's configuration. | | list | | List the container images on the system.(alias ls) | | load | | Load an image from the docker archive. | | mount | | Mount an image's root filesystem. | | prune | | Remove all unused images from the local store. | | pull | | Pull an image from a registry. | | push | | Push an image from local storage to elsewhere. | | rm | | Remove one or more locally stored images. | | save | | Save an image to docker-archive or oci. | | scp | | Securely copy an image from one host to another. | | search | | Search a registry for an image. | | sign | | Create a signature for an image. | | tag | | Add an additional name to a local image. | | tree | | Print layer hierarchy of an image in a tree format. | | trust | | Manage container registry image trust policy. | | unmount | | Unmount an image's root filesystem. | | untag | | Remove one or more names from a locally-stored image. |
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: export2config.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: export2config namespace: default spec: components: name: export2config-demo-server type: webservice properties: image: oamdev/hello-world port: 8000 workflow: steps: name: apply-server type: apply-component outputs: name: status valueFrom: output.status.conditions[0].message properties: component: export2config-demo-server name: export-config type: export2config inputs: from: status parameterKey: data.serverstatus properties: configName: my-configmap data: testkey: | testvalue value-line-2 ```
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: pull_request_template.md

<!-- Thank you for the PR!!! --> Fixes #<issue number> in case of a bug fix, this should point to a bug and any other related issue(s) Description <!-- Describe your changes here- ideally you can get that description straight from your descriptive commit message(s)! --> Submitter Checklist These are the criteria that every PR should meet, please check them off as you review them: [ ] Adds integration tests if needed. See for more details. Reviewer Notes [ ] The code flow looks good. [ ] Unit tests and or integration tests added. Release Notes Describe any changes here so maintainer can include it in the release notes, or delete this block. ``` Examples of user facing changes: kaniko adds a new flag `--registry-repo` to override registry ```
Project: ShardingSphere (App Definition and Development / Database)
File: menushortcuts.en.md

date: 2016-04-09T16:50:16+02:00 title: Menu extra shortcuts weight: 25 You can define additional menu entries or shortcuts in the navigation menu without any link to content. Edit the website configuration `config.toml` and add a `[[menu.shortcuts]]` entry for each link your want to add. Example from the current website: [[menu.shortcuts]] name = "<i class='fab fa-github'></i> Github repo" identifier = "ds" url = "https://github.com/matcornic/hugo-theme-learn" weight = 10 [[menu.shortcuts]] name = "<i class='fas fa-camera'></i> Showcases" url = "/showcase" weight = 11 [[menu.shortcuts]] name = "<i class='fas fa-bookmark'></i> Hugo Documentation" identifier = "hugodoc" url = "https://gohugo.io/" weight = 20 [[menu.shortcuts]] name = "<i class='fas fa-bullhorn'></i> Credits" url = "/credits" weight = 30 By default, shortcuts are preceded by a title. This title can be disabled by setting `disableShortcutsTitle=true`. However, if you want to keep the title but change its value, it can be overriden by changing your local i18n translation string configuration. For example, in your local `i18n/en.toml` file, add the following content [Shortcuts-Title] other = "<Your value>" Read more about and When using a multilingual website, you can set different menus for each language. In the `config.toml` file, prefix your menu configuration by `Languages.<language-id>`. Example from the current website: [Languages] [Languages.en] title = "Documentation for Hugo Learn Theme" weight = 1 languageName = "English" [[Languages.en.menu.shortcuts]] name = "<i class='fab fa-github'></i> Github repo" identifier = "ds" url = "https://github.com/matcornic/hugo-theme-learn" weight = 10 [[Languages.en.menu.shortcuts]] name = "<i class='fas fa-camera'></i> Showcases" url = "/showcase" weight = 11 [[Languages.en.menu.shortcuts]] name = "<i class='fas fa-bookmark'></i> Hugo Documentation" identifier = "hugodoc" url = "https://gohugo.io/" weight = 20 [[Languages.en.menu.shortcuts]] name = "<i class='fas fa-bullhorn'></i> Credits" url = "/credits" weight = 30 [Languages.fr] title = "Documentation du thme Hugo Learn" weight = 2 languageName = "Franais" [[Languages.fr.menu.shortcuts]] name = "<i class='fab fa-github'></i> Repo Github" identifier = "ds" url = "https://github.com/matcornic/hugo-theme-learn" weight = 10 [[Languages.fr.menu.shortcuts]] name = "<i class='fas fa-camera'></i> Vitrine" url = "/showcase" weight = 11 [[Languages.fr.menu.shortcuts]] name = "<i class='fas fa-bookmark'></i> Documentation Hugo" identifier = "hugodoc" url = "https://gohugo.io/" weight = 20 [[Languages.fr.menu.shortcuts]] name = "<i class='fas fa-bullhorn'></i> Crdits" url = "/credits" weight = 30 Read more about and
Project: NeuVector (Provisioning / Security & Compliance)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Beam (App Definition and Development / Streaming & Messaging)
File: python-dependencies.md

type: languages title: "Python SDK dependencies" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> This page provides the information about the Apache Beam Python SDK dependencies. If your pipeline requires additional dependencies, see . Dependencies of the Apache Beam Python SDK are defined in the `setup.py` file in the Beam repository. To view them, take the following steps: Open `setup.py`. ``` https://github.com/apache/beam/blob/release-<VERSION_NUMBER>/sdks/python/setup.py ``` <p class="paragraph-wrap">Replace `&lt;VERSIONNUMBER&gt;` with the major.minor.patch version of the SDK. For example, <a href="https://github.com/apache/beam/blob/release-{{< param releaselatest >}}/sdks/python/setup.py" target="blank" rel="noopener noreferrer">https://github.com/apache/beam/blob/release-{{< param releaselatest >}}/sdks/python/setup.py</a> provides the dependencies for the {{< param release_latest >}} release.</p> Review the core dependency list under `REQUIRED_PACKAGES`. Note: If you need , such as `gcp` or `dataframe`, review the lists in `extras_require` for additional dependencies. You can also retrieve the dependency list from the command line using the following process: Create a clean virtual environment on your local machine using a supported python version. ``` $ python3 -m venv env && source ./env/bin/activate && pip install --upgrade pip setuptools wheel ``` . Retrieve the list of dependencies. ``` $ pip install pipdeptree && pipdeptree -p apache-beam ``` If you have a `docker` installation, you can inspect the dependencies preinstalled in Beam Python SDK [container images](/documentation/runtime/environments/) by creating a container from an image, for example: `docker run --rm -it --entrypoint=/bin/sh apache/beampython3.10sdk:2.55.0 -c "pip list"`. You can also find the list of the dependencies installed in Beam containers in `baseimagerequirements.txt` files in the for a corresponding Beam release branch and Python minor version.
Project: Koperator (App Definition and Development / Streaming & Messaging)
File: BUG_REPORT.md

name: Bug Report about: Report a bug to help us improve title: '' labels: '' assignees: '' Please provide a description of the problem. Please describe what you expected would happen. Please describe what happened instead. Please provide the version number where this issue was encountered. First step Second step etc. [ ] I have verified this does not duplicate an existing issue
Project: KubeArmor (Provisioning / Security & Compliance)
File: kubearmor_vm.md

This recipe explains how to use KubeArmor directly on a VM/Bare-Metal machine, and we tested the following steps on Ubuntu hosts. The recipe installs `kubearmor` as systemd process and `karmor` cli tool to manage policies and show alerts/telemetry. Download the or KubeArmor. Install KubeArmor (VER is the kubearmor release version) ``` sudo apt --no-install-recommends install ./kubearmor${VER}linux-amd64.deb ``` > Note that the above command doesn't installs the recommended packages, as we ship object files along with the package file. In case you don't have BTF, consider removing `--no-install-recommends` flag. <details><summary>For distributions other than Ubuntu/Debian</summary> <p> Refer to install pre-requisites. Download release tarball from KubeArmor releases for the version you want ``` wget https://github.com/KubeArmor/KubeArmor/releases/download/v${VER}/kubearmor${VER}linux-amd64.tar.gz ``` Unpack the tarball to the root directory: ``` sudo tar --no-overwrite-dir -C / -xzf kubearmor${VER}linux-amd64.tar.gz sudo systemctl daemon-reload ``` </p> </details> ``` sudo systemctl start kubearmor ``` Check the status of KubeArmor using `sudo systemctl status kubearmor` or use `sudo journalctl -u kubearmor -f` to continuously monitor kubearmor logs. Following policy is to deny execution of `sleep` binary on the host: ```yaml= apiVersion: security.kubearmor.com/v1 kind: KubeArmorHostPolicy metadata: name: hsp-kubearmor-dev-proc-path-block spec: process: matchPaths: path: /usr/bin/sleep # try sleep 1 action: Block ``` Save the above policy to `hostpolicy.yaml` and apply: ``` karmor vm policy add hostpolicy.yaml ``` Now if you run `sleep` command, the process would be denied execution. Note that `sleep` may not blocked if you run it in the same terminal where you apply the above policy. In that case, please open a new terminal and run `sleep` again to see if the command is blocked. ``` karmor logs --json ``` ```json= { "Timestamp": 1639803960, "UpdatedTime": "2021-12-18T05:06:00.077564Z", "ClusterName": "Default", "HostName": "pandora", "HostPID": 3390423, "PPID": 168556, "PID": 3390423, "UID": 1000, "PolicyName": "hsp-kubearmor-dev-proc-path-block", "Severity": "1", "Type": "MatchedHostPolicy", "Source": "zsh", "Operation": "Process", "Resource": "/usr/bin/sleep", "Data": "syscall=SYS_EXECVE", "Action": "Block", "Result": "Permission denied" } ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: koyeb.md

id: koyeb title: Deploying with Koyeb sidebar_label: Koyeb description: How to deploy Backstage to Koyeb This guide explains how to deploy Backstage to , a serverless platform that provides the fastest way to deploy applications globally. Koyeb supports git-driven and container-based deployments. Before you begin, make sure you have a to follow this guide. First, install the and follow the instructions in the to login. Then, configure your `app-config.yaml` with your `baseUrl`: ```yaml app: baseUrl: https://<your-app>.koyeb.app backend: baseUrl: https://<your-app>.koyeb.app listen: port: ${PORT} ``` Push your Backstage application with its to Koyeb using the following command: ```bash koyeb app init example-backstage \ --git github.com/<YOURGITHUBUSERNAME>/<YOURREPOSITORYNAME> \ --git-branch main \ --ports 8000:http \ --routes /:8000 \ --env PORT=8000 ``` Your application will be built and deployed to Koyeb. Once the build has finished, you will be able to access your application running on Koyeb by clicking the URL ending with `.koyeb.app`. Congratulations! Now you should have Backstage up and running!
Project: ArangoDB (App Definition and Development / Database)
File: error_codes.md

+++ title = "Error codes" description = "Error codes with their good and bad sides." weight = 30 +++ Error codes are reasonable error handling technique, also working in C. In this case the information is also stored as an `int`, but returned by value, which makes it possible to make functions pure (side-effect-free and referentially transparent). ```c++ int readInt(const char * filename, int& val) { FILE* fd; int r = openFile(filename, /out/ fd); if (r != 0) return r; // return whatever error openFile() returned r = readInt(fd, /out/ val); if (r != 0) return READERRC_NOINT; // my error code return 0; // success } ``` Because the type of the error information (`int`) is known statically, no memory allocation or type erasure is required. This technique is very efficient. All failure paths written manually can be considered both an advantage and a disadvantage. Forgetting to put a failure handling `if` causes bugs. If I need to substitute an error code returned by lower-level function with mine more appropriate at this level, the information about the original failure is gone. Also, all possible error codes invented by different programmers in different third party libraries must fit into one `int` and not overlap with any other error code value. This is quite impossible and does not scale well. Because errors are communicated through returned values, we cannot use function's return type to return computed values. Computed values are written to function output parameters, which requires objects to be created before we have values to put into them. This requires many objects in unintended state to exist. Writing to output parameters often requires an indirection and can incur some run-time cost.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show.md

layout: global title: Show Commands displayTitle: Show Commands license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. * * * *
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_s3_delete.md

Delete a S3 YugabyteDB Anywhere storage configuration Delete a S3 storage configuration in YugabyteDB Anywhere ``` yba storage-config s3 delete [flags] ``` ``` -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for delete ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere S3 storage configuration
Project: StarRocks (App Definition and Development / Database)
File: distinct_map_keys.md

displayed_sidebar: "English" Removes duplicate keys from a map, because keys in a map must be unique in terms of semantics. This function keeps only the last value for identical keys, called LAST WIN. This function is used when querying MAP data from external tables if there are duplicate keys in maps. StarRocks internal tables natively remove duplicate keys in maps. This function is supported from v3.1 onwards. ```Haskell distinctmapkeys(any_map) ``` `any_map`: the MAP value from which you want to remove duplicate keys. Returns a new map without duplicate keys in each map. If the input is NULL, NULL is returned. Example 1: Simple usage. ```plain select distinctmapkeys(map{"a":1,"a":2}); +-+ | distinctmapkeys(map{'a':1,'a':2}) | +-+ | {"a":2} | +-+ ``` Example 2: Query MAP data from external tables and remove duplicate keys from the `col_map` column. ```plain select distinctmapkeys(colmap) as unique, colmap from external_table; +++ | unique | col_map | +++ | {"c":2} | {"c":1,"c":2} | | NULL| NULL | | {"e":4,"d":5} | {"e":4,"d":5} | +++ 3 rows in set (0.05 sec) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.23.md

layout: release date: 2022-11-10 tag: v0.6.23 language: en Add new capability registry @Revolyssup (#6504) Add k8s static components @Revolyssup (#6494) [CI] Fix `indent-error-flow` from `golangci-lint` report @acald-creator (#6502) fix: incorrect if condition in makefile for detecting os @nishantwrp (#6501) fix: 404 when extension is reloaded @Abhishek-kumar09 (#6511) [server] Delete MeshSync data on deleting K8s Context @theBeginner86 (#6435) fonts and object fields additional @harkiratsm (#6505) [Node Configuration] Background Color @harkiratsm (#6496) fix to field template [rjsf] @harkiratsm (#6495) Fixing behaviour of object in array @harkiratsm (#6481) fix: openssl-legacy-provider flag causing errors on doing ui-build in macos @nishantwrp (#6499) [Config Tooltip] bugs fixes @harkiratsm (#6492) [chore] Update Dynamic Route to catch multiple segments @theBeginner86 (#6490) Bump @emotion/react from 11.10.4 to 11.10.5 in /provider-ui @dependabot (#6464) Bump eslint from 8.24.0 to 8.26.0 in /provider-ui @dependabot (#6471) Add end to end tests for kubernetes components @Revolyssup (#6264) Fix test adapter pipeline workflow @AugustasV (#6498) [chore] Update Dynamic Route to catch multiple segments @theBeginner86 (#6490) Bump @emotion/react from 11.10.4 to 11.10.5 in /provider-ui @dependabot (#6464) Bump eslint from 8.24.0 to 8.26.0 in /provider-ui @dependabot (#6471) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @AugustasV, @Revolyssup, @acald-creator, @dependabot, @dependabot[bot], @harkiratsm, @l5io, @leecalcote, @nishantwrp, @theBeginner86, @warunicorn19 and l5io
Project: Chef InSpec (Provisioning / Security & Compliance)
File: csv.md

+++ title = "csv resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "csv" identifier = "inspec/resources/os/csv.md csv resource" parent = "inspec/resources/os" +++ Use the `csv` Chef InSpec audit resource to test configuration data in a CSV file. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `csv` resource block declares the configuration data to be tested: describe csv('file', true) do its('name') { should cmp 'foo' } end Test `csv` file without headers describe csv('file', false).params do its([0]) { should cmp 'name' } end where `'file'` is the path to a CSV file `true` or `false` tests a CSV file with or without headers. Default value: `true`. `name` is a configuration setting in a CSV file `should eq 'foo'` tests a value of `name` as read from a CSV file versus the value declared in the test `params` is the method for fetching data from a CSV file without headers. `[0]` is the array element position. The following examples show how to use this Chef InSpec audit resource. describe csv('some_file.csv', false).params do its([0]) { should eq ["name"] } end describe csv('some_file.csv') do its('setting') { should eq 1 } end The `name` property tests the value of `name` as read from a CSV file compared to the value declared in the test. its('name') { should cmp 'foo' } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}