cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: compiling-running-tests.md

id: version-0.20.5-incubating-compiling-running-tests title: Running Tests sidebar_label: Running Tests original_id: compiling-running-tests <!-- 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. --> Heron uses for building and running unit tests. Before running tests, first set up your build environment as described in . The following command will run all tests: ```bash $ bazel test heron/... ``` To run a specific [test target](http://bazel.io/docs/test-encyclopedia.html), pass the test target name. ```bash $ bazel test heron/statemgrs/tests/java:localfs-statemgr_unittest ``` To see a full listing of all Bazel test targets: ```bash $ bazel query 'kind(".*_test rule", ...)' ``` For Java targets only: ```bash $ bazel query 'kind("java_test rule", ...)' ``` For C++ targets: ```bash $ bazel query 'kind("cc_test rule", ...)' ``` For Python targets: ```bash $ bazel query 'kind("pex_test rule", ...)' ``` Integration tests are divided into two categories: Functional integration tests These integration tests are designed for testing the functionality of Heron, such as topologies and groupings. To run the functional integration tests on a Mac OS X, do the following: ```bash $ ./scripts/runintegrationtest.sh ``` Failure integration tests These integration tests are designed for testing recovery from failure/restart in certain processes, such as Topology Manager and Metrics Manager. To run the failure integration tests on a Mac OS X, do the following: ```bash $ bazel build integration_test/src/... $ ./bazel-bin/integrationtest/src/python/localtest_runner/local-test-runner ```
Project: KICS (Provisioning / Security & Compliance)
File: 7af2f4a3-00d9-47f3-8d15-ca0888f4e5b2.md

title: ElasticSearch Encryption With KMS Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7af2f4a3-00d9-47f3-8d15-ca0888f4e5b2 Query name: ElasticSearch Encryption With KMS Disabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: Check if any ElasticSearch domain isn't encrypted with KMS.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "awselasticsearchdomain" "positive1" { domain_name = "example" elasticsearch_version = "1.5" encryptatrest { enabled = true } } ``` ```tf title="Negative test num. 1 - tf file" resource "awselasticsearchdomain" "negative1" { domain_name = "example" elasticsearch_version = "1.5" encryptatrest { enabled = true kmskeyid = "some-key-id" } } ```
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_nodeattestor_jointoken.md

Must be used in conjunction with the agent-side join_token plugin The `join_token` plugin attests a node based on a pre-shared, one-time-use join token. A token must be generated by the server before it can be used to attest a node. The server uses the token to generate a SPIFFE ID with the form: ```xml spiffe://<trustdomain>/spire/agent/jointoken/<token> ``` This plugin has no configuration options. Tokens may be generated through the CLI utility (`spire-server token generate`) or through the CreateJoinToken RPC of the SPIRE Server .
Project: Druid (App Definition and Development / Database)
File: query-processing.md

id: query-processing title: "Query processing" <!-- ~ 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. --> This topic provides a high-level overview of how Apache Druid distributes and processes queries. The general flow is as follows: A query enters the service, which identifies the segments with data that may pertain to that query. The list of segments is always pruned by time, and may also be pruned by other attributes depending on how the datasource is partitioned. The Broker identifies which and services are serving those segments and distributes a rewritten subquery to each of the services. The Historical and MiddleManager services execute each subquery and return results to the Broker. The Broker merges the partial results to get the final answer, which it returns to the original caller. Druid uses time and attribute pruning to minimize the data it must scan for each query. For filters that are more precise than what the Broker uses for pruning, the inside each segment allow Historical services to identify matching rows before accessing the data. Once the Historical service knows which rows match a particular query, it only accesses the requires rows and columns. To maximize query performance, Druid uses the following techniques: Pruning the set of segments accessed for a query. Within each segment, using indexes to identify which rows must be accessed. Within each segment, only reading the specific rows and columns that are relevant to a particular query. See the following topic for more information: to learn how Druid services process query statements.
Project: KICS (Provisioning / Security & Compliance)
File: integrations_bitbucketpipelines.md

You can integrate KICS into Bitbucket Pipelines CI/CD. This provides you the ability to run KICS scans in your Bitbucket repositories and streamline vulnerabilities and misconfiguration checks to your infrastructure as code (IaC). ```yaml image: checkmarx/kics:latest pipelines: default: step: name: "Cx KICS" script: kics scan --ignore-on-exit results -p ${PWD} -o ${PWD} artifacts: results.json ``` <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/kics-scan-bitbucket-pipelines.png" width="850">
Project: Meshery (Provisioning / Automation & Configuration)
File: postgres-operator.md

layout: integration title: Postgres Operator subtitle: Collaborative and visual infrastructure as code for Postgres Operator image: /assets/img/integrations/postgres-operator/icons/color/postgres-operator-color.svg permalink: extensibility/integrations/postgres-operator docURL: https://docs.meshery.io/extensibility/integrations/postgres-operator description: integrations-category: Database integrations-subcategory: App Definition and Development registrant: Artifact Hub components: name: operator-configuration colorIcon: assets/img/integrations/postgres-operator/components/operator-configuration/icons/color/operator-configuration-color.svg whiteIcon: assets/img/integrations/postgres-operator/components/operator-configuration/icons/white/operator-configuration-white.svg description: name: postgresql colorIcon: assets/img/integrations/postgres-operator/components/postgresql/icons/color/postgresql-color.svg whiteIcon: assets/img/integrations/postgres-operator/components/postgresql/icons/white/postgresql-white.svg description: name: postgres-team colorIcon: assets/img/integrations/postgres-operator/components/postgres-team/icons/color/postgres-team-color.svg whiteIcon: assets/img/integrations/postgres-operator/components/postgres-team/icons/white/postgres-team-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: KubeEdge (Provisioning / Automation & Configuration)
File: CHANGES.md

v2/apierror:* return Unknown GRPCStatus when err source is HTTP () (), refs update google.golang.org/api to latest () () v2/apierror:* add apierror.FromWrappingError () () v2:* copy DetermineContentType functionality () () v2:* resolve bad genproto pseudoversion in go.mod () () add ExtractProtoMessage to apierror () () v2:* add OnHTTPCodes CallOption () () v2/apierror:* use errors.As in FromError () () v2:* bump release-please processing () ()
Project: StarRocks (App Definition and Development / Database)
File: lcase.md

displayed_sidebar: "English" This function converts a string to lower-case. It is analogous to the function lower. ```Haskell VARCHAR lcase(VARCHAR str) ``` ```Plain Text mysql> SELECT lcase("AbC123"); +--+ |lcase('AbC123') | +--+ |abc123 | +--+ ``` LCASE
Project: YugabyteDB (App Definition and Development / Database)
File: _index.md

title: Troubleshoot YugabyteDB Anywhere headerTitle: Troubleshoot linkTitle: Troubleshoot description: Troubleshoot issues in YugabyteDB Anywhere image: /images/section_icons/troubleshoot/troubleshoot.png headcontent: Diagnose and troubleshoot issues that arise from YugabyteDB universes and YugabyteDB Anywhere. menu: v2.18_yugabyte-platform: parent: yugabytedb-anywhere identifier: troubleshoot-yp weight: 710 type: indexpage <div class="row"> <div class="col-12 col-md-6 col-lg-12 col-xl-6"> <a class="section-link icon-offset" href="install-upgrade-issues/vm/"> <div class="head"> <img class="icon" src="/images/sectionicons/quickstart/install.png" aria-hidden="true" /> <div class="title">Install and upgrade issues</div> </div> <div class="body"> Troubleshoot issues encountered when installing or upgrading YugabyteDB Anywhere. </div> </a> </div> <div class="col-12 col-md-6 col-lg-12 col-xl-6"> <a class="section-link icon-offset" href="universe-issues/"> <div class="head"> <img class="icon" src="/images/sectionicons/quickstart/create_cluster.png" aria-hidden="true" /> <div class="title">Universe issues</div> </div> <div class="body"> Troubleshoot a YugabyteDB universe. </div> </a> </div> <div class="col-12 col-md-6 col-lg-12 col-xl-6"> <a class="section-link icon-offset" href="universe-issues/"> <div class="head"> <img class="icon" src="/images/sectionicons/quickstart/create_cluster.png" aria-hidden="true" /> <div class="title">Cloud provided configuration issues</div> </div> <div class="body"> Troubleshoot issues encountered when configuring cloud providers. </div> </a> </div> </div> -ybadmin/). {{<index/block>}} {{<index/item title="Upgrade YugabyteDB Anywhere" body="Upgrade your YugabyteDB Anywhere installation." href="upgrade-yp-installer/" icon="/images/sectionicons/quickstart/install.png">}} {{<index/item title="Synchronize replication after upgrade" body="Synchronize xCluster replication after an upgrade for universes set up using yb-admin." href="upgrade-yp-xcluster-ybadmin/" icon="/images/section_icons/manage/pitr.png">}} {{</index/block>}}
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: ConfluenceResultListItem.md

ConfluenceResultListItem.tsx reference ```tsx import React from 'react'; import { Link } from '@backstage/core-components'; import { IndexableDocument } from '@backstage/plugin-search-common'; import { Divider, ListItem, ListItemIcon, ListItemText, } from '@material-ui/core'; type Props = { result: IndexableDocument; }; export const ConfluenceResultListItem = ({ result }: Props) => { // Remove html tags from document text before displaying const chars = []; let isTag = false; for (const c of result.text.substring(0, 500)) { if (c === '<') { isTag = true; continue; } if (c === '>') { isTag = false; chars.push(' '); continue; } if (!isTag) { chars.push(c); } } const excerpt = chars.join('').substring(0, 80) + (result.text.length > 80 ? '...' : ''); return ( <Link to={result.location}> <ListItem alignItems="center"> <ListItemIcon> <img width="20" height="20" src="https://cdn.worldvectorlogo.com/logos/confluence-1.svg" /> </ListItemIcon> <ListItemText primaryTypographyProps={{ variant: 'h6' }} primary={result.title} secondary={excerpt} /> </ListItem> <Divider /> </Link> ); }; ```
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: images.md

Monokle Desktop has a dedicated Images panel which can be accessed from the menu: Clicking Images will show the list of all images that are found in the Navigator. The list of images will changed based on the Mode you're in: Local mode Preview mode (Helm or Kustomize) Cluster mode Clicking on an Image will select it and will open an Image Details panel on top of the Editor. In the panel, you can find basic information about the image and browse the image's tags. Hovering over an image will show the "Replace" action: Clicking on "Replace" will open a modal which allows you to enter a new tag for that image: After clicking "Done", the tag will be replaced with the newly specified value across all your resources.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: pull_request_template.md

Fixes <issue-or-jira-number> Release version: v/e5.? Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked: [ ] Added tests for the changes [ ] Added property-based tests for code which performs user input validation [ ] Changed lines covered in coverage report [ ] Change log has been added to `changes/(ce|ee)/(feat|perf|fix|breaking)-<PR-id>.en.md` files [ ] For internal contributor: there is a jira ticket to track this change if documentation update is required, or link to a follow-up jira ticket [ ] Schema changes are backward compatible (manual trigger) [ ] Change log has been added to `changes/` dir for user-facing artifacts update
Project: external-secrets (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: kind/bug assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: provide all relevant manifests provide the Kubernetes and ESO version Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-star.md

layout: global title: star (*) Clause displayTitle: Star (*) Clause license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. A shorthand to name all the referencable columns in the FROM clause or a specific table reference's columns or fields in the FROM clause. The star clause is most frequently used in the SELECT list. Spark also supports its use in function invocation and certain n-ary operations within the SELECT list and WHERE clause. ``` [ name . ] * [ except_clause ] except_clause EXCEPT ( { columnname | fieldname } [, ...] ) ``` name* If present limits the columns or fields to be named to those in the specified referencable field, column, or table. except_clause* Optionally prunes columns or fields from the referencable set of columns identified in the select_star clause. column_name* A column that is part of the set of columns that you can reference. field_name* A reference to a field in a column of the set of columns that you can reference. If you exclude all fields from a STRUCT, the result is an empty STRUCT. Each name must reference a column included in the set of columns that you can reference or their fields. Otherwise, Spark SQL raises a UNRESOLVEDCOLUMN error. If names overlap or are not unique, Spark raises an EXCEPTOVERLAPPING_COLUMNS error. ```sql -- Return all columns in the FROM clause SELECT * FROM VALUES(1, 2) AS TA(c1, c2), VALUES(a, b) AS TB(ca, cb); 1 2 a b -- Return all columns from TA SELECT TA.* FROM VALUES(1, 2) AS TA(c1, c2), VALUES(a, b) AS TB(ca, cb); 1 2 -- Return all columns except TA.c1 and TB.cb SELECT * EXCEPT (c1, cb) FROM VALUES(1, 2) AS TA(c1, c2), VALUES(a, b) AS TB(ca, cb); 2 a -- Return all columns, but strip the field x from the struct. SELECT TA.* EXCEPT (c1.x) FROM VALUES(named_struct(x, x, y, y), 2) AS (c1, c2), VALUES(a, b) AS TB(ca, cb); { y } 2 a b -- Return the first not-NULL column in TA SELECT coalesce(TA.*) FROM VALUES(1, 2) AS TA(c1, c2), VALUES(a, b) AS TB(ca, cb); 1 -- Return 1 if any column in TB contains a c. SELECT CASE WHEN c IN (TB.*) THEN 1 END FROM VALUES(1, 2) AS TA(c1, c2), VALUES(a, b) AS TB(ca, cb); NULL -- Return all column as a single struct SELECT (*) FROM VALUES(1, 2) AS TA(c1, c2), VALUES(a, b) AS TB(ca, cb); { c1: 1, c2: 2, ca: a, cb: b } -- Flatten a struct into individual columns SELECT c1.* FROM VALUES(named_struct('x', 1, 'y', 2)) AS TA(c1); 1 2 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: fabedge.md

layout: integration title: Fabedge subtitle: Collaborative and visual infrastructure as code for Fabedge image: /assets/img/integrations/fabedge/icons/color/fabedge-color.svg permalink: extensibility/integrations/fabedge docURL: https://docs.meshery.io/extensibility/integrations/fabedge description: integrations-category: Runtime integrations-subcategory: Cloud Native Network registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-cache-refresh.md

layout: global title: REFRESH displayTitle: REFRESH license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. `REFRESH` is used to invalidate and refresh all the cached data (and the associated metadata) for all Datasets that contains the given data source path. Path matching is by prefix, i.e. "/" would invalidate everything that is cached. ```sql REFRESH resource_path ``` resource_path* The path of the resource that is to be refreshed. ```sql -- The Path is resolved using the datasource's File Index. CREATE TABLE test(ID INT) using parquet; INSERT INTO test SELECT 1000; CACHE TABLE test; INSERT INTO test SELECT 100; REFRESH "hdfs://path/to/table"; ```
Project: Pachyderm (App Definition and Development / Streaming & Messaging)
File: Pulumi.dev1.README.md

Used for testing pulumi infra changes for the pulumi core project. This stack is reserved for testing pulumi IAC itself. The `pulumi up` is usually executed locally not from CI. This provides an environment to test IAC changes before they are commited and used by the other stacks. ITS A GOOD IDEA TO ASK IF ANYONE ELSE IS USING THIS STACK. You can always create a DEV2 etc if needed. The test DB test password is reqiored and needs to be set like so. Never check these values in. CI Uses its own stored in CircleCI. pulumi config set --secret rdsPGDBPassword $IACCIDB_PASSWORD `$ENTACTCODE` - Test enterprise env variable key needs to be set locally from where ever the `pulumi up` is called from. The following can be overwritten `pulumi config set pachdVersion << pachdVersion >>` `pulumi config set helmChartVersion << helmChartVersion >>` Tag all resources so we can track billing and usage. ``` Tags: pulumi.StringMap{ "Project": pulumi.String("Feature Testing"), "Service": pulumi.String("CI"), "Owner": pulumi.String("pachyderm-ci"), "Team": pulumi.String("Core"), }, ```
Project: YugabyteDB (App Definition and Development / Database)
File: cr-cr-staging-tables-sql.md

title: Create procedure crstagingtables() linkTitle: Create crstagingtables() headerTitle: Create the procedure crstagingtables() description: Creates a procedure that uses dynamic SQL to create three staging tables with the same structure. menu: v2.18: identifier: cr-cr-staging-tables-sql parent: ingest-scripts weight: 10 type: docs This procedure makes use of the function to get all the values as a `text construct to iterate of the array's values. Save this script as "cr-cr-staging-tables.sql" ```plpgsql drop procedure if exists crstagingtables() cascade; create procedure crstagingtables() language plpgsql as $body$ declare drop_table constant text := ' drop table if exists ? cascade; '; createstagingtable constant text := ' create table ?( code int not null, geo_value text not null, signal text not null, time_value date not null, direction text, issue date not null, lag int not null, value numeric not null, stderr numeric not null, sample_size numeric not null, geo_type text not null, data_source text not null, constraint ?pk primary key(geovalue, time_value)); '; names constant text[] not null := ( select arrayagg(stagingtable) from covidcast_names); name text not null := ''; begin foreach name in array names loop execute replace(drop_table, '?',name); execute replace(createstagingtable, '?',name); end loop; end; $body$; ```