cwielenb/CNCF-Dataset huggingface dataset:
Project: MongoDB (App Definition and Development / Database)
File: TESTING.md

Testing ======= Zstandard CI testing is split up into three sections: short, medium, and long tests. Short Tests -- Short tests run on CircleCI for new commits on every branch and pull request. They consist of the following tests: Compilation on all supported targets (x86, x86_64, ARM, AArch64, PowerPC, and PowerPC64) Compilation on various versions of gcc, clang, and g++ `tests/playTests.sh` on x86_64, without the tests on long data (CLI tests) Small tests (`tests/legacy.c`, `tests/longmatch.c`) on x64_64 Medium Tests Medium tests run on every commit and pull request to `dev` branch, on TravisCI. They consist of the following tests: The following tests run with UBsan and Asan on x86_64 and x86, as well as with Msan on x86_64 `tests/playTests.sh --test-large-data` Fuzzer tests: `tests/fuzzer.c`, `tests/zstreamtest.c`, and `tests/decodecorpus.c` `tests/zstreamtest.c` under Tsan (streaming mode, including multithreaded mode) Valgrind Test (`make -C tests test-valgrind`) (testing CLI and fuzzer under `valgrind`) Fuzzer tests (see above) on ARM, AArch64, PowerPC, and PowerPC64 Long Tests Long tests run on all commits to `release` branch, and once a day on the current version of `dev` branch, on TravisCI. They consist of the following tests: Entire test suite (including fuzzers and some other specialized tests) on: x86_64 and x86 with UBsan and Asan x86_64 with Msan ARM, AArch64, PowerPC, and PowerPC64 Streaming mode fuzzer with Tsan (for the `zstdmt` testing) ZlibWrapper tests, including under valgrind Versions test (ensuring `zstd` can decode files from all previous versions) `pzstd` with asan and tsan, as well as in 32-bits mode Testing `zstd` with legacy mode off Entire test suite and make install on macOS
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: userns.image.md

Sets the configuration for user namespaces when handling `RUN` instructions. The configured value can be "" (the empty string) or "container" to indicate that a new user namespace is created, it can be "host" to indicate that the user namespace in which `podman` itself is being run is reused, or it can be the path to a user namespace which is already in use by another process.
Project: ArangoDB (App Definition and Development / Database)
File: snippet.md

<div class="code-snippet">{{ $snippet := split (readFile (printf "snippets/%s" (.Get 0))) (printf "//! [%s]" (.Get 1)) }}{{ $lineno := split (index $snippet 0) "\n" | len }}{{highlight (strings.TrimLeft "\r\n" (strings.TrimRight "\r\n " (index $snippet 1))) "c++" ""}}<a href="{{ $.Site.Params.snippetsURL }}{{ .Get 0 }}#L{{ add 1 $lineno }}" class="code-snippet-url" target="_blank">View this code on Github</a></div>
Project: ArangoDB (App Definition and Development / Database)
File: hook_result.md

+++ title = "Hook result" description = "" weight = 30 +++ We now tell Outcome that for every instance of our localised `result<T>`, that on failure construction only, we want custom code to be run which increments the current slot in TLS storage and writes the current stack backtrace into it. For Outcome before v2.2, we must do this by inserting a specially named free function into a namespace searched by ADL: {{% snippet "errorcodeextended.cpp" "errorcodeextended3" %}} For Outcome v2.2 and later, we must do this by using a custom no value policy which contains a function named `onresultconstruction()`. The function implementation is identical between both mechanisms, just the name and placement of the function declaration differs. The only non-obvious part above is the call to {{< api "void setsparestorage(basicresult|basicoutcome *, uint16_t) noexcept" >}}. Both `result` and `outcome` keep their internal state metadata in a `uint32_t`, half of which is not used by Outcome. As it can be very useful to keep a small unique number attached to any particular `result` or `outcome` instance, we permit user code to set those sixteen bits to anything they feel like. The corresponding function to retrieve those sixteen bits is {{< api "uint16t sparestorage(const basicresult|basicoutcome *) noexcept" >}}. The state of the sixteen bits of spare storage are ignored during comparison operations. The sixteen bits of spare storage propagate during the following operations: Copy and move construction between `result`'s. Copy and move construction between `outcome`'s. Copy and move construction from a `result` to an `outcome`. Converting copy and move constructions for all the above. Assignment for all of the above. They are NOT propagated in these operations: Any conversion or translation which goes through a `failuretype` or `successtype`. Any conversion or translation which goes through a `ValueOrError` concept match. Any unpacking or repacking of value/error/exception e.g. a manual repack of an `outcome` into a `result`.
Project: KICS (Provisioning / Security & Compliance)
File: e01de151-a7bd-4db4-b49b-3c4775a5e881.md

title: Redshift Using Default Port hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e01de151-a7bd-4db4-b49b-3c4775a5e881 Query name: Redshift Using Default Port Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Redshift should not use the default port (5439) because an attacker can easily guess the port<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" name: Redshift community.aws.redshift: command: create node_type: ds1.xlarge identifier: new_cluster username: cluster_admin password: 1nsecur3 port: 5439 ``` ```yaml title="Negative test num. 1 - yaml file" name: Redshift2 community.aws.redshift: command: create node_type: ds1.xlarge identifier: new_cluster username: cluster_admin password: 1nsecur3 port: 1150 ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: top.md

title: "Top" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.combiners" class="Top" >}} Transforms for finding the largest (or smallest) set of elements in a collection, or the largest (or smallest) set of values associated with each key in a collection of key-value pairs. In the following example, we create a pipeline with a `PCollection`. Then, we get the largest or smallest elements in different ways. We use `Top.Largest()` to get the largest elements from the entire `PCollection`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONTopLargest" show="toplargest" >}} {{< /playground >}} We use `Top.LargestPerKey()` to get the largest elements for each unique key in a `PCollection` of key-values. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONTopLargestPerKey" show="toplargestperkey" >}} {{< /playground >}} We use `Top.Smallest()` to get the smallest elements from the entire `PCollection`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONTopSmallest" show="topsmallest" >}} {{< /playground >}} We use `Top.SmallestPerKey()` to get the smallest elements for each unique key in a `PCollection` of key-values. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONTopSmallestPerKey" show="topsmallestperkey" >}} {{< /playground >}} We use `Top.Of()` to get elements with customized rules from the entire `PCollection`. You can change how the elements are compared with `key`. By default you get the largest elements, but you can get the smallest by setting `reverse=True`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONTopOf" show="topof" >}} {{< /playground >}} We use `Top.PerKey()` to get elements with customized rules for each unique key in a `PCollection` of key-values. You can change how the elements are compared with `key`. By default you get the largest elements, but you can get the smallest by setting `reverse=True`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONTopPerKey" show="topper_key" >}} {{< /playground >}} to combine elements. Takes samples of the elements in a collection. {{< button-pydoc path="apache_beam.transforms.combiners" class="Top" >}}
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cpuset-mems.md

Memory nodes (MEMs) in which to allow execution (0-3, 0,1). Only effective on NUMA systems. If there are four memory nodes on the system (0-3), use --cpuset-mems=0,1 then processes in the container only uses memory from the first two memory nodes. On some systems, changing the resource limits may not be allowed for non-root users. For more details, see https://github.com/containers/podman/blob/main/troubleshooting.md#26-running-containers-with-resource-limits-fails-with-a-permissions-error This option is not supported on cgroups V1 rootless systems.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12299.en.md

Montior API: Add `retainedmsgcount` field to `/api/v5/monitor_current`. Add `licensequota` field to `/api/v5/monitorcurrent` Add `retainedmsgcount` and `nodeuptime` fields to `/api/v5/monitorcurrent/nodes/{node}`. Add `retainedmsgcount`, `licensequota` and `nodeuptime` fields to `/api/v5/monitor_current/nodes/{node}`. Prometheus API: Add `emqxcertexpiryat` and `emqxlicenseexpiryat` to `/api/v5/prometheus/stats` to display TLS listener certificate expiration time and license expiration time. Add `/api/v5/prometheus/auth` endpoint to provide metrics such as execution count and running status for all authenticatiors and authorizators. Add `/api/v5/prometheus/data_integration` endpoint to provide metrics such as execution count and status for all rules, actions, and connectors. Limitations: Prometheus push gateway only supports the content in `/api/v5/prometheus/stats?mode=node` For more API details and metric type information. Please see also in swagger api docs.
Project: YDB (App Definition and Development / Database)
File: combining_queries.md

Results of several SELECT statements (or subqueries) can be combined using `UNION` and `UNION ALL` keywords. ```yql query1 UNION [ALL] query2 (UNION [ALL] query3 ...) ``` Union of more than two queries is interpreted as a left-associative operation, that is ```yql query1 UNION query2 UNION ALL query3 ``` is interpreted as ```yql (query1 UNION query2) UNION ALL query3 ``` If the underlying queries have one of the `ORDER BY/LIMIT/DISCARD/INTO RESULT` operators, the following rules apply: `ORDER BY/LIMIT/INTO RESULT` is only allowed after the last query; `DISCARD` is only allowed before the first query; the operators apply to the `UNION [ALL]` as a whole, instead of referring to one of the queries; to apply the operator to one of the queries, enclose the query in parantheses
Project: StarRocks (App Definition and Development / Database)
File: map_keys.md

displayed_sidebar: "English" Returns an array of all the keys in the specified map. This function is supported from v2.5. ```Haskell mapkeys(anymap) ``` `any_map`: the MAP value from which you want to retrieve keys. The return value is in the format of `array<keyType>`. The element type in the array matches the key type in the map. If the input is NULL, NULL is returned. If a key or value in the MAP value is NULL, NULL is processed as a normal value and contained in the result. From v3.1 onwards, StarRocks supports defining MAP columns when you create a table. This example uses table `test_map`, which contains the following data: ```Plain CREATE TABLE test_map( col_int INT, col_map MAP<VARCHAR(50),INT> ) DUPLICATE KEY(col_int); INSERT INTO test_map VALUES (1,map{"a":1,"b":2}), (2,map{"c":3}), (3,map{"d":4,"e":5}); SELECT * FROM testmap ORDER BY colint; +++ | colint | colmap | +++ | 1 | {"a":1,"b":2} | | 2 | {"c":3} | | 3 | {"d":4,"e":5} | +++ 3 rows in set (0.05 sec) ``` Obtain all the keys from each row of the `col_map` column. ```Plaintext select mapkeys(colmap) from testmap order by colint; +-+ | mapkeys(colmap) | +-+ | ["a","b"] | | ["c"] | | ["d","e"] | +-+ 3 rows in set (0.05 sec) ``` This example uses Hive table `hive_map`, which contains the following data: ```Plaintext SELECT * FROM hivemap ORDER BY colint; +++ | colint | colmap | +++ | 1 | {"a":1,"b":2} | | 2 | {"c":3} | | 3 | {"d":4,"e":5} | +++ ``` After a is created in your cluster, you can use this catalog and the mapkeys() function to obtain all the keys from each row of the `colmap` column. ```Plaintext select mapkeys(colmap) from hivemap order by colint; +-+ | mapkeys(colmap) | +-+ | ["a","b"] | | ["c"] | | ["d","e"] | +-+ 3 rows in set (0.05 sec) ```
Project: YugabyteDB (App Definition and Development / Database)
File: ubuntu.md

<!-- +++ private=true +++ --> Perform the following steps to install yb-voyager using apt for Ubuntu: {{< note title="Note" >}} `apt` installation is only supported for Ubuntu 22. For other versions such as 18 and 20, use the install script via the Source installation option. {{< /note >}} Install the Yugabyte apt repository on your machine using the following command: ```sh wget https://s3.us-west-2.amazonaws.com/downloads.yugabyte.com/repos/reporpms/yb-apt-repo1.0.0all.deb sudo apt-get install ./yb-apt-repo1.0.0all.deb ``` This repository contains the `yb-voyager` debian package and the dependencies required to run `yb-voyager`. Clean the `apt-get` cache and package lists using the following commands:: ```sh sudo apt-get clean sudo apt-get update ``` Install yb-voyager and its dependencies using the following command: ```sh sudo apt-get install yb-voyager ``` Check that yb-voyager is installed using the following command: ```sh yb-voyager version ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.49.md

layout: release date: 2023-02-03 tag: v0.6.49 language: en Revert to before Kompose @acald-creator (#6990) Switch the logic in querying Kubernetes cluster config, and removed `<br />` @acald-creator (#6983) Quick fix @acald-creator (#6992) [Server] Add Support for Dry Run @sudo-NithishKarthik (#6903) Added disabled icon theme color[For Extention] @Harshit-Dandriyal (#6991) [Confirmation Modal] Add triangular badge in Confirmation Modal @Abhishek-kumar09 (#6986) Bump github.com/layer5io/meshsync from 0.6.8 to 0.6.9 @dependabot (#6973) Bump github.com/layer5io/meshkit from 0.6.22 to 0.6.23 @dependabot (#6975) Add apiVersion as query param for MeshModel components @Revolyssup (#6985) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Harshit-Dandriyal, @Revolyssup, @acald-creator, @dependabot, @dependabot[bot], @leecalcote and @sudo-NithishKarthik
Project: ShardingSphere (App Definition and Development / Database)
File: refresh-database-metadata.en.md

+++ title = "REFRESH DATABASE METADATA FROM GOVERNANCE CENTER" weight = 10 +++ The `REFRESH DATABASE METADATA` syntax is used to refresh the metadata of the local logic database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql RefreshDatabaseMetadata ::= 'FORCE'? 'REFRESH' 'DATABASE' 'METADATA' databaseName? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is to refresh all database metadata. When using `FORCE` to refresh metadata, the latest metadata will be obtained locally and written to the governance center. If without `FORCE`, it will be pulled from the governance center. Refresh metadata for specified database ```sql REFRESH DATABASE METADATA sharding_db; ``` Refresh all database metadata ```sql REFRESH DATABASE METADATA; ``` Force refresh all database metadata ```sql FORCE REFRESH DATABASE METADATA; ``` `FORCE`, `REFRESH`, `DATABASE`, `METADATA`
Project: StarRocks (App Definition and Development / Database)
File: months_sub.md

displayed_sidebar: "English" Subtracts specified months from the date. ```Haskell DATETIME months_sub(DATETIME expr1, INT expr2); ``` `expr1`: the specified date. It must be of the DATETIME or DATE type. `expr2`: the month to subtract. It must be INT type. Returns a DATETIME value. ```Plain Text select months_sub('2022-02-28 15:04:05', 1); +--+ | months_sub('2022-02-28 15:04:05', 1) | +--+ | 2022-01-28 15:04:05 | +--+ select months_sub('2022-02-28', 1); +--+ | months_sub('2022-02-28', 1) | +--+ | 2022-01-28 00:00:00 | +--+
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_security_center_policies.md

+++ title = "azurermsecuritycenter_policies resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermsecuritycenter_policies" identifier = "inspec/resources/azure/azurermsecuritycenterpolicies.md azurermsecuritycenterpolicies resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azuresecuritycenterpolicies" >}} Use the `azurermsecuritycenter_policies` InSpec audit resource to test properties of some or all Azure Security Center Policies. Security Center Policies are defined for each Resource Group. A Security Center Policy called `default` also exists for every subscription. This resource interacts with version `2015-06-01-Preview` of the Azure Management API. For more information see the >). At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.0.0 of the inspec-azure resource pack. An `azurermsecuritycenter_policies` resource block uses an optional filter to select a group of Security Center Policies and confirm that the expected groups exist. describe azurermsecuritycenter_policies do ... end describe azurermsecuritycenter_policies do its('names') { should include 'default' } end describe azurermsecuritycenter_policies.where(name: 'default') it { should exist } end `names` Filters the results to include only those Security Center Policies that match the given name. This is a string value. describe azurermsecuritycenter_policies.where(name: 'default') it { should exist } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermsecuritycenter_policies.where(name: 'default') it { should exist } end describe azurermsecuritycenter_policies.where(name: 'DoesNotExist') it { should_not exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: Kubescape (Provisioning / Security & Compliance)
File: providers.md

Kubescape results are a very useful input to security services. Here are a list of commercial services that are compatible with Kubescape. If you develop one, please send a PR to add it to this list! ARMO Platform is the enterprise solution based on, and powered by Kubescape. Its a multi-cloud Kubernetes and CI/CD security platform with a single pane of glass. Features include risk analysis, security compliance, misconfiguration, image vulnerability, repository and registry scanning, RBAC visualization, and more. The Community Edition is free forever! .
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.22.md

RabbitMQ `3.10.22` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang versions older than 24.3 have reached . This release of RabbitMQ or later versions. Nodes will fail to start on older Erlang releases. Erlang 25.3 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . The package unintentionally limited supported Erlang versions to `<= 25.3.0` instead of `< 26`. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.22.tar.xz` instead of the source tarball produced by GitHub.
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_create.md

Helps with the creation of various Kyverno resources. Helps with the creation of various Kyverno resources. ``` kyverno create [flags] ``` ``` kyverno create metrics-config -i ns-included-1 -i ns-included-2 -e ns-excluded kyverno create test -p policy.yaml -r resource.yaml -f values.yaml --pass policy-name,rule-name,resource-name,resource-namespace,resource-kind kyverno create user-info -u molybdenum@somecorp.com -g basic-user -c admin kyverno create values -g request.mode=dev -n prod,env=prod --rule policy,rule,env=demo --resource policy,resource,env=demo ``` ``` -h, --help help for create ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Kubernetes Native Policy Management. - Create a Kyverno policy exception file. - Create a Kyverno metrics-config file. - Create a Kyverno test file. - Create a Kyverno user-info file. - Create a Kyverno values file.