cwielenb/CNCF-Dataset huggingface dataset:
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

Welcome to Kubernetes. We are excited about the prospect of you joining our ! The Kubernetes community abides by the CNCF . Here is an excerpt: As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We have full documentation on how to get started contributing here: <! If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources --> Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. -->
Project: TiDB (App Definition and Development / Database)
File: 2023-04-15-ddl-pause-resume.md

Author: Tracking Issue: https://github.com/pingcap/tidb/issues/40041 https://github.com/pingcap/tidb/issues/18015 DDL jobs are running asynchronously in the background, which may take a very long time to execute. The Admin could cancel the running DDL job if necessary, for example, out of resource. As a DDL job may take a lot of effort, it could be a big waste to just cancel and restart the job. It has several stages and steps back in the yard to finish a DDL job, we may just pause it at some step and resume it right from that place. Also, such feature will benefit the Upgrade of the TiDB Cluster. Add two commands to pause and resume a long-running DDL job. In particularly: `admin pause ddl jobs 3,5;` The jobs (here are job 3 and job 5) should be in Running or Queueing(Wait) state. Other states should be rejected. `admin resume ddl jobs 3,5;` Only Paused jobs could be resumed. Other states should be rejected. There is no change on the architecture, just following the current one. The whole design is simple: Add pause/resume in parser Add builder in planner Add builder in executor Valid the job's state, and turn it to be Pausing, if `admin pause ...` by end user 4.1 Valid the state first, only Running job could be paused, just like `admin cancel ...` 4.2 Turn the state to be Pausing 4.3 Background worker will check the state, and turn the state to be Paused , then just return and stay in current stage; And this is what is different from `admin cancel ...` 4.4 Background worker will continue fetching the job and check the state, and keep doing nothing until the state changed 4.5 Specially, the Reorg state could take a long time (maybe minutes, even hours), we also need to check the state of the job, and stop the reorg accordingly Validate the job's state, and turn it to be Queueing, if `admin resume ...` by end user 5.1 After the job's state changes, the background worker should check the job's state and continue the work 5.2 No other actions should be taken Create an index `create index idxusr on tuser(name);` In another session, show the DDL jobs `admin show ddl jobs 15;` It will show 15 DDL jobs, change the number if you want to see more. And then, find the running one (job_id) you want to pause. Pause the job by `admin pause ddl jobs $jobid` - $jobid is what you get from upper step Resume the paused job Also, you can find the Paused jobs by (change the number if you want to see more): `admin show ddl jobs 15;` Then, reumse it by: `admin resume ddl jobs $job_id` None.
Project: StarRocks (App Definition and Development / Database)
File: RESTORE.md

displayed_sidebar: "English" Restores data to a specified database, table, or partition. Currently, StarRocks only supports restoring data to OLAP tables. RESTORE is an asynchronous operation. You can check the status of a RESTORE job using , or cancel a RESTORE job using . CAUTION Only users with the ADMIN privilege can restore data. In each database, only one running BACKUP or RESTORE job is allowed each time. Otherwise, StarRocks returns an error. ```SQL RESTORE SNAPSHOT <dbname>.<snapshotname> FROM <repository_name> [ ON ( <tablename> [ PARTITION ( <partitionname> [, ...] ) ] [ AS <table_alias>] [, ...] ) ] PROPERTIES ("key"="value", ...) ``` | Parameter | Description | | | | | db_name | Name of the database that the data is restored to. | | snapshot_name | Name for the data snapshot. | | repository_name | Repository name. | | ON | Name of the tables to restore. The whole database is restored if this parameter is not specified. | | PARTITION | Name of the partitions to be restored. The whole table is restored if this parameter is not specified. You can view the partition name using . | | PROPERTIES | Properties of the RESTORE operation. Valid keys:<ul><li>`backuptimestamp`: Backup timestamp. **Required**. You can view backup timestamps using .</li><li>`replicationnum`: Specify the number of replicas to be restored. Default: `3`.</li><li>`meta_version`: This parameter is only used as a temporary solution to restore the data backed up by the earlier version of StarRocks. The latest version of the backed up data already contains `meta version`, and you do not need to specify it.</li><li>`timeout`: Task timeout. Unit: second. Default: `86400`.</li></ul> | Example 1: Restores the table `backuptbl` in the snapshot `snapshotlabel1` from the `examplerepo` repository to the database `exampledb`, and the backup timestamp is `2018-05-04-16-45-08`. Restores one replica. ```SQL RESTORE SNAPSHOT exampledb.snapshotlabel1 FROM example_repo ON ( backup_tbl ) PROPERTIES ( "backup_timestamp"="2018-05-04-16-45-08", "replication_num" = "1" ); ``` Example 2: Restores partitions `p1` and `p2` of table `backuptbl` in `snapshotlabel2` and table `backuptbl2` from `examplerepo` to database `exampledb`, and rename `backuptbl2` to `new_tbl`. The backup timestamp is `2018-05-04-17-11-01`. Restores three replicas by default. ```SQL RESTORE SNAPSHOT exampledb.snapshotlabel2 FROM example_repo ON( backup_tbl PARTITION (p1, p2), backuptbl2 AS newtbl ) PROPERTIES ( "backup_timestamp"="2018-05-04-17-11-01" ); ```
Project: Druid (App Definition and Development / Database)
File: release-notes.md

id: release-notes title: "Release notes" <!-- ~ 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. --> <!--Replace {{DRUIDVERSION}} with the correct Druid version.--> Apache Druid {{DRUIDVERSION}} contains over $NUMBERFEATURES new features, bug fixes, performance enhancements, documentation improvements, and additional test coverage from $NUMBEROF_CONTRIBUTORS contributors. <!-- Replace {{MILESTONE}} with the correct milestone number. For example: https://github.com/apache/druid/issues?q=is%3Aclosed+milestone%3A28.0+sort%3Aupdated-desc+ --> See the for additional details, including bug fixes. Review the and before you upgrade to Druid {{DRUIDVERSION}}. If you are upgrading across multiple versions, see the page, which lists upgrade notes for the most recent Druid versions. <!-- This file is a collaborative work in process. Adding a release note to this file doesn't guarantee its presence in the next release until the release branch is cut and the release notes are finalized. This file contains the following sections: Important features, changes, and deprecations Functional area and related changes Upgrade notes and incompatible changes Please add your release note to the appropriate section and include the following: Detailed title Summary of the changes (a couple of sentences) aimed at Druid users Link to the associated PR If your release note contains images, put the images in the release-info/assets folder. For tips about how to write a good release note, see . --> This section contains important information about new and existing features. This section contains detailed release notes separated by areas. The following dependencies have had their versions bumped:
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.8.76-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : If tuple of NULLs, e.g. `(NULL, NULL)` is on the left hand side of `IN` operator with tuples of non-NULLs on the right hand side, e.g. `SELECT (NULL, NULL) IN ((0, 0), (3, 1))` return 0 instead of throwing an exception about incompatible types. The expression may also appear due to optimization of something like `SELECT (NULL, NULL) = (8, 0) OR (NULL, NULL) = (3, 2) OR (NULL, NULL) = (0, 0) OR (NULL, NULL) = (3, 1)`. This closes . (). Backported in : Disable settings `usehedgedrequests` and `asyncsocketfor_remote` because there is an evidence that it may cause issues. (). Backported in : Server might fail to start if `datatypedefault_nullable` setting is enabled in default profile, it's fixed. Fixes . (). Backported in : QueryAliasVisitor to prefer alias for ASTWithAlias if subquery was optimized to constant. Fixes . Fixes . (). Backported in : Fixed `Not found column` error when selecting from `MaterializeMySQL` with condition on key column. Fixes . (). Backported in : Fixed simple key dictionary from DDL creation if primary key is not first attribute. Fixes . (). Backported in : Fixed very rare (distributed) race condition between creation and removal of ReplicatedMergeTree tables. It might cause exceptions like `node doesn't exist` on attempt to create replicated table. Fixes . (). Backported in : Fix possible crash in case if `unknown packet` was received form remote query (with `asyncsocketfor_remote` enabled). Maybe fixes . (). Backported in : `ORDER BY` with `COLLATE` was not working correctly if the column is in primary key (or is a monotonic function of it) and the setting `optimizereadinorder` is not turned off. This closes . Workaround for older versions: turn the setting `optimizereadinorder` off. (). Backported in : Remove support for `argMin` and `argMax` for single `Tuple` argument. The code was not memory-safe. The feature was added by mistake and it is confusing for people. These functions can be reintroduced under different names later. This fixes and reverts . (). Backported in : Kafka storage may support `arrow` and `arrowstream` format messages. (). Backported in : - Bug fix for `deltaSum` aggregate function in counter reset case ... (). Backported in : Fix bug that does not allow cast from empty array literal, to array with dimensions greater than 1. Closes . (). Backported in : When modify column's default value without datatype, and this column is used as ReplacingMergeTree's parameter like column `b` in the below example, then the server will core dump: ``` CREATE TABLE altertest (a Int32, b DateTime) ENGINE = ReplacingMergeTree(b) ORDER BY a; ALTER TABLE altertest MODIFY COLUMN `b` DEFAULT now(); ``` the sever throw error: ``` 2021.04.22 09:48:00.685317 (). Backported in : Fix `columns` function when multiple joins in select query. Closes . (). Fix logical error in stress tests ().
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: use.md

Imports definitions from an external source for use in the current source file. The contents of a source file form a module. Multiple modules that share a common root can be combined into a single use clause by using `use some::root::{m1, m2::sub_module::{m3, m4}}` The `TREMOR_PATH` environment path variable is a `:` delimited set of paths. Each path is an absolute or relative path to a directory. When using relative paths - these are relative to the working directory where the `tremor` executable is executed from. The tremor standard library MUST be added to the path to be accessible to scripts.
Project: KICS (Provisioning / Security & Compliance)
File: 70b42736-efee-4bce-80d5-50358ed94990.md

title: Group With Privilege Escalation By Actions 'iam:AttachGroupPolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 70b42736-efee-4bce-80d5-50358ed94990 Query name: Group With Privilege Escalation By Actions 'iam:AttachGroupPolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:AttachGroupPolicy' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:AttachGroupPolicy", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: memory-swap.md

A limit value equal to memory plus swap. A unit can be b (bytes), k (kibibytes), m (mebibytes), or g (gibibytes). Must be used with the -m (--memory) flag. The argument value must be larger than that of -m (--memory) By default, it is set to double the value of --memory. Set number to -1 to enable unlimited swap. This option is not supported on cgroups V1 rootless systems.
Project: Clair (Provisioning / Security & Compliance)
File: ISSUE_TEMPLATE.md

<!-- Project discussion and other meta topics should be discussed on the mailing list or in the discussions section. GitHub issues are ONLY for bugs and features for the Clair API. Please first create an issue on your client's repository before opening one here. Are you using a development build of Clair? Your problem might be solved by switching to a stable release. --> <! your content here > <! your content here > <! your content here > <!-- Please attach or paste logs from both clair and clairctl. --> <!-- Issues that do not contain the Environment section are AUTOMATICALLY CLOSED. If you're making a feature request, please specify "N/A" under the environment section. Please note that issues against Clair v2 will be closed automatically unless someone has volunteered to work on it. --> Clair version/image: Clair client name/version: Host OS: Kernel (e.g. `uname -a`): Kubernetes version (use `kubectl version`): Network/Firewall setup:
Project: YugabyteDB (App Definition and Development / Database)
File: cloud-provider-config-issues.md

title: Troubleshoot cloud provider configuration issues headerTitle: linkTitle: Cloud provider configuration issues description: Troubleshoot issues encountered when configuring cloud providers for YugabyteDB Anywhere. menu: v2.18_yugabyte-platform: identifier: cloud-provider-config-issues parent: troubleshoot-yp weight: 15 type: docs You might encounter issues during configuration of cloud providers for YugabyteDB Anywhere. If you experience difficulties while troubleshooting, contact . You can diagnose and remedy a failure that occurred when as follows: Navigate to Tasks on the left-side menu. Sort the tasks by their status. Find your task of type Create Provider among the Failed tasks and click the corresponding See Details. On the Task details page shown in the following illustration, click Expand to view the diagnostic information: Typically, the failure is caused by your subscription not having enough quota on Azure to create the specific size VM cores in a specific region. To resolve the issue, increase the quota limit by following instructions provided in .
Project: ShardingSphere (App Definition and Development / Database)
File: CONTRIBUTING.md

You can report a bug, submit a new feature enhancement recommendation, or commit codes by a pull request. Before reporting a bug, please search from google to confirm that you cannot find any hint on it. Look at the to confirm this issue is not a duplicated one. a new issue. Define a clear and descriptive title for the issue. If a bug is reported, please provide information below: Details for reproduce bug step by step. Include SQL, configuration, expected results, actual results and tracing log. ShardingSphere and your OS version. Source code that reproduce the bug on GitHub, can be linked here. Stack trace if exception thrown. Screenshot and animated gif to help bug reproduce if necessary. Screenshot for CPU, Memory, Network and IO stat if performance issue. If enhancement recommendation reported, please provide information below: Details for enhancement behaviour. Explain why this enhancement is general feature for most developers. List similar features which already available in other product if possible. Both open source and commercial software are available. Assign label after issue created. Label should be bug, enhancement, discussion and so on. Please pay attention to the issue and provide more information during discuss. Please close issue when it is resolved. If you don't close it, we will close it after 3 days If this issue has new information, please reopen it again. Please note, issue can reopen which only closed by yourself. Please choose an interested issue, or create a new issue and then settle a correct label. Reply a deadline message to pickup this issue. Find a mentor in , he will give you feedback for design and implements. Fork to your GitHub repo and begin to work. Please follow , and complete check before pull request submit. Submit a pull request to master branch when finished. Mentor will do code review and discuss some details, include design, implement, performance and code style. Code will be merged until mentor accepted. Finally, congratulations that you have become the official contributor for Apache ShardingSphere.
Project: GraphScope (App Definition and Development / Database)
File: python_tutorials.md

We provide a set of comprehensive tutorials for Python users to get started with GraphScope. In the tutorials you could learn how to launch a session, to load graphs, and to run analytical analysis, interactive queries as well as graph neural network trainings using GAE, GIE and GLE in GraphScope. The tutorials are organized as jupyter notebooks. Users can try them in any jupyter notebook servers. You could play with those tutorials using our well-prepared jupyterlab environment in . All tutorials are listed as follows:
Project: StarRocks (App Definition and Development / Database)
File: TSC_members.md

See for the definition of these community contributor roles. chaoyli Dshadowzh imay kangkaisen trueeyu ABingHuang Astralidea caneGuy choury decster dirtysalt gengjun-git HangyuanLiu leeLeft liuyehcf meegoo miomiocat mofeiatwork nshangyiming satanson sduzh Seaven sevev silverbullet233 stdpain stephen-shelby wyb Youngwb ZiheLiu
Project: Vitess (App Definition and Development / Database)
File: api-server.md

VTAdmin uses to multiplex gRPC and HTTP traffic over a single port. Internally, VTAdmin has an adaptation layer (see ) that converts query parameters into protobuf messages, so that all HTTP and gRPC requests are powered by the same implementation. For a full listing of the available gRPC methods, see , and for a full listing of available HTTP routes, see .
Project: KICS (Provisioning / Security & Compliance)
File: dfa20ffa-f476-428f-a490-424b41e91c7f.md

title: Secret Expiration Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dfa20ffa-f476-428f-a490-424b41e91c7f Query name: Secret Expiration Not Set Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: Make sure that for all secrets the expiration date is set<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermkeyvault_secret" "positive1" { name = "secret-sauce" value = "szechuan" keyvaultid = azurermkeyvault.example.id tags = { environment = "Production" } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermkeyvault_secret" "negative1" { name = "secret-sauce" value = "szechuan" keyvaultid = azurermkeyvault.example.id tags = { environment = "Production" } expiration_date = "2020-12-30T20:00:00Z" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_gcs_describe.md

Describe a GCS YugabyteDB Anywhere storage configuration Describe a GCS storage configuration in YugabyteDB Anywhere ``` yba storage-config gcs describe [flags] ``` ``` -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere GCS storage configuration
Project: Beam (App Definition and Development / Streaming & Messaging)
File: distinct.md

title: "Distinct" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.util" class="Distinct" >}} Produces a collection containing distinct elements of the input collection. In the following example, we create a pipeline with two `PCollection`s of produce. We use `Distinct` to get rid of duplicate elements, which outputs a `PCollection` of all the unique elements. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_Distinct" show="distinct" >}} {{< /playground >}} counts the number of elements within each aggregation. {{< button-pydoc path="apache_beam.transforms.util" class="Distinct" >}}