cwielenb/CNCF-Dataset huggingface dataset:
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: 0001-python-version-3-6-plus.md

Status: accepted Date: 2020-10-20 Technical Story: https://github.com/theupdateframework/python-tuf/issues/1125 We are planning a refactor of tuf where: We do not want to try and support end-of-life versions of the language. We want to use modern language features, such as typing. We want to ease maintainer burden, by reducing the major language versions supported. Python 2.7 is end-of-life Python 3.5 is end-of-life Modern Python allows use of desirable features such as type hints Supporting end-of-life Python versions adds maintenance overhead Support Python 2.7 and 3.5+ Support Python 2.7 and 3.6+ Support Python 2.7 and 3.6+ (with polyfill modules) Support only Python 3.6+ Chosen option: "Support only Python 3.6+", because we want modern features and lower maintainer effort as we work to improve our codebase through the refactor effort. New modules should target Python 3.6+. Using modules to polyfill standard library features from Python 3.6+ feels untenable as more libraries are dropping support for EOL Python releases. Leaves major adopter and contributor without an actively developed client for some of their customers stuck on older Python versions.
Project: GraphScope (App Definition and Development / Database)
File: how_to_test.md

GraphScope is comprised of three engines targeting for different business scenario, and a coordinator that could bring them together, and a client for users to connect and perform various tasks. We already covered how to test for engines in Here in this guide we will focus on how to do the e2e test, where multiple engines will working together. Here we would use a prebuilt docker image with necessary dependencies installed. ```bash docker run --name dev -it --shm-size=4096m registry.cn-hongkong.aliyuncs.com/graphscope/graphscope-dev:latest ``` Please refer to to find more options to get a dev environment. With `gs` command-line utility, you can build all targets for GraphScope with a single command. ```bash python3 gsctl.py make install ``` Run a bunch of test cases that involves 3 engines ```bash python3 gsctl.py test e2e --local ``` Make sure you have installed. ```bash python3 gsctl.py make-image all ``` Executing this command will generate the corresponding images for each component. It would produce a couple of images like this :::{figure-md} <img src="../images/gs-images.png" alt="GraphScope Images" width="80%"> Images of GraphScope ::: Or you could choose to generate image for a specific component. For example ```bash python3 gsctl.py make-image analytical ``` Try `python3 gsctl.py make-image -h` for more available options. Please refer to to get a cluster if you doesn't have one. The tests would launch a couple of pods on your cluster, so you need to set appropriate environment variables to let it use your newly built image. Take our previous built image for example, which has an empty registry (or you could say it's `docker.io` by default), and tagged `latest` ```bash python3 gsctl.py test e2e --k8s --registry="docker.io" --tag="latest" ```
Project: StarRocks (App Definition and Development / Database)
File: radians.md

displayed_sidebar: "English" Converts `x` from an angle to a radian. ```Haskell REDIANS(x); ``` `x`: supports the DOUBLE data type. Returns a value of the DOUBLE data type. ```Plain mysql> select radians(90); +--+ | radians(90) | +--+ | 1.5707963267948966 | +--+ 1 row in set (0.00 sec) ```
Project: Druid (App Definition and Development / Database)
File: reset-cluster.md

id: reset-cluster title: "reset-cluster tool" <!-- ~ 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. --> The `reset-cluster` tool can be used to completely wipe out Apache Druid cluster state stored on Metadata and Deep storage. This is intended to be used in dev/test environments where you typically want to reset the cluster before running the test suite. `reset-cluster` automatically figures out necessary information from Druid cluster configuration. So the java classpath used in the command must have all the necessary druid configuration files. It can be run in one of the following ways. ``` java -classpath "/my/druid/lib/*" -Ddruid.extensions.loadList="[]" org.apache.druid.cli.Main \ tools reset-cluster \ [--metadataStore] \ [--segmentFiles] \ [--taskLogs] \ [--hadoopWorkingPath] ``` or ``` java -classpath "/my/druid/lib/*" -Ddruid.extensions.loadList="[]" org.apache.druid.cli.Main \ tools reset-cluster \ --all ``` Usage documentation can be printed by running following command. ``` $ java -classpath "/my/druid/lib/*" -Ddruid.extensions.loadList="[]" org.apache.druid.cli.Main help tools reset-cluster NAME druid tools reset-cluster - Cleanup all persisted state from metadata and deep storage. SYNOPSIS druid tools reset-cluster [--all] [--hadoopWorkingPath] [--metadataStore] [--segmentFiles] [--taskLogs] OPTIONS --all delete all state stored in metadata and deep storage --hadoopWorkingPath delete hadoopWorkingPath --metadataStore delete all records in metadata storage --segmentFiles delete all segment files from deep storage --taskLogs delete all tasklogs ```
Project: StarRocks (App Definition and Development / Database)
File: subdivide_bitmap.md

displayed_sidebar: "English" Splits a large bitmap into multiple sub-bitmaps. This function is mainly used to export bitmaps. Bitmaps that are too large will exceed the maximum packet size allowed in the MySQL protocol. This function is supported from v2.5. ```Haskell BITMAP subdivide_bitmap(bitmap, length) ``` `bitmap`: The bitmap that needs to be split, required. `length`: The maximum length of each sub-bitmap, required. Bitmaps larger than this value will be split into multiple small bitmaps. Returns multiple sub-bitmaps not larger than `length`. Suppose there is a table `t1`, in which the `c2` column is a BITMAP column. ```Plain -- Use bitmaptostring() to convert values in `c2` into a string. mysql> select c1, bitmaptostring(c2) from t1; ++-+ | c1 | bitmaptostring(c2) | ++-+ | 1 | 1,2,3,4,5,6,7,8,9,10 | ++-+ -- Split `c2` into small bitmaps whose maximum length is 3. mysql> select c1, bitmaptostring(subdividebitmap) from t1, subdividebitmap(c2, 3); +++ | c1 | bitmaptostring(subdivide_bitmap) | +++ | 1 | 1,2,3 | | 1 | 4,5,6 | | 1 | 7,8,9 | | 1 | 10 | +++ ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-container.1.md

% podman-container 1 podman\-container - Manage containers podman container subcommand The container command allows management of containers | Command | Man Page | Description | | | | - | | attach | | Attach to a running container. | | checkpoint | | Checkpoint one or more running containers. | | cleanup | | Clean up the container's network and mountpoints. | | clone | | Create a copy of an existing container. | | commit | | Create new image based on the changed container. | | cp | | Copy files/folders between a container and the local filesystem. | | create | | Create a new container. | | diff | | Inspect changes on a container's filesystem | | exec | | Execute a command in a running container. | | exists | | Check if a container exists in local storage | | export | | Export a container's filesystem contents as a tar archive. | | init | | Initialize a container | | inspect | | Display a container's configuration. | | kill | | Kill the main process in one or more containers. | | list | | List the containers on the system.(alias ls) | | logs | | Display the logs of a container. | | mount | | Mount a working container's root filesystem. | | pause | | Pause one or more containers. | | port | | List port mappings for the container. | | prune | | Remove all stopped containers from local storage. | | ps | | Print out information about containers. | | rename | | Rename an existing container. | | restart | | Restart one or more containers. | | restore | | Restore one or more containers from a checkpoint. | | rm | | Remove one or more containers. | | run | | Run a command in a container. | | runlabel | | Execute a command as described by a container-image label. | | start | | Start one or more containers. | | stats | | Display a live stream of one or more container's resource usage statistics. | | stop | | Stop one or more running containers. | | top | | Display the running processes of a container. | | unmount | | Unmount a working container's root filesystem.(Alias unmount) | | unpause | | Unpause one or more containers. | | update | | Update the cgroup configuration of a given container. | | wait | | Wait on one or more containers to stop and print their exit codes. | , ,
Project: Stolon (App Definition and Development / Database)
File: stolonctl_update.md

Update a cluster specification Update a cluster specification ``` stolonctl update [flags] ``` ``` -f, --file string file containing a complete cluster specification or a patch to apply to the current cluster specification -h, --help help for update -p, --patch patch the current cluster specification instead of replacing it ``` ``` --cluster-name string cluster name --kube-context string name of the kubeconfig context to use --kube-namespace string name of the kubernetes namespace to use --kube-resource-kind string the k8s resource kind to be used to store stolon clusterdata and do sentinel leader election (only "configmap" is currently supported) --kubeconfig string path to kubeconfig file. Overrides $KUBECONFIG --log-level string debug, info (default), warn or error (default "info") --metrics-listen-address string metrics listen address i.e "0.0.0.0:8080" (disabled by default) --store-backend string store backend type (etcdv2/etcd, etcdv3, consul or kubernetes) --store-ca-file string verify certificates of HTTPS-enabled store servers using this CA bundle --store-cert-file string certificate file for client identification to the store --store-endpoints string a comma-delimited list of store endpoints (use https scheme for tls communication) (defaults: http://127.0.0.1:2379 for etcd, http://127.0.0.1:8500 for consul) --store-key string private key file for client identification to the store --store-prefix string the store base prefix (default "stolon/cluster") --store-skip-tls-verify skip store certificate verification (insecure!!!) --store-timeout duration store request timeout (default 5s) ``` - stolon command line client
Project: ClickHouse (App Definition and Development / Database)
File: 85_bug-report.md

name: Bug report about: Wrong behavior (visible to users) in the official ClickHouse release. title: '' labels: 'potential bug' assignees: '' Please make sure that the version you're using is still supported (you can find the list ). You have to provide the following information whenever possible. Describe what's wrong A clear and concise description of what works not as it is supposed to. A link to reproducer in . Does it reproduce on the most recent release? Enable crash reporting Change "enabled" to true in "sendcrashreports" section in `config.xml`: ``` <sendcrashreports> <!-- Changing <enabled> to true allows sending crash reports to --> <!-- the ClickHouse core developers team via Sentry https://sentry.io --> <enabled>false</enabled> ``` How to reproduce Which ClickHouse server version to use Which interface to use, if it matters Non-default settings, if any `CREATE TABLE` statements for all tables involved Sample data for all these tables, use if necessary Queries to run that lead to an unexpected result Expected behavior A clear and concise description of what you expected to happen. Error message and/or stacktrace If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0-rc-4.md

layout: release date: 2021-02-25 tag: v0.5.0-rc-4 [Docs] Language separation for Functionality index @leecalcote (#2457) [mesheryctl] Create dedicated section for tokens in default config @aneeshnema (#2436) Improve provider capabilities loading @utkarsh-pro (#2452) Improve context view command output @utkarsh-pro (#2443) [UI]: Fixes chip and paper card in /management @Nikhil-Ladha (#2446) Updated response for loadReqBasePath @dhruv0000 (#2418) Fixed: Header Overlapping with sidebar @chinmaym07 (#2445) Fixed error 404 on installation page @Anita-ihuman (#2441) Jomefavourite#2304 @jomefavourite (#2388) Updated Suported Service Meshes table @bartkalanski (#2447)
Project: KICS (Provisioning / Security & Compliance)
File: 75480b31-f349-4b9a-861f-bce19588e674.md

title: S3 Bucket ACL Allows Read to Any Authenticated User hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 75480b31-f349-4b9a-861f-bce19588e674 Query name: S3 Bucket ACL Allows Read to Any Authenticated User Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: S3 Buckets should not be readable to any authenticated user<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" name: Create an empty bucket2 amazon.aws.aws_s3: bucket: mybucket mode: create permission: authenticated-read ``` ```yaml title="Negative test num. 1 - yaml file" name: Create an empty bucket amazon.aws.aws_s3: bucket: mybucket mode: create name: Create an empty bucket2 amazon.aws.aws_s3: bucket: mybucket mode: create permission: private ```
Project: Kraken (Provisioning / Container Registry)
File: ROADMAP.md

Kraken's performance goal is to be capable of distributing a 100GB blob to 10k hosts concurrently at 80% of host nic limit. Currently, Kraken works the best if blob is smaller than 10G, so some peers could become seeders soon, and help reduce load on origin cluster. If the blob is too big, peers joined later will spend extra effort to find openings in the network, and the topology they form would not be very balanced, negatively impacting download speed. To support extra large blobs, one possible solution is to let the cluster periodically rebalance itself to converge to a random regular graph, which in theory could guarantee high download speed for all participants. Kraken supports bi-directional TLS between all components for image tags, and bi-directional TLS between image builder and Kraken for all data. Uploaders can be autherized; and since blobs are content addressable, data integrity is protected. However, blob content in torrent traffic is not encrypted, so it's still vulnerable to eavesdropping. We plan to support TLS on torrent traffic. We are looking into integrating Kraken with Kubernetes, so Kraken can preheat hosts at the beginning of rolling upgrades, and speed up deployments. This would require a Kubernetes scheduler that supports in-place upgrade. Mutating tags is allowed, but the behavior is undefined. Replication probably won't trigger, and most tag lookups could still return the old tag due to caching. We plan to support tag mutation. Current visualization tool is based on agent logs. If feasible, we hope to support realtime visualization. Kraken's torrent library is based on a simplified version of BitTorrent, however it is not compatible with the BitTorrent protocol. We may investigate BitTorrent compatibility in the future.
Project: StarRocks (App Definition and Development / Database)
File: year.md

displayed_sidebar: "English" Returns the year part in a date and returns a value that ranges from 1000 to 9999. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT YEAR(DATETIME date) ``` ```Plain Text MySQL > select year('1987-01-01'); +--+ | year('1987-01-01 00:00:00') | +--+ | 1987 | +--+ ``` YEAR
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.11.md

RabbitMQ `3.10.11` is a maintenance release in the `3.10.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.2 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . This release of RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Stream unsubscription leaked metric counters. GitHub issue: Quorum queue replicas no longer try to contact their unreachable peers for metrics. Previously this could result in a 30-40s delay for certain HTTP API requests that list queue metrics if one or more cluster members were down or stopped. GitHub issues: , `rabbitmq-diagnostics status` now handles server responses where free disk space is not yet computed. This is the case with nodes early in the boot process. GitHub issue: When a plugin was enabled as a dependency (e.g. `rabbitmqshovel` as a dependency of `rabbitmqshovel_management`), CLI tools previously did not discover commands in such plugins. Only explicitly enabled or plugins were scanned for commands. This behavior was confusing. Now all enabled (explicitly or as a dependency) plugins are scanned. Contributed by @SimonUnge (AWS). GitHub issue: Addition of a stream member could fail if the node being added was very early in its boot process (and doesn't have a certain stream-related components started). GitHub issue: Support for "modified" disposition outcome used by some client libraries (such as QPid). GitHub issue: Management UI links now include "noopener" and "noreferrer" attributes to protect them against . Note that since management UI only includes a small number of external links to trusted resources, reverse tabnabbing is unlikely to affect most users. However, it can show up in security scanner results and become an issue in environments where a modified version of RabbitMQ is offered as a service. Contributed by @illotum (AWS). GitHub issue: Plugin could stop in environments where no static Shovels were defined and a specific sequence of events happens at the same time. Contributed by @gomoripeti. GitHub issue: When installation directory was overridden, the plugins directory did not respect the updated base installation path. GitHub issue: `ra` was upgraded `osiris` was upgraded `seshat` was upgraded `credentials_obfuscation` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.11.tar.xz` instead of the source tarball produced by GitHub.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.14.0.md

add missed logger level by @180909 in https://github.com/Edgenesis/shifu/pull/528 cleanup pipeline, use make for building and loading by @tomqin93 in https://github.com/Edgenesis/shifu/pull/534 rebase v0.13.0 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/527 Bump k8s.io/client-go from 0.26.1 to 0.26.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/518 Bump github.com/onsi/gomega from 1.27.1 to 1.27.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/517 Bump sigs.k8s.io/controller-runtime from 0.14.4 to 0.14.5 by @dependabot in https://github.com/Edgenesis/shifu/pull/519 Bump golang.org/x/crypto from 0.6.0 to 0.7.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/529 Bump github.com/onsi/ginkgo/v2 from 2.8.4 to 2.9.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/532 Bump github.com/briandowns/spinner from 1.22.0 to 1.23.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/530 Bump github.com/onsi/gomega from 1.27.2 to 1.27.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/535 Bump github.com/onsi/gomega from 1.27.3 to 1.27.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/537 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.13.0...v0.14.0
Project: StarRocks (App Definition and Development / Database)
File: default_catalog.md

displayed_sidebar: "English" This topic describes what the default catalog is, and how to query the internal data of StarRocks by using the default catalog. StarRocks 2.3 and later provide an internal catalog to manage the internal data of StarRocks. Each StarRocks cluster has only one internal catalog named `default_catalog`. Currently, you cannot modify the name of the internal catalog or create a new internal catalog. Connect your StarRocks cluster. If you use the MySQL client to connect the StarRocks cluster, you go to `default_catalog` by default after connecting. If you use JDBC to connect the StarRocks cluster, you can go directly to the destination database in the default catalog by specifying `defaultcatalog.dbname` when connecting. (Optional) Use to view databases: ```SQL SHOW DATABASES; ``` Or ```SQL SHOW DATABASES FROM <catalog_name>; ``` (Optional) Use to switch to the destination catalog in the current session: ```SQL SET CATALOG <catalog_name>; ``` Then, use to specify the active database in the current session: ```SQL USE <db_name>; ``` Or, you can use to directly go to the active database in the destination catalog: ```SQL USE <catalogname>.<dbname>; ``` Use to query internal data: ```SQL SELECT * FROM <table_name>; ``` If you do not specify the active database in the preceding steps, you can directly specify it in a select query: ```SQL SELECT * FROM <dbname>.<tablename>; ``` Or ```SQL SELECT * FROM defaultcatalog.<dbname>.<table_name>; ``` To query data in `olapdb.olaptable`, you can perform one of the following operations: ```SQL USE olap_db; SELECT * FROM olap_table limit 1; ``` Or ```SQL SELECT * FROM olapdb.olaptable limit 1; ``` Or ```SQL SELECT * FROM defaultcatalog.olapdb.olap_table limit 1; ``` To query data from external data sources, see .
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Registrar.md

/ / Registrar .Registrar `Registrar` listen: `CommandListener` catchall<`T`, `O`\>(`offer`, `handler`, `prio`, `options?`): `void` | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | : | :- | | `offer` | `CatchAllOffer` | | `handler` | <`T`, `O`\> | | `prio` | `number` | | `options?` | | `void` find<`T`, `O`\>(`route`, `fromPlugin?`, `noOverride?`): `Promise`<`Command`<`T`, `O`\>\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | : | :-- | | `route` | `string` | | `fromPlugin?` | `string` | | `noOverride?` | `boolean` | `Promise`<`Command`<`T`, `O`\>\> override<`T`, `O`\>(`route`, `fromPlugin`, `handler`, `options?`): `Promise`<`Command`<`T`, `O`\>\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `route` | `string` | | `fromPlugin` | `string` | | `handler` | `CommandOverrideHandler`<`T`, `O`\> | | `options?` | | `Promise`<`Command`<`T`, `O`\>\> subtree<`T`, `O`\>(`route`, `options`): `Command`<`T`, `O`\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `route` | `string` | | `options` | | `Command`<`T`, `O`\> subtreeSynonym<`T`, `O`\>(`route`, `masterTree`, `options?`): `void` | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `route` | `string` | | `masterTree` | `Command`<`T`, `O`\> | | `options?` | | `void` synonym<`T`, `O`\>(`route`, `handler`, `master`, `options?`): `void` | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | : | :- | | `route` | `string` | | `handler` | <`T`, `O`\> | | `master` | `Command`<`T`, `O`\> | | `options?` | | `void`