cwielenb/CNCF-Dataset huggingface dataset:
Project: Packer (App Definition and Development / Application Definition & Image Build)
File: nightly-release-readme.md

Nightly releases are snapshots of the development activity on the Packer project that may include new features and bug fixes scheduled for upcoming . These releases are made available to make it easier for users to test their existing build configurations against the latest Packer code base for potential issues or to experiment with new features, with a chance to provide feedback on ways to improve the changes before being released. As these releases are snapshots of the latest code, you may encounter an issue compared to the latest stable release. Users are encouraged to run nightly releases in a non production environment. If you encounter an issue, please check our to see if the issue has already been reported; if a report hasn't been made, please report it so we can review the issue and make any needed fixes. Note: Nightly releases are only available via GitHub Releases, and artifacts are not codesigned or notarized. Distribution via other such as the Releases Site or Homebrew is not yet supported.
Project: Copa (Provisioning / Security & Compliance)
File: installation.md

title: Installation On macOS and Linux, `copa` can be installed via : ```bash brew install copa ``` You can download the latest and previous versions of `copa` from the . (optional as a scanner) ```bash git clone https://github.com/project-copacetic/copacetic cd copacetic make sudo mv dist/linux_amd64/release/copa /usr/local/bin/ ```
Project: StarRocks (App Definition and Development / Database)
File: sharedDataCNconf.md

Before starting CNs, add the following configuration items in the CN configuration file cn.conf: ```Properties starletport = <starletport> storagerootpath = <storagerootpath> ``` The CN heartbeat service port for the StarRocks shared-data cluster. Default value: `9070`. The storage volume directory that the local cached data depends on. Multiple volumes are separated by semicolon (;). Example: `/data1;/data2`. The default value for `storagerootpath` is `${STARROCKS_HOME}/storage`. Local cache is effective when queries are frequent and the data being queried is recent, but there are cases that you may wish to turn off the local cache completely. In a Kubernetes environment with CN pods that scale up and down in number on demand, the pods may not have storage volumes attached. When the data being queried is in a data lake in remote storage and most of it is archive (old) data. If the queries are infrequent the data cache will have a low hit ratio and the benefit may not be worth having the cache. To turn off the data cache set: ```Properties storagerootpath = ``` NOTE The data is cached under the directory `<storage_root_path>/starlet_cache`.
Project: Harbor (Provisioning / Container Registry)
File: 1-13-admin-search-users.md

Test 1-13 - Admin User Search Users. ======= To verify that Admin user can search users. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database, LDAP or AD. Log in as the admin user to the UI. The admin user should see a list of users in "Admin Options". Enter different keywords or partial words to see if the user list can be filtered according to the criteria. As described in steps 1-3. None
Project: Presto (App Definition and Development / Database)
File: pull_request_template.md

<!Describe your changes in detail--> <!Why is this change required? What problem does it solve?--> <!If it fixes an open issue, please link to the issue here.--> <!Describe any public API or user-facing feature change or any performance impact--> <!Please fill in how you tested your change--> , , , and . [ ] PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced. [ ] Documented new properties (with its default value), SQL syntax, functions, or other functionality. . [ ] Adequate tests were added if applicable. [ ] CI passed. Please follow and fill in the release notes below. ``` == RELEASE NOTES == General Changes ... :pr:`12345` ... :pr:`12345` Hive Connector Changes ... :pr:`12345` ... :pr:`12345` ``` If release note is NOT required, use: ``` == NO RELEASE NOTE == ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: feature_request.md

name: Feature Request about: Create a Feature Request for Dapr title: '' labels: kind/enhancement assignees: '' <!-- If you need to report a security issue please visit https://docs.dapr.io/operations/support/support-security-issues --> <!-- Remove the '> ' to select --> /area runtime /area operator /area placement /area docs /area test-and-release <!-- Please also discuss possible business value --> <!-- How should this new feature be announced in our release notes? It can be populated later. --> <!-- Keep it as a single line. Examples: --> <!-- RELEASE NOTE: ADD New feature in Dapr. --> <!-- RELEASE NOTE: FIX Bug in runtime. --> <!-- RELEASE NOTE: UPDATE Runtime dependency. --> RELEASE NOTE:
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-start.md

layout: default title: mesheryctl-system-start permalink: reference/mesheryctl/system/start redirect_from: reference/mesheryctl/system/start/ type: reference display-title: "false" language: en command: system subcommand: start Start Meshery Start Meshery and each of its cloud native components. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start [flags] </div> </pre> Start meshery <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start </div> </pre> (optional) skip opening of MesheryUI in browser. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start --skip-browser </div> </pre> (optional) skip checking for new updates available in Meshery. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start --skip-update </div> </pre> Reset Meshery's configuration file to default settings. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start --reset </div> </pre> Specify Platform to deploy Meshery to. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start -p docker </div> </pre> Specify Provider to use. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system start --provider Meshery </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for start -p, --platform string platform to deploy Meshery to. --provider string (optional) Defaults to the provider specified in the current context --reset (optional) reset Meshery's configuration file to default settings. --skip-browser (optional) skip opening of MesheryUI in browser. --skip-update (optional) skip checking for new Meshery's container images. </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Distribution (Provisioning / Container Registry)
File: implementations.md

draft: true This is a list of known implementations of the Distribution API spec. CNCF distribution is the reference implementation of the distribution API specification. It aims to fully implement the entire specification. Implements API 2.0.1 Known Issues No resumable push support Content ranges ignored Blob upload status will always return a starting range of 0 Implements API 2.0.0 Known Issues No resumable push support No PATCH implementation for blob upload Content ranges ignored
Project: StarRocks (App Definition and Development / Database)
File: minutes_add.md

displayed_sidebar: "English" Adds the specified minutes to the date, accurate to the minute. ```Haskell DATETIME minutes_add(DATETIME|DATE date, INT minutes); ``` `date`: the start time. It must be of the DATETIME or DATE type. `minutes`: the minutes to add. It must be of the INT type, it could be greater, equal or less than zero. Returns a DATETIME value. Returns NULL if either `date` or `minutes` is NULL. ```Plain select minutes_add('2022-01-01 01:01:01', 2); ++ | minutes_add('2022-01-01 01:01:01', 2) | ++ | 2022-01-01 01:03:01 | ++ select minutes_add('2022-01-01 01:01:01', -1); +-+ | minutes_add('2022-01-01 01:01:01', -1) | +-+ | 2022-01-01 01:00:01 | +-+ select minutes_add('2022-01-01', 1); ++ | minutes_add('2022-01-01', 1) | ++ | 2022-01-01 00:01:00 | ++ ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_client_common.InputProviderState.md

/ / InputProviderState .InputProviderState `Optional` execUUID: `string` the execution ID for this prompt, if any `Optional` isReEdit: `boolean` did user click to re-edit the input? `Optional` isearch: `default` state of active reverse-i-search model: `BlockModel` Copy from props; to help with getDerivedStateFromProps `Optional` multiline: `boolean` is the input in multi-line mode? if true, use text area rather than in-line input `Optional` pasteMultiLineTexts: `string` did user paste multiline texts `Optional` prompt: `InputElement` DOM element for prompt; set via `ref` in render() below `Optional` tabCompletion: `TabCompletionState` state of tab completion `Optional` typeahead: `string` typeahead completion?
Project: YDB (App Definition and Development / Database)
File: evaluate.md

`EVALUATE IF`: Executing an action depending on the condition. It's followed by: Condition. with the name and parameters of the action or an anonymous action. An optional `ELSE` followed by the second `DO` for a situation where the condition is not met. `EVALUATE FOR`: Executing an action for each item in the list. It's followed by: applied to each next element in the list. `IN` keyword. The above-declared named expression applied to the list the action is executed on. with the name and parameters of an action or an anonymous action. In the parameters, you can use both the current element from the first paragraph and any named expressions declared above, including the list itself. An optional `ELSE` followed by the second `DO` for the situation when the list is empty. Examples ```yql DEFINE ACTION $hello() AS SELECT "Hello!"; END DEFINE; DEFINE ACTION $bye() AS SELECT "Bye!"; END DEFINE; EVALUATE IF RANDOM(0) > 0.5 DO $hello() ELSE DO $bye(); EVALUATE IF RANDOM(0) > 0.1 DO BEGIN SELECT "Hello!"; END DO; EVALUATE FOR $i IN AsList(1, 2, 3) DO BEGIN SELECT $i; END DO; ``` ```yql -- copy the $input table to $count of new tables $count = 3; $input = "my_input"; $inputs = ListReplicate($input, $count); $outputs = ListMap( ListFromRange(0, $count), ($i) -> { RETURN "tmp/out_" || CAST($i as String) } ); $pairs = ListZip($inputs, $outputs); DEFINE ACTION $copy_table($pair) as $input = $pair.0; $output = $pair.1; INSERT INTO $output WITH TRUNCATE SELECT * FROM $input; END DEFINE; EVALUATE FOR $pair IN $pairs DO $copy_table($pair) ELSE DO EMPTY_ACTION (); -- you may omit this ELSE, -- do nothing is implied by default ``` {% note info %} Note that `EVALUATE` is run before the operation starts. Please also note that in `EVALUATE` you can't use . {% endnote %}
Project: Druid (App Definition and Development / Database)
File: indexing-service.md

id: indexing-service title: "Indexing Service" <!-- ~ 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. --> The Apache Druid indexing service is a highly-available, distributed service that runs indexing related tasks. Indexing are responsible for creating and Druid . The indexing service is composed of three main components: that can run a single task, that manage Peons, and an that manages task distribution to MiddleManagers. Overlords and MiddleManagers may run on the same process or across multiple processes, while MiddleManagers and Peons always run on the same process. Tasks are managed using API endpoints on the Overlord service. Please see for more information. See . See . See . See .
Project: ArangoDB (App Definition and Development / Database)
File: app-map-httplib2.md

+++ title = "Mapping the HTTP library into the Application `2/2`" weight = 35 +++ If you remember the tutorial section on the , this is an example of how to implement a custom `valueorerror` Concept converter in Outcome: {{% snippet "finale.cpp" "appmaphttplib2" %}} The first thing that you should note is that these custom converters must be injected directly into the `BOOSTOUTCOMEV2_NAMESPACE::convert` namespace, and they must partially or completely specialise {{% api "valueorerror<T, U>" %}}. Here we specialise the converter for `valueorerror` conversions from `httplib::result<U>` to `app::outcome<T>` i.e. from our third party HTTP library's error type into our application's `outcome` type (which is unique to our application, as we hard code an `app`-local error type). The second thing to note is that you need to set `enableresultinputs` and `enableoutcomeinputs` appropriately, otherwise `result` and `outcome` inputs will not be matched by this converter[^1]. In this converter, we really do wish to convert other `result` and `outcome` inputs, so we mark these booleans as `true`. The third thing to note is the requirements on `operator()`. If the requirements are not met, the `valueorerror` converting constructor in `basicresult` and `basicoutcome` disables. Note the requirement that the decayed `operator()` input `X` matches `httplib::result<U>`, and that `T` is constructible from `U`. This means that the {{% api "explicit basicresult(concepts::valueorerror<T, E> &&)" %}} and {{% api "explicit basicoutcome(concepts::valueorerror<T, E> &&)" %}} constructors are available if, and only if, the input type is a `httplib::result<U>`, and the result's value type is constructible from the input's value type. If `operator()` is available, it naturally converts a `httplib::result<U>` into an `app::outcome<T>` by either forwarding any success as-is, or calling `app::makehttplibexception()` to type erase the `httplib::failure` into an `app::httplib_error`.
Project: BOSH (Provisioning / Automation & Configuration)
File: RELEASING.md

A Gomega release is a tagged sha and a GitHub release. To cut a release: Ensure CHANGELOG.md is up to date. Use ```bash LAST_VERSION=$(git tag --sort=version:refname | tail -n1) CHANGES=$(git log --pretty=format:'- %s [%h]' HEAD...$LAST_VERSION) echo -e "## NEXT\n\n$CHANGES\n\n### Features\n\n### Fixes\n\n### Maintenance\n\n$(cat CHANGELOG.md)" > CHANGELOG.md ``` to update the changelog Categorize the changes into Breaking Changes (requires a major version) New Features (minor version) Fixes (fix version) Maintenance (which in general should not be mentioned in `CHANGELOG.md` as they have no user impact) Update GOMEGAVERSION in `gomegadsl.go` Commit, push, and release: ``` git commit -m "vM.m.p" git push gh release create "vM.m.p" git fetch --tags origin master ```
Project: KICS (Provisioning / Security & Compliance)
File: 71bf8cf8-f0a1-42fa-b9d2-d10525e0a38e.md

title: UNIX Ports Out Of Range hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 71bf8cf8-f0a1-42fa-b9d2-d10525e0a38e Query name: UNIX Ports Out Of Range Platform: Dockerfile Severity: <span style="color:#5bc0de">Info</span> Category: Networking and Firewall URL: Exposing UNIX ports out of range from 0 to 65535<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="3" FROM gliderlabs/alpine:3.3 RUN apk --no-cache add nginx EXPOSE 65536/tcp 80 443 22 CMD ["nginx", "-g", "daemon off;"] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM gliderlabs/alpine:3.3 RUN apk --no-cache add nginx EXPOSE 3000 80 443 22 CMD ["nginx", "-g", "daemon off;"] ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_describe.md

title: kbcli bench describe Describe a benchmark. ``` kbcli bench describe [flags] ``` ``` kbcli bench describe mybench ``` ``` -h, --help help for describe ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Run a benchmark.
Project: ClickHouse (App Definition and Development / Database)
File: atomic.md

slug: /en/engines/database-engines/atomic sidebar_label: Atomic sidebar_position: 10 It supports non-blocking and queries and atomic queries. `Atomic` database engine is used by default. ``` sql CREATE DATABASE test [ENGINE = Atomic]; ``` All tables in database `Atomic` have persistent and store data in directory `/clickhouse_path/store/xxx/xxxyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy/`, where `xxxyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy` is UUID of the table. Usually, the UUID is generated automatically, but the user can also explicitly specify the UUID in the same way when creating the table (this is not recommended). For example: ```sql CREATE TABLE name UUID '28f1c61c-2970-457a-bffe-454156ddcfef' (n UInt64) ENGINE = ...; ``` :::note You can use the setting to display the UUID with the `SHOW CREATE` query. ::: queries are performed without changing the UUID or moving table data. These queries do not wait for the completion of queries using the table and are executed instantly. On `DROP TABLE` no data is removed, database `Atomic` just marks table as dropped by moving metadata to `/clickhousepath/metadatadropped/` and notifies background thread. Delay before final table data deletion is specified by the setting. You can specify synchronous mode using `SYNC` modifier. Use the setting to do this. In this case `DROP` waits for running `SELECT`, `INSERT` and other queries which are using the table to finish. Table will be actually removed when it's not in use. query swaps tables or dictionaries atomically. For instance, instead of this non-atomic operation: ```sql RENAME TABLE newtable TO tmp, oldtable TO newtable, tmp TO oldtable; ``` you can use one atomic query: ``` sql EXCHANGE TABLES newtable AND oldtable; ``` For tables, it is recommended not to specify engine parameters - path in ZooKeeper and replica name. In this case, configuration parameters and will be used. If you want to specify engine parameters explicitly, it is recommended to use `{uuid}` macros. This is useful so that unique paths are automatically generated for each table in ZooKeeper. system table
Project: YugabyteDB (App Definition and Development / Database)
File: large-datasets-ysql.md

title: Benchmark YSQL performance with large datasets headerTitle: Large datasets linkTitle: Large datasets description: Benchmark YSQL performance with large datasets headcontent: Benchmark YSQL performance with large datasets menu: v2.18: identifier: large-datasets-2-ysql parent: benchmark weight: 7 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../large-datasets-ysql/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> <li > <a href="../large-datasets-ycql/" class="nav-link"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> </ul> Coming soon.
Project: KICS (Provisioning / Security & Compliance)
File: 24d932e1-91f0-46ea-836f-fdbd81694151.md

title: Route53 Record Undefined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 24d932e1-91f0-46ea-836f-fdbd81694151 Query name: Route53 Record Undefined Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Route53 HostedZone must have the Record Set defined.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" AWSTemplateFormatVersion: "2010-09-09" Description: "Router53" Resources: HostedZone: Type: AWS::Route53::HostedZone Properties: Name: "HostedZone" ``` ```json title="Positive test num. 2 - json file" hl_lines="5" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "Router53", "Resources": { "HostedZone": { "Type": "AWS::Route53::HostedZone", "Properties": { "Name": "HostedZone" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: "Router53" Resources: HostedZone: Type: AWS::Route53::HostedZone Properties: Name: "HostedZone" RecordSet: Type: AWS::Route53::RecordSet Properties: HostedZoneId: !Ref HostedZoneId Name: !Join ['', [!Ref DomainName, '.', !Ref HostedZoneName, '.']] Type: CNAME TTL: '900' ResourceRecords: !Ref DnsEndpoint ``` ```json title="Negative test num. 2 - json file" { "Description": "Router53", "Resources": { "HostedZone": { "Type": "AWS::Route53::HostedZone", "Properties": { "Name": "HostedZone" } }, "RecordSet": { "Type": "AWS::Route53::RecordSet", "Properties": { "HostedZoneId": "HostedZoneId", "Name": [ "", [ "DomainName", ".", "HostedZoneName", "." ] ], "Type": "CNAME", "TTL": "900", "ResourceRecords": [ "DnsEndpoint" ] } } }, "AWSTemplateFormatVersion": "2010-09-09" } ```