cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: interpreting-performance-test-results.md

layout: default title: Interpreting Performance Test Results abstract: This guide is to help users to glean an insights of what the performance tests result should look like. permalink: guides/performance-management/interpreting-performance-test-results type: guides category: performance language: en Once a performance tests and run, it's disco analysis is performed and test results persisted. Results or downloadable and persisted in the format. <img src="{{ site.baseurl }}/assets/img/performance-management/dashboard.png" /> <img src="{{ site.baseurl }}/assets/img/performance-management/chart.png" /> For the best experience, you should compare between two or more tests of similar configuration. Tests that are configured with a high degree of variance (e.g., one test ran for a duration of 5 minutes, while another test ran for a duration of 1 hour) will produce comparisons that are more difficult to extrapolate insights from. Latency and throughput are the two most significantly examined signals. Meshery will use different algorithms to calculate results depending upon which load generator was used to run the test.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: mindvalley.md

title: "Mindvalley" icon: /images/logos/powered-by/mindvalley.png hasLink: "https://www.mindvalley.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: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_modes.md

Display the various modes in which to run the e2e plugin ``` sonobuoy modes [flags] ``` ``` -h, --help help for modes --verbose Do not truncate output for each mode. ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generate reports on your Kubernetes cluster by running plugins
Project: YugabyteDB (App Definition and Development / Database)
File: int-results.md

title: int-results linkTitle: int-results headerTitle: Output from running dontile(), dopercentrank(), and documedist() on t4.intscore description: Output from running dontile(), dopercentrank(), and documedist() on t4.intscore. menu: v2.18: identifier: int-results parent: normal-distribution-analysis-reports weight: 40 type: docs ``` Using ntile(). bucket | n | mins | maxs --+++ 1 | 5000 | 0.00000 | 33.00000 2 | 5000 | 33.00000 | 38.00000 3 | 5000 | 38.00000 | 40.00000 4 | 5000 | 40.00000 | 43.00000 5 | 5000 | 43.00000 | 45.00000 6 | 5000 | 45.00000 | 46.00000 7 | 5000 | 46.00000 | 48.00000 8 | 5000 | 48.00000 | 50.00000 9 | 5000 | 50.00000 | 51.00000 10 | 5000 | 51.00000 | 52.00000 11 | 5000 | 52.00000 | 54.00000 12 | 5000 | 54.00000 | 55.00000 13 | 5000 | 55.00000 | 57.00000 14 | 5000 | 57.00000 | 58.00000 15 | 5000 | 58.00000 | 60.00000 16 | 5000 | 60.00000 | 62.00000 17 | 5000 | 62.00000 | 64.00000 18 | 5000 | 64.00000 | 67.00000 19 | 5000 | 67.00000 | 71.00000 20 | 5000 | 71.00000 | 100.00000 Using percent_rank(). 1 | 5074 | 0.00000 | 33.00000 2 | 6330 | 34.00000 | 38.00000 3 | 3745 | 39.00000 | 40.00000 4 | 6871 | 41.00000 | 43.00000 5 | 5361 | 44.00000 | 45.00000 6 | 2963 | 46.00000 | 46.00000 7 | 6343 | 47.00000 | 48.00000 8 | 6611 | 49.00000 | 50.00000 9 | 3334 | 51.00000 | 51.00000 10 | 3491 | 52.00000 | 52.00000 11 | 6904 | 53.00000 | 54.00000 12 | 3476 | 55.00000 | 55.00000 13 | 6484 | 56.00000 | 57.00000 14 | 3055 | 58.00000 | 58.00000 15 | 5640 | 59.00000 | 60.00000 16 | 5066 | 61.00000 | 62.00000 17 | 4295 | 63.00000 | 64.00000 18 | 5162 | 65.00000 | 67.00000 19 | 4822 | 68.00000 | 71.00000 20 | 4973 | 72.00000 | 100.00000 Using cume_dist(). 1 | 4215 | 0.00000 | 32.00000 2 | 5622 | 33.00000 | 37.00000 3 | 3353 | 38.00000 | 39.00000 4 | 6342 | 40.00000 | 42.00000 5 | 5071 | 43.00000 | 44.00000 6 | 2778 | 45.00000 | 45.00000 7 | 6123 | 46.00000 | 47.00000 8 | 6419 | 48.00000 | 49.00000 9 | 3375 | 50.00000 | 50.00000 10 | 3334 | 51.00000 | 51.00000 11 | 6923 | 52.00000 | 53.00000 12 | 3472 | 54.00000 | 54.00000 13 | 6785 | 55.00000 | 56.00000 14 | 3175 | 57.00000 | 57.00000 15 | 5937 | 58.00000 | 59.00000 16 | 5315 | 60.00000 | 61.00000 17 | 4779 | 62.00000 | 63.00000 18 | 5574 | 64.00000 | 66.00000 19 | 5456 | 67.00000 | 70.00000 20 | 5952 | 71.00000 | 100.00000 ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: bash.md

+++ title = "bash resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "bash" identifier = "inspec/resources/os/bash.md bash resource" parent = "inspec/resources/os" +++ Use the `bash` Chef InSpec audit resource to test an arbitrary command that is run on the system using a Bash script. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `command` resource block declares a command to be run, one (or more) expected outputs, and the location to which that output is sent: describe bash('command') do it { should exist } its('property') { should eq 'expected value' } end where `'command'` must specify a command to be run `'property'` is one of `exit_status`, `stderr`, or `stdout` `'expected value'` tests the output of the command run on the system versus the expected output stated in the test For example: describe bash('ls -al /') do its('stdout') { should match /bin/ } its('stderr') { should eq '' } its('exit_status') { should eq 0 } end The `exit_status` property returns the exit status for the command. its('exit_status') { should eq 0 } The `stderr` property returns results of the command as returned in standard error (stderr). its('stderr') { should eq '' } The `stdout` property returns the results of the command as returned in standard output (stdout). its('stdout') { should match /bin/ } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. If an absolute path is provided, the `exist` matcher tests if the command exists on the filesystem at the specified location. Otherwise, the `exist` matcher tests if the command is found in the PATH. it { should exist }
Project: FOSSA (Provisioning / Security & Compliance)
File: projectjson.md

The `project.json` file maintains a list of packages used in a project, known as a package management format. It supersedes `packages.config` but is in turn superseded by `PackageReference` with NuGet 4.0+. Walk the directory and find all files names `project.json` Parse the JSON file and search for the `dependencies` section: ``` "dependencies": { "Microsoft.NETCore": "5.0.0", "System.Runtime.Serialization.Primitives": "4.0.10" } ```
Project: Strimzi (App Definition and Development / Streaming & Messaging)
File: KAFKA_VERSIONS.md

There is no definitive guide as every version might bring surprises. But these are some of the tasks you usually have to do. If you add a new minor version, add new 3rd party libs directory to `docker-images/artifacts/kafka-thirdparty-libs` This directory is typically shared by all patch releases which are part of the same minor release. So it is named `<MAJOR>.<MINOR>.x`- e.g. `1.1.x` Add a `pom.xml` file with dependencies and make sure they are aligned with the dependencies inside Kafka (e.g. use similar version of Jackson libraries) Typically, you would do this by copying the directory for the previous minor version Add the new version to `kafka-versions.yaml` file If the version you are adding is the latest, mark it as `default: true` and mark the previous one as `default: false` If the version you are adding is the latest Update the Kafka versions and protocol versions in the documentation `attributes.adoc` If needed, update the examples (only in the `packaging/examples` directory): The `version` and the `inter.broker.protocol.version` fields The Docker image tag in the Kafka connect Build example Update the main `pom.xml` to use the latest Kafka version in the operator Update `systemtest/src/test/resources/upgrade/BundleUpgrade.yaml` with the new version Update protocol versions in `cluster-operator/src/test/java/io/strimzi/operator/cluster/model/KafkaConfigurationTests.java` if needed Make sure the `cluster-operator/src/test/java/io/strimzi/operator/cluster/KafkaVersionTestUtils.java` is up-to-date If you are adding a release candidate which is not yet published to Maven central, make sure to update the `STFILEPLUGINURLDEFAULT` field in `systemtest/src/main/java/io/strimzi/systemtest/Environment.java` to get the system tests to pass. Run `make all` to update all the installation files, generated docs files, Helm chart etc. You will need to commit also all the files it updates before opening a PR. Add a `CHANGELOG.md` record Run unit tests Run system tests (typically as part of the PR on Azure Pipelines) Edit the `kafka-versions.yaml` file and mark the version as unsupported (do not remove it, just set the `supported` flag to `false`) Run `make all` to update all the installation files, generated docs files, Helm chart etc. You will need to commit also all the files it updates before opening a PR. Make sure the version is not referenced anywhere anymore (apart from the obvious places such as CHANGELOG.md) Add a `CHANGELOG.md` record Run unit tests Run system tests
Project: Chef InSpec (Provisioning / Security & Compliance)
File: enhanced-outcomes.md

Enhanced Outcomes refers to the addition of new control outcomes to the InSpec vocabulary. It is essential to understand that Enhanced Outcomes refers to new control outcomes, the results of running a control. The results of running a test, a `describe block` are determined by RSpec and are limited to `Pass`, `Fail`, and `Skip`. Test outcomes are much more difficult to extend than control outcomes. Enhanced Outcomes adds three new control outcomes to the existing `Pass`, `Fail`, and `Skip` outcomes. In the first iteration of Enhanced Outcomes, the Error outcome is detected: if the message of any test includes the text "Control source error" OR the result of any test includes a backtrace Then the entire control should be marked `Error`. Additional means of detecting error may be developed in the future. Error's abbreviation is `ERR`. Error's UI color assignment is `Indigo`. If the control is not in `Error` and the impact of the control is `0.0`, then the control's outcome is `Not Applicable`. Not Applicable's abbreviation is `N/A`. Not Applicable's UI color assignment is `Sky Blue`. If the control is not in `Error` or `Not Applicable`, and all test results are `Skipped`, then the control outcome is `Not Reviewed`. Not Reviewed replaces `Skipped` as a control outcome. Not Reviewed's abbreviation is `N/R`. Not Reviewed's UI color assignment is `Amber`. A new CLI option will be introduced for `inspec exec`, `inspec shell`, and `inspec schema` that controls the Enhanced Outcomes functionality. In InSpec 5.x, a user must request the enhanced outcomes functionality explicitly by adding the `--enhanced-outcomes` option. In InSpec 6.x, --enhanced-outcomes will default to `true`. A user may request disabling the enhanced outcomes functionality by adding the `--no-enhanced-outcomes` option.
Project: ClickHouse (App Definition and Development / Database)
File: v20.11.5.18-stable.md

Backported in : Fix performance of reading from `Merge` tables over huge number of `MergeTree` tables. Fixes . (). Backported in : Throw error when use ColumnTransformer replace non exist column. (). Backported in : Fixed uncontrolled growth of TDigest. (). Backported in : Return number of affected rows for INSERT queries via MySQL protocol. Previously ClickHouse used to always return 0, it's fixed. Fixes . (). Backported in : TODO. (). Backported in : Fix optimization of group by with enabled setting `optimizeaggregatorsofgroupby_keys` and joins. Fixes . (). Backported in : Fix order by optimization with monotonous functions. Fixes . (). Backported in : Bug fix for funciton fuzzBits, related issue: . (). Backported in : Fix ColumnConst comparison which leads to crash. This fixed . (). Backported in : Fix possible wrong index analysis when the types of the index comparison are different. This fixes . (). Backported in : Fix . When clickhouse-copier handle non-partitioned table, throws segfault error. (). Backported in : Fix set index invalidation when there are const columns in the subquery. This fixes . (). Backported in : Fix crash while reading from `JOIN` table with `LowCardinality` types. Fixes . (). Backported in : Fix duplicates after `DISTINCT` which were possible because of incorrect optimization. Fixes . (). (). Backported in : Fix `ORDER BY` with enabled setting `optimizeredundantfunctionsinorder_by`. (). Backported in : Fix bug when mark cache size was underestimated by clickhouse. It may happen when there are a lot of tiny files with marks. (). Backported in : Fix alter query hang when the corresponding mutation was killed on the different replica. Fixes . (). Backported in : When clickhouse-client is used in interactive mode with multiline queries, single line comment was erronously extended till the end of query. This fixes . (). Backported in : Exception `fmt::v7::format_error` can be logged in background for MergeTree tables. This fixes . (). Backported in : In might be determined incorrectly if cluster is circular- (cross-) replicated or not when executing `ON CLUSTER` query due to race condition when `pool_size` > 1. It's fixed. (). Fix optimizetrivialcount_query with partition predicate (backport to 20.11). (). Backported in : Fixed `Function not implemented` error when executing `RENAME` query in `Atomic` database with ClickHouse running on Windows Subsystem for Linux. Fixes . (). Backported in : Fixed problem when ClickHouse fails to resume connection to MySQL servers. (). Backported in : Do not restore parts from WAL if `inmemorypartsenablewal` is disabled. (). Backported in : Update embedded timezone data to version 2020d (also update cctz to the latest master). ().
Project: RBAC Lookup (Provisioning / Security & Compliance)
File: usage.md

In the simplest use case, rbac-lookup will return any matching user, service account, or group along with the roles it has been given. ``` rbac-lookup rob SUBJECT SCOPE ROLE rob@example.com cluster-wide ClusterRole/view rob@example.com nginx-ingress ClusterRole/edit ``` The wide output option includes the kind of subject along with the source role binding. ``` rbac-lookup rob --output wide SUBJECT SCOPE ROLE SOURCE User/rob@example.com cluster-wide ClusterRole/view ClusterRoleBinding/rob-cluster-view User/rob@example.com nginx-ingress ClusterRole/edit RoleBinding/rob-edit User/ron@example.com web ClusterRole/edit RoleBinding/ron-edit ServiceAccount/rops infra ClusterRole/admin RoleBinding/rops-admin ``` It's also possible to filter output by the kind of RBAC Subject. The `--kind` or `-k` parameter accepts `user`, `group`, and `serviceaccount` as values. ``` rbac-lookup ro --output wide --kind user SUBJECT SCOPE ROLE SOURCE User/rob@example.com cluster-wide ClusterRole/view ClusterRoleBinding/rob-cluster-view User/rob@example.com nginx-ingress ClusterRole/edit RoleBinding/rob-edit User/ron@example.com web ClusterRole/edit RoleBinding/ron-edit ``` ``` --context string context to use for Kubernetes config --gke enable GKE integration -h, --help help for rbac-lookup -k, --kind string filter by this RBAC subject kind (user, group, serviceaccount) --kubeconfig string config file location -o, --output string output format (normal, wide) ```
Project: Open Policy Administration Layer (OPAL) (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Submit a bug report to help us improve title: '' labels: bug assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Please include steps to reproduce the bug: i.e: run OPAL, submit a realtime update through the API, etc. Please also include: Full logs of opal server and opal client Your configuration for OPAL server and OPAL client i.e: docker compose, Kubernetes YAMLs, environment variables, etc. you should redact any secrets/tokens/api keys in your config Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. OPAL version Version: [e.g. 0.1.18]
Project: Ansible (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

Hi! Nice to see you here! Please see the for information on how to ask questions on the and IRC. The GitHub issue tracker is not the best place for questions for various reasons, but both IRC and the mailing list are very helpful places for those things, as the community page explains best. By contributing to this project you agree to the . The Ansible project is licensed under the or later. Some portions of the code fall under other licenses as noted in individual files. The Ansible project accepts contributions through GitHub pull requests. Please review the for more information on contributing to Ansible. First and foremost, also check the . You can report bugs or make enhancement requests at the by filling out the issue template that will be presented. Also please make sure you are testing on the latest released version of Ansible or the development branch. See the for details. Thanks! This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. ```text Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 1 Letterman Drive Suite D4700 San Francisco, CA, 94129 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ```
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.7.24-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Do not fetch changed submodules in the builder container. (). Select from system tables when table based on table function. (). Fix incomplete query result for UNION in view() function. (). Fix crash in case of adding a column with type Object(JSON) (). Fix segfault during Kerberos initialization (). Fix: RabbitMQ OpenSSL dynamic loading issue (). Fix crash in FPC codec (). Backported in :. (). Rewrite jobs to use callable workflow (). Continue rewriting workflows to reusable tests (). Better exception messages ().
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: KICS (Provisioning / Security & Compliance)
File: 7db8bd7e-9772-478c-9ec5-4bc202c5686f.md

title: OSS Bucket Lifecycle Rule Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7db8bd7e-9772-478c-9ec5-4bc202c5686f Query name: OSS Bucket Lifecycle Rule Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Backup URL: OSS Bucket should have lifecycle rule enabled and set to true<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" resource "alicloudossbucket" "ossbucketlifecycle_enabled2" { bucket = "bucket-170309-lifecycle" acl = "public-read" lifecycle_rule { id = "rule-days" prefix = "path1/" enabled = false expiration { days = 365 } } lifecycle_rule { id = "rule-date" prefix = "path2/" enabled = true expiration { date = "2018-01-12" } } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "alicloudossbucket" "ossbucketlifecycle_enabled3" { bucket = "bucket-170309-versioning" acl = "private" versioning { status = "Enabled" } } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudossbucket" "ossbucketlifecycle_enabled1" { bucket = "bucket-170309-lifecycle" acl = "public-read" lifecycle_rule { id = "rule-days" prefix = "path1/" enabled = true expiration { days = 365 } } lifecycle_rule { id = "rule-date" prefix = "path2/" enabled = true expiration { date = "2018-01-12" } } } ```
Project: StarRocks (App Definition and Development / Database)
File: bitmap_contains.md

displayed_sidebar: "English" Calculates whether the input value is in the bitmap column, and returns a Boolean value. ```Haskell B00LEAN BITMAP_CONTAINS(BITMAP bitmap, BIGINT input) ``` ```Plain Text MySQL > select bitmapcontains(tobitmap(1),2) cnt; ++ | cnt | ++ | 0 | ++ MySQL > select bitmapcontains(tobitmap(1),1) cnt; ++ | cnt | ++ | 1 | ++ ``` BITMAP_CONTAINS,BITMAP