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

Have you reviewed every line of your changes by yourself? Have you added enough test cases to cover the new feature or bug fix? Also, add comments to describe your test cases. Do function names keep consistent with its behavior? Is it easy to infer the function's behavior by its name? Is there any code that confuses the reviewer? Add comments on them! You'll be asked to do so anyway. Make sure there is no syntax or spelling error in your comments. Some online syntax checking tools like Grammarly may be helpful. Is there any way to refactor the code to make it more readable? If the refactoring touches a lot of existing code, send another PR to do it. Make sure the PR does only one thing and nothing else. Make sure the diff size is no more than 500, split it into small PRs if it is too large.
Project: VMClarity (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

Please provide a meaningful description of what this change will do, or is for. Bonus points for including links to related issues, other PRs, or technical references. Note that by not including a description, you are asking reviewers to do extra work to understand the context of this change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all. [ ] Bug Fix [ ] New Feature [ ] Breaking Change [ ] Refactor [ ] Documentation [ ] Other (please describe) [ ] Existing issues have been referenced (where applicable) [ ] I have verified this change is not present in other open pull requests [ ] Functionality is documented [ ] All code style checks pass [ ] New code contribution is covered by automated tests [ ] All new and existing tests pass
Project: Hazelcast IMDG (App Definition and Development / Database)
File: 01-executor-service-stats.md

| Since: 4.1| |-| Hazelcast has 3 different executor service implementations exposed with public api. These three different types of executor services are called as executor service, scheduled executor service and durable executor service. Only executor type which has statistics available among these is executor service. Statistics collection is not done for scheduled and durable ones. In this design, we make same statistics with executor service available for the other executor types. These statistics are only available for monitoring from management center. The statistics we have currently is represented with class `LocalExecutorStats`. ``` public interface LocalExecutorStats extends LocalInstanceStats { / Returns the number of pending operations on the executor service. * @return the number of pending operations on the executor service */ long getPendingTaskCount(); / Returns the number of started operations on the executor service. * @return the number of started operations on the executor service */ long getStartedTaskCount(); / Returns the number of completed operations on the executor service. * @return the number of completed operations on the executor service */ long getCompletedTaskCount(); / Returns the number of cancelled operations on the executor service. * @return the number of cancelled operations on the executor service */ long getCancelledTaskCount(); / Returns the total start latency of operations started. * @return the total start latency of operations started */ long getTotalStartLatency(); / Returns the total execution time of operations finished. * @return the total execution time of operations finished */ long getTotalExecutionLatency(); } ``` On submit of each task, we start to collect these statistics and with metrics subsystem, we made these available to management center. `DynamicMetricsProvider` interface is implemented by `DistributedScheduledExecutorService` and `DistributedDurableExecutorService` for this purpose. Statistics are available by default, they can be disabled via `ScheduledExecutorConfig` or `DurableExecutorConfig`. NOTE: Durable executor service has no cancellation capability hence no stats available for it. `scheduledExecutor` and `durableExecutor` prefixes are used for scheduled and durable executor services respectively. ``` [name=executorName,unit=ms,metric=scheduledExecutor.creationTime]=1598016899537 [name=executorName,unit=count,metric=scheduledExecutor.pending]=0 [name=executorName,unit=count,metric=scheduledExecutor.started]=1 [name=executorName,unit=count,metric=scheduledExecutor.completed]=0 [name=executorName,unit=count,metric=scheduledExecutor.cancelled]=0 [name=executorName,unit=ms,metric=scheduledExecutor.totalStartLatency]=2 [name=executorName,unit=ms,metric=scheduledExecutor.totalExecutionTime]=0 ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-secret-inspect.1.md

% podman-secret-inspect 1 podman\-secret\-inspect - Display detailed information on one or more secrets podman secret inspect [options] secret [...] Inspects the specified secret. By default, this renders all results in a JSON array. If a format is specified, the given template is executed for each result. Secrets can be queried individually by providing their full name or a unique partial name. Format secret output using Go template. | Placeholder | Description | |--|-| | .CreatedAt ... | When secret was created (relative timestamp, human-readable) | | .ID | ID of secret | | .SecretData | Secret Data (Displayed only with --showsecret option) | | .Spec ... | Details of secret | | .Spec.Driver ... | Driver info | | .Spec.Driver.Name | Driver name (string) | | .Spec.Driver.Options ... | Driver options (map of driver-specific options) | | .Spec.Labels ... | Labels for this secret | | .Spec.Name | Name of secret | | .UpdatedAt ... | When secret was last updated (relative timestamp, human-readable) | Print usage statement. Print inspect output in human-readable format Display secret data Inspect the secret mysecret. ``` $ podman secret inspect mysecret ``` Inspect the secret mysecret and display the Name and Scope field. ``` $ podman secret inspect --format "{{.Name} {{.Scope}}" mysecret ``` Inspect the secret mysecret and display the Name and SecretData fields. Note this will display the secret data to the screen. ``` $ podman secret inspect --showsecret --format "{{.Name} {{.SecretData}}" mysecret ``` , January 2021, Originally compiled by Ashley Cui <acui@redhat.com>
Project: Tinkerbell (Provisioning / Automation & Configuration)
File: MACOS_TESTING.md

When developing on MacOS it may be necessary to create a symlink to `/var/run/docker.sock`. First, validate `/var/run/docker.sock` does not exist. If it does not exist, verify the socket exists at `$HOME/.docker/run/docker.sock` and create a symlink. ``` sudo ln -s $HOME/.docker/run/docker.sock /var/run/docker.sock ```
Project: SuperEdge (Provisioning / Automation & Configuration)
File: SECURITY.md

If you encounter any failure in the process of using SuperEdge, you can use Contact us, or give us feedback via the contact information below: | Administrator | Mail address | | :--: | :-: | | Wenjun Tang | dodia@163.com | | Gerald Wang | neweyes1987@gmail.com | | Attlee Wang | wangdong102425@gmail.com | | Kaiyue Chen | chenkaiyue2008@163.com | | Fee Li | feeli202012@gmail.com | We welcome you to give us feedback on vulnerabilities, and we will fix vulnerabilities in time.
Project: secureCodeBox (Provisioning / Security & Compliance)
File: integrating-a-scanner.md

title: "Integrating A New Scanner" sidebar_position: 1 In the secureCodeBox we created new Custom Resource Definitions (CRD) for Kubernetes to manage scanners (ScanType) and hooks (see ). To add a new Scanner you need to add a new ScanType (see ) and a parser for its results. The directory structure of a scanner Helm Chart will look something like this: ```bash scanners/nmap cascading-rules ... docs README.ArtifactHub.md README.DockerHub-Parser.md README.DockerHub-Scanner.md examples demo-target-ssh findings.yaml nmap-results.xml scan.yaml ... parser Dockerfile package.json package-lock.json parser.js parser.test.js testFiles ... templates cascading-rules.yaml nmap-parse-definition.yaml nmap-scan-type.yaml scanner Dockerfile Chart.yaml values.yaml Makefile README.md .helm-docs.gotmpl .helmignore .gitignore ``` To create a new Helm Chart for your scanner you can use the following command (replace new-scanner with the name of the scanner): ```bash make create-new-scanner NAME=new-scanner ``` This command will create a new directory named new-scanner and some template files provided by `helm` to simplify the creation of Helm Charts (see ). The following pages describe the purpose of all files and how to configure them.
Project: CFEngine (Provisioning / Automation & Configuration)
File: BSD.md

BSD is not officially supported. These are some basic instructions for getting CFEngine Community to build on FreeBSD. Tested on FreeBSD 12.1 VM in AWS EC2. ``` $ su root -c 'pkg update -f && pkg install -y gdb gcc gmake lmdb autoconf automake libtool git python3' ``` ``` $ git clone --recursive https://github.com/cfengine/core.git $ git clone --recursive https://github.com/cfengine/masterfiles.git ``` ``` $ (cd masterfiles && ./autogen.sh && su root -c "gmake install") ``` To check out PR `#3589` to branch `bsd-branch`, do: ``` $ cd core $ git fetch origin pull/3589/head:bsd-branch && git checkout bsd-branch ``` ``` $ git config --global user.email "A" && git config --global user.name "A" $ git rebase master ``` Within `core` directory: ``` $ ./autogen.sh --enable-debug -C --with-lmdb=/usr/local/ --with-pcre2=/usr/local/ $ gmake -j8 ``` ``` $ su root -c 'gmake install' ``` Example bootstrap, using IP from `ifconfig`: ``` $ su root -c '/var/cfengine/bin/cf-key' $ ifconfig | grep inet inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::8f7:3cff:fe7d:5e7c%xn0 prefixlen 64 scopeid 0x2 inet 172.31.45.172 netmask 0xfffff000 broadcast 172.31.47.255 $ su root -c '/var/cfengine/bin/cf-agent -B 172.31.45.172' R: Bootstrapping from host '172.31.42.230' via built-in policy '/var/cfengine/inputs/failsafe.cf' R: This host assumes the role of policy server R: Updated local policy from policy server R: Triggered an initial run of the policy R: Started the server R: Started the scheduler notice: Bootstrap to '172.31.42.230' completed successfully! $ ```
Project: YugabyteDB (App Definition and Development / Database)
File: zrem.md

title: ZREM linkTitle: ZREM description: ZREM menu: preview: parent: api-yedis weight: 2530 aliases: /preview/api/redis/zrem /preview/api/yedis/zrem type: docs `ZREM key member [member...]` This command removes the `members` specified in the sorted set at `key` and returns the number of `members` removed. `Members` specified that do not exist in key are ignored. If `key` does not exist, 0 is returned. If `key` is associated with non sorted-set data, an error is returned. The number of `members` removed from the sorted set. You can do this as shown below. ```sh $ ZADD z_key 1.0 v1 2.0 v2 ``` ``` (integer) 2 ``` ```sh $ ZREM z_key v2 v3 ``` ``` (integer) 1 ``` ```sh $ ZREM z_key v1 v2 v3 ``` ``` (integer) 1 ``` ```sh $ ZCARD z_key ``` ``` (integer) 0 ``` , , , ,
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.33.md

RabbitMQ `3.8.33` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a `3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . `rabbitmq-diagnostics status` is now more resilient and won't fail if free disk space monitoring repeatedly fails (gets disabled) on the node. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.33.tar.xz` instead of the source tarball produced by GitHub.
Project: Siddhi (App Definition and Development / Streaming & Messaging)
File: SECURITY.md

The WSO2 security team welcomes contributions from our user community, developers, and security researchers to reinforce our product security. The security team at WSO2 will be more than happy to assist you in such efforts. We strongly encourage you to report security vulnerabilities to our private security mailing list: security@wso2.com - first, before disclosing them in any public forums. This is a private mailing list where only members of the WSO2 internal security team are subscribed to, and is treated as top priority. If you wish to send secure messages to security@wso2.com, you may use the following key: security@wso2.com: F0AB 72EC D77A 6162 4C48 A245 0CF3 FD36 E100 FF07 pgp.mit.edu Please use the following template in reporting vulnerabilities: Vulnerable Siddhi distribution(s) and version(s) Overview: High-level overview of the issue and self-assessed severity Description: Include the steps to reproduce Impact: Self-assessed impact Solution: Any proposed solution An overview of the vulnerability handling process: The user reports the vulnerability privately to security@wso2.com The WSO2 security team works privately with the user to resolve the vulnerability. The initial response time will be less than one hour Fix the vulnerability and QA verifies the solution There will be a patch released with the identified fix. There will be a new release of the component/product based on the severity of the issue identified. Announce the vulnerability and share the patch publicly
Project: KICS (Provisioning / Security & Compliance)
File: 9ec311bf-dfd9-421f-8498-0b063c8bc552.md

title: IAM User With Access To Console hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9ec311bf-dfd9-421f-8498-0b063c8bc552 Query name: IAM User With Access To Console Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: AWS IAM Users should not have access to console<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "awsiamuser" "example" { name = "example" path = "/" force_destroy = true } resource "awsiamuserloginprofile" "example_login" { user = awsiamuser.example.name pgpkey = "keybase:somepersonthatexists" } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "example" { name = "example" path = "/" force_destroy = true } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: window.md

title: "Window" <!-- 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. --> <table align="left"> <a target="_blank" class="button" href="https://beam.apache.org/releases/javadoc/current/index.html?org/apache/beam/sdk/transforms/windowing/Window.html"> <img src="/images/logos/sdks/java.png" width="20px" height="20px" alt="Javadoc" /> Javadoc </a> </table> <br><br> Logically divides up or groups the elements of a collection into finite windows according to a function. {{< playground height="700px" >}} {{< playgroundsnippet language="java" path="SDKJAVAWindow" show="mainsection" >}} {{< /playground >}} converts between explicit and implicit form of various Beam values. applies a function to determine a timestamp to each element in the output collection.
Project: YugabyteDB (App Definition and Development / Database)
File: include-connect.md

<!-- +++ private = true +++ --> Expect an output similar to the following: ```output +-+ | yugabyted | +-+ | Status : Running. | | Replication Factor : 1 | | YugabyteDB UI : http://127.0.0.1:15433 | | JDBC : jdbc:postgresql://127.0.0.1:5433/yugabyte?user=yugabyte&password=yugabyte | | YSQL : bin/ysqlsh -U yugabyte -d yugabyte | | YCQL : bin/ycqlsh -u cassandra | | Data Dir : /Users/myuser/var/data | | Log Dir : /Users/myuser/var/logs | | Universe UUID : 41e54e9f-6f2f-4a46-befe-e0cd65d3056a | +-+ ``` After the cluster has been created, clients can connect to the YSQL and YCQL APIs at `http://localhost:5433` and `http://localhost:9042` respectively. You can also check `~/var/data` to see the data directory and `~/var/logs` to see the logs directory. Execute the following command to check the cluster status at any time: ```sh ./bin/yugabyted status ``` Using the YugabyteDB SQL shell, , you can connect to your cluster and interact with it using distributed SQL. ysqlsh is installed with YugabyteDB and is located in the bin directory of the YugabyteDB home directory. (If you have previously installed YugabyteDB version 2.8 or later and created a cluster on the same computer, you may need to to run the latest features.) To open the YSQL shell, run `ysqlsh`: ```sh ./bin/ysqlsh ``` ```output ysqlsh (11.2-YB-2.21.0.0-b545) Type "help" for help. yugabyte=# ``` To load sample data and explore an example using ysqlsh, follow the instructions in . When you start a cluster using yugabyted, you can monitor the cluster using the YugabyteDB UI, available at . The YugabyteDB UI provides cluster status, node information, performance metrics, and more.
Project: Strimzi (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

Select the type of your PR Bugfix Enhancement / new feature Refactoring Documentation Please describe your pull request Please go through this checklist and make sure all applicable tasks have been done [ ] Write tests [ ] Make sure all tests pass [ ] Update documentation [ ] Check RBAC rights for Kubernetes / OpenShift roles [ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally [ ] Reference relevant issue(s) and close them after merging [ ] Update CHANGELOG.md [ ] Supply screenshots for visual changes, such as Grafana dashboards
Project: KICS (Provisioning / Security & Compliance)
File: integrations_tfcloud.md

You can integrate KICS into Terraform Cloud as a Task Event Hook. This provides you the ability to run a KICS scan on the plan in the pre-apply stage. To Configure Task Event Hook go to: Organization Settings -> Integrations -> Task Event Hook -> Create Event Hook <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/createeventhook_tfcloud.png" width="850"> Set the name you wish for the Task Event Hook In the Hook endpoint URL place: ``` https://kics.io/tfc/event?failOn=low ``` And Create event hook. Note: You can choose which kind of severity you wish for KICS to fail on by passing `failOn` as query parameter in the URL. KICS will fail on any result found with that severity and above. Available Severities are: critical high medium low info Query parameter `failOn` is required and cannot be empty. To add KICS Event Hook as a Task to your Workspace go to: Workspace Settings -> Tasks -> Available Event Hooks and Choose KICS Event Hook you just created <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/createworkspacetask.png" width="850"> Choose the Enforcement Level and press Create And now every time a new plan is started KICS will scan this plan for Vulnerabilities and missconfigurations Task Failed <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/taskfailedtfcloud.png" width="850"> To see KICS Scan report press `Details` to download the html report and see all vulnerabilities found by KICS Please keep in mind the report link is only active for 15 minutes Task Passed <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/tasksuccesstfcloud.png" width="850">
Project: Kafka (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

*More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* *Summary of testing strategy (including rationale) for the feature or bug fix. Unit and/or integration tests are expected for any behaviour change and system tests should be considered for larger changes.* [ ] Verify design and implementation [ ] Verify test coverage and CI build status [ ] Verify documentation (including upgrade notes)
Project: ClickHouse (App Definition and Development / Database)
File: v22.7.2.15-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix seeking while reading from encrypted disk. This PR fixes . (). Backported in : Fix data race and possible heap-buffer-overflow in Avro format. Closes Closes . (). Backported in : Fix bug with maxsplit argument for splitByChar, which was not working correctly. (). Backported in : Fix wrong index analysis with tuples and operator `IN`, which could lead to wrong query result. (). Backported in : Fix `CANNOTREADALLDATA` exception with `localfilesystemreadmethod=pread_threadpool`. This bug affected only Linux kernel version 5.9 and 5.10 according to . (). Replace MemoryTrackerBlockerInThread to LockMemoryExceptionInThread (). Change mysql-odbc url ().
Project: StarRocks (App Definition and Development / Database)
File: SHOW_PROFILELIST.md

displayed_sidebar: "English" Lists the query profile records cached in your StarRocks cluster. For more information about query profile, see . This feature is supported from v3.1 onwards. No privilege is required to perform this operation. ```SQL SHOW PROFILELIST [LIMIT n] ``` `LIMIT n`: lists n most recent records. | Return | Description | | - | | | QueryId | The ID of the query. | | StartTime | The start time of the query. | | Time | The latency of the query. | | State | The status of the query, including:`Error`: The query encounters an error.`Finished`: The query is finished.`Running`: The query is running. | | Statement | The statement of the query. | Example 1: Show five most recent query profile records. ```SQL SHOW PROFILELIST LIMIT 5; ```
Project: KICS (Provisioning / Security & Compliance)
File: 9db38e87-f6aa-4b5e-a1ec-7266df259409.md

title: Email Alerts Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9db38e87-f6aa-4b5e-a1ec-7266df259409 Query name: Email Alerts Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Make sure that alerts notifications are set to 'On' in the Azure Security Center Contact<br> ```tf title="Positive test num. 1 - tf file" hl_lines="4" resource "azurermsecuritycenter_contact" "positive1" { email = "contact@example.com" phone = "+1-555-555-5555" alert_notifications = false } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermsecuritycenter_contact" "negative1" { email = "contact@example.com" phone = "+1-555-555-5555" alert_notifications = true } ```
Project: Stolon (App Definition and Development / Database)
File: pg_rewind.md

Stolon can use to speedup instance resynchronization (for example resyncing an old master or a slave ahead of the current master) without the need to copy all the new master data. It can be enabled setting to true the cluster specification option `usePgrewind` (defaults to false): ``` bash stolonctl [cluster options] update --patch '{ "usePgrewind" : true }' ``` This will also enable the `walloghints` postgresql parameter. If previously `walloghints` wasn't enabled you should restart the postgresql instances (you can do so restarting the `stolon-keeper`) pg_rewind needs to connect to the master database with a superuser role (see the ).