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

displayed_sidebar: "English" Lists the operations currently being performed by threads executing within the server. The current version of StarRocks only supports listing queries. :::tip This operation does not require privileges. ::: ```SQL SHOW [FULL] PROCESSLIST ``` | Parameter | Required | Description | | | -- | - | | FULL | No | If you specify this parameter, the complete SQL statement will be displayed. Otherwise, only the first 100 characters of the statement are displayed. | | Return | Description | | - | | | Id | Connection ID. | | User | The name of the user who runs the operation. | | Host | The hostname of the client which runs the operation. | | Db | The name of the database where the operation is executed. | | Command | The type of the command. | | ConnectionStartTime | Time when the connection starts. | | Time | The time (in second) since the operation has entered the current state. | | State | The state of the operation. | | Info | The command that the operation is executing. | If the current user is `root`, this statement lists the operations of all users in the cluster. Otherwise, only operations of the current user are listed. Example 1: lists the operations state via the user `root`. ```Plain SHOW PROCESSLIST; ++++-++++-++ | Id | User | Host | Db | Command | ConnectionStartTime | Time | State | Info | ++++-++++-++ | 0 | root | x.x.x.x:xxxx | tpcds | Query | 2022-10-09 19:58:25 | 0 | OK | SHOW PROCESSLIST | ++++-++++-++ ```
Project: Checkov (Provisioning / Security & Compliance)
File: bitbucket_pipelines.md

layout: default title: bitbucket_pipelines resource scans nav_order: 1 | | Id | Type | Entity | Policy | IaC | Resource Link | |-|--||--|||-| | 0 | CKVBITBUCKETPIPELINES1 | bitbucket_pipelines | | | 1 | CKVBITBUCKETPIPELINES1 | bitbucket_pipelines | pipelines.*. | | 2 | CKVBITBUCKETPIPELINES1 | bitbucket_pipelines | pipelines.default |
Project: KICS (Provisioning / Security & Compliance)
File: 2bff9906-4e9b-4f71-9346-8ebedfdf43ef.md

title: PSP Allows Privilege Escalation hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2bff9906-4e9b-4f71-9346-8ebedfdf43ef Query name: PSP Allows Privilege Escalation Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: PodSecurityPolicy should not allow privilege escalation<br> ```tf title="Positive test num. 1 - tf file" hl_lines="50 7" resource "kubernetespodsecurity_policy" "example" { metadata { name = "terraform-example" } spec { privileged = false allowprivilegeescalation = true volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } resource "kubernetespodsecurity_policy" "example2" { metadata { name = "terraform-example" } spec { privileged = false volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetespodsecurity_policy" "example2" { metadata { name = "terraform-example" } spec { privileged = false allowprivilegeescalation = false volumes = [ "configMap", "emptyDir", "projected", "secret", "downwardAPI", "persistentVolumeClaim", ] runasuser { rule = "MustRunAsNonRoot" } se_linux { rule = "RunAsAny" } supplemental_groups { rule = "MustRunAs" range { min = 1 max = 65535 } } fs_group { rule = "MustRunAs" range { min = 1 max = 65535 } } readonlyroot_filesystem = true } } ```
Project: Distribution (Provisioning / Container Registry)
File: deprecated-schema-v1.md

title: Image manifest version 2, schema 1 description: Update deprecated schema v1 images keywords: registry, on-prem, images, tags, repository, distribution, api, advanced, manifest With the release of image manifest version 2, schema 2, image manifest version 2, schema 1 has been deprecated. This could lead to compatibility and vulnerability issues in images that haven't been updated to image manifest version 2, schema 2. This page contains information on how to update from image manifest version 2, schema 1. However, these instructions will not ensure your new image will run successfully. There may be several other issues to troubleshoot that are associated with the deprecated image manifest that will block your image from running successfully. A list of possible methods to help update your image is also included below. One way to upgrade an image from image manifest version 2, schema 1 to schema 2 is to `docker pull` the image and then `docker push` the image with a current version of Docker. Doing so will automatically convert the image to use the latest image manifest specification. Converting an image to image manifest version 2, schema 2 converts the manifest format, but does not update the contents within the image. Images using manifest version 2, schema 1 may contain unpatched vulnerabilities. We recommend looking for an alternative image or rebuilding it. You can rebuild the image by updating the `FROM` statement in your `Dockerfile`. If your image manifest is out-of-date, there is a chance the image pulled from your `FROM` statement in your `Dockerfile` is also out-of-date. See the and the for more information on how to update the `FROM` statement in your `Dockerfile`.
Project: ClickHouse (App Definition and Development / Database)
File: generate_series.md

slug: /en/sql-reference/table-functions/generate_series sidebar_position: 146 sidebarlabel: generateseries `generateseries(START, STOP)` - Returns a table with the single generateseries column (UInt64) that contains integers from start to stop inclusively. `generateseries(START, STOP, STEP)` - Returns a table with the single generateseries column (UInt64) that contains integers from start to stop inclusively with spacing between values given by STEP. The following queries return tables with the same content but different column names: ``` sql SELECT * FROM numbers(10, 5); SELECT * FROM generate_series(10, 14); ``` And the following queries return tables with the same content but different column names (but the second option is more efficient): ``` sql SELECT * FROM numbers(10, 11) WHERE number % 3 == (10 % 3); SELECT * FROM generate_series(10, 20, 3) ; ```
Project: YugabyteDB (App Definition and Development / Database)
File: go.md

title: Build a YugabyteDB YEDIS application using Go headerTitle: Build an application using Go linkTitle: Go description: Use Go to build a YugabyteDB application that interacts with YEDIS aliases: /preview/yedis/develop/client-drivers/go menu: preview: identifier: client-drivers-yedis-go parent: develop-yedis type: docs This tutorial assumes that you have: installed YugabyteDB, created a universe, and are able to interact with it using the Redis shell. If not, please follow these steps in . installed Go version 1.8 or later To install the driver, locally run the following `go get` command. ```sh $ go get github.com/go-redis/redis ``` Create a file `ybredishelloworld.go` and copy the contents below. ```go package main; import ( "fmt" "log" "github.com/go-redis/redis" ) func main() { // Connect to the cluster. client := redis.NewClient(&redis.Options{ Addr: "localhost:6379", Password: "", // no password set DB: 0, // use the default DB }) defer client.Close() // Insert some data (for user id 1). var userid string = "1" ok, err := client.HMSet(userid, map[string]interface{}{ "name": "John", "age": "35", "language": "Redis"}).Result() if (err != nil) { log.Fatal(err) } fmt.Printf("HMSET returned '%s' for id=%s with values: name=John, age=35, language=Redis\n", ok, userid) // Query the data. result, err := client.HGetAll("1").Result() fmt.Printf("Query result for id=%s: '%v'\n", userid, result) } ``` To execute the file, run the following command. ```sh $ go run ybredishelloworld.go ``` You should see the following as the output. ``` HMSET returned 'OK' for id=1 with values: name=John, age=35, language=Redis Query result for id=1: 'map[age:35 language:Redis name:John]' ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: logging.md

Lagoon provides access to the following logs via Kibana: Logs from the Kubernetes Routers, including every single HTTP and HTTPS request with: Source IP URL Path HTTP verb Cookies Headers User agent Project Container name Response size Response time Logs from containers: `stdout` and `stderr` messages Container name Project Lagoon logs: Webhooks parsing Build logs Build errors Any other Lagoon related logs Application logs: For Drupal: install the module in order to receive logs from Drupal Watchdog. For Laravel: install the package. For other workloads: Send logs to `udp://application-logs.lagoon.svc:5140` Ensure logs are structured as JSON encoded objects. Ensure the `type` field contains the name of the Kubernetes namespace (`$LAGOONPROJECT-$LAGOONENVIRONMENT`). To access the logs, please check with your Lagoon administrator to get the URL for the Kibana route \(for amazee.io, this is \). Each Lagoon user account has their own login and will see the logs only for the projects to which they have access. Each Lagoon user account also has their own Kibana Tenant, which means no saved searches or visualizations are shared with another account. If you would like to know more about how to use Kibana: .
Project: BigchainDB (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

Make sure the title of this pull request has the form: Problem: A short statement of the problem. A short statement about how this PR solves the Problem. What issues does this PR resolve, if any? Please include lines like the following (i.e. "Resolves #NNNN), so that when this PR gets merged, GitHub will automatically close those issues. Resolves #NNNN Resolves #MMMM What does this pull request implement, if any?
Project: ArangoDB (App Definition and Development / Database)
File: implicit_inplace_value_error_exception_constructor.md

+++ title = "`basic_outcome(A1 &&, A2 &&, Args ...)`" description = "Implicit inplace value or error or exception constructor. Available if `predicate::enableinplacevalueerrorexception_constructor<A1, A2, Args ...>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "inplace-constructors"] weight = 440 +++ Implicit inplace value or error or exception constructor. Delegates to an appropriate explicit inplace constructor depending on input. Requires: predicate::enableinplacevalueerrorexception_constructor<A1, A2, Args ...>` is true. Complexity: Same as for the `valuetype` or `errortype` or `exception_type` constructor which accepts `A1, A2, Args ...`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the Args is left indeterminate.
Project: ShardingSphere (App Definition and Development / Database)
File: stop-migration.en.md

+++ title = "STOP MIGRATION" weight = 15 +++ The `STOP MIGRATION` syntax is used to stop migration process. {{< tabs >}} {{% tab name="Grammar" %}} ```sql StopMigration ::= 'STOP' 'MIGRATION' migrationJobId migrationJobId ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `migrationJobId` needs to be obtained through syntax query Stop migration process ```sql STOP MIGRATION 'j010180026753ef0e25d3932d94d1673ba551'; ``` `STOP`, `MIGRATION`
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-305.md

Pulsar client use Netty DNS to resolve hostnames. Currently Pulsar client levereage on JVM detected DNS servers or on Google DNS servers if nothing was found (as per Netty default). You cannot change which DNS use to resolve hostnames but you are forced to use local server one (like DNS servers configured through resolv.conf or similar ways) or leverage on some Netty "black magic" system properties. The ability to directly configure which DNS use is strictly necessary in environment with "specialized" DNS servers. Add a new configuration on Pulsar client to explicitly set which DNS use. Fully configure DNS layer, properties, timeouts etcetera. A new client configuration will be added to list wich DNS server use. Such configuration will be checked when creating Pulsar clients to instantiate the DNS resolver. If no configuration is provided the client must use current defaults. The new configuration will be read from org.apache.pulsar.client.impl.ConnectionPool to configure a DnsNameResolverBuilder Add new dnsServerAddresses method on org.apache.pulsar.client.api.ClientBuilder. There are no breaking changes, if dnsServerAddresses is not configuret Pulsar will continue to behave like now. NA NA Add new dnsServerAddresses property on org.apache.pulsar.client.impl.conf.ClientConfigurationData. NA NA NA The client will have the ability to use a different set of DNS servers. It is possible to alter hostnames resolutions however it is expected that this does not pose any security risks. Just remove dnsServerAddresses configuration Configure a dnsServerAddresses server list. The configuration is not mandatory, Pulsar can run without it just like before. Expose an interface builder to fully configure the DNS layer. It has much more impact and conflict with existing configuration properties dnsLookupBindAddress and dnsLookupBindPort. Mailing List discussion thread: https://lists.apache.org/thread/p0870y7o6brv5y1ghn5tz9hvs24bl1k4 Mailing List voting thread: https://lists.apache.org/thread/7dd0htk0qqkrjxztj445lj3qskxr2dky
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_queues_receive.md

Queues receive a messages from a queue channel command Queues receive command allows to receive one or many messages from a queue channel ``` kubemq queues receive [flags] ``` ``` kubemq queue receive q1 kubemq queue receive q1 -m 3 -t 5 kubemq queue receive q1 -w ``` ``` -h, --help help for receive -m, --messages int set how many messages we want to get from a queue (default 1) -t, --wait-timeout int set how many seconds to wait for 'queues' messages (default 2) -w, --watch set watch on 'queues' channel ``` - Execute Kubemq 'queues' commands
Project: KICS (Provisioning / Security & Compliance)
File: fb889ae9-2d16-40b5-b41f-9da716c5abc1.md

title: Parameter JSON Reference Does Not Exists (v2) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: fb889ae9-2d16-40b5-b41f-9da716c5abc1 Query name: Parameter JSON Reference Does Not Exists (v2) Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Parameter reference should exist on parameters definition field<br> ```json title="Positive test num. 1 - json file" hl_lines="19" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/definitions/User" } }, "parameters": [ { "$ref": "#/parameters/maxParam" }, { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "query", "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="14" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/definitions/User" parameters: "$ref": "#/parameters/maxParam" "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: query 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": { "$ref": "#/definitions/User" } }, "parameters": [ { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "query", "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': "$ref": "#/definitions/User" parameters: "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: query 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: Pinniped (Provisioning / Key Management)
File: configure-concierge-supervisor-jwt.md

title: Configure the Pinniped Concierge to validate JWT tokens issued by the Pinniped Supervisor description: Set up JSON Web Token (JWT) based token authentication on an individual Kubernetes cluster using the Pinniped Supervisor as the OIDC provider. cascade: layout: docs menu: docs: name: With Supervisor weight: 40 parent: howto-configure-concierge aliases: /docs/howto/configure-concierge-supervisor-jwt/ The Concierge can validate , which are commonly issued by identity providers. This guide shows you how to use this capability in conjunction with the Pinniped Supervisor. Each FederationDomain defined in a Pinniped Supervisor acts as an OIDC issuer. By installing the Pinniped Concierge on multiple Kubernetes clusters, and by configuring each cluster's Concierge as described below to trust JWT tokens from a single Supervisor's FederationDomain, your clusters' users may safely use their identity across all of those clusters. Users of these clusters will enjoy a unified, once-a-day login experience for all the clusters with their `kubectl` CLI. If you would rather not use the Supervisor, you may want to instead. This how-to guide assumes that you have already with working ingress, and that you have . It also assumes that you have configured an `OIDCIdentityProvider`, `LDAPIdentityProvider`, or `ActiveDirectoryIdentityProvider` for the Supervisor as the source of your user's identities. Various examples of configuring these resources can be found in these guides. It also assumes that you have already on all the clusters in which you would like to allow users to have a unified identity. Create a JWTAuthenticator describing how to validate tokens from your Supervisor's FederationDomain: ```yaml apiVersion: authentication.concierge.pinniped.dev/v1alpha1 kind: JWTAuthenticator metadata: name: my-supervisor-authenticator spec: issuer: https://my-issuer.example.com/any/path audience: my-unique-cluster-identifier-da79fa849 tls: certificateAuthorityData: LS0tLS1CRUdJTiBDRVJUSUZJQ0...0tLQo= ``` If you've saved this into a file `my-supervisor-authenticator.yaml`, then install it into your cluster using: ```sh kubectl apply -f my-supervisor-authenticator.yaml ``` Do this on each cluster in which you would like to allow users from that FederationDomain to log in. Don't forget to give each cluster a unique `audience` value for security reasons. Next, !
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-ddl-drop-function.md

layout: global title: DROP FUNCTION displayTitle: DROP FUNCTION license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. The `DROP FUNCTION` statement drops a temporary or user defined function (UDF). An exception will be thrown if the function does not exist. ```sql DROP [ TEMPORARY ] FUNCTION [ IF EXISTS ] function_name ``` function_name* Specifies the name of an existing function. The function name may be optionally qualified with a database name. Syntax: `[ databasename. ] functionname` TEMPORARY* Should be used to delete the `TEMPORARY` function. IF EXISTS* If specified, no exception is thrown when the function does not exist. ```sql -- Create a permanent function `test_avg` CREATE FUNCTION test_avg AS 'org.apache.hadoop.hive.ql.udf.generic.GenericUDAFAverage'; -- List user functions SHOW USER FUNCTIONS; +-+ | function| +-+ |default.test_avg| +-+ -- Create Temporary function `test_avg` CREATE TEMPORARY FUNCTION test_avg AS 'org.apache.hadoop.hive.ql.udf.generic.GenericUDAFAverage'; -- List user functions SHOW USER FUNCTIONS; +-+ | function| +-+ |default.test_avg| | test_avg| +-+ -- Drop Permanent function DROP FUNCTION test_avg; -- Try to drop Permanent function which is not present DROP FUNCTION test_avg; Error: Error running query: org.apache.spark.sql.catalyst.analysis.NoSuchPermanentFunctionException: Function 'default.test_avg' not found in database 'default'; (state=,code=0) -- List the functions after dropping, it should list only temporary function SHOW USER FUNCTIONS; +--+ |function| +--+ |test_avg| +--+ -- Drop Temporary function DROP TEMPORARY FUNCTION IF EXISTS test_avg; ```
Project: ClickHouse (App Definition and Development / Database)
File: v23.2.7.32-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fixed excessive reading in queries with `FINAL`. (). Backported in : Fix glibc compatibility check: replace `preadv` from musl. (). Fix key not found error for queries with multiple StorageJoin (). Fix race on Outdated parts loading (). Fix bug in DISTINCT (). Fix msan issue in randomStringUTF8(<uneven number>) (). Fix IPv6 encoding in protobuf (). Avoid deadlock when starting table in attach thread of `ReplicatedMergeTree` (). JIT compilation not equals NaN fix (). Fix crash with `multiIf` and constant condition and nullable arguments (). Fix Keeper deadlock on exception when preprocessing requests. (). Improve test reports (). Fallback auth gh api (). Improve CI: status commit, auth for getghapi (). Update github.com/distribution/distribution (). Catch issues with dockerd during the build ().