cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: latency-histogram.md

title: View latency histogram and P99 latency metrics for slow queries headerTitle: Latency histogram and P99 latencies linkTitle: Latency histogram description: View histogram and P99 latency metrics for slow queries menu: v2.18_yugabyte-platform: parent: alerts-monitoring identifier: latency-histogram weight: 50 type: docs Percentile metrics form the core set of metrics that enable users to measure query performance against SLOs (Service Level Objectives). Surfacing percentile metrics per normalized query and by Ops (Operations/second) type enables you to measure query performance against SLOs. Additionally, these metrics can help identify performance issues efficiently and quickly. You can view P99, P95, P90, and P50 metrics for every query displayed on the dashboard. You can view latency histograms for every YSQL query you run on one or multiple nodes of your universe and get an aggregated view of the metrics. Slow queries are only available for YSQL, with percentile metrics available in YBA version 2.18.2 or later, and latency histogram support in YugabyteDB version 2.18.1 (or later), or 2.19.1 (or later). To view the latency histogram and P99 metrics, access the Slow Queries dashboard and run YSQL queries using the following steps: Navigate to Universes, select your universe, then select Queries > Slow Queries. You may have to enable the Query monitoring option if it is not already. Run some queries on your universe by selecting one or more queries in the Slow Queries tab. You can see the query details listing the P25, P50, P90, P95, and P99 latency metrics as per the following illustration. To discard latency statistics gathered so far, click the Reset stats button on the Slow Queries dashboard to run on each node. {{< note title="Note" >}} If latency histogram is not reported by YBA, then the histogram graph is not displayed. If the P99 latency statistics are not reported by YBA (for example, because the database version doesn't support it), then `-` is displayed in the Query Details. {{< /note >}} for details on how to run queries and view the results. Latency histogram and percentile metrics are obtained using the `yblatencyhistogram` column in `pgstatstatements` and `ybgetpercentile` function. Refer to for details on using latency histograms in YugabyteDB.
Project: KICS (Provisioning / Security & Compliance)
File: 8173d5eb-96b5-4aa6-a71b-ecfa153c123d.md

title: CloudTrail Multi Region Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8173d5eb-96b5-4aa6-a71b-ecfa153c123d Query name: CloudTrail Multi Region Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: CloudTrail multi region should be enabled, which means attributes 'ismultiregiontrail' and 'includeglobalserviceevents' should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "aws_cloudtrail" "positive1" { name = "npositive_1" s3bucketname = "bucketlog_1" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="4" resource "aws_cloudtrail" "positive2" { name = "npositive_2" s3bucketname = "bucketlog_2" ismultiregion_trail = false } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="5" resource "aws_cloudtrail" "positive3" { name = "npositive_3" s3bucketname = "bucketlog_3" ismultiregion_trail = true includeglobalservice_events = false } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_cloudtrail" "negative1" { name = "negative" s3bucketname = "bucketlog" ismultiregion_trail = true } ```
Project: userver (App Definition and Development / Streaming & Messaging)
File: TODO.md

For my personal use mostly, in no particular order More topologies (multi-primary, automatic primary detection etc.) (~10h) TLS (3h, think about file access if any) Better unit-tests with clear separation of what is tested (8h) Fault-tolerance/chaos tests (ages) CI for MySQL 5.7, MySQL 8.0+ and MariaDB (+ the same for testsuite) (6h) Logging, metrics and some tests for metrics (6h) Better testing setup (without that ugly bash we have right now) (4h) MySQL Cache - very similar to PGs one, just unify (4h)
Project: KICS (Provisioning / Security & Compliance)
File: 5da47109-f8d6-4585-9e2b-96a8958a12f5.md

title: Basic Auth File Is Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5da47109-f8d6-4585-9e2b-96a8958a12f5 Query name: Basic Auth File Is Set Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: When using kube-apiserver command, the 'basic-auth-file' flag should not be set<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver", "--basic-auth-file=/path/to/any/file"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--basic-auth-file=/path/to/any/file"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: [] restartPolicy: OnFailure ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2023-02-32-10_2302b19a.md

timestamp: "2023-10-12 02:31:54 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.25.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.10.29-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fixed backward incompatibility in (de)serialization of states of `min`, `max`, `any`, `argMin`, `argMax` aggregate functions with `String` argument. The incompatibility was introduced in https://github.com/ClickHouse/ClickHouse/pull/41431 and affects 22.9, 22.10 and 22.11 branches (fixed since 22.9.6, 22.10.4 and 22.11.2 correspondingly). Some minor releases of 22.3, 22.7 and 22.8 branches are also affected: 22.3.13...22.3.14 (fixed since 22.3.15), 22.8.6...22.8.9 (fixed since 22.8.10), 22.7.6 and newer (will not be fixed in 22.7, we recommend to upgrade from 22.7.* to 22.8.10 or newer). This release note does not concern users that have never used affected versions. Incompatible versions append extra `'\0'` to strings when reading states of the aggregate functions mentioned above. For example, if an older version saved state of `anyState('foobar')` to `statecolumn` then incompatible version will print `'foobar\0'` on `anyMerge(statecolumn)`. Also incompatible versions write states of the aggregate functions without trailing `'\0'`. Newer versions (that have the fix) can correctly read data written by all versions including incompatible versions, except one corner case. If an incompatible version saved a state with a string that actually ends with null character, then newer version will trim trailing `'\0'` when reading state of affected aggregate function. For example, if an incompatible version saved state of `anyState('abrac\0dabra\0')` to `statecolumn` then incompatible versions will print `'abrac\0dabra'` on `anyMerge(statecolumn)`. The issue also affects distributed queries when an incompatible version works in a cluster together with older or newer versions. (). Backported in : Wait for all files are in sync before archiving them in integration tests. (). Backported in : - Fix several buffer over-reads. (). Backported in : Fixed queries with `SAMPLE BY` with prewhere optimization on tables using `Merge` engine. (). Backported in : Fix a bug when row level filter uses default value of column. (). Backported in : Fixed primary key analysis with conditions involving `toString(enum)`. (). Fix 02267fileglobsschemainference.sql flakiness (). Update SECURITY.md on new stable tags (). Use all parameters with prefixes from ssm (). Temporarily disable `testhivequery` (). Do not checkout submodules recursively (). Use docker images cache from merged PRs in master and release branches (). Fix pagination issue in GITHUBJOBID() ().
Project: RBAC Manager (Provisioning / Security & Compliance)
File: aks.md

Azure Kubernetes Service (AKS) enables mapping Azure Active Directory (AAD) users and groups to RBAC users and groups. Although not enabled by default, this post shows . With AAD integration enabled, groups and users are mapped directly to RBAC. Users are mapped using their user name (generally email) while groups are mapped using the group object ID. ```yaml apiVersion: rbacmanager.reactiveops.io/v1beta1 kind: RBACDefinition metadata: name: sample-config rbacBindings: name: web-developers subjects: kind: User name: jane@example.com kind: User name: joe@example.com roleBindings: clusterRole: edit namespace: web name: sample-group subjects: kind: Group name: 894656e1-39f8-4bfe-b16a-510f61af6f41 roleBindings: clusterRole: edit namespace: api ``` Because group IDs are not easy to understand in a Kubernetes context, we generally recommend sticking with AAD users and using RBAC Definitions to group them. This ensures that all authorization config for Kubernetes stays within Kubernetes.
Project: Vault (Provisioning / Key Management)
File: forms.md

<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> <!-- END doctoc generated TOC please keep comment here to allow auto update --> Render `FlashMessage` on success Handling errors/validation messages: Render API errors using a `<MessageError>` or `Hds::Alert` at the top of forms Display validation error messages `onsubmit` (not `onchange` for inputs) Render an `<AlertInline>` form buttons, especially if the error banner is hidden from view (long forms). Message options: The `invalidFormMessage` from a model's `validate()` method that includes an error count Generic message for API errors or forms without model validations: 'There was an error submitting this form.' Add `has-error-border` class to invalid inputs
Project: KICS (Provisioning / Security & Compliance)
File: 9e0c33ed-97f3-4ed6-8be9-bcbf3f65439f.md

title: Cloud SQL Instance With Cross DB Ownership Chaining On hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9e0c33ed-97f3-4ed6-8be9-bcbf3f65439f Query name: Cloud SQL Instance With Cross DB Ownership Chaining On Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: GCP SQL Instance should not have Cross DB Ownership Chaining On<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" name: sql_instance google.cloud.gcpsqlinstance: auth_kind: serviceaccount databaseversion: SQLSERVER13_1 name: "{{ resource_name }}-2" project: test_project region: us-central1 serviceaccountfile: /tmp/auth.pem settings: database_flags: name: cross db ownership chaining value: on tier: db-n1-standard-1 state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: sql_instance google.cloud.gcpsqlinstance: auth_kind: serviceaccount databaseversion: SQLSERVER13_1 name: '{{ resource_name }}-2' project: test_project region: us-central1 serviceaccountfile: /tmp/auth.pem settings: database_flags: name: name1 value: value1 tier: db-n1-standard-1 state: present ```
Project: KICS (Provisioning / Security & Compliance)
File: bb9ac4f7-e13b-423d-a010-c74a1bfbe492.md

title: Memory Not Limited hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bb9ac4f7-e13b-423d-a010-c74a1bfbe492 Query name: Memory Not Limited Platform: DockerCompose Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than the designated amount of memory<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: resources: limits: cpus: '0.3' reservations: cpus: '0.1' ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4" version: "2.4" services: criwhat: build: context: "./cri/what" restart: "unless-stopped" cpus: 0.25 environment: NODE_ENV=production PORT=5000 FLAG=FLAG-TOOMANYERRORSTOOMANY_DETAILS ports: 12345:6000 ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="3 7" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: ``` <details><summary>Positive test num. 4 - yaml file</summary> ```yaml hl_lines="8" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: resources: reservations: cpus: '0.1' memory: 128M ``` </details> <details><summary>Positive test num. 5 - yaml file</summary> ```yaml hl_lines="5" version: "3.9" services: redis: image: redis:alpine deploy: restart_policy: condition: on-failure delay: 5s max_attempts: 3 window: 120s ``` </details> ```yaml title="Negative test num. 1 - yaml file" version: "3.7" services: zapzop: image: openzapzop/zapzop ports: 6412:6412 deploy: resources: limits: cpus: '0.3' memory: 256M reservations: cpus: '0.1' memory: 128M ``` ```yaml title="Negative test num. 2 - yaml file" version: "2.4" services: criwhat: build: context: "./cri/what" restart: "unless-stopped" cpus: 0.25 mem_limit: 512m environment: NODE_ENV=production PORT=4000 FLAG=FLAG-TOOMANYERRORSTOOMANY_DETAILS ports: 12345:6000 ```
Project: StarRocks (App Definition and Development / Database)
File: space.md

displayed_sidebar: "English" Returns a string of the specified number of spaces. ```Haskell space(x); ``` `x`: the number of spaces to return. The supported data type is INT. Returns a value of the VARCHAR type. ```Plain Text mysql> select space(6); +-+ | space(6) | +-+ | | +-+ 1 row in set (0.00 sec) ``` SPACE
Project: KICS (Provisioning / Security & Compliance)
File: eafe4bc3-1042-4f88-b988-1939e64bf060.md

title: IAM Policies Attached To User hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: eafe4bc3-1042-4f88-b988-1939e64bf060 Query name: IAM Policies Attached To User Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: IAM policies should be attached only to groups or roles<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" name: Assign a policy called Admin to user community.aws.iam_policy: iam_type: user iam_name: administrators policy_name: Admin state: present policydocument: adminpolicy.json ``` ```yaml title="Negative test num. 1 - yaml file" name: Assign a policy called Admin to the administrators group community.aws.iam_policy: iam_type: group iam_name: administrators policy_name: Admin state: present policydocument: adminpolicy.json ```
Project: KICS (Provisioning / Security & Compliance)
File: 7674a686-e4b1-4a95-83d4-1fd53c623d84.md

title: Config Rule For Encrypted Volumes Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7674a686-e4b1-4a95-83d4-1fd53c623d84 Query name: Config Rule For Encrypted Volumes Disabled Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Check if AWS config rules do not identify Encrypted Volumes as a source.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2" name: foo community.aws.awsconfigrule: name: testconfigrule state: present description: 'This AWS Config rule checks for public write access on S3 buckets' scope: compliance_types: 'AWS::S3::Bucket' source: owner: AWS identifier: 'S3BUCKETPUBLICWRITEPROHIBITED' ``` ```yaml title="Negative test num. 1 - yaml file" name: foo community.aws.awsconfigrule: name: testconfigrule state: present description: This AWS Config rule checks for public write access on S3 buckets scope: compliance_types: AWS::S3::Bucket source: owner: AWS identifier: ENCRYPTED_VOLUMES ```
Project: KICS (Provisioning / Security & Compliance)
File: 36a27826-1bf5-49da-aeb0-a60a30c0e834.md

title: Kubelet Client Certificate Or Key Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 36a27826-1bf5-49da-aeb0-a60a30c0e834 Query name: Kubelet Client Certificate Or Key Not Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: When using kube-apiserver command, the 'kubelet-client-key' and 'kubelet-client-certificate' flags should be set<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--kubelet-client-certificate=/path/to/any/file.pem"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--kubelet-client-key=/path/to/any/file"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver", "--kubelet-client-certificate=/path/to/any/file.pem", "--kubelet-client-key=/path/to/any/file2.pem"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--kubelet-client-certificate=/path/to/any/file.pem", "--kubelet-client-key=/path/to/any/file2"] restartPolicy: OnFailure ```
Project: Stolon (App Definition and Development / Database)
File: bug-report.md

name: Bug Report about: Report a bug on Stolon labels: bug <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! NOTE: Please submit only bug reports. For other question or if unsure ask on the --> What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Stolon version: Stolon running environment (if useful to understand the bug): Others:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc-5h.md

layout: release date: 2022-03-28 tag: v0.6.0-rc-5h language: en [DDE] UI styling changes and configure to work with meshery server @sudo-NithishKarthik (#5292) Update URL viladate, compatible with RFC that is not URL standard @m9rco (#5287) [CI] Restructure makefile @leecalcote (#5283) Thank you to our contributors for making this release possible: @leecalcote, @m9rco, @sudo-NithishKarthik and @warunicorn19
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.9.24-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Keeper performance improvement: improve commit performance for cases when many different nodes have uncommitted states. This should help with cases when a follower node can't sync fast enough. (). Backported in : Update tzdata to 2022f. Mexico will no longer observe DST except near the US border: https://www.timeanddate.com/news/time/mexico-abolishes-dst-2022.html. Chihuahua moves to year-round UTC-6 on 2022-10-30. Fiji no longer observes DST. See https://github.com/google/cctz/pull/235 and https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995209. (). Backported in : Before the fix, the user-defined config was preserved by RPM in `$file.rpmsave`. The PR fixes it and won't replace the user's files from packages. (). Backported in : Add a CI step to mark commits as ready for release; soft-forbid launching a release script from branches but master. (). Backported in : Fixed `Unknown identifier (aggregate-function)` exception which appears when a user tries to calculate WINDOW ORDER BY/PARTITION BY expressions over aggregate functions: ``` CREATE TABLE default.tenk1 ( `unique1` Int32, `unique2` Int32, `ten` Int32 ) ENGINE = MergeTree ORDER BY tuple() SETTINGS indexgranularity = 8192; SELECT ten, sum(unique1) + sum(unique2) AS res, rank() OVER (ORDER BY sum(unique1) + sum(unique2) ASC) AS rank FROM complex GROUP BY ten ORDER BY ten ASC; ``` which gives: ``` Code: 47. DB::Exception: Received from localhost:9000. DB::Exception: Unknown identifier: sum(unique1); there are columns: unique1, unique2, ten: While processing sum(unique1) + sum(unique2) ASC. (UNKNOWN_IDENTIFIER) ```. (). Backported in : A segmentation fault related to DNS & c-ares has been reported. The below error ocurred in multiple threads: ``` 2022-09-28 15:41:19.008,2022.09.28 15:41:19.008088 (). Backported in : Fix rare NOTFOUNDCOLUMNINBLOCK error when projection is possible to use but there is no projection available. This fixes . The bug was introduced in https://github.com/ClickHouse/ClickHouse/pull/25563. (). Do not warn about kvm-clock (). Revert revert 41268 disable s3 parallel write for part moves to disk s3 (). Always run `BuilderReport` and `BuilderSpecialReport` in all CI types ().