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

displayed_sidebar: "English" The modulus function that returns the remainder of `dividend` divided by `divisor`. ```SQL mod(dividend, divisor) ``` `dividend`: The number to be divided. `divisor`: The number that divides. Both `dividend` and `divisor` support the following data types: TINYINT SMALLINT INT BIGINT LARGEINT FLOAT DOUBLE DECIMALV2 DECIMAL32 DECIMAL64 DECIMAL128 NOTE `dividend` and `divisor` must agree in the data type. StarRocks performs an implicit conversion if they do not agree in the data type. Returns a value of the same data type as the `dividend`. StarRocks returns NULL if `divisor` is specified as 0. ```Plain mysql> select mod(3.14,3.14); +--+ | mod(3.14, 3.14) | +--+ | 0 | +--+ mysql> select mod(3.14, 3); +--+ | mod(3.14, 3) | +--+ | 0.14 | +--+ select mod(11,-5); ++ | mod(11, -5)| ++ | 1 | ++ select mod(-11,5); +-+ | mod(-11, 5) | +-+ | -1 | +-+ ```
Project: TiDB (App Definition and Development / Database)
File: SECURITY.md

The primary goal of this process is to reduce the total exposure time of users to publicly known vulnerabilities. TiDB security team is responsible for the entire vulnerability management process, including internal communication and external disclosure. If you find a vulnerability or encounter a security incident involving vulnerabilities of this repository, please report it as soon as possible to the TiDB security team (security@tidb.io). Please kindly help provide as much vulnerability information as possible in the following format: Issue title*: Overview*: Affected components and version number*: CVE number (if any): Vulnerability verification process*: Contact information*: The asterisk (*) indicates the required field. The TiDB security team will confirm the vulnerabilities and contact you within 2 working days after your submission. We will publicly thank you after fixing the security vulnerability. To avoid negative impact, please keep the vulnerability confidential until we fix it. We would appreciate it if you could obey the following code of conduct: The vulnerability will not be disclosed until a patch is released for it. The details of the vulnerability, for example, exploits code, will not be disclosed.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: oneget.md

+++ title = "oneget resource" draft = false gh_repo = "inspec" platform = "windows" [menu] [menu.inspec] title = "oneget" identifier = "inspec/resources/os/oneget.md oneget resource" parent = "inspec/resources/os" +++ Use the `oneget` Chef InSpec audit resource to test if the named package and/or package version is installed on the system. This resource uses Oneget, which is `part of the Windows Management Framework 5.0 and Windows 10 <https://github.com/OneGet/oneget>`. This resource uses the `Get-Package` cmdlet to return all of the package names in the Oneget repository. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `oneget` resource block declares a package and (optionally) a package version: describe oneget('name') do it { should be_installed } end where `('name')` must specify the name of a package, such as `'VLC'` `be_installed` is a valid matcher for this resource The `version` property tests if the named package version is on the system: its('version') { should eq '1.2.3' } The following examples show how to use this Chef InSpec audit resource. describe oneget('VLC') do it { should be_installed } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `be_installed` matcher tests if the named package is installed on the system: it { should be_installed }
Project: StarRocks (App Definition and Development / Database)
File: tasks.md

displayed_sidebar: "English" `tasks` provides information about asynchronous tasks. The following fields are provided in `tasks`: | Field | Description | | -- | | | TASK_NAME | Name of the task. | | CREATE_TIME | Time when the task was created. | | SCHEDULE | Task schedule. If the task is regularly triggered, this field displays `START xxx EVERY xxx`. | | DATABASE | Database where the task belongs. | | DEFINITION | SQL definition of the task. | | EXPIRE_TIME | Time when the task expires. |
Project: openGauss (App Definition and Development / Database)
File: CONTRIBUTING.md

A great way to contribute to the project is to send a detailed report when you encounter an issue. We always appreciate a well-written, thorough bug report and feature propose, and will appreciate you for it! When reporting issues, refer to this format: Is this a BUG REPORT or FEATURE REQUEST? What happened? What you expected to happen? What happened? How to reproduce it (as minimally and precisely as possible) Anything else we need to know? Environment See more about . If you are a beginner and expect this project as the gate to open source world, this tutorial is one of the best choices for you. Just follow the guidance and you will find the pleasure to become a contributor. Before making modifications of this project, you need to make sure that this project have been forked to your own repository. It means that there will be parallel development between this repo and your own repo, so be careful to avoid the inconsistency between these two repos. If you want to download the code to the local machine, ```git``` is the best way: ``` git clone https://yourrepourl/community.git ``` To avoid inconsistency between multiple branches, we SUGGEST checking out to a new branch: ``` git checkout -b newbranchname origin/master ``` Then you can change the code arbitrarily. After updating the code, you should push the update in the formal way: ``` git add . git status (Check the update status) git commit -m "Your commit description" git commit --amend (Add the concrete description of your commit) git push origin newbranchname ``` In the last step, your need to pull a compare request between your new branch and development branch. After finishing the pull request, the CI will be automatically set up for building test. When submitting pull requests, refer to this format: What this PR does / why we need it? Which issue this PR fixes? Special notes for your reviewer Release note See more about . ```TO BE DEFINED```
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_ECS_ContainerInstance.md

The following is a sample class and Lambda function that receives Amazon ECS Container instance state change events record data as an input and writes some of the record data to CloudWatch Logs. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go package main import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" ) func handler(ctx context.Context, ecsEvent events.ECSContainerInstanceEvent) { outputJSON, _ := json.MarshalIndent(ecsEvent, "", " ") fmt.Printf("Data = %s", outputJSON) } func main() { lambda.Start(handler) } ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.6.4.44-stable.md

Backported in : Fix data race in `lgamma` function. This race was caught only in `tsan`, no side effects a really happened. (). Backported in : Fix access to redis dictionary after connection was dropped once. It may happen with `cache` and `direct` dictionary layouts. (). Backported in : Fix parsing row policies from users.xml when names of databases or tables contain dots. This fixes , . (). Backported in : AvroConfluent: Skip Kafka tombstone records AvroConfluent: Support skipping broken records ... (). Backported in : Return passed number for numbers with MSB set in roundUpToPowerOfTwoOrZero(). (). Backported in : Fix queries with constant columns and `ORDER BY` prefix of primary key. (). Backported in : Fix empty output for `Arrow` and `Parquet` formats in case if query return zero rows. It was done because empty output is not valid for this formats. (). Backported in : Fix possible race in `StorageMemory`. https://clickhouse-test-reports.s3.yandex.net/0/9cac8a7244063d2092ad25d45502611e18d3749c/stresstest(thread)/stderr.log Have no idea how to write a test. (). Backported in : Fix invalid return type for comparison of tuples with `NULL` elements. Fixes . (). Backported in : Fix error in `parseDateTimeBestEffort` function when unix timestamp was passed as an argument. This fixes . (). Backported in : Fix secondary indices corruption in compact parts. (). Backported in : Concurrent `ALTER ... REPLACE/MOVE PARTITION ...` queries might cause deadlock. It's fixed. (). Backported in : Fix crash in JOIN with StorageMerge and `set enableoptimizepredicate_expression=1`. (). Backported in : Do not optimize any(arrayJoin()) -> arrayJoin() under optimizemovefunctionsoutof_any. (). Backported in : Fix incorrect message in `clickhouse-server.init` while checking user and group. (). Backported in : Fix incorrect sorting for `FixedString` columns. Fixes . ().
Project: KICS (Provisioning / Security & Compliance)
File: 265d9725-2fb8-42a2-bc57-3279c5db82d5.md

title: Lambda Function Without Tags hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 265d9725-2fb8-42a2-bc57-3279c5db82d5 Query name: Lambda Function Without Tags Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: AWS Lambda Functions must have associated tags.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2" name: add tags community.aws.lambda: name: 'Lambda function' state: present zip_file: 'code.zip' runtime: 'python2.7' role: 'arn:aws:iam::987654321012:role/lambdabasicexecution' handler: 'hellopython.myhandler' ``` ```yaml title="Negative test num. 1 - yaml file" name: add tags community.aws.lambda: name: 'Lambda function' state: present zip_file: 'code.zip' runtime: 'python2.7' role: 'arn:aws:iam::987654321012:role/lambdabasicexecution' handler: 'hellopython.myhandler' tags: key1: 'value1' ```
Project: Kyverno (Provisioning / Security & Compliance)
File: logging.md

Logging is done using `logging` package in the codebase. The logger relies on sigs.k8s.io/controller-runtime/pkg/log that provides methods to define logs. Default log level is 2. Can be modified by adding command-line argument `-v=<level_int>`. The `globalLog` variable in logging package is a reference to logr.Logger from controller-runtime/pkg/log. :warning: Initially, call depth applied to the logger do not get set. When logging.Setup is called in main, globalLog is switched to the real logger, in turn, all loggers created after logging.Setup won't be subject to the call depth limitation and will work if the underlying sink supports it. ``` WithName: logging.WithName("setup") : adds "setup" as prefix. WithValues: logging.WithValues("key","value") : adds key-value pairs. ControllerLogger: logging.ControllerLogger("name") : creates a logger to be used by controllers. it sets a log level of 3. ``` ``` logging.Error(err,"failed due to this error","key","value") ``` Prints the stack trace where the error was defined for more details. There are no methods for fatal, os.Exit() needs to be called by the caller. Info: ``` logging.Info("information message","key","value") logging.V(4).Info("level log4","log_level","4") : prints the log information based on the defined verbosity. ```
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: builder_overview.md

+++ title = "About Chef Habitat Builder" description = "Chef Habitat Builder is Chef's Application Delivery Enterprise hub" gh_repo = "habitat" aliases = ["/habitat/using-builder/"] [menu] [menu.habitat] title = "Chef Habitat Builder" identifier = "habitat/builder/builder" parent = "habitat/builder" weight = 10 +++ Chef Habitat Builder acts as the core of Chef's Application Delivery Enterprise hub. Chef Habitat Builder was first launched as a cloud service and as the repository of all available plan templates built by Chef and the supporting community. Due to the fact that the application source code is stored alongside the build package, many users expressed a preference for storing packages and running Chef Habitat Builder on-prem. As a result, Chef Habitat Builder can be consumed either as a cloud based or on-premises solution. Plan files are stored in the Chef Habitat Builder SaaS, where they can be viewed and accessed by the Chef Habitat community and then shared with the on-premises version of the builder where they can then be copied and maintained locally. Application Manifest* - The Application Manifest provides a single application directory, which includesat a minimumthe compiled app artifact, dynamic links to all direct and transitive runtime dependencies ,and instructions to install and run the app. Deployment Channel Management* - Pre-canned deployment channels that can be used as-is or a user can custom design their own channels. Apps that are deployed through Chef Habitat can subscribe to a channel and be auto-upgraded whenever the app is promoted. Origin Management* - Save your application delivery content in uniquely named spaces that you can control. Content Library* - Hundreds of pre-built and core dependencies, which makes it easy to get started with Chef Habitat. Custom Data and Reporting APIs* - Rich APIs enable the capability to export to CSV or JSON. DevOps Integration APIs* - Provides an API so that clients can find and download the necessary packages to run their applications. Additional APIs also enable easy integration with other popular DevOps tools, including Jenkins, Terraform, Artifactory, Hashi Vault, and many others. Role Based User Access* - Improves your organizations operational safety by letting you assign specific levels of access to each origin member. For more information on how the SaaS and On-Prem versions of Chef Habitat Builder work together, read the blog -
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Paimon.md

Paimon source connector Read data from Apache Paimon. | name | type | required | default value | |-|--|-|| | warehouse | String | Yes | - | | database | String | Yes | - | | table | String | Yes | - | | hdfssitepath | String | No | - | Paimon warehouse path The database you want to access The table you want to access The file path of `hdfs-site.xml` ```hocon source { Paimon { warehouse = "/tmp/paimon" database = "default" table = "st_test" } } ``` Add Paimon Source Connector
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-rename.1.md

% podman-rename 1 podman\-rename - Rename an existing container podman rename container newname podman container rename container newname Rename changes the name of an existing container. The old name is freed, and is available for use. This command can be run on containers in any state. However, running containers may not fully receive the effects until they are restarted - for example, a running container may still use the old name in its logs. At present, only containers are supported; pods and volumes cannot be renamed. Rename container with a given name. ``` $ podman rename oldContainer aNewName ``` Rename container with a given ID. ``` $ podman rename 717716c00a6b testcontainer ``` Create an alias for container with a given ID. ``` $ podman container rename 6e7514b47180 databaseCtr ```
Project: Flink (App Definition and Development / Streaming & Messaging)
File: state.md

title: "State" weight: 31 type: docs aliases: /docs/dev/python/datastream/state.html <!-- 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. --> <meta http-equiv="refresh" content="0; url={{< ref "docs/dev/datastream/fault-tolerance/state" >}} "/>
Project: KUDO (App Definition and Development / Application Definition & Image Build)
File: 0003-kep-cli.md

kep-number: 3 title: KEP CLI Proposal short-desc: Initial CLI description authors: "@fabianbaier" owners: "@fabianbaier" editor: TBD creation-date: 2019-02-14 last-updated: 2019-02-20 status: implementable * * * * * * * * * * * This KEP aims to improve the end user experience via a CLI that makes the life of an operator easier. Right now, interacting with KUDO consists of a chain of cumbersome steps that require specific business logic. By providing one global entry point for the user (e.g. to install or interact with operators, get the status of current plans etc.) we can abstract complexity from the user and drive adaptation. Currently, installing your `Operators` requires not just the proper configuration of your YAML files but also multiple interactions with `kubectl`. Having CLI tooling to simplify the path for cluster operators to deployment and maintenance of installed `Operators` adds not just value across the community but also helps implementing best practices when using KUDO. The goal of this KEP is to have a CLI binary that can be used under the Kubectl Plugin System to work with KUDO. We should drive making the adaption to KUDO easier Not to confuse flags Providing metrics for usage and error reporting Non-Goals are: Just building another wrapper around `kubectl` Adding complexity This is where we get down to the nitty gritty of what the proposal actually is. As a user I want to be able to install an operator to my cluster. As a user I want to be able to uninstall an operator from my cluster. As a user I want to be able to list current installed operators in my namespace. As a user I want to be able to get the status of all plans of an Instance. As a user I want to be able to trigger specific plans of an Instance. As a user I want to be able to audit the trail of executed plans. As a user I want to be able to execute into my Instance environment. As an application operator, I want to be able to run CLI tooling, built for the Operator against an Instance. As a user I want to be able to get a shell to a specific operator. As a user I want to be able to read logs to a specific operator and its components. Some caveats: Airgapped clusters Application logic with extra plugins for specific operators To be continued... TBD If we see adoption in the community. TBD
Project: KICS (Provisioning / Security & Compliance)
File: 8c3bedf1-c570-4c3b-b414-d068cd39a00c.md

title: AKS Network Policy Misconfigured hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8c3bedf1-c570-4c3b-b414-d068cd39a00c Query name: AKS Network Policy Misconfigured Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Azure Kubernetes Service should have the proper network policy configuration to ensure the principle of least privileges, which means that 'networkprofile.networkpolicy' should be defined<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="24 10" name: Create a managed Azure Container Services (AKS) instance03 azurermaks: name: myAKS location: eastus resource_group: myResourceGroup dns_prefix: akstest kubernetes_version: 1.14.6 network_profile: network_policy: istio linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: "cf72ca99-f6b9-4004-b0e0-bee10c521948" client_secret: "Password123!" agentpoolprofiles: name: default count: 5 vmsize: StandardD2_v2 tags: Environment: Production name: Create a managed Azure Container Services (AKS) instance04 azurermaks: name: myAKS location: eastus resource_group: myResourceGroup dns_prefix: akstest kubernetes_version: 1.14.6 linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: "cf72ca99-f6b9-4004-b0e0-bee10c521948" client_secret: "Password123!" agentpoolprofiles: name: default count: 5 vmsize: StandardD2_v2 tags: Environment: Production ``` ```yaml title="Negative test num. 1 - yaml file" name: Create a managed Azure Container Services (AKS) instance01 azurermaks: name: myAKS location: eastus resource_group: myResourceGroup dns_prefix: akstest kubernetes_version: 1.14.6 network_profile: network_policy: calico linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: cf72ca99-f6b9-4004-b0e0-bee10c521948 client_secret: Password123! agentpoolprofiles: name: default count: 5 vmsize: StandardD2_v2 tags: Environment: Production name: Create a managed Azure Container Services (AKS) instance02 azurermaks: name: myAKS location: eastus resource_group: myResourceGroup dns_prefix: akstest kubernetes_version: 1.14.6 network_profile: network_policy: azure linux_profile: admin_username: azureuser ssh_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA... service_principal: client_id: cf72ca99-f6b9-4004-b0e0-bee10c521948 client_secret: Password123! agentpoolprofiles: name: default count: 5 vmsize: StandardD2_v2 tags: Environment: Production ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: googleplay.md

title: "Google Play" icon: /images/logos/powered-by/googleplay.png hasLink: "https://play.google.com/" <!-- 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. -->