cwielenb/CNCF-Dataset huggingface dataset:
Project: LinuxKit (Provisioning / Automation & Configuration)
File: README.md

This directory contains the files to build and run a container containing the virtio and Hyper-V socket stress tests. `../../cases/test-virtsock-server.yml` builds images which start the server inside the VM. The client, to be run on the host as per this , can be obtained compiled from . Build the images: `linuxkit build tests/cases/test-virtsock-server.yml` Copy the `test-virtsock-server.iso` to a Windows system Create a Type 1 Hyper-V VM (called `virtsock`). No Disk or network required Add the ISO to the CDROM device Make sure you enable a named pipe for COM1 (call it `virtsock`) Start the VM Connect to the serial console (to get debug output) with `putty -serial \\.\pipe\virtsock` Run the client: ``` $vmId = (get-vm virtsock).Id .\virtsock_stress.exe -c $vmId -v 1 -c 1000000 -p 10 ``` This creates `1000000` connections from `10` threads to the VM and sends some random amount of data of the connection before tearing it down. There are more options to change the behaviour. Add scripts to create Hyper-V VM Enable virtio sockets in `linuxkit run` with HyperKit Add some sample client YAML files which would connect from the VM to the host Hook up to CI for both HyperKit and Hyper-V for the specified architecture. For example, contains packages to be installed only on `linuxkit/alpine` for `x84_64`. `packages.repo.<name>` - these files contain the list of packages to mirror locally in `linuxkit/alpine`, like `packages`, but to pull those packages from the provided `<name>` of Alpine's `apk` repo. For example, `packages.repo.edge` installs packages from Alpine's `edge` package repository. `packages.<arch>.repo.<name>` - these files contain the list of packages to mirror locally in `linuxkit/alpine` for a specific architecture, like `packages.<arch>`, but to pull those packages from the provided `<name>` of Alpine's `apk` repor. For example, `packages.x8664.repo.edge` installs packages from Alpine's `edge` package repository, hut only when building for `8664`. In addition, the may install certain packages directly from source, if they are not available in the `apk` repositories, or the versions are insufficient. The final versions of packages installed are available in `versions.<arch>`.
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_version.md

Print sonobuoy version ``` sonobuoy version [flags] ``` ``` --context string Context in the kubeconfig to use. -h, --help help for version --kubeconfig Kubeconfig Path to explicit kubeconfig file. --short If true, prints just the Sonobuoy version. ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generate reports on your Kubernetes cluster by running plugins
Project: KICS (Provisioning / Security & Compliance)
File: e8bb41e4-2f24-4e84-8bea-8c7c070cf93d.md

title: Serving Revision Spec Without Timeout Seconds hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e8bb41e4-2f24-4e84-8bea-8c7c070cf93d Query name: Serving Revision Spec Without Timeout Seconds Platform: Knative Severity: <span style="color:#5bc0de">Info</span> Category: Insecure Configurations URL: Serving Revision Spec should have Timeout Seconds defined to avoid Denial of Service<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="42 7" apiVersion: serving.knative.dev/v1 kind: Service metadata: name: dummy spec: template: spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" containerConcurrency: 100 apiVersion: serving.knative.dev/v1 kind: Service metadata: name: dummy spec: template: spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" containerConcurrency: 100 timeoutSeconds: 0 ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: serving.knative.dev/v1 kind: Service metadata: name: dummy spec: template: spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" containerConcurrency: 100 timeoutSeconds: 600 ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.5.9.4-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix extremely long backoff for background tasks when the background pool is full. Fixes . (). Backported in : Fix possible crash in `pointInPolygon` if the setting `validate_polygons` is turned off. (). 21.5 manual backport of (). 21.5 Docker unbundled fix ().
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_pubsub_topics.md

+++ title = "googlepubsubtopics resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlepubsubtopics" identifier = "inspec/resources/gcp/googlepubsubtopics.md googlepubsubtopics resource" parent = "inspec/resources/gcp" +++ A `googlepubsubtopics` is used to test a Google Topic resource ```ruby describe googlepubsubtopics(project: 'chef-gcp-inspec') do it { should exist } its('names') { should include 'inspec-gcp-topic' } its('count') { should be >=1 } end describe.one do googlepubsubtopics(project: 'chef-gcp-inspec').names.each do |topic_name| describe googlepubsubtopic(project: 'chef-gcp-inspec', name: topic_name) do it { should exist } end end end ``` Properties that can be accessed from the `googlepubsubtopics` resource: See the resource for more information. `names` : an array of `googlepubsubtopic` name `kmskeynames` : an array of `googlepubsubtopic` kmskeyname `labels` : an array of `googlepubsubtopic` labels `messagestoragepolicies` : an array of `googlepubsubtopic` messagestoragepolicy 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: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_completion.md

title: "operator-sdk completion" Load completions for the specified shell Output shell completion code for the specified shell. The shell code must be evaluated to provide interactive completion of operator-sdk commands. Detailed instructions on how to do this for each shell are provided in their own commands. ``` -h, --help help for completion ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - - Load bash completions - Load fish completions - Load powershell completions - Load zsh completions
Project: Flink (App Definition and Development / Streaming & Messaging)
File: sub-queries.md

title: "Sub-Queries" weight: 8 type: docs <!-- 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. --> Hive dialect supports sub-queries in the `FROM` clause. The sub-query has to be given a name because every table in a `FROM` clause must have a name. Columns in the sub-query select list must have unique names. The columns in the sub-query select list are available in the outer query just like columns of a table. The sub-query can also be a query expression with `UNION`. Hive dialect supports arbitrary levels of sub-queries. ```sql selectstatement FROM ( selectstatement ) [ AS ] name ``` ```sql SELECT col FROM ( SELECT a+b AS col FROM t1 ) t2 ``` Hive dialect also supports some types of sub-queries in the `WHERE` clause. ```sql select_statement FROM table WHERE { colName { IN | NOT IN } | NOT EXISTS | EXISTS } ( subqueryselectstatement ) ``` ```sql SELECT * FROM t1 WHERE t1.x IN (SELECT y FROM t2); SELECT * FROM t1 WHERE EXISTS (SELECT y FROM t2 WHERE t1.x = t2.x); ```
Project: ShardingSphere (App Definition and Development / Database)
File: show-compute-nodes.en.md

+++ title = "SHOW COMPUTE NODES" weight = 3 +++ The `SHOW COMPUTE NODES` syntax is used to query compute nodes information. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowComputeNodes ::= 'SHOW' 'COMPUTE' 'NODES' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Columns | Description | ||| | instance_id | instance id | | instance_type | instance type | | host | host | | port | port | | status | status | | mode_type | mode type | | worker_id | worker id | | labels | labels | | version | version | ```sql mysql> SHOW COMPUTE NODES; +--++++--++--+--+-+ | instanceid | instancetype | host | port | status | modetype | workerid | labels | version | +--++++--++--+--+-+ | 3e84d33e-cb97-42f2-b6ce-f78fea0ded89 | PROXY | 127.0.0.1 | 3307 | OK | Cluster | -1 | | 5.4.2 | +--++++--++--+--+-+ 1 row in set (0.01 sec) ``` `SHOW`, `COMPUTE`, `NODES`
Project: Juju (Provisioning / Automation & Configuration)
File: test-failure-FAQ.md

Test Failure FAQ ================ This is an attempt to create a resource for weird test failures. Almost certainly there is a deadlock in the code, or the test is actually using time.Sleep for a long value. You need to fix the test. Now that the logs are kept in mongo, the debug log code attempts to tail the oplog to get the new logs. Most tests don't set up mongo in replicaset mode, so no oplog collection is created. Most debug-log tests now mock out the oplog with a capped collection for testing purposes. If you hit this error, you need to either provide a mock oplog, or don't call debug-log.
Project: YugabyteDB (App Definition and Development / Database)
File: recover_server.md

title: Recover failed YB-TServer and YB-Master linkTitle: Recover YB-TServer and YB-Master description: Recover YB-TServer and YB-Master aliases: /troubleshoot/cluster/recover-server/ /preview/troubleshoot/cluster/recover-server/ menu: preview: parent: troubleshoot-cluster weight: 828 type: docs A cluster might be running while a YB-TServer process, YB-Master process, or a node fails. The following sample steps demonstrate how to recover a process if you have a N-node setup with replication factor (RF)=3. It is recommended to have a cron or systemd setup to ensure that the YB-TServer and YB-Master processes are restarted if they are not running. This handles transient failures, such as a node rebooting or process crash due to an unexpected behavior. If you are using systemd and want to find the names of the services to restart, use the following command: ```sh sudo systemctl list-units --type=service | grep yb ``` You should see output similar to the following: ```output yb-controller.service loaded active running Yugabyte Controller yb-master.service loaded active running Yugabyte master service yb-tserver.service loaded active running Yugabyte tserver service ``` Typically, if a node has failed, the system automatically recovers and continues to function with the remaining N-1 nodes. If the failed node does not recover soon enough, and N-1 >= 3, then the under-replicated tablets will be re-replicated automatically to return to RF=3 on the remaining N-1 nodes. If a node has experienced a permanent failure on a YB-TServer, you should start another YB-TServer process on a new node. This node will join the cluster, and the load balancer will automatically take the new YB-TServer into consideration and start rebalancing tablets to it. If a new YB-Master needs to be started to replace a failed one, the master quorum needs to be updated. Suppose, the original YB-Masters were n1, n2, n3. And n3 needs to be replaced with a new YB-Master n4. Then you need to use the `yb-admin` subcommand `changemasterconfig`, as follows: ```sh ./bin/yb-admin -masteraddresses n1:7100,n2:7100 changemasterconfig REMOVESERVER n3 7100 ./bin/yb-admin -masteraddresses n1:7100,n2:7100 changemasterconfig ADDSERVER n4 7100 ``` The YB-TServer's in-memory state automatically learns of the new master after the `ADD_SERVER` step and does not need a restart. You should update the configuration file of all YB-TServer processes which specifies the master addresses to reflect the new quorum of n1, n2, n4. This is to handle the case if the `yb-tserver` restarts at some point in the future. You might choose to perform planned cluster changes, such as moving the entire cluster to a brand new set of nodes (for example, move from machines of type A to type B). For instructions on how to do this, see .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.38.md

layout: release date: 2022-12-23 tag: v0.6.38 language: en Convert 2 API calls to 1 for Applications @Revolyssup (#6752) Send notification of deployment failure @Revolyssup (#6772) Updated Guide for setting up meshery in Windows (special instruction for the compiler) @UtkarshMishra12 (#6764) Solved Issue 6754 for Designs Page @hs05june (#6758) FlushMeshSync button in actions column of environment settings centered @deepakdinesh1123 (#6675) Thank you to our contributors for making this release possible: @Chadha93, @Revolyssup, @UtkarshMishra12, @deepakdinesh1123, @hs05june, @leecalcote and l5io
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_logging_organization_log_sinks.md

+++ title = "googleloggingorganizationlogsinks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleloggingorganizationlogsinks" identifier = "inspec/resources/gcp/googleloggingorganizationlogsinks.md googleloggingorganizationlogsinks resource" parent = "inspec/resources/gcp" +++ A `googleloggingorganizationlogsinks` is used to test a Google OrganizationLogSink resource ```ruby describe googleloggingorganizationlogsinks(organization: '190694428152') do its('names') { should include 'inspec-gcp-org-sink' } end ``` Properties that can be accessed from the `googleloggingorganizationlogsinks` resource: See the resource for more information. `organizations` : an array of `googleloggingorganizationlogsink` organization `names` : an array of `googleloggingorganizationlogsink` name `filters` : an array of `googleloggingorganizationlogsink` filter `destinations` : an array of `googleloggingorganizationlogsink` destination `writer_identities` : an array of `googleloggingorganizationlogsink` writer_identity `include_children` : an array of `googleloggingorganizationlogsink` include_children 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: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: container_orchestration.md

+++ title = "Container Orchestration" description = "Container Orchestration with Chef Habitat" gh_repo = "habitat" [menu] [menu.habitat] title = "Container Orchestration" identifier = "habitat/containers/container-orchestration" parent = "habitat/containers" weight = 20 +++ Chef Habitat packages may be exported with the Supervisor directly into a , but frequently the container is running in a container orchestrator such as Kubernetes or Mesos. Container orchestrators provide scheduling and resource allocation, ensuring workloads are running and available. Containerized Chef Habitat packages can run within these runtimes, managing the applications while the runtimes handle the environment surrounding the application (ie. compute, networking, security).
Project: NebulaGraph (App Definition and Development / Database)
File: enhancement.md

name: Enhancement about: Suggest an enhancement to make the code neat or more efficient. title: '' labels: type/enhancement assignees: '' Introduction <!-- concise introduction to problem, motivation, and overview of proposed solution --> Contents <!-- Please describe the enhancement what you want in this section --> Related work <!-- In this section you can add other related tasks to help assigner to complete the task more easily -->
Project: Goldilocks (Provisioning / Security & Compliance)
File: code-of-conduct.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: NeuVector (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Environment Platform: [e.g. Kubernetes, OpenShift, Rancher, Managed k8s (AKS, EKS, GKE, IKS, ...), ...] Kubernetes/Platform Version(s): Describe the bug A clear and concise description of what the bug is. (If you are encountering a deployment error, check out the README or navigate to https://open-docs.neuvector.com for full deployment documentation. Incorrect runtime is the most common reason for Controller and Enforcer CrashLoopBackOff events.) 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. UI Issue Desktop (please complete the following information): OS: [e.g. MacOs 12.1, Windows 10] Browser [e.g. chrome, safari] Version [e.g. 22] Additional context Add any other context about the problem here.
Project: StarRocks (App Definition and Development / Database)
File: SET_DEFAULT_STORAGE_VOLUME.md

displayed_sidebar: "English" Sets a storage volume as the default storage volume. After creating a storage volume for an external data source, you can set it as the default storage volume of your StarRocks cluster. This feature is supported from v3.1. CAUTION Only users with the USAGE privilege on a specific storage volume can perform this operation. The default storage volume cannot be dropped or disabled. You must set the default storage volume for a shared-data StarRocks cluster because StarRocks stores the system statistics information in the default storage volume. ```SQL SET <storagevolumename> AS DEFAULT STORAGE VOLUME ``` | Parameter | Description | | - | | | storagevolumename | The name of the storage volume to be set as the default storage volume. | Example 1: Set the storage volume `mys3volume` as the default storage volume. ```SQL MySQL > SET mys3volume AS DEFAULT STORAGE VOLUME; Query OK, 0 rows affected (0.01 sec) ```
Project: KICS (Provisioning / Security & Compliance)
File: 625abc0e-f980-4ac9-a775-f7519ee34296.md

title: API Gateway Deployment Without Access Log Setting hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 625abc0e-f980-4ac9-a775-f7519ee34296 Query name: API Gateway Deployment Without Access Log Setting Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: API Gateway Deployment should have access log setting defined when connected to an API Gateway Stage.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsapigateway_deployment" "examplee" { restapiid = "some rest api id" stage_name = "some name" tags { project = "ProjectName" } } resource "awsapigateway_stage" "example00" { deploymentid = awsapigatewaydeployment.example.id restapiid = awsapigatewayrestapi.example.id stage_name = "example" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awsapigateway_deployment" "example3" { restapiid = "some rest api id" stage_name = "some name" tags { project = "ProjectName" } } resource "awsapigateway_stage" "example000" { deploymentid = awsapigatewaydeployment.example3.id restapiid = awsapigatewayrestapi.example.id stage_name = "example" } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="1" resource "awsapigateway_deployment" "example4" { restapiid = "some rest api id" stage_name = "some name" tags { project = "ProjectName" } } resource "awsapigateway_stage" "example0000" { deploymentid = awsapigatewaydeployment.example4.id restapiid = awsapigatewayrestapi.example.id stage_name = "example" accesslogsettings { destination_arn = "dest" format = "format" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigateway_deployment" "example5" { restapiid = "some rest api id" stage_name = "some name" stage_description = "some description" tags { project = "ProjectName" } } resource "awsapigateway_stage" "example0" { deploymentid = awsapigatewaydeployment.example5.id restapiid = awsapigatewayrestapi.example.id stage_name = "example" accesslogsettings { destination_arn = "dest" format = "format" } } ```