cwielenb/CNCF-Dataset huggingface dataset:
Project: Harbor (Provisioning / Container Registry)
File: 9-11-LDAP-user-push-signed-images.md

Test 9-11 User push signed images(LDAP mode) ======= To verify user can sign and push images(LDAP mode) User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server.(authmode is set to ldapauth.) The user data is stored in an LDAP or AD server. A Linux host with Docker CLI(Docker client) installed. Same as Test 9-01 except that users are from LDAP/AD. Same as Test 9-01. None
Project: Beam (App Definition and Development / Streaming & Messaging)
File: tour-of-beam.md

title: "The Tour of Beam" <!-- 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. --> The "Tour of Beam" is an interactive way of learning to write Beam code with a sandbox, where you can write and run pipelines while walking through various concepts. Please to try it out.
Project: StarRocks (App Definition and Development / Database)
File: bitmap_subset_limit.md

displayed_sidebar: "English" Intercepts a specified number of elements from a BITMAP value with element value starting from `start range`. The output elements are a subset of `src`. This function is mainly used for scenarios such as paginated queries. It is supported from v3.1. This function is similar to . The difference is that this function intercepts elements starting from an element value (`startrange`) whereas subbitmap intercepts elements starting from an offset. ```Haskell BITMAP bitmapsubsetlimit(BITMAP src, BIGINT start_range, BIGINT limit) ``` `src`: the BITMAP value from which to obtain elements. `start_range`: the start range to intercept elements. It must be a BIGINT value. If the specified start range exceeds the maximum element of the BITMAP value and `limit` is positive, NULL is returned. See Example 4. `limit`: the number of elements to obtain starting from `start_range`. Negative limits are counted from right to left. If the number of matching elements is less than the value of `limit`, all the matching elements are returned. Returns a value of the BITMAP type. NULL is returned if any of the input parameters is invalid. The subset elements include `start range`. Negative limits are counted from right to left. See example 3. In the following examples, the input of bitmapsubsetlimit() is the output of . For example, `bitmapfromstring('1,1,3,1,5,3,5,7,7,9')` returns `1, 3, 5, 7, 9`. bitmapsubsetlimit() takes this BITMAP value as the input. Example 1: Obtain 4 elements from the BITMAP value with elements values starting from 1. ```Plaintext select bitmaptostring(bitmapsubsetlimit(bitmapfromstring('1,1,3,1,5,3,5,7,7,9'), 1, 4)) value; ++ | value | ++ | 1,3,5,7 | ++ ``` Example 2: Obtain 100 elements from the BITMAP value with elements value starting from 1,. The limit exceeds the length of the BITMAP value and all the matching elements are returned. ```Plaintext select bitmaptostring(bitmapsubsetlimit(bitmapfromstring('1,1,3,1,5,3,5,7,7,9'), 1, 100)) value; +--+ | value | +--+ | 1,3,5,7,9 | +--+ ``` Example 3: Obtain -2 elements from the BITMAP value with elements value starting from 5 (counting from right to left). ```Plaintext select bitmaptostring(bitmapsubsetlimit(bitmapfromstring('1,1,3,1,5,3,5,7,7,9'), 5, -2)) value; +--+ | value | +--+ | 3,5 | +--+ ``` Example 4: The start range 10 exceeds the maximum element of the BITMAP value `1,3,5,7,9` and limit is positive. NULL is returned. ```Plain select bitmaptostring(bitmapsubsetinrange(bitmapfrom_string('1,1,3,1,5,3,5,7,7,9'), 10, 15)) value; +-+ | value | +-+ | NULL | +-+ ```
Project: Daytona (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. Ubuntu 22.04] Daytona Version: [e.g. v0.0.1] Additional context Add any other context about the problem here.
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: pravega-security-encryption.md

<!-- Copyright Pravega Authors. 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. --> Pravega ensures that all the data in flight can be passed by applying encryption. The different can be configured with TLS and encryption can be enabled for them. Pravega expects administrators and users to create and manage certificate creation, deployment and management. Pravega provides various configuration parameters using which certificates for different communication channels can be specified. Pravega uses same certificate to interact with the Controller and Segment Store. The certificates needs to be mentioned specifically on the client and the server machine. Note: These certificates are not loaded from the truststore. Pravega Segment Store uses Apache Bookkeeper as Tier 1 Storage. Apache Bookkeeper supports JKS based truststore. Segment Store uses JKS based truststore to interact with it. See, for more details. Pravega Segment Store and Pravega Controller interact with Apache Zookeeper. These connections can be encrypted based on configuration. The details about the configurations can be found at for and for . Pravega uses Apache BookKeeper as Tier 1 implementation. Apache Bookkeeper currently does not support encryption of data written to disk. Pravega can work with different storage options for Tier 2. To use any specific storage option, it is necessary to implement a storage interface. We currently have the following options implemented: HDFS Extended S3 File system (NFS). Pravega does not encrypt data before storing it in Tier 2. Consequently, Tier 2 encryption is only an option in the case the storage system provides it natively, and as such, needs to be configured directly in the storage system, not via Pravega.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: ISSUE_TEMPLATE.md

Thank you for using RabbitMQ. STOP NOW AND READ THIS before proceeding, or your issue will be moved to Discussions and deleted. Please read https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md and https://github.com/rabbitmq/rabbitmq-server/blob/main/CONTRIBUTING.md#github-issues first. Unless you are certain that you are eligible for community support from the core team, please direct your questions to https://github.com/rabbitmq/rabbitmq-server/discussions and https://rabbitmq.com/discord/. Issues that lack key relevant information, such as RabbitMQ and Erlang versions used The operating system used and its version (distribution) Client library (and any "higher level" libraries or frameworks used) used and their versions Specific and detailed* steps to set up an environment where the behavior can be reproduced will be moved to Discussions and then deleted. RabbitMQ Core Team does use GitHub issues for questions and discussions. Root cause analysis and technical operations guidance will ONLY will provided to those eligible per https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md.
Project: YugabyteDB (App Definition and Development / Database)
File: amazon-dynamodb.md

title: Compare Amazon DynamoDB with YugabyteDB headerTitle: Amazon DynamoDB linkTitle: Amazon DynamoDB description: Compare Amazon DynamoDB with YugabyteDB. aliases: /comparisons/amazon-dynamodb/ menu: preview_faq: parent: comparisons identifier: comparisons-dynamodb weight: 1105 type: docs Amazon DynamoDB is a fully-managed NoSQL database offered by Amazon Web Services. While it works very well for smaller scale applications, the limitations it poses in the context of larger scale applications are not well understood. Our post highlights the above items in better detail. YugabyteDB is an open source database with transactional consistency, low latency, and geo-distribution built into the core of a common storage engine. It is Consistent and Partition-tolerant (CP), and provides native support for JSONB, high performance secondary indexes, cloud-native operational ease, and the ability to handle high data density. Not only is it an excellent alternative to Amazon DynamoDB, it also negates the need for a separate RDBMS and cache. Our post further details the differences between YugabyteDB and DynamoDB.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-update.md

layout: default title: mesheryctl-system-update permalink: reference/mesheryctl/system/update redirect_from: reference/mesheryctl/system/update/ type: reference display-title: "false" language: en command: system subcommand: update Pull new Meshery images/manifest files. Pull new Meshery container images and manifests from artifact repository. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system update [flags] </div> </pre> Pull new Meshery images from Docker Hub. This does not update mesheryctl. This command may be executed while Meshery is running. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system update </div> </pre> Pull the latest manifest files alone <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system update --skip-reset </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for update --skip-reset (optional) skip checking for new Meshery manifest files. </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> Usage of mesheryctl system update Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: CloudARK KubePlus (App Definition and Development / Application Definition & Image Build)
File: README.md

](https://travis-ci.org/kubernetes-sigs/yaml) kubernetes-sigs/yaml is a permanent fork of . A wrapper around designed to enable a better way of handling YAML when marshaling to and from structs. In short, this library first converts YAML to JSON using go-yaml and then uses `json.Marshal` and `json.Unmarshal` to convert to or from the struct. This means that it effectively reuses the JSON struct tags as well as the custom JSON methods `MarshalJSON` and `UnmarshalJSON` unlike go-yaml. For a detailed overview of the rationale behind this method, . This package uses and therefore supports . Caveat #1: When using `yaml.Marshal` and `yaml.Unmarshal`, binary data should NOT be preceded with the `!!binary` YAML tag. If you do, go-yaml will convert the binary data from base64 to native binary data, which is not compatible with JSON. You can still use binary in your YAML files though - just store them without the `!!binary` tag and decode the base64 in your code (e.g. in the custom JSON methods `MarshalJSON` and `UnmarshalJSON`). This also has the benefit that your YAML and your JSON binary data will be decoded exactly the same way. As an example: ``` BAD: exampleKey: !!binary gIGC GOOD: exampleKey: gIGC ... and decode the base64 data in your code. ``` Caveat #2: When using `YAMLToJSON` directly, maps with keys that are maps will result in an error since this is not supported by JSON. This error will occur in `Unmarshal` as well since you can't unmarshal map keys anyways since struct fields can't be keys. To install, run: ``` $ go get sigs.k8s.io/yaml ``` And import using: ``` import "sigs.k8s.io/yaml" ``` Usage is very similar to the JSON library: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) type Person struct { Name string `json:"name"` // Affects YAML field names too. Age int `json:"age"` } func main() { // Marshal a Person struct to YAML. p := Person{"John", 30} y, err := yaml.Marshal(p) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ // Unmarshal the YAML back into a Person struct. var p2 Person err = yaml.Unmarshal(y, &p2) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(p2) /* Output: {John 30} */ } ``` `yaml.YAMLToJSON` and `yaml.JSONToYAML` methods are also available: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) func main() { j := []byte(`{"name": "John", "age": 30}`) y, err := yaml.JSONToYAML(j) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: name: John age: 30 */ j2, err := yaml.YAMLToJSON(y) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(j2)) /* Output: {"age":30,"name":"John"} */ } ```
Project: YugabyteDB (App Definition and Development / Database)
File: array-remove.md

title: array_remove() linkTitle: array_remove() headerTitle: array_remove() description: array_remove() menu: v2.18: identifier: array-remove parent: array-functions-operators type: docs Purpose: Return a new array where every occurrence of the specified value has been removed from the specified input array. Signature: ``` input value: anyarray, anyelement return value: anyarray ``` Note: This function requires the array from which values are to be removed is one-dimensional. This restriction is understood in light of the fact that arrays are rectilinearin other words, the geometry of an array whose dimensionality is two or more is fixed at creation time. For examples illustrating this rule, see . Example: ```plpgsql create table t(k int primary key, arr int[]); insert into t(k, arr) values (1, '{1, 2, 2, 2, 5, 6}'::int[]); select arr as "old value of arr" from t where k = 1; update t set arr = array_remove(arr, 2) where k = 1; select arr as "new value of arr" from t where k = 1; ``` This is the result of the two queries: ``` old value of arr {1,2,2,2,5,6} new value of arr {1,5,6} ```
Project: Pluto (Provisioning / Security & Compliance)
File: code-of-conduct.md

meta: name: description content: "Fairwinds Pluto | Contribution Code of Conduct" In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: ArangoDB (App Definition and Development / Database)
File: inequality_failure_type.md

+++ title = "`bool operator!=(const failure_type<A, void> &) const`" description = "Returns true if this result does not compare equal to the failure type sugar. Constexpr and noexcept propagating." categories = ["comparisons"] weight = 860 +++ Returns true if this result is successful or its error does not compare equal to the error in the failure type sugar. Comparison is done using `operator!=` on `errortype` and `A`. If `A` is `void`, this call aliases {{% api "bool hasvalue() const noexcept" %}}. Requires: `operator!=` must be a valid expression between `errortype` and `A`, or `A` is `void`. If `errortype` is `void`, then so must be `A`. Complexity: Whatever the underlying `operator!=` has. Constexpr and noexcept of underlying operations is propagated. Guarantees: None.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.3-en.md

Websocket listener failed to read headers `X-Forwarded-For` and `X-Forwarded-Port` Deleted `cluster_singleton` from MQTT bridge config document. This config is no longer applicable in 5.0 Fix `emqx/emqx:latest` docker image publish to use the Erlang flavor, but not Elixir flavor Changed the `exp` field in JWT auth to be optional rather than required to fix backwards compatability with 4.X releases. Improve the speed of dashboard's HTTP API routing rule generation, which sometimes causes timeout
Project: ArangoDB (App Definition and Development / Database)
File: building.md

<!-- Copyright 2018 Paul Fultz II Distributed under the Boost Software License, Version 1.0. (http://www.boost.org/LICENSE10.txt) --> Building ======== Boost.HigherOrderFunctions library uses cmake to build. To configure with cmake create a build directory, and run cmake: mkdir build cd build cmake .. Installing To install the library just run the `install` target: cmake --build . --target install Tests -- The tests can be built and run by using the `check` target: cmake --build . --target check The tests can also be ran using Boost.Build, just copy library to the boost source tree, and then: cd test b2 Documentation The documentation is built using Sphinx. First, install the requirements needed for the documentation using `pip`: pip install -r doc/requirements.txt Then html documentation can be generated using `sphinx-build`: sphinx-build -b html doc/ doc/html/ The final docs will be in the `doc/html` folder.
Project: KICS (Provisioning / Security & Compliance)
File: af167837-9636-4086-b815-c239186b9dda.md

title: Cross-Account IAM Assume Role Policy Without ExternalId or MFA hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: af167837-9636-4086-b815-c239186b9dda Query name: Cross-Account IAM Assume Role Policy Without ExternalId or MFA Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Cross-Account IAM Assume Role Policy should require external ID or MFA to protect cross-account access<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" name: Create a role with description and tags community.aws.iam_role: name: mynewrole assumerolepolicy_document: > { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Principal": { "AWS": "arn:aws:iam::987654321145:root" }, "Effect": "Allow", "Resource": "*", "Sid": "" } ] } description: This is My New Role tags: env: dev ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4" name: Create a role with description and tags2 community.aws.iam_role: name: mynewrole2 assumerolepolicy_document: > { "Version": "2012-10-17", "Statement": { "Action": "sts:AssumeRole", "Principal": { "AWS": "arn:aws:iam::987654321145:root" }, "Effect": "Allow", "Resource": "*", "Sid": "", "Condition": { "Bool": { "aws:MultiFactorAuthPresent": "false" } } } } description: This is My New Role tags: env: dev ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="4" name: Create a role with description and tags3 community.aws.iam_role: name: mynewrole3 assumerolepolicy_document: > { "Version": "2012-10-17", "Statement": { "Action": "sts:AssumeRole", "Principal": { "AWS": "arn:aws:iam::987654321145:root" }, "Effect": "Allow", "Resource": "*", "Sid": "", "Condition": { "StringEquals": { "sts:ExternalId": "" } } } } description: This is My New Role tags: env: dev ``` ```yaml title="Negative test num. 1 - yaml file" name: Create a role with description and tags4 community.aws.iam_role: name: mynewrole4 assumerolepolicy_document: > { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Principal": { "AWS": "arn:aws:iam::987654321145:root" }, "Effect": "Allow", "Resource": "*", "Sid": "", "Condition": { "StringEquals": { "sts:ExternalId": "98765" } } } ] } description: This is My New Role tags: env: dev ``` ```yaml title="Negative test num. 2 - yaml file" name: Create a role with description and tags5 community.aws.iam_role: name: mynewrole5 assumerolepolicy_document: > { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Principal": { "AWS": "arn:aws:iam::987654321145:root" }, "Effect": "Allow", "Resource": "*", "Sid": "", "Condition": { "Bool": { "aws:MultiFactorAuthPresent": "true" } } } ] } description: This is My New Role tags: env: dev ```