cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_billing_project_billing_info.md

+++ title = "googlebillingprojectbillinginfo resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlebillingprojectbillinginfo" identifier = "inspec/resources/gcp/googlebillingprojectbillinginfo.md googlebillingprojectbillinginfo resource" parent = "inspec/resources/gcp" +++ A `googlebillingprojectbillinginfo` is used to test a Google ProjectBillingInfo resource ```ruby describe googlebillingprojectbillinginfo(project_id: 'chef-gcp-inspec') do it { should exist } its('billingaccountname') { should eq 'billingAccounts/012345-567890-ABCDEF' } its('billing_enabled') { should eq true } end ``` Properties that can be accessed from the `googlebillingprojectbillinginfo` resource: `project_id` : The project id to retrieve billing info for. `billingaccountname` : The resource name of the billing account associated with the project, if any. For example, `billingAccounts/ 012345-567890-ABCDEF`. `billing_enabled` : True if the project is associated with an open billing account, to which usage on the project is charged. False if the project is associated with a closed billing account, or no billing account at all, and therefore cannot use paid services.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- Welcome to the Operator SDK! Before contributing, make sure to: Read the contributing guidelines https://github.com/operator-framework/operator-sdk/blob/master/CONTRIBUTING.MD Rebase your branch on the latest upstream master Link any relevant issues, PR's, or documentation Check that the commit message is concice and helpful: When fixing an issue, add "Closes #<ISSUE_NUMBER>" Sign your commit https://github.com/apps/dco Follow the below checklist if making a user-facing change Note, the location for ansible operator related logic has changed. For ansible operator related changes, please create the Pull Request in https://github.com/operator-framework/ansible-operator-plugins --> Description of the change: Motivation for the change: Checklist If the pull request includes user-facing changes, extra documentation is required: )
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.11.md

RabbitMQ `3.11.11` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Streams consumers that oscillate between being active and inactive, or just happen to be temporarily become really slow, could become completely starved of deliveries. That is, their message delivery rate could drop to 0 while other consumers did not have this problem. GitHub issue: Stream coordinator process memory footprint is now reported correctly (and classified differently). Contributed by @gomoripeti (CloudAMQP). GitHub issue: There is now a way to pre-configure users and their permissions for newly created virtual hosts: ``` ini defaultusers.qauser.vhost_pattern = qa.* defaultusers.qauser.tags = policymaker,monitoring defaultusers.qauser.password = fd237824441a78cd922410af4b83f0888186a8d7 defaultusers.qauser.read = .* defaultusers.qauser.write = .* defaultusers.qauser.configure = .* ``` This is primarily useful in environments where RabbitMQ is provided as a service but customers (clients) have control over virtual hosts. Contributed by @illotum (AWS). GitHub issue: . HTTP API will now respond with a `405 Method Not Allowed` instead of a 500 when an unsupported method is used by the client. Contributed by @gomoripeti (CloudAMQP). GitHub issue: Consumers on `/queue/` destinations that consume from now can specify the `x-stream-max-segment-size-bytes` setting via `SUBSCRIBE` frame headers. GitHub issues: Node key TTL setting was unintentionally ignored. GitHub issues: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.11.tar.xz` instead of the source tarball produced by GitHub.
Project: Keycloak (Provisioning / Security & Compliance)
File: WRITING_TESTS.md

Don't do this: ```typescript cy.findByTestId("rs-keys-tab").click(); cy.findByTestId("rs-providers-tab").click(); cy.findAllByTestId("provider-name-link") .contains("test_hmac-generated") .click(); ``` Instead use a page object as it is a lot easier to get the intended functionality of the test: ```typescript realmSettings.goToProvidersTab(); realmSettings.fillOutForm({ name: "test" }).save(); ``` Write locators in the PageObject layer and in object variables when possible to avoid hardcoding. Set type of element at the end of the variable name (e.g. saveBtn, nameInput, userDrpDwn) Avoid adding click to name methods, methods should be named as an action goToX, openX, createX, etc. Consistent naming (e.g goToTab methods, somewhere named goToTab, other goToXTab) We have `keycloakBefore` that will navigate to the main page, control request errors and wait for the load to finish. You can then have multiple test or create a new `describe` block to setup some data for your test. ```typescript describe("Realm roles test", () => { before(() => { keycloakBefore(); loginPage.logIn(); }); beforeEach(() => { sidebarPage.goToRealmRoles(); }); ``` Example of `describe` to setup data for that test: ```typescript import adminClient from "../support/util/AdminClient"; describe("Edit role details", () => { before(() => { adminClient.createRealmRole({ name: editRoleName, description, }); }); after(() => { adminClient.deleteRealmRole(editRoleName); }); it("Should edit realm role details", () => { // ... ``` Sometimes you will get the following error: Cypress failed because the element has been detached from the DOM This is because the DOM has been updated in between selectors. You can remedy this by waiting on REST calls. You can see the rest calls in the cypress IDE. ```typescript cy.intercept("/admin/realms/master/").as("search"); // ... pressing a button that will perform the search cy.wait(["@search"]); // wait for the call named search ``` If there were no calls and you still get this error, try using `{force: true}`, but try not to use it everywhere. For example, there could be an unexpected open modal blocking the element, so even the user wouldnt be able to use that element.
Project: Dragonfly (Provisioning / Container Registry)
File: PULL_REQUEST_TEMPLATE.md

<! Provide a general summary of your changes in the Title above --> <! Describe your changes in detail --> <! This project only accepts pull requests related to open issues --> <! If suggesting a new feature or change, please discuss it in an issue first --> <! If fixing a bug, there should be an issue describing it with steps to reproduce --> <! Please link to the issue here: --> <! Why is this change required? What problem does it solve? --> <! What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> [ ] Bug fix (non-breaking change which fixes an issue) [ ] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change) [ ] Documentation Update (if none of the other choices apply) <! Go over all the following points, and put an `x` in all the boxes that apply. --> <! If you're unsure about any of these, don't hesitate to ask. We're here to help! --> [ ] My change requires a change to the documentation. [ ] I have updated the documentation accordingly. [ ] I have read the CONTRIBUTING document. [ ] I have added tests to cover my changes.
Project: KICS (Provisioning / Security & Compliance)
File: b80b14c6-aaa2-4876-b651-8a48b6c32fbf.md

title: Network Policy Is Not Targeting Any Pod hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b80b14c6-aaa2-4876-b651-8a48b6c32fbf Query name: Network Policy Is Not Targeting Any Pod Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Check if any network policy is not targeting any pod.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="14" resource "kubernetesnetworkpolicy" "example" { metadata { name = "terraform-example-network-policy" namespace = "default" } spec { pod_selector { match_expressions { key = "name" operator = "In" values = ["webfront", "api"] } match_labels = { app = "ngnix" } } ingress { ports { port = "http" protocol = "TCP" } ports { port = "8125" protocol = "UDP" } from { namespace_selector { match_labels = { name = "default" } } } from { ip_block { cidr = "10.0.0.0/8" except = [ "10.0.0.0/24", "10.0.1.0/24", ] } } } egress {} # single empty rule to allow all egress traffic policy_types = ["Ingress", "Egress"] } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetesnetworkpolicy" "example2" { metadata { name = "terraform-example-network-policy" namespace = "default" } spec { pod_selector { match_expressions { key = "name" operator = "In" values = ["webfront", "api"] } match_labels = { app = "ngnix2" } } ingress { ports { port = "http" protocol = "TCP" } ports { port = "8125" protocol = "UDP" } from { namespace_selector { match_labels = { name = "default" } } } from { ip_block { cidr = "10.0.0.0/8" except = [ "10.0.0.0/24", "10.0.1.0/24", ] } } } egress {} # single empty rule to allow all egress traffic policy_types = ["Ingress", "Egress"] } } resource "kubernetes_pod" "test2" { metadata { name = "terraform-example" labels = { app = "ngnix2" } } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } resource "kubernetesnetworkpolicy" "example222" { metadata { name = "terraform-example-network-policy" namespace = "default" } spec { pod_selector { match_expressions { key = "name" operator = "In" values = ["webfront", "api"] } match_labels = { app = "kubernetes_pod.test2.metadata.0.labels.app" } } ingress { ports { port = "http" protocol = "TCP" } ports { port = "8125" protocol = "UDP" } from { namespace_selector { match_labels = { name = "default" } } } from { ip_block { cidr = "10.0.0.0/8" except = [ "10.0.0.0/24", "10.0.1.0/24", ] } } } egress {} # single empty rule to allow all egress traffic policy_types = ["Ingress", "Egress"] } } ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.4.6.53-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : SALT is allowed for CREATE USER <user> IDENTIFIED WITH sha256_hash. (). Backported in : - Change `all|noarch` packages to architecture-dependent - Fix some documentation for it - Push aarch64|arm64 packages to artifactory and release assets - Fixes . (). Backported in : Fix unexpected errors with a clash of constant strings in aggregate function, prewhere and join. Close . (). Backported in : Fix logical error in normalizeUTF8 functions. Closes . (). Backported in : Fix setting castipv4ipv6defaultonconversionerror for internal cast function. Closes . (). Backported in : Fix bug with nested short-circuit functions that led to execution of arguments even if condition is false. Closes . (). Backported in : Fix incorrect result of distributed queries with `DISTINCT` and `LIMIT`. Fixes . (). Backported in : Fix parts removal (will be left forever if they had not been removed on server shutdown) after incorrect server shutdown. (). Backported in : Fix table creation to avoid replication issues with pre-22.4 replicas. (). Backported in : Now it's possible to start a clickhouse-server and attach/detach tables even for tables with the incorrect values of IPv4/IPv6 representation. Proper fix for issue . (). Backported in : Adapt some more nodes to avoid issues with pre-22.4 replicas. (). Backported in : `rankCorr` function will work correctly if some arguments are NaNs. This closes . (). Backported in : Fix use-after-free for Map combinator that leads to incorrect result. (). Backported in : Server might fail to start if it cannot resolve hostname of external ClickHouse dictionary. It's fixed. Fixes . (). Backported in : - Fix potential error with literals in `WHERE` for join queries. Close . (). Backported in : Fixed problem with infs in `quantileTDigest`. Fixes . (). Integration tests (). Try to fix some trash (). Update protobuf files for kafka and rabbitmq (). Try fix `testgrpcprotocol/test.py::test_progress` (). Update docker-compose to try get rid of v1 errors (). Fix backports diff ().
Project: ArangoDB (App Definition and Development / Database)
File: narrow_value_check.md

+++ title = "`static void narrowvaluecheck(Impl &&) noexcept`" description = "Observer policy performing hard UB if no value is present. Constexpr, never throws." categories = ["observer-policies"] weight = 400 +++ Observer policy performing hard UB if no value is present, by calling {{% api "static void _ub(Impl &&)" %}}. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: windowing.md

In the world of data processing on an unbounded stream, Windowing is a concept of grouping data using temporal boundaries. We use event-time to discover temporal boundaries on an unbounded, infinite stream and to ensure the datasets within the boundaries are complete. The is applied on these grouped datasets. For example, when we say, we want to find number of users online per minute, we use windowing to group the users into one minute buckets. The entirety of windowing is under the `groupBy` section. ```yaml vertices: name: my-udf udf: groupBy: window: ... keyed: ... ``` Since a window can be , we have an explicit field called `keyed`to differentiate between both (see below). Under the `window` section we will define different types of windows. Numaflow supports the following types of windows A `non-keyed` partition is a partition where the window is the boundary condition. Data processing on a non-keyed partition cannot be scaled horizontally because only one partition exists. A non-keyed partition is usually used after aggregation and is hardly seen at the head section of any data processing pipeline. (There is a concept called Global Window where there is no windowing, but let us table that for later). A `keyed` partition is a partition where the partition boundary is a composite key of both the window and the key from the payload (e.g., GROUP BY country, where country names are the keys). Each smaller partition now has a complete set of datasets for that key and boundary. The subdivision of dividing a huge window-based partition into smaller partitions by adding keys along with the window will help us horizontally scale the distribution. Keyed partitions are heavily used to aggregate data and are frequently seen throughout the processing pipeline. We could also convert a non-keyed problem to a set of keyed problems and apply a non-keyed function at the end. This will help solve the original problem in a scalable manner without affecting the result's completeness and/or accuracy. When a `keyed` window is used, an optional `partitions` can be specified in the vertex for parallel processing. Numaflow supports both Keyed and Non-Keyed windows. We set `keyed` to either `true` (keyed) or `false` (non-keyed). Please note that the non-keyed windows are not horizontally scalable as mentioned above. ```yaml vertices: name: my-reduce partitions: 5 # Optional, defaults to 1 udf: groupBy: window: ... keyed: true # Optional, defaults to false ```
Project: KICS (Provisioning / Security & Compliance)
File: 77783205-c4ca-4f80-bb80-c777f267c547.md

title: APT-GET Missing '-y' To Avoid Manual Input hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 77783205-c4ca-4f80-bb80-c777f267c547 Query name: APT-GET Missing '-y' To Avoid Manual Input Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Supply-Chain URL: Check if apt-get calls use the flag -y to avoid user manual input.<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2 3 4" FROM node:12 RUN apt-get install python=2.7 RUN apt-get install apt-utils RUN ["apt-get", "install", "apt-utils"] ``` ```dockerfile title="Positive test num. 2 - dockerfile file" hl_lines="2 3 4" FROM node:12 RUN sudo apt-get install python=2.7 RUN sudo apt-get install apt-utils RUN ["sudo", "apt-get", "install", "apt-utils"] ``` ```dockerfile title="Positive test num. 3 - dockerfile file" hl_lines="2" FROM node:12 RUN DUMMY=test apt-get install python=2.7 ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM node:12 RUN apt-get -y install apt-utils RUN apt-get -qy install git gcc RUN ["apt-get", "-y", "install", "apt-utils"] ``` ```dockerfile title="Negative test num. 2 - dockerfile file" FROM node:12 RUN sudo apt-get -y install apt-utils RUN sudo apt-get -qy install git gcc RUN ["sudo", "apt-get", "-y", "install", "apt-utils"] ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.87.md

layout: release date: 2023-05-02 tag: v0.6.87 [meshmodel] add ingress to service relationship @MUzairS15 (#7626) Increase testing coverage and fix defer error @Aisuko (#7633) Increase test coverage for mesheryctl @Aisuko (#7631) Bump @emotion/react from 11.10.5 to 11.10.8 in /ui @dependabot (#7646) Bump next from 13.1.5 to 13.3.4 in /provider-ui @dependabot (#7641) Bump @mui/icons-material from 5.11.11 to 5.11.16 in /provider-ui @dependabot (#7640) [Extensions] Add publish feature support for extensions @Chadha93 (#7555) Bump eslint-plugin-cypress from 2.12.1 to 2.13.3 in /ui @dependabot (#7639) Bump @emotion/react from 11.10.6 to 11.10.8 in /provider-ui @dependabot (#7637) [rjsf] pluralize, checkboxes dark mode, cleanup @harkiratsm (#7635) Bump eslint from 8.32.0 to 8.39.0 in /provider-ui @dependabot (#7638) Bump @storybook/react from 6.5.16 to 7.0.7 in /ui @dependabot (#7643) Bump @emotion/react from 11.10.5 to 11.10.8 in /ui @dependabot (#7646) Bump next from 13.1.5 to 13.3.4 in /provider-ui @dependabot (#7641) Bump @mui/icons-material from 5.11.11 to 5.11.16 in /provider-ui @dependabot (#7640) Bump eslint-plugin-cypress from 2.12.1 to 2.13.3 in /ui @dependabot (#7639) Bump @emotion/react from 11.10.6 to 11.10.8 in /provider-ui @dependabot (#7637) Bump eslint from 8.32.0 to 8.39.0 in /provider-ui @dependabot (#7638) Bump @storybook/react from 6.5.16 to 7.0.7 in /ui @dependabot (#7643) Bump github.com/layer5io/meshery-operator from 0.6.6 to 0.6.8 @dependabot (#7647) fix typo in summary @shivamganwani (#7628) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aisuko, @Chadha93, @MUzairS15, @acald-creator, @dependabot, @dependabot[bot], @harkiratsm, @leecalcote, @shivamganwani, MUzairS15 and l5io
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-error-conditions-codec-not-available-error-class.md

layout: global title: CODECNOTAVAILABLE error class displayTitle: CODECNOTAVAILABLE error class 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. <!-- DO NOT EDIT THIS FILE. It was generated automatically by `org.apache.spark.SparkThrowableSuite`. --> SQLSTATE: 56038 The codec `<codecName>` is not available. This error class has the following derived error classes: Available codecs are `<availableCodecs>`. Consider to set the config `<configKey>` to `<configVal>`.
Project: Druid (App Definition and Development / Database)
File: proposal.md

name: Proposal about: A template for major Druid change proposals title: "" labels: Proposal, Design Review assignees: '' A description of the problem. This section should provide a detailed description of the changes being proposed. This will usually be the longest section; please feel free to split this section or other sections into subsections if needed. This section should include any changes made to user-facing interfaces, for example: Parameters JSON query/ingest specs SQL language Emitted metrics A discussion of why this particular solution is the best one. One good way to approach this is to discuss other alternative solutions that you considered and decided against. This should also include a discussion of any specific benefits or drawbacks you are aware of. This section should describe how the proposed changes will impact the operation of existing clusters. It should answer questions such as: Is anything going to be deprecated or removed by this change? How will we phase out old behavior? Is there a migration path that cluster operators need to be aware of? Will there be any effect on the ability to do a rolling upgrade, or to do a rolling downgrade if an operator wants to switch back to a previous version? An optional discussion of how the proposed changes will be tested. This section should focus on higher level system test strategy and not unit tests (as UTs will be implementation dependent). An optional discussion of things that you believe are out of scope for the particular proposal but would be nice follow-ups. It helps show where a particular change could be leading us. There isn't any commitment that the proposal author will actually work on the items discussed in this section.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-farm-update.1.md

% podman-farm-update 1 podman\-farm\-update - Update an existing farm podman farm update [options] name Update a farm by either adding connections to it, removing connections from it, or setting it as the new default farm. Add new connections to an existing farm. Multiple connections can be added at once. Set the current farm as the default. Remove one or more connections from an existing farm. Add two connections to specified farm: ``` $ podman farm update --add f35,f38 farm1 ``` Add connection to specified farm: ``` $ podman farm update --remove f35 farm1 ``` Change specified farm to be default: ``` $ podman farm update --default farm2 ``` , July 2023, Originally compiled by Urvashi Mohnani (umohnani at redhat dot com)s
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: man_docs.md

Generating man pages from a cobra command is incredibly easy. An example is as follows: ```go package main import ( "log" "github.com/spf13/cobra" "github.com/spf13/cobra/doc" ) func main() { cmd := &cobra.Command{ Use: "test", Short: "my test program", } header := &doc.GenManHeader{ Title: "MINE", Section: "3", } err := doc.GenManTree(cmd, header, "/tmp") if err != nil { log.Fatal(err) } } ``` That will get you a man page `/tmp/test.3`