cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v22.7.6.74-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Add setting to disable limit on kafkanumconsumers. Closes . (). Backported in : Fix memory safety issues with functions `encrypt` and `contingency` if Array of Nullable is used as an argument. This fixes . (). Backported in : Add `source` field to deb packages, update `nfpm`. (). Backported in : Fix unused unknown columns introduced by WITH statement. This fixes . (). Backported in : - Fix crash while parsing values of type `Object` that contains arrays of variadic dimension. (). Backported in : During insertion of a new query to the `ProcessList` allocations happen. If we reach the memory limit during these allocations we can not use `OvercommitTracker`, because `ProcessList::mutex` is already acquired. Fixes . (). Backported in : In it was reported that the `host_regexp` functionality was not working properly with a name to address resolution in `/etc/hosts`. It's fixed. (). Backported in : Fix access rights for `DESCRIBE TABLE url()` and some other `DESCRIBE TABLE <table_function>()`. (). Backported in : Fix possible segfaults, use-heap-after-free and memory leak in aggregate function combinators. Closes . (). Backported in : Queries with `OFFSET` clause in subquery and `WHERE` clause in outer query might return incorrect result, it's fixed. Fixes . (). Backported in : Fix incorrect logical error `Expected relative path` in disk object storage. Related to . (). Backported in : Add column type check before UUID insertion in MsgPack format. (). Backported in : Malicious data in Native format might cause a crash. (). Backported in : The aggregate function `categorialInformationValue` was having incorrectly defined properties, which might cause a null pointer dereferencing at runtime. This closes . (). Backported in : Writing data in Apache `ORC` format might lead to a buffer overrun. (). Backported in : Queries with `ORDER BY` and `1500 <= LIMIT <= maxblocksize` could return incorrect result with missing rows from top. Fixes . (). Backported in : Fix possible `pipeline stuck` exception for queries with `OFFSET`. The error was found with `enableoptimizepredicate_expression = 0` and always false condition in `WHERE`. Fixes . (). Backported in : Fix possible crash in `SELECT` from `Merge` table with enabled `optimizemonotonousfunctionsinorder_by` setting. Fixes . (). use ROBOTCLICKHOUSECOMMIT_TOKEN for create-pull-request (). use input token instead of env var (). Migrate artifactory (). CaresPTRResolver small safety improvement (). Docker server version (). Download ccache from release PRs for backports (). Increase open files limit (). Remove `-WithTerminatingZero` methods (). Remove trash from Field (). Mask some information in logs. (). Build latest tags ONLY from master branch (). Fix the typo preventing building latest images (). Revert "ColumnVector: optimize UInt8 index with AVX512VBMI ()" ().
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.45.md

layout: release date: 2021-08-10 tag: v0.5.45 [UI]Fixed Notification Card Collapse behavior @NikhilSharma03 (#3835) [mesheryctl] Added `-c` flag into `system view` command @afzal442 (#3813) Refactor Patterns and add some features @utkarsh-pro (#3805) [WIP] Updating operator docs @metonymic-smokey (#3817) Thank you to our contributors for making this release possible: @NikhilSharma03, @afzal442, @leecalcote, @metonymic-smokey, @navendu-pottekkat, @sudo-NithishKarthik and @utkarsh-pro
Project: SPIFFE (Provisioning / Key Management)
File: SUNIL_RAVIPATI.md

Sunil Ravipati leads SPIFFE/SPIRE integration efforts at Carelon (formerly Anthem). He has participated in the SPIFFE community for over 4 years and would be an excellent member of the steering committee. GitHub Handle: @ai2017 LinkedIn Profile: https://www.linkedin.com/in/sunilravipati/ Current Affiliation: Carelon (formerly Anthem)
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.174.md

layout: release date: 2023-11-10 tag: v0.6.174 [chore] bump meshkit to v0.6.83 @theBeginner86 (#9338) [Server] Fix K8S subscription repeated reinitialization issue @MUzairS15 (#9336) [Extensions] Enhance Meshery Docker Extension UI @senali-d (#9323) fix go.sum issue arisen due to conflicts @MUzairS15 (#9326) Upgrade `meshkit` which also fixes comp generation. @MUzairS15 (#9324) removed requirements for k8s connections @EraKin575 (#8854) [pattern] Support for pattern_id in Deploy handler @theBeginner86 (#9334) [UI] Add Formatted Kubernetes metadata to connections @aabidsofi19 (#9321) [UI] Fix Registry Treeview @aabidsofi19 (#9331) Fix RJSF form expanding on selecting multiple technologies in info modal @Yashsharma1911 (#9266) Fix contrast issue @ptdatta (#9328) Bump react-relay from 14.1.0 to 16.0.0 in /ui @dependabot (#9268) Update meshmodel-generators.yml @Jougan-0 (#9327) Generator @Jougan-0 (#9309) Bump react-relay from 14.1.0 to 16.0.0 in /ui @dependabot (#9268) Bump github.com/go-errors/errors from 1.4.2 to 1.5.1 @dependabot (#9270) Bump google.golang.org/api from 0.143.0 to 0.149.0 in /scripts/component_generation @dependabot (#9275) Thank you to our contributors for making this release possible: @EraKin575, @Jougan-0, @MUzairS15, @Yashsharma1911, @aabidsofi19, @dependabot, @dependabot[bot], @leecalcote, @ptdatta, @senali-d and @theBeginner86
Project: ClickHouse (App Definition and Development / Database)
File: v21.6.2.7-prestable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Use old modulo function version when used in partition key. Closes . (). Backported in : Set `max_threads = 1` to fix mutation fail of StorageMemory. Closes . (). Backported in : Allow empty HTTP headers. Fixes . (). Backported in : Fixed a bug in moving Materialized View from Ordinary to Atomic database (`RENAME TABLE` query). Now inner table is moved to new database together with Materialized View. Fixes . (). Backported in : Fix drop partition with intersect fake parts. In rare cases there might be parts with mutation version greater than current block number. (). Backported in : Fix incorrect monotonicity of toWeek function. This fixes . This bug was introduced in https://github.com/ClickHouse/ClickHouse/pull/5212 , and was exposed later by smarter partition pruner. (). Backported in : Fixed the behavior when query `SYSTEM RESTART REPLICA` or `SYSTEM SYNC REPLICA` is being processed infinitely. This was detected on server with extremely little amount of RAM. (). Backported in : Fix usage of tuples in `CREATE .. AS SELECT` queries. (). Backported in : Enable reading of subcolumns for distributed tables. (). Use memmove in PODArray::insert to handle memory overlapping. (). Fix cli argument in clickhouse-server.init (). Fix several cases in cast operator ().
Project: Beam (App Definition and Development / Streaming & Messaging)
File: scala.md

type: languages title: "Apache Beam Scala SDK" <!-- 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. --> The official SDK for writing Beam Pipelines in Scala is . Scio is a Scala API for Apache Beam and Google Cloud Dataflow inspired by Apache Spark and Scalding. Scio aims to be a thin wrapper on top of Beam while offering idiomatic Scala style API. Learn more about Scio .
Project: KICS (Provisioning / Security & Compliance)
File: 4bd21e68-38c1-4d58-acdc-6a14b203237f.md

title: DynamoDB Table Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4bd21e68-38c1-4d58-acdc-6a14b203237f Query name: DynamoDB Table Not Encrypted Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS DynamoDB Tables should have server-side encryption<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="18" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: TableName: my-table AttributeDefinitions: AttributeName: id AttributeType: N AttributeName: name AttributeType: S KeySchema: AttributeName: id KeyType: HASH ProvisionedThroughput: ReadCapacityUnits: 5 WriteCapacityUnits: 5 SSESpecification: SSEEnabled: false ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="17" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: TableName: my-table AttributeDefinitions: AttributeName: id AttributeType: N AttributeName: name AttributeType: S KeySchema: AttributeName: id KeyType: HASH ProvisionedThroughput: ReadCapacityUnits: 5 WriteCapacityUnits: 5 SSESpecification: SSEType: KMS ``` ```yaml title="Negative test num. 1 - yaml file" Resources: MyDynamoDBTable: Type: AWS::DynamoDB::Table Properties: TableName: my-table AttributeDefinitions: AttributeName: id AttributeType: N AttributeName: name AttributeType: S KeySchema: AttributeName: id KeyType: HASH ProvisionedThroughput: ReadCapacityUnits: 5 WriteCapacityUnits: 5 SSESpecification: SSEEnabled: true ```
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Operating System OS: [e.g. iOS] Version [e.g. 22] Additional context Add any other context about the problem here.
Project: KICS (Provisioning / Security & Compliance)
File: 08b81bb3-0985-4023-8602-b606ad81d279.md

title: EC2 Instance Using Default Security Group hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 08b81bb3-0985-4023-8602-b606ad81d279 Query name: EC2 Instance Using Default Security Group Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: EC2 instances should not use default security group(s)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" Resources: MyEC2Instance: Type: AWS::EC2::Instance Properties: ImageId: "ami-79fd7eee" KeyName: "testkey" SecurityGroups: !Ref default BlockDeviceMappings: DeviceName: "/dev/sdm" Ebs: VolumeType: "io1" Iops: "200" DeleteOnTermination: "false" VolumeSize: "20" DeviceName: "/dev/sdk" NoDevice: {} ``` ```json title="Positive test num. 2 - json file" hl_lines="23" { "Resources": { "MyEC2Instance": { "Properties": { "BlockDeviceMappings": [ { "DeviceName": "/dev/sdm", "Ebs": { "DeleteOnTermination": "false", "Iops": "200", "VolumeSize": "20", "VolumeType": "io1" } }, { "DeviceName": "/dev/sdk", "NoDevice": {} } ], "ImageId": "ami-79fd7eee", "KeyName": "testkey", "SecurityGroups": [ "default" ] }, "Type": "AWS::EC2::Instance" } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: MyEC2Instancee: Type: AWS::EC2::Instance Properties: ImageId: "ami-79fd7eee" KeyName: "testkey" SecurityGroups: !Ref my_sg BlockDeviceMappings: DeviceName: "/dev/sdm" Ebs: VolumeType: "io1" Iops: "200" DeleteOnTermination: "false" VolumeSize: "20" DeviceName: "/dev/sdk" NoDevice: {} ``` ```json title="Negative test num. 2 - json file" { "Resources": { "MyEC2Instancee": { "Properties": { "BlockDeviceMappings": [ { "DeviceName": "/dev/sdm", "Ebs": { "DeleteOnTermination": "false", "Iops": "200", "VolumeSize": "20", "VolumeType": "io1" } }, { "DeviceName": "/dev/sdk", "NoDevice": {} } ], "ImageId": "ami-79fd7eee", "KeyName": "testkey", "SecurityGroups": [ "my_sg" ] }, "Type": "AWS::EC2::Instance" } } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_firewalls.md

+++ title = "googlecomputefirewalls resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputefirewalls" identifier = "inspec/resources/gcp/googlecomputefirewalls.md googlecomputefirewalls resource" parent = "inspec/resources/gcp" +++ A `googlecomputefirewalls` is used to test a Google Firewall resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputefirewalls(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } its('firewall_names') { should include 'inspec-gcp-firewall' } its('firewall_directions') { should include 'INGRESS' } end ``` describe googlecomputefirewalls(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end describe googlecomputefirewalls(project: 'chef-inspec-gcp') do its('firewall_names') { should include "my-app-firewall-rule" } end describe googlecomputefirewalls(project: 'chef-inspec-gcp') do its('firewallnames') { shouldnot include "default-allow-ssh" } end describe googlecomputefirewalls(project: 'chef-inspec-gcp').where(firewall_direction: 'INGRESS') do it { should_not exist } end Properties that can be accessed from the `googlecomputefirewalls` resource: See the resource for more information. `alloweds` : an array of `googlecomputefirewall` allowed `creation_timestamps` : an array of `googlecomputefirewall` creation_timestamp `denieds` : an array of `googlecomputefirewall` denied `descriptions` : an array of `googlecomputefirewall` description `destination_ranges` : an array of `googlecomputefirewall` destination_ranges `firewall_directions` : an array of `googlecomputefirewall` direction `disableds` : an array of `googlecomputefirewall` disabled `log_configs` : an array of `googlecomputefirewall` log_config `firewall_ids` : an array of `googlecomputefirewall` id `firewall_names` : an array of `googlecomputefirewall` name `networks` : an array of `googlecomputefirewall` network `priorities` : an array of `googlecomputefirewall` priority `source_ranges` : an array of `googlecomputefirewall` source_ranges `sourceserviceaccounts` : an array of `googlecomputefirewall` sourceserviceaccounts `source_tags` : an array of `googlecomputefirewall` source_tags `targetserviceaccounts` : an array of `googlecomputefirewall` targetserviceaccounts `target_tags` : an array of `googlecomputefirewall` target_tags This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Tetragon (Provisioning / Security & Compliance)
File: new-page-template.md

title: "Long Page Title" linkTitle: "Short Nav Title" weight: 100 description: >- Page description for heading and indexes. Edit this template to create your new page. Give it a good name, ending in `.md` - e.g. `getting-started.md` Edit the "front matter" section at the top of the page (weight controls how its ordered amongst other pages in the same directory; lowest number first). Add a good commit message at the bottom of the page (<80 characters; use the extended description field for more detail). Create a new branch so you can preview your new file and request a review via Pull Request.
Project: YDB (App Definition and Development / Database)
File: agg_list.md

Get all column values as a list. When combined with `DISTINCT`, it returns only distinct values. The optional second parameter sets the maximum number of values to be returned. If you know already that you have few distinct values, use the `AGGREGATELISTDISTINCT` aggregate function to build the same result in memory (that might not be enough for a large number of distinct values). The order of elements in the result list depends on the implementation and can't be set externally. To return an ordered list, sort the result, for example, with . To return a list of multiple values from one line, DO NOT use the `AGGREGATELIST` function several times, but add all the needed values to a container, for example, via or , then pass this container to a single `AGGREGATELIST` call. For example, you can combine it with `DISTINCT` and the function (it's an equivalent of `','.join(list)` in Python) to output to a string all the values found in the column after . Examples ```yql SELECT AGGREGATE_LIST( region ), AGGREGATE_LIST( region, 5 ), AGGREGATE_LIST( DISTINCT region ), AGGREGATELISTDISTINCT( region ), AGGREGATELISTDISTINCT( region, 5 ) FROM users ``` ```yql -- An equivalent of GROUP_CONCAT in MySQL SELECT String::JoinFromList(CAST(AGGREGATE_LIST(region, 2) AS List<String>), ",") FROM users ``` These functions also have a short notation: `AGGLIST` and `AGGLIST_DISTINCT`. {% note alert %} Execution is NOT lazy, so when you use it, be sure that the list has a reasonable size (about a thousand items or less). To stay on the safe side, better use a second optional numeric argument that limits the number of items in the list. {% endnote %}
Project: KICS (Provisioning / Security & Compliance)
File: 99614418-f82b-4852-a9ae-5051402b741c.md

title: MAINTAINER Instruction Being Used hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 99614418-f82b-4852-a9ae-5051402b741c Query name: MAINTAINER Instruction Being Used Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: The MAINTAINER instruction sets the Author field of the generated images. The LABEL instruction is a much more flexible version of this and you should use it instead, as it enables setting any metadata you require, and can be viewed easily<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="4" FROM alpine:3.5 RUN apk add --update py2-pip RUN pip install --upgrade pip MAINTAINER "SvenDowideit@home.org.au" COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM alpine:3.5 RUN apk add --update py2-pip RUN pip install --upgrade pip LABEL maintainer="SvenDowideit@home.org.au" COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] ```
Project: Puppet (Provisioning / Automation & Configuration)
File: unicode.md

Now that Puppet only supports Ruby 1.9+, developers should be aware of how Ruby handles Strings and Regexp objects. Specifically, every instance of these two classes will have an encoding attribute determined in a number of ways. If the source file has an encoding specified in the magic comment at the top, the instance will take on that encoding. Otherwise, the encoding will be determined by the LC\_LANG or LANG environment variables. Otherwise, the encoding will default to ASCII-8BIT In general, please be aware that Ruby regular expressions need to be compatible with the encoding of a string being used to match them. If they are not compatible you can expect to receive an error such as: Encoding::CompatibilityError: incompatible encoding regexp match (ASCII-8BIT regexp with UTF-8 string) In addition, some escape sequences are only valid if the regular expression is marked as an ASCII-8BIT object. If the regular expression is not marked as ASCII-8BIT, you can get an error such as: SyntaxError: (irb):7: invalid multibyte escape: /\xFF/ This error is particularly common when serializing a string to other representations like JSON or YAML. To resolve the problem you can explicitly mark the regular expression as ASCII-8BIT using the /n flag: "a" =~ /\342\230\203/n Finally, any time you're thinking of a string as an array of bytes rather than an array of characters, common when escaping a string, you should work with everything in ASCII-8BIT. Changing the encoding will not change the data itself and allow the Regexp and the String to deal with bytes rather than characters.
Project: RethinkDB (App Definition and Development / Database)
File: STYLE.md

The general rule is: Write code in a manner similar to that around it. This document describes guidelines that people new to the codebase tend not to immediately pick up on. These aren't universal rules (besides the first rule) and situations might require your better judgement. Use `if (...) {`, `while (...) {`, and `switch (...) {`, not `if(...){`, `while(...){`, and `switch(...){`. Use braces. Header files should be included in the following order: Your parent .hpp file (if you are a .cc file), C system headers (`<math.h>`, `<unistd.h>`, etc), Standard C++ headers (`<vector>`, `<algorithm>`, etc), Boost headers, with `"errors.hpp"` included before them, if there are any. Local headers with full paths (`"rdb_protocol/protocol.hpp"`, etc). > Reason: It's always good to have one .cc file include each .hpp file first, so that you know it includes all of its dependencies. The Google Style Guide specifies the C/C++/Local order and we blindly assume there's a reason. errors.hpp defines `BOOSTENABLEASSERT_HANDLER` to make Boost assertion failures get forwarded to the RethinkDB assertion mechanism, so it needs to go before boost headers. Don't use non-const lvalue references, except, perhaps, in return values. > Reason: The entire codebase does things this way. Right now, somebody seeing `foo(bar)` can currently expect `bar` not to be modified. > Exception: `std::swap` and STL-like `swap` methods, perhaps, and other peculiar situations. Don't make fields whose type is a reference type (const or non-const), and don't turn references into pointers in ways that might surprise the caller. > Reason: This makes object lifetime dependencies easier to see (somebody calling `foo(bar)` can assume there's no new restrictions on the lifetime of `bar` -- the code must become `foo(&bar)` which shows that something spooky is happening). > Null pointer dereferences are also easier to track down than use-after-free bugs. (Also, they generally don't happen: a function taking a pointer argument does not imply that it accepts a null pointer value, and this hasn't been a problem.) If your type should not be copied, use the `DISABLE_COPYING` macro to make it non-copyable. > Or declare its copy constructor and assignment operator with `= delete;` yourself. Run (from the src directory) `../scripts/check_style.sh` to see if your code has introduced any of a certain class of style errors. > The include-what-you-use errors exist to make you suffer -- but keeping awareness of this makes efforts to untangle header file dependences a lot less labor-intensive. > Bogus errors can be suppressed with `// NOLINT(specific/category)`. > This script has caught several bugs (mostly race conditions caused by not using reentrant "_r" versions of libc functions).