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

| Version | Supported | | - | | | 5.1.x | :whitecheckmark: | | 5.0.x | :whitecheckmark: | | 4.4.x | :whitecheckmark: | | < 4.4 | :x: | Any design or implementation issue that substantially affects the confidentiality or integrity of user data is likely to be in scope for the program. Common examples including: Cross-site scripting Cross-site request forgery Mixed-content scripts Authentication or authorization flaws Server-side code execution bugs Out of concern for the availability of our services to all users, please do not attempt to carry out DoS attacks, leverage black hat SEO techniques, spam people, brute force authentication, or do other similarly questionable things. We also discourage the use of any vulnerability testing tools that automatically generate very significant volumes of traffic. Depending on their impacts, some of the reported issues may not qualify. Although we review them on a case-by-case basis, here are some of the issues that typically do not earn a monetary reward: Bugs requiring exceedingly unlikely user interaction Brute forcing User enumeration Non security related bugs Abuse When investigating a vulnerability, please, only ever target your own accounts. Never attempt to access anyone else's data and do not engage in any activity that would be disruptive or damaging to other users. In the case the same vulnerability is present on multiple products, please combine and send one report. If you have found a vulnerability, please contact us at security@emqx.io. Note that we are only able to answer technical vulnerability reports. Duplicate reports will not be rewarded, first report on the specific vulnerability will be rewarded. The report should include steps in plain text how to reproduce the vulnerability (not only video or images).
Project: ClickHouse (App Definition and Development / Database)
File: quota_usage.md

slug: /en/operations/system-tables/quota_usage Quota usage by the current user: how much is used and how much is left. Columns: `quota_name` () Quota name. `quotakey`() Key value. For example, if keys = \[`ip address`\], `quotakey` may have a value 192.168.1.1. `start_time`(()) Start time for calculating resource consumption. `end_time`(()) End time for calculating resource consumption. `duration` (()) Length of the time interval for calculating resource consumption, in seconds. `queries` (()) The total number of requests on this interval. `query_selects` (()) The total number of select requests on this interval. `query_inserts` (()) The total number of insert requests on this interval. `max_queries` (()) Maximum number of requests. `errors` (()) The number of queries that threw an exception. `max_errors` (()) Maximum number of errors. `result_rows` (()) The total number of rows given as a result. `maxresultrows` (()) Maximum number of result rows. `result_bytes` (()) RAM volume in bytes used to store a queries result. `maxresultbytes` (()) Maximum RAM volume used to store a queries result, in bytes. `read_rows` (()) The total number of source rows read from tables for running the query on all remote servers. `maxreadrows` (()) Maximum number of rows read from all tables and table functions participated in queries. `read_bytes` (()) The total number of bytes read from all tables and table functions participated in queries. `maxreadbytes` (()) Maximum of bytes read from all tables and table functions. `failedsequentialauthentications` (()) The total count of sequential authentication failures. If the user entered the correct password before exceed `failedsequentialauthentications` threshold then the counter will be reset. `maxfailedsequential_authentications` (()) Maximum count of sequential authentication failures. `execution_time` (()) The total query execution time, in seconds (wall time). `maxexecutiontime` (()) Maximum of query execution time.
Project: Meshery (Provisioning / Automation & Configuration)
File: releases.md

layout: default title: Releases permalink: project/releases abstract: List of released Meshery versions and their release notes. redirect_from: project/releases/ language: en type: project category: project list: include See also Meshery's and process. {% assign sorted_release = site.releases | sort: 'date' | reverse %} <table> <tr><th> Version </th><th> Date </th></tr> {% for releases in sorted_release %} {% assign releasedate = releases.date | date: "%B %d, %Y" %} <tr> <td style="text-align:center"> <a href="{{site.baseurl}}/{{page.permalink}}/{{ releases.tag }}">{{ releases.tag }}</a> </td> <td style="text-align:center"> {{releasedate}} </td> </tr> {% endfor %} </table>
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12267.en.md

Add a new `timeout` parameter to the `cluster/:node/invite` interface. Previously the default timeout was 5s which would often be caused by HTTP API calls due to emqx taking too long to join cluster. Add a new endpoint `/cluster/:node/invite_async` to support an asynchronous way to invite nodes to join the cluster, and a new endpoint `cluster/invitation` to inspect the join status.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.11.3.md

This update includes a fix for operator deployment on Kubernetes. When using the Dapr Operator on Kubernetes with Argo Controller enabled, the operator would fail to start with the following error: ``` time="2023-07-11T17:22:49.937549597Z" level=fatal msg="error running operator: error running operator: failed to wait for rollout caches to sync: timed out waiting for cache to be synced" instance=dapr-operator-7cd6d96dfd-9wbj7 scop Stream closed EOF for dapr-system/dapr-operator-7cd6d96dfd-9wbj7 (dapr-operator) ``` The Dapr Operator would fail to start when Argo Controller is enabled and a Argo rollout is performend. The Dapr Operator was not creating the full Operator scheme before waiting for the controller manager to start. Updated the Dapr Operator to create the full Operator scheme before waiting for the controller manager to start.
Project: BOSH (Provisioning / Automation & Configuration)
File: bug_report.md

name: Bug report about: Create a report to help us improve Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior (example): Deploy a bosh director on <IaaS> with <configuration options> Upload <stemcell> and <cloud-config> Deploy <manifest> `bosh ssh` to a specific instance Run <commands> on the vm to see the behavior Expected behavior A clear and concise description of what you expected to happen. Logs Logs are always helpful! Add logs to help explain your problem. Versions (please complete the following information): Infrastructure: [e.g. AWS, GCP, etc] BOSH version [e.g. 266.7] BOSH CLI version [e.g. 5.1.1] Stemcell version [e.g. ubuntu-xenial/97.10] ... other versions of releases being used (BOSH DNS, Credhub, UAA, BPM, etc) Deployment info: If possible, share your (redacted) manifest and any ops files used to deploy BOSH or any other releases on top of BOSH. If you used any deployment strategy it'd be helpful to point it out and share as much about it as possible (e.g. bosh-deployment, PCF, genesis, spiff, etc) Additional context Add any other context about the problem here.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 09_basic_triggers.md

Prompt: What is a trigger in Apache Beam? Response: Apache Beam uses triggers to determine when to emit the aggregated results of each , referred to as a pane. Triggers provide two additional capabilities compared to : Allowing early results to be output before the end of the window. Allowing late data to be handled after the end of the window. This feature lets you control the flow of your data and balance between completeness, latency, and cost. You set the triggers for a `PCollection` by setting the `trigger` parameter of the `WindowInto` transform. ```python pcollection | WindowInto( FixedWindows(1 * 60), trigger=AfterProcessingTime(1 * 60), accumulation_mode=AccumulationMode.DISCARDING) ``` When a trigger fires, it emits the current contents of the window as a pane. Because a trigger can fire multiple times, the accumulation mode determines whether the system accumulates the window panes as the trigger fires, or discards them. This behavior is controlled by the parameter of the `WindowInto` transform. Beam provides several that you can use to determine when to emit the results of your pipeline's windowed computations: Event time triggers Processing time triggers Data-driven triggers Composite triggers One of the most useful trigger patterns is the trigger, which fires a single time when Apache Beam estimates that all the data has arrived, such as when the watermark passes the end of the window.
Project: YugabyteDB (App Definition and Development / Database)
File: ataccama.md

title: Ataccama DQ Analyzer linkTitle: Ataccama DQ Analyzer description: Use Ataccama DQ Analyzer with YSQL API menu: preview_integrations: identifier: ataccama parent: data-discovery weight: 571 type: docs combines advanced data profiling and analysis capabilities with a point-and-click interface that is basic enough for business managers to use without extensive training. All Ataccama solutions use databases in one way or another. They can be used as data sources and repositories for storing data. Because YugabyteDB's YSQL API is wire-compatible with PostgreSQL, DQ Analyzer can connect to YugabyteDB as a data source using the PostgreSQL JDBC driver which is shipped with the analyzer itself. Your YugabyteDB cluster should be up and running. Refer to . Follow the steps in to connect the database. Perform the following modifications as part of the connection steps: Select PostgreSQL as the database type but provide the configuration to connect to YugabyteDB. DQ Analyzer can connect to YugabyteDB considering it as PostgreSQL. Change the port from `5432` to `5433`.
Project: KICS (Provisioning / Security & Compliance)
File: a68da022-e95a-4bc2-97d3-481e0bd6d446.md

title: Components Header Definition Is Unused hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a68da022-e95a-4bc2-97d3-481e0bd6d446 Query name: Components Header Definition Is Unused Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: Components headers definitions should be referenced or removed from Open API definition<br> ```json title="Positive test num. 1 - json file" hl_lines="45" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "success", "content": { "application/json": { "schema": { "type": "array", "items": { "$ref": "#/components/schemas/MyObject" } } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "headers": { "xPages": { "schema": { "type": "integer", "description": "number of pages" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="29" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: success content: application/json: schema: type: array items: "$ref": "#/components/schemas/MyObject" components: schemas: MyObject: type: object properties: id: type: string name: type: string headers: xPages: schema: type: integer description: number of pages ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "success", "content": { "application/json": { "schema": { "type": "array", "items": { "$ref": "#/components/schemas/MyObject" } }, "headers": { "X-Pages": { "$ref": "#/components/headers/xPages" } } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "headers": { "xPages": { "schema": { "type": "integer", "description": "number of pages" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: success content: application/json: schema: type: array items: "$ref": "#/components/schemas/MyObject" headers: X-Pages: "$ref": "#/components/headers/xPages" components: schemas: MyObject: type: object properties: id: type: string name: type: string headers: xPages: schema: type: integer description: number of pages ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Tablestore.md

Tablestore sink connector Write data to `Tablestore` | name | type | required | default value | |-|--|-|| | end_point | string | yes | - | | instance_name | string | yes | - | | accesskeyid | string | yes | - | | accesskeysecret | string | yes | - | | table | string | yes | - | | primary_keys | array | yes | - | | batch_size | string | no | 25 | | common-options | config | no | - | endPoint to write to Tablestore. The instanceName of Tablestore. The access id of Tablestore. The access secret of Tablestore. The table of Tablestore. The primaryKeys of Tablestore. Sink plugin common parameters, please refer to for details. ```bash Tablestore { end_point = "xxxx" instance_name = "xxxx" accesskeyid = "xxxx" accesskeysecret = "xxxx" table = "sink" primarykeys = ["pk1","pk2","pk3","pk_4"] } ``` Add Tablestore Sink Connector
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-typeof.md

title: jsonbtypeof() and jsontypeof() headerTitle: jsonbtypeof() and jsontypeof() linkTitle: jsonb_typeof() description: Return the data type of the JSON value as a SQL text value. menu: v2.18: identifier: jsonb-typeof parent: json-functions-operators weight: 250 type: docs Purpose: Return the data type of the JSON value as a SQL `text` value. Signature For the `jsonb` variant: ``` input value: jsonb return value: text ``` Notes: Possible return values are string, number, boolean, null, object, and array, as follows. ```plpgsql do $body$ declare j_string constant jsonb := '"dog"'; j_number constant jsonb := '42'; j_boolean constant jsonb := 'true'; j_null constant jsonb := 'null'; j_object constant jsonb := '{"a": 17, "b": "x", "c": true}'; j_array constant jsonb := '[17, "x", true]'; begin assert jsonbtypeof(jstring) = 'string' and jsonbtypeof(jnumber) = 'number' and jsonbtypeof(jboolean) = 'boolean' and jsonbtypeof(jnull) = 'null' and jsonbtypeof(jobject) = 'object' and jsonbtypeof(jarray) = 'array', 'unexpected'; end; $body$; ```
Project: KICS (Provisioning / Security & Compliance)
File: 41a38329-d81b-4be4-aef4-55b2615d3282.md

title: RAM Account Password Policy Not Required Symbols hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 41a38329-d81b-4be4-aef4-55b2615d3282 Query name: RAM Account Password Policy Not Required Symbols Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Secret Management URL: RAM account password security should require at least one symbol<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "alicloudramaccountpasswordpolicy" "corporate2" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudramaccountpasswordpolicy" "corporate1" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = true hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.pc.md

/ / pc .pc command(`cmdline`): `string` | Name | Type | | :-- | :- | | `cmdline` | `string` | `string` examples(`examples`, `sectionTitle?`): `string` | Name | Type | Default value | | :- | :- | : | | `examples` | `Example`[] | `undefined` | | `sectionTitle` | `string` | `'Examples'` | `string` intro(`paragraph`): `string` | Name | Type | | :- | :- | | `paragraph` | `string` | `string` option(`opts`): `string` | Name | Type | | :-- | : | | `opts` | `string` \| `string`[] | `string` options(`options`): `string` | Name | Type | | :-- | : | | `options` | `Option`[] | `string` pipeline(`code`): `string` | Name | Type | | :-- | :- | | `code` | `string` | `string` pretty-printed version of the given bash pipeline related(`related`): `string` | Name | Type | | :-- | : | | `related` | `string`[] | `string` title(`_`): `string` | Name | Type | | : | : | | `_` | `Title` | `string` usage(`usages`): `string` | Name | Type | | :- | : | | `usages` | `string`[] | `string`
Project: Qdrant (App Definition and Development / Database)
File: CONTRIBUTING.md

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's: Reporting a bug Discussing the current state of the code Submitting a fix Proposing new features We use github to host code, to track issues and feature requests, as well as accept pull requests. Pull requests are the best way to propose changes to the codebase (we use ). We actively welcome your pull requests: Fork the repo and create your branch from `dev`. If you've added code that should be tested, add tests. If you've changed APIs, update the documentation and API Schema definitions (see ) Ensure the test suite passes. Make sure your code lints (with cargo). Issue that pull request! In short, when you submit code changes, your submissions are understood to be under the same that covers the project. Feel free to contact the maintainers if that's a concern. We use GitHub issues to track public bugs. Report a bug by ; it's that easy! Great Bug Reports tend to have: A quick summary and/or background Steps to reproduce Be specific! Give sample code if you can. What you expected would happen What actually happens Notes (possibly including why you think this might be happening, or stuff you tried that didn't work) If you are modifying Rust code, make sure it has no warnings from Cargo and follow . The project uses formatter. Please ensure to run it using the ```cargo +nightly fmt --all``` command. The project also use lint collection, so please ensure running ``cargo clippy --workspace --all-features`` before submitting the PR. By contributing, you agree that your contributions will be licensed under its Apache License 2.0.
Project: KICS (Provisioning / Security & Compliance)
File: 128df7ec-f185-48bc-8913-ce756a3ccb85.md

title: Outdated GKE Version hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 128df7ec-f185-48bc-8913-ce756a3ccb85 Query name: Outdated GKE Version Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Running outdated versions of Google Kubernetes Engine (GKE) can expose it to known vulnerabilities and attacks. To reduce these risks, it is recommended to ensure that GKE is always running the latest version.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="25 2" resource "googlecontainercluster" "positive1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 master_auth { username = "" password = "" clientcertificateconfig { issueclientcertificate = false } } timeouts { create = "30m" update = "40m" } minmasterversion = "1.24" } resource "googlecontainercluster" "positive2" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 master_auth { username = "" password = "" clientcertificateconfig { issueclientcertificate = false } } timeouts { create = "30m" update = "40m" } node_version = "1.24" } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecontainercluster" "negative1" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 master_auth { username = "" password = "" clientcertificateconfig { issueclientcertificate = false } } timeouts { create = "30m" update = "40m" } minmasterversion = "latest" } resource "googlecontainercluster" "negative2" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 master_auth { username = "" password = "" clientcertificateconfig { issueclientcertificate = false } } timeouts { create = "30m" update = "40m" } minmasterversion = "1.25" } resource "googlecontainercluster" "negative3" { name = "marcellus-wallace" location = "us-central1-a" initialnodecount = 3 master_auth { username = "" password = "" clientcertificateconfig { issueclientcertificate = false } } timeouts { create = "30m" update = "40m" } minmasterversion = "1.25" node_version = "1.25" } ```
Project: ClickHouse (App Definition and Development / Database)
File: one.md

slug: /en/operations/system-tables/one This table contains a single row with a single `dummy` UInt8 column containing the value 0. This table is used if a `SELECT` query does not specify the `FROM` clause. This is similar to the `DUAL` table found in other DBMSs. Example ```sql SELECT * FROM system.one LIMIT 10; ``` ```response dummy 0 1 rows in set. Elapsed: 0.001 sec. ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_rm.md

<!MARKERGENSTART--> Removes stopped service containers By default, anonymous volumes attached to containers will not be removed. You can override this with -v. To list all volumes, use "docker volume ls". Any data which is not in a volume will be lost. | Name | Type | Default | Description | |:|:--|:--|:-| | `--dry-run` | | | Execute command in dry run mode | | `-f`, `--force` | | | Don't ask to confirm removal | | `-s`, `--stop` | | | Stop the containers, if required, before removing | | `-v`, `--volumes` | | | Remove any anonymous volumes attached to containers | <!MARKERGENEND--> Removes stopped service containers. By default, anonymous volumes attached to containers are not removed. You can override this with `-v`. To list all volumes, use `docker volume ls`. Any data which is not in a volume is lost. Running the command with no options also removes one-off containers created by `docker compose run`: ```console $ docker compose rm Going to remove djangoquickstartwebrun_1 Are you sure? [yN] y Removing djangoquickstartwebrun_1 ... done ```