cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: start-stop-processes.md

title: Start and stop processes headerTitle: Start and stop processes linkTitle: Start and stop processes description: Use YugabyteDB Anywhere to start and stop processes. menu: v2.18_yugabyte-platform: identifier: start-stop-processes parent: manage-deployments weight: 10 type: docs You can restart the node's processes by navigating to Universes, selecting your universe, then selecting Nodes, and then clicking Actions > Start Processes corresponding to the node. This returns the node to the Live state. In some cases, the system might experience an unrecoverable error. To mitigate, you can use the Release Instance option for the stopped node. This also removes the backing instance. For details, see . If a node needs the intervention, you can click its associated Actions > Stop Processes. Once the YB-TServer and, possibly, YB-Master server are stopped, the node status is updated and the instance is ready for the planned system changes. Generally, when a YB-Master is stopped on a node, YugabyteDB Anywhere automatically attempts to start a new YB-Master on another node in the same Availability Zone as the node on which YB-Master is stopped. This ensures that the number of YB-Master servers equals the replication factor (RF) and YB-Master servers are never underreplicated. It is recommended not to stop more than (RF - 1) / 2 processes at any given time. For example, on an RF=3 cluster with three nodes, there can only be one node with stopped processes to allow the majority of the nodes to perform Raft consensus operations.
Project: YugabyteDB (App Definition and Development / Database)
File: perf_prepare.md

title: PREPARE statement [YSQL] headerTitle: PREPARE linkTitle: PREPARE description: Use the PREPARE statement to create a handle to a prepared statement by parsing, analyzing, and rewriting (but not executing) the target statement. menu: v2.18: identifier: perf_prepare parent: statements type: docs Use the `PREPARE` statement to create a handle to a prepared statement by parsing, analyzing, and rewriting (but not executing) the target statement. {{%ebnf%}} prepare_statement {{%/ebnf%}} The statement in `PREPARE` may (should) contain parameters (e.g. `$1`) that will be provided by the expression list in `EXECUTE`. The data type list in `PREPARE` represent the types for the parameters used in the statement. Create a sample table. ```plpgsql yugabyte=# CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Prepare a simple insert. ```plpgsql yugabyte=# PREPARE ins (bigint, double precision, int, text) AS INSERT INTO sample(k1, k2, v1, v2) VALUES ($1, $2, $3, $4); ``` Execute the insert twice (with different parameters). ```plpgsql yugabyte=# EXECUTE ins(1, 2.0, 3, 'a'); ``` ```plpgsql yugabyte=# EXECUTE ins(2, 3.0, 4, 'b'); ``` Check the results. ```plpgsql yugabyte=# SELECT * FROM sample ORDER BY k1; ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 2 | 3 | 4 | b (2 rows) ```
Project: Cadence Workflow (Provisioning / Automation & Configuration)
File: PROPOSALS.md

The design process for changes to Cadence is modeled on the . describing the proposal. Like any GitHub issue, a proposal issue is followed by an initial discussion about the suggestion. For Proposal issues: The goal of the initial discussion is to reach agreement on the next step: (1) accept, (2) decline, or (3) ask for a design doc. The discussion is expected to be resolved in a timely manner. If the author wants to write a design doc, then they can write one. A lack of agreement means the author should write a design doc. If a Proposal issue leads to a design doc: The design doc should be presented as a Google Doc and must follow . The design doc should be linked from the opened GitHub issue. The design doc should only allow edit access to authors of the document. Do not create the document from a corporate G Suite account. If you want to edit from a corporate G Suite account then first create the document from a personal Google account and grant edit access to your corporate G Suite account. Comment access should also be accessible by the public. Make sure this is the case by clicking "Share" and "Get shareable link" ensuring you select "Anyone with the link can comment". Once comments and revisions on the design doc wind down, there is a final discussion about the proposal. The goal of the final discussion is to reach agreement on the next step: (1) accept or (2) decline. The discussion is expected to be resolved in a timely manner. Once the design doc is agreed upon, the author shall export the contents of the Google Doc as a Markdown document and submit a PR to add it to the proposal repository. Authors can use to convert the document but any cleanup required must be done by hand. The design doc should be checked in at `docs/design/XYZ-shortname.md`, where `XYZ` is the GitHub issue number and `shortname` is a short name (a few dash-separated words at most). The design doc should be added to the list of existing proposals in `docs/design/index.md` The author (and/or other contributors) do the work as described by the "Implementation" section of the proposal. This project is released under the .
Project: KICS (Provisioning / Security & Compliance)
File: 3cb4af0b-056d-4fb1-8b95-fdc4593625ff.md

title: Using Default Service Account hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3cb4af0b-056d-4fb1-8b95-fdc4593625ff Query name: Using Default Service Account Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Defaults URL: Instances should not be configured to use the Default Service Account, that has full access to all Cloud APIs, which means the attribute 'service_account' and its sub attribute 'email' must be defined. Additionally, 'email' must not be empty and must also not be a default Google Compute Engine service account.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2 100 73 46 127" resource "googlecomputeinstance" "positive1" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } } resource "googlecomputeinstance" "positive2" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } resource "googlecomputeinstance" "positive3" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { email = "" scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } resource "googlecomputeinstance" "positive4" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { email = "a" scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } resource "googlecomputeinstance" "positive5" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { email = "email@developer.gserviceaccount.com" scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputeinstance" "negative1" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } // Local SSD disk scratch_disk { interface = "SCSI" } network_interface { network = "default" access_config { // Ephemeral IP } } service_account { email = "email@email.com" scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } ```
Project: ClickHouse (App Definition and Development / Database)
File: permissions-for-queries.md

slug: /en/operations/settings/permissions-for-queries sidebar_position: 58 sidebar_label: Permissions for Queries Queries in ClickHouse can be divided into several types: Read data queries: `SELECT`, `SHOW`, `DESCRIBE`, `EXISTS`. Write data queries: `INSERT`, `OPTIMIZE`. Change settings query: `SET`, `USE`. queries: `CREATE`, `ALTER`, `RENAME`, `ATTACH`, `DETACH`, `DROP` `TRUNCATE`. `KILL QUERY`. The following settings regulate user permissions by the type of query: Restricts permissions for read data, write data, and change settings queries. When set to 1, allows: All types of read queries (like SELECT and equivalent queries). Queries that modify only session context (like USE). When set to 2, allows the above plus: SET and CREATE TEMPORARY TABLE :::tip Queries like EXISTS, DESCRIBE, EXPLAIN, SHOW PROCESSLIST, etc are equivalent to SELECT, because they just do select from system tables. ::: Possible values: 0 Read, Write, and Change settings queries are allowed. 1 Only Read data queries are allowed. 2 Read data and Change settings queries are allowed. Default value: 0 :::note After setting `readonly = 1`, the user cant change `readonly` and `allow_ddl` settings in the current session. When using the `GET` method in the , `readonly = 1` is set automatically. To modify data, use the `POST` method. Setting `readonly = 1` prohibits the user from changing settings. There is a way to prohibit the user from changing only specific settings. Also there is a way to allow changing only specific settings under `readonly = 1` restrictions. For details see . ::: Allows or denies queries. Possible values: 0 DDL queries are not allowed. 1 DDL queries are allowed. Default value: 1 :::note You cannot run `SET allowddl = 1` if `allowddl = 0` for the current session. ::: :::note KILL QUERY `KILL QUERY` can be performed with any combination of readonly and allow_ddl settings. :::
Project: Gradle Build Tool (App Definition and Development / Application Definition & Image Build)
File: notes-template.md

The Gradle team is excited to announce Gradle @version@. This release features , , ... , and more. <!-- Include only their name, impactful features should be called out separately below. THIS LIST SHOULD BE ALPHABETIZED BY [PERSON NAME] - the docs:updateContributorsInReleaseNotes task will enforce this ordering, which is case-insensitive. --> We would like to thank the following community members for their contributions to this release of Gradle: Be sure to check out the for insight into what's planned for future releases. Switch your build to use Gradle @version@ by updating your wrapper: `./gradlew wrapper --gradle-version=@version@` See the to learn about deprecations, breaking changes, and other considerations when upgrading to Gradle @version@. For Java, Groovy, Kotlin, and Android compatibility, see the . <!-- Do not add breaking changes or deprecations here! Add them to the upgrade guide instead. --> <!-- ================== TEMPLATE ============================== <a name="FILL-IN-KEY-AREA"></a> <<<FILL IN CONTEXT FOR KEY AREA>>> Example: The improves build performance by caching the result of the configuration phase. Using the configuration cache, Gradle can skip the configuration phase entirely when nothing that affects the build configuration has changed. HIGHLIGHT the use case or existing problem the feature solves EXPLAIN how the new release addresses that problem or use case PROVIDE a screenshot or snippet illustrating the new feature, if applicable LINK to the full documentation for more details ================== END TEMPLATE ========================== ========================================================== ADD RELEASE FEATURES BELOW vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv --> <!-- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ADD RELEASE FEATURES ABOVE ========================================================== --> Promoted features are features that were incubating in previous versions of Gradle but are now supported and subject to backward compatibility. See the User Manual section on the for more information. The following are the features that have been promoted in this Gradle release. <!-- --> <!-- This section will be populated automatically --> Known issues are problems that were discovered post-release that are directly related to changes made in this release. <!-- This section will be populated automatically --> We love getting contributions from the Gradle community. For information on contributing, please see . If you find a problem with this release, please file a bug on adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the . We hope you will build happiness with Gradle, and we look forward to your feedback via or on .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.33.md

layout: release date: 2022-12-07 tag: v0.6.33 language: en Replacing Mui icons to SVG's. @Krishna2323 (#6637) [bug] Fix struct dereferencing @theBeginner86 (#6648) [UI] Playground: Change verbiage for limited feature access @leecalcote (#6638) [bug] Fix struct dereferencing @theBeginner86 (#6648) Removed deprecated GH actions @acald-creator (#6641) Thank you to our contributors for making this release possible: @Krishna2323, @Revolyssup, @acald-creator, @leecalcote, @theBeginner86 and l5io
Project: RethinkDB (App Definition and Development / Database)
File: WINDOWS.md

Note VS must be installed in default directory (any drive) In installer tick desktop C++ workload, and in individual components: MSVC v141 Windows 10 SDK 10.0.19041.0 CMake tool Warning Make sure that `perl` package IS NOT installed in cygwin! Additional Cygwin packages: make curl wget patch Install and make sure it's added to PATH Download, unpack anywhere and add to PATH From a Cygwin shell: ``` ./configure make -j$(nproc) ``` Will first download and build the libraries that RethinkDB needs, then build RethinkDB itself and place it in `build\Release_x64\rethinkdb.exe` If `make` complains about missing files in `mk/gen`, run `mkdir mk/gen` manually. Then run `make -j` again.
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: ClickHouse (App Definition and Development / Database)
File: fileCluster.md

slug: /en/sql-reference/table-functions/fileCluster sidebar_position: 61 sidebar_label: fileCluster Enables simultaneous processing of files matching a specified path across multiple nodes within a cluster. The initiator establishes connections to worker nodes, expands globs in the file path, and delegates file-reading tasks to worker nodes. Each worker node is querying the initiator for the next file to process, repeating until all tasks are completed (all files are read). :::note This function will operate correctly only in case the set of files matching the initially specified path is identical across all nodes, and their content is consistent among different nodes. In case these files differ between nodes, the return value cannot be predetermined and depends on the order in which worker nodes request tasks from the initiator. ::: Syntax ``` sql fileCluster(clustername, path[, format, structure, compressionmethod]) ``` Arguments `cluster_name` Name of a cluster that is used to build a set of addresses and connection parameters to remote and local servers. `path` The relative path to the file from . Path to file also supports . `format` of the files. Type: . `structure` Table structure in `'UserID UInt64, Name String'` format. Determines column names and types. Type: . `compression_method` Compression method. Supported compression types are `gz`, `br`, `xz`, `zst`, `lz4`, and `bz2`. Returned value A table with the specified format and structure and with data from files matching the specified path. Example Given a cluster named `mycluster` and given the following value of setting `userfiles_path`: ``` bash $ grep userfilespath /etc/clickhouse-server/config.xml <userfilespath>/var/lib/clickhouse/userfiles/</userfiles_path> ``` Also, given there are files `test1.csv` and `test2.csv` inside `userfilespath` of each cluster node, and their content is identical across different nodes: ```bash $ cat /var/lib/clickhouse/user_files/test1.csv 1,"file1" 11,"file11" $ cat /var/lib/clickhouse/user_files/test2.csv 2,"file2" 22,"file22" ``` For example, one can create these files by executing these two queries on every cluster node: ```sql INSERT INTO TABLE FUNCTION file('file1.csv', 'CSV', 'i UInt32, s String') VALUES (1,'file1'), (11,'file11'); INSERT INTO TABLE FUNCTION file('file2.csv', 'CSV', 'i UInt32, s String') VALUES (2,'file2'), (22,'file22'); ``` Now, read data contents of `test1.csv` and `test2.csv` via `fileCluster` table function: ```sql SELECT * FROM fileCluster('my_cluster', 'file{1,2}.csv', 'CSV', 'i UInt32, s String') ORDER BY i, s ``` ``` is 1 file1 11 file11 is 2 file2 22 file22 ``` All patterns supported by table function are supported by FileCluster. See Also
Project: ClickHouse (App Definition and Development / Database)
File: minmap.md

slug: /en/sql-reference/aggregate-functions/reference/minmap sidebar_position: 142 Syntax: `minMap(key, value)` or `minMap(Tuple(key, value))` Calculates the minimum from `value` array according to the keys specified in the `key` array. Passing a tuple of keys and value arrays is identical to passing two arrays of keys and values. The number of elements in `key` and `value` must be the same for each row that is totaled. Returns a tuple of two arrays: keys in sorted order, and values calculated for the corresponding keys. Example: ``` sql SELECT minMap(a, b) FROM values('a Array(Int32), b Array(Int64)', ([1, 2], [2, 2]), ([2, 3], [1, 1])) ``` ``` text minMap(a, b) ([1,2,3],[2,1,1]) ```
Project: KICS (Provisioning / Security & Compliance)
File: 5ea624e4-c8b1-4bb3-87a4-4235a776adcc.md

title: SNS Topic Publicity Has Allow and NotAction Simultaneously hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5ea624e4-c8b1-4bb3-87a4-4235a776adcc Query name: SNS Topic Publicity Has Allow and NotAction Simultaneously Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: SNS topic Publicity should not have 'Effect: Allow' and argument 'NotAction' at the same time. If it has 'Effect: Allow', the argument stated should be 'Action'.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" resource "awssnstopic" "positive1" { name = "my-topic-with-policy" } resource "awssnstopic_policy" "positive2" { arn = awssnstopic.test.arn policy = <<POLICY { "Version": "2012-10-17", "Id": "MYPOLICYTEST", "Statement": [ { "NotAction": "s3:DeleteBucket", "Resource": "arn:aws:s3:::*", "Sid": "MyStatementId", "Effect": "Allow" } ] } POLICY } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="12" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYPOLICYTEST", "Statement": [ { "NotAction": "s3:DeleteBucket", "Resource": "arn:aws:s3:::*", "Sid": "MyStatementId", "Effect": "Allow" } ] } POLICY serversideencryption_configuration { rule { applyserversideencryptionby_default { kmsmasterkeyid = awskms_key.mykey.arn sse_algorithm = "aws:kms" } } } } ``` ```tf title="Negative test num. 1 - tf file" resource "awssnstopic" "negative1" { name = "my-topic-with-policy" } resource "awssnstopic_policy" "negative2" { arn = awssnstopic.test.arn policy = <<POLICY { "Version": "2012-10-17", "Id": "MYPOLICYTEST", "Statement": [ { "Action": "s3:DeleteBucket", "Resource": "arn:aws:s3:::*", "Sid": "MyStatementId", "Effect": "Allow" } ] } POLICY } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } policy = <<POLICY { "Version": "2012-10-17", "Id": "MYPOLICYTEST", "Statement": [ { "Action": "s3:DeleteBucket", "Resource": "arn:aws:s3:::*", "Sid": "MyStatementId", "Effect": "Allow" } ] } POLICY serversideencryption_configuration { rule { applyserversideencryptionby_default { kmsmasterkeyid = awskms_key.mykey.arn sse_algorithm = "aws:kms" } } } } ```
Project: Cadence Workflow (Provisioning / Automation & Configuration)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Version of Cadence server, and client(which language) This is very important to root cause bugs. Server version: Client version: Client langauge: Describe the bug A clear and concise description of what the bug is. To Reproduce Is the issue reproducible? [Yes | No] Steps to reproduce the behavior: A clear and concise description of the reproduce steps. Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here, E.g. Stackstace, workflow history.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cgroups.md

Determines whether the container creates CGroups. Default is enabled. The enabled option creates a new cgroup under the cgroup-parent. The disabled option forces the container to not create CGroups, and thus conflicts with CGroup options (--cgroupns and --cgroup-parent). The no-conmon option disables a new CGroup only for the conmon process. The split option splits the current CGroup in two sub-cgroups: one for conmon and one for the container payload. It is not possible to set --cgroup-parent with split.