cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: fitbit.md

title: "Fitbit" icon: /images/logos/powered-by/fitbit.png hasLink: "https://www.fitbit.com/" <!-- 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: StarRocks (App Definition and Development / Database)
File: hours_sub.md

displayed_sidebar: "English" Reduces the specified date and time by a specified number of hours. ```Haskell DATETIME hours_sub(DATETIME|DATE date, INT hours); ``` `date`: It must be a valid DATE or DATETIME expression. `hours`: The number of hours reduced. The supported data type is INT. Returns a DATETIME value. If the date does not exist, for example, `2022-21-01`, or if the date is not a DATE or DATETIME value, NULL is returned. ```Plain Text select hours_sub('2022-01-01 01:01:01', 1); +-+ | hours_sub('2022-01-01 01:01:01', 1) | +-+ | 2022-01-01 00:01:01 | +-+ select hours_sub('2022-01-01 01:01:01', -1); +--+ | hours_sub('2022-01-01 01:01:01', -1) | +--+ | 2022-01-01 02:01:01 | +--+ select hours_sub('2022-01-01', 1); +-+ | hours_sub('2022-01-01', 1) | +-+ | 2021-12-31 23:00:00 | +-+ select hours_sub('2022-01-01', -1); +--+ | hours_sub('2022-01-01', -1) | +--+ | 2022-01-01 01:00:00 | +--+ Error case: select hours_sub('2022-21-01', -1); +--+ | hours_sub('2022-21-01', -1) | +--+ | NULL | +--+ ```
Project: BOSH (Provisioning / Automation & Configuration)
File: feature_request.md

name: Feature request about: Suggest an idea for this project 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.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 1.8.md

We can't wait for you to try our newest features! Compare Anything is a feature that's true to its name: Compare clusters in two separate regions to see how they differ. Compare a Helm charts standalone and high-availability setup. Compare production and development Helm charts or Kustomizations. Compare a Helm and Kustomize Preview to troubleshoot a migration. Use the new Images tab from the left menu to view all images used across your resources Additionally, you can view information about each image and easily replace the tag across all your resources. When working with Helm templates, you can now hover over the values references to quickly preview them. For more info about these new features and additional UX updates
Project: ClickHouse (App Definition and Development / Database)
File: order-by.md

slug: /en/sql-reference/statements/alter/order-by sidebar_position: 41 sidebar_label: ORDER BY ``` sql ALTER TABLE [db].name [ON CLUSTER cluster] MODIFY ORDER BY new_expression ``` The command changes the of the table to `new_expression` (an expression or a tuple of expressions). Primary key remains the same. The command is lightweight in a sense that it only changes metadata. To keep the property that data part rows are ordered by the sorting key expression you cannot add expressions containing existing columns to the sorting key (only columns added by the `ADD COLUMN` command in the same `ALTER` query, without default column value). :::note It only works for tables in the family (including tables). :::
Project: Dragonfly (Provisioning / Container Registry)
File: README.md

Build tool: ```shell go build -o bin/stress test/stress/main.go ``` Run stress: ```shell bin/stress -connections 100 -duration 1s -proxy http://127.0.0.1:65001 \ --url http://localhost/misc/d7y-test/blobs/sha256/128K ``` Example output: ```text Latency avg 17.286522ms min 617.801s max 84.201941ms Latency Distribution 50% 11.39049ms 75% 18.308966ms 90% 49.052485ms 95% 55.886513ms 99% 65.013042ms HTTP codes 200 5849 Throughput 731.1MB Request 5849/s ``` ```text Usage of ./stress: -connections int concurrency count of connections (default 100) -duration duration testing duration (default 1m40s) -output string all request statistics (default "/tmp/statistics.txt") -proxy string target proxy for downloading, example: http://127.0.0.1:65001 -url string target url for stress testing, example: http://localhost ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: reporting-issues.md

title: Reporting Issues linkTitle: Reporting Issues weight: 5 If any part of the operator-sdk project has bugs or documentation mistakes, please let us know by . We treat bugs and mistakes very seriously and believe no issue is too small. Before creating a bug report, please check that an issue reporting the same problem does not already exist. To make the bug report accurate and easy to understand, please try to create bug reports that are: Specific. Include as much details as possible: which version, what environment, what configuration, etc. Reproducible. Include the steps to reproduce the problem. We understand some issues might be hard to reproduce, please include the steps that might lead to the problem. Isolated. Please try to isolate and reproduce the bug with minimum dependencies. It would significantly slow down the speed to fix a bug if too many dependencies are involved in a bug report. Debugging external systems that rely on operator-sdk is out of scope, but we are happy to provide guidance in the right direction or help with using operator-sdk itself. Unique. Do not duplicate existing bug report. Scoped. One bug per report. Do not follow up with another bug inside one report. It may be worthwhile to read before creating a bug report. We might ask for further information to locate a bug. A duplicated bug report will be closed.
Project: KICS (Provisioning / Security & Compliance)
File: bbe3dd3d-fea9-4b68-a785-cfabe2bbbc54.md

title: Policy Without Principal hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bbe3dd3d-fea9-4b68-a785-cfabe2bbbc54 Query name: Policy Without Principal Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: All policies, except IAM identity-based policies, should have the 'Principal' element defined<br> ```tf title="Positive test num. 1 - tf file" hl_lines="9" provider "aws" { region = "us-east-1" } resource "awskmskey" "secure_policy" { description = "KMS key + secure_policy" deletionwindowin_days = 7 policy = <<EOF { "Version": "2008-10-17", "Statement": [ { "Sid": "Secure Policy", "Effect": "Allow", "Resource": "*", "Action": [ "kms:Create*", "kms:Describe*", "kms:Enable*", "kms:List*", "kms:Put*", "kms:Update*", "kms:Revoke*", "kms:Disable*", "kms:Get*", "kms:Delete*", "kms:TagResource", "kms:UntagResource", "kms:ScheduleKeyDeletion", "kms:CancelKeyDeletion" ] } ] } EOF } ``` ```tf title="Negative test num. 1 - tf file" provider "aws" { region = "us-east-1" } resource "awskmskey" "secure_policy" { description = "KMS key + secure_policy" deletionwindowin_days = 7 policy = <<EOF { "Version": "2008-10-17", "Statement": [ { "Sid": "Secure Policy", "Effect": "Allow", "Resource": "*", "Action": [ "kms:Create*", "kms:Describe*", "kms:Enable*", "kms:List*", "kms:Put*", "kms:Update*", "kms:Revoke*", "kms:Disable*", "kms:Get*", "kms:Delete*", "kms:TagResource", "kms:UntagResource", "kms:ScheduleKeyDeletion", "kms:CancelKeyDeletion" ], "Principal": "AWS": [ "arn:aws:iam::AWS-account-ID:user/user-name-1", "arn:aws:iam::AWS-account-ID:user/UserName2" ] } ] } EOF } ``` ```tf title="Negative test num. 2 - tf file" resource "awsiamuser" "user" { name = "test-user" } resource "awsiamrole" "role" { name = "test-role" assumerolepolicy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Principal": { "Service": "ec2.amazonaws.com" }, "Effect": "Allow", "Sid": "" } ] } EOF } resource "awsiamgroup" "group" { name = "test-group" } resource "awsiampolicy" "policy" { name = "test-policy" description = "A test policy" policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Action": [ "ec2:Describe*" ], "Effect": "Allow", "Resource": "*" } ] } EOF } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.user.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] policyarn = awsiam_policy.policy.arn } ``` ```tf title="Negative test num. 3 - tf file" data "awsiampolicy_document" "glue-example-policyX" { statement { actions = [ "glue:CreateTable", ] resources = ["arn:data.awspartition.current.partition:glue:data.awsregion.current.name:data.awscalleridentity.current.account_id:*"] principals { identifiers = ["arn:aws:iam::var.accountid:saml-provider/var.providername"] type = "AWS" } } } resource "awsglueresource_policy" "exampleX" { policy = data.awsiampolicy_document.glue-example-policyX.json } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 09-22-2023-01-32-09_17c4c4f2.md

timestamp: "2023-09-22 01:31:53 UTC Fri" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.21.5" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Beam (App Definition and Development / Streaming & Messaging)
File: precommit-policies.md

title: "Pre-commit Test Policies" <!-- 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. --> Pre-commit test - Any single test in a pre-commit test suite. Pre-commit test suite - A collection of pre-commit tests that have a common denominator. A test suite runs in a single Jenkins job. Currently, suites are grouped by SDK languages, e.g., Python, Java, and Go. A PR must pass pre-commit tests before being committed to the main Beam repo. The relevant pre-commit test suites are automatically launched according to PR contents. Breakage is when one or more tests in a pre-commit test suite fails or is flaky (occasionally fails). Breakages should be fixed within 8 hours. Slowness is when the total time to run a pre-commit suite exceeds 30 minutes\*, including the time the job spends in the Jenkins queue. Slowness should be fixed within 24 hours. \* See the [Pre-commit Slowness Triage Guide](/contribute/precommit-triage-guide/) for a precise definition of slowness and for information on dealing with slowness. For any problem, the options are, one of: Roll back the culprit PR. Roll out a fix within 24 hours. Disable the slow test or feature temporarily (make sure there's a tracking issue to re-enable it).
Project: Kraken (Provisioning / Container Registry)
File: CONTRIBUTING.md

Please feel free to submit new issues. Start by reading our . Please follow standard fork-and-pull workflow. Fork the repo on GitHub Clone the project locally Commit changes to your own branch Push the change back to your fork Submit a Pull request. We will review and merge your change. Most tests and scripts assumes the developer to have Docker installed locally. To install dependencies: ``` $ make vendor ``` To run unit tests: ``` $ make unit-test ``` To run integration tests: ``` $ make integration ``` To build docker images: ``` $ make images ```
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: valid.md

Name | Description | Type | Required | Default | -- | - | -- | - cluster | The cluster to use. | string | true | resource | The resource to get or apply. | map[string]_ | true | options | The options to get or apply. | | true | Name | Description | Type | Required | Default | -- | - | -- | - threeWayMergePatch | The strategy of the resource. | | true | Name | Description | Type | Required | Default | -- | - | -- | - enabled | The strategy to get or apply the resource. | bool | false | true annotationPrefix | The annotation prefix to use for the three way merge patch. | string | false | resource Name | Description | Type | Required | Default | -- | - | -- | - \- | | {} | true | Name | Description | Type | Required | Default | -- | - | -- | - cluster | The cluster to use. | string | true | resource | The resource to get or apply. | map[string]_ | true | options | The options to get or apply. | | true | Name | Description | Type | Required | Default | -- | - | -- | - threeWayMergePatch | The strategy of the resource. | | true | Name | Description | Type | Required | Default | -- | - | -- | - enabled | The strategy to get or apply the resource. | bool | false | true annotationPrefix | The annotation prefix to use for the three way merge patch. | string | false | resource Name | Description | Type | Required | Default | -- | - | -- | - \- | | {} | true | Name | Description | Type | Required | Default | -- | - | -- | - cluster | The cluster to use. | string | true | filter | The filter to list the resources. | | false | resource | The resource to list. | map[string]_ | true | Name | Description | Type | Required | Default | -- | - | -- | - namespace | The namespace to list the resources. | string | false | matchingLabels | The label selector to filter the resources. | map[string]string | false | Name | Description | Type | Required | Default | -- | - | -- | - \- | | {} | true | Name | Description | Type | Required | Default | -- | - | -- | - cluster | The cluster to use. | string | true | resource | The resource to patch. | map[string]_ | true | patch | The patch to be applied to the resource with kubernetes patch. | | true | Name | Description | Type | Required | Default | -- | - | -- | - type | The type of patch being provided. | "merge" or "json" or "strategic" | true | data | | _ | true | Name | Description | Type | Required | Default | -- | - | -- | - \- | | {} | true |
Project: Fluvio (App Definition and Development / Streaming & Messaging)
File: PERF.md

This runs on Ubuntu Clone Flame Graph ``` git clone https://github.com/brendangregg/FlameGraph ``` Install Perf tools ``` sudo apt-get install linux-tools-5.4.0-1029-aws -y ``` Ensure release profile is set to debug to `Cargo.toml` ``` [profile.release] debug = true ``` ``` make RELEASE=true smoke-test ``` Create a topic ``` ./target/release/fluvio topic create t1 ``` ``` sudo perf record -p $(pgrep -f spu) --call-graph dwarf ``` ``` ./target/release/fluvio produce t1 -r $(ls /var/log/journal//*.journal) ``` then control-c Convert perf data into script ``` sudo perf script > perf.script ``` Generate graph ``` FlameGraph/stackcollapse-perf.pl perf.script | FlameGraph/flamegraph.pl > flame.svg ```
Project: Flink (App Definition and Development / Streaming & Messaging)
File: connector.md

title: "Connectors and Formats" weight: 5 type: docs <!-- 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. --> Flink applications can read from and write to various external systems via connectors. It supports multiple formats in order to encode and decode data to match Flink's data structures. An overview of available connectors and formats is available for both and . In order to use connectors and formats, you need to make sure Flink has access to the artifacts implementing them. For each connector supported by the Flink community, we publish two artifacts on : `flink-connector-<NAME>` which is a thin JAR including only the connector code, but excluding eventual third-party dependencies `flink-sql-connector-<NAME>` which is an uber JAR ready to use with all the connector third-party dependencies The same applies for formats as well. Note that some connectors may not have a corresponding `flink-sql-connector-<NAME>` artifact because they do not require third-party dependencies. {{< hint info >}} The uber/fat JARs are supported mostly for being used in conjunction with the , but you can also use them in any DataStream/Table application. {{< /hint >}} In order to use a connector/format module, you can either: Shade the thin JAR and its transitive dependencies in your job JAR Shade the uber JAR in your job JAR Copy the uber JAR directly in the `/lib` folder of the Flink distribution For shading dependencies, check out the specific and guides. For a reference about the Flink distribution, check . {{< hint info >}} Deciding whether to shade the uber JAR, the thin JAR or just include the dependency in the distribution is up to you and your use case. If you shade a dependency, you will have more control over the dependency version in the job JAR. In case of shading the thin JAR, you will have even more control over the transitive dependencies, since you can change the versions without changing the connector version (binary compatibility permitting). In case of embedding the connector uber JAR directly in the Flink distribution `/lib` folder, you will be able to control in one place connector versions for all jobs. {{< /hint >}}
Project: ClickHouse (App Definition and Development / Database)
File: v22.5.4.19-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix seeking while reading from encrypted disk. This PR fixes . (). Backported in : Former packages used to install systemd.service file to `/etc`. The files there are marked as `conf` and are not cleaned out, and not updated automatically. This PR cleans them out. (). Backported in : Fix reading of sparse columns from `MergeTree` tables that store their data in S3. (). Backported in : Fix data race and possible heap-buffer-overflow in Avro format. Closes Closes . (). Backported in : Fix bug with maxsplit argument for splitByChar, which was not working correctly. (). Backported in : Fix wrong index analysis with tuples and operator `IN`, which could lead to wrong query result. (). Backported in : Fix `CANNOTREADALLDATA` exception with `localfilesystemreadmethod=pread_threadpool`. This bug affected only Linux kernel version 5.9 and 5.10 according to . (). Fix reading from s3 in some corner cases (). Replace MemoryTrackerBlockerInThread to LockMemoryExceptionInThread (). Change mysql-odbc url ().
Project: SlimToolkit (Provisioning / Security & Compliance)
File: LICENSE.md

MIT License Copyright (c) 2017 Segment.io 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: Podman (App Definition and Development / Application Definition & Image Build)
File: network-alias.md

Add a network-scoped alias for the <<container|pod>>, setting the alias for all networks that the container joins. To set a name only for a specific network, use the alias option as described under the --network option. If the network has DNS enabled (`podman network inspect -f {{.DNSEnabled}} <name>`), these aliases can be used for name resolution on the given network. This option can be specified multiple times. NOTE: When using CNI a <<container|pod>> only has access to aliases on the first network that it joins. This limitation does not exist with netavark/aardvark-dns.
Project: Puppet (Provisioning / Automation & Configuration)
File: profiling.md

Puppet is a beast. Puppet is at times a very slow beast. Maybe we can find what is making it slow and fix it. There is a built-in system of profiling that can be used to identify some slow spots. This can only work with code that is explicitly instrumented, which, at the time of this writing, is primarily the compiler. To enable profiling there are several options: To profile every request on the master add `--profile` to your master's startup. To profile a single run for an agent add `--profile` to your agent's options for that run. To profile a masterless run add `--profile` to your `puppet apply` options. The timing information will be output to the logs and tagged with the word "PROFILE". For the agent there is actually a second system: evaltrace. You can enable this on the agent by passing it `--evaltrace`. Timing information for each resource will be output to the logs. For much finer grained profiling, you'll want to use . Once you have the gem installed you can either modify the code to profile a certain section (using RubyProf.profile) or run the master with ruby-prof by adding `use Rack::RubyProf, :path => '/temp/profile'` to the config.ru for your master. Puppet has a number of benchmark scenarios to pinpoint problems in specific, known, use cases. The benchmark scenarios live in the `benchmarks` directory. To run a scenario you do: bundle exec rake benchmark:<scenario_name> You can also run `heapdump`, `memoryprofile` or `profile` tasks for each scenario. You'll first need to run `bundle install --with development` to install the prerequisite gems. The `heap_dump` task generates a heap dump with object allocation tracing enabled. The `memory_profile` task generates a memory profile listing retained memory by file and location. The `profile` task generates a calltrace of the benchmark scenario: bundle exec rake benchmark:<scenario_name>:profile The calltrace file is viewable with .
Project: CockroachDB (App Definition and Development / Database)
File: hotranges-request.md

<a name="cockroach.server.serverpb.HotRangesRequest"></a> HotRangesRequest queries one or more cluster nodes for a list of ranges currently considered hot by the node(s). Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | node_id | | | NodeID indicates which node to query for a hot range report. It is possible to populate any node ID; if the node receiving the request is not the target node, it will forward the request to the target node.<br><br>If left empty, the request is forwarded to every node in the cluster. | | | page_size | | | | | | page_token | | | | | | tenant_id | | | | |