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

slug: /en/sql-reference/statements/select/from sidebar_label: FROM The `FROM` clause specifies the source to read data from: and clauses may also be used to extend the functionality of the `FROM` clause. Subquery is another `SELECT` query that may be specified in parenthesis inside `FROM` clause. `FROM` clause can contain multiple data sources, separated by commas, which is equivalent of performing on them. When `FINAL` is specified, ClickHouse fully merges the data before returning the result. This also performs all data transformations that happen during merges for the given table engine. It is applicable when selecting data from from tables using the following table engines: `ReplacingMergeTree` `SummingMergeTree` `AggregatingMergeTree` `CollapsingMergeTree` `VersionedCollapsingMergeTree` `SELECT` queries with `FINAL` are executed in parallel. The setting limits the number of threads used. Queries that use `FINAL` execute slightly slower than similar queries that do not use `FINAL` because: Data is merged during query execution. Queries with `FINAL` may read primary key columns in addition to the columns specified in the query. `FINAL` requires additional compute and memory resources because the processing that normally would occur at merge time must occur in memory at the time of the query. However, using FINAL is sometimes necessary in order to produce accurate results (as data may not yet be fully merged). It is less expensive than running `OPTIMIZE` to force a merge. As an alternative to using `FINAL`, it is sometimes possible to use different queries that assume the background processes of the `MergeTree` engine have not yet occurred and deal with it by applying an aggregation (for example, to discard duplicates). If you need to use `FINAL` in your queries in order to get the required results, it is okay to do so but be aware of the additional processing required. `FINAL` can be applied automatically using setting to all tables in a query using a session or a user profile. Using the `FINAL` keyword ```sql SELECT x, y FROM mytable FINAL WHERE x > 1; ``` Using `FINAL` as a query-level setting ```sql SELECT x, y FROM mytable WHERE x > 1 SETTINGS final = 1; ``` Using `FINAL` as a session-level setting ```sql SET final = 1; SELECT x, y FROM mytable WHERE x > 1; ``` If the `FROM` clause is omitted, data will be read from the `system.one` table. The `system.one` table contains exactly one row (this table fulfills the same purpose as the DUAL table found in other DBMSs). To execute a query, all the columns listed in the query are extracted from the appropriate table. Any columns not needed for the external query are thrown out of the subqueries. If a query does not list any columns (for example, `SELECT count() FROM t`), some column is extracted from the table anyway (the smallest one is preferred), in order to calculate the number of rows.
Project: Kapitan (Provisioning / Automation & Configuration)
File: 2023-06-01.md

author: Alessandro De Maria authorghuser: ademariag read_time: 10m date: 2022-12-04 The Kapicorp team is happy to to announce a new release of Kapitan. This release contains loads of improvements for the past 6 months, the majority of which have been contributions from our community! Head over our on GitHub for a full list of features and contributors. Please help us by visiting our page.
Project: KICS (Provisioning / Security & Compliance)
File: 084c6686-2a70-4710-91b1-000393e54c12.md

title: Shield Advanced Not In Use hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 084c6686-2a70-4710-91b1-000393e54c12 Query name: Shield Advanced Not In Use Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: AWS Shield Advanced should be used for Amazon Route 53 hosted zone, AWS Global Accelerator accelerator, Elastic IP Address, Elastic Load Balancing, and Amazon CloudFront Distribution to protect these resources against robust DDoS attacks<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" data "awsavailabilityzones" "available" {} data "aws_region" "current" {} data "awscalleridentity" "current" {} resource "aws_eip" "positive1" { vpc = true } resource "awsshieldprotection" "positive1" { name = "example" resourcearn = "arn:aws:ec2:${data.awsregion.current.name}:${data.awscalleridentity.current.accountid}:eip-allocation/${awseip.positive.id}" tags = { Environment = "Dev" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awsroute53zone" "positive2" { name = "example.com" } resource "awsshieldprotection" "positive2" { name = "example" resourcearn = awsroute53_zone.positive.arn tags = { Environment = "Dev" } } ``` ```tf title="Negative test num. 1 - tf file" data "awsavailabilityzones" "available" {} data "aws_region" "current" {} data "awscalleridentity" "current" {} resource "aws_eip" "negative1" { vpc = true } resource "awsshieldprotection" "negative1" { name = "example" resourcearn = "arn:aws:ec2:${data.awsregion.current.name}:${data.awscalleridentity.current.accountid}:eip-allocation/${awseip.negative1.id}" tags = { Environment = "Dev" } } ``` ```tf title="Negative test num. 2 - tf file" resource "awsroute53zone" "negative2" { name = "example.com" } resource "awsshieldprotection" "negative2" { name = "example" resourcearn = awsroute53_zone.negative2.arn tags = { Environment = "Dev" } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: mount.md

+++ title = "mount resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "mount" identifier = "inspec/resources/os/mount.md mount resource" parent = "inspec/resources/os" +++ Use the `mount` Chef InSpec audit resource to test the mount points on FreeBSD and Linux systems. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. An `mount` resource block declares the synchronization settings that should be tested: describe mount('path') do it { should MATCHER 'value' } end where `('path')` is the path to the mounted directory `MATCHER` is a valid matcher for this resource `'value'` is the value to be tested The following examples show how to use this Chef InSpec audit resource. describe mount('/') do it { should be_mounted } its('device') { should eq '/dev/mapper/VolGroup-lv_root' } its('type') { should eq 'ext4' } its('options') { should eq ['rw', 'mode=620'] } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `be_mounted` matcher tests if the file is accessible from the file system: it { should be_mounted } The `device` matcher tests the device from the `fstab` table: its('device') { should eq '/dev/mapper/VolGroup-lv_root' } The `options` matcher tests the mount options for the file system from the `fstab` table: its('options') { should eq ['rw', 'mode=620'] } The `type` matcher tests the file system type: its('type') { should eq 'ext4' }
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: scaler.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: website spec: components: name: frontend type: webservice properties: image: nginx traits: type: scaler properties: replicas: 2 type: sidecar properties: name: "sidecar-test" image: "fluentd" name: backend type: worker properties: image: busybox cmd: sleep '1000' ```
Project: ClickHouse (App Definition and Development / Database)
File: uniqhll12.md

slug: /en/sql-reference/aggregate-functions/reference/uniqhll12 sidebar_position: 194 Calculates the approximate number of different argument values, using the algorithm. ``` sql uniqHLL12(x[, ...]) ``` Arguments The function takes a variable number of parameters. Parameters can be `Tuple`, `Array`, `Date`, `DateTime`, `String`, or numeric types. Returned value A -type number. Implementation details Function: Calculates a hash for all parameters in the aggregate, then uses it in calculations. Uses the HyperLogLog algorithm to approximate the number of different argument values. 2^12 5-bit cells are used. The size of the state is slightly more than 2.5 KB. The result is not very accurate (up to ~10% error) for small data sets (<10K elements). However, the result is fairly accurate for high-cardinality data sets (10K-100M), with a maximum error of ~1.6%. Starting from 100M, the estimation error increases, and the function will return very inaccurate results for data sets with extremely high cardinality (1B+ elements). Provides the determinate result (it does not depend on the query processing order). We do not recommend using this function. In most cases, use the or function. See Also
Project: KICS (Provisioning / Security & Compliance)
File: 8152e0cf-d2f0-47ad-96d5-d003a76eabd1.md

title: Lambda Functions Without X-Ray Tracing hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8152e0cf-d2f0-47ad-96d5-d003a76eabd1 Query name: Lambda Functions Without X-Ray Tracing Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: AWS Lambda functions should have TracingConfig enabled. For this, property 'tracing_Config.mode' should have the value 'Active'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="28 45" resource "awsiamrole" "iamforlambda2" { name = "iamforlambda" assumerolepolicy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Principal": { "Service": "lambda.amazonaws.com" }, "Effect": "Allow", "Sid": "" } ] } EOF } resource "awslambdafunction" "test_lambda2" { filename = "lambdafunctionpayload.zip" functionname = "lambdafunction_name" role = awsiamrole.iamforlambda.arn handler = "exports.test" tracing_config { mode = "PassThrough" } sourcecodehash = filebase64sha256("lambdafunctionpayload.zip") runtime = "nodejs12.x" environment { variables = { foo = "bar" } } } resource "awslambdafunction" "test_lambda3" { filename = "lambdafunctionpayload.zip" functionname = "lambdafunction_name" role = awsiamrole.iamforlambda.arn handler = "exports.test" sourcecodehash = filebase64sha256("lambdafunctionpayload.zip") runtime = "nodejs12.x" environment { variables = { foo = "bar" } } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamrole" "iamforlambda" { name = "iamforlambda" assumerolepolicy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Principal": { "Service": "lambda.amazonaws.com" }, "Effect": "Allow", "Sid": "" } ] } EOF } resource "awslambdafunction" "test_lambda" { filename = "lambdafunctionpayload.zip" functionname = "lambdafunction_name" role = awsiamrole.iamforlambda.arn handler = "exports.test" tracing_config { mode = "Active" } sourcecodehash = filebase64sha256("lambdafunctionpayload.zip") runtime = "nodejs12.x" environment { variables = { foo = "bar" } } } ```
Project: ClickHouse (App Definition and Development / Database)
File: int-uint.md

slug: /en/sql-reference/data-types/int-uint sidebar_position: 2 sidebar_label: UInt8, UInt16, UInt32, UInt64, UInt128, UInt256, Int8, Int16, Int32, Int64, Int128, Int256 Fixed-length integers, with or without a sign. When creating tables, numeric parameters for integer numbers can be set (e.g. `TINYINT(8)`, `SMALLINT(16)`, `INT(32)`, `BIGINT(64)`), but ClickHouse ignores them. `Int8` \[-128 : 127\] `Int16` \[-32768 : 32767\] `Int32` \[-2147483648 : 2147483647\] `Int64` \[-9223372036854775808 : 9223372036854775807\] `Int128` \[-170141183460469231731687303715884105728 : 170141183460469231731687303715884105727\] `Int256` \[-57896044618658097711785492504343953926634992332820282019728792003956564819968 : 57896044618658097711785492504343953926634992332820282019728792003956564819967\] Aliases: `Int8` `TINYINT`, `INT1`, `BYTE`, `TINYINT SIGNED`, `INT1 SIGNED`. `Int16` `SMALLINT`, `SMALLINT SIGNED`. `Int32` `INT`, `INTEGER`, `MEDIUMINT`, `MEDIUMINT SIGNED`, `INT SIGNED`, `INTEGER SIGNED`. `Int64` `BIGINT`, `SIGNED`, `BIGINT SIGNED`, `TIME`. `UInt8` \[0 : 255\] `UInt16` \[0 : 65535\] `UInt32` \[0 : 4294967295\] `UInt64` \[0 : 18446744073709551615\] `UInt128` \[0 : 340282366920938463463374607431768211455\] `UInt256` \[0 : 115792089237316195423570985008687907853269984665640564039457584007913129639935\] Aliases: `UInt8` `TINYINT UNSIGNED`, `INT1 UNSIGNED`. `UInt16` `SMALLINT UNSIGNED`. `UInt32` `MEDIUMINT UNSIGNED`, `INT UNSIGNED`, `INTEGER UNSIGNED` `UInt64` `UNSIGNED`, `BIGINT UNSIGNED`, `BIT`, `SET`
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: markdown-overview.md

You can edit this example, using the editor to the left, or explore the other tabs in this playground. Kui interprets and displays markdown source. Kui has special interpretation for a some of the common bits of markdown syntax, allowing you to author: that provide sample output, and let the user re-execute the code in their context , using markdown blockquotes , using syntax adopted from [pymdown's Details extension](https://facelessuser.github.io/pymdown-extensions/extensions/details/) , using familiar colon-delimeted syntax :rocket: , using syntax adopted from [pymdown's Tabbed extension](https://facelessuser.github.io/pymdown-extensions/extensions/tabbed/)
Project: KICS (Provisioning / Security & Compliance)
File: b5ed026d-a772-4f07-97f9-664ba0b116f8.md

title: IAM Policy Grants Full Permissions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b5ed026d-a772-4f07-97f9-664ba0b116f8 Query name: IAM Policy Grants Full Permissions Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: IAM policy should not grant full permissions to resources from the get-go, instead of granting permissions gradually as necessary.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" name: Create IAM Managed Policy community.aws.iammanagedpolicy: policy_name: "ManagedPolicy" policy: Version: "2012-10-17" Statement: Effect: "Allow" Action: "*" Resource: "*" make_default: false state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: Create IAM Managed Policy community.aws.iammanagedpolicy: policy_name: ManagedPolicy policy: Version: '2012-10-17' Statement: Effect: Allow Action: logs:CreateLogGroup Resource: SomeResource make_default: false state: present ``` ```yaml title="Negative test num. 2 - yaml file" name: Create IAM Managed Policy community.aws.iammanagedpolicy: policy_name: ManagedPolicy policy: Version: '2012-10-17' Statement: Effect: Allow Action: '*' Resource: ec2messages:GetEndpoint make_default: false state: present ```
Project: GreptimeDB (App Definition and Development / Database)
File: pull_request_template.md

I hereby agree to the terms of the . !!! DO NOT LEAVE THIS BLOCK EMPTY !!! Please explain IN DETAIL what the changes are in this PR and why they are needed: Summarize your change (mandatory) How does this PR work? Need a brief introduction for the changed logic (optional) Describe clearly one logical change and avoid lazy messages (optional) Describe any limitations of the current code (optional) [ ] I have written the necessary rustdoc comments. [ ] I have added the necessary unit tests and integration tests. [ ] This PR requires documentation updates.
Project: KICS (Provisioning / Security & Compliance)
File: 209189f3-c879-48a7-9703-fbcfa96d0cef.md

title: BOM - AWS MQ hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 209189f3-c879-48a7-9703-fbcfa96d0cef Query name: BOM - AWS MQ Platform: CloudFormation Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of MQ resources found. Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easy to set up and operate message brokers on AWS.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" AWSTemplateFormatVersion: "2010-09-09" Description: "Create a basic ActiveMQ broker" Resources: BasicBroker: Type: "AWS::AmazonMQ::Broker" Properties: AutoMinorVersionUpgrade: "false" BrokerName: MyBasicBroker DeploymentMode: SINGLE_INSTANCE EncryptionOptions: UseAwsOwnedKey: true EngineType: ActiveMQ EngineVersion: "5.15.0" HostInstanceType: mq.t2.micro PubliclyAccessible: true Users: ConsoleAccess: "true" Groups: MyGroup Password: Ref: "BrokerPassword" Username: Ref: "BrokerUsername" ``` ```json title="Positive test num. 2 - json file" hl_lines="5" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "Create a basic ActiveMQ broker", "Resources": { "BasicBroker2": { "Type": "AWS::AmazonMQ::Broker", "Properties": { "BrokerName": "MyBasicBroker", "DeploymentMode": "SINGLE_INSTANCE", "EngineType": "ActiveMQ", "EngineVersion": "5.15.0", "HostInstanceType": "mq.t2.micro", "Users": [ { "ConsoleAccess": "true", "Groups": [ "MyGroup" ], "Password": { "Ref": "BrokerPassword" }, "Username": { "Ref": "BrokerUsername" } } ], "AutoMinorVersionUpgrade": "false" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myDistribution: Type: AWS::CloudFront::Distribution Properties: DistributionConfig: Enabled: true ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myDistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "Enabled": "true" } } } } } ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.9.19-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Any allocations inside OvercommitTracker may lead to deadlock. Logging was not very informative so it's easier just to remove logging. Fixes . (). Backported in : Fix bug in filesystem cache that could happen in some corner case which coincided with cache capacity hitting the limit. Closes . (). Backported in : Fix error `Block structure mismatch` which could happen for INSERT into table with attached MATERIALIZED VIEW and enabled setting `extremes = 1`. Closes and . (). Backported in : Declare RabbitMQ queue without default arguments `x-max-length` and `x-overflow`. (). Backported in : Fix segmentation fault in MaterializedPostgreSQL database engine, which could happen if some exception occurred at replication initialisation. Closes . (). Backported in : Fix incorrect fetch postgresql tables query fro PostgreSQL database engine. Closes . (). Reproduce and a little bit better fix for LC dict right offset. (). Retry docker buildx commands with progressive sleep in between (). Add docker_server.py running to backport and release CIs ().
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_ls.md

List all Projects and Stacks List all project and stack information in the current directory or the specify directory. The default output is in a human friendly format, and it also supports a variety of formatted structure output. ``` kusion ls [WORKDIR] [flags] ``` ``` kusion ls kusion ls ./path/to/project_dir kusion ls ./path/to/project_dir --format=tree kusion ls ./path/to/project_dir --format=json kusion ls ./path/to/project_dir --format=yaml kusion ls ./path/to/project_dir --format=tree --level=1 ``` ``` --format string Output format of the project information. valid values: json, yaml, tree, human (default "human") -h, --help help for ls -L, --level int Max display depth of the project and stack tree. One of 0,1,2 (default 2) ``` - Kusion is the platform engineering engine of KusionStack
Project: FOSSA (Provisioning / Security & Compliance)
File: integrating.md

FOSSA CLI (occasionally referred to as Spectrometer) is a tool that requires minimal configuration: usually, only a FOSSA API key is required. If you do not have an API key, please check the for instructions on generating an API key. ```sh export FOSSAAPIKEY=abcdef123456 ``` This runs dependency analysis in the current directory, uploading results to FOSSA ```sh fossa analyze ``` ```sh fossa test ``` This may take some time to return while FOSSA downloads and scans each dependency for display in our web UI. For additional commands and command flags, use `--help`: ```sh fossa --help fossa analyze --help ```
Project: StarRocks (App Definition and Development / Database)
File: be_compactions.md

displayed_sidebar: "English" `be_compactions` provides statistical information on compaction tasks. The following fields are provided in `be_compactions`: | Field | Description | | | - | | BE_ID | ID of the BE. | | CANDIDATES_NUM | Number of candidates for compaction tasks. | | BASECOMPACTIONCONCURRENCY | Number of base compaction tasks that are running. | | CUMULATIVECOMPACTIONCONCURRENCY | Number of cumulative compaction tasks that are running. | | LATESTCOMPACTIONSCORE | Compaction score of the last compaction task. | | CANDIDATEMAXSCORE | The maximum compaction score of the task candidate. | | MANUALCOMPACTIONCONCURRENCY | Number of manual compaction tasks that are running. | | MANUALCOMPACTIONCANDIDATES_NUM | Number of candidates for manual compaction tasks. |
Project: KICS (Provisioning / Security & Compliance)
File: cb3f5ed6-0d18-40de-a93d-b3538db31e8c.md

title: Security Group Rule Without Description hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: cb3f5ed6-0d18-40de-a93d-b3538db31e8c Query name: Security Group Rule Without Description Platform: Terraform Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: It's considered a best practice for AWS Security Group to have a description<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awssecuritygroup" "allow_tls" { name = "allow_tls" vpcid = awsvpc.main.id ingress { description = "TLS from VPC" from_port = 443 to_port = 443 protocol = "tcp" cidrblocks = [awsvpc.main.cidr_block] ipv6cidrblocks = [awsvpc.main.ipv6cidr_block] } tags = { Name = "allow_tls" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awssecuritygroup" "allow_tls" { name = "allow_tls" description = "Allow TLS inbound traffic" vpcid = awsvpc.main.id ingress { description = "TLS from VPC" from_port = 443 to_port = 443 protocol = "tcp" cidrblocks = [awsvpc.main.cidr_block] ipv6cidrblocks = [awsvpc.main.ipv6cidr_block] } tags = { Name = "allow_tls" } } ```
Project: Dragonfly (Provisioning / Container Registry)
File: dfcache_import.md

% DFCACHE(1) Version v2.1.0 | Frivolous "Dfcache" Documentation dfcache import import file into P2P cache system Import file into P2P cache system. ```shell dfcache import <-i cid> <file>|<-I file> [flags] ``` ```shell -i, --cid string content or cache ID, e.g. sha256 digest of the content --config string the path of configuration file with yaml extension name, default is /etc/dragonfly/dfcache.yaml, it can also be set by env var: DFCACHE_CONFIG --console whether logger output records to the stdout --jaeger string jaeger endpoint url, like: http://localhost:14250/api/traces --logdir string Dfcache log directory --pprof-port int listen port for pprof, 0 represents random port (default -1) --service-name string name of the service for tracer (default "dragonfly-dfcache") -t, --tag string different tags for the same cid will be recognized as different files in P2P network --timeout duration Timeout for this cache operation, 0 is infinite --verbose whether logger use debug level --workhome string Dfcache working directory -h, --help help for import -I, --input string import the given file into P2P network ``` - the P2P cache client of dragonfly