cwielenb/CNCF-Dataset huggingface dataset:
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_set_encryptionkey.md

title: "Command - devspace set encryptionkey" sidebar_label: devspace set encryptionkey Sets the encryption ``` devspace set encryptionkey [flags] ``` ``` Sets an encryption key for a given cluster Examples: devspace set encryptionkey mykey --cluster mycluster devspace set encryptionkey --cluster mycluster --reset ``` ``` --cluster string The cluster to apply this key for -h, --help help for encryptionkey ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-array-length.md

title: jsonbarraylength() and jsonarraylength() linkTitle: jsonbarraylength() headerTitle: jsonbarraylength() and jsonarraylength() description: Return the count of values in an array using jsonbarraylength() and jsonarraylength(). menu: v2.18: identifier: jsonb-array-length parent: json-functions-operators weight: 80 type: docs Purpose: Return the count of values (primitive or compound) in the array. You can use this to iterate over the elements of a JSON array using the operator. Signature For the `jsonb` variant: ``` input value: jsonb return value: integer ``` Notes: Each function in this pair requires that the supplied JSON value is an array. ```plpgsql do $body$ declare j constant jsonb := '["a", 42, true, null]'; lastidx constant int := (jsonbarray_length(j) - 1); expected_typeof constant text[] := array['string', 'number', 'boolean', 'null']; begin for n in 0..last_idx loop assert jsonbtypeof(j -> n) = expectedtypeof[n + 1], 'unexpected'; end loop; end; $body$; ``` This example uses the function. Reading the values themselves would need to use a `case` statement that tests the emergent JSON data type and that selects the leg whose assignment target has the right SQL data type. This is straightforward only for primitive JSON values. If a compound JSON value is encountered, then it must be decomposed, recursively, until the ultimate JSON primitive value leaves are reached. This complexity reflects the underlying impedance mismatch between the JSON type system and the SQL type system. Introspecting a JSON value when you have no a priori understanding of its structure is tricky.
Project: StarRocks (App Definition and Development / Database)
File: date_slice.md

displayed_sidebar: "English" Converts a given time into the beginning or end of a time interval based on the specified time granularity. This function is supported from v2.5. ```Haskell DATE date_slice(DATE dt, INTERVAL N type[, boundary]) ``` `dt`: the time to convert, DATE. `INTERVAL N type`: the time granularity, for example, `interval 5 day`. `N` is the length of time interval. It must be an INT value. `type` is the unit, which can be YEAR, QUARTER, MONTH, WEEK, DAY, HOUR, MINUTE, SECOND. If `type` is set to HOUR, MINUTE, or SECOND for a DATE value, an error is returned. `boundary`: optional. It is used to specify whether to return the beginning (`FLOOR`) or end (`CEIL`) of the time interval. Valid values: FLOOR, CEIL. If this parameter is not specified, `FLOOR` is the default. Returns a value of the DATE type. The time interval starts from A.D. `0001-01-01 00:00:00`. Example 1: Convert a given time to the beginning of a 5-year time interval without specifying the `boundary` parameter. ```Plaintext select date_slice('2022-04-26', interval 5 year); +--+ | date_slice('2022-04-26', INTERVAL 5 year, floor) | +--+ | 2021-01-01 | +--+ ``` Example 2: Convert a given time to the end of a 5-day time interval. ```Plaintext select date_slice('0001-01-07', interval 5 day, CEIL); ++ | date_slice('0001-01-07', INTERVAL 5 day, ceil) | ++ | 0001-01-11 | ++ ``` The following examples are provided based on the `testalltype_select` table. ```Plaintext select * from testalltypeselect order by idint; +++--+ | iddate | iddatetime | id_int | +++--+ | 2052-12-26 | 1691-12-23 04:01:09 | 0 | | 2168-08-05 | 2169-12-18 15:44:31 | 1 | | 1737-02-06 | 1840-11-23 13:09:50 | 2 | | 2245-10-01 | 1751-03-21 00:19:04 | 3 | | 1889-10-27 | 1861-09-12 13:28:18 | 4 | +++--+ 5 rows in set (0.06 sec) ``` Example 3: Convert a given DATE value to the beginning of a 5-second time interval. ```Plaintext select dateslice(iddate, interval 5 second, FLOOR) from testalltype_select order by id_int; ERROR 1064 (HY000): can't use date_slice for date with time(hour/minute/second) ``` An error is returned because the system cannot find the second part of a DATE value. Example 4: Convert a given DATE value to the beginning of a 5-day time interval. ```Plaintext select dateslice(iddate, interval 5 day, FLOOR) from testalltype_select order by id_int; +--+ | dateslice(iddate, INTERVAL 5 day, floor) | +--+ | 2052-12-24 | | 2168-08-03 | | 1737-02-04 | | 2245-09-29 | | 1889-10-25 | +--+ 5 rows in set (0.14 sec) ``` Example 5: Convert a given DATE value to the end of a 5-day time interval. ```Plaintext select dateslice(iddate, interval 5 day, CEIL) from testalltype_select order by id_int; +-+ | dateslice(iddate, INTERVAL 5 day, ceil) | +-+ | 2052-12-29 | | 2168-08-08 | | 1737-02-09 | | 2245-10-04 | | 1889-10-30 | +-+ 5 rows in set (0.17 sec) ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.1.3.en.md

Fixed rule action metrics inconsistency where dropped requests were not accounted for. Update ekka to version 0.15.8, mria to version 0.5.10, and optvar to 1.0.5. This fixes occasional assertion failures: `{{badmatch,noproc},[{optvar,read,2,[{file,"optvar.erl"},{line,140}]},{optvar,read,1,[{file,"optvar.erl"},{line,124}]},...` Fix HTTP API error when a publish topic rewrite rule targets a topic with wildcards. Now it returns error 400 (Bad Match) instead of error 500 (Internal Error). Update ekka to version 0.15.9. This fixes dangling etcd locks occurred if acquiring the lock failed with a timeout. Fixed this crash issue when starting on Windows or any other platform without RocksDB support.
Project: KICS (Provisioning / Security & Compliance)
File: 9df7f78f-ebe3-432e-ac3b-b67189c15518.md

title: Cluster Master Authentication Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9df7f78f-ebe3-432e-ac3b-b67189c15518 Query name: Cluster Master Authentication Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Kubernetes Engine Clusters must have Master Authentication set to enabled, which means the attribute 'master_auth' must have the subattributes 'username' and 'password' defined and not empty<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="32 3 46 18 61" name: create a cluster1 google.cloud.gcpcontainercluster: name: my-cluster1 initialnodecount: 2 node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a cluster2 google.cloud.gcpcontainercluster: name: my-cluster2 initialnodecount: 2 master_auth: password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a cluster3 google.cloud.gcpcontainercluster: name: my-cluster3 initialnodecount: 2 master_auth: username: cluster_admin node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a cluster4 google.cloud.gcpcontainercluster: name: my-cluster4 initialnodecount: 2 master_auth: username: password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a cluster5 google.cloud.gcpcontainercluster: name: my-cluster5 initialnodecount: 2 master_auth: username: cluster_admin password: node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a cluster google.cloud.gcpcontainercluster: name: my-cluster initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present ```
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.23.0.md

Rebase fixes from v0.22.0 release branch by @tomqin93 in https://github.com/Edgenesis/shifu/pull/654 Bump k8s.io/client-go from 0.27.2 to 0.27.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/639 Bump github.com/minio/minio-go/v7 from 7.0.56 to 7.0.59 by @dependabot in https://github.com/Edgenesis/shifu/pull/647 Bump golang.org/x/net from 0.10.0 to 0.12.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/649 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.22.0...v0.23.0
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.25.0.md

title: v1.25.0 weight: 998975000 Makefile content is updated as shown below. ```sh `KUBEBUILDERASSETS="$(shell $(ENVTEST) use $(ENVTESTK8S_VERSION) --bin-dir $(LOCALBIN) -p path)" go test ./... -coverprofile cover.out`, ``` Add support for building binary in multiple platforms. Add the below content to the Makefile. ```sh PLATFORMS ?= linux/arm64,linux/amd64,linux/s390x,linux/ppc64le .PHONY: docker-buildx docker-buildx: test ## Build and push docker image for the manager for cross-platform support sed -e '1 s/\(^FROM\)/FROM --platform=\$$\{BUILDPLATFORM\}/; t' -e ' 1,// s//FROM --platform=\$$\{BUILDPLATFORM\}/' Dockerfile > Dockerfile.cross docker buildx create --name project-v3-builder docker buildx use project-v3-builder docker buildx build --push --platform=$(PLATFORMS) --tag ${IMG} -f Dockerfile.cross docker buildx rm project-v3-builder rm Dockerfile.cross ``` (go/v3) Bump dependencies in go.mod file ```go go 1.19 github.com/onsi/ginkgo/v2 v2.1.4 github.com/onsi/gomega v1.19.0 github.com/prometheus/client_golang v1.12.2 k8s.io/api v0.25.0 k8s.io/apimachinery v0.25.0 k8s.io/client-go v0.25.0 sigs.k8s.io/controller-runtime v0.13.0 ``` (go/v3) Update `controller-tools` from `0.9.2` to `0.10.0`. In the `Makefile` file, replace `CONTROLLERTOOLSVERSION ?= v0.9.2` with `CONTROLLERTOOLSVERSION ?= v0.10.0` See for more details. In the project `Makefile` below the `docker-push` target add the new `docker-buildx` target. ```sh PLATFORMS ?= linux/arm64,linux/amd64,linux/s390x,linux/ppc64le .PHONY: docker-buildx docker-buildx: test ## Build and push docker image for the manager for cross-platform support sed -e '1 s/\(^FROM\)/FROM --platform=\$$\{BUILDPLATFORM\}/; t' -e ' 1,// s//FROM --platform=\$$\{BUILDPLATFORM\}/' Dockerfile > Dockerfile.cross docker buildx create --name project-v3-builder docker buildx use project-v3-builder docker buildx build --push --platform=$(PLATFORMS) --tag ${IMG} -f Dockerfile.cross docker buildx rm project-v3-builder rm Dockerfile.cross ``` See for more details.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.27.md

RabbitMQ `3.9.27` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 24.2, and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . Starting with this release, RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Release notes can be found on GitHub at . Free disk space monitor robustness improvements. Backported by @drencrom (Canonical). GitHub issue: `raft.adaptivefailuredetector.pollinterval` exposes 's `pollinterval` setting to RabbitMQ users. Increasing it can reduce the probability of false positives in clusters where inter-node communication links are used at close to maximum capacity. The default is `5000` (5 seconds). GitHub issue: When both `diskfreelimit.relative` and `diskfreelimit.absolute`, or both `vmmemoryhighwatermark.relative` and `vmmemoryhighwatermark.absolute` are set, the absolute settings will now take precedence. Contributed by @SimonUnge (AWS). GitHub issue: Classic queues with enabled could run into an exception. GitHub issue: When a was cleared, nodes emitted an of the wrong type. GitHub issue: New key supported by `rabbitmqctl listqueues`: `effectivepolicy_definition` that returns merged definitions of regular and effective for the queue. GitHub issue: New HTTP API endpoint, `GET /api/config/effective`, returns effective node configuration. This is an HTTP API counterpart of `rabbitmq-diagnostics environment`. Contributed by @SimonUnge (AWS). GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.27.tar.xz` instead of the source tarball produced by GitHub.
Project: Shifu (Provisioning / Automation & Configuration)
File: design-rtsp-record-application.md

User can use this application to watch RTSP using ffmpeg or other third-party package to store the stream into PV in other host which supporting GPU that can accelerate video encoding. application running in the kubernetes allow user to connect RTSP server, and record the RTSP stream into file like mp4 / flv and so on, user can export file out of kubernetes. The application is a HTTP Server running in the kubernetes, which can store the RTSP stream into a file like mp4 / flv and so on, user can export file out of kubernetes with the instruction manual. application manage a map to record the info of each device which record and can save this map into a file in PV for Backups, When The Application is up, it will recover from backups first. user can register his device using `/register`, so that application need using a Kubernetes to get this namespace's secret. rbac.yaml ```yaml kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata: name: application namespace: shifu-app rules: apiGroups: [""] resources: ["secrets"] verbs: [ "get", "list", "watch", "update", "create","delete"] ``` We need to store the video in pieces, each clip is 1 hour by default, the user can set this option, user can customize the path where the files saved this application could using the third-party package like ffmpeg to implement it or using `exec.Command` ffmpeg command example: ```bash ffmpeg -i RTSP://[RTSPURL] -c copy -map 0 -segmenttime 300 -f segment video/output%03d.mp4 ``` Create PVC and PV need Separate with other deploy to avoid user delete pv by mistake. ```yaml apiVersion: v1 kind: PersistentVolume metadata: name: <devicename>-pv namespace: deviceshifu labels: pv: <devicename>-pv spec: capacity: storage: 10Gi volumeMode: Filesystem accessModes: ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: slow apiVersion: v1 kind: PersistentVolumeClaim metadata: name: <devicename>-pvc spec: resources: requests: storage: 10Gi volumeMode: Filesystem accessModes: ReadWriteOnce selector: matchLabels: pv: <devicename>-pv ``` recording server deployment.yaml ```yaml ... volumeMounts: name: storage-pv mountPath: /data ... volumns: name: storge-pv persistentVolumeClaim: claimName: pvc-name optional: true ``` `/register` regist the RTSP Stream which need to record ```json { "deviceName":"", "secretName":"", "serverAddress":"", "recoding":true, // default recoding when register } ``` `/unregister` unregister is remove the Target RTSP Server from application and stop to recording but the data exists will not delete. ```json { "deviceName":"", } ``` `/update` turn on or down the recording from the device(RTSP Server) ```json { "deviceName":"", "record":false, } ``` We can use Hikvision / Dahua Camera, create a deviceShifu-TCP and application to connect it and record the stream into file. Meanwhile we can create a mock-RTSP server or build a mock-RTSP device docker image to test.
Project: TiDB (App Definition and Development / Database)
File: 2018-10-22-the-column-pool.md

Author(s): Last updated: 2018-10-22 Discussion at: This proposal is aimed to enable a fine-grained buffer reuse strategy. With the help of the proposed column pool, we can: Reduce the total memory consumption during the execution phase. Support column-oriented expression evaluation and leverage the power of vectorized expression execution. At present, the buffer reuse is in the granularity of Chunk. The disadvantages of this Chunk-oriented reuse strategy are: This buffer reuse strategy isn't effective in some scenarios. Some memory hold by the operators which are inactive can also be reused to reduce total memory consumption when executing a query. In order to reuse a Chunk, we have to design the resource recycling strategy for every operator which uses multiple goroutines to exploit the thread-level parallelism. For example, hash join. It makes the code more complicated and harder to be maintained. The memory used in the current query can not be reused in the next query within the same session. Thus the golang GC pressure is increased and the OLTP performance on a TiDB server is impacted. The main idea of this proposal is to change the Chunk-oriented buffer reuse strategy to Column-oriented and use a session-level column pool to achieve that. Considering that the current TiDB only supports a limited number of types, we only need to consider 5 kinds of columns: 4 fixed length columns: 4/8/16/40 1 variable length column The column pool can be accessed by multiple goroutines concurrently, and to reduce the lock conflict, we can split the pool into shards and randomize the target shard in each Put/Get operation. Each shard of a column pool is implemented as a last in first out stack, which helps to release the unused column in the pool. And in most cases, the required length of a new column is equal to the previous column put into the column pool. No No Implement the column pool firstly. Remove the complicated, error-prone resource recycling strategy for each operator. Replace each NewChunkWithCapacity() with pool.GetChunk(). No
Project: external-secrets (Provisioning / Security & Compliance)
File: pulumi.md

Sync environments, configs and secrets from to Kubernetes using the External Secrets Operator. Pulumi are recommended to access Pulumi ESC. A Pulumi SecretStore can be created by specifying the `organization` and `environment` and referencing a Kubernetes secret containing the `accessToken`. ```yaml apiVersion: external-secrets.io/v1beta1 kind: SecretStore metadata: name: secret-store spec: provider: pulumi: organization: <NAMEOFTHE_ORGANIZATION> environment: <NAMEOFTHE_ENVIRONMENT> accessToken: secretRef: name: <NAMEOFKUBE_SECRET> key: <KEYINKUBE_SECRET> ``` If required, the API URL (`apiUrl`) can be customized as well. If not specified, the default value is `https://api.pulumi.com`. Secrets can be referenced by defining the `key` containing the JSON path to the secret. Pulumi ESC secrets are internally organized as a JSON object. ```yaml apiVersion: external-secrets.io/v1beta1 kind: ExternalSecret metadata: name: secret spec: refreshInterval: 5m secretStoreRef: kind: SecretStore name: secret-store data: secretKey: <KEYINKUBE_SECRET> remoteRef: key: <PULUMIPATHSYNTAX> ``` Note: `key` is not following the JSON Path syntax, but rather the Pulumi path syntax. root root.nested root["nested"] root.double.nest root["double"].nest root root.array[0] root.array[100] root.array[0].nested root.array.nested root.nested.array[0].double[1] root["key with \"escaped\" quotes"] root["key with a ."] ["root key with \"escaped\" quotes"].nested root.array[].field root.array[""].field See for more information.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.5.md

RabbitMQ `3.9.5` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.0.5 at the time of release. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Virtual host metadata (description, tags) was not imported from definitions. GitHub issue: Reduced unnecessary debug logging from streams. GitHub issue: AWS API calls are now retried multiple times. Contributed by AWS. GitHub issue: `PUT /api/vhosts/{name}` now can update metadata (tags and descriptions) for existing virtual hosts. GitHub issue: No dependency changes in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.5.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: integrations.md

You can integrate KICS with your favorite CI/CD pipelines. We provide plugins for some CI/CD tools. For some others we provide a tutorial on how the integration can be done. Integrate KICS with: More soon... The pipelines examples can be found in our KICS is natively embedded in , a 100% Open-Source tool for CI/CD workflows that analyzes consistency and quality of: 48 languages 22 formats 20 tooling formats excessive copy-pastes and spelling mistakes It also generates various reports, and can apply formatting and auto-fixes, to ensure all your projects sources are clean, whatever IDE/toolbox are used by their developers. To install MegaLinter in your repository, just run the following command `npx mega-linter-runner --install`
Project: ShardingSphere (App Definition and Development / Database)
File: show-compute-node-mode.en.md

+++ title = "SHOW COMPUTE NODE MODE" weight = 6 +++ The `SHOW COMPUTE NODE MODE` syntax is used to query current proxy instance mode configuration information. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowComputeNodeInfo ::= 'SHOW' 'COMPUTE' 'NODE' 'MODE' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Columns | Description | |--|| | type | type of proxy mode configuration | | repository | type of persist repository | | props | properties of persist repository | Query current proxy instance mode configuration information ```sql SHOW COMPUTE NODE MODE; ``` ```sql mysql> SHOW COMPUTE NODE MODE; ++++ | type | repository | props | ++++ | Cluster | ZooKeeper | {"operationTimeoutMilliseconds":500,"timeToLiveSeconds":60,"maxRetries":3,"namespace":"governance_ds","server-lists":"localhost:2181","retryIntervalMilliseconds":500} | ++++ 1 row in set (0.00 sec) ``` `SHOW`, `COMPUTE`, `NODE`, `MODE`