cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: update-go-version.md

A quick guide to update KubeVirt's Go version. To update the Go version we need to update the builder image so that it uses the new version, push it to the registry and finally let KubeVirt use the new builder image. In addition, have to be updated if the current version does not support the target Go version. Change the `GIMMEGOVERSION` in the to the desired Go version. Rebuild the builder image by executing `make builder-build`. Publish new builder image with `make builder-publish`. Note: Proper access rights are required in order to publish builder image. When publish is finished, the builder image tag will be presented. For instance, if the output of `make builder-publish` is: ```shell 2103210933-9be558add-amd64: digest: sha256:cc83534b5d99da35643f8a2a87830b0dabcb4f130c1db181a835dc8def09174b size: 3271 TMP_IMAGES=' quay.io/kubevirt/builder:2103210933-9be558add-amd64' export DOCKERCLIEXPERIMENTAL=enabled DOCKERCLIEXPERIMENTAL=enabled docker manifest create --amend quay.io/kubevirt/builder:2103210933-9be558add quay.io/kubevirt/builder:2103210933-9be558add-amd64 Created manifest list quay.io/kubevirt/builder:2103210933-9be558add docker manifest push quay.io/kubevirt/builder:2103210933-9be558add sha256:d828eb647e7ef3115f39ff4cb2d5d41da39b4134056e429be16c3a019b521957 cleanup rm manifests/ -rf ``` The image tag is `2103210933-9be558add` Change `KUBEVIRTBUILDERIMAGE` variable in to the tag from the previous step. In change `go_version` to the desired Go version. Should look similar to: ```shell goregistertoolchains( go_version = "1.14.14", nogo = "@//:nogo_vet", ) ``` In find current Bazel release's SHA ID which can be found under `iobazelrules_go`. Should look similar to: ```shell http_archive( name = "iobazelrules_go", sha256 = "52d0a57ea12139d727883c2fef03597970b89f2cc2a05722c42d1d7d41ec065b", urls = [ ... ], ) ``` Visit and check whether the current Bazel version supports the new Go version. If it is not supported, replace the `iobazelrules_go` definition with the one provided in Bazel's page.
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-05-2022-02-42-10_103cc75f.md

timestamp: "2022-10-05 02:42:17 UTC Wed" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.10" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: ClickHouse (App Definition and Development / Database)
File: row_policies.md

slug: /en/operations/system-tables/row_policies Contains filters for one particular table, as well as a list of roles and/or users which should use this row policy. Columns: `name` () Name of a row policy. `short_name` () Short name of a row policy. Names of row policies are compound, for example: myfilter ON mydb.mytable. Here "myfilter ON mydb.mytable" is the name of the row policy, "myfilter" is it's short name. `database` () Database name. `table` () Table name. Empty if policy for database. `id` () Row policy ID. `storage` () Name of the directory where the row policy is stored. `select_filter` (()) Condition which is used to filter rows. `is_restrictive` () Shows whether the row policy restricts access to rows, see . Value: `0` The row policy is defined with `AS PERMISSIVE` clause. `1` The row policy is defined with `AS RESTRICTIVE` clause. `applytoall` () Shows that the row policies set for all roles and/or users. `applytolist` (()) List of the roles and/or users to which the row policies is applied. `applytoexcept` (()) The row policies is applied to all roles and/or users excepting of the listed ones.
Project: Athenz (Provisioning / Key Management)
File: SECURITY.md

| Version | Supported | | - | | | 1.10.x | :whitecheckmark: | | 1.9.x | :whitecheckmark: | | < 1.9.0 | :x: | If you've found a vulnerability or a potential vulnerability in Athenz, please let us know at cncf-athenz-maintainers@lists.cncf.io. We'll send a confirmation email to acknowledge your report, and we'll send an additional email when we've identified the issue positively or negatively.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-having.md

layout: global title: HAVING Clause displayTitle: HAVING 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. The `HAVING` clause is used to filter the results produced by `GROUP BY` based on the specified condition. It is often used in conjunction with a clause. ```sql HAVING boolean_expression ``` boolean_expression* Specifies any expression that evaluates to a result type `boolean`. Two or more expressions may be combined together using the logical operators ( `AND`, `OR` ). Note The expressions specified in the `HAVING` clause can only refer to: Constants Expressions that appear in GROUP BY Aggregate functions ```sql CREATE TABLE dealer (id INT, city STRING, car_model STRING, quantity INT); INSERT INTO dealer VALUES (100, 'Fremont', 'Honda Civic', 10), (100, 'Fremont', 'Honda Accord', 15), (100, 'Fremont', 'Honda CRV', 7), (200, 'Dublin', 'Honda Civic', 20), (200, 'Dublin', 'Honda Accord', 10), (200, 'Dublin', 'Honda CRV', 3), (300, 'San Jose', 'Honda Civic', 5), (300, 'San Jose', 'Honda Accord', 8); -- `HAVING` clause referring to column in `GROUP BY`. SELECT city, sum(quantity) AS sum FROM dealer GROUP BY city HAVING city = 'Fremont'; +-++ | city|sum| +-++ |Fremont| 32| +-++ -- `HAVING` clause referring to aggregate function. SELECT city, sum(quantity) AS sum FROM dealer GROUP BY city HAVING sum(quantity) > 15; +-++ | city|sum| +-++ | Dublin| 33| |Fremont| 32| +-++ -- `HAVING` clause referring to aggregate function by its alias. SELECT city, sum(quantity) AS sum FROM dealer GROUP BY city HAVING sum > 15; +-++ | city|sum| +-++ | Dublin| 33| |Fremont| 32| +-++ -- `HAVING` clause referring to a different aggregate function than what is present in -- `SELECT` list. SELECT city, sum(quantity) AS sum FROM dealer GROUP BY city HAVING max(quantity) > 15; +++ | city|sum| +++ |Dublin| 33| +++ -- `HAVING` clause referring to constant expression. SELECT city, sum(quantity) AS sum FROM dealer GROUP BY city HAVING 1 > 0 ORDER BY city; +--++ | city|sum| +--++ | Dublin| 33| | Fremont| 32| |San Jose| 13| +--++ -- `HAVING` clause without a `GROUP BY` clause. SELECT sum(quantity) AS sum FROM dealer HAVING sum(quantity) > 10; ++ |sum| ++ | 78| ++ ```
Project: ClickHouse (App Definition and Development / Database)
File: v23.3.14.78-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fix strange additional QEMU logging after , see https://s3.amazonaws.com/clickhouse-test-reports/50078/a4743996ee4f3583884d07bcd6501df0cfdaa346/statelesstestsreleasedatabasereplicated_ (). Backported in : Resource with source code including submodules is built in Darwin special build task. It may be used to build ClickHouse without checkouting submodules. (). Backported in : Enrich `changed_images.json` with the latest tag from master for images that are not changed in the pull request. (). Backported in : We build and upload them for every push, which isn't worth it. (). Fix parameterized view with cte and multiple usage (). Check recursion depth in OptimizedRegularExpression (). Fix lightweight delete after drop of projection (). Fix sorting of sparse columns with large limit (). Fix adding sub-second intervals to DateTime (). Fix: allow IPv6 for bloom filter (). Check for overflow before addition in `analysisOfVariance` function (). reproduce and fix the bug in removeSharedRecursive (). Fix aggregate projections with normalized states (). Fix possible parsing error in WithNames formats with disabled inputformatwithnamesuse_header (). Fix "Invalid number of rows in Chunk" in MaterializedPostgreSQL (). Prevent attaching parts from tables with different projections or indices (). Fix trash optimization (up to a certain extent) (). Fix parsing of arrays in cast operator (). NO CL ENTRY: 'Revert "Backport to 23.3: reproduce and fix the bug in removeSharedRecursive"'. (). Test libunwind changes. (). Refactor CI_CONFIG (). Use pathlib.Path in S3Helper, rewrite build reports, improve small things (). Fixed parameterized_view test after backporting a fix 23.3 (). Update automated commit status comment (). S3 artifacts (). Fix CI skip build and skip tests checks (). Update WebObjectStorage.cpp (). Do not set PR status label (). Get rid of the most of `os.path` stuff (). check if block is empty after async insert retries (). MaterializedPostgreSQL: remove back check (). Remove existing moving/ dir if allowremovestalemovingparts is off ().
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_virtual_networks.md

+++ title = "azurermvirtualnetworks resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermvirtualnetworks" identifier = "inspec/resources/azure/azurermvirtualnetworks.md azurermvirtualnetworks resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurevirtual_networks" >}} Use the `azurermvirtualnetworks` InSpec audit resource to test properties related to virtual networks for a resource group. This resource interacts with version `2018-02-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.1.0 of the inspec-azure resource pack. The `resource_group` must be given as a parameter. describe azurermvirtualnetworks(resource_group: 'MyResourceGroup') do ... end describe azurermvirtualnetworks(resource_group: 'MyResourceGroup') do it { should exist } end `resource_group` describe azurermvirtualnetworks(resource_group: 'MyResourceGroup') do ... end Filters the results to only those that match the given name. describe azurermvirtualnetworks(resource_group: 'MyResourceGroup') .where(name: 'MyVnetName') do it { should exist } end describe azurermvirtualnetworks(resourcegroup: 'MyResourceGroup').where { name.startwith?('prefix') } do it { should exist } end `names` Gives a list of all the virtual network names in the resource group. its('names') { should include('VnetName1', 'VnetName2') } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. describe azurermvirtualnetworks(resource_group: 'MyResourceGroup') do it { should_not exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.4.20-lts.md

sidebar_position: 1 sidebar_label: 2022 - Add `le` method for ClickHouseVersion - Fix autoversion for existing tag - dockerserver now support getting version from tags - Add python unit tests to backport workflow. (). Backported in : Fix usage of quota with asynchronous inserts. (). Backported in : Fix possible loss of subcolumns in type `Object`. (). Backported in : Fix possible `Can't adjust last granule` exception while reading subcolumns of type `Object`. (). Backported in : Fix reading from `Kafka` tables when `kafkanumconsumers > 1` and `kafkathreadper_consumer = 0`. Returns parallel & multithreaded reading, accidentally broken in 21.11. Closes . (). Backported in : Fix reading of empty arrays in reverse order (in queries with descending sorting by prefix of primary key). ().
Project: Kubefirst (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

Firstly, we want to thank you for investing your valuable time to contribute to Kubefirst! Please note that this file is a work-in-progress, so more details will be added in the future. Note we have a which needs to be followed in all your interactions with the project to keep our community healthy. At Kubefirst, we believe that every contribution is valuable, not just the code one, which means we welcome ; ; like unclear section, missing information or even typos; and, of course, any code contributions to Kubefirst, or the documentations. Before making a code change, first discuss your idea via an . Please check if a feature request or bug report does before creating a new one. Kubefirst is created using the . To set up your computer, follow . Once Go is installed, you can run Kubefirst from any branch using `go run .`. Go will automatically install the needed modules listed in the file. As an example, if you want to create a , the command would be `go run . k3d create`. Note that even if you run kubefirst from `main`, the version used will be the . If you also want to use the latest from `main` for the template also, you need to run to use the `--gitops-template-url`, and the `--gitops-template-branch` as follow: ```shell go run . k3d create --gitops-template-url https://github.com/kubefirst/gitops-template --gitops-template-branch main ``` Since Go is a compiled programming language, every time you use the `run` command, Go will compile the code before running it. If you want to save time, you can compile your code using `go build`, which will generate a file named `kubefirst`. You will then be able to run your compiled version with the `./kubefirst` command. Please check the file from the repository. If you need help in your Kubefirst journey as a contributor, please join our . We have the `#contributors` channel where you can ask any questions or get help with anything contribution-related. For support as a user, please ask in the `#helping-hands` channel, or directly to @fharper (Fred in Slack), our Developer Advocate.
Project: ClickHouse (App Definition and Development / Database)
File: skewpop.md

slug: /en/sql-reference/aggregate-functions/reference/skewpop sidebar_position: 150 Computes the of a sequence. ``` sql skewPop(expr) ``` Arguments `expr` returning a number. Returned value The skewness of the given distribution. Type Example ``` sql SELECT skewPop(value) FROM serieswithvalue_column; ```
Project: KICS (Provisioning / Security & Compliance)
File: 2e48d91c-50e4-45c8-9312-27b625868a72.md

title: WAF Is Disabled For Azure Application Gateway hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2e48d91c-50e4-45c8-9312-27b625868a72 Query name: WAF Is Disabled For Azure Application Gateway Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Check if Web Application Firewall is disabled or not configured for Azure's Application Gateway.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11 7" resource "azurermapplicationgateway" "positive1" { name = "example-appgateway" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location waf_configuration { enabled = false } } resource "azurermapplicationgateway" "positive2" { name = "example-appgateway" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermapplicationgateway" "negative1" { name = "example-appgateway" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location waf_configuration { enabled = true } } ```
Project: Ansible (Provisioning / Automation & Configuration)
File: SECURITY.md

Ansible applies security fixes according to the 3-versions-back support policy. Please find more information in [our docs]( https://docs.ansible.com/ansible/devel/referenceappendices/releaseand_maintenance.html#release-status ). We encourage responsible disclosure practices for security vulnerabilities. Please read our [policies for reporting bugs]( https://docs.ansible.com/ansible/devel/community/reportingbugsand_features.html#reporting-a-bug ) if you want to report a security issue that might affect Ansible.
Project: BigchainDB (App Definition and Development / Database)
File: generate-key-pair-for-ssh.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > This page describes how to use `ssh-keygen` to generate a public/private RSA key pair that can be used with SSH. (Note: `ssh-keygen` is found on most Linux and Unix-like operating systems; if you're using Windows, then you'll have to use another tool, such as PuTTYgen.) By convention, SSH key pairs get stored in the `~/.ssh/` directory. Check what keys you already have there: ```text ls -1 ~/.ssh/ ``` Next, make up a new key pair name (called `<name>` below). Here are some ideas: `aws-bdb-2` `tim-bdb-azure` `chris-bcdb-key` Next, generate a public/private RSA key pair with that name: ```text ssh-keygen -t rsa -C "<name>" -f ~/.ssh/<name> ``` It will ask you for a passphrase. You can use whatever passphrase you like, but don't lose it. Two keys (files) will be created in `~/.ssh/`: `~/.ssh/<name>.pub` is the public key `~/.ssh/<name>` is the private key
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.4.69-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : If the database is already initialized, it doesn't need to be initialized again upon subsequent launches. This can potentially fix the issue of infinite container restarts when the database fails to load within 1000 attempts (relevant for very large databases and multi-node setups). (). Backported in : Resource with source code including submodules is built in Darwin special build task. It may be used to build ClickHouse without checkouting submodules. (). Backported in : Solve issue with launching standalone clickhouse-keeper from clickhouse-server package. (). Backported in : Fix integration check python script to use gh api url - Add Readme for CI tests. (). Fix "Invalid number of rows in Chunk" in MaterializedPostgreSQL (). Move obsolete format settings to separate section (). Fix: insert quorum w/o keeper retries (). Prevent attaching parts from tables with different projections or indices (). Proper cleanup in case of exception in ctor of ShellCommandSource (). Fix deadlock in LDAP assigned role update (). Fix for background download in fs cache (). Fix functions execution over sparse columns (). Fix bug with inability to drop detached partition in replicated merge tree on top of S3 without zero copy (). Fix trash optimization (up to a certain extent) (). Fix parsing of arrays in cast operator (). Fix filtering by virtual columns with OR filter in query (). Fix MongoDB connection issues (). Destroy fiber in case of exception in cancelBefore in AsyncTaskExecutor (). Fix crash in QueryNormalizer with cyclic aliases (). Fix filtering by virtual columns with OR filter in query (resubmit) (). Backported in :. (). S3 artifacts (). Fix CI skip build and skip tests checks (). Update WebObjectStorage.cpp (). Do not set PR status label (). Get rid of the most of `os.path` stuff (). Clean data dir and always start an old server version in aggregate functions compatibility test. (). check if block is empty after async insert retries (). MaterializedPostgreSQL: remove back check (). Remove existing moving/ dir if allowremovestalemovingparts is off (). Bump curl to 8.4 ().
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: MIGRATION_GUIDE.md

Starting from , the import path will be: "github.com/golang-jwt/jwt/v4" The `/v4` version will be backwards compatible with existing `v3.x.y` tags in this repo, as well as `github.com/dgrijalva/jwt-go`. For most users this should be a drop-in replacement, if you're having troubles migrating, please open an issue. You can replace all occurrences of `github.com/dgrijalva/jwt-go` or `github.com/golang-jwt/jwt` with `github.com/golang-jwt/jwt/v4`, either manually or by using tools such as `sed` or `gofmt`. And then you'd typically run: ``` go get github.com/golang-jwt/jwt/v4 go mod tidy ``` The original migration guide for older releases can be found at https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md.
Project: OAuth2 Proxy (Provisioning / Key Management)
File: SECURITY.md

id: security title: Security :::note OAuth2 Proxy is a community project. Maintainers do not work on this project full time, and as such, while we endeavour to respond to disclosures as quickly as possible, this may take longer than in projects with corporate sponsorship. ::: :::important If you believe you have found a vulnerability within OAuth2 Proxy or any of its dependencies, please do NOT open an issue or PR on GitHub, please do NOT post any details publicly. ::: Security disclosures MUST be done in private. If you have found an issue that you would like to bring to the attention of the maintenance team for OAuth2 Proxy, please compose an email and send it to the list of maintainers in our file. Please include as much detail as possible. Ideally, your disclosure should include: A reproducible case that can be used to demonstrate the exploit How you discovered this vulnerability A potential fix for the issue (if you have thought of one) Versions affected (if not present in master) Your GitHub ID We use to privately discuss fixes for disclosed vulnerabilities. If you include a GitHub ID with your disclosure we will add you as a collaborator for the advisory so that you can join the discussion and validate any fixes we may propose. For minor issues and previously disclosed vulnerabilities (typically for dependencies), we may use regular PRs for fixes and forego the security advisory. Once a fix has been agreed upon, we will merge the fix and create a new release. If we have multiple security issues in flight simultaneously, we may delay merging fixes until all patches are ready. We may also backport the fix to previous releases, but this will be at the discretion of the maintainers.