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

sidebar_position: 1 sidebar_label: 2023 Backported in : Fixed `UNKNOWN_TABLE` exception when attaching to a materialized view that has dependent tables that are not available. This might be useful when trying to restore state from a backup. (). Backported in : Use sccache as a replacement for ccache and using S3 as cache backend. (). Backported in : The `clickhouse/clickhouse-keeper` image used to be pushed only with tags `-alpine`, e.g. `latest-alpine`. As it was suggested in https://github.com/ClickHouse/examples/pull/2, now it will be pushed as suffixless too. (). Fix changing an expired role (). Fix bug in zero-copy replication disk choice during fetch (). Fix NOT_IMPLEMENTED error with CROSS JOIN and algorithm = auto (). Disable logical expression optimizer for expression with aliases. (). Fix query parameters (). Parameterized view bug fix 47287 47247 (). Proper fix for bug in parquet, revert reverted (). Fix wait for zero copy lock during move (). Hotfix for too verbose warnings in HTTP (). fix: keeper systemd service file include invalid inline comment (). Better error messages in ReplicatedMergeTreeAttachThread (). Fix `00933testfixextraseekoncompressed_cache` in releases. (). Fix startup on older systemd versions (). Add a fuse for backport branches w/o a created PR (). Only valid Reviews.STATES overwrite existing reviews (). Place short return before big block, improve logging (). Artifacts s3 prefix (). Fix tsan error lock-order-inversion ().
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: connect-database-in-production-environment.md

title: Connect database in production environment description: How to connect to a database in production environment keywords: [connect to a database, production environment] sidebar_position: 3 sidebar_label: Production environment In the production environment, it is normal to connect a database with CLI and SDK clients. There are three scenarios. Scenario 1: Client1 and the database are in the same Kubernetes cluster. To connect client1 and the database, see . Scenario 2: Client2 is outside the Kubernetes cluster, but it is in the same VPC as the database. To connect client2 and the database, see . Scenario 3: Client3 and the database are in different VPCs, such as other VPCs or the public network. To connect client3 and the database, see . See the figure below to get a clear image of the network location. You can connect with the database ClusterIP or domain name. To check the database endpoint, use `kbcli cluster describe ${cluster-name}`. ```bash kbcli cluster describe x Name: x Created Time: Mar 01,2023 11:45 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY default apecloud-mysql ac-mysql-8.0.30 Running Delete Endpoints: COMPONENT MODE INTERNAL EXTERNAL x ReadWrite x-mysql.default.svc.cluster.local:3306 <none> Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME mysql x-mysql-0 leader Running cn-northwest-1b ip-10-0-2-184.cn-northwest-1.compute.internal/10.0.2.184 Mar 01,2023 11:45 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS mysql false 1 / 1 1Gi / 1Gi data:10Gi <none> Images: COMPONENT TYPE IMAGE mysql mysql registry.cn-hangzhou.aliyuncs.com/apecloud/apecloud-mysql-server:8.0.30-5.alpha2.20230105.gd6b8719.2 Events(last 5 warnings, see more:kbcli cluster list-events -n default x): TIME TYPE REASON OBJECT MESSAGE ``` You can enable the External LoadBalancer of the cloud vendor. :::note The following command creates a LoadBalancer instance for the database instance, which may incur expenses from your cloud vendor. ::: ```bash kbcli cluster expose ${cluster-name} --type internet --enable=true ``` To disable the LoadBalancer instance, execute the following command. ```bash kbcli cluster expose ${cluster-name} --type internet --enable=false ``` :::note The instance is inaccessible after you disable the LoadBalancer instance. ::: A stable domain name for long-term connections is required. An Internal LoadBalancer provided by the cloud vendor can be used for this purpose. :::note The following command creates a LoadBalancer instance for the database instance, which may incur expenses from your cloud vendor. ::: ```bash kbcli cluster expose ${cluster-name} --type vpc --enable=true ``` To disable the LoadBalancer instance, execute the following command. :::note Once disabled, the instance is not accessible. ::: ```bash kbcli cluster expose ${cluster-name} --type vpc --enable=false ```
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-extract-path-text.md

title: jsonbextractpathtext() and jsonextractpathtext() [JSON] headerTitle: jsonbextractpathtext() and jsonextractpathtext() linkTitle: jsonbextractpathtext() and jsonextractpathtext() description: Provide identical functionality to the "#>>" operator. menu: v2.18: identifier: jsonb-extract-path-text parent: json-functions-operators weight: 140 type: docs Purpose: Provide the identical functionality to the operator. Signature For the `jsonb` variant: ``` input value: jsonb, VARIADIC text return value: text ``` Notes: The result of `jsonbextractpathtext()` bears the same relationship to the result of its counterpart as does the result of the operator to that of its counterpart. For the same reason that there is no reason to prefer `jsonbextractpath()` over `#>`, there is no reason to prefer `jsonbextractpathtext()` over `#>>`.
Project: Salt Project (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

Fixes Remove this section if not relevant Remove this section if not relevant [NOTICE] Bug fixes or features added to Salt require tests. <!-- Please review the for details on how to implement tests into Salt's test suite. --> [ ] Docs [ ] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html [ ] Tests written/updated Yes/No Please review for best practices, including the . See GitHub's for more information about signing commits with GPG.
Project: ShardingSphere (App Definition and Development / Database)
File: drop-shadow-rule.en.md

+++ title = "DROP SHADOW RULE" weight = 3 +++ The `DROP SHADOW RULE` syntax is used to drop shadow rule for specified database {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropShadowRule ::= 'DROP' 'SHADOW' 'RULE' ifExists? ruleName ('FROM' databaseName)? ifExists ::= 'IF' 'EXISTS' ruleName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When databaseName is not specified, the default is the currently used DATABASE. If DATABASE is not used, No database selected will be prompted; `ifExists` clause is used for avoid `Shadow rule not exists` error. Drop shadow rule for specified database ```sql DROP SHADOW RULE shadowrule FROM shadowdb; ``` Drop shadow rule for current database ```sql DROP SHADOW RULE shadow_rule; ``` Drop shadow rule with `ifExists` clause ```sql DROP SHADOW RULE IF EXISTS shadow_rule; ``` `DROP`, `SHODOW`, `RULE`, `FROM`
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: userns-uid-map.md

Directly specifies a UID mapping to be used to set ownership, at the filesystem level, on the working container's contents. Commands run when handling `RUN` instructions default to being run in their own user namespaces, configured using the UID and GID maps. Entries in this map take the form of one or more triples of a starting in-container UID, a corresponding starting host-level UID, and the number of consecutive IDs which the map entry represents. This option overrides the remap-uids setting in the options section of /etc/containers/storage.conf. If this option is not specified, but a global --userns-uid-map setting is supplied, settings from the global option is used. If none of --userns-uid-map-user, --userns-gid-map-group, or --userns-uid-map are specified, but --userns-gid-map is specified, the UID map is set to use the same numeric values as the GID map.
Project: KICS (Provisioning / Security & Compliance)
File: ac1564a3-c324-4747-9fa1-9dfc234dace0.md

title: Shared Host Network Namespace hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ac1564a3-c324-4747-9fa1-9dfc234dace0 Query name: Shared Host Network Namespace Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: Container should not share the host network namespace<br> ```tf title="Positive test num. 1 - tf file" hl_lines="7" resource "kubernetes_pod" "test" { metadata { name = "terraform-example" } spec { host_network = 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" "test2" { metadata { name = "terraform-example" } spec { host_network = 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: Harbor (Provisioning / Container Registry)
File: 9-03-DB-user-pull-signed-images.md

Test 9-03 User pull signed images(DB mode) ======= To verify user can pull signed images. User guide This test requires one Harbor instance is running and available. A Linux machine with Docker CLI(Docker client) installed. NOTE: In below test, project X should be replaced by an existing project and <harborip> should be replaced by your harbor's ip or FQDN. If you are using a self-signed certificate,make sure to copy the CA root cert into ```/etc/docker/certs.d/<harborip>``` and ```$HOME/.docker/tls/<harbor_ip>:4443/``` Login UI. On Docker client, run ```sh export DOCKERCONTENTTRUST=1 export DOCKERCONTENTTRUSTSERVER=https://<harborip>:4443 ``` and login Harbor. Pull an image from project X. Image can be pulled successful. None
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: e5.6.1.en.md

Do not save invalid uploaded backup files. Rename `messagequeuetoolong` error reason to `mailboxoverflow` `mailboxoverflow` is consistent with the corresponding config parameter: `forceshutdown.maxmailboxsize`. Upgrade HTTP client libraries. The HTTP client library (`gun-1.3`) incorrectly appends a `:portnumber` suffix to the `Host` header for standard ports (`http` on port 80, `https` on port 443). This could cause compatibility issues with servers or gateways performing strict `Host` header checks (e.g., AWS Lambda, Alibaba Cloud HTTP gateways), leading to errors such as `InvalidCustomDomain.NotFound` or "The specified CustomDomain does not exist." Improve cluster discovery behaviour when a node is manually removed from a cluster using 'emqx ctl cluster leave' command. Previously, if the configured cluster 'discovery_strategy' was not 'manual', the left node might re-discover and re-join the same cluster shortly after it left (unless it was stopped). After this change, 'cluster leave' command disables automatic cluster_discovery, so that the left node won't re-join the same cluster again. Cluster discovery can be re-enabled by running 'emqx ctl discovery enable` or by restarting the left node. Handle several errors in `/clients/{clientid}/mqueuemessages` and `/clients/{clientid}/inflightmessages` APIs: Internal timeout, which means that EMQX failed to get the list of Inflight/Mqueue messages within the default timeout of 5 s. This error may occur when the system is under a heavy load. The API will return 500 `{"code":"INTERNAL_ERROR","message":"timeout"}` response and log additional details. Client shutdown. The error may occur if the client connection is shutdown during the API call. The API will return 404 `{"code": "CLIENT_SHUTDOWN", "message": "Client connection has been shutdown"}` response in this case. Make sure stats `'subscribers.count'` `'subscribers.max'` countains shared-subscribers. It only contains non-shared subscribers previously. Fixed an issue that prevented importing source data integrations and retained messages. Before the fix: source data integrations are ignored from the backup file importing the `mnesia` table for retained messages are not supported Fixed `clusterrpccommit` transaction ID cleanup procedure after `cluster leave` on replicant nodes. Previously, the transaction id of the core node would be deleted prematurely, blocking configuration updates on the core node. The RocketMQ action has been fixed so that the topic configiuration works correctly. If more than one action used a single connector before this fix, all actions messages got delivered to the topic that was used first. Fixed an issue when users were not able to see the "Retained Messages" under the "Monitoring" menu in the admin dashboard. "Retained messages" backend API uses `qlc`, and `qlc` uses `file_sorter` that puts temporary files in the working directory by default, which is not writable by emqx user since 58d0f04. This patch fixes this by making `/opt/emqx` directory owned by `emqx:emqx`.
Project: KICS (Provisioning / Security & Compliance)
File: 7d544dad-8a6c-431c-84c1-5f07fe9afc0e.md

title: Group With Privilege Escalation By Actions 'glue:CreateDevEndpoint' And 'iam:PassRole' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7d544dad-8a6c-431c-84c1-5f07fe9afc0e Query name: Group With Privilege Escalation By Actions 'glue:CreateDevEndpoint' And 'iam:PassRole' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'glue:CreateDevEndpoint' and 'iam:PassRole' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "glue:CreateDevEndpoint", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" groups = [awsiamgroup.cosmic.name] policyarn = awsiam_policy.policy.arn } resource "awsiampolicy" "policy" { name = "test-policy" description = "A test policy" policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PassRole", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: ArangoDB (App Definition and Development / Database)
File: errno.md

+++ title = "errno" description = "errno with their good and bad sides." weight = 20 +++ The idiom of returning, upon failure, a special value and storing an error code (an `int`) inside a global (or thread-local) object `errno` is inherited from C, and used in its Standard Library: ```c++ int readValue(const char * filename) { FILE* f = fopen(filename, "r"); if (f == NULL) return 0; // special value indicating failure // keep errno value set by fopen() int i; int r = fscanf(f, "%d", &i); if (r == 0 || r == EOF) { // special values: i not read errno = ENODATA; // choose error value to return return 0; fclose(f); errno = 0; // clear error info (success) return i; } ``` One advantage (to some, and a disadvantage to others) of this technique is that it uses familiar control statements (`if` and `return`) to indicate all execution paths that handle failures. When we read this code we know when and under what conditions it can exit without producing the expected result. Because on failure, as well as success, we write into a global (or thread-local) object, our functions are not pure: they have side effects. This means many useful compiler optimizations (like common subexpression elimination) cannot be applied. This shows that it is not only C++ that chooses suboptimal solutions for reporting failures. Whatever type we return, we always need a special value to spare, which is sometimes troublesome. In the above example, if the successfully read value of `i` is `0`, and we return it, our callers will think it is a failure even though it is not. Error propagation using `if` statements and early `return`s is manual. We can easily forget to check for the failure, and incorrectly let the subsequent operations execute, potentially causing damage to the program state. Upon nearly each function call layer we may have to change error code value so that it reflects the error condition adequate to the current layer. If we do so, the original error code is gone.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_reset_dependencies.md

title: "Command - devspace reset dependencies" sidebar_label: devspace reset dependencies Resets the dependencies cache ``` devspace reset dependencies [flags] ``` ``` Deletes the complete dependency cache Examples: devspace reset dependencies ``` ``` -h, --help help for dependencies ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --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 strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: 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) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: erlang-distributions-compare-10988.md

Erlang Distribution traffic, node network traffic and CPU + PerfTest message throughput and latency RabbitMQ Compare the effects of running Erlang Distribution with different compression algorithms (deflate, lz4, zstd, etc.) Metrics displayed: Erlang Distribution outgoing link traffic / s Network incoming & outgoing traffic / s CPU utilisation Messages published & consumed / s End-to-end message latency Filter by: RabbitMQ Cluster PerfTest Instance & message latency percentile Host when using Container when using Depends on `rabbitmq-prometheus` plugin, built-in since Learn more about To get it working locally with RabbitMQ in 3 simple steps, follow this
Project: ShardingSphere (App Definition and Development / Database)
File: sql-parser.en.md

+++ title = "SQL-parser" weight = 8 +++ The SQL parser YAML configuration is readable and easy to use. The YAML files allow you to separate the code from the configuration, and easily modify the configuration file as needed. ```yaml sqlParser: sqlStatementCache: # SQL statement local cache initialCapacity: # Initial capacity of local cache maximumSize: # Maximum capacity of local cache parseTreeCache: # Parse tree local cache initialCapacity: # Initial capacity of local cache maximumSize: # Maximum capacity of local cache ``` Set local cache configuration. Set parser configuration. Use a parsing engine to parse SQL. ```yaml sqlParser: sqlStatementCache: initialCapacity: 2000 maximumSize: 65535 parseTreeCache: initialCapacity: 128 maximumSize: 1024 ```
Project: Harbor (Provisioning / Container Registry)
File: 7-11-Project-admin-readonly.md

Test 7-11 Project admin read-only privilege ======= To verify project admin user has read-only privilege for replication rules and jobs. User guide This test requires at least two Harbor instance are running and available. At least a replication rule is created. The replication rule has at least one job. A member has been added to the project that the rule is applied to as admin. Login UI using the project admin user. Go to `Projects->Project_Name->Replication` page. In step2, the user should have read-only privilege to all rules and jobs. None