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

Copyright 2016-2023 Dgraph Labs, Inc. Source code in this repository is variously licensed under the Apache Public License 2.0 (APL) and the Dgraph Community License (DCL). A copy of each license can be found in the directory. 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. Dgraph is a registered trademark of Dgraph Labs, Inc.
Project: KICS (Provisioning / Security & Compliance)
File: 7af1c447-c014-4f05-bd8b-ebe3a15734ac.md

title: SQL Analysis Services Port 2383 (TCP) Is Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7af1c447-c014-4f05-bd8b-ebe3a15734ac Query name: SQL Analysis Services Port 2383 (TCP) Is Publicly Accessible Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Check if port 2383 on TCP is publicly accessible by checking the CIDR block range that can access it.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="65 37 9 51 23" name: example using security group rule descriptions amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: "{{ aws_profile }}" region: us-east-1 rules: proto: tcp ports: 2383 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 name: example using security group rule descriptions 2 amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: "{{ aws_profile }}" region: us-east-1 rules: proto: tcp ports: 2383 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 name: example using security group rule descriptions 3 amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: "{{ aws_profile }}" region: us-east-1 rules: proto: tcp to_port: -1 from_port: -1 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 name: example using security group rule descriptions 4 amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: "{{ aws_profile }}" region: us-east-1 rules: proto: tcp ports: 2000-3000 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 name: example using security group rule descriptions 5 amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: "{{ aws_profile }}" region: us-east-1 rules: proto: tcp to_port: 3000 from_port: 2000 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 ``` ```yaml title="Negative test num. 1 - yaml file" name: example using security group rule descriptions amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: '{{ aws_profile }}' region: us-east-1 rules: proto: tcp ports: 2383 cidrip: awsvpc.main.cidr_block rule_desc: allow all on port 2383 name: example using security group rule descriptions 2 amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: '{{ aws_profile }}' region: us-east-1 rules: proto: udp ports: 2383 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 name: example using security group rule descriptions 3 amazon.aws.ec2_group: name: awsEc2 description: sg with rule descriptions vpc_id: vpc-xxxxxxxx profile: '{{ aws_profile }}' region: us-east-1 rules: proto: tcp to_port: 4000 from_port: 3000 cidr_ip: 0.0.0.0/0 rule_desc: allow all on port 2383 ```
Project: mirrord (App Definition and Development / Application Definition & Image Build)
File: STYLE.md

When naming Senders and Receivers, use `atx` and `brx` respectively - where `a` is the thing the Sender is sending, and `b` is the thing Receiver is receiving. E.g. `agentmessagetx`, `httpresponserx`. Document above the declaration of the variable/struct member whats being sent from where to where. Suggested format: `<src> --<what's being sent>> <dst>`. Example: `/// HTTP client task -IDs of closed connections-> TcpStealHandler` If known, the meaning of the objects being sent is documented, not just their type. Dont use local in naming in agent code, since it could be unclear if its local to the agent, or to the users system. Instead, use agent, cluster, pod, container, layer, user_application to specify where this item is local to. When using `unwrap` or `expect`, always explain why its ok to do so in a comment (except for in tests obviously). Only use `Option`s where it is valid to have a `None`. Avoid passing around `Option`s that are expected to always be `Some`, and hold the inner value instead as early as possible. That way, developers don't have to make sure that the `Option` that is expected to be `Some` is not `None` at later points along the run. Also, the code is easier to read this way: you don't have to somehow know that an `Option` is expected to never be `None` in order to understand the code.
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Creating-a-new-Storm-project.md

title: Creating a New Storm Project layout: documentation documentation: true This page outlines how to set up a Storm project for development. The steps are: Add Storm jars to classpath If using multilang, add multilang dir to classpath Follow along to see how to set up the project in Eclipse. You'll need the Storm jars on your classpath to develop Storm topologies. Using is highly recommended. of how to setup your pom.xml for a Storm project. If you don't want to use Maven, you can include the jars from the Storm release on your classpath. To set up the classpath in Eclipse, create a new Java project, include `src/jvm/` as a source path, and make sure all the jars in `lib/` and `lib/dev/` are in the `Referenced Libraries` section of the project. If you implement spouts or bolts in languages other than Java, then those implementations should be under the `multilang/resources/` directory of the project. For Storm to find these files in local mode, the `resources/` dir needs to be on the classpath. You can do this in Eclipse by adding `multilang/` as a source folder. You may also need to add multilang/resources as a source directory. For more information on writing topologies in other languages, see . To test that everything is working in Eclipse, you should now be able to `Run` the `WordCountTopology.java` file. You will see messages being emitted at the console for 10 seconds.
Project: YDB (App Definition and Development / Database)
File: table-attribute-add.md

With the `table attribute add` command, you can add a to your table. General format of the command: ```bash {{ ydb-cli }} [global options...] table attribute add [options...] <table path> ``` `global options`: . `options`: . `table path`: The table path. Look up the description of the command to add a custom attribute: ```bash {{ ydb-cli }} table attribute add --help ``` | Name | Description | | | `--attribute` | The custom attribute in the `<key>=<value>` format. You can use `--attribute` many times to add multiple attributes by a single command. | Add the custom attributes with the keys `attrkey1`, `attrkey2` and the respective values `attrvalue1`, `attrvalue2` to the `my-table` table: ```bash {{ ydb-cli }} table attribute add --attribute attrkey1=attrvalue1 --attribute attrkey2=attrvalue2 my-table ```
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Operations_Broker.md

Broker Role is ASYNCMASTER, SYNCMASTER or SLAVE. If you cannot tolerate message missing, we suggest you deploy SYNCMASTER and attach a SLAVE to it. If you feel ok about missing, but you want the Broker to be always available, you may deploy ASYNCMASTER with SLAVE. If you just want to make it easy, you may only need a ASYNC_MASTER without SLAVE. ASYNCFLUSH is recommended, for SYNCFLUSH is expensive and will cause too much performance loss. If you want reliability, we recommend you use SYNC_MASTER with SLAVE. | Parameter name | Default | Description | | -- | -- | | | listenPort | 10911 | listen port for client | | namesrvAddr | null | name server address | | brokerIP1 | InetAddress for network interface | Should be configured if having multiple addresses | | brokerIP2 | InetAddress for network interface | If configured for the Master broker in the Master/Slave cluster, slave broker will connect to this port for data synchronization | | brokerName | null | broker name | | brokerClusterName | DefaultCluster | this broker belongs to which cluster | | brokerId | 0 | broker id, 0 means master, positive integers mean slave | | storePathCommitLog | $HOME/store/commitlog/ | file path for commit log | | storePathConsumerQueue | $HOME/store/consumequeue/ | file path for consume queue | | mappedFileSizeCommitLog | 1024 1024 1024(1G) | mapped file size for commit log | | deleteWhen | 04 | When to delete the commitlog which is out of the reserve time | | fileReserverdTime | 72 | The number of hours to keep a commitlog before deleting it | | brokerRole | ASYNCMASTER | SYNCMASTER/ASYNC_MASTER/SLAVE | | flushDiskType | ASYNCFLUSH | {SYNCFLUSH/ASYNCFLUSH}. Broker of SYNCFLUSH mode flushes each message onto disk before acknowledging producer. Broker of ASYNC_FLUSH mode, on the other hand, takes advantage of group-committing, achieving better performance. |
Project: CFEngine (Provisioning / Automation & Configuration)
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 other's 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 Member project maintainer or <contact@cfengine.com>.
Project: SPIFFE (Provisioning / Key Management)
File: DANIEL_FELDMAN.md

I've worked on SPIFFE-related projects for about 5 years and have helped deployments at several large companies. I've hosted the SIG-SPIRE biweekly show-and-tell for SPIFFE projects since 2020. I'm hoping to continue to grow the project and build a stronger community. GitHub Handle: @dfeldman Email Address: dfeldman.mn@gmail.com LinkedIn Profile: linkedin.com/in/dfeldman Current Affiliation: Independent consulting
Project: CockroachDB (App Definition and Development / Database)
File: health-request.md

<a name="cockroach.server.serverpb.HealthRequest"></a> HealthRequest requests a liveness or readiness check. A liveness check is triggered via ready set to false. In this mode, an empty response is returned immediately, that is, the caller merely learns that the process is running. A readiness check (ready == true) is suitable for determining whether user traffic should be directed at a given node, for example by a load balancer. In this mode, a successful response is returned only if the node: is not in the process of shutting down or booting up (including waiting for cluster bootstrap); is regarded as healthy by the cluster via the recent broadcast of a liveness beacon. Absent either of these conditions, an error code will result. Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | ready | | | ready specifies whether the client wants to know whether the target node is ready to receive traffic. If a node is unready, an error will be returned. | |
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

Change log description (2-3 concise points about the changes in this PR. When committing this PR, the committer is expected to copy the content of this section to the merge description box) Purpose of the change (e.g., Fixes #666, Closes #1234) What the code does (Detailed description of the code changes) How to verify it (Optional: steps to verify that the changes are effective)
Project: KICS (Provisioning / Security & Compliance)
File: a58d1a2d-4078-4b80-855b-84cc3f7f4540.md

title: IAM Group Inline Policies hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a58d1a2d-4078-4b80-855b-84cc3f7f4540 Query name: IAM Group Inline Policies Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: IAM Groups should not use inline policies and instead use managed policies. If a group is deleted, the inline policy is also deleted<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" AWSTemplateFormatVersion: "2010-09-09" Description: A sample template Resources: myuser: Type: AWS::IAM::Group Properties: Path: "/" LoginProfile: Password: myP@ssW0rd Policies: PolicyName: giveaccesstoqueueonly PolicyDocument: Version: '2012-10-17' Statement: Effect: Allow Action: sqs:* Resource: !GetAtt myqueue.Arn Effect: Deny Action: sqs:* NotResource: !GetAtt myqueue.Arn ``` ```json title="Positive test num. 2 - json file" hl_lines="12" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "A sample template", "Resources": { "myuser": { "Type": "AWS::IAM::Group", "Properties": { "Path": "/", "LoginProfile": { "Password": "myP@ssW0rd" }, "Policies": [ { "PolicyName": "giveaccesstoqueueonly", "PolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sqs:*" ], "Resource": [ "myqueue.Arn" ] }, { "Effect": "Deny", "Action": [ "sqs:*" ], "NotResource": [ "myqueue.Arn" ] } ] } } ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: A sample template Resources: myuser: Type: AWS::IAM::Group ``` ```json title="Negative test num. 2 - json file" { "Description": "A sample template", "Resources": { "myuser": { "Type": "AWS::IAM::Group" } }, "AWSTemplateFormatVersion": "2010-09-09" } ```
Project: Redis (App Definition and Development / Database)
File: question.md

name: Question about: Ask the Redis developers title: '[QUESTION]' labels: '' assignees: '' Please keep in mind that this issue tracker should be used for reporting bugs or proposing improvements to the Redis server. Generally, questions about using Redis should be directed to the : It is also possible that your question was already asked here, so please do a quick issues search before submitting. Lastly, if your question is about one of Redis' , you may to contact your client's developers for help. That said, please feel free to replace all this with your question :)
Project: StarRocks (App Definition and Development / Database)
File: DELETE_SQLBLACKLIST.md

displayed_sidebar: "English" Deletes an SQL regular expression from the SQL blacklist. For more about SQL Blacklist, see . :::tip This operation requires the SYSTEM-level BLACKLIST privilege. You can follow the instructions in to grant this privilege. ::: ```SQL DELETE SQLBLACKLIST <sqlindexnumber> ``` `sqlindexnumber`: the index number of the SQL regular expression in the blacklist. Separate multiple index numbers with a comma (,) and a space. You can obtain the index number using . ```Plain mysql> DELETE SQLBLACKLIST 3, 4; mysql> SHOW SQLBLACKLIST; +-+--+ | Index | Forbidden SQL | +-+--+ | 1 | select count\(\*\) from .+ | | 2 | select idint \* 4, idtinyint, idvarchar from testalltypenullable except select idint, idtinyint, idvarchar from testbasic except select \(idint \* 9 \- 8\) \/ 2, idtinyint, idvarchar from testalltypenullable2 except select idint, idtinyint, idvarchar from testbasic_nullable | +-+--+ ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: Twitter.md

title: "Twitter" icon: /images/logos/powered-by/Twitter.png hasLink: "https://www.youtube.com/watch?v=bKrYUDZ1yx8&list=PL4dEBWmGSIU9OkXQU2OAXmITPLhiMSPRp&index=6" <!-- 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. -->
Project: ShardingSphere (App Definition and Development / Database)
File: show-sharding-table-nodes.en.md

+++ title = "SHOW SHARDING TABLE NODES" weight = 9 +++ `SHOW SHARDING TABLE NODES` syntax is used to query sharding table nodes in specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowShardingTableNode::= 'SHOW' 'SHARDING' 'TABLE' 'NODES' tableName? ('FROM' databaseName)? tableName ::= identifier 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 the currently used DATABASE. If DATABASE is not used, No database selected will be prompted. | Columns | Descriptions | ||--| | name | Sharding rule name | | nodes | Sharding nodes | Query sharding table nodes for specified table in the specified logical database ```sql SHOW SHARDING TABLE NODES torderitem FROM sharding_db; ``` ```sql mysql> SHOW SHARDING TABLE NODES torderitem FROM sharding_db; +--++ | name | nodes | +--++ | torderitem | resource0.torderitem0, resource0.torderitem1, resource1.torderitem0, resource1.torderitem1 | +--++ 1 row in set (0.00 sec) ``` Query sharding table nodes for specified table in the current logical database ```sql SHOW SHARDING TABLE NODES torderitem; ``` ```sql mysql> SHOW SHARDING TABLE NODES torderitem; +--++ | name | nodes | +--++ | torderitem | resource0.torderitem0, resource0.torderitem1, resource1.torderitem0, resource1.torderitem1 | +--++ 1 row in set (0.00 sec ``` Query sharding table nodes for all tables in the specified logical database ```sql SHOW SHARDING TABLE NODES FROM sharding_db; ``` ```sql mysql> SHOW SHARDING TABLE NODES FROM sharding_db; +--++ | name | nodes | +--++ | torderitem | resource0.torderitem0, resource0.torderitem1, resource1.torderitem0, resource1.torderitem1 | +--++ 1 row in set (0.00 sec) ``` Query sharding table nodes for all tables in the current logical database ```sql SHOW SHARDING TABLE NODES; ``` ```sql mysql> SHOW SHARDING TABLE NODES; +--++ | name | nodes | +--++ | torderitem | resource0.torderitem0, resource0.torderitem1, resource1.torderitem0, resource1.torderitem1 | +--++ 1 row in set (0.00 sec ``` `SHOW`, `SHARDING`, `TABLE`, `NODES`, `FROM`
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.1.3.0.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | plugin for generic shuffle service* Allow ReduceTask loading a third party plugin for shuffle (and merge) instead of the default shuffle. | Major | Port HADOOP-8175 (Add mkdir -p flag) to branch-1* FsShell mkdir now accepts a -p flag. Like unix, mkdir -p will not fail if the directory already exists. Unlike unix, intermediate directories are always created, regardless of the flag, to avoid incompatibilities. | Major | CLONE - The logging level of the tasks should be configurable by the job* Allow logging level of map/reduce tasks to be configurable. Configuration changes: add mapred.map.child.log.level add mapred.reduce.child.log.level | Major | DistCp will fail to copy with -delete switch* Has dependency on MAPREDUCE-1285/MAPREDUCE-5698 | Major | Support utf-8 text with BOM (byte order marker)* WARNING: No release note provided for this change. | Minor | Update DistCp v1 to optionally not use tmp location (branch-1 only)* DistCp v1 currently copies files to a temporary location and then renames that to the specified destination. This can cause performance issues on file systems such as S3. A -skiptmp flag is added to bypass this step and copy directly to the destination.
Project: Salt Project (Provisioning / Automation & Configuration)
File: README-how-to-build.md

The build client is where the msi installer is built. You need 64bit Windows 10 Git repositories `salt`, `salt-windows-nsis` and `salt-windows-msi` .Net 3.5 SDK (for WiX)<sup>*</sup> <sup></sup> <sup></sup> MicrosoftVC143CRT_x64.msm from Visual Studio 2015<sup></sup> MicrosoftVC143CRT_x86.msm from Visual Studio 2015<sup></sup> Notes: <sup>*</sup> `build.cmd` will open `optionalfeatures` if necessary. <sup></sup> `build.cmd` will download them to `.\_cache.dir` and install if necessary. Build the Nullsoft (NSIS) exe installer Or execute `test-copymockfilestosalt_repo.cmd` for only testing configuration Execute build.cmd Wix is transaction safe: either the product is installed or the prior state is restored/rolled back. C# is not. Product.wxs: main file. (EXPERIMENTAL) salt-minion Windows Service requires or CustomAction01/: custom actions in C# *-discovered-files.wxs: TEMPORARY FILE Immediate custom actions serve initialization (before the install transaction starts) and must not change the system. Deferred custom action may change the system but run in a "sandbox". Postfix | Example | Meaning -- | - | - `IMCAC` | `ReadConfigIMCAC` | Immediate custom action written in C# `DECAC` | `WriteConfigDECAC` | Deferred custom action written in C# `CADH` | `WriteConfigCADH` | Custom action data helper (only for deferred custom action) "Custom action data helper" send properties to the deferreed actions in the sandbox. msi conditions for install, uninstall, upgrade: https://stackoverflow.com/a/17608049 Install sequences documentation: The Windows installer restricts the maximum values of the : major.minor.build `255.255.65535` Therefore we generate an "internal version": Salt 3002.1 becomes `30.02.1` Python 2.7 = VC CRT 9.0 = VS 2008 Python 3.6 = VC CRT 14.0 = VS 2017
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: code-block3.md

title: Yoyoyo layout: 1: left This should appear in a left split. blank Desc1 blank Desc2. Minor step minor Should render as a minor step. blank Desc3. blank Desc4. Another minor step minor Also minor. blank Desc5. This should appear in a default split. ```bash id: AAA intentionalerror ``` === "tab1" ```{.bash .no-copy} id: BBB echo BBB ``` ```bash id: CCC echo CCC ``` === "tab2" ```bash id: DDD echo DDD ``` ```bash id: EEE echo EEE ```