cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 2a153952-2544-4687-bcc9-cc8fea814a9b.md

title: Variable Without Description hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2a153952-2544-4687-bcc9-cc8fea814a9b Query name: Variable Without Description Platform: Terraform Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: All variables should contain a valid description.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" variable "cluster_name" { default = "example" type = string } resource "awsekscluster" "positive1" { dependson = [awscloudwatchloggroup.example] name = var.cluster_name } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="4" variable "cluster_name" { default = "example" type = string description = " " } resource "awsekscluster" "positive1" { dependson = [awscloudwatchloggroup.example] name = var.cluster_name } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="4" variable "cluster_name" { default = "example" type = string description = "" } resource "awsekscluster" "positive1" { dependson = [awscloudwatchloggroup.example] name = var.cluster_name } ``` ```tf title="Negative test num. 1 - tf file" variable "cluster_name" { default = "example" description = "cluster name" type = string } resource "awsekscluster" "negative1" { dependson = [awscloudwatchloggroup.example] enabledclusterlog_types = ["api", "audit", "authenticator", "controllerManager", "scheduler"] name = var.cluster_name } ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.19.1-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Improve performance of JSON and XML output formats. (). Backported in : Quota limit was not reached, but the limit was exceeded. This PR fixes . (). Backported in : Fix bug when remove unneeded columns in subquery. If there is an aggregation function in query without group by, do not remove if it is unneeded. (). Backported in : Fix `ORDER BY ... WITH FILL` with set `TO` and `FROM` and no rows in result set. (). Backported in : Functions for case-insensitive search in UTF8 strings like `positionCaseInsensitiveUTF8` and `countSubstringsCaseInsensitiveUTF8` might find substrings that actually does not match, it's fixed. (). Backported in : Using `formatRow` function with not row formats led to segfault. Don't allow to use this function with such formats (because it doesn't make sense). (). Backported in : Remove not like function into RPNElement. (). Backported in : Disable `partialmergejoinlefttablebufferbytes` before bug in this optimization is fixed. See ). * Remove redundant option `partialmergejoin_optimizations`. (). Backported in : Settings `inputformatallowerrorsnum` and `inputformatallowerrorsratio` did not work for parsing of domain types, such as `IPv4`, it's fixed. Fixes . (). Backported in : Fix race in JSONEachRowWithProgress output format when data and lines with progress are mixed in output. (). Backported in : Fix usage of `Buffer` table engine with type `Map`. Fixes . (). Backported in : Fix crash when function `dictGet` with type is used for dictionary attribute when type is `Nullable`. Fixes . (). Backported in : Fix possible assertion `../src/IO/ReadBuffer.h:58: bool DB::ReadBuffer::next(): Assertion '!hasPendingData()' failed.` in TSKV format. (). Backported in : Number of active replicas might be determined incorrectly when inserting with quorum if setting `replicatedcanbecome_leader` is disabled on some replicas. It's fixed. (). BloomFilter index check fix (). Support toUInt8/toInt8 for if constant condition optimization. ().
Project: YugabyteDB (App Definition and Development / Database)
File: cloud-add-peering.md

title: Peering connections headerTitle: linkTitle: Peering connections description: Manage peering connections to your cloud VPCs. headcontent: Manage peering connections to your VPCs menu: preview_yugabyte-cloud: identifier: cloud-add-peering parent: cloud-vpcs weight: 30 type: docs A peering connection connects a YugabyteDB Managed VPC with a VPC on the same cloud provider (AWS or GCP) - typically one that hosts an application that you want to have access to your cluster. Peering connections are not supported in Azure (use a ). {{< youtube id="Yu59wX8Rsug" title="Create a peering connection to access a cluster in YugabyteDB Managed" >}} In the context of YugabyteDB Managed, when a Yugabyte cluster is deployed in a VPC, it can connect to an application running on a peered VPC as though it was located on the same network; all traffic stays in the cloud provider's network. The VPCs can be in different regions, but ideally should be in the same region. You must create a VPC before you can configure a peering connection. To learn how to peer VPCs, refer to . Peering Connections on the VPC Network tab of the Networking page displays a list of peering connections configured for your account that includes the peering connection name, cloud provider, the network name (GCP) or ID (AWS) of the peered VPC, the name of the YugabyteDB VPC, and of the connection (Pending or Active). To view the peering connection details, select a peering connection in the list to display the Peering Details sheet. To create a peering connection, click Add Peering Connection. For details, refer to . To terminate a peering connection, click the Delete icon for the peering connection in the list you want to terminate, then click Terminate. You can also terminate a peering connection by clicking Terminate Peering in the Peering Details sheet. If a peering connection is Pending, you need to complete the peering with the corresponding cloud provider. Refer to or . If you have an Active peering connection but are unable to connect to a cluster in the VPC, ensure that you have added the CIDR block of the peered application VPC to your cluster's IP allow list. For information on adding IP allow lists, refer to .
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: time-extraction-filter.md

A `timeExtractionFilter` built-in transformer implements both the `eventTimeExtractor` and `filter` built-in functions. It evaluates a message on a pipeline and if valid, extracts event time from the payload of the messsage. `filterExpr` is used to evaluate and drop invalid messages. `eventTimeExpr` is used to compile the payload to a string representation of the event time. `format` is used to convert the event time in string format to a `time.Time` object. The expressions for the filter and event time extractor are implemented with `expr` and `sprig` libraries. These function can be accessed directly in expression. `payload` keyword represents the message object. It will be the root element to represent the message object in expression. `json` - Convert payload in JSON object. e.g: `json(payload)` `int` - Convert element/payload into `int` value. e.g: `int(json(payload).id)` `string` - Convert element/payload into `string` value. e.g: `string(json(payload).amount)` `Sprig` library has 70+ functions. `sprig` prefix need to be added to access the sprig functions. E.g: `sprig.trim(string(json(payload).timestamp))` # Remove spaces from either side of the value of field `timestamp` Depending on whether a `format` is specified, the Event Time Extractor uses different approaches to convert the event time string to a `time.Time` object. ```yaml spec: vertices: name: in source: http: {} transformer: builtin: name: timeExtractionFilter kwargs: filterExpr: int(json(payload).id) < 100 eventTimeExpr: json(payload).item[1].time eventTimeFormat: 2006-01-02T15:04:05Z07:00 ```
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: sup_crypto.md

+++ title = "Supervisor Cryptography" date = 2020-10-26T19:09:25-07:00 draft = false gh_repo = "habitat" [menu] [menu.habitat] title = "Supervisor Cryptography" identifier = "habitat/supervisors/Supervisor Cryptography" parent = "habitat/supervisors" weight = 70 +++ Chef Habitat implements cryptography using a Rust of called `libsodium`. `libsodium` provides a fast, modern framework for encryption, decryption, signing, and verification. Chef Habitat uses both symmetric encryption (for wire encryption) and asymmetric encryption (for everything else). If you are not familiar with the difference between the two, please consult . When you have either wire encryption or service group encryption turned on, the messages use the Curve25519, Salsa20, and Poly1305 ciphers specified in . Chef Habitat packages are signed using checksums. BLAKE2b is a cryptographic hash function faster than MD5, SHA-1, SHA-2 and SHA3, yet provides at least as much security as the latest standard SHA-3. You can examine the first four lines of a `.hart` file to extract the signature from it, because it is an `xz`-compressed tarball with a metadata header. The `hab pkg header` command will do this for you. ```bash hab pkg header somefile.hart ``` outputs: ```bash Reading package header for somefile.hart Package : somefile.hart Format Version : HART-1 Key Name : myorigin-19780608081445 Hash Type : BLAKE2b Raw Signature : a8yDoiA0Mv0CcW6xVyfkSOIZ0LW0beef4RPtvKL56MxemgG6dMVlKG1Ibplp7DUByr5az0kI5dmJKXgK6KURDzM1N2Y2MGMxYWJiMTNlYjQxMjliZTMzNGY0MWJlYTAzYmI4NDZlZzM2MDRhM2Y5M2VlMDkyNDFlYmVmZDk1Yzk= ``` The `.hart` file format is designed in this way to allow you to extract both the signature and the payload separately for inspection. To extract only the `xz`-compressed content, bypassing the signature, you could type this: ```bash tail -n +6 somefile.hart | xzcat | tar x ```
Project: Druid (App Definition and Development / Database)
File: standalone-realtime.md

id: standalone-realtime layout: doc_page title: "Realtime Process" <!-- ~ 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. --> Older versions of Apache Druid supported a standalone 'Realtime' process to query and index 'stream pull' modes of real-time ingestion. These processes would periodically build segments for the data they had collected over some span of time and then set up hand-off to servers. This processes could be invoked by ``` org.apache.druid.cli.Main server realtime ``` This model of stream pull ingestion was deprecated for a number of both operational and architectural reasons, and removed completely in Druid 0.16.0. Operationally, realtime nodes were difficult to configure, deploy, and scale because each node required an unique configuration. The design of the stream pull ingestion system for realtime nodes also suffered from limitations which made it not possible to achieve exactly once ingestion. The extensions `druid-kafka-eight`, `druid-kafka-eight-simpleConsumer`, `druid-rabbitmq`, and `druid-rocketmq` were also removed at this time, since they were built to operate on the realtime nodes. Please consider using the or for stream pull ingestion instead.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: controller-configmap.md

The controller ConfigMap is used for controller-wide settings. For a detailed example, please see . The configuration should be under `controller-config.yaml` key in the ConfigMap, as a string in `yaml` format: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: numaflow-controller-config data: controller-config.yaml: | defaults: containerResources: | ... isbsvc: jetstream: ... ``` Currently, we support configuring the init and main container resources for steps across all the pipelines. The configuration is under `defaults` key in the ConfigMap. For example, to set the default container resources for steps across all the pipelines: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: numaflow-controller-config data: controller-config.yaml: | defaults: containerResources: | limits: memory: "256Mi" cpu: "200m" requests: memory: "128Mi" cpu: "100m" ``` One of the important configuration items in the ConfigMap is about . We currently use 3rd party technologies such as `JetStream` to implement ISB Services, if those applications have new releases, to make them available in Numaflow, the new versions need to be added in the ConfigMap. For example, there's a new `Nats JetStream` version `x.y.x` available, a new version configuration like below needs to be added before it can be referenced in the `InterStepBufferService` spec. ```yaml apiVersion: v1 kind: ConfigMap metadata: name: numaflow-controller-config data: controller-config.yaml: | isbsvc: jetstream: versions: version: x.y.x # Name it whatever you want, it will be referenced in the InterStepBufferService spec. natsImage: nats:x.y.x metricsExporterImage: natsio/prometheus-nats-exporter:0.9.1 configReloaderImage: natsio/nats-server-config-reloader:0.7.0 startCommand: /nats-server ```
Project: MongoDB (App Definition and Development / Database)
File: otel_resmoke.md

OTel is one of two systems we use to capture metrics from resmoke. For mongo-tooling-metrics please see the documentation . Using OTel we capture the following things How long a resmoke suite takes to run (a collection of js tests) How long each test in a suite takes to run (a single js test) Duration of hooks before and after test/suite Resmoke archiver (when there is a failure we archive core dumps) To see this visually navigate to the and view a recent trace. The bulk of configuration is done in the `setup_tracing(...)` method in . This method includes documentation on how it works. See documentation See documentation We mostly capture data by using a decorator on methods. Example taken from ``` TRACER = trace.get_tracer("resmoke") @TRACER.startascurrentspan("funcname") def func_name(...): span = trace.getcurrentspan() span.set_attribute("attr1", True) ``` This system is nice because the decorator captures exceptions and other failures and a user can never forget to close a span. On occasion we will also start a span using the `with` clause in python. However, the decorator method is preferred since the method below makes more of a readability impact on the code. This example is taken from ``` with TRACER.startascurrentspan("funcname", attributes={}): func_name(...) ... ``` Using and we can see the most expensive single js tests. We plan to make tickets for teams to fix these long running tests for cloud savings as well as developer time savings.
Project: zot (Provisioning / Container Registry)
File: _zot.md

`zot` === `zot` extension has following components accessible under `/v2/_zot` endpoint. Component | Endpoint | Description | | | `/v2/_zot/ext/search` | efficient and enhanced registry search capabilities using graphQL backend | `/v2/_zot/ext/mgmt` | config management | `/v2/_zot/ext/userprefs` | change user preferences | `/v2/_zot/ext/cosign` | cosign public key management | `/v2/_zot/ext/notation` | notation certificate management [1] https://github.com/opencontainers/distribution-spec/tree/main/extensions
Project: Apache CarbonData (App Definition and Development / Database)
File: documentation.md

<!-- 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. --> Apache CarbonData is a new big data file format for faster interactive query using advanced columnar storage, index, compression and encoding techniques to improve computing efficiency, which helps in speeding up queries by an order of magnitude faster over PetaBytes of data. File Format Concepts: Start with the basics of understanding the and its . This will help to understand other parts of the documentation, including deployment, programming and usage guides. Quick Start: on your local machine or . CarbonData SQL Language Reference: CarbonData extends the Spark SQL language and adds several and statements to support operations on it. Refer to the to understand the supported features and functions. Programming Guides: You can read our guides about or to learn how to integrate CarbonData with your applications. CarbonData can be integrated with popular execution engines like , and . CarbonData can be integrated with popular storage engines like HDFS, Huawei Cloud(OBS) and . Refer to the section to understand all modes of Integrating CarbonData. The Apache CarbonData community welcomes all kinds of contributions from anyone with a passion for faster data format.Contributing to CarbonData doesnt just mean writing code. Helping new users on the mailing list, testing releases, and improving documentation are also welcome.Please follow the before proposing a design or code change. Compiling CarbonData: This will help you to compile and generate the jars for test. Wiki: You can read the page for upcoming release plan, blogs and training materials. Summit: Presentations from past summits and conferences can be found . Blogs: Blogs by external users can be found . Performance reports: TPC-H performance reports can be found . Trainings: Training records on design and code flows can be found .
Project: YugabyteDB (App Definition and Development / Database)
File: create_procedure,arg_decl_with_dflt,arg_decl,subprogram_signature,unalterable_proc_attribute,lang_name,implementation_definition,sql_stmt_list,alterable_fn_and_proc_attribute.grammar.md

```output.ebnf createprocedure ::= CREATE [ OR REPLACE ] PROCEDURE subprogramname ( [ argdeclwith_dflt [ , ... ] ] ) { unalterableprocattribute | alterablefnandprocattribute } [ ... ] argdeclwithdflt ::= argdecl [ { DEFAULT | = } expression ] argdecl ::= [ argname ] [ argmode ] argtype subprogramsignature ::= argdecl [ , ... ] unalterableprocattribute ::= [ LANGUAGE lang_name | AS implementation_definition ] lang_name ::= SQL | PLPGSQL | C implementationdefinition ::= ' sqlstmt_list ' | ' plpgsqlblockstmt ' | ' objfile ' [ , ' linksymbol ' ] sqlstmtlist ::= sqlstmt ; [ sqlstmt ... ] alterablefnandprocattribute ::= SET configuration_parameter { TO value | = value | FROM CURRENT } | RESET configuration_parameter | RESET ALL | [ EXTERNAL ] SECURITY { INVOKER | DEFINER } ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: pull_request_template.md

<!-- Please explain the changes you've made. --> <!-- We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation. --> Please reference the issue this PR will close: #[issue number] Please make sure you've completed the relevant tasks for this PR, out of the following list: [ ] Code compiles correctly [ ] Created/updated tests [ ] Unit tests passing [ ] End-to-end tests passing [ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number] [ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number] [ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc.5x.md

layout: release date: 2022-06-16 tag: v0.6.0-rc.5x language: en [Server] Fix error code conflicts @gr455 (#5626) Allow provider to be set via query parameter @sudo-NithishKarthik (#5627) Fix failing save context for incluster @Revolyssup (#5601) [dde] UI Change to adapt to the exposed server version @sudo-NithishKarthik (#5596) fix: Service mesh provisioning @sudo-NithishKarthik (#5595) exposed meshery server version in dde @warunicorn19 (#5591) Fix panic @Revolyssup (#5593) Fix NATS connectivity test @MUzairS15 (#5583) Fix problems with context-switching operation from Header @Abhishek-kumar09 (#5625) Fix: Metrics components not showing up in dashboard @Abhishek-kumar09 (#5624) Fix Event Streams in Meshery Notification Center @Abhishek-kumar09 (#5621) lifecycle minor bug fix with no adapter @Abhishek-kumar09 (#5620) Bug fixes @MUzairS15 (#5611) [Fix] Lifecylce Page Fixes @Abhishek-kumar09 (#5614) Bump eslint-plugin-react from 7.29.4 to 7.30.0 in /provider-ui @dependabot (#5580) Improve UI @MUzairS15 (#5602) Bump @babel/eslint-parser from 7.17.0 to 7.18.2 in /ui @dependabot (#5555) Multi context refactor @Revolyssup (#5528) Ci/marioarriaga92/5592 fix cypress v10 legacy config file error @MarioArriaga92 (#5597) [UI] Pattern file bug fixes @Chadha93 (#5587) [UI] Settings button style fix for lifecycle @Chadha93 (#5588) material-ui/core from 4.12.3 to 4.12.4 @Harshit-Dandriyal (#5585) [UI] Pattern file bug fixes @Chadha93 (#5587) Fix golangci-lint failures @haanhvu (#5612) Bump eslint-plugin-react from 7.29.4 to 7.30.0 in /provider-ui @dependabot (#5580) [Lifecycle] Remove CPX from default config @leecalcote (#5604) Bump @babel/eslint-parser from 7.17.0 to 7.18.2 in /ui @dependabot (#5555) Bump google.golang.org/grpc from 1.46.0 to 1.47.0 @dependabot (#5560) [Doc] Add troubleshooting steps for Service Mesh installation @MUzairS15 (#5616) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @MUzairS15, @MarioArriaga92, @Revolyssup, @dependabot, @dependabot[bot], @gr455, @haanhvu, @l5io, @leecalcote, @sudo-NithishKarthik, @warunicorn19 and Nithish