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

slug: /en/operations/system-tables/asynchronous_inserts Contains information about pending asynchronous inserts in queue. Columns: `query` () Query string. `database` () The name of the database the table is in. `table` () Table name. `format` () Format name. `first_update` () First insert time with microseconds resolution. `total_bytes` () Total number of bytes waiting in the queue. `entries.query_id` () - Array of query ids of the inserts waiting in the queue. `entries.bytes` () - Array of bytes of each insert query waiting in the queue. Example Query: ``` sql SELECT * FROM system.asynchronous_inserts LIMIT 1 \G; ``` Result: ``` text Row 1: query: INSERT INTO public.dataguess (userid, datasource_id, timestamp, path, type, num, str) FORMAT CSV database: public table: data_guess format: CSV first_update: 2023-06-08 10:08:54.199606 total_bytes: 133223 entries.query_id: ['b46cd4c4-0269-4d0b-99f5-d27668c6102e'] entries.bytes: [133223] ``` See Also Description of the `query_log` system table which contains common information about queries execution. This table contains information about async inserts performed.
Project: KICS (Provisioning / Security & Compliance)
File: 0f04217d-488f-4e7a-bec8-f16159686cd6.md

title: DynamoDB Table Point In Time Recovery Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0f04217d-488f-4e7a-bec8-f16159686cd6 Query name: DynamoDB Table Point In Time Recovery Disabled Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Best Practices URL: It's considered a best practice to have point in time recovery enabled for DynamoDB Table<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: PointInTimeRecoverySpecification: PointInTimeRecoveryEnabled: false ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: TableName: my-table ``` ```json title="Positive test num. 3 - json file" hl_lines="8" { "Resources": { "DynamoDBOnDemandTable1": { "Type": "AWS::DynamoDB::Table", "Properties": { "BillingMode": "PAYPERREQUEST", "PointInTimeRecoverySpecification" : { "PointInTimeRecoveryEnabled" : false } } }, "AWSTemplateFormatVersion": "2010-09-09", "Description": "Sample CloudFormation template for DynamoDB with customer managed CMK" } } ``` <details><summary>Positive test num. 4 - json file</summary> ```json hl_lines="5" { "Resources": { "DynamoDBOnDemandTable1": { "Type": "AWS::DynamoDB::Table", "Properties": { "BillingMode": "PAYPERREQUEST" } }, "AWSTemplateFormatVersion": "2010-09-09", "Description": "Sample CloudFormation template for DynamoDB with customer managed CMK" } } ``` </details> <details><summary>Positive test num. 5 - yaml file</summary> ```yaml hl_lines="5" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: PointInTimeRecoverySpecification: {} ``` </details> <details><summary>Positive test num. 6 - json file</summary> ```json hl_lines="7" { "Resources": { "DynamoDBOnDemandTable1": { "Type": "AWS::DynamoDB::Table", "Properties": { "BillingMode": "PAYPERREQUEST", "PointInTimeRecoverySpecification" : {} } }, "AWSTemplateFormatVersion": "2010-09-09", "Description": "Sample CloudFormation template for DynamoDB with customer managed CMK" } } ``` </details> ```yaml title="Negative test num. 1 - yaml file" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: PointInTimeRecoverySpecification: PointInTimeRecoveryEnabled: true ``` ```json title="Negative test num. 2 - json file" { "Resources": { "DynamoDBOnDemandTable1": { "Type": "AWS::DynamoDB::Table", "Properties": { "BillingMode": "PAYPERREQUEST", "PointInTimeRecoverySpecification" : { "PointInTimeRecoveryEnabled" : true } } }, "AWSTemplateFormatVersion": "2010-09-09", "Description": "Sample CloudFormation template for DynamoDB with customer managed CMK" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 6e8849c1-3aa7-40e3-9063-b85ee300f29f.md

title: SQS With SSE Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6e8849c1-3aa7-40e3-9063-b85ee300f29f Query name: SQS With SSE Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Amazon Simple Queue Service (SQS) queue should protect the contents of their messages using Server-Side Encryption (SSE)<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awssqsqueue" "positive1" { name = "terraform-example-queue" kmsdatakeyreuseperiod_seconds = 300 } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="3" resource "awssqsqueue" "positive2" { name = "terraform-example-queue" kmsmasterkey_id = "" kmsdatakeyreuseperiod_seconds = 300 } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="1" resource "awssqsqueue" "positive3" { name = "terraform-example-queue" kmsmasterkey_id = null kmsdatakeyreuseperiod_seconds = 300 } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="1" module "user_queue" { source = "terraform-aws-modules/sqs/aws" version = "~> 2.0" name = "user" tags = { Service = "user" Environment = "dev" } } ``` </details> <details><summary>Positive test num. 5 - tf file</summary> ```tf hl_lines="12" module "user_queue" { source = "terraform-aws-modules/sqs/aws" version = "~> 2.0" name = "user" tags = { Service = "user" Environment = "dev" } kmsmasterkey_id = "" } ``` </details> <details><summary>Positive test num. 6 - tf file</summary> ```tf hl_lines="1" module "user_queue" { source = "terraform-aws-modules/sqs/aws" version = "~> 2.0" name = "user" tags = { Service = "user" Environment = "dev" } kmsmasterkey_id = null } ``` </details> <details><summary>Positive test num. 7 - tf file</summary> ```tf hl_lines="3" resource "awssqsqueue" "positive7" { name = "terraform-example-queue" sqsmanagedsse_enabled = false } ``` </details> ```tf title="Negative test num. 1 - tf file" resource "awssqsqueue" "negative1" { name = "terraform-example-queue" kmsmasterkey_id = "alias/aws/sqs" kmsdatakeyreuseperiod_seconds = 300 } ``` ```tf title="Negative test num. 2 - tf file" module "user_queue" { source = "terraform-aws-modules/sqs/aws" version = "~> 2.0" name = "user" tags = { Service = "user" Environment = "dev" } kmsmasterkey_id = "alias/aws/sqs" } ``` ```tf title="Negative test num. 3 - tf file" resource "awssqsqueue" "negative3" { name = "terraform-example-queue" sqsmanagedsse_enabled = true } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.48.md

layout: release date: 2023-02-02 tag: v0.6.48 language: en Revert Makefile.core.mk @acald-creator (#6961) improve debug logs for the `mesheryctl pattern apply` cmd @ayushthe1 (#6935) error messages for mesheryctl system and mesheryctl system token improved @deepakdinesh1123 (#6955) Bump postcss from 8.4.20 to 8.4.21 in /ui @dependabot (#6974) add svg for published @MUzairS15 (#6970) Dark theme of meshery @Harshit-Dandriyal (#6527) Telemetry Providers @MUzairS15 (#6868) [UI] Move to small icon for rjsf custom components @Chadha93 (#6962) Bump postcss from 8.4.20 to 8.4.21 in /ui @dependabot (#6974) Bump github.com/briandowns/spinner from 1.19.0 to 1.20.0 @dependabot (#6978) [Server] Designs: add share functionality @MUzairS15 (#6950) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @MUzairS15, @Revolyssup, @acald-creator, @ayushthe1, @deepakdinesh1123, @dependabot, @dependabot[bot], @l5io, @leecalcote and l5io
Project: ArangoDB (App Definition and Development / Database)
File: is_error_code_available.md

+++ title = "`iserrorcode_available<T>`" description = "True if an error code can be constructed from a `T`." +++ `::value` is true if an error code can be constructed from a `T` e.g. if there exists an ADL discovered free function `makeerrorcode(T)`. `::type` is the type that would result if `::value` is true, else `void`. Overridable: By template specialisation into the `trait` namespace. Default: True if `T` is an error code, else to metaprogramming which performs the ADL discovery of `makeerrorcode(T)`. Note that the STL defines multiple overloads of an ADL discovered free function {{% api "std::makeerrorcode(T)" %}} for its error enumerations, as does Boost.System for the Boost error enumerations. Thus this trait will pick up those free functions for those error types. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::trait` Header: `<boost/outcome/trait.hpp>` Variable alias: `iserrorcodeavailablev<T>`
Project: Harbor (Provisioning / Container Registry)
File: 7-14-Endpoints-endpoints-delete.md

Test 7-14 Endpoints endpoint delete ======= To verify admin user can delete an endpoint. User guide This test requires one Harbor instance is running and available. At least one endpoint should exist. Login UI as admin user. In `Administration->Registries` page, delete an endpoint in use by a rule. In `Administration->Registries` page, delete an endpoint not in use by a rule. In step2, endpoint can not be deleted. In step3, endpoint can be deleted. None
Project: StarRocks (App Definition and Development / Database)
File: grouping_id.md

displayed_sidebar: "English" grouping_id is used to distinguish the grouping statistics results of the same grouping standard. ```Haskell GROUPING_ID(expr) ``` ```Plain MySQL > SELECT COL1,GROUPING_ID(COL2) AS 'GroupingID' FROM tbl GROUP BY ROLLUP (COL1, COL2); +++ | COL1 | GroupingID | +++ | NULL | 1 | | 2.20 | 1 | | 2.20 | 0 | | 1.10 | 1 | | 1.10 | 0 | +++ ```
Project: Falco (Provisioning / Security & Compliance)
File: 20200818-artifacts-storage.md

This document reflects the way we store the Falco artifacts. Bintray: artifacts distribution platform The Falco packages are automatically built and sent to in the following cases: a pull request gets merged into the master branch (Falco development releases) a new Falco release (git tag) happens on the master branch (Falco stable releases) The only prerequisite is that the specific Falco source code builds successfully and that the tests pass. As per proposal we provide three kind of Falco packages: DEB RPM Tarball Thus, we have three repositories for the Falco stable releases: https://bintray.com/falcosecurity/deb https://bintray.com/falcosecurity/rpm https://bintray.com/falcosecurity/bin And three repositories for the Falco development releases: https://bintray.com/falcosecurity/deb-dev https://bintray.com/falcosecurity/rpm-dev https://bintray.com/falcosecurity/bin-dev The process of publishing a set of prebuilt Falco drivers is implemented by the Drivers Build Grid (DBG) in the repository (`driverkit` directory). This process is driven by the configuration files (YAML) present in the `driverkit/config` directory in the repository. Each of these files represents a prebuilt driver (eventually two: kernel module and eBPF probe, when possible) that will be published on if it builds correctly. Every time the `driverkit/config` directory on the master branch has some changes from the previous commit the CI system, which you can find defined in the file, takes care of building and publishing all the drivers. The driver versions we ship prebuilt drivers for are: the driver version associated with the last Falco stable version () the driver version associated with the penultimate Falco stable version The prebuilt drivers get published into generic artifacts repository. You can also visualize the full list of prebuilt drivers by driver version visiting this . The generation of new prebuilt drivers takes usually place with a frequency of 1-2 weeks, on a best-effort basis. Thus, it can happen the list of available prebuilt drivers does not yet contain the driver version currently on Falco master. Nevertheless, this process is an open, auditable, and transparent one. So, by sending a pull-request towards repository containing the configuration YAML files you can help the Falco community stay on track. Some pull-requests you can look at to create your own are: https://github.com/falcosecurity/test-infra/pull/165 https://github.com/falcosecurity/test-infra/pull/163 https://github.com/falcosecurity/test-infra/pull/162 While, the documentation of the YAML configuration files can be found . As per Falco packages, also the Falco official container images are automatically published to the . These images are built and published in two cases: a pull request gets merged into the master branch (Falco development releases) a new Falco release (git tag) happens (Falco stable releases) For a detailed explanation of the container images we build and ship look at the following .
Project: Parsec (Provisioning / Security & Compliance)
File: README.md

<!-- -- Copyright 2019 Contributors to the Parsec project. -- SPDX-License-Identifier: Apache-2.0 > <p align="center"> <img src="./doc/images/parsec/ARM1007PARSEC LogoST2RGBStacked_Colour.png" alt="Parsec logo"/> <br><br> <a href="https://crates.io/crates/parsec-service"><img alt="Crates.io" src="https://img.shields.io/crates/v/parsec-service"></a> <a href="https://docs.rs/parsec-service"><img src="https://docs.rs/parsec-service/badge.svg" alt="Code documentation"/></a> <a href="https://bestpractices.coreinfrastructure.org/projects/4856"><img src="https://bestpractices.coreinfrastructure.org/projects/4856/badge"></a> <a href="https://codecov.io/gh/parallaxsecond/parsec"><img src="https://codecov.io/gh/parallaxsecond/parsec/branch/main/graph/badge.svg?token=FbpUGoN331"/></a> </p> PARSEC is the Platform AbstRaction for SECurity, an open-source initiative to provide a common API to hardware security and cryptographic services in a platform-agnostic way. This abstraction layer keeps workloads decoupled from physical platform details, enabling cloud-native delivery flows within the data center and at the edge. <p align="center"> <img src="./doc/images/parsec/ParsecConceptDiagram.png" alt="Parsec Concept Diagram"/> </p> Read the Parsec documentation . Read the whitepaper . Use Parsec when you need: A portable interface to your platform's Root of Trust in order to manage keys and perform cryptographic operations without knowledge of the hardware. A simple and portable way to access the best available security of your platform in your preferred programming language. The value proposition of Parsec is that it provides the following: Abstraction a common API that is truly agnostic and based on modern cryptographic principles Mediation security as a microservice, brokering access to the hardware and providing isolated key stores in a multi-tenant environment Ergonomics a client library ecosystem that brings the API to the fingertips of developers in any programming language: easy to consume, hard to get wrong Openness an open-source project inviting contributions to enhance the ecosystem both within the service and among its client libraries PARSEC is a collaborative project. The current list of the individuals and organizations who maintain this project can be found . See who is . If you are running on x86 Linux, check out to get started with Parsec quickly! For examples of how to access PARSEC as a client application, check . Check the , and guides for more information on building, installing, testing and using Parsec! Come and ask questions or talk with the Parsec Community in our Slack channel or biweekly meetings. See the repository for more information on how to join. We would be happy for you to contribute to Parsec! Please check the to know more about the contribution process. Check the on the board if you need any ideas ! Check . The software is provided under Apache-2.0. Contributions to this project are accepted under the same license.
Project: ShardingSphere (App Definition and Development / Database)
File: openGauss.en.md

+++ title = "The Cooperation Between ShardingSphere and openGauss" weight = 1 chapter = true +++ On May 29th, the "[Beijing] openGauss Meetup" event hosted by the openGauss community and jointly hosted by Beijing Kunpeng Joint Innovation Center, ENMOTECH, SANGFOR, and SphereEx was successfully held at Zhongguancun, Beijing. This Meetup is also the first joint event after SphereEx officially joined the openGauss community. At the Meetup site, Zhang Liang, CEO of SphereEx, shared the theme of "The Cooperation Between ShardingSphere and openGauss". {{< qq m3250lnfeir >}}
Project: KICS (Provisioning / Security & Compliance)
File: 8bc2168c-1723-4eeb-a6f3-a1ba614b9a6d.md

title: IAM Password Without Minimum Length hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8bc2168c-1723-4eeb-a6f3-a1ba614b9a6d Query name: IAM Password Without Minimum Length Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: IAM password should have the required minimum length<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="16 2 27" name: Password policy for AWS account community.aws.iampasswordpolicy: state: present require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: true pwmaxage: 60 pwreuseprevent: 5 pw_expire: false name: awsiamaccountpasswordpolicy community.aws.iampasswordpolicy: state: present minpwlength: 3 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: true pwmaxage: 60 pwreuseprevent: 5 pw_expire: false name: awsiamaccountpasswordpolicy_2 community.aws.iampasswordpolicy: state: present minimumpasswordlength: 3 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: true pwmaxage: 60 pwreuseprevent: 5 pw_expire: false ``` ```yaml title="Negative test num. 1 - yaml file" name: Password policy for AWS account community.aws.iampasswordpolicy: state: present minpwlength: 8 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: true pwmaxage: 60 pwreuseprevent: 5 pw_expire: false name: awsiamaccountpasswordpolicy community.aws.iampasswordpolicy: state: present minimumpasswordlength: 8 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: true pwmaxage: 60 pwreuseprevent: 5 pw_expire: false ```
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 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 or screenshots about the feature request here.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: ipc.md

Set the IPC namespace mode for a container. The default is to create a private IPC namespace. "": Use Podman's default, defined in containers.conf. container:id: reuses another container's shared memory, semaphores, and message queues host: use the host's shared memory, semaphores, and message queues inside the container. Note: the host mode gives the container full access to local shared memory and is therefore considered insecure. none: private IPC namespace, with /dev/shm not mounted. ns:path: path to an IPC namespace to join. private: private IPC namespace. shareable: private IPC namespace with a possibility to share it with other containers.
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-agg.md

title: jsonb_agg() headerTitle: jsonb_agg() linkTitle: jsonb_agg() description: Aggregate a SETOF values into a JSON array. menu: v2.18: identifier: jsonb-agg parent: json-functions-operators weight: 57 type: docs Purpose: This is an aggregate function. (Aggregate functions compute a single result from a `SETOF` input SQL values.) It creates a JSON array whose values are the JSON representations of the aggregated SQL values. Signature: ``` input value: SETOF anyelement return value: jsonb ``` Notes: The syntax "order by column1 nulls first" within the parentheses of the aggregate function is not specific to `jsonb_agg()`. Rather, it is a generic feature of aggregate functions. The same syntax is used with the function for SQL arrays. ```plpgsql create type rt as (key1 int, key2 text); do $body$ declare agg jsonb; expected_agg constant jsonb not null := '[ {"key1": null, "key2": "ant"}, {"key1": 1, "key2": "dog"}, {"key1": 2, "key2": "cat"}, {"key1": 4, "key2": null }, {"key1": 5, "key2": "ant"} ]'::jsonb; begin with tab as ( values (5::int, 'ant'::text), (2::int, 'cat'::text), (null::int, 'ant'::text), (1::int, 'dog'::text), (4::int, null::text)) select json_agg((column1, column2)::rt order by column1 nulls first) into strict agg from tab; assert (agg = expected_agg), 'unexpected'; end; $body$; ``` You can also aggregate SQL arrays into a ragged JSON array of JSON arrays like this: ```plpgsql do $body$ declare agg jsonb not null := '"?"'; expected_agg constant jsonb not null := '[ ["a", "b", "c"], ["d" ], ["e", "f" ] ]'::jsonb; begin with tab as ( values (array['a', 'b', 'c']::text[]), (array['d' ]::text[]), (array['e', 'f' ]::text[])) select json_agg((column1)::text[] order by column1 nulls first) into strict agg from tab; assert (agg = expected_agg), 'unexpected'; end; $body$; ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_top.md

<!MARKERGENSTART--> Display the running processes | Name | Type | Default | Description | |:|:--|:--|:--| | `--dry-run` | | | Execute command in dry run mode | <!MARKERGENEND--> Displays the running processes ```console $ docker compose top examplefoo1 UID PID PPID C STIME TTY TIME CMD root 142353 142331 2 15:33 ? 00:00:00 ping localhost -c 5 ```
Project: KICS (Provisioning / Security & Compliance)
File: 38300d1a-feb2-4a48-936a-d1ef1cd24313.md

title: Missing Zypper Clean hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 38300d1a-feb2-4a48-936a-d1ef1cd24313 Query name: Missing Zypper Clean Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Reduce layer and image size by deleting unneeded caches after running zypper<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2" FROM busybox:1.0 RUN zypper install HEALTHCHECK CMD curl --fail http://localhost:3000 || exit 1 ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM busybox:1.0 RUN zypper install -y httpd=2.4 && zypper clean HEALTHCHECK CMD curl --fail http://localhost:3000 || exit 1 ``` ```dockerfile title="Negative test num. 2 - dockerfile file" FROM golang:1.16 AS builder WORKDIR /go/src/github.com/foo/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go ./ RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app . RUN zypper install FROM alpine:latest RUN apk --no-cache add ca-certificates WORKDIR /root/ COPY --from=builder /go/src/github.com/foo/href-counter/app ./ CMD ["./app"] RUN useradd -ms /bin/bash patrick USER patrick ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-manifest-rm.1.md

% podman-manifest-rm 1 podman\-manifest\-rm - Remove manifest list or image index from local storage podman manifest rm list-or-index [...] Removes one or more locally stored manifest lists. podman manifest rm `<list>` podman manifest rm listid1 listid2 storage.conf (`/etc/containers/storage.conf`) storage.conf is the storage configuration file for all tools using containers/storage The storage configuration file specifies all of the available container storage options for tools using shared container storage. , ,