cwielenb/CNCF-Dataset huggingface dataset:
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.34.0.md

Formatting code by @tomqin93 in https://github.com/Edgenesis/shifu/pull/777 Bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.9.0 to 1.9.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/784 Bump k8s.io/client-go from 0.28.4 to 0.29.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/786 Bump github.com/gopcua/opcua from 0.5.2 to 0.5.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/779 Bump github.com/DATA-DOG/go-sqlmock from 1.5.0 to 1.5.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/782 Bump golang.org/x/crypto from 0.16.0 to 0.17.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/788 Bump github.com/minio/minio-go/v7 from 7.0.65 to 7.0.66 by @dependabot in https://github.com/Edgenesis/shifu/pull/787 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.33.0...v0.34.0
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.5.0.md

Implement telemetryservice TDengine by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/350 <BugFix>add channel to avoid mock MQTT Server start brefore the other test pass by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/359 <enhance> rebase v0.4.0 release fixes back to main by @tomqin93 in https://github.com/Edgenesis/shifu/pull/360 <BugFix> rebase fixes made in v0.4.1 back to main by @tomqin93 in https://github.com/Edgenesis/shifu/pull/368 <BugFix>fix some bug on unit test by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/373 <bugFix>Fix telemetry service path by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/364 fix demo install script by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/376 <Enhance> use multistage to build socket mock device by @tomqin93 in https://github.com/Edgenesis/shifu/pull/370 modify all int to int64 by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/366 test: use `T.Setenv` to set env vars in tests by @Juneezee in https://github.com/Edgenesis/shifu/pull/375 feat: update ignore by @180909 in https://github.com/Edgenesis/shifu/pull/357 add Shifu config init by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/367 new readme by @rachelzhang0922 in https://github.com/Edgenesis/shifu/pull/352 Add contribution guide and corresponding shifuctl parts to it by @saiyan86 in https://github.com/Edgenesis/shifu/pull/288 update contribution guide by @saiyan86 in https://github.com/Edgenesis/shifu/pull/377 @Juneezee made their first contribution in https://github.com/Edgenesis/shifu/pull/375 @180909 made their first contribution in https://github.com/Edgenesis/shifu/pull/357 Bump github.com/eclipse/paho.mqtt.golang from 1.4.1 to 1.4.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/355 Bump github.com/taosdata/driver-go/v3 from 3.0.2 to 3.0.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/363 Bump github.com/spf13/cobra from 1.5.0 to 1.6.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/371 Bump github.com/onsi/gomega from 1.22.1 to 1.24.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/372 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.4.0...v0.5.0
Project: ArangoDB (App Definition and Development / Database)
File: copy_file2.md

+++ title = "Upgrading the Filesystem TS" description = "" weight = 20 tags = ["payload"] +++ An Outcome based solution to the dual overload problem is straightforward: {{% snippet "outcomepayload.cpp" "filesystemapi_fixed" %}} Starting at the bottom, there is now a single `copyfile()` function which returns a `fsresult<void>`. As `result` is either successful or not, there is no longer any point in returning a boolean, so we simply return `void` on success. On failure, as the template alias `fs_result<T>` above it shows, we are returning a `failure_info` structure containing an error code and the same additional information as `filesystem_error` provides. It is important to note that the fact that `failure_info` is defined in namespace `filesystem2` is very important. This is because Outcome uses to find the `makeerrorcode()` function, as well as other customisation point free functions. In other words, only the namespaces as defined by ADL are searched when finding a free function telling us what to do for `failure_info`, which includes the namespace `failure_info` is declared into.
Project: external-secrets (Provisioning / Security & Compliance)
File: decoding-strategy.md

The External Secrets Operator has the feature to allow multiple decoding strategies during an object generation. The `decodingStrategy` field allows the user to set the following Decoding Strategies based on their needs. `decodingStrategy` can be placed under `spec.data.remoteRef`, `spec.dataFrom.extract` or `spec.dataFrom.find`. It will configure the decoding strategy for that specific operation, leaving others with the default behavior if not set. ESO will not try to decode the secret value. ESO will try to decode the secret value using method. If the decoding fails, an error is produced. ESO will try to decode the secret value using method. If the decoding fails, an error is produced. ESO will try to decode using Base64/Base64URL strategies. If the decoding fails, ESO will apply decoding strategy None. No error is produced to the user. Given that we have the given secret information: ``` { "name": "Gustavo", "surname": "Fring", "address":"aGFwcHkgc3RyZWV0", } ``` if we apply the following dataFrom: ``` spec: dataFrom: extract: key: my-secret decodingStrategy: Auto ``` It will render the following Kubernetes Secret: ``` data: name: R3VzdGF2bw== #Gustavo surname: RnJpbmc= #Fring address: aGFwcHkgc3RyZWV0 #happy street ``` At this time, decoding Strategy Auto is only trying to check if the original input is valid to perform Base64 operations. This means that some non-encoded secret values might end up being decoded, producing gibberish. This is the case for numbered values like `123456` or some specially crafted string values such as `happy/street`. !!! note If you are using `decodeStrategy: Auto` and start to see ESO pulling completely wrong secret values into your kubernetes secret, consider changing it to `None` to investigate it.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_drop_elasticsearch.md

title: Kubectl-Dba Data Drop Elasticsearch menu: docs_{{ .version }}: identifier: kubectl-dba-data-drop-elasticsearch name: Kubectl-Dba Data Drop Elasticsearch parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Delete data from elasticsearch database Use this cmd to delete inserted data in a elasticsearch object ``` kubectl-dba data drop elasticsearch [flags] ``` ``` kubectl dba drop -n demo es es-quickstart ``` ``` -h, --help help for elasticsearch ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Drop data from a database
Project: StarRocks (App Definition and Development / Database)
File: debuginfo.md

displayed_sidebar: "English" From v2.5 onwards, the debuginfo file of BE is stripped from the StarRocks installation package to reduce the size and space usage of the installation package. You can see two packages at . In this figure, you can click `Get Debug Symbol files` to download the debuginfo package. `StarRocks-2.5.10.tar.gz` is the installation package and you can click Download to download this package. This change does not affect your download behavior or use of StarRocks. You can download only the installation package for cluster deployment and upgrade. The debuginfo package is only for developers to debug programs using GDB. GDB 12.1 or later is recommended for debugging. Download and decompress the debuginfo package. ```SQL wget https://releases.starrocks.io/starrocks/StarRocks-<sr_ver>.debuginfo.tar.gz tar -xzvf StarRocks-<sr_ver>.debuginfo.tar.gz ``` > NOTE > > Replace `<sr_ver>` with the version number of the StarRocks installation package you want to download. Load the debuginfo file when you perform GDB debugging. Method 1 ```Shell objcopy --add-gnu-debuglink=starrocksbe.debug starrocksbe ``` This operation associates the debug info file with your executable file. Method 2 ```Shell gdb -s starrocksbe.debug -e starrocksbe -c `core_file` ``` The debuginfo file works well with perf and pstack. You can directly use perf and pstack without additional operations.
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: LICENSE.md

Copyright (C) 2014 by Oleku Konko Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_promote.md

title: kbcli cluster promote Promote a non-primary or non-leader instance as the new primary or leader of the cluster ``` kbcli cluster promote NAME [--component=<comp-name>] [--instance <instance-name>] [flags] ``` ``` kbcli cluster promote mycluster --instance mycluster-mysql-1 kbcli cluster promote mycluster kbcli cluster promote mycluster --component=mysql --instance mycluster-mysql-1 ``` ``` --auto-approve Skip interactive approval before promote the instance --component string Specify the component name of the cluster, if the cluster has multiple components, you need to specify a component --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") -h, --help help for promote --instance string Specify the instance name as the new primary or leader of the cluster, you can get the instance name by running "kbcli cluster list-instances" --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed ``` ``` --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: Scylla (App Definition and Development / Database)
File: modules.md

ScyllaDB Module Index ===================== Following is a rough diagram how the various modules in ScyllaDB interact. ```mermaid classDiagram class storage_proxy class messaging_service class database class keyspace class table class cql class cdc class view class alternator class forward_service class storage_service class gossiper class db_config class db_commitlog storage_proxy ..> database : read/write storageproxy ..> messagingservice : rpc storage_proxy ..> cdc : update storage_proxy ..> gossiper: check node liveness storage_proxy ..> view : update cql ..> cdc : configure cql ..> view : configure alternator ..> cdc : configure cql ..> forward_service : data path for autopar aggregations forwardservice ..> storageproxy : read forwardservice ..> messagingservice : rpc cql ..> storage_proxy : data path alternator ..> storage_proxy : data path database --* db_commitlog : commit cql ..> cdc : configure alternator ..> cdc : configure database --o keyspace keyspace --o table ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_clusterversion_unset-default.md

title: kbcli clusterversion unset-default Unset the clusterversion if it's default. ``` kbcli clusterversion unset-default NAME [flags] ``` ``` kbcli clusterversion unset-default ac-mysql-8.0.30 ``` ``` -h, --help help for unset-default ``` ``` --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 ``` - ClusterVersion command.
Project: SPIRE (Provisioning / Key Management)
File: plugin_agent_nodeattestor_sshpop.md

Must be used in conjunction with the server-side sshpop plugin The `sshpop` plugin provides attestation data for a node that has been provisioned with an ssh identity through an out-of-band mechanism and responds to a signature based proof-of-possession challenge issued by the server plugin. The SPIFFE ID produced by the server-side `sshpop` plugin is based on the certificate fingerprint, which is an unpadded url-safe base64 encoded sha256 hash of the certificate in openssh format. ```xml spiffe://<trust_domain>/spire/agent/sshpop/<fingerprint> ``` | Configuration | Description | Default | ||--|-| | `hostkeypath` | The path to the private key on disk in openssh format. | `"/etc/ssh/sshhostrsa_key"` | | `hostcertpath` | The path to the certificate on disk in openssh format. | `"/etc/ssh/sshhostrsa_key-cert.pub"` | A sample configuration: ```hcl NodeAttestor "sshpop" { plugin_data { hostcertpath = "./conf/agent/dummyagentssh_key-cert.pub" hostkeypath = "./conf/agent/dummyagentssh_key" } } ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: DOWNLOADS.md

[The latest Podman release version is always available on the GitHub releases page](https://github.com/containers/podman/releases/latest). These are official, signed, sealed, and blessed artifacts intended for general use. Though for super-serious production use, please utilize the pre-packaged podman provided by your OS/Distro vendor. If you're looking for something even more bleeding-edge, esp. for testing purposes and/or in other CI systems. There are several permalinks available depending on how much you want to download. Everything inside has at least gone through and passed CI testing. However, they are all unsigned, and frequently changing. Perfectly fine for non-production testing but please don't take them beyond that. [Giant artifacts archive](https://api.cirrus-ci.com/v1/artifact/github/containers/podman/Artifacts/binary.zip) containing every binary produced in CI from the most recent successful run. Warning: This file is pretty large, expect a 700+MB download. However, it's guaranteed to contain everything, where as the items below can change or become unavailable due to somebody forgetting to update this doc. <!-- WARNING: The items linked below all come from scripts in the `artifacts_task` map of `.cirrus.yml`. When adding or updating any item below, please ensure it matches corresponding changes in the artifacts task. --> Raw dynamically linked ELF (x86_64) binaries for , , , and Built on the latest supported Fedora release. MacOS , , and installation packages. Again, these are not signed, so expect warnings if you try to install them. There's also binary release ZIP-files for and . Windows for x86_64 only. Other podman-remote release builds (includes configuration files & documentation): * * * *
Project: Microcks (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

This document contains a list of maintainers in this repo. If you're interested in contributing, and becoming a maintainer, see . | Maintainer | GitHub ID | Email | | | | -- | | Laurent Broudoux | | laurent@microcks.io | | Yacine Kheddache | | yacine@microcks.io | | Maintainer | GitHub ID | Email | | | | -- |
Project: Neo4j (App Definition and Development / Database)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: feature assignees: '' Please note that GitHub issues are only meant for bug reports/feature requests. If you have questions on how to use Neo4j, please ask on instead of creating an issue here. Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.