cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v21.8.13.6-lts.md

sidebar_position: 1 sidebar_label: 2022 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 crash with empty result on odbc query. Closes . (). Backported in : Fix crash when function `dictGet` with type is used for dictionary attribute when type is `Nullable`. Fixes . (). Backported in : Fix a bug about function transform with decimal args. (). Backported in : - Change configuration path from `keeperserver.sessiontimeoutms` to `keeperserver.coordinationsettings.sessiontimeoutms` when constructing a `KeeperTCPHandler` - Same with `operationtimeout`. (). Backported in : Some `GET_PART` entry might hang in replication queue if part is lost on all replicas and there are no other parts in the same partition. It's fixed in cases when partition key contains only columns of integer types or `Date. (). Backported in : Fixed `Directory ... already exists and is not empty` error when detaching part. (). 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. (). Backported in : XML dictionaries identifiers, used in table create query, can be qualified to `default_database` during upgrade to newer version. Closes . (). Backported in : Some replication queue entries might hang for `temporarydirectorieslifetime` (1 day by default) with `Directory tmpmerge<part_name>` or `Part ... (state Deleting) already exists, but it will be deleted soon` or similar error. It's fixed. Fixes . (). Backported in : Fixed crash with SIGFPE in aggregate function `avgWeighted` with `Decimal` argument. Fixes . (). Backported in : Fix possible exception at RabbitMQ storage startup by delaying channel creation. (). Backported in : fix crash when used fuzzBits with multiply same FixedString, Close . (). Backported in : Fix possible crash (or incorrect result) in case of `LowCardinality` arguments of window function. Fixes . (). NO CL ENTRY: 'fix json error after downgrade'. (). Fix data race in ProtobufSchemas (). Column default dictGet identifier fix (). Fix possible Pipeline stuck in case of StrictResize processor. (). Fix arraySlice with null args. (). 21.8 ExternalDictionariesLoader fix build (). Fix queries with hasColumnInTable constant condition and non existing column (). 21.8 ExternalDictionariesLoader fix (). Merge (). Merge ().
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.7.62-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Set `backgroundfetchespool_size` to 8 that is better for production usage with frequent small insertions or slow ZooKeeper cluster. (). Backported in : Raised the threshold on max number of matches in result of the function `extractAllGroupsHorizontal`. (). Backported in : Fixed a bug with unlimited wait for auxiliary AWS requests. (). Backported in : Fix error `Cannot find column in ActionsDAG result` which may happen if subquery uses `untuple`. Fixes . (). Backported in : Remove non-essential details from suggestions in clickhouse-client. This closes . (). Backported in : Some values were formatted with alignment in center in table cells in `Markdown` format. Not anymore. (). LibraryDictionarySource fix possible leak ().
Project: KICS (Provisioning / Security & Compliance)
File: 3ae83918-7ec7-4cb8-80db-b91ef0f94002.md

title: Security Group Unrestricted Access To RDP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3ae83918-7ec7-4cb8-80db-b91ef0f94002 Query name: Security Group Unrestricted Access To RDP Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Security Groups does not allow 0.0.0.0/0 for rdp (port:3389)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="15" Resources: Ec2Instance: Type: 'AWS::EC2::Instance' Properties: SecurityGroups: !Ref InstanceSecurityGroup KeyName: mykey ImageId: '' InstanceSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: Allow http to client host VpcId: Ref: myVPC SecurityGroupIngress: IpProtocol: tcp FromPort: 3389 ToPort: 3389 CidrIp: 0.0.0.0/0 SecurityGroupEgress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 0.0.0.0/0 ``` ```json title="Positive test num. 2 - json file" hl_lines="10" { "Resources": { "InstanceSecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "GroupDescription": "Allow http to client host", "VpcId": { "Ref": "myVPC" }, "SecurityGroupIngress": [ { "IpProtocol": "tcp", "FromPort": 3389, "ToPort": 3389, "CidrIp": "0.0.0.0/0" } ], "SecurityGroupEgress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "0.0.0.0/0" } ] } }, "Ec2Instance": { "Type": "AWS::EC2::Instance", "Properties": { "KeyName": "mykey", "ImageId": "", "SecurityGroups": [ "InstanceSecurityGroup" ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: Ec2Instance: Type: 'AWS::EC2::Instance' Properties: SecurityGroups: !Ref InstanceSecurityGroup KeyName: mykey ImageId: '' InstanceSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: Allow http to client host VpcId: Ref: myVPC SecurityGroupIngress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 127.0.0.1/32 SecurityGroupEgress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 127.0.0.1/33 ``` ```json title="Negative test num. 2 - json file" { "Resources": { "Ec2Instance": { "Type": "AWS::EC2::Instance", "Properties": { "SecurityGroups": [ "InstanceSecurityGroup" ], "KeyName": "mykey", "ImageId": "" } }, "InstanceSecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "SecurityGroupEgress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "127.0.0.1/33" } ], "GroupDescription": "Allow http to client host", "VpcId": { "Ref": "myVPC" }, "SecurityGroupIngress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "127.0.0.1/32" } ] } } } } ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_restart.md

<!MARKERGENSTART--> Restart service containers | Name | Type | Default | Description | |:|:|:--|:--| | `--dry-run` | | | Execute command in dry run mode | | `--no-deps` | | | Don't restart dependent services | | `-t`, `--timeout` | `int` | `0` | Specify a shutdown timeout in seconds | <!MARKERGENEND--> Restarts all stopped and running services, or the specified services only. If you make changes to your `compose.yml` configuration, these changes are not reflected after running this command. For example, changes to environment variables (which are added after a container is built, but before the container's command is executed) are not updated after restarting. If you are looking to configure a service's restart policy, refer to or .
Project: ClickHouse (App Definition and Development / Database)
File: v24.1.7.18-stable.md

sidebar_position: 1 sidebar_label: 2024 Fix deadlock in parallel parsing when lots of rows are skipped due to errors (). Fixmaxquerysizeforkqlcompound_operator: (). Fix crash with different allowexperimentalanalyzer value in subqueries (). Fix Keeper reconfig for standalone binary (). Backported in : Debug and fix markreleaseready. (). Backported in : Just a preparation for the merge queue support. (). Backported in : ... (). Cancel PipelineExecutor properly in case of exception in spawnThreads ().
Project: Vitess (App Definition and Development / Database)
File: GUIDING_PRINCIPLES.md

The Vitess project operates under the guiding principles described below. The is responsible for upholding these principles and keeping this document updated with any changes. To be the most performant, scalable, and available NewSQL storage system in the Cloud. Vitess can currently run on bare-metal or in the cloud. However, the trend is clear that applications are moving to the cloud. For the foreseeable future, we should continue to support the ability to run on bare-metal, because it will facilitate migration to the cloud. The Vitess architecture is generic enough to accommodate any other RDBMS in the future. However, Vitess currently runs on MySQL and has many features that provide compatibility with it. Vitess should remain focused on MySQL until all frictions are removed for those who wish to migrate from MySQL to Vitess. The vision of the Vitess project is to serve the software community by gaining popularity and adoption. Vitess is driven by high technical standards, and these must be maintained. It is also important to take into account that multiple humans are participating in the project, and we must ensure that we all treat each other well. In this respect, we will honor the following values: Technical excellence Innovation and creativity Fairness and equality Diversity Inclusiveness Openness Adherence to the
Project: Vitess (App Definition and Development / Database)
File: pull_request_template.md

<!-- Thank you for your contribution to the Vitess project. How to contribute: https://vitess.io/docs/contributing/ Please first make sure there is an open Issue to discuss the feature/fix suggested in this PR. If this is a new feature, please mark the Issue as "RFC". --> <!-- if this PR is Work in Progress please create it as a Draft Pull Request --> <!-- A few sentences describing the overall goals of the pull request's commits. --> <!-- If this is a bug fix and you think the fix should be backported, please write so. --> <!-- List related issues and pull requests. If this PR fixes an issue, please add it using Fixes #???? --> [ ] "Backport to:" labels have been added if this change should be back-ported to release branches [ ] If this change is to be back-ported to previous releases, a justification is included in the PR description [ ] Tests were added or are not required [ ] Did the new or modified tests pass consistently locally and on CI? [ ] Documentation was added or is not required <!-- Notes regarding deployment of the contained body of work. These should note any db migrations, etc. -->
Project: ArangoDB (App Definition and Development / Database)
File: example.md

+++ title = "Example C++ function" description = "" weight = 20 +++ Let us start with a simple C++ function which we wish to make available to C code: {{% snippet "cpp_api.cpp" "function" %}} As the alias `statusresult<sizet>` defaults the erased type to the alias `system_code`, the `tostring()` function returns (in concrete types) `basicresult<sizet, statuscode<erased<intptr_t>>>`. The standard Outcome function referenced is documented at {{% api "std::errorcode errorfromexception(std::exceptionptr &&ep = std::currentexception(), std::errorcode notmatched = std::makeerrorcode(std::errc::resourceunavailabletryagain)) noexcept" %}}. The proposed `<system_error2>` reference library implementation provides an identically named function taking similar parameters, but it returns a `outcomee::systemcode` (`statuscode<erased<intptrt>>`) instead of a `std::error_code`.
Project: Neo4j (App Definition and Development / Database)
File: CONTRIBUTING.md

At , we develop our software in the open at GitHub. This provides transparency for you, our users, and allows you to fork the software to make your own additions and enhancements. We also provide areas specifically for community contributions, in particular the space. There's an active and where we work directly with the community. If you're not already a member, sign up! We love our community and wouldn't be where we are without you. Where you raise an issue depends largely on the nature of the problem. Firstly, if you are an Enterprise customer, you might want to head over to our . There are plenty of public channels available too, though. If you simply want to get started or have a question on how to use a particular feature, drop a line to the , ask a question in , or us. If you think you might have hit a bug in our software (it happens occasionally!) or you have specific feature request then use the issue feature on the relevant GitHub repository. Check first though as someone else may have already raised something similar. also hosts a ton of questions and might already have a discussion around your problem. Make sure you have a look there too. Include as much information as you can in any request you make: Which versions of our products are you using? Which language (and which version of that language) are you developing with? What operating system are you on? Are you working with a cluster or on a single machine? What code are you running? What errors are you seeing? What solutions have you tried already? If you want to contribute a pull request, we have a little bit of process you'll need to follow: Do all your work in a personal fork of the original repository , don't merge (we prefer to keep our history clean) Create a branch (with a useful name) for your contribution Make sure you're familiar with the appropriate coding style (this varies by language so ask if you're in doubt) Include unit tests if appropriate (obviously not necessary for documentation changes) Take a moment to read and sign our We can't guarantee that we'll accept pull requests and may ask you to make some changes before they go in. Occasionally, we might also have logistical, commercial, or legal reasons why we can't accept your work but we'll try to find an alternative way for you to contribute in that case. Remember that many community members have become regular contributors and some are now even Neo employees! If you have an idea for a new tool or library, start by talking to other people in the community. Chances are that someone has a similar idea or may have already started working on it. The best software comes from getting like minds together to solve a problem. And we'll do our best to help you promote and co-ordinate your Neo ecosystem projects. If you want to find out more about how you can contribute, head over to our website for .
Project: Vault (Provisioning / Key Management)
File: ISSUE_TEMPLATE.md

<!-- Please reserve GitHub issues for bug reports and feature requests. For questions, the best place to get answers is on our , as they will get more visibility from experienced users than the issue tracker. Please note: We take Vault's security and our users' trust very seriously. If you believe you have found a security issue in Vault, please responsibly disclose by contacting us at security@hashicorp.com. Our PGP key is available at . --> <!-- Uncomment this section if this is a feature request. Include or exclude other sections as deemed appropriate. Feature Request: --> Environment: <!-- The version can be retrieved with `vault version`. --> Vault Version: Operating System/Architecture: Vault Config File: <!-- Configuration file used for the vault server. --> ```hcl ``` Startup Log Output: <!-- Logs from vault's output on startup, if available. --> ```text ``` Expected Behavior: <!-- What should have happened? --> Actual Behavior: <!-- What actually happened? --> Steps to Reproduce: <!-- List the steps required to reproduce the issue. --> Important Factoids: <!-- Describe any atypical environment setup, if any. --> References: <!-- Link to any references, such as GitHub issues or pull requests. -->
Project: StarRocks (App Definition and Development / Database)
File: sqrt.md

displayed_sidebar: "English" Calculates the square root of a value. dsqrt is same as sqrt. ```Haskell DOUBLE SQRT(DOUBLE x); DOUBLE DSQRT(DOUBLE x); ``` `x`: You can specify only a numeric value. This function converts the numeric value into a DOUBLE value before calculation. Returns a value of the DOUBLE data type. If you specify a non-numeric value, this function returns `NULL`. ```Plain mysql> select sqrt(3.14); +-+ | sqrt(3.14) | +-+ | 1.772004514666935 | +-+ 1 row in set (0.01 sec) mysql> select dsqrt(3.14); +-+ | dsqrt(3.14) | +-+ | 1.772004514666935 | +-+ ```
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: DOCUMENTATION.md

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. SparkR documentation is generated by using in-source comments and annotated by using . After making changes to the documentation and generating man pages, you can run the following from an R console in the SparkR home directory ```R library(devtools) devtools::document(pkg="./pkg", roclets=c("rd")) ``` You can verify if your changes are good by running R CMD check pkg/
Project: Meshery (Provisioning / Automation & Configuration)
File: cert-manager-crds.md

layout: integration title: Cert Manager Crds subtitle: Collaborative and visual infrastructure as code for Cert Manager Crds image: /assets/img/integrations/cert-manager-crds/icons/color/cert-manager-crds-color.svg permalink: extensibility/integrations/cert-manager-crds docURL: https://docs.meshery.io/extensibility/integrations/cert-manager-crds description: integrations-category: Security & Compliance integrations-subcategory: Security & Compliance registrant: Artifact Hub components: featureList: [ "Simplifies the process of obtaining, renewing and using those certificates.", "Supports issuing certificates from a variety of sources.", "Ensures certificates remain valid and up to date." ] howItWorks: "Cloud native certificate management" howItWorksDetails: "X.509 certificate management for Kubernetes and OpenShift" language: en list: include type: extensibility category: integrations
Project: Beam (App Definition and Development / Streaming & Messaging)
File: feature-comparison.md

type: languages title: "Beam Java 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. -->
Project: OAuth2 Proxy (Provisioning / Key Management)
File: contribution.md

id: contribution title: Contribution Guide We track bugs and issues using Github. If you find a bug, please open an Issue. When opening an Issue or Pull Request please follow the preconfigured template and take special note of the checkboxes. If you want to fix a bug, add a new feature or extend existing functionality, please create a fork, create a feature branch and open a PR back to this repo. Please mention open bug issue number(s) within your PR if applicable. We suggest using with the official extension. This project is currently still using go 1.19. You can follow the installation guide for go And you can find go version 1.19 in the archived section Clone your fork, create a feature branch and update the depedencies to get started. ```bash git clone git@github.com:<YOUR_FORK>/oauth2-proxy cd oauth2-proxy git branch feature/<BRANCH_NAME> git push --set-upstream origin feature/<BRANCH_NAME> go mod download ``` For starting oauth2-proxy locally open the debugging tab and create the `launch.json` and select `Go: Launch Package`. ```json { "version": "0.2.0", "configurations": [ { "name": "Launch OAuth2-Proxy with Dex", "type": "go", "request": "launch", "mode": "auto", "program": "${workspaceFolder}", "args": [ "--config", // The following configuration contains settings for a locally deployed // upstream and dex as an idetity provider "contrib/local-environment/oauth2-proxy.cfg" ] }, { "name": "Launch OAuth2-Proxy with Keycloak", "type": "go", "request": "launch", "mode": "auto", "program": "${workspaceFolder}", "args": [ "--config", // The following configuration contains settings for a locally deployed // upstream and keycloak as an idetity provider "contrib/local-environment/oauth2-proxy-keycloak.cfg" ] } ] } ``` Before you can start your local version of oauth2-proxy, you will have to use the provided docker compose files to start a local upstream service and identity provider. We suggest using as your upstream for testing as it allows for request and response introspection of all things HTTP. Open a terminal and switch to the `contrib/local-environment` directory. Dex as your IdP: `docker compose -f docker-compose.yaml up dex etcd httpbin` Keycloak as your IdP: `docker compose -f docker-compose-keycloak.yaml up keycloak httpbin` The username for both is `admin@example.com` and password is `password`. Start oauth2-proxy from the debug tab and open http://oauth2-proxy.localtest.me:4180/ for testing.
Project: KICS (Provisioning / Security & Compliance)
File: 610e266e-6c12-4bca-9925-1ed0cd29742b.md

title: Security Opt Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 610e266e-6c12-4bca-9925-1ed0cd29742b Query name: Security Opt Not Set Platform: DockerCompose Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: Attribute 'security_opt' should be defined.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" version: "3.9" services: webapp: build: context: ./ dockerfile: Dockerfile-alternate args: buildno: 1 ports: "8080:8080" "3000:3000" ``` ```yaml title="Negative test num. 1 - yaml file" version: "3.9" services: webapp: build: context: ./ dockerfile: Dockerfile-alternate args: buildno: 1 ports: "8080:8080" "3000:3000" security_opt: apparmor:unconfined ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-network-rm.1.md

% podman-network-rm 1 podman\-network\-rm - Remove one or more networks podman network rm [options] [network...] Delete one or more Podman networks. The `force` option removes all containers that use the named network. If the container is running, the container is stopped and removed. Seconds to wait before forcibly stopping the running containers that are using the specified network. The --force option must be specified to use the --time option. Use -1 for infinite wait. Delete specified network: ``` Deleted: podman9 ``` Delete specified network and all containers associated with the network: ``` Deleted: fred ``` 0 All specified networks removed 1 One of the specified networks did not exist, and no other failures 2 The network is in use by a container or a Pod 125 The command fails for any other reason , August 2019, Originally compiled by Brent Baude <bbaude@redhat.com>