cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: show-sharding-key-generator.en.md

+++ title = "SHOW SHARDING KEY GENERATORS" weight = 5 +++ `SHOW SHARDING KEY GENERATORS` syntax is used to query sharding key generators in specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowShardingKeyGenerators::= 'SHOW' 'SHARDING' 'KEY' 'GENERATORS' ('FROM' databaseName)? 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. | column | Description | |--|--| | name | Sharding key generator name | | type | Sharding key generator type | | props | Sharding key generator properties | Query the sharding key generators of the specified logical database ```sql SHOW SHARDING KEY GENERATORS FROM sharding_db; ``` ```sql mysql> SHOW SHARDING KEY GENERATORS FROM sharding_db; +-+--+-+ | name | type | props | +-+--+-+ | snowflakekeygenerator | snowflake | | +-+--+-+ 1 row in set (0.00 sec) ``` Query the sharding key generators of the current logical database ```sql SHOW SHARDING KEY GENERATORS; ``` ```sql mysql> SHOW SHARDING KEY GENERATORS; +-+--+-+ | name | type | props | +-+--+-+ | snowflakekeygenerator | snowflake | | +-+--+-+ 1 row in set (0.00 sec) ``` `SHOW`, `SHARDING`, `KEY`, `GENERATORS`, `FROM`
Project: Notary (Provisioning / Security & Compliance)
File: list.md

Use `notation list` to list all the signatures associated with a signed OCI artifact. `Tags` are mutable, but `Digests` uniquely and immutably identify an artifact. If a tag is used to identify a signed artifact, notation resolves the tag to the `digest` first. Upon successful execution, both the digest of the signed artifact and the digests of signatures manifest associated with signed artifact are printed out as following: ```shell <registry>/<repository>@<digest> application/vnd.cncf.notary.signature <digestofsignature_manifest> <digestofsignature_manifest> ``` ```text List all the signatures associated with a signed OCI artifact Usage: notation list [flags] <reference> Aliases: list, ls Flags: -d, --debug debug mode -h, --help help for list --insecure-registry use HTTP protocol while connecting to registries. Should be used only for testing --max-signatures int maximum number of signatures to evaluate or examine (default 100) --oci-layout [Experimental] list signatures stored in OCI image layout -p, --password string password for registry operations (default to $NOTATION_PASSWORD if not specified) -u, --username string username for registry operations (default to $NOTATION_USERNAME if not specified) -v, --verbose verbose mode ``` ```shell notation list <registry>/<repository>:<tag> ``` An example output: ```shell localhost:5000/net-monitor@sha256:8456f085dd609fd12cdebc5f80b6f33f25f670a7a9a03c8fa750b8aee0c4d657 application/vnd.cncf.notary.signature sha256:647039638efb22a021f59675c9449dd09956c981a44b82c1ff074513c2c9f273 sha256:6bfb3c4fd485d6810f9656ddd4fb603f0c414c5f0b175ef90eeb4090ebd9bfa1 ``` The following example lists the signatures associated with the image in OCI layout directory named `hello-world`. To access this flag `--oci-layout` , set the environment variable `NOTATION_EXPERIMENTAL=1`. Reference an image in OCI layout directory using tags: ```shell export NOTATION_EXPERIMENTAL=1 notation list --oci-layout hello-world:v1 ``` Reference an image in OCI layout directory using exact digest: ```shell export NOTATION_EXPERIMENTAL=1 notation list --oci-layout hello-world@sha256:xxx ``` An example output: ```shell hello-world@sha256:a08753c0c7bcdaaf5c2fdb375f68e860c34bffb146368982c201d41769e1763c application/vnd.cncf.notary.signature sha256:647039638efb22a021f59675c9449dd09956c981a44b82c1ff074513c2c9f273 sha256:6bfb3c4fd485d6810f9656ddd4fb603f0c414c5f0b175ef90eeb4090ebd9bfa1 ```
Project: ORY Hydra (Provisioning / Key Management)
File: TokenPaginationHeaders.md

Name | Type | Description | Notes | - | - | - Link | Pointer to string | The link header contains pagination links. For details on pagination please head over to the . in: header | [optional] XTotalCount | Pointer to string | The total number of clients. in: header | [optional] `func NewTokenPaginationHeaders() *TokenPaginationHeaders` NewTokenPaginationHeaders instantiates a new TokenPaginationHeaders object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewTokenPaginationHeadersWithDefaults() *TokenPaginationHeaders` NewTokenPaginationHeadersWithDefaults instantiates a new TokenPaginationHeaders object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *TokenPaginationHeaders) GetLink() string` GetLink returns the Link field if non-nil, zero value otherwise. `func (o TokenPaginationHeaders) GetLinkOk() (string, bool)` GetLinkOk returns a tuple with the Link field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPaginationHeaders) SetLink(v string)` SetLink sets Link field to given value. `func (o *TokenPaginationHeaders) HasLink() bool` HasLink returns a boolean if a field has been set. `func (o *TokenPaginationHeaders) GetXTotalCount() string` GetXTotalCount returns the XTotalCount field if non-nil, zero value otherwise. `func (o TokenPaginationHeaders) GetXTotalCountOk() (string, bool)` GetXTotalCountOk returns a tuple with the XTotalCount field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPaginationHeaders) SetXTotalCount(v string)` SetXTotalCount sets XTotalCount field to given value. `func (o *TokenPaginationHeaders) HasXTotalCount() bool` HasXTotalCount returns a boolean if a field has been set.
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.3.44-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Added settings `inputformatipv4defaultonconversionerror`, `inputformatipv6defaultonconversionerror` to allow insert of invalid ip address values as default into tables. Closes . (). Backported in : Fix possible deadlock in cache. (). Backported in : Fix cast into IPv4, IPv6 address in IN section. Fixes . (). Backported in : Fix bug in conversion from custom types to string that could lead to segfault or unexpected error messages. Closes . (). Backported in : Fixes parsing of the arguments of the functions `extract`. Fixes . (). Backported in : Respect only quota & period from groups, ignore shares (which are not really limit the number of the cores which can be used). (). Backported in : Avoid processing per-column TTL multiple times. (). Slightly better performance of inserts to `Object` type (). Fix race in data type `Object` (). Fix crash with enabled `optimizefunctionsto_subcolumns` (). Fix enable LLVM for JIT compilation in CMake (). Backport release to 22.3 ().
Project: KICS (Provisioning / Security & Compliance)
File: e28ceb92-d588-4166-aac5-766c8f5b7472.md

title: AWS Password Policy With Unchangeable Passwords hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e28ceb92-d588-4166-aac5-766c8f5b7472 Query name: AWS Password Policy With Unchangeable Passwords Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Unchangeable passwords in AWS password policy<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9 21" name: Password policy for AWS account community.aws.iampasswordpolicy: state: present minpwlength: 8 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: false pwmaxage: 60 pwreuseprevent: 5 pw_expire: false name: Alias Password policy for AWS account community.aws.iampasswordpolicy: state: present minpwlength: 8 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpasswordchange: false pwmaxage: 60 pwreuseprevent: 5 pw_expire: false ``` ```yaml title="Negative test num. 1 - yaml file" name: Password policy for AWS account community.aws.iampasswordpolicy: state: present minpwlength: 8 require_symbols: false require_numbers: true require_uppercase: true require_lowercase: true allowpwchange: true pwmaxage: 60 pwreuseprevent: 5 pw_expire: false ```
Project: YugabyteDB (App Definition and Development / Database)
File: managed-labs.md

title: Product labs linkTitle: Product labs description: Discover how YugabyteDB solves latency and performance issues. headcontent: Test YugabyteDB Managed features using a demo application in real time menu: preview_yugabyte-cloud: identifier: managed-labs parent: yugabytedb-managed weight: 15 type: docs Use Product Labs to explore core features of YugabyteDB using a demo application connected to globally distributed test clusters in real time. Labs run a live demo application, accessing real clusters deployed in a variety of geographies and topologies. To run a lab: . . On the Labs page, choose a scenario and click Try It Out Now to launch the lab in a new tab. Follow the on-screen instructions. The following lab is available (with more in development). Learn how you can minimize application latencies for users in widely dispersed geographies using and deployments. {{< youtube id="jqZxUydBaMQ" title="Global Applications with YugabyteDB Managed" >}} Labs are time-limited to three hours. You can only run one instance of a lab in your account at a time. If another team member is running the lab, try again later.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_register.md

title: kbcli cluster register Pull the cluster chart to the local cache and register the type to 'create' sub-command ``` kbcli cluster register [NAME] --source [CHART-URL] [flags] ``` ``` kbcli cluster register orioledb --source https://github.com/apecloud/helm-charts/releases/download/orioledb-cluster-0.6.0-beta.44/orioledb-cluster-0.6.0-beta.44.tgz kbcli cluster register neon -source pkg/cli/cluster/charts/neon-cluster.tgz ``` ``` --alias string Set the cluster type alias --auto-approve Skip interactive approval when registering an existed cluster type -h, --help help for register -S, --source string Specify the cluster type chart source, support a URL or a local file path ``` ``` --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: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2023-02-34-10_fd072f64.md

timestamp: "2023-10-12 02:33:41 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.25.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Daemon-Fault-Tolerance.md

title: Daemon Fault Tolerance layout: documentation documentation: true Storm has several different daemon processes. Nimbus that schedules workers, supervisors that launch and kill workers, the log viewer that gives access to logs, and the UI that shows the status of a cluster. When a worker dies, the supervisor will restart it. If it continuously fails on startup and is unable to heartbeat to Nimbus, Nimbus will reschedule the worker. The tasks assigned to that machine will time-out and Nimbus will reassign those tasks to other machines. The Nimbus and Supervisor daemons are designed to be fail-fast (process self-destructs whenever any unexpected situation is encountered) and stateless (all state is kept in Zookeeper or on disk). As described in , the Nimbus and Supervisor daemons must be run under supervision using a tool like daemontools or monit. So if the Nimbus or Supervisor daemons die, they restart like nothing happened. Most notably, no worker processes are affected by the death of Nimbus or the Supervisors. This is in contrast to Hadoop, where if the JobTracker dies, all the running jobs are lost. If you lose the Nimbus node, the workers will still continue to function. Additionally, supervisors will continue to restart workers if they die. However, without Nimbus, workers won't be reassigned to other machines when necessary (like if you lose a worker machine). Storm Nimbus is highly available since 1.0.0. More information please refer to document. Storm provides mechanisms to guarantee data processing even if nodes die or messages are lost. See for the details.
Project: Hazelcast IMDG (App Definition and Development / Database)
File: icmp_helper.md

`PATHTOJDKINCLUDEDIR`: The full path for the include directory under your JDK installation. ``` gcc -c -I ${PATHTOJDKINCLUDEDIR} -fPIC -o icmphelper.o icmphelper.c gcc -shared -fPIC -Wl,-soname,libicmphelper.so -o libicmphelper.so icmp_helper.o -lc ```
Project: Seata (App Definition and Development / Database)
File: 1.8.0.md

| <details> <summary><mark>Release notes</mark></summary> Seata 1.8.0 Released. Seata is an easy-to-use, high-performance, open source distributed transaction solution. The version is updated as follows: ] support Dameng database ] support PolarDB-X 2.0 database ] bugfix: fix TC retry rollback wrongly, after the XA transaction fail and rollback ] fix dm escaped characters for upper and lower case column names ] fix the issue of missing sentinel password in store redis mode ] fix some configurations that are not deprecated show "Deprecated" ] some minor syntax optimization ] remove dependency without license ] remove 7z format compression support ] remove mariadb.jdbc dependency ] fix codecov chart not display ] optimize some scripts related to Apollo ] standardized the properties of codecov.yml ] support jmx port in seata ] fix npm package vulnerabilities ] fix npm package vulnerabilities ] remove sofa test cases ] upgrade druid and add `test-druid.yml` ] fix unit test in java 21 ] upgrade native-lib-loader version ] fix zookeeper UT failed ] fixed jedis version for `seata-server` Thanks to these contributors for their code commits. Please report an unintended omission. <!-- Please make sure your Github ID is in the list below --> Also, we receive many valuable issues, questions and advices from our community. Thanks for you all.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: gcp-forseti.md

title: GCP audit with Forseti labels: category: publiccloud inventors: google code: https://forsetisecurity.org videos: title: Repeatable GCP Environments at Scale with Cloud Build Infra-as-Code Pipelines speakers: name: Morgante Pell organization: google name: Andrew Phillips organization: google venue: Cloud Next 2019 link: https://www.youtube.com/watch?v=3vfXQxWJazM&feature=youtu.be&t=2054 Google cloud provides a plethora of software as a service. Forseti, built using OPA, lets you run policy checks against the software resources on Google cloud and remediate violations.
Project: ClickHouse (App Definition and Development / Database)
File: any.md

slug: /en/sql-reference/aggregate-functions/reference/any sidebar_position: 6 Selects the first encountered value of a column. Syntax ```sql any(column) ``` Aliases: `any_value`, . Parameters `column`: The column name. Returned value By default, it ignores NULL values and returns the first NOT NULL value found in the column. Like it supports `RESPECT NULLS`, in which case it will select the first value passed, independently on whether it's NULL or not. :::note The return type of the function is the same as the input, except for LowCardinality which is discarded. This means that given no rows as input it will return the default value of that type (0 for integers, or Null for a Nullable() column). You might use the `-OrNull` ) to modify this behaviour. ::: :::warning The query can be executed in any order and even in a different order each time, so the result of this function is indeterminate. To get a determinate result, you can use the or function instead of `any`. ::: Implementation details In some cases, you can rely on the order of execution. This applies to cases when `SELECT` comes from a subquery that uses `ORDER BY`. When a `SELECT` query has the `GROUP BY` clause or at least one aggregate function, ClickHouse (in contrast to MySQL) requires that all expressions in the `SELECT`, `HAVING`, and `ORDER BY` clauses be calculated from keys or from aggregate functions. In other words, each column selected from the table must be used either in keys or inside aggregate functions. To get behavior like in MySQL, you can put the other columns in the `any` aggregate function. Example Query: ```sql CREATE TABLE any_nulls (city Nullable(String)) ENGINE=Log; INSERT INTO any_nulls (city) VALUES (NULL), ('Amsterdam'), ('New York'), ('Tokyo'), ('Valencia'), (NULL); SELECT any(city) FROM any_nulls; ``` ```response any(city) Amsterdam ```
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: release-branch-backporting.md

Bug fixes are eligible to be backported from the main branch to any previous release branch. The following criteria must be met before a backport can be considered. It is the reviewer's and approver's responsibility to uphold this policy. Bug Fix Only: The backport must be a and the bug fix must be first merged into the main branch. The only exception is when a bug only exists in a stable branch and does not exist in the main branch. Release Note The PR description's release-note section must indicate in a brief one line statement what the backport addresses. This note gets automatically put into our release notes when a new release is cut from the stable branch. Detailed Description The backport pull request's description must either contain a detailed explanation for what the bug fix addresses or contain a link to such a explanation present in another PR/Issue. CI Lanes Must Pass The release branch being backported to must still be able to execute the unit and functional test lanes in order to validate the bug fix on that branch. This only impacts very old branches that are no longer compatible with our CI system. For the purposes of determining what is eligible for a backport we define a bug fix as any set of patches that loosely fall into one of the following categories. Addresses a logical defect in KubeVirt Fixes or improves the stability of our test suite Any infrastructure change related testing or releasing Logging and debug changes aimed at improving supportability of a stable release. There is purposefully some ambiguity here. These are meant to be read as guidelines to help reviewers make judgment calls. The intent here is to keep our release branches as stable as possible and only backport PRs that meet that goal. It's possible the eligibility of a backport will not be clear cut, and require some debate. Take for instance a PR that introduces new functionality to address a defect. Would this be considered a bug fix? Maybe, maybe not. The reviewers will have to weigh whether backporting will improve overall stability or introduce unacceptable risk.
Project: YugabyteDB (App Definition and Development / Database)
File: incrby.md

title: INCRBY linkTitle: INCRBY description: INCRBY menu: preview: parent: api-yedis weight: 2215 aliases: /preview/api/redis/incrby /preview/api/yedis/incrby type: docs `INCRBY key delta` This command adds `delta` to the number that is associated with the given `key`. The numeric value must a 64-bit signed integer. If the `key` does not exist, the associated string is set to "0" before performing the operation. If the given `key` is associated with a non-string value, or if its associated string cannot be converted to an integer, an error is raised. Returns the value after addition. ```sh $ SET yugakey 7 ``` ``` "OK" ``` ```sh $ INCRBY yugakey 3 ``` ``` 10 ``` , , , , , ,