cwielenb/CNCF-Dataset huggingface dataset:
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_json_scan.md

Runs tests against any json compatible payloads/policies. Runs tests against any json compatible payloads/policies. NOTE: This is an experimental command, use `KYVERNO_EXPERIMENTAL=true` to enable it. ``` kyverno json scan [flags] ``` ``` -h, --help help for scan --labels strings Labels selectors for policies --output string Output format (text or json) (default "text") --payload string Path to payload (json or yaml file) --policy strings Path to kyverno-json policies --pre-process strings JMESPath expression used to pre process payload ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Runs tests against any json compatible payloads/policies.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: plantix.md

title: "Plantix" icon: /images/logos/powered-by/plantix.png hasLink: "https://plantix.net/en/" <!-- Licensed 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. -->
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_dataprotection_restore.md

title: kbcli dataprotection restore Restore a new cluster from backup ``` kbcli dataprotection restore [flags] ``` ``` kbcli dp restore mybackup --cluster cluster-name ``` ``` --cluster string The cluster to restore -h, --help help for restore --restore-to-time string point in time recovery(PITR) --volume-restore-policy string the volume claim restore policy, supported values: [Serial, Parallel] (default "Parallel") ``` ``` --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 --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 ``` - Data protection command.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-error-conditions-failed-read-file-error-class.md

layout: global title: FAILEDREADFILE error class displayTitle: FAILEDREADFILE 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`. --> SQLSTATE: KD001 Encountered error while reading file `<path>`. This error class has the following derived error classes: Could not read footer. Please ensure that the file is in either ORC or Parquet format. If not, please convert it to a valid format. If the file is in the valid format, please check if it is corrupt. If it is, you can choose to either ignore it or fix the corruption. File does not exist. It is possible the underlying files have been updated. You can explicitly invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in SQL or by recreating the Dataset/DataFrame involved. Data type mismatches when reading Parquet column `<column>`. Expected Spark type `<expectedType>`, actual Parquet type `<actualType>`.
Project: Dragonfly (Provisioning / Container Registry)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <dragonfly-maintainers@googlegroups.com>. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Druid (App Definition and Development / Database)
File: druid-powered.md

title: Powered by Apache Druid <!-- 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. --> Edit this page in the repo. To see your changes, navigate to them from the .
Project: VMClarity (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature Request about: Suggest a feature for this project title: '' labels: '' assignees: '' Please describe the problem to be addressed by the proposed feature. Please describe what you envision the solution to this problem would look like. Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and tradeoffs being made. Please provide any other information that may be relevant.
Project: FOSSA (Provisioning / Security & Compliance)
File: README.md

Out-of-band diagnostics for FOSSA CLI. Usually we try to ensure that diagnostics are captured in the FOSSA CLI debug bundle. However sometimes we need information that isn't reasonable to collect on every system (due to performance, privacy, or other reasons). Sometimes we also want to validate a diagnostic is useful before we include it in the debug bundle. These diagnostics are generally used when directed by FOSSA support; as such the typical way of getting help documentation is using the `--help` argument. Enables users to get detailed diagnosis of walking the local file system for a project. Intended to be used to help troubleshoot situations where FOSSA CLI is slow to walk over a file system by gathering detailed information about the entries that are walked. Information reported: The file paths walked. Whether they are on the same device as the root folder. Their type (symlink, file, folder). Whether they are read-only. Their depth in the directory structure (relative to the root folder). The deepest directory observed. The total count of each kind of entry walked. File paths may be filtered with regular expressions: see `diagnose walk --help` for details. Example: ``` diagnose walk --filter '\.git' --filter '\.md' ``` By default, `diagnose` reports rather verbose data. This is to minimize configuration required for users; they can just run it with the default arguments and send FOSSA the entire output for maximal diagnostics. However, this can be customized via the `--format`, `--trace-spans`, and `--trace-level` arguments. This subcommand allows visualization of those customizations.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.md

Thank you for your intention to contribute to the Apache Flink project. As an open-source community, we highly appreciate external contributions to our project. To make the process smooth for the project committers (those who review and accept changes) and contributors (those who propose new changes via pull requests), there are a few rules to follow. Please check out the to understand how contributions are made. A detailed explanation can be found in our which also contains a list of coding guidelines that you should follow. For pull requests, there is a with criteria taken from the How to Contribute Guide and the Coding Guidelines.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: ssh_key.md

+++ title = "ssh_key resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "ssh_key" identifier = "inspec/resources/os/sshkey.md sshkey resource" parent = "inspec/resources/os" +++ Use the `ssh_key` Chef InSpec audit resource to test ssh keys. Supported key types RSA, DSA(Limited support. Not verifies private key) , ECDSA, Ed25519 {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.18.0 of Chef InSpec. The `ssh_key` resource tests the properties of an SSH key file. Provide the path to a key file or a key filename. If you pass in a filename, this resource checks for keys on default path `~/.ssh/`. ```rb describe sshkey('~/.ssh/idrsa') do it { should be_private } it { should be_public } its('type') { should cmp /rsa/ } its('key_length') { should eq 2048 } its('mode') { should cmp '0400' } end ``` You can use an optional passphrase with `ssh_key`: ```rb describe sshkey('~/.ssh/idrsa', '<PASSPHRASE>') do it { should be_private } end ``` Replace `<PASSPHRASE>` with the private key passphrase. The `key_length` property tests the number of bits in the key pair. This only works with RSA keys. ```rb describe sshkey('~/.ssh/idrsa') do its('key_length') { should eq 4096 } end ``` The `type` property verifies the key type. ```rb describe sshkey('~/.ssh/idecdsa') do its('type') { should cmp /ecdsa/ } end ``` Allowed values: `rsa` `ecdsa` `ed25519` `dsa` The ssh_key resource also tests the same properties that the tests. For example, you can use the `mode` property to test if the mode assigned to the SSH key matches the specified value. ```rb describe sshkey('~/.ssh/idrsa') do its('mode') { should cmp '0400' } end ``` For a full list of available matchers, see the . Use `be_public` to verify that a key is public key: ```rb describe sshkey('~/.ssh/ided25519.pub') do it { should be_public } end ``` Use `be_private` to verify that a key is a private key: ```rb describe sshkey('~/.ssh/idecdsa', '<PASSPHRASE>') do it { should be_private } end ``` Replace `<PASSPHRASE>` with the private key passphrase.
Project: YugabyteDB (App Definition and Development / Database)
File: extension-postgres-fdw.md

title: postgres_fdw extension headerTitle: postgres_fdw extension linkTitle: postgres_fdw description: Using the postgres_fdw extension in YugabyteDB menu: v2.18: identifier: extension-postgres-fdw parent: pg-extensions weight: 20 type: docs The module provides the foreign-data wrapper postgres_fdw, which can be used to access data stored in external PostgreSQL servers. First, enable the extension: ```sql CREATE EXTENSION postgres_fdw; ``` To connect to a remote YSQL or PostgreSQL database, create a foreign server object. Specify the connection information (except the username and password) using the `OPTIONS` clause: ```sql CREATE SERVER myserver FOREIGN DATA WRAPPER postgresfdw OPTIONS (host 'hostip', dbname 'externaldb', port 'port_number'); ``` Specify the username and password using `CREATE USER MAPPING`: ```sql CREATE USER MAPPING FOR mylocaluser SERVER myserver OPTIONS (user 'remoteuser', password 'password'); ``` You can now create foreign tables using `CREATE FOREIGN TABLE` and `IMPORT FOREIGN SCHEMA`: ```sql CREATE FOREIGN TABLE tablename (colname1 int, colname2 int) SERVER myserver OPTIONS (schemaname 'schema', tablename 'table'); IMPORT FOREIGN SCHEMA foreignschemaname FROM SERVER myserver INTO localschema_name; ``` You can execute `SELECT` statements on the foreign tables to access the data in the corresponding remote tables.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_describe-config.md

title: kbcli cluster describe-config Show details of a specific reconfiguring. ``` kbcli cluster describe-config [flags] ``` ``` kbcli cluster describe-config mycluster kbcli cluster describe-config mycluster --component=mysql kbcli cluster describe-config mycluster --component=mysql --show-detail kbcli cluster describe-config mycluster --component=mysql --config-file=my.cnf --show-detail ``` ``` --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-file strings Specify the name of the configuration file to be describe (e.g. for mysql: --config-file=my.cnf). If unset, all files. --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 describe-config --show-detail If true, the content of the files specified by config-file will be printed. ``` ``` --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: YDB (App Definition and Development / Database)
File: compact.md

Improves aggregation efficiency if the query author knows in advance that none of aggregation keys finds large amounts of data (i.e., with the order of magnitude exceeding a gigabyte or a million of rows). If this assumption fails to materialize, then the operation may fail with Out of Memory error or start running much slower compared to the non-COMPACT version. Unlike the usual GROUP BY, the Map-side combiner stage and additional Reduce are disabled for each field with aggregation. Example: ```yql SELECT key, COUNT (DISTINCT value) AS count -- top 3 keys by the number of unique values FROM my_table GROUP COMPACT BY key ORDER BY count DESC LIMIT 3; ```
Project: TiDB (App Definition and Development / Database)
File: logredaction.md

Background: Issue: https://github.com/pingcap/tidb/issues/18566 Our database may store some sensitive information, such as customer ID number, credit card number, etc. This sensitive information sometimes exists in the error message in some manners like a form of key-value, and this information will be printed in the log along with the error. Some of our users do not want this sensitive information to spread along with logs. Therefore, our requirement is to provide a switch which can hide these possible sensitive information when printing the log. For example, ```sql mysql> create table t (a int, unique key (a)); Query OK, 0 rows affected (0.00 sec) mysql> insert into t values (1),(1); ERROR 1062 (23000): Duplicate entry '1' for key 'a' mysql> set @@session.tidbredactlog=1; Query OK, 0 rows affected (0.00 sec) mysql> insert into t values (1),(1); ERROR 1062 (23000): Duplicate entry '?' for key '?' ``` And its corresponding log is ``` [2020/10/20 11:45:37.796 +08:00] [INFO] [conn.go:800] ["command dispatched failed"] [conn=5] [connInfo="id:5, addr:127.0.0.1:57222 status:10, collation:utf8generalci, user:root"] [command=Query] [status="inTxn:0, autocommit:1"] [sql="insert into t values (1),(1)"] [txn_mode=OPTIMISTIC] [err="[kv:1062]Duplicate entry '1' for key 'a'"] [2020/10/20 11:45:49.539 +08:00] [INFO] [conn.go:800] ["command dispatched failed"] [conn=5] [connInfo="id:5, addr:127.0.0.1:57222 status:10, collation:utf8generalci, user:root"] [command=Query] [status="inTxn:0, autocommit:1"] [sql="insert into t values ( ? ) , ( ? )"] [txn_mode=OPTIMISTIC] [err="[kv:1062]Duplicate entry '?' for key '?'"] ``` As you can see, after enabling `tidbredactlog`, sensitive content is hidden both in the error message and in the log.
Project: ArangoDB (App Definition and Development / Database)
File: inequality_success_type.md

+++ title = "`bool operator==(const success_type<A> &) const`" description = "Returns true if this result compares equal to the success type sugar. Constexpr and noexcept propagating." categories = ["comparisons"] weight = 810 +++ Returns true if this result is successful and its value compares equal to the value in the success type sugar. Comparison is done using `operator==` on `valuetype` and `A`. If `A` is `void`, this call aliases {{% api "bool hasvalue() const noexcept" %}}. Requires: `operator==` must be a valid expression between `valuetype` and `A`, or `A` is `void`. If `valuetype` is `void`, then so must be `A`. Complexity: Whatever the underlying `operator==` has. Constexpr and noexcept of underlying operations is propagated. Guarantees: None.