cwielenb/CNCF-Dataset huggingface dataset:
Project: Koperator (App Definition and Development / Streaming & Messaging)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, 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 within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. 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 . 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 01_basic_learning_apache_beam.md

Prompt: What is Apache Beam? Response: Apache Beam is an open-source unified programming model for data processing pipelines. It provides a set of language-specific SDKs that allow you to define and execute data processing workflows. Apache Beam allows you to write pipelines in one of the supported languages (Java, Python, Go, and Scala). The pipelines can be executed on one of the supported runners (Apache Flink, Apache Spark, and Google Cloud Dataflow). Learning Apache Beam is a valuable skill for data processing and analysis. Here are some resources to get you started: section of the Apache Beam website is a perfect place to start. It provides an overview of Apache Beam and its key concepts. For a hands-on introduction, you can start by exploring the , which demonstrates the basic concepts of Apache Beam. The is an interactive tour that teaches you core Beam concepts. It provides a sandbox environment to write and run pipelines while exploring different topics. The offers an interactive space to experiment with Beam's transforms and examples without installing anything on your system. After you have a basic understanding of Apache Beam, you can start to build your own pipelines. The Apache Beam website has a number of resources that can help you get started, including , and . For those interested in the source code, you can explore the on GitHub. By leveraging these resources, you can build a strong foundation in Apache Beam and start constructing your own data processing pipelines. Additionally, Apache Beam is an open-source project, and contributions are welcome. Whether you're fixing bugs, improving documentation, or adding new features, your work can benefit the entire Beam community. To learn more about how you can contribute, visit the section of the Apache Beam website.
Project: KICS (Provisioning / Security & Compliance)
File: 6c7cfec3-c686-4ed2-bf58-a1ec054b63fc.md

title: Redis Cache Allows Non SSL Connections hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6c7cfec3-c686-4ed2-bf58-a1ec054b63fc Query name: Redis Cache Allows Non SSL Connections Platform: Crossplane Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Redis Cache resource should not allow non-SSL connections.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="14" apiVersion: cache.azure.crossplane.io/v1beta1 kind: Redis metadata: name: azureRedis3 spec: providerConfigRef: name: crossplane-azure forProvider: location: West Europe sku: name: Basic family: C capacity: 0 enableNonSslPort: true ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: cache.azure.crossplane.io/v1beta1 kind: Redis metadata: name: azureRedis spec: providerConfigRef: name: crossplane-azure forProvider: location: West Europe sku: name: Basic family: C capacity: 0 enableNonSslPort: false apiVersion: cache.azure.crossplane.io/v1beta1 kind: Redis metadata: name: azureRedis2 spec: providerConfigRef: name: crossplane-azure forProvider: location: West Europe sku: name: Basic family: C capacity: 0 ```
Project: SPIRE (Provisioning / Key Management)
File: telemetry_config.md

If telemetry is desired, it may be configured by using a dedicated `telemetry { ... }` section. The following metrics collectors are currently supported: Prometheus Statsd DogStatsd M3 In-Memory You may use all, some, or none of the collectors. The following collectors support multiple declarations in the event that you want to send metrics to more than one collector: Statsd DogStatsd M3 | Configuration | Type | Description | Default | |--|||--| | `InMem` | `InMem` | In-memory configuration | running | | `Prometheus` | `Prometheus` | Prometheus configuration | | | `DogStatsd` | `[]DogStatsd` | List of DogStatsd configurations | | | `Statsd` | `[]Statsd` | List of Statsd configurations | | | `M3` | `[]M3` | List of M3 configurations | | | `MetricPrefix` | `string` | Prefix to add to all emitted metrics | spireserver/spireagent | | `EnableHostnameLabel` | `bool` | Enable adding hostname to labels | true | | `AllowedPrefixes` | `[]string` | A list of metric prefixes to allow, with '.' as the separator | | | `AllowedPrefixes` | `[]string` | A list of metric prefixes to allow, with '.' as the separator | | | `BlockedPrefixes` | `[]string` | A list of metric prefixes to block, with '.' as the separator | | | `AllowedLabels` | `[]string` | A list of metric labels to allow, with '.' as the separator | | | `BlockedLabels` | `[]string` | A list of metric labels to block, with '.' as the separator | | | Configuration | Type | Description | ||-|| | `host` | `string` | Prometheus server host | | `port` | `int` | Prometheus server port | | Configuration | Type | Description | ||-|-| | `address` | `string` | DogStatsd address | | Configuration | Type | Description | ||-|-| | `address` | `string` | Statsd address | | Configuration | Type | Description | ||-|-| | `address` | `string` | M3 address | | `env` | `string` | M3 environment, e.g. `production`, `staging` | Here is a sample configuration: ```hcl telemetry { Prometheus { port = 9988 } DogStatsd = [ { address = "localhost:8125" }, ] Statsd = [ { address = "localhost:1337" }, { address = "collector.example.org:8125" }, ] M3 = [ { address = "localhost:9000" env = "prod" }, ] InMem {} AllowedLabels = [] BlockedLabels = [] AllowedPrefixes = [] BlockedPrefixes = [] } ``` See the for a list of all the supported metrics.
Project: StarRocks (App Definition and Development / Database)
File: isnull.md

displayed_sidebar: "English" Checks whether the value is `NULL`, returns `1` if it is `NULL`, and returns `0` if it is not `NULL`. ```Haskell ISNULL(v) ``` `v`: the value to check. All date types is supported. Returns 1 if it is `NULL`, and returns 0 if it is not `NULL`. ```plain text MYSQL > SELECT c1, isnull(c1) FROM t1; ++--+ | c1 | `c1` IS NULL | ++--+ | NULL | 1 | | 1 | 0 | ++--+ ```
Project: YugabyteDB (App Definition and Development / Database)
File: end.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="232" height="70" viewbox="0 0 232 70"><path class="connector" d="M0 22h15m46 0h30m106 0h20m-136 25q0 5 5 5h5m57 0h54q5 0 5-5m-131-25q5 0 5 5v33q0 5 5 5h116q5 0 5-5v-33q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="46" height="25" rx="7"/><text class="text" x="25" y="22">END</text><rect class="literal" x="91" y="5" width="106" height="25" rx="7"/><text class="text" x="101" y="22">TRANSACTION</text><rect class="literal" x="91" y="35" width="57" height="25" rx="7"/><text class="text" x="101" y="52">WORK</text><polygon points="228,29 232,29 232,15 228,15" style="fill:black;stroke-width:0"/></svg>
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.20.md

RabbitMQ `3.7.20` is a maintenance release that focuses on bug fixes. RabbitMQ `3.7.x` series is supported . Per the new Erlang version support policy in effect starting with January 2019, this release . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . Rolling cluster upgrade could fail if new versions were deployed to all cluster nodes at once instead of a rolling upgrade-then-restart for each node individually. GitHub issue: Improved error handling in a module that continuously registers the node with avoids log noise. GitHub issue: `rabbitmqctl await_startup` failed with an exception when effective timeout was set to `infinity`. GitHub issue: `rabbitmq-diagnostics checkportconnectivity` produced a false positive in an IPv6-only environment. Contributed by Gabriele Santomaggio. GitHub issue: `rabbitmq-diagnostics status`, `rabbitmq-diagnostics cluster_status`, `rabbitmq-diagnostics listeners` now support `--formatter=erlang` (raw Erlang data structure output) GitHub issue: Requests to Kubernetes API endpoints failed with an `nxdomain` (domain name resolution failure) in an IPv6-only environment. Now the plugin will configure its HTTP[S] client to use IPv6 if the tells it to. See to learn more. GitHub issue: The plugin will now configure its HTTP[S] client to use IPv6 if the tells it to. See to learn more. GitHub issue: It is now possible to specify service metadata values: ``` ini clusterformation.consul.svcmeta.key1 = value1 clusterformation.consul.svcmeta.key2 = value2 ``` GitHub issue: The plugin will now configure its HTTP[S] client to use IPv6 if the tells it to. See to learn more. GitHub issue: The plugin will now configure its HTTP[S] client to use IPv6 if the tells it to. See to learn more. GitHub issue: Connection could not be restarted after a heartbeat timeout due to strict pattern matching. Contributed by Giuseppe D'Anna (@larrywax). GitHub issue: The plugin will no log a warning when DN lookup settings are incomplete. GitHub issue: On Windows, deleting the file used by an active (running) trace resulted in an `EACCES` exception. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.20.tar.xz`.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.1.md

RabbitMQ `3.9.1` is a maintenance release in the `3.9.x` release series. . Please refer to the Upgrading to 3.9 section from if you are upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.0.5 at the time of release. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Clients that used global QoS prefetch (deprecated as of 3.9.0) ran into an exception when acknowledging deliveries. GitHub issue: Improved resiliency of stream coordinator in certain conditions. GitHub issues: , Nodes failed to start when hostname contained non-ASCII (broader Unicode) characters. GitHub issue: `rabbitmq-diagnostics stream_status` fails with an exception when the `--tracking` option was used. GitHub issue: `rabbitmq-diagnostics stream_status` used an outdated documentation guide link. GitHub issue: New releases of the client are again published to Hex.pm. GitHub issue: `connection_timeout` was adjusted to avoid a confusing warning. GitHub issue: contributed by @britto Corrected a typo in direct connection net tick time adjustment. GitHub issue: contributed by @britto No dependency changes in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.1.tar.xz` instead of the source tarball produced by GitHub.
Project: ArangoDB (App Definition and Development / Database)
File: set_has_error.md

+++ title = "`static void sethas_error(Impl &&, bool) noexcept`" description = "Sets whether the implementation has an error. Constexpr, never throws." categories = ["modifiers"] weight = 310 +++ Sets whether the implementation has an error by setting or clearing the relevant bit in the flags. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: ClickHouse (App Definition and Development / Database)
File: revoke.md

slug: /en/sql-reference/statements/revoke sidebar_position: 39 sidebar_label: REVOKE Revokes privileges from users or roles. Revoking privileges from users ``` sql REVOKE [ON CLUSTER clustername] privilege[(columnname [,...])] [,...] ON {db.table|db.|.|table|} FROM {user | CURRENTUSER} [,...] | ALL | ALL EXCEPT {user | CURRENTUSER} [,...] ``` Revoking roles from users ``` sql REVOKE [ON CLUSTER clustername] [ADMIN OPTION FOR] role [,...] FROM {user | role | CURRENTUSER} [,...] | ALL | ALL EXCEPT {username | rolename | CURRENT_USER} [,...] ``` To revoke some privilege you can use a privilege of a wider scope than you plan to revoke. For example, if a user has the `SELECT (x,y)` privilege, administrator can execute `REVOKE SELECT(x,y) ...`, or `REVOKE SELECT * ...`, or even `REVOKE ALL PRIVILEGES ...` query to revoke this privilege. You can revoke a part of a privilege. For example, if a user has the `SELECT .` privilege you can revoke from it a privilege to read data from some table or a database. Grant the `john` user account with a privilege to select from all the databases, excepting the `accounts` one: ``` sql GRANT SELECT ON . TO john; REVOKE SELECT ON accounts.* FROM john; ``` Grant the `mira` user account with a privilege to select from all the columns of the `accounts.staff` table, excepting the `wage` one. ``` sql GRANT SELECT ON accounts.staff TO mira; REVOKE SELECT(wage) ON accounts.staff FROM mira; ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_sysbench_cleanup.md

title: kbcli bench sysbench cleanup Cleanup the data of SysBench for cluster ``` kbcli bench sysbench cleanup [ClusterName] [flags] ``` ``` kbcli bench sysbench cleanup mycluster --user xxx --password xxx --database mydb kbcli bench sysbench cleanup mycluster --user xxx --password xxx --database mydb --tables 10 --size 25000 ``` ``` -h, --help help for cleanup ``` ``` --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 --database string database name --disable-compression If true, opt-out of response compression for all requests to the server --flag int the flag of sysbench, 0(normal), 1(long), 2(three nodes) --host string the host of database --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 --password string the password of database --port int the port of database --read-percent int the percent of read, only useful when type is oltpreadwrite_pct --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 --size int the data size of per table (default 25000) --tables int the number of tables (default 10) --threads ints the number of threads, you can set multiple values, like 4,8 (default [4]) --times int the number of test times (default 60) --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 --type strings sysbench type, you can set multiple values (default [oltpreadwrite]) --user string the user of database --write-percent int the percent of write, only useful when type is oltpreadwrite_pct ``` - run a SysBench benchmark
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_use_provider.md

title: "Command - devspace use provider" sidebar_label: devspace use provider Change the default provider ``` devspace use provider [flags] ``` ``` Use a specific cloud provider as default for future commands Example: devspace use provider my.domain.com ``` ``` -h, --help help for provider ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: code-of-conduct.md

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Examples of unacceptable behavior by participants include: The use of sexualized language or imagery Personal attacks Trolling or insulting/derogatory comments Public or private harassment Publishing others' private information, such as physical or electronic addresses, without explicit permission Other unethical or unprofessional conduct. 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. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a project maintainer or the Operator SDK team <aos-operator-sdk@redhat.com>. This Code of Conduct is adapted from the Contributor Covenant (http://contributor-covenant.org), version 1.2.0, available at http://contributor-covenant.org/version/1/2/0/ Red Hat events are working conferences intended for professional networking and collaboration in the Red Hat community. Attendees are expected to behave according to professional standards and in accordance with their employers policies on appropriate workplace behavior. While at Red Hat events or related social networking opportunities, attendees should not engage in discriminatory or offensive speech or actions including but not limited to gender, sexuality, race, age, disability, or religion. Speakers should be especially aware of these concerns. Red Hat does not condone any statements by speakers contrary to these standards. Red Hat reserves the right to deny entrance and/or eject from an event (without refund) any individual found to be engaging in discriminatory or offensive speech or actions. Please bring any concerns to the immediate attention of designated on-site staff, or the Operator SDK team <aos-operator-sdk@redhat.com>.