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

sidebar_position: 1 sidebar_label: 2024 Backported in : Copy S3 file GCP fallback to buffer copy in case GCP returned `Internal Error` with `GATEWAY_TIMEOUT` HTTP error code. (). Backported in : Update tzdata to 2024a. (). Backported in : If you want to run initdb scripts every time when ClickHouse container is starting you shoud initialize environment varible CLICKHOUSEALWAYSRUNINITDBSCRIPTS. (). Fixkqlissuefoundby_wingfuzz (). Fix error "Read beyond last offset" for AsynchronousBoundedReadBuffer (). Fix query start time on non initial queries (). rabbitmq: fix having neither acked nor nacked messages (). Fix parsing of partition expressions surrounded by parens (). Fix optimizeuniqto_count removing the column alias (). Fix cosineDistance crash with Nullable (). Hide sensitive info for s3queue (). Fix deadlock in parallel parsing when lots of rows are skipped due to errors (). Fixmaxquerysizeforkqlcompound_operator: (). Reduce the number of read rows from `system.numbers` (). Fix buffer overflow in CompressionCodecMultiple (). Remove nonsense from SQL/JSON (). Prevent setting custom metadata headers on unsupported multipart upload operations (). Fix crash in arrayEnumerateRanked (). Fix crash when using input() in INSERT SELECT JOIN (). Fix crash with different allowexperimentalanalyzer value in subqueries (). Remove recursion when reading from S3 (). Fix Keeper reconfig for standalone binary (). Backported in : Decoupled changes from . (). Backported in : Arm and amd docker build jobs use similar job names and thus overwrite job reports - aarch64 and amd64 suffixes added to fix this. (). Backported in : Debug and fix markreleaseready. (). Backported in : ... (). Backported in : ... (). Backported in : ... (). NO CL ENTRY: 'Revert "Backport to 23.12: CI: do not reuse builds on release branches"'. (). CI: move ci-specifics from job scripts to ci.py (). Make ZooKeeper actually sequentialy consistent (). Fix special build reports in release branches (). CI: do not reuse builds on release branches (). Fix mark release ready (). Ability to detect undead ZooKeeper sessions (). Detect io_uring in tests (). Cancel PipelineExecutor properly in case of exception in spawnThreads (). Remove broken test while we fix it (). Speed up cctools building ().
Project: ClickHouse (App Definition and Development / Database)
File: having.md

slug: /en/sql-reference/statements/select/having sidebar_label: HAVING Allows filtering the aggregation results produced by . It is similar to the clause, but the difference is that `WHERE` is performed before aggregation, while `HAVING` is performed after it. It is possible to reference aggregation results from `SELECT` clause in `HAVING` clause by their alias. Alternatively, `HAVING` clause can filter on results of additional aggregates that are not returned in query results. `HAVING` cant be used if aggregation is not performed. Use `WHERE` instead.
Project: YugabyteDB (App Definition and Development / Database)
File: cloud-queries-slow.md

title: View slow queries in YugabyteDB Managed headerTitle: View slow queries linkTitle: Slow queries description: View slow running queries that have run on your YugabyteDB Managed cluster. headcontent: View slow running queries that have run on your cluster menu: preview_yugabyte-cloud: identifier: cloud-queries-slow parent: cloud-monitor weight: 300 type: docs Evaluate the performance of slow queries that have run on your cluster using the Slow Queries option on the cluster Performance tab. Use this data to: Visually identify slower running database operations. Evaluate query execution times over time. Discover potential queries for . {{< youtube id="hXphqRCQImQ" title="Monitor and optimize queries in YugabyteDB Managed" >}} Slow queries are not available for YCQL. To filter the query list, enter query text in the filter field. To sort the list by column, click the column heading. Click Edit Options to select the columns to display. To reset the slow queries list, click Reset. To view query details, click the right-arrow button for the query in the list to display the Query Details sheet. The following table describes the Slow Queries column values. | Column | Description | | | | | User | The name of role used to access YSQL database. | | Total time | The total duration (in milliseconds) of all iterations this query has taken. | | Count | The total number of times this type of query has executed. | | Rows | The total number of database table rows returned across all iterations of this query | | Database | The YSQL database used by the query. |
Project: Druid (App Definition and Development / Database)
File: password-provider.md

id: password-provider title: "Password providers" <!-- ~ 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. --> Passwords help secure Apache Druid systems such as the metadata store and the keystore that contains server certificates, and so on. These passwords have corresponding runtime properties associated with them, for example `druid.metadata.storage.connector.password` corresponds to the metadata store password. By default users can directly set the passwords in plaintext for runtime properties. For example, `druid.metadata.storage.connector.password=pwd` sets the password to be used by Druid to connect to the metadata store to `pwd`. Alternatively, users can can set passwords as environment variables. Environment variable passwords allow users to avoid exposing passwords in the `runtime.properties` file. You can set an environment variable password as in the following example: ```json druid.metadata.storage.connector.password={ "type": "environment", "variable": "METADATASTORAGEPASSWORD" } ``` The values are described below. |Field|Type|Description|Required| |--|-|--|--| |`type`|String|password provider type|Yes: `environment`| |`variable`|String|environment variable to read password from|Yes| Another option that provides even greater control is to securely fetch passwords at runtime using a custom extension of the `PasswordProvider` interface that is registered at Druid process startup. For more information, see . To use this implementation, simply set the relevant password runtime property similarly to how was shown for the environment variable password: ```json druid.metadata.storage.connector.password={ "type": "<registeredpasswordprovidername>", "<jacksonproperty>": "<value>", ... } ```
Project: ArangoDB (App Definition and Development / Database)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. Expected behavior Please describe what you expected to happen. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error '...' If applicable, add screenshots to help explain your problem. System (please complete the following information): OS: [e.g. Mac] Version [e.g. 22] Compiler [e.g. gcc] Build System [e.g. Makefile] Other hardware specs [e.g Core 2 duo...] Additional context Add any other context about the problem here.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-error-conditions-invalid-interval-format-error-class.md

layout: global title: INVALIDINTERVALFORMAT error class displayTitle: INVALIDINTERVALFORMAT error class 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. <!-- DO NOT EDIT THIS FILE. It was generated automatically by `org.apache.spark.SparkThrowableSuite`. --> Error parsing '`<input>`' to interval. Please ensure that the value provided is in a valid format for defining an interval. You can reference the documentation for the correct format. This error class has the following derived error classes: Uncaught arithmetic exception while parsing '`<input>`'. Interval string cannot be empty. Interval string cannot be null. `<unit>` cannot have fractional part. Interval can only support nanosecond precision, `<value>` is out of range. Invalid interval prefix `<prefix>`. Invalid unit `<unit>`. Invalid value `<value>`. Expect a number after `<word>` but hit EOL. Expect a unit name after `<word>` but hit EOL. Unknown error when parsing `<word>`. Unrecognized number `<number>`.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_explain-config.md

title: kbcli cluster explain-config List the constraint for supported configuration params. ``` kbcli cluster explain-config [flags] ``` ``` kbcli cluster explain-config mycluster kbcli cluster explain-config mycluster --component=mysql --config-specs=mysql-3node-tpl kbcli cluster explain-config mycluster --component=mysql --config-specs=mysql-3node-tpl --trunc-document=false --trunc-enum=false kbcli cluster explain-config mycluster --param=sql_mode ``` ``` --components strings Specify the name of Component to describe (e.g. for apecloud-mysql: --component=mysql). If the cluster has only one component, unset the parameter." --config-specs strings Specify the name of the configuration template to describe. (e.g. for apecloud-mysql: --config-specs=mysql-3node-tpl) -h, --help help for explain-config --param string Specify the name of parameter to be query. It clearly display the details of the parameter. --trunc-document If the document length of the parameter is greater than 100, it will be truncated. --trunc-enum If the value list length of the parameter is greater than 20, it will be truncated. (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 ``` - Cluster command.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: how-to-fix-broken-links.md

In this Monokle tutorial, we will illustrate the steps to fix broken links. Lets get started! <em>Note: Please follow this guide to install Monokle </em> Launch Monokle and, on the welcome screen, there are three options to start working with projects: Select an exisiting folder. Create an empty project. Start from a template. Click Select an existing project to add your project folder containing K8 resources. Select your folder to parse its manifest in the file explorer. In the file explorer, you can view manifests, including their resources, and their relationships. Scroll up & down to navigate and select the required manifests. Once you select a manifest, its related resources will be highlighted automatically in the navigator. Scroll down in the navigator and hover over a resource link with a warning signal. <em>Note: The link with a warning signal indicates that the link is broken.</em> Click on the link provided in the tooltip. <em>Note: The source code for the specific resource will be highlighted automatically in the editor.</em> Manually update the name of the highlighted dead endpoint with a working endpoint to fix the broken link. <em>Note: The warning triangle will automatically go away once a valid link is provided.</em> Please feel free to join our open source community on Discord with this and start your discussion.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.40.md

layout: release date: 2022-12-31 tag: v0.6.40 language: en Solve leftover bug due to merge conflict @Revolyssup (#6813) add a support for CustomTextTooltip in the formContext @harkiratsm (#6815) cypress: assign cy params to validate modal @Abhishek-kumar09 (#6812) [Docs] Meshery CLI Contributing Guide Details and Artifacts @leecalcote (#6811) Updated design spec doc links to point to detailed design spec doc @eeshaanSA (#6797) Add MeshModel endpoints to swagger docs @Revolyssup (#6806) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @eeshaanSA, @harkiratsm, @leecalcote and l5io
Project: kpt (Provisioning / Automation & Configuration)
File: 05-updating-a-package.md

An independent package records the exact commit where the local fork and the upstream package diverged. This enables kpt to fetch any update to the upstream package and merge it with local changes. Before you update the package, you want to commit your local changes. First, to see the changes you've made to the fork of the upstream package: ```shell $ git diff ``` If you're happy with the changes, commit them: ```shell $ git add .; git commit -m "My changes" ``` For example, you can update to version `v0.10` of the `wordpress` package: ```shell $ kpt pkg update wordpress@v0.10 ``` This is a porcelain for manually updating the `upstream` section in the `Kptfile` : ```yaml upstream: type: git git: repo: https://github.com/GoogleContainerTools/kpt directory: /package-examples/wordpress ref: v0.10 updateStrategy: resource-merge ``` and then running: ```shell $ kpt pkg update wordpress ``` The `update` command updates the local `wordpress` package and the dependent `mysql` package to the upstream version `v0.10` by doing a 3-way merge between: Original upstream commit New upstream commit Local (edited) package Several different strategies are available to handle the merge. By default, the `resource-merge` strategy is used which performs a structural comparison of the resource using OpenAPI schema. ?> Refer to the for usage. Once you have successfully updated the package, commit the changes: ```shell $ git add .; git commit -m "Updated wordpress to v0.10" ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_azure_delete.md

Delete an Azure YugabyteDB Anywhere storage configuration Delete an Azure storage configuration in YugabyteDB Anywhere ``` yba storage-config azure delete [flags] ``` ``` -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for delete ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere Azure storage configuration
Project: KICS (Provisioning / Security & Compliance)
File: cb319d87-b90f-485e-a7e7-f2408380f309.md

title: High KMS Key Rotation Period hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: cb319d87-b90f-485e-a7e7-f2408380f309 Query name: High KMS Key Rotation Period Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: KMS Key should have automatic rotation enabled and the rotation period should not be higher than a year<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "alicloudkmskey" "keypos1" { description = "Hello KMS" pendingwindowin_days = "7" status = "Enabled" automatic_rotation = "Disabled" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="6" resource "alicloudkmskey" "keypos1" { description = "Hello KMS" pendingwindowin_days = "7" status = "Enabled" automatic_rotation = "Enabled" rotation_interval = "366d" } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="6" resource "alicloudkmskey" "keypos1" { description = "Hello KMS" pendingwindowin_days = "7" status = "Enabled" automatic_rotation = "Enabled" rotation_interval = "31536010s" } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="1" resource "alicloudkmskey" "keypos1" { description = "Hello KMS" pendingwindowin_days = "7" status = "Enabled" } ``` </details> ```tf title="Negative test num. 1 - tf file" resource "alicloudkmskey" "key" { description = "Hello KMS" pendingwindowin_days = "7" status = "Enabled" automatic_rotation = "Enabled" rotation_interval = "7d" } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: serverless-workflow.md

layout: integration title: Serverless Workflow subtitle: Collaborative and visual infrastructure as code for Serverless Workflow image: /assets/img/integrations/serverless-workflow/icons/color/serverless-workflow-color.svg permalink: extensibility/integrations/serverless-workflow docURL: https://docs.meshery.io/extensibility/integrations/serverless workflow description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: KICS (Provisioning / Security & Compliance)
File: ad0875c1-0b39-4890-9149-173158ba3bba.md

title: Cloud Storage Bucket Versioning Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ad0875c1-0b39-4890-9149-173158ba3bba Query name: Cloud Storage Bucket Versioning Disabled Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Cloud Storage Bucket should have versioning enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: a-new-pubsub-topic type: storage.v1.bucket properties: storageClass: STANDARD location: EUROPE-WEST3 ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="8" resources: name: a-new-pubsub-topic2 type: storage.v1.bucket properties: storageClass: STANDARD location: EUROPE-WEST3 versioning: enabled: false ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: a-new-pubsub-topic3 type: storage.v1.bucket properties: storageClass: STANDARD location: EUROPE-WEST3 versioning: enabled: true ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: restart-a-redis-cluster.md

title: Restart a Redis cluster description: How to restart a Redis cluster keywords: [redis, restart] sidebar_position: 4 sidebar_label: Restart You can restart all pods of the cluster. When an exception occurs in a database, you can try to restart it. :::note Restarting a Redis cluster triggers a concurrent restart and the leader may change after the cluster restarts. ::: Restart a cluster. You can use `kbcli` or create an OpsRequest to restart a cluster. Option 1. (Recommended) Use kbcli Configure the values of `components` and `ttlSecondsAfterSucceed` and run the command below to restart a specified cluster. ```bash kbcli cluster restart redis-cluster --components="redis" \ --ttlSecondsAfterSucceed=30 ``` `components` describes the component name that needs to be restarted. `ttlSecondsAfterSucceed` describes the time to live of an OpsRequest job after the restarting succeeds. Option 2. Create an OpsRequest Run the command below to restart a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: ops-restart spec: clusterRef: redis-cluster type: Restart restart: componentName: redis EOF ``` Validate the restart operation. Check the cluster status to identify the restart status. ```bash kbcli cluster list <name> ``` STATUS=Restarting: it means the cluster restart is in progress. STATUS=Running: it means the cluster has been restarted. *Example* ```bash kbcli cluster list redis-cluster > NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME redis-cluster default redis redis-7.0.x Delete Running Apr 10,2023 19:20 UTC+0800 ```