cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: adding-proto-messages.md

Spark Connect adopts proto3, which does not support the use of the `required` constraint anymore. For non-message proto fields, there is also no `hasfieldname` functions to easy tell if a filed is set or not-set. (Read ) When adding fields that have required semantics, developers are required to follow the outlined process. Fields that are semantically required for the server to correctly process the incoming message must be documented with `(Required)`. For scalar fields the server will not perform any additional input validation. For compound fields, the server will perform minimal checks to avoid null pointer exceptions but will not perform any semantic validation. Example: ```protobuf message DataSource { // (Required) Supported formats include: parquet, orc, text, json, parquet, csv, avro. string format = 1; } ``` Semantically optional fields must be marked by `optional`. The server side will then use this information to branch into different behaviors based on the presence or absence of this field. Due to the lack of configurable default values for scalar types, the pure presence of an optional value does not define its default value. The server side implementation will interpret the observed value based on its own rules. Example: ```protobuf message DataSource { // (Optional) If not set, Spark will infer the schema. optional string schema = 2; } ```
Project: ClickHouse (App Definition and Development / Database)
File: skewsamp.md

slug: /en/sql-reference/aggregate-functions/reference/skewsamp sidebar_position: 151 Computes the of a sequence. It represents an unbiased estimate of the skewness of a random variable if passed values form its sample. ``` sql skewSamp(expr) ``` Arguments `expr` returning a number. Returned value The skewness of the given distribution. Type . If `n <= 1` (`n` is the size of the sample), then the function returns `nan`. Example ``` sql SELECT skewSamp(value) FROM serieswithvalue_column; ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_login.md

title: "Command - devspace login" sidebar_label: devspace login Log into DevSpace Cloud ``` devspace login [flags] ``` ``` If no --key is supplied the browser will be opened and the login page is shown Example: devspace login devspace login --key myaccesskey ``` ``` -h, --help help for login --key string Access key to use --provider string Provider to use ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: ShardingSphere (App Definition and Development / Database)
File: unlabel-compute-node.en.md

+++ title = "UNLABEL COMPUTE NODES" weight = 6 +++ The `UNLABEL COMPUTE NODES` syntax is used to remove specified label from `PROXY` instance. {{< tabs >}} {{% tab name="Grammar" %}} ```sql UnlabelComputeNode ::= 'UNLABEL' 'COMPUTE' 'NODE' instance_id 'WITH' labelName instance_id ::= string labelName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} needs to be obtained through syntax query Remove specified label from `PROXY` instance ```sql UNLABEL COMPUTE NODE "0699e636-ade9-4681-b37a-65240c584bb3" WITH label_1; ``` `UNLABEL`, `COMPUTE`, `NODES`, `WITH`
Project: KICS (Provisioning / Security & Compliance)
File: 587d5d82-70cf-449b-9817-f60f9bccb88c.md

title: Container Host Pid Is True hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 587d5d82-70cf-449b-9817-f60f9bccb88c Query name: Container Host Pid Is True Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Minimize the admission of containers wishing to share the host process ID namespace<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" resource "kubernetes_pod" "positive1" { metadata { name = "terraform-example" } spec { host_pid = true container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "negative1" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } resource "kubernetes_pod" "negative2" { metadata { name = "terraform-example" } spec { host_pid = false container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ```
Project: YugabyteDB (App Definition and Development / Database)
File: tidb.md

title: Compare TiDB with YugabyteDB headerTitle: TiDB linkTitle: TiDB description: Compare TiDB database with YugabyteDB. aliases: /comparisons/tidb/ menu: preview_faq: parent: comparisons identifier: comparisons-tidb weight: 1076 type: docs PingCap's TiDB is a MySQL-compatible distributed database built on TiKV, and takes design inspiration from Google Spanner and Apache HBase. While its sharding and replication architecture are similar to that of Spanner, it follows a very different design for multi-shard transactions. TiDB uses Google Percolator as the inspiration for its multi-shard transaction design. This choice essentially makes TiDB unfit for deployments with geo-distributed writes since the majority of transactions in a random-access OLTP workload will now experience high WAN latency when acquiring a timestamp from the global timestamp oracle running in a different region. Additionally, TiDB lacks support for critical relational data modeling constructs such as foreign key constraints and Serializable isolation level. The following posts cover some more details around how YugabyteDB differs from TiDB.
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: habitat_supervisor_overview.md

Chef Habitat Supervisor is a process manager that has two primary responsibilities: A Supervisor runs your app's services. It starts, stops, updates, and monitors the services according to your plan. Supervisors can talk to each other. You can connect Supervisors together into a network and instruct them to send information to each other and take actions based on that information. In the Supervisor you can define topologies for you application, such as leader-follower or standalone, or more complex applications that include databases. The supervisor also allows you to inject tunables into your application. Allowing you to defer decisions about how your application behaves until runtime.
Project: KICS (Provisioning / Security & Compliance)
File: b4803607-ed72-4d60-99e2-3fa6edf471c6.md

title: BasePath With Wrong Format hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b4803607-ed72-4d60-99e2-3fa6edf471c6 Query name: BasePath With Wrong Format Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: The 'basePath' value format must match the pattern '^/'<br> ```json title="Positive test num. 1 - json file" hl_lines="7" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "basePath": "api/incorrect", "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="5" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 basePath: "api/incorrect" paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: limit2 in: body description: max records to return required: true schema: type: object parameters: limitParam: name: limit in: body description: max records to return required: true schema: type: object ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "basePath": "/api", "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 basePath: "/api" paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: limit2 in: body description: max records to return required: true schema: type: object parameters: limitParam: name: limit in: body description: max records to return required: true schema: type: object ```
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: CHANGELOG-7.0.md

See . The `SearchHit` structure changed from ``` // SearchHit is a single hit. type SearchHit struct { ... Source *json.RawMessage `json:"_source,omitempty"` // stored document source ... } ``` to ``` // SearchHit is a single hit. type SearchHit struct { ... Source json.RawMessage `json:"_source,omitempty"` // stored document source ... } ``` As `json.RawMessage` is a `[]byte`, there is no need to specify it as `*json.RawMessage` as `json.RawMessage` is perfectly ok to represent a `nil` value. So when deserializing the search hits, you need to change your code from: ``` for _, hit := range searchResult.Hits.Hits { var doc Doc err := json.Unmarshal(hit.Source, &doc) // notice the here if err != nil { // Deserialization failed } } ``` to ``` for _, hit := range searchResult.Hits.Hits { var doc Doc err := json.Unmarshal(hit.Source, &doc) // it's missing here if err != nil { // Deserialization failed } } ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.3.3.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Fails to build using Maven 3.8.1* In order to resolve build issues with Maven 3.8.1, we have to bump SolrJ to latest version 8.8.2 as of now. Solr is used by YARN application catalog. Hence, we would recommend upgrading Solr cluster accordingly before upgrading entire Hadoop cluster to 3.4.0 if the YARN application catalog service is used. | Major | Replace log4j 1.x with reload4j* log4j 1 was replaced with reload4j which is fork of log4j 1.2.17 with the goal of fixing pressing security issues. If you are depending on the hadoop artifacts in your build were explicitly excluding log4 artifacts, and now want to exclude the reload4j files, you will need to update your exclusion lists \<exclusion\> \<groupId\>org.slf4j\</groupId\> \<artifactId\>slf4j-reload4j\</artifactId\> \</exclusion\> \<exclusion\> \<groupId\>ch.qos.reload4j\</groupId\> \<artifactId\>reload4j\</artifactId\> \</exclusion\>
Project: KICS (Provisioning / Security & Compliance)
File: 2596545e-1757-4ff7-a15a-8a9a180a42f3.md

title: Parameter Object With Incorrect Ref (v2) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2596545e-1757-4ff7-a15a-8a9a180a42f3 Query name: Parameter Object With Incorrect Ref (v2) Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Parameter Object reference must always point to '#/parameters'<br> ```json title="Positive test num. 1 - json file" hl_lines="22" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "A list of users", "schema": { "$ref": "#/definitions/User" } } }, "parameters": [ { "$ref": "#/definitions/User" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "integer" } } }, "definitions": { "User": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="16" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: A list of users schema: "$ref": "#/definitions/User" parameters: "$ref": "#/definitions/User" parameters: limitParam: name: limit in: body description: max records to return required: true schema: type: integer definitions: User: type: object required: id name properties: id: type: integer format: int64 name: type: string ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "A list of users", "schema": { "$ref": "#/definitions/User" } } }, "parameters": [ { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "integer" } } }, "definitions": { "User": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: A list of users schema: "$ref": "#/definitions/User" parameters: "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: body description: max records to return required: true schema: type: integer definitions: User: type: object required: id name properties: id: type: integer format: int64 name: type: string ```
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_workspace_update.md

Update a workspace configuration This command updates a workspace configuration with specified configuration file, where the file must be in the YAML format. ``` kusion workspace update ``` ``` kusion workspace update dev -f dev.yaml ``` ``` -f, --file string the path of workspace configuration file -h, --help help for update ``` ``` --profile string Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex) (default "none") --profile-output string Name of the file to write the profile to (default "profile.pprof") ``` - Workspace is a logical concept representing a target that stacks will be deployed to
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: binadd.md

The `BinAdd` rule defines additive operations |Operator|Description| ||| |`+`|Binary addition| |`-`|Binary subtraction| Note that the `+` binary operation is also used for string concatenation, array concatination and for iserting/overwriting fields in a LHS record from a HRS record.
Project: Clair (Provisioning / Security & Compliance)
File: README.md

](https://quay.io/repository/projectquay/clair) ](https://pkg.go.dev/github.com/quay/clair/v4) ](http://webchat.freenode.net/?channels=clair) Note: The `main` branch may be in an unstable or even broken state during development. Please use [releases] instead of the `main` branch in order to get stable binaries. Clair is an open source project for the [static analysis] of vulnerabilities in application containers (currently including [OCI] and [docker]). Clients use the Clair API to index their container images and can then match it against known vulnerabilities. Our goal is to enable a more transparent view of the security of container-based infrastructure. Thus, the project was named `Clair` after the French term which translates to clear, bright, transparent. [The book] contains all the documentation on Clair's architecture and operation. Mailing List: IRC: # on freenode.org Bugs: See for details on submitting patches and the contribution workflow. Clair is under the Apache 2.0 license. See the file for details.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_snapshots.md

+++ title = "googlecomputesnapshots resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputesnapshots" identifier = "inspec/resources/gcp/googlecomputesnapshots.md googlecomputesnapshots resource" parent = "inspec/resources/gcp" +++ A `googlecomputesnapshots` is used to test a Google Snapshot resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputesnapshots(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } end describe.one do googlecomputesnapshots(project: 'chef-gcp-inspec').names do |snapshot_name| describe googlecomputesnapshot(project: 'chef-gcp-inspec', name: snapshot_name) do its('source_disk') { should match 'inspec-snapshot-disk' } end end end ``` Properties that can be accessed from the `googlecomputesnapshots` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputesnapshot` creation_timestamp `ids` : an array of `googlecomputesnapshot` id `disksizegbs` : an array of `googlecomputesnapshot` disksizegb `names` : an array of `googlecomputesnapshot` name `descriptions` : an array of `googlecomputesnapshot` description `storage_bytes` : an array of `googlecomputesnapshot` storage_bytes `licenses` : an array of `googlecomputesnapshot` licenses `labels` : an array of `googlecomputesnapshot` labels `label_fingerprints` : an array of `googlecomputesnapshot` label_fingerprint `source_disks` : an array of `googlecomputesnapshot` source_disk `zones` : an array of `googlecomputesnapshot` zone `snapshotencryptionkeys` : an array of `googlecomputesnapshot` snapshotencryptionkey `sourcediskencryption_keys` : an array of `googlecomputesnapshot` sourcediskencryption_key This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: ArangoDB (App Definition and Development / Database)
File: hook_result_construction.md

+++ title = "`void hookresultconstruction(T *, U &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the implicit constructors of `basic_result`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onresultconstruction(T *, U &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the implicit constructors of `basicresult`. See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_result.hpp>`
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_port.md

<!MARKERGENSTART--> Print the public port for a port binding | Name | Type | Default | Description | |:-|:|:--|:--| | `--dry-run` | | | Execute command in dry run mode | | `--index` | `int` | `0` | Index of the container if service has multiple replicas | | `--protocol` | `string` | `tcp` | tcp or udp | <!MARKERGENEND--> Prints the public port for a port binding
Project: MongoDB (App Definition and Development / Database)
File: task_timeouts.md

There are two types of timeouts that : Exec timeout: The exec timeout is the overall timeout for a task. Once the total runtime for a test hits this value, the timeout logic will be triggered. This value is specified by exec_timeout_secs in the evergreen configuration. Idle timeout: The idle timeout is the amount of time in which evergreen will wait for output to be created before it considers the task hung and triggers timeout logic. This value is specified by timeout_secs in the evergreen configuration. Note: In most cases, exec_timeout is usually the more useful of the timeouts. There are a few ways in which the timeout can be determined for a task running in evergreen. Specified in 'etc/evergreen.yml': Timeout can be specified directly in the 'evergreen.yml' file, both on tasks and build variants. This can be useful for setting default timeout values, but is limited since different build variants frequently have different runtime characteristics and it is not possible to set timeouts for a task running on a specific build variant. etc/evergreen_timeouts.yml: The 'etc/evergreen_timeouts.yml' file for overriding timeouts for specific tasks on specific build variants. This provides a work-around for the limitations of specifying the timeouts directly in the 'evergreen.yml'. In order to use this method, the task must run the "determine task timeout" and "update task timeout expansions" functions at the beginning of the task evergreen definition. Most resmoke tasks already do this. buildscripts/evergreen_task_timeout.py: This is the script that reads the 'etc/evergreen_timeouts.yml' file and calculates the timeout to use. Additionally, it will check the historic test results of the task being run and see if there is enough information to calculate timeouts based on that. It can also be used for more advanced ways of determining timeouts (e.g. the script is used to set much more aggressive timeouts on tasks that are run in the commit-queue).