cwielenb/CNCF-Dataset huggingface dataset:
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.28.md

RabbitMQ `3.7.28` is a security patch release. RabbitMQ `3.7.x` series are out of general support and covered by the through October 1st, 2020. Please consider to . RabbitMQ Core team would like to thank Ofir Hamam and Tomer Hadad at Ernst & Young's Hacktics Advanced Security Center for researching and responsibly disclosing the vulnerability addressed in this release. This release . Erlang `21.3+` is now a hard requirement checked on node startup. Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . Addressed a Windows-specific binary planting security vulnerability that allowed for arbitrary code execution. The vulnerability requires the attacker to have local access and elevated privileges, and cannot be executed remotely. : `6.7` (medium severity). This vulnerability was researched and by Ofir Hamam and Tomer Hadad at Ernst & Young's Hacktics Advanced Security Center. Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.28.tar.xz`.
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.16.32-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Use sccache as a replacement for ccache and using S3 as cache backend. (). Backported in : The `clickhouse/clickhouse-keeper` image used to be pushed only with tags `-alpine`, e.g. `latest-alpine`. As it was suggested in https://github.com/ClickHouse/examples/pull/2, now it will be pushed as suffixless too. (). Fix bug in zero-copy replication disk choice during fetch (). Fix query parameters (). Fix wait for zero copy lock during move (). Fix crash in polygonsSymDifferenceCartesian (). Backport to 22.8: Fix moving broken parts to the detached for the object storage disk on startup (). Add a fuse for backport branches w/o a created PR (). Only valid Reviews.STATES overwrite existing reviews (). Place short return before big block, improve logging (). Artifacts s3 prefix (). Fix tsan error lock-order-inversion ().
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: generator.md

Generator Source is mainly used for development purpose, where you want to have self-contained source to generate some messages. We mainly use generator for load testing and integration testing of Numaflow. The load generated is per replica. ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: simple-pipeline spec: vertices: name: in source: generator: rpu: 100 duration: 1s msgSize: 1024 name: p1 udf: builtin: name: cat name: out sink: log: {} edges: from: in to: p1 from: p1 to: out ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubedb-operator_version.md

title: Kubedb-Operator Version menu: docs_{{ .version }}: identifier: kubedb-operator-version name: Kubedb-Operator Version parent: reference-operator menuname: docs{{ .version }} sectionmenuid: reference Prints binary version number. ``` kubedb-operator version [flags] ``` ``` --check string Check version constraint -h, --help help for version --short Print just the version number. ``` ``` --default-seccomp-profile-type string Default seccomp profile --use-kubeapiserver-fqdn-for-aks if true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522 (default true) ``` -
Project: ArangoDB (App Definition and Development / Database)
File: on_result_copy_construction.md

+++ title = "`static void onresultcopy_construction(T *, U &&) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the converting copy constructors of `basic_result`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the converting copy constructors of `basicresult` (NOT the standard copy constructor). See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: 02 - test.md

`KubeBlocks` uses make for a variety of test actions. Setting up a local control plane and test all packages: ```shell make test ``` Test specific packages: ```shell make test TEST_PACKAGES=./controllers/... make test-delve TEST_PACKAGES=./controllers/apps/... ``` ```shell make test-current-ctx ``` Instead of setting up a local control plane, this command will point to the control plane of an existing cluster by `$HOME/.kube/config`. ```shell make test cover-report ``` This command will test all packages and generate a coverage report file `cover.html`, and open by your default browser automatically.
Project: ShardingSphere (App Definition and Development / Database)
File: drop-default-shadow-algorithm.en.md

+++ title = "DROP DEFAULT SHADOW ALGORITHM" weight = 6 +++ The `DROP DEFAULT SHADOW ALGORITHM` syntax is used to drop default shadow algorithm for specified database {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropDefaultShadowAlgorithm ::= 'DROP' 'DEFAULT' 'SHADOW' 'ALGORITHM' ifExists? ('FROM' databaseName)? ifExists ::= 'IF' 'EXISTS' databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When databaseName is not specified, the default is the currently used DATABASE. If DATABASE is not used, No database selected will be prompted; `ifExists` clause used for avoid `Default shadow algorithm not exists` error. Drop default shadow algorithm for specified database ```sql DROP DEFAULT SHADOW ALGORITHM FROM shadow_db; ``` Drop default shadow algorithm for current database ```sql DROP DEFAULT SHADOW ALGORITHM; ``` Drop default shadow algorithm with `ifExists` clause ```sql DROP DEFAULT SHADOW ALGORITHM IF EXISTS; ``` `DROP`, `DEFAULT`, `SHODOW`, `ALGORITHM`, `FROM`
Project: ArangoDB (App Definition and Development / Database)
File: explicit_make_exception_ptr_move_converting_constructor.md

+++ title = "`explicit basicresult(basicresult<R, S, P> &&)`" description = "Explicit converting move constructor from compatible `basicresult`. Available if `predicate::enablemakeexceptionptrcompatibleconversion<R, S, P>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 324 +++ Explicit converting move constructor from compatible `basicresult`. Calls {{% api "void onresultmoveconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablemakeexceptionptrcompatible_conversion<R, S, P>` is true. Complexity: Same as for the move constructors of the underlying types. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.
Project: Microcks (App Definition and Development / Application Definition & Image Build)
File: CODE_OF_CONDUCT.md

Microcks project follows the . In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make 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. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team via info@microcks.io. The project team will review and investigate all complaints, and will respond in a way that it deems 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: KICS (Provisioning / Security & Compliance)
File: 0e75052f-cc02-41b8-ac39-a78017527e95.md

title: Privilege Escalation Using Become Plugin hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0e75052f-cc02-41b8-ac39-a78017527e95 Query name: Privilege Escalation Using Become Plugin Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: In order to perform an action as a different user with the become_user, 'become' must be defined and set to 'true'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4 44 15 53 61 31" hosts: localhost name: become_user without become become_user: bar tasks: name: Simple hello ansible.builtin.debug: msg: hello hosts: localhost name: become_user with become false become_user: root become: false tasks: name: Simple hello ansible.builtin.debug: msg: hello hosts: localhost tasks: name: become and become_user on different tasks block: name: Sample become become: true ansible.builtin.command: ls . name: Sample become_user become_user: foo ansible.builtin.command: ls . hosts: localhost tasks: name: become false block: name: Sample become become: true ansible.builtin.command: ls . name: Sample become_user become_user: postgres become: false ansible.builtin.command: ls . hosts: localhost tasks: name: become_user with become task as false ansible.builtin.command: whoami become_user: mongodb become: false changed_when: false hosts: localhost tasks: name: become_user without become ansible.builtin.command: whoami become_user: mysql changed_when: false ``` ```yaml title="Negative test num. 1 - yaml file" hosts: localhost become_user: postgres become: true tasks: name: some task ansible.builtin.command: whoamyou changed_when: false hosts: localhost tasks: name: become from the same scope ansible.builtin.command: whoami become: true become_user: postgres changed_when: false ```
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: README.md

This website is built using , a modern static website generator. ``` $ yarn ``` ``` $ yarn start ``` This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ``` $ yarn build ``` This command generates static content into the `build` directory and can be served using any static contents hosting service. Using SSH: ``` $ USE_SSH=true yarn deploy ``` Not using SSH: ``` $ GIT_USER=<Your GitHub username> yarn deploy ``` If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch. b.com/cyclops-ui/cyclops/actions/workflows/ci.yml"><img height="20" src="https://github.com/cyclops-ui/cyclops/actions/workflows/ci.yml/badge.svg"></a> </div> Welcome to Cyclops, a powerful user interface for managing and interacting with Kubernetes clusters. Cyclops is designed to simplify the management of containerized applications on Kubernetes, providing an intuitive and user-friendly experience for developers, system administrators, and DevOps professionals. Divide the responsibility between your infrastructure and your developer teams so everyone can play to their strengths. Automate your processes and shrink the window for deployment mistakes. Find out how to it to your cluster on our landing page and give it a go! (~10 minute tutorial) ]" Before installing Cyclops, make sure you have all the Cyclops can either be installed manually by applying the latest manifest or with the . To install Cyclops using `kubectl` into your cluster, run commands below: ```bash kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.5.0/install/cyclops-install.yaml && kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.5.0/install/demo-templates.yaml ``` It will create a new namespace called `cyclops` and deploy everything you need for your Cyclops instance to run. Now all that is left is to expose Cyclops server outside the cluster: ```bash kubectl port-forward svc/cyclops-ui 3000:3000 -n cyclops ``` You can now access Cyclops in your browser on . Every Cyclops instance comes with a couple of predefined templates, feel free to use and abuse them! Helm charts used for these templates can be found . You can use this repo as a guide if you want to create your own templates. More information on creating your own can be found on our . RBAC support for accessing charts stored on private GitHub repositories Git as manifest destination Customizable Module details page Feel free to suggest features you would like to see!
Project: Beam (App Definition and Development / Streaming & Messaging)
File: sdk-harness-config.md

title: "SDK Harness Configuration" <!-- 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. --> Beam allows configuration of the to accommodate varying cluster setups. (The options below are for Python, but much of this information should apply to the Java and Go SDKs as well.) `environment_type` determines where user code will be executed. `environmentconfig` configures the environment depending on the value of `environmenttype`. `DOCKER` (default): User code is executed within a container started on each worker node. This requires docker to be installed on worker nodes. `environment_config`: URL for the Docker container image. Official Docker images are available and are used by default. Alternatively, you can build your own image by following the instructions . `PROCESS`: User code is executed by processes that are automatically started by the runner on each worker node. `environment_config`: JSON of the form `{"os": "<OS>", "arch": "<ARCHITECTURE>", "command": "<process to execute>", "env":{"<Environment variables 1>": "<ENV_VAL>"} }`. All fields in the JSON are optional except `command`. For `command`, it is recommended to use the bootloader executable, which can be built from source with `./gradlew :sdks:python:container:build` and copied from `sdks/python/container/build/target/launcher/linux_amd64/boot` to worker machines. Note that the Python bootloader assumes Python and the `apache_beam` module are installed on each worker machine. `EXTERNAL`: User code will be dispatched to an external service. For example, one can start an external service for Python workers by running `docker run -p=50000:50000 apache/beampython3.6sdk --worker_pool`. `environment_config`: Address for the external service, e.g. `localhost:50000`. To access a Dockerized worker pool service from a Mac or Windows client, set the `BEAMWORKERPOOLINDOCKER_VM` environment variable on the client: `export BEAMWORKERPOOLINDOCKER_VM=1`. `LOOPBACK`: User code is executed within the same process that submitted the pipeline. This option is useful for local testing. However, it is not suitable for a production environment, as it performs work on the machine the job originated from. `environment_config` is not used for the `LOOPBACK` environment. `sdkworkerparallelism` sets the number of SDK workers that run on each worker node. The default is 1. If 0, the value is automatically set by the runner by looking at different parameters, such as the number of CPU cores on the worker machine. Only used for Python pipelines on Flink and Spark runners.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: json-merge-patch.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: busybox spec: components: name: busybox type: webservice properties: image: busybox cmd: ["sleep", "86400"] labels: pod-label-key: pod-label-value to-delete-label-key: to-delete-label-value traits: type: json-merge-patch properties: metadata: labels: deploy-label-key: deploy-label-added-value spec: replicas: 3 template: metadata: labels: pod-label-key: pod-label-modified-value to-delete-label-key: null spec: containers: name: busybox-new image: busybox:1.34 command: ["sleep", "864000"] ```
Project: FoundationDB (App Definition and Development / Database)
File: pull_request_template.md

Replace this text with your description here... The general pull request guidelines can be found . Please check each of the following things and check all boxes before accepting a PR. [ ] The PR has a description, explaining both the problem and the solution. [ ] The description mentions which forms of testing were done and the testing seems reasonable. [ ] Every function/class/actor that was touched is reasonably well documented. If this PR is made against a release-branch, please also check the following: [ ] This change/bugfix is a cherry-pick from the next younger branch (younger `release-branch` or `main` if this is the youngest branch) [ ] There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)
Project: YugabyteDB (App Definition and Development / Database)
File: ulimit.md

<!-- +++ private = true +++ --> {{< note title="Note" >}} The build may fail with "too many open files". In that case, increase the nofile limit in `/etc/security/limits.conf` as follows: ```sh echo "* - nofile 1048576" | sudo tee -a /etc/security/limits.conf ``` Start a new shell session, and check the limit increase with `ulimit -n`. {{< /note >}}
Project: Metal³ (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<!-- please add a icon to the title of this PR and delete this line and similar ones --> <!-- the icon will be either (:warning:, major or breaking changes), (:sparkles:, feature additions), (:bug:, patch and bugfixes), (:book:, documentation or proposals), or (:seedling:, minor or other) --> What this PR does / why we need it: Which issue(s) this PR fixes (optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged): Fixes #
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_deployments.md

title: "Command - devspace list deployments" sidebar_label: devspace list deployments Lists and shows the status of all deployments ``` devspace list deployments [flags] ``` ``` Shows the status of all deployments ``` ``` -h, --help help for deployments ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-11766.en.md

Implemented a preliminary Role-Based Access Control for the REST API. In this version, there are three predefined roles: Administrator: This role could access all resources. Viewer: This role can only view resources and data, corresponding to all GET requests in the REST API. Publisher: This role is special for MQTT messages publish, it can only access publish-related endpoints.
Project: KICS (Provisioning / Security & Compliance)
File: 4bb76f17-3d63-4529-bdca-2b454529d774.md

title: CloudTrail Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4bb76f17-3d63-4529-bdca-2b454529d774 Query name: CloudTrail Logging Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Checks if logging is enabled for CloudTrail.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "aws_cloudtrail" "positive1" { name = "positive" s3bucketname = "bucketlog" enable_logging = false } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_cloudtrail" "negative1" { name = "negative_1" s3bucketname = "bucketlog" enable_logging = true } resource "aws_cloudtrail" "negative2" { name = "negative_2" s3bucketname = "bucketlog" } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.158.md

layout: release date: 2023-10-15 tag: v0.6.158 Adjust link to attach properly to the 'catalog of curated design templates' text @MeenuyD (#9051) meshery-operator v0.6.13 @leecalcote (#9099) Upgrade asaskevich/govalidator @leecalcote (#9101) cuelang.org/go v0.6.0 @leecalcote (#9097) Bump golang.org/x/net from 0.9.0 to 0.17.0 in /scripts/component_updater @dependabot (#9081) Upgrade lib/pq @leecalcote (#9102) [Deps] Golang: golang.org/x/net upgrade @leecalcote (#9110) [Dependency] Component Updater: x.net @leecalcote (#9109) meshkit v0.6.72 @leecalcote (#9098) change k8s context switch background color @AkashKumar7902 (#8727) [UI] Upgrade to notistack v3 w/no MUI v5 dependency @leecalcote (#9112) [UI] Deps: "react-redux": "^8.1.3", @leecalcote (#9111) Thank you to our contributors for making this release possible: @AkashKumar7902, @MeenuyD, @dependabot, @dependabot[bot] and @leecalcote