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

Falco rules repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path to packages provided can contain one or more packages. Each package version must be on a separate folder. You can have multiple rules files in a single package, or create a package for each rules file, it's completely up to you. In the same way, you can decide if you want to provide one or multiple versions of your rules packages. The structure of a repository with multiple packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml more file3-rules.yaml file1-rules.yaml file2-rules.yaml 2.0.0 artifacthub-pkg.yml file1-rules.yaml package2 1.0.0 artifacthub-pkg.yml file1-rules.yaml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml file1-rules.yaml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. Rules files must have the `-rules.yaml` suffix. If you want to exclude some paths in your package from the indexing, you can do it using the `ignore` field in your , which uses `.gitignore` syntax. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your rules files or even new rules packages to your git repository, they'll be automatically indexed and listed in Artifact Hub. Rules source GitHub URL: Repository URL used in Artifact Hub: `https://github.com/tegioz/cloud-native-security-hub/artifact-hub/falco` (please note how the tree/master part is not used)
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_stop.md

title: kbcli cluster stop Stop the cluster and release all the pods of the cluster. ``` kbcli cluster stop NAME [flags] ``` ``` kbcli cluster stop mycluster ``` ``` --auto-approve Skip interactive approval before stopping the cluster --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 stop --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: ClickHouse (App Definition and Development / Database)
File: uniqthetasketch.md

slug: /en/sql-reference/aggregate-functions/reference/uniqthetasketch sidebar_position: 195 title: uniqTheta Calculates the approximate number of different argument values, using the . ``` sql uniqTheta(x[, ...]) ``` Arguments The function takes a variable number of parameters. Parameters can be `Tuple`, `Array`, `Date`, `DateTime`, `String`, or numeric types. Returned value A -type number. Implementation details Function: Calculates a hash for all parameters in the aggregate, then uses it in calculations. Uses the algorithm to approximate the number of different argument values. 4096(2^12) 64-bit sketch are used. The size of the state is about 41 KB. The relative error is 3.125% (95% confidence), see the for detail. See Also
Project: Beam (App Definition and Development / Streaming & Messaging)
File: bigqueryio.md

layout: section title: "BigQuery patterns" section_menu: section-menu/documentation.html permalink: /documentation/patterns/bigqueryio/ <!-- 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. --> The samples on this page show you common patterns for use with BigQueryIO. {{< language-switcher java py >}} In production systems, it is useful to implement the deadletter pattern with BigQueryIO outputting any elements which had errors during processing by BigQueryIO into another PCollection for further processing. The samples below print the errors, but in a production system they can be sent to a deadletter table for later correction. {{< paragraph class="language-java" >}} When using `STREAMING_INSERTS` you can use the `WriteResult` object to access a `PCollection` with the `TableRows` that failed to be inserted into BigQuery. If you also set the `withExtendedErrorInfo` property , you will be able to access a `PCollection<BigQueryInsertError>` from the `WriteResult`. The `PCollection` will then include a reference to the table, the data row and the `InsertErrors`. Which errors are added to the deadletter queue is determined via the `InsertRetryPolicy`. {{< /paragraph >}} {{< paragraph class="language-py" >}} In the result tuple you can access `FailedRows` to access the failed inserts. {{< /paragraph >}} {{< highlight java >}} {{< code_sample "examples/java/src/main/java/org/apache/beam/examples/snippets/Snippets.java" BigQueryIODeadLetter >}} {{< /highlight >}} {{< highlight py >}} {{< codesample "sdks/python/apachebeam/examples/snippets/snippets.py" BigQueryIODeadLetter >}} {{< /highlight >}}
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.
Project: KICS (Provisioning / Security & Compliance)
File: 9850d621-7485-44f7-8bdd-b3cf426315cf.md

title: IAM Password Without Minimum Length hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9850d621-7485-44f7-8bdd-b3cf426315cf Query name: IAM Password Without Minimum Length Platform: Pulumi Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: IAM password should have the required minimum length<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="16 7" name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:iam:AccountPasswordPolicy properties: name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:iam:AccountPasswordPolicy properties: minimumPasswordLength: 10 ``` ```yaml title="Negative test num. 1 - yaml file" name: aws-eks runtime: yaml description: An EKS cluster resources: example: type: aws:iam:AccountPasswordPolicy properties: minimumPasswordLength: 14 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.92.md

layout: release date: 2023-06-13 tag: v0.6.92 [performance] Final changes for nighthawk @MUzairS15 (#7847) [Performance] fix nighthawk @MUzairS15 (#7846) [chore] Update API for auto archive meshery server @theBeginner86 (#7719) [chore] Error codes cleanup @nebula-aac (#7789) Add golden files back, because they are required by the other pakcages' test cases @Aisuko (#7834) [Performance] Fix issues with Performance profiles @Abhishek-kumar09 (#7830) [Catalog] Support Unpublish Catalog Content @theBeginner86 (#7753) [bug] Remove False check for ValidPatternfile @theBeginner86 (#7835) [chore] Update APIs @theBeginner86 (#7844) trigger workflow run on Pull request @Abhishek-kumar09 (#7841) change permission to test the action yaml @Abhishek-kumar09 (#7840) [Snapshot] test on pull_request target @Abhishek-kumar09 (#7839) [Snapshot Action] Update MeshMap Snapshot github action @Abhishek-kumar09 (#7833) Bump github.com/prometheus/common from 0.42.0 to 0.44.0 @dependabot (#7780) [playground] Adding workflow to Update K8s Cleanup Script @suhail34 (#7825) [Catalog] Support Unpublish Catalog Content @theBeginner86 (#7753) [chore] Update APIs @theBeginner86 (#7844) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aisuko, @MUzairS15, @Revolyssup, @dependabot, @leecalcote, @nebula-aac, @suhail34, @theBeginner86 and MUzairS15
Project: FOSSA (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: "[BUG]" labels: '' assignees: '' Important: Bug reports should be directed to `support@fossa.com` for faster response and prioritization. Bug reports may still be created here but they may not get immediate attention and may be closed in favor of internally tracked tickets. Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Run `fossa analyze ...` See error Expected behavior A clear and concise description of what you expected to happen. Debug bundle Please run `fossa` with the `--debug` flag and attach the resulting `fossa.debug.json.gz` file here. Additional context Add any other context you think is relevant about the problem here.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_kubectl.PodList.md

/ / PodList .PodList `PodList` apiVersion: `"v1"` KubeResource.apiVersion `Optional` content: `void` KubeResource.content packages/core/mdist/models/entity.d.ts:50 `Optional` contentType: `string` KubeResource.contentType packages/core/mdist/models/entity.d.ts:51 isKubeResource: `true` KubeResource.isKubeResource `Optional` isSimulacrum: `boolean` KubeResource.isSimulacrum items: <\>[] kind: `"PodList"` KubeResource.kind `Optional` kuiRawData: `string` KubeResource.kuiRawData `Optional` metadata: { `creationTimestamp?`: `string` ; `generation?`: `string` ; `labels?`: `Record`<`string`, `string`\> ; `name`: `string` ; `namespace?`: `string` } & `Partial`<`WithOwnerReferences`\> & `Partial`<`WithResourceVersion`\> & { `annotations?`: `object` ; `creationTimestamp?`: `string` ; `generateName?`: `string` ; `generation?`: `string` ; `labels?`: { [key: string]: `string`; } ; `name`: `string` ; `namespace?`: `string` ; `uid?`: `string` } KubeResource.metadata packages/core/mdist/models/entity.d.ts:23 `Optional` nameHash: `string` KubeResource.nameHash packages/core/mdist/models/entity.d.ts:42 `Optional` onclick: `Object` family of onclick handlers | Name | Type | | :-- | :- | | `kind?` | `string` | | `name?` | `string` | | `nameHash?` | `string` | | `namespace?` | `string` | KubeResource.onclick packages/core/mdist/models/entity.d.ts:44 originatingCommand: `EvaluatorArgs`<\> KubeResource.originatingCommand `Optional` presentation: `Presentation` KubeResource.presentation packages/core/mdist/models/entity.d.ts:53 `Optional` prettyName: `string` name hash, e.g. the hash part of auto-generated names, or an openwhisk activation id KubeResource.prettyName packages/core/mdist/models/entity.d.ts:41 `Optional` spec: `any` KubeResource.spec `Optional` status: KubeResource.status `Optional` toolbarText: `ToolbarText` KubeResource.toolbarText packages/core/mdist/models/entity.d.ts:52 `Optional` version: `string` optional designation of resource version KubeResource.version packages/core/mdist/models/entity.d.ts:39
Project: Chef InSpec (Provisioning / Security & Compliance)
File: cpan.md

+++ title = "cpan resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "cpan" identifier = "inspec/resources/os/cpan.md cpan resource" parent = "inspec/resources/os" +++ Use the `cpan` Chef InSpec audit resource to test Perl modules that are installed by system packages or the CPAN installer. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.43.5 of InSpec. A `cpan` resource block declares a package and (optionally) a package version: describe cpan('package_name') do it { should be_installed } end where `'package_name'` is the name of the package, such as `'DBD::Pg'` `be_installed` tests to see if the package described above is installed This resource uses package names and perl library paths as resource parameters. describe cpan('DBD:Pg') do it { should be_installed } end describe cpan('DBD::Pg') do it { should be_installed } its('version') { should eq '3.7.0' } end Hint: You can pass multiple paths separated with a colon `/path/to/perl5/lib:/usr/share/perl5/vendor_perl/lib/perl5` describe cpan('DBD::Pg', '/home/username/perl5/lib/perl5') do it { should be_installed } end The following examples show how to use this Chef InSpec audit resource. The `version` property tests if the named package version is on the system: its('version') { should eq '1.2.3' } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `be_installed` matcher tests if the named package is installed on the system: it { should be_installed }
Project: Doris (App Definition and Development / Database)
File: quote.md

{ "title": "QUOTE", "language": "zh-CN" } <!-- 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. --> `VARCHAR quote(VARCHAR str)` ,'' ``` mysql> select quote('hello world!\\t'); +-+ | quote('hello world!\t') | +-+ | 'hello world!\t' | +-+ ``` QUOTE
Project: ClickHouse (App Definition and Development / Database)
File: v21.6.6.51-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : `CAST` from `Date` to `DateTime` (or `DateTime64`) was not using the timezone of the `DateTime` type. It can also affect the comparison between `Date` and `DateTime`. Inference of the common type for `Date` and `DateTime` also was not using the corresponding timezone. It affected the results of function `if` and array construction. Closes . (). Backported in : Fixed bug in deserialization of random generator state with might cause some data types such as `AggregateFunction(groupArraySample(N), T))` to behave in a non-deterministic way. (). Backported in : Fixed possible error 'Cannot read from istream at offset 0' when reading a file from DiskS3. (). Backported in : Fix potential crash when calculating aggregate function states by aggregation of aggregate function states of other aggregate functions (not a practical use case). See . (). Backported in : Fix segfault when sharding_key is absent in task config for copier. (). Backported in : Fix assertion in PREWHERE with non-uint8 type, close . (). Backported in : Fix wrong totals for query `WITH TOTALS` and `WITH FILL`. Fixes . (). Backported in : Fix null pointer dereference in `EXPLAIN AST` without query. (). Backported in : `REPLACE PARTITION` might be ignored in rare cases if the source partition was empty. It's fixed. Fixes . (). Backported in : Fixed `No such file or directory` error on moving `Distributed` table between databases. Fixes . (). Backported in : Fix data race when querying `system.clusters` while reloading the cluster configuration at the same time. (). NO CL ENTRY: 'Partial backport to 21.6'. (). ExpressionCache destruction fix ().
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_onprem_list.md

List On-premises YugabyteDB Anywhere providers List On-premises YugabyteDB Anywhere providers ``` yba provider onprem list [flags] ``` ``` -h, --help help for list ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, instance-types and nodes. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere on-premises provider
Project: ArangoDB (App Definition and Development / Database)
File: has_error.md

+++ title = "`bool has_error() const noexcept`" description = "Returns true if an error is present. Constexpr, never throws." categories = ["observers"] weight = 592 +++ Returns true if an error is present. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.12.2.md

This patch release contains bug fixes: The mTLS configuration was always enabled for Dapr sidecards in Kubernetes, regardless of the `daprsystem` configuration. Users on Dapr 1.12.1 could not disable mTLS for Dapr sidecars in Kubernetes. The `daprsystem` configuration was not being read correctly by the sidecar injector. The `daprsystem` configuration is now read correctly by the sidecar injector and the mTLS option is correctly set for Dapr sidecars in Kubernetes.
Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: "[Bug] " labels: kind/bug assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Kubernetes/Openshift Cluster Version Desktop (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 22] Additional context Add any other context about the problem here.