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

slug: /en/sql-reference/aggregate-functions/reference/quantiletdigestweighted sidebar_position: 208 Computes an approximate of a numeric data sequence using the algorithm. The function takes into account the weight of each sequence member. The maximum error is 1%. Memory consumption is `log(n)`, where `n` is a number of values. The performance of the function is lower than performance of or . In terms of the ratio of State size to precision, this function is much better than `quantile`. The result depends on the order of running the query, and is nondeterministic. When using multiple `quantile*` functions with different levels in a query, the internal states are not combined (that is, the query works less efficiently than it could). In this case, use the function. :::note Using `quantileTDigestWeighted` and can lead to significant error. In this case, consider possibility of using instead. ::: Syntax ``` sql quantileTDigestWeighted(level)(expr, weight) ``` Alias: `medianTDigestWeighted`. Arguments `level` Level of quantile. Optional parameter. Constant floating-point number from 0 to 1. We recommend using a `level` value in the range of `. `expr` Expression over the column values resulting in numeric , or . `weight` Column with weights of sequence elements. Weight is a number of value occurrences. Returned value Approximate quantile of the specified level. Type: for numeric data type input. if input values have the `Date` type. if input values have the `DateTime` type. Example Query: ``` sql SELECT quantileTDigestWeighted(number, 1) FROM numbers(10) ``` Result: ``` text quantileTDigestWeighted(number, 1) 4.5 ``` See Also
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_kubeblocks_upgrade.md

title: kbcli kubeblocks upgrade Upgrade KubeBlocks. ``` kbcli kubeblocks upgrade [flags] ``` ``` kbcli kubeblocks upgrade --version=0.4.0 kbcli kubeblocks upgrade --set replicaCount=3 ``` ``` --auto-approve Skip interactive approval before upgrading KubeBlocks --check Check kubernetes environment before upgrade (default true) -h, --help help for upgrade --set stringArray Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) --set-file stringArray Set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2) --set-json stringArray Set JSON values on the command line (can specify multiple or separate values with commas: key1=jsonval1,key2=jsonval2) --set-string stringArray Set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) --timeout duration Time to wait for upgrading KubeBlocks, such as --timeout=10m (default 5m0s) -f, --values strings Specify values in a YAML file or a URL (can specify multiple) --version string Set KubeBlocks version --wait Wait for KubeBlocks to be ready. It will wait for a --timeout period (default true) ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - KubeBlocks operation commands.
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_workspace.md

Workspace is a logical concept representing a target that stacks will be deployed to Workspace is a logical concept representing a target that stacks will be deployed to. Workspace is managed by platform engineers, which contains a set of configurations that application developers do not want or should not concern, and is reused by multiple stacks belonging to different projects. ``` kusion workspace [flags] ``` ``` -h, --help help for workspace ``` ``` --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") ``` - Kusion is the Platform Orchestrator of Internal Developer Platform - Create a new workspace - Delete a workspace - List all workspace names - Show a workspace configuration - Update a workspace configuration
Project: Open Policy Containers (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Welcome, and thank you for considering contributing to OPCR. We encourage you to help out by raising issues, improving documentation, fixing bugs, or adding new features If you're interested in contributing please start by reading this document. If you have any questions at all, or don't know where to start, please reach out to us on . Please also take a look at our , which details how contributors are expected to conduct themselves as part of the OPCR community. To contribute bug fixes or features to OPCR: Communicate your intent. Make your changes. Test your changes. Update documentation and examples where appropriate. Open a Pull Request (PR). Communicating your intent lets the OPCR maintainers know that you intend to contribute, and how. This sets you up for success - you can avoid duplicating an effort that may already be underway, adding a feature that may be rejected, or heading down a path that you would be steered away from at review time. The best way to communicate your intent is via a detailed GitHub issue. Take a look first to see if there's already an issue relating to the thing you'd like to contribute. If there isn't, please raise a new one! Let us know what you'd like to work on, and why. The Open Policy Registry maintainers can't always triage new issues immediately, but we encourage you to bring them to our attention via .
Project: YugabyteDB (App Definition and Development / Database)
File: upgrade-nodes-csp.md

title: Apply operating system upgrades and patches to universe nodes headerTitle: Patch and upgrade the Linux operating system linkTitle: Patch Linux OS description: Apply operating system upgrades and patches to universe nodes. headcontent: Apply operating system upgrades and patches to universe nodes menu: stable_yugabyte-platform: identifier: upgrade-nodes-1-csp parent: manage-deployments weight: 10 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../upgrade-nodes-csp/" class="nav-link active"> <i class="fa-solid fa-cloud"></i> Public Cloud </a> </li> <li > <a href="../upgrade-nodes/" class="nav-link"> <i class="fa-solid fa-building"></i> On-premises </a> </li> <!-- <li> <a href="../kubernetes/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Kubernetes </a> </li> --> </ul> You can apply operating system patches and upgrades to running universes on AWS, GCP, and Azure. Upgrades are performed via a rolling update, where one node in the universe is taken offline, patched, and restarted before updating the next. The universe continues to function normally during this process, however the upgrade can impact performance. For best results, do the following: Perform upgrades during low traffic periods to reduce the impact of rolling updates. Avoid performing upgrades during scheduled backups. If your universe uses a Linux version managed by YugabyteDB Anywhere, updated images are automatically added to the provider. If your universe uses a custom Linux version and you want to upgrade to a new custom version, you must first add the updated custom Linux version to the universe provider configuration. Refer to . To apply operating system patch or upgrade, do the following: Navigate to your universe, click Actions, and choose Upgrade Linux Version. Select the target version. If the universe has a read replica, to select a different Linux version for the replica, deselect the Use the same version for the primary cluster and the read replicas option and select the version to use for the read replica. Specify the delay (in seconds) between restarting servers for the rolling upgrade. Click Upgrade. When finished, you can confirm all nodes in the universe are running correctly in YBA by navigating to the universe Nodes tab.
Project: StarRocks (App Definition and Development / Database)
File: repeat.md

displayed_sidebar: "English" This function repeats `str` by a number of times according to `count`. When `count` is below 1, it returns an empty string. When `str` or `count` is NULL, it returns NULL. ```Haskell VARCHAR repeat(VARCHAR str, INT count) ``` ```Plain Text MySQL > SELECT repeat("a", 3); +-+ | repeat('a', 3) | +-+ | aaa | +-+ MySQL > SELECT repeat("a", -1); +--+ | repeat('a', -1) | +--+ | | +--+ ``` REPEAT,
Project: Meshery (Provisioning / Automation & Configuration)
File: installation-brew.md

You need to have `Brew` installed on your Linux or macOS system to perform these actions. To install `mesheryctl` using homebrew, execute the following commands. <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs"> $ brew install mesheryctl </div></div> </pre> You're ready to run Meshery. To do so, execute the following command. <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs"> $ mesheryctl system start </div></div> </pre> Meshery server supports customizing authentication flow callback URL, which can be configured in the following way <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs"> $ MESHERYSERVERCALLBACK_URL=https://custom-host mesheryctl system start </div></div> </pre> `mesheryctl` uses your current Kubernetes context, your KUBECONFIG environment variable (`~/.kube/config` by default). Confirm if this Kubernetes cluster you want Meshery to interact with by running the following command: `kubectl config get-contexts`. If there are multiple contexts in your kubeconfig file, specify the one you want to use with the `use-context` subcommand: `kubectl config use-context <context-to-use>`. To upgrade `mesheryctl`, execute the following command. <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs"> $ brew upgrade mesheryctl </div></div> </pre> <details> <summary> Example output of a successful upgrade. </summary> <pre><code> ~ brew upgrade mesheryctl ==> Upgrading 1 outdated package: meshery/tap/mesheryctl 0.3.2 -> 0.3.4 ==> Upgrading meshery/tap/mesheryctl ==> Downloading https://github.com/layer5io/meshery/releases/download/v0.3.4/mesheryctl0.3.4Darwinx8664.zip ==> Downloading from https://github-production-release-asset-2e65be.s3.amazonaws.com/157554479/17522b00-2af0-11ea-8aef-cbfe8 /usr/local/Cellar/mesheryctl/0.3.4: 5 files, 10.2MB, built in 4 seconds Removing: /usr/local/Cellar/mesheryctl/0.3.2... (5 files, 10.2MB) Removing: /Users/lee/Library/Caches/Homebrew/mesheryctl--0.3.2.zip... (3.9MB) ==> Checking for dependents of upgraded formulae... ==> No dependents found! </code></pre> <br /> </details>
Project: StarRocks (App Definition and Development / Database)
File: arrays_overlap.md

displayed_sidebar: "English" Checks whether the intersection of two arrays is empty. The arrays that you specify must be of the same data type. If the intersection is empty, this function returns `0`. Otherwise, this function returns `1`. ```Haskell arrays_overlap(input0, input1) ``` `input0`: one of the two arrays that you want to compare. `input1`: the other of the two arrays that you want to compare. The value of this parameter must be of the same data type as the value of the `input0` parameter. Returns a value of the BOOLEAN data type. Example 1: ```Plain mysql> select arrays_overlap([11, 9, 3, 2], [null, 11]); +--+ | arrays_overlap([11,9,3,2], [NULL,11]) | +--+ | 1 | +--+ ``` Example 2: ```Plain mysql> select arrays_overlap([9, 3, 2], [null, 11]); +--+ | arrays_overlap([9,3,2], [NULL,11]) | +--+ | 0 | +--+ ``` Example 3: ```Plain mysql> select arrays_overlap([9, 3, null, 2], [null, 11]); +-+ | arrays_overlap([9,3,NULL,2], [NULL,11]) | +-+ | 1 | +-+ ``` Example 4: ```Plain mysql> select arrays_overlap([9, 3, "SQL", 2], [null, "SQL"]); +--+ | arrays_overlap([9,3,'SQL',2], [NULL,'SQL']) | +--+ | 1 | +--+ ```
Project: Kapitan (Provisioning / Automation & Configuration)
File: kap_8_google_secret_management.md

This feature will enable users to retrieve secrets from Google Secret Manager API using the `gsm` keyword. `project_id` uniquely identifies GCP projects, and it needs to be made accessible to kapitan in one of the following ways: As a part of target ```yaml parameters: kapitan: secrets: gsm: projectid: ProjectId ``` As a flag ```shell kapitan refs --google-project-id=<ProjectId> --write gsm:/path/to/secretid -f secretidfile.txt ``` As an environment variable ```shell export PROJECTID=<ProjectId> ``` In GCP, a secret contains one or more secret versions, along with its metadata. The actual contents of a secret are stored in a secret version. Each secret is identified by a name. We call that variable `secretid` e.g. my\treasured\secret_. The URI of the secret becomes `projects/<ProjectId>/secrets/mytreasured_secret` The following command will be used to add a `secret_id` to kapitan. ```shell echo "mytreasuredsecret" | kapitan refs --write gsm:path/to/secretinsidekapitan -t <target_name> -f - ``` The `-t <targetname>` is used to get the information about ProjectID. The `secretid` is Base64 encoded and stored in `path/to/secretinside_kapitan` as ```yaml data: bXlfdHJlYXN1cmVkX3NlY3JldAo= encoding: original type: gsm gsm_params: projectid: ProjectID ``` Secrets can be refered using `?{gsm:path/to/secretid:versionid}` e.g. ```yaml parameter: mysql: storage: 10G storage_class: standard image: mysql:latest users: root: password: ?{gsm:path/to/secretid:versionid} ``` Here, `version_id` will be an optional argument. By default it will point to `latest`. After compilation, the secret reference will be postfixed with 8 characters from the sha256 hash of the retrieved password ```yaml apiVersion: v1 data: MYSQLROOTPASSWORD: ?{gsm:path/to/secretid:versionid:deadbeef} kind: Secret metadata: labels: name: example-mysql name: example-mysql namespace: minikube-mysql type: Opaque ``` To reveal the secret, the following command will be used `$ kapitan ref --reveal -f compiled/file/containing/secret` note Kapitan will not be responsible for authentication or access management to GCP
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.7.2.md

When enabling the API logging preview feature, a nil reference can occur and crash the sidecar. In addition, the logged API for gRPC is being fixed not to include a memory address but just the method's name. Logic for API logging in gRPC did not initialize logger object for internal service to service communication for Dapr sidecar.See . Skip logging for internal gRPC invocation and print method name only for other gRPC API calls.
Project: KICS (Provisioning / Security & Compliance)
File: 9f751a80-31f0-43a3-926c-20772791a038.md

title: Nifcloud LB Listener Use HTTP Port hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9f751a80-31f0-43a3-926c-20772791a038 Query name: Nifcloud LB Listener Use HTTP Port Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: The lb listener use http port<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloudloadbalancer_listener" "positive" { loadbalancername = "example" instance_port = 80 loadbalancerport = 80 } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloudloadbalancer_listener" "negative" { loadbalancername = "example" instance_port = 443 loadbalancerport = 443 } ```
Project: YugabyteDB (App Definition and Development / Database)
File: security-checklist-yp.md

title: Security checklist for YugabyteDB Anywhere headerTitle: Security checklist linkTitle: Security checklist description: Security measures that can be implemented to protect your YugabyteDB Anywhere and YugabyteDB universes. menu: v2.18_yugabyte-platform: parent: security identifier: security-checklist-yp weight: 10 type: docs You can apply security measures to protect your YugabyteDB Anywhere and YugabyteDB universes. Encryption in transit (TLS) ensures that network communication between servers is secure. You can configure YugabyteDB to use TLS to encrypt intra-cluster and client to server network communication. It is recommended to enable encryption in transit in YugabyteDB clusters and clients to ensure the privacy and integrity of data transferred over the network. For more information, see . Encryption at rest ensures that data at rest, stored on disk, is protected. You can configure YugabyteDB with a user-generated symmetric key to perform cluster-wide encryption. For more information, see . Roles can be assigned to grant users only the essential privileges based on the operations they need to perform against YugabyteDB Anywhere. Typically, a Super Admin role is created first. The Super Admin can create additional admins and other users with fewer privileges. For information on how to enable role-based access control in YugabyteDB Anywhere, see . Authentication requires that all clients provide valid credentials before they can connect to a YugabyteDB cluster. The authentication credentials in YugabyteDB are stored internally in the YB-Master system tables. The authentication mechanisms available to users depends on what is supported and exposed by the YSQL, YCQL, and YEDIS APIs. For more information, see .
Project: KICS (Provisioning / Security & Compliance)
File: 8fdb08a0-a868-4fdf-9c27-ccab0237f1ab.md

title: ElastiCache Redis Cluster Without Backup hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8fdb08a0-a868-4fdf-9c27-ccab0237f1ab Query name: ElastiCache Redis Cluster Without Backup Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Backup URL: ElastiCache Redis cluster should have 'snapshotretentionlimit' higher than 0<br> ```tf title="Positive test num. 1 - tf file" hl_lines="16 1" resource "awselasticachecluster" "positive1" { cluster_id = "cluster" engine = "redis" node_type = "cache.m5.large" numcachenodes = 1 parametergroupname = awselasticacheparameter_group.default.id } resource "awselasticachecluster" "positive2" { cluster_id = "cluster" engine = "redis" node_type = "cache.m5.large" numcachenodes = 1 parametergroupname = awselasticacheparameter_group.default.id snapshotretentionlimit = 0 } resource "awselasticacheparameter_group" "default" { name = "cache-params" family = "redis2.8" parameter { name = "activerehashing" value = "yes" } parameter { name = "min-slaves-to-write" value = "2" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awselasticachecluster" "negative1" { cluster_id = "cluster" engine = "redis" node_type = "cache.m5.large" numcachenodes = 1 parametergroupname = awselasticacheparameter_group.default.id snapshotretentionlimit = 5 } resource "awselasticacheparameter_group" "default" { name = "cache-params" family = "redis2.8" parameter { name = "activerehashing" value = "yes" } parameter { name = "min-slaves-to-write" value = "2" } } ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.5.29-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Add setting to disable limit on kafkanumconsumers. Closes . (). Backported in : The setting `showaddressesinstacktraces` was accidentally disabled in default `config.xml`. It's removed from the config now, so the setting is enabled by default. (). Backported in : Fix issue with passing MySQL timeouts for MySQL database engine and MySQL table function. Closes ?notificationreferrerid=NT_kwDOAzsV57MzMDMxNjAzNTY5OjU0MjAzODc5. (). Backported in : Add macOS binaries to GH release assets, it fixes . (). Backported in : - Fix crash while parsing values of type `Object` that contains arrays of variadic dimension. (). Backported in : During insertion of a new query to the `ProcessList` allocations happen. If we reach the memory limit during these allocations we can not use `OvercommitTracker`, because `ProcessList::mutex` is already acquired. Fixes . (). Backported in : Fix memory leak while pushing to MVs w/o query context (from Kafka/...). (). Backported in : Fix access rights for `DESCRIBE TABLE url()` and some other `DESCRIBE TABLE <table_function>()`. (). Backported in : Fixed "possible deadlock avoided" error on automatic conversion of database engine from Ordinary to Atomic. (). Backported in : Fix background clean up of broken detached parts. (). use ROBOTCLICKHOUSECOMMIT_TOKEN for create-pull-request (). use input token instead of env var (). CaresPTRResolver small safety improvement ().
Project: Harbor (Provisioning / Container Registry)
File: 1-01-DB-user-registration.md

Test 1-01 - User Registration (DB Mode) ======= To verify that a non-admin user can register an account (signup) when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). On the Harbor's home page, click "Sign Up" Enter user information to register a user. Use the username of the newly registered user to log in to the UI. Log out from the UI. Use the email of the newly registered user to log in to the UI. On a Docker client host, use `docker login <harbor_host>` command to verify the user can log in by either the username or email . (verify both) Log out from the UI and register another new user. Try to provide invalid values of input to see if validation works: username is the same as an existing user username is very long in length wrong email formatting email is very long in length password input does not compliant to password rule two passwords do not match A new user created in step 2. The new user can log in via UI in Step 3 and Step 5. The new user can log in via docker client in Step 6 by email and username. Invalid input during sign up can be rejected, proper error messages can be displayed in Step 7. None