cwielenb/CNCF-Dataset huggingface dataset:
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.2.0.md

not push telemetry if no specified endpoint by @kris21he in https://github.com/Edgenesis/shifu/pull/264 fix alway get ip after telemetry failed by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/271 fix negative instruction timeout by @tomqin93 in https://github.com/Edgenesis/shifu/pull/278 Customized deviceShifu design by @saiyan86 and @seanli33056 in https://github.com/Edgenesis/shifu/pull/221 Bump k8s.io/client-go from 0.25.1 to 0.25.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/266 Added design for deviceShifu-plc4x by @BtXin in https://github.com/Edgenesis/shifu/pull/270 Update CODEOWNERS to include kris21he by @tomqin93 in https://github.com/Edgenesis/shifu/pull/272 PowerShell stub for deviceShifu by @tomqin93 in https://github.com/Edgenesis/shifu/pull/255 Use nightly tags for main branch by @tomqin93 in https://github.com/Edgenesis/shifu/pull/276 implement socket encoding and bufferlength by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/268 add telemetry source by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/269 Renamed telemetry collection to user metrics by @BtXin in https://github.com/Edgenesis/shifu/pull/274 Bump up Go version to 1.19.1 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/277 N/A @kris21he made their first contribution in https://github.com/Edgenesis/shifu/pull/264 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.1.1...v0.2.0
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.33.0.md

Bump github.com/minio/minio-go/v7 from 7.0.63 to 7.0.64 by @dependabot in https://github.com/Edgenesis/shifu/pull/762 Bump github.com/onsi/gomega from 1.29.0 to 1.30.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/763 Bump k8s.io/client-go from 0.28.3 to 0.28.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/765 Bump github.com/minio/minio-go/v7 from 7.0.64 to 7.0.65 by @dependabot in https://github.com/Edgenesis/shifu/pull/769 Bump github.com/onsi/ginkgo/v2 from 2.13.1 to 2.13.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/770 Bump golang.org/x/net from 0.18.0 to 0.19.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/772 remove IP retrieval process from usermetric by @tomqin93 in https://github.com/Edgenesis/shifu/pull/773 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.32.0...v0.33.0
Project: Apache CarbonData (App Definition and Development / Database)
File: carbon-pr-readme.md

<!-- 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. --> This code is heavily inspired by the similar tool in Apache Falcon. This section documents the process for reviewing and merging code changes contributed via Github pull requests. It assumes you have a clone of carbondata's Git repository. carbon_pr.py is a script that automates the process of accepting a code change into the project. It creates a temporary branch from apache/master, squashes the commits in the pull request, rewrites the commit message in the squashed commit to follow a standard format including information about each original commit, merges the squashed commit into the temporary branch, pushes the code to apache/trunk and closes the JIRA ticket. The push will then be mirrored to apache-github/master, which will cause the PR to be closed due to the pattern in the commit message. Note that the script will ask the user before executing remote updates (i.e. git push and closing JIRA ticket), so it can still be used even if the user wants to skip those steps. If you want to close JIRA issues using the script then you will need to install `jira` library. You can install it using `easy_install` with `sudo easy_install jira` or using pip with `pip install jira` The script requires two remotes to be configured - one for the github repo of the project(to download pull requests), and one for the git repo of the project(to push the changes). Add aliases for the remotes expected by the merge script: git remote add apache https://git-wip-us.apache.org/repos/asf/carbondata.git git remote add apache-github https://github.com/apache/carbondata.git If you execute the script without doing any setup, the script will output the commands that you need to execute to setup these remotes. Once the pull request is ready to be merged (it has been reviewed, feedback has been addressed, CI build has been successful and the branch merges cleanly into trunk): Run the merge script `python carbon_pr.py` Answer the questions prompted by the script. TIP: If you don't want to enter your jira credentials again and again then you can set the `JIRAUSERNAME` and `JIRAPASSWORD` environment variables and the script will use them instead of prompting for credentials.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: installation.md

title: "Installation" weight: 2 type: docs aliases: /dev/python/installation.html <!-- 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. --> {{< hint info >}} Python version (3.8, 3.9, 3.10 or 3.11) is required for PyFlink. Please run the following command to make sure that it meets the requirements: {{< /hint >}} ```bash $ python --version ``` Your system may include multiple Python versions, and thus also include multiple Python binary executables. You can run the following `ls` command to find out what Python binary executables are available in your system: ```bash $ ls /usr/bin/python* ``` To satisfy the PyFlink requirement regarding the Python environment version, you can choose to soft link `python` to point to your `python3` interpreter: ```bash ln -s /usr/bin/python3 python ``` In addition to creating a soft link, you can also choose to create a Python virtual environment (`venv`). You can refer to the documentation page for details on how to achieve that setup. If you dont want to use a soft link to change the system's `python` interpreter point to, you can use the configuration way to specify the Python interpreter. For specifying the Python interpreter used to compile the jobs, you can refer to the configuration . For specifying the Python interpreter used to execute the Python UDF, you can refer to the configuration . PyFlink is available in and can be installed as follows: {{< stable >}} ```bash $ python -m pip install apache-flink=={{< version >}} ``` {{< /stable >}} {{< unstable >}} ```bash $ python -m pip install apache-flink ``` {{< /unstable >}} You can also build PyFlink from source by following the . <span class="label label-info">Note</span> Starting from Flink 1.11, its also supported to run PyFlink jobs locally on Windows and so you could develop and debug PyFlink jobs on Windows.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.1.2.en.md

Release packages for Amazon Linux 2023 Unify the listener switch to `enable`, while being compatible with the previous `enabled`. Support HTTP API for setting alarm watermark of license. Add `/cluster/topology` HTTP API endpoint `GET` request to the endpoint returns the cluster topology: connections between RLOG core and replicant nodes. The Webhook/HTTP bridge has been refactored to its own Erlang application. This allows for more flexibility in the future, and also allows for the bridge to be run as a standalone application. Release packages for Debian 12. Updated `jq` dependency to version 0.3.10 which includes `oniguruma` library update to version 6.9.8 with few minor security fixes. Updated RocksDB version to 1.8.0-emqx-1 via ekka update to 0.15.6. Improve the speed of clients querying in HTTP API `/clients` endpoint with default parameters Avoid logging irrelevant error messages during EMQX shutdown. Fixes crash when updating binding with a non-integer port. Config value for `maxpacketsize` has a max value of 256MB defined by protocol. This is now enforced and any configuration with a value greater than that will break. Fix produces valid HOCON file when atom type is used. Remove unnecessary `"` from HOCON file. Avoid to create duplicated subscription by HTTP API or client in Stomp gateway Make the username and password params of CoAP client to optional in connection mode. Fix the issue of abnormal data statistics for LwM2M client. Consistently return `404` for `DELETE` operations on non-existent resources. Fix a bug where node configuration may fail to synchronize correctly when joining the cluster. Fixed an issue preventing plugins from starting/stopping after changing configuration via `emqx ctl conf load`. The `headers` default value in /prometheus API should be a map instead of a list. Fix while a WebSocket packet contains more than one MQTT packet, the order of MQTT packets will be reversed. Ensure that the range of percentage type is from 0% to 100%. Fix a typo in the log, when EMQX received an abnormal `PUBREL` packet, the `pubrel` was mistakenly typo as `pubrec`. Restored support for the special `$queue/` shared subscription. Fix `emqx_ctl cluster join`, `leave`, and `status` commands. Import additional configurations from EMQX backup file (`emqx ctl import` command): rule_engine (previously not imported due to the bug) topic_metrics (previously not implemented) slow_subs (previously not implemented). Improve startup order of EMQX applications. Simplify build scripts and improve code reuse. Import additional configurations from EMQX backup file (`emqx ctl import` command): rule_engine (previously not imported due to the bug) topic_metrics (previously not implemented) slow_subs (previously not implemented).
Project: KICS (Provisioning / Security & Compliance)
File: 268c65a8-58ad-43e4-9019-1a9bbc56749f.md

title: BOM - GCP PD hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 268c65a8-58ad-43e4-9019-1a9bbc56749f Query name: BOM - GCP PD Platform: GoogleDeploymentManager Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of Persistent Disk resources found. Persistent Disk is Google's local durable storage service, fully integrated with Google Cloud products, Compute Engine and Google Kubernetes Engine.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3 11 19 24 31" resources: type: compute.v1.disk name: disk-1-data properties: sizeGb: 10 zone: us-east1-c diskEncryptionKey: sha_256: 68b4caecf5d5130426a8b8f0222cdd7f31232b5c99a5bf0daf19099e26e2ec29 rawKey: SGVsbG8gZnJvbSBHb29nbGUgQ2xvdWQgUGxhdGZvcm0= type: compute.v1.disk name: disk-2-data properties: sizeGb: 10 zone: us-east1-c diskEncryptionKey: sha_256: 68b4caecf5d5130426a8b8f0222cdd7f31232b5c99a5bf0daf19099e26e2ec29 kmsKeyName: disk-crypto-key type: compute.v1.disk name: disk-3-data properties: sizeGb: 10 zone: us-east1-c type: compute.v1.disk name: disk-4-data properties: sizeGb: 10 zone: us-east1-c diskEncryptionKey: sha_256: 68b4caecf5d5130426a8b8f0222cdd7f31232b5c99a5bf0daf19099e26e2ec29 type: compute.v1.disk name: disk-5-data properties: sizeGb: 10 zone: us-east1-c diskEncryptionKey: sha_256: 68b4caecf5d5130426a8b8f0222cdd7f31232b5c99a5bf0daf19099e26e2ec29 rawKey: "" ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: vm-template4 type: compute.v1.instance properties: zone: us-central1-a machineType: zones/us-central1-a/machineTypes/n1-standard-1 disks: deviceName: boot type: PERSISTENT boot: true autoDelete: true initializeParams: sourceImage: projects/debian-cloud/global/images/family/debian-9 diskEncryptionKey: sha_256: 68b4caecf5d5130426a8b8f0222cdd7f31232b5c99a5bf0daf19099e26e2ec29 rawKey: SGVsbG8gZnJvbSBHb29nbGUgQ2xvdWQgUGxhdGZvcm0= networkInterfaces: network: global/networks/default ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: no-relative-monorepo-imports.md

Forbid relative imports that reach outside of the package in a monorepo. Add the rules as follows, it has no options: ```js "@backstage/no-relative-monorepo-imports": ["error"] ``` The following patterns are considered files used during development, and only need dependencies to be declared in devDependencies: ```python !src/ # Any files outside of src are considered dev files src//.test. src//.stories. src//__testUtils__/ src//__mocks__/ src/setupTests.* ``` Assuming an import from for example `plugins/bar/src/index.ts`: ```ts import { FooCard } from '../../foo'; import { FooCard } from '../../foo/src/components/FooCard'; ``` ```ts import { FooCard } from '@internal/plugin-foo'; // This is allowed by this rule, but not by no-forbidden-package-imports import { FooCard } from '@internal/plugin-foo/src/components/FooCard'; ```
Project: ArangoDB (App Definition and Development / Database)
File: tryv2_failure_likely.md

+++ title = "`BOOSTOUTCOMETRYV2FAILURELIKELY(spec, expr)`" description = "Evaluate an expression which results in an understood type, continuing execution if successful, immediately returning `tryoperationreturn_as(X)` from the calling function if unsuccessful." +++ Evaluate an expression which results in a type matching the following customisation points, continuing execution if successful, immediately returning {{% api "tryoperationreturn_as(X)" %}} from the calling function if unsuccessful: `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationhasvalue(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationreturnas(X)" %}} `BOOSTOUTCOMEV2NAMESPACE::`{{% api "tryoperationextractvalue(X)" %}} Default overloads for these customisation points are provided. See . Hints are given to the compiler that the expression will be unsuccessful. If you expect success, you should use {{% api "BOOSTOUTCOMETRYV(expr)" %}} instead. Overridable: Not overridable. Definition: Firstly the expression's temporary is bound to a uniquely named, stack allocated, `spec`. If that reference's bound object's `tryoperationhasvalue()` is false, immediately execute `return tryoperationreturnas(propagated unique reference);`, propagating the rvalue/lvalue/etc-ness of the original expression. Header: `<boost/outcome/try.hpp>`
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: coredns_plugins_repositories.md

CoreDNS plugins repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path/to/packages provided can contain metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple plugins packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your plugins packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.
Project: Parsec (Provisioning / Security & Compliance)
File: CONTRIBUTORS.md

This file aims to acknowledge the specific contributors referred to in the "Contributors to the Parsec project" copyright notice. Arm Ltd. Docker Inc. Mirantis Inc. Anton Antonov (@anta5010) Paul Howard (@paulhowardarm) Ionut Mihalcea (@ionut-arm) Hugues de Valon (@hug-dev) Jesper Brynolf (@Superhepper) Samuel Bailey (@sbailey-arm) Patrick Uiterwijk (@puiterwijk) Nicolas Stalder (@nickray) Edmund Grimley Evans (@egrimley-arm) Matt Davis (@MattDavis00) Mohamed Omar Asaker (@mohamedasaker-arm) Gowtham Suresh Kumar (@gowthamsk-arm) William Brown (@firstyear) Tomas Agustin Gonzalez Orlando (@tgonzalezorlandoarm)
Project: StarRocks (App Definition and Development / Database)
File: locate.md

displayed_sidebar: "English" This function is used for finding the location of a substring in a string (starting counting from 1 and measured in characters). If the third argument pos is specified, it will start to find positions of substr in strings below pos. If str is not found, it will return 0. ```Haskell INT locate(VARCHAR substr, VARCHAR str[, INT pos]) ``` ```Plain Text MySQL > SELECT LOCATE('bar', 'foobarbar'); +-+ | locate('bar', 'foobarbar') | +-+ | 4 | +-+ MySQL > SELECT LOCATE('xbar', 'foobar'); +--+ | locate('xbar', 'foobar') | +--+ | 0 | +--+ MySQL > SELECT LOCATE('bar', 'foobarbar', 5); +-+ | locate('bar', 'foobarbar', 5) | +-+ | 7 | +-+ ``` LOCATE
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_domain.md

title: DROP DOMAIN statement [YSQL] headerTitle: DROP DOMAIN linkTitle: DROP DOMAIN description: Use the DROP DOMAIN statement to remove a domain from the database. menu: v2.18: identifier: ddldropdomain parent: statements type: docs Use the `DROP DOMAIN` statement to remove a domain from the database. {{%ebnf%}} drop_domain {{%/ebnf%}} Specify the name of the domain. An error is raised if the specified domain does not exist (unless `IF EXISTS` is set). An error is raised if any objects depend on this domain (unless `CASCADE` is set). Do not throw an error if the domain does not exist. Automatically drop objects that depend on the domain such as table columns using the domain data type and, in turn, all other objects that depend on those objects. Refuse to drop the domain if objects depend on it (default). ```plpgsql yugabyte=# CREATE DOMAIN idx DEFAULT 5 CHECK (VALUE > 0); ``` ```plpgsql yugabyte=# DROP DOMAIN idx; ``` ```plpgsql yugabyte=# CREATE DOMAIN idx DEFAULT 5 CHECK (VALUE > 0); ``` ```plpgsql yugabyte=# CREATE TABLE t (k idx primary key); ``` ```plpgsql yugabyte=# DROP DOMAIN idx CASCADE; ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-011-state-store-api-parity.md

Accepted We reviewed parity of state store APIs . GetState APIs continue to have Single Key Get and Bulk Get APIs behaviour as current 0.10.0 version. SaveState API will continue to have one SaveState API endpoint. If user wants to save single key, same save state API will be used for passing single item in the bulk set. Potential issues arises if following new single key save state API is introduced: `Post : state/{storeName}/{key}` This will conflict with State Transaction API, if the key is "transaction" GetBulkState API, if the key is "bulk" So the decision is to continue the Save State API behaviour as current 0.10.0 version. Bulk Delete API might come in future versions based on the scenarios. No changes needed to bring the parity among state store APIs. APIs continue to remain same as current 0.10.0 version.
Project: Tetragon (Provisioning / Security & Compliance)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC