cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-kata-release.md

title: "Apache Beam Katas" date: 2019-05-30 00:00:01 -0800 categories: blog aliases: /blog/2019/05/30/beam-kata-release.html authors: henryken <!-- 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. --> We are happy to announce , a set of interactive Beam coding exercises (i.e. ) that can help you in learning Apache Beam concepts and programming model hands-on. <!--more--> Beam Katas objective is to provide a series of structured hands-on learning experiences for learners to understand about Apache Beam and its SDKs by solving exercises with gradually increasing complexity. It is built based on . Beam Katas is available for both Java and Python SDKs. Currently we have about 20 lessons that cover Apache Beam fundamentals, such as core transforms, common transforms, and simple use case (word count), with more katas to be added in the coming future. To start with the courses, you can simply download or and then browse the integrated Stepik courses from the menu. Search for Beam Katas and once the course is loaded on the IDE, youre good to go. We have plans to add more katas covering more topics including some of the intermediate and advanced ones in the coming future, such as windowing, streaming, and use case patterns. We would also like to welcome you to by building and adding more katas that you think would be useful for people to learn more about Apache Beam, and eventually become Beam Masters! <br/> <img src="/images/blog/beam-kata/beam-kata-intellij-edu-1.png" alt="Beam Kata - IntelliJ Edu" width="363" height="350"> <img src="/images/blog/beam-kata/beam-kata-intellij-edu-2.png" alt="Beam Kata - IntelliJ Edu" width="455" height="350"> <img src="/images/blog/beam-kata/beam-kata-pycharm-edu-1.png" alt="Beam Kata - PyCharm Edu" width="363" height="350"> <img src="/images/blog/beam-kata/beam-kata-pycharm-edu-2.png" alt="Beam Kata - PyCharm Edu" width="459" height="350">
Project: KICS (Provisioning / Security & Compliance)
File: 1a07a446-8e61-4e4d-bc16-b0781fcb8211.md

title: Kubelet Event QPS Not Properly Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1a07a446-8e61-4e4d-bc16-b0781fcb8211 Query name: Kubelet Event QPS Not Properly Set Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: When using the kubelet command, the '--event-qps' should be set to 0<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet"] args: ["--event-qps=1"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet","--event-qps=3"] args: [] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="5" apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration address: "192.168.0.8" port: 20250 eventRecordQPS: 2 serializeImagePulls: false tlsCertFile: "someFile.txt" tlsPrivateKeyFile: "someFile.txt" evictionHard: memory.available: "200Mi" ``` <details><summary>Positive test num. 4 - yaml file</summary> ```yaml hl_lines="2" apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration address: "192.168.0.8" port: 20250 serializeImagePulls: false tlsCertFile: "someFile.txt" tlsPrivateKeyFile: "someFile.txt" evictionHard: memory.available: "200Mi" ``` </details> ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet"] args: ["--event-qps=0"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet"] args: [] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 3 - yaml file" apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration address: "192.168.0.8" port: 20250 serializeImagePulls: false eventRecordQPS: 0 tlsCertFile: "someFile.txt" tlsPrivateKeyFile: "someFile.txt" evictionHard: memory.available: "200Mi" ``` <details><summary>Negative test num. 4 - json file</summary> ```json { "kind": "KubeletConfiguration", "apiVersion": "kubelet.config.k8s.io/v1beta1", "port": 10250, "readOnlyPort": 10255, "cgroupDriver": "cgroupfs", "eventRecordQPS": 0, "hairpinMode": "promiscuous-bridge", "serializeImagePulls": false, "featureGates": { "RotateKubeletClientCertificate": true, "RotateKubeletServerCertificate": true } } ``` </details>
Project: YugabyteDB (App Definition and Development / Database)
File: ta-20398.md

title: TA-20398 headerTitle: Slow execution of copy command and multi-row inserts headcontent: 23 Jan 2024 type: docs showRightNav: true cascade: unversioned: true menu: preview_releases: identifier: ta-20398 weight: 1 rightNav: hideH2: true type: docs | Product | Affected Versions | Related Issues | Fixed In | | :- | : | :- | :- | | {{<product "ysql">}} | {{<release "2.19.1.x, 2.20.0.x">}} | {{<issue 20398>}} | {{<release "2.20.1.3">}} | You can face slow data load when using the copy command or when doing multi-row inserts. This particular issue can be identified with the following metrics. Low bloom filter usage; very low value for metrics `rocksdbbloomfilterchecked` and `rocksdbbloomfilteruseful` High block cache miss; high value for metric `rocksdbblockcachedatamiss` Upgrade to a release with the fix. Data load into a table using multi-insert statements or copy command slowed performance due to a bug in bloom filter check. This issue arose from two commits which were preventing bloom filters from being used. To address this, the commits were reverted, although this action needed to be selective to retain a crucial bug fix. A fix that addresses the issue essentially includes a rollback of the original changes, while preserving the necessary bug fix. The fix has been backported and is available in v2.20.1.3+ and v2.20.2.0.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-11597.en.md

Upgrade ekka to 0.15.13, which includes the following changes: upgrade Mria to 0.6.2: make bootstrap batch size configurable, improve robustness of mria_membership processes, fix log message formatting error Add `node.defaultbootstrapbatch_size` option to EMQX configuration. Increasing the value of this option can greatly reduce a replicant node startup time, especially when EMQX cluster interconnect network latency is high and EMQX built-in database holds large amount of data, e.g. when the number of subscriptions is high.
Project: cert-manager (Provisioning / Security & Compliance)
File: feature-request.md

name: Feature request about: Suggest an idea to improve cert-manager Is your feature request related to a problem? Please describe. <!--A clear and concise description of what the problem is--> Describe the solution you'd like <!--A clear and concise description of what you want to happen.--> Describe alternatives you've considered <!--A clear and concise description of any alternative solutions or features you've considered.--> Additional context <!--Add any other context about the feature request here.--> Environment details (remove if not applicable): Kubernetes version: Cloud-provider/provisioner: cert-manager version: Install method: e.g. helm/static manifests /kind feature
Project: KICS (Provisioning / Security & Compliance)
File: 9391103a-d8d7-4671-ac5d-606ba7ccb0ac.md

title: Etcd Client Certificate Authentication Set To False hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9391103a-d8d7-4671-ac5d-606ba7ccb0ac Query name: Etcd Client Certificate Authentication Set To False Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: When using etcd commands, the '--client-cert-auth' flag should be defined<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="21" apiVersion: apps/v1 kind: Deployment metadata: name: app-etcd-deployment spec: selector: matchLabels: app: app replicas: 1 template: metadata: labels: app: app version: v1 spec: serviceAccountName: database containers: name: database image: gcr.io/google_containers/etcd:v3.2.18 imagePullPolicy: IfNotPresent command: ["etcd"] args: ["--client-cert-auth=false"] nodeSelector: kubernetes.io/hostname: worker02 restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="21" apiVersion: apps/v1 kind: Deployment metadata: name: app-etcd-deployment spec: selector: matchLabels: app: app replicas: 1 template: metadata: labels: app: app version: v1 spec: serviceAccountName: database containers: name: database image: gcr.io/google_containers/etcd:v3.2.18 imagePullPolicy: IfNotPresent command: ["etcd"] args: [] nodeSelector: kubernetes.io/hostname: worker02 restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: apps/v1 kind: Deployment metadata: name: app-etcd-deployment spec: selector: matchLabels: app: app replicas: 1 template: metadata: labels: app: app version: v1 spec: serviceAccountName: database containers: name: database image: gcr.io/google_containers/etcd:v3.2.18 imagePullPolicy: IfNotPresent command: ["etcd"] args: ["--client-cert-auth=true"] nodeSelector: kubernetes.io/hostname: worker02 restartPolicy: OnFailure ```
Project: Trivy (Provisioning / Security & Compliance)
File: dotnet.md

Trivy supports `.NET core` and `NuGet` package managers. The following scanners are supported. | Artifact | SBOM | Vulnerability | License | |--|:-:|:-:|:-:| | .Net Core | | | - | | NuGet | | | | The following table provides an outline of the features Trivy offers. | Package manager | File | Transitive dependencies | Dev dependencies | | Position | |::|--|:--:|:-:|::|:--:| | .Net Core | *.deps.json | | Excluded | - | | | NuGet | packages.config | | Excluded | - | - | | NuGet | *Packages.props | - | Excluded | - | - | | NuGet | packages.lock.json | | Included | | | Trivy parses `*.deps.json` files. Trivy currently excludes dev dependencies from the report. Trivy only finds dependency names and versions from `packages.config` files. To build dependency graph, it is better to use `packages.lock.json` files. Trivy parses `*Packages.props` files. Both legacy `Packages.props` and modern `Directory.Packages.props` are supported. `packages.config` files don't have information about the licenses used. Trivy uses files from to detect licenses. !!! note The `licenseUrl` field is . Trivy doesn't parse this field and only checks the [license] field (license `expression` type only). Currently only the default path and `NUGET_PACKAGES` environment variable are supported. Don't forgot to lock files in your project. !!! tip Please make sure your lock file is up-to-date after modifying dependencies. Same as
Project: FOSSA (Provisioning / Security & Compliance)
File: glide.md

Glide is very commonly encountered as a buildtool for older Go projects. Though deprecated, it's prevalent enough among existing projects that it warrants support in fossa-cli. Find all files named `glide.lock` `glide.lock` is a yaml-formatted file containing pinned package versions: ```yaml hash: 12345 updated: 2018-10-12T14:37:49.968644-07:00 imports: name: github.com/pkg/one version: 100 subpackages: compute name: github.com/pkg/three/v3 version: 300 repo: fossas/privatefork ```
Project: KICS (Provisioning / Security & Compliance)
File: ae5b6871-7f45-42e0-bb4c-ab300c4d2026.md

title: Privileged Containers Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ae5b6871-7f45-42e0-bb4c-ab300c4d2026 Query name: Privileged Containers Enabled Platform: DockerCompose Severity: <span style="color:#bb2124">High</span> Category: Resource Management URL: Privileged containers should be used with extreme caution, they have all of the capabilities that the linux kernel offers for docker.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" version: "3.9" services: webapp: build: context: ./dir dockerfile: Dockerfile-alternate args: buildno: 1 privileged: true ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="13" version: "3.9" services: webapp: build: context: ./dir dockerfile: Dockerfile-alternate args: buildno: 1 ports: "8080:8080" "3000:3000" privileged: true cap_drop: all ``` ```yaml title="Negative test num. 1 - yaml file" version: "3.9" services: webapp: build: context: ./dir dockerfile: Dockerfile-alternate args: buildno: 1 ``` ```yaml title="Negative test num. 2 - yaml file" version: "3.9" services: webapp: build: context: ./dir dockerfile: Dockerfile-alternate args: buildno: 1 ports: "8080:8080" "3000:3000" privileged: false ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.14.md

layout: release date: 2021-05-20 tag: v0.5.14 manifests updated @kumarabd (#2986) [Lifecycle] Helm: Update container image repo with the correct location @nakul-shahdadpuri (#2973) Kumarabd/feature/fixe @kumarabd (#2964) Kumarabd/feature/fi @kumarabd (#2978) Change endpoint in meshconfig(platform: Docker) @metonymic-smokey (#2951)
Project: StarRocks (App Definition and Development / Database)
File: percentile_empty.md

displayed_sidebar: "English" Constructs a PERCENTILE value, which is used to fill in null values for data loading using or . ```Haskell PERCENTILE_EMPTY(); ``` None Returns a PERCENTILE value. Create a table. The `percent` column is a PERCENTILE column. ```sql CREATE TABLE `aggregate_tbl` ( `site_id` largeint(40) NOT NULL COMMENT "id of site", `date` date NOT NULL COMMENT "time of event", `citycode` varchar(20) NULL COMMENT "citycode of user", `pv` bigint(20) SUM NULL DEFAULT "0" COMMENT "total page views", `percent` PERCENTILE PERCENTILE_UNION COMMENT "others" ) ENGINE=OLAP AGGREGATE KEY(`siteid`, `date`, `citycode`) COMMENT "OLAP" DISTRIBUTED BY HASH(`site_id`) PROPERTIES ("replication_num" = "3"); ``` Insert data into the table. ```sql INSERT INTO aggregate_tbl VALUES (5, '2020-02-23', 'citycode', 555, percentileempty()); ```
Project: StarRocks (App Definition and Development / Database)
File: array_sort.md

displayed_sidebar: "English" Sorts the elements of an array in ascending order. ```Haskell array_sort(array) ``` `array`: the array whose elements you want to sort. Only the ARRAY data type is supported. Returns an array. This function sorts the elements of an array only in ascending order. `NULL` values are placed at the beginning of the array that is returned. If you want to sort the elements of an array in descending order, use the function. The elements of the returned array have the same data type as the elements of the input array. The following table is used as an example: ```plaintext mysql> select * from test; ++--+ | c1 | c2 | ++--+ | 1 | [4,3,null,1] | | 2 | NULL | | 3 | [null] | | 4 | [8,5,1,4] | ++--+ ``` Sort the values of column `c2` in ascending order. ```plaintext mysql> select c1, array_sort(c2) from test; +++ | c1 | array_sort(`c2`) | +++ | 1 | [null,1,3,4] | | 2 | NULL | | 3 | [null] | | 4 | [1,4,5,8] | +++ ```
Project: VMClarity (Provisioning / Security & Compliance)
File: troubleshooting.md

- How to debug the Scanner VMs can differ per provider these are documented below. On AWS VMClarity is configured to create the Scanner VMs with the same key-pair that the VMClarity server has. The Scanner VMs run in a private network, however the VMClarity Server can be used as a bastion/jump host to reach them via SSH. ``` ssh -i <key-pair private key> -J ubuntu@<vmclarity server public IP> ubuntu@<scanner VM private IP address> ``` Once SSH access has been established, the status of the VM's start up configuration can be debugged by checking the cloud-init logs: ``` sudo journalctl -u cloud-final ``` And the vmclarity-scanner service logs: ``` sudo journalctl -u vmclarity-scanner ```
Project: Harbor (Provisioning / Container Registry)
File: 2-14-LDAP-user-view-projects.md

Test 2-14 - User View Projects (LDAP Mode) ======= To verify that a non-admin user can view projects in (LDAP mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. There is at least a non-admin user. The user has at least 3 private projects. The registry has at least 3 public repositories. Same as Test 2-04 except that users are from LDAP/AD. Same as Test 2-04. None
Project: YugabyteDB (App Definition and Development / Database)
File: type_character.md

title: Character data types [YSQL] headerTitle: Character data types linkTitle: Character description: Use character-based data types to specify data of a string of Unicode characters. menu: v2.18: identifier: api-ysql-datatypes-character parent: api-ysql-datatypes type: docs Character-based data types are used to specify data of a string of Unicode characters. Data type | Description | -|-| `CHAR` | Character string of 1 byte | `CHAR` (n) | Character string of fixed-length (n) and blank padded | `CHARACTER` (n) | Character string of fixed-length (n) and blank padded | `CHARACTER` `VARYING` (n) | Character string of variable-length with maximum limit (n) | `VARCHAR` (n) | Character string of variable-length with maximum limit (n) | `VARCHAR` | Character string of variable and unlimited length | `TEXT` | Character string of variable and unlimited length | ```ebnf text_literal ::= "'" [ '' | letter ...] "'" ``` Where Single quote must be escaped as (''). `letter` is any character except for single quote (`[^']`). Character-based data types can be part of the `PRIMARY KEY`. Value of character data type are convertible and comparable to non-text data types.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.9-en.md

Add `certcommonname` and `certsubject` placeholder support for authzhttp and authz_mongo . Use milliseconds internally in emqx_delayed to store the publish time, improving precision . More rigorous checking of flapping to improve stability of the system . No message(s) echo for the message publish APIs . Prior to this fix, the message publish APIs (`api/v5/publish` and `api/v5/publish/bulk`) echos the message back to the client in HTTP body. This change fixed it to only send back the message ID. Check ACLs for last will testament topic before publishing the message . Fix GET /listeners API crash when some nodes (in a cluster) is still loading the configs . Fix empty variable interpolation in authentication and authorization . Placeholders for undefined variables are rendered now as empty strings and do not cause errors anymore. Fix the latency statistics error of the slow subscription stats . Prior to this change when `stats_type` is `internal` or `response`, the begin time stamp was taken at wrong precision. Fix shared subscription message re-dispatches . When discarding QoS 2 inflight messages, there were excessive logs For wildcard deliveries, the re-dispatch used the wrong topic (the publishing topic, but not the subscribing topic), caused messages to be lost when dispatching. Upgrade http client `gun` from 1.3.7 to Prior to this fix, long-lived HTTPS connections for HTTP auth or webhook integrations may stall indefinitely, causing massive timeouts for HTTP requests.
Project: secureCodeBox (Provisioning / Security & Compliance)
File: parser-dir.md

title: parser (Directory) sidebar_position: 6 This directory contains the parser for your scanner to transform the results of your scanner to Findings (see: ). For the parser we use multi-stage builds (see: ). For our JavaScript Parser SDK the Dockerfile should look like this: ```dockerfile ARG baseImageTag FROM node:14-alpine as build RUN mkdir -p /home/app WORKDIR /home/app COPY package.json package-lock.json ./ RUN npm ci --production FROM securecodebox/parser-sdk-nodejs:${baseImageTag:-latest} WORKDIR /home/app/parser-wrapper/parser/ COPY --from=build --chown=app:app /home/app/nodemodules/ ./nodemodules/ COPY --chown=app:app ./parser.js ./parser.js ``` If your parser does not require any external dependencies, A multi-stage build is not needed. Instead, a simpler Dockerfile can be used. ```dockerfile ARG namespace ARG baseImageTag FROM securecodebox/parser-sdk-nodejs:${baseImageTag:-latest} WORKDIR /home/app/parser-wrapper/parser/ COPY --chown=app:app ./parser.js ./parser.js ``` See for instructions on how to build your parser. To create a parser for your scanner you will have to execute the following steps in the parser directory: Your `package.json` should look something like this: ```json { "name": "nmap-parser", "version": "1.0.0", "description": "Parses result files for the type: 'nmap-xml'", "main": "", "scripts": {}, "keywords": [], "author": "iteratec GmbH", "license": "Apache-2.0", "dependencies": { "lodash": "^4.17.20", "xml2js": "^0.4.23" }, "devDependencies": {} } ``` If you need additional dependencies you can install them via `npm install`. Create a `parser.js` file and update the parser function of the Parser SDK. A starting point would be: ```javascript async function parse(fileContent) { return []; } module.exports.parse = parse; ``` After your scanner has finished, the Parser SDK will retrieve the output results and call your custom parse function `parse`. The SDK expects a finding object as specified in . The `id`, `parsedat` and `identifiedat` fields can be omitted, as they will be added by the Parser SDK. Please provide some tests for your parser in the `parser.test.js` file. To make sure that the output complies with the format specified in you should call the method `validateParser(parseResult)` from the ParserSDK and assert that it must resolve (not throw errors). You can do so e.g. by calling the following code. See the already existing parsers for reference. ```javascript const { validateParser, } = require("@securecodebox/parser-sdk-nodejs/parser-utils"); const findings = await parse(fileContent); await expect(validateParser(findings)).resolves.toBeUndefined(); ``` If you need additional files for your test please save these in the `testFiles` directory. Please take a look at for more information. Assuming you've set up the scanner , you can run your unit test with `make unit-tests`.