cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 105e20dd-8449-4d71-95c6-d5dac96639af.md

title: Success Response Code Undefined for Trace Operation hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 105e20dd-8449-4d71-95c6-d5dac96639af Query name: Success Response Code Undefined for Trace Operation Platform: OpenAPI Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Trace should define the '200' successful code<br> ```json title="Positive test num. 1 - json file" hl_lines="12" { "openapi": "3.0.0", "info": { "title": "Simple API", "version": "1.0.0" }, "paths": { "/item": { "trace": { "operationId": "traceItem", "summary": "Trace item", "responses": { "default": { "description": "Error", "schema": { "$ref": "#/components/schemas/Error" } } } } } }, "components": { "schemas": { "Error": { "type": "object", "properties": { "code": { "type": "string" }, "message": { "type": "string" } }, "required": [ "code", "message" ] } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10" openapi: 3.0.0 info: title: Simple API version: 1.0.0 paths: "/item": trace: operationId: traceItem summary: Trace item responses: default: description: Error schema: "$ref": "#/components/schemas/Error" components: schemas: Error: type: object properties: code: type: string message: type: string required: code message ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API", "version": "1.0.0" }, "paths": { "/item": { "trace": { "operationId": "traceItem", "summary": "Trace item", "responses": { "200": { "description": "success" }, "default": { "description": "Success" } } }, "patch": { "operationId": "updateItem", "summary": "Update item", "responses": { "default": { "description": "Error", "schema": { "$ref": "#/components/schemas/Error" } } } } } }, "components": { "schemas": { "Error": { "type": "object", "properties": { "code": { "type": "string" }, "message": { "type": "string" } }, "required": [ "code", "message" ] } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API version: 1.0.0 paths: "/item": trace: operationId: traceItem summary: Trace item responses: "200": description: success default: description: Success patch: operationId: updateItem summary: Update item responses: default: description: Error schema: "$ref": "#/components/schemas/Error" components: schemas: Error: type: object properties: code: type: string message: type: string required: code message ```
Project: YDB (App Definition and Development / Database)
File: ensure.md

Checking for the user conditions: `Ensure()`: Checking whether the predicate is true at query execution. `EnsureType()`: Checking that the expression type exactly matches the specified type. `EnsureConvertibleTo()`: A soft check of the expression type (with the same rules as for implicit type conversion). If the check fails, the entire query fails. Arguments: An expression that will result from a function call if the check is successful. It's also checked for the data type in the corresponding functions. Ensure uses a Boolean predicate that is checked for being `true`. The other functions use the data type that can be obtained using the , or a string literal with a . An optional string with an error comment to be included in the overall error message when the query is complete. The data itself can't be used for type checks, since the data check is performed at query validation (or can be an arbitrary expression in the case of Ensure). To check the conditions based on the final calculation result, it's convenient to combine Ensure with . Examples ```yql SELECT Ensure( value, value < 100, "value out or range" ) AS value FROM my_table; ``` ```yql SELECT EnsureType( value, TypeOf(other_value), "expected value and other_value to be of same type" ) AS value FROM my_table; ``` ```yql SELECT EnsureConvertibleTo( value, Double?, "expected value to be numeric" ) AS value FROM my_table; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.100.md

layout: release date: 2023-06-30 tag: v0.6.100 Fix operator check in `system check` @alphaX86 (#7977) [Filters] Fix wasm filter binary upload issues @Abhishek-kumar09 (#7975) [bug] Fix GraphQL Query for Catalog content @theBeginner86 (#7985) [UI] Dark mode toggle switch text fix in user preferences section @HarshDobariya79 (#7962) [Filters] Add Support For Unpublish Filters in Server @theBeginner86 (#7970) [bug] Fix GraphQL Query for Catalog content @theBeginner86 (#7985) [CI] Update build-ui-and-server.yml @theBeginner86 (#7987) [CI] Update build-ui-and-server.yml @theBeginner86 (#7986) [Docs] Meshery Operator Update @leecalcote (#7983) [Filters] Add Support For Unpublish Filters in Server @theBeginner86 (#7970) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aisuko, @HarshDobariya79, @MUzairS15, @alphaX86, @l5io, @leecalcote, @theBeginner86 and l5io
Project: YugabyteDB (App Definition and Development / Database)
File: tablespaces-yugabyted.md

To create a local cluster with the preceding configuration, use the following yugabyted commands: ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP1>/yugabyte-data \ --listen=<IP1> \ --masterflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1a" \ --tserverflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1a" ``` ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP2>/yugabyte-data \ --listen=<IP2> \ --join=<IP1> \ --masterflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1b" \ --tserverflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1b" ``` ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP3>/yugabyte-data \ --listen=<IP3> \ --join=<IP1> \ --masterflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1c" \ --tserverflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1c" ``` ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP4>/yugabyte-data \ --listen=<IP4> \ --join=<IP1> \ --tserverflags "placementcloud=aws,placementregion=ap-south-1,placementzone=ap-south-1a" ``` ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP5>/yugabyte-data \ --listen=<IP5> \ --join=<IP1> \ --tserverflags "placementcloud=aws,placementregion=eu-west-2,placementzone=eu-west-2c" ``` ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP6>/yugabyte-data \ --listen=<IP6> \ --join=<IP1> \ --tserverflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1a" ``` ```sh ./bin/yugabyted start \ --base_dir=/home/yugabyte/<IP7>/yugabyte-data \ --listen=<IP7> \ --join=<IP1> \ --tserverflags "placementcloud=aws,placementregion=us-east-1,placementzone=us-east-1a" ``` After cluster creation, verify that the nodes have been created with the given configuration by navigating to the Tablet Servers page in the YB-Master UI.
Project: Kapitan (Provisioning / Automation & Configuration)
File: getting_started.md

Using our reference repositories you can easily get started with Kapitan repository is meant show you many working examples of things you can do with Kapitan. You can use this to get familiar with Kapitan ``` $ git clone git@github.com:kapicorp/kapitan-reference.git kapitan-templates $ cd kapitan-templates $ ./kapitan compile Compiled postgres-proxy (1.51s) Compiled tesoro (1.70s) Compiled echo-server (1.64s) Compiled mysql (1.67s) Compiled gke-pvm-killer (1.17s) Compiled prod-sockshop (4.74s) Compiled dev-sockshop (4.74s) Compiled tutorial (1.68s) Compiled global (0.76s) Compiled examples (2.60s) Compiled pritunl (2.03s) Compiled sock-shop (4.36s) ``` Using based cookiecutter ```shell pip3 install cruft ``` ```shell cruft create http://github.com/kapicorp/kapitan-reference --checkout cookiecutter --no-input Dependency https://github.com/kapicorp/generators.git: saved to system/lib Dependency https://github.com/kapicorp/generators.git: saved to system/generators/kubernetes Dependency https://github.com/kapicorp/generators.git: saved to system/generators/terraform Rendered inventory (1.74s) Compiled echo-server (0.14s) ``` !!! success "recommended" If you use the provided repository, we already package a `kapitan` shell script that wraps the docker command to run Kapitan ```shell $ ./kapitan compile Compiled postgres-proxy (1.51s) Compiled tesoro (1.70s) Compiled echo-server (1.64s) Compiled mysql (1.67s) Compiled gke-pvm-killer (1.17s) Compiled prod-sockshop (4.74s) Compiled dev-sockshop (4.74s) Compiled tutorial (1.68s) Compiled global (0.76s) Compiled examples (2.60s) Compiled pritunl (2.03s) Compiled sock-shop (4.36s) ``` ](https://github.com/kapicorp/kapitan/releases) !!! success "recommended" ](https://hub.docker.com/r/kapicorp/kapitan) ](https://github.com/kapicorp/kapitan/actions?query=workflow%3A%22Docker+Build+and+Push%22) === "Linux" ```shell alias kapitan="docker run -t --rm -u $(id -u) -v $(pwd):/src:delegated kapicorp/kapitan" kapitan -h ``` === "Mac" ```shell alias kapitan="docker run -t --rm -v $(pwd):/src:delegated kapicorp/kapitan" kapitan -h ``` === "Linux" ```shell sudo apt-get update && sudo apt-get install -y python3.8-dev python3-pip python3-yaml ``` === "Mac" ```shell brew install python3 libyaml libmagic ``` === "Linux" !!! note "" `kapitan` will be installed in `$HOME/.local/lib/python3.7/bin` ```shell pip3 install --user --upgrade kapitan ``` === "Mac" !!! note "" `kapitan` will be installed in `$HOME/Library/Python/3.7/bin` ```shell pip3 install --user --upgrade kapitan ``` !!! attention "not recommended" ```shell sudo pip3 install --upgrade kapitan ```
Project: YDB (App Definition and Development / Database)
File: topic-write.md

The `topic write` command writes messages to a topic from a file or `stdin`: ```bash {{ ydb-cli }} [connection options] topic write <topic-path> \ [--file STR] [--format STR] [--transform STR] \ [additional parameters...] ``` {% include %} `<topic-path>`: Topic path, the only required parameter. `--file VAL` (`-f VAL`): Read a stream of incoming messages and write them to a topic from the specified file. If not set, messages are read from `stdin`. `--format STR`: Format of the incoming message stream. Supported formats | Name | Description | | | `single-message`<br>(default) | The entire input stream is treated as a single message to be written to the topic. | | `newline-delimited` | A stream at the input contains multiple messages delimited with the `0x0A` newline character. | `--transform VAL`: Method for transforming messages. Defaults to `none`. Possible values: `base64`: Decode each message in the input stream from and write the output to the topic. If decoding fails, the command is aborted with an error. `none`: Write the contents of a message from the input stream to the topic byte by byte without transforming them. | Name | Description | | | `--delimiter STR` | Delimiter byte. The input stream is delimited into messages with the specified byte. Specified only if no `--format` is set. Specified as an escaped string. | | `--message-group-id STR` | Message group string ID. If not set, all messages generated from the input stream are assigned the same ID value as a hexadecimal string representation of a random three-byte integer. | | `--codec STR` | Codec used for message compression on the client before sending them to the server. Possible values: `RAW` (no compression, default), `GZIP`, and `ZSTD`. Compression causes higher CPU utilization on the client when reading and writing messages, but usually lets you reduce the volume of data transferred over the network and stored. When consumers read messages, they're automatically decompressed with the codec used when writing them, without specifying any special options. Make sure the specified codec is listed in the as supported. | {% include %} All the examples given below use a topic named `topic1`. Writing a terminal input to a single message Once the command is run, you can type any multi-line text and press `Ctrl+D` to input it. ```bash {{ ydb-cli }} -p quickstart topic write topic1 ``` Writing the contents of the `message.bin` file to a single message compressed with the GZIP codec ```bash {{ ydb-cli }} -p quickstart topic write topic1 -f message.bin --codec GZIP ``` Writing the contents of the `example.txt` file delimited into messages line by line ```bash {{ ydb-cli }} -p quickstart topic write topic1 -f example.txt --format newline-delimited ``` Writing a resource downloaded via HTTP and delimited into messages with tab characters ```bash curl http://example.com/resource | {{ ydb-cli }} -p quickstart topic write topic1 --delimiter "\t" ```
Project: KICS (Provisioning / Security & Compliance)
File: 98ce8b81-7707-4734-aa39-627c6db3d84b.md

title: Auto TLS Set To True hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 98ce8b81-7707-4734-aa39-627c6db3d84b Query name: Auto TLS Set To True Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: When using etcd commands, the '--auto-tls' should be set to false<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="21" apiVersion: apps/v1 kind: Deployment metadata: name: app-etcd-deployment spec: selector: matchLabels: app: app replicas: 1 template: metadata: labels: app: app version: v1 spec: serviceAccountName: database containers: name: database image: gcr.io/google_containers/etcd:v3.2.18 imagePullPolicy: IfNotPresent command: ["etcd"] args: ["--auto-tls=true"] nodeSelector: kubernetes.io/hostname: worker02 restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: apps/v1 kind: Deployment metadata: name: app-etcd-deployment spec: selector: matchLabels: app: app replicas: 1 template: metadata: labels: app: app version: v1 spec: serviceAccountName: database containers: name: database image: gcr.io/google_containers/etcd:v3.2.18 imagePullPolicy: IfNotPresent command: ["etcd"] args: [] nodeSelector: kubernetes.io/hostname: worker02 restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: apps/v1 kind: Deployment metadata: name: app-etcd-deployment spec: selector: matchLabels: app: app replicas: 1 template: metadata: labels: app: app version: v1 spec: serviceAccountName: database containers: name: database image: gcr.io/google_containers/etcd:v3.2.18 imagePullPolicy: IfNotPresent command: ["etcd", "--auto-tls=false"] args: [] nodeSelector: kubernetes.io/hostname: worker02 restartPolicy: OnFailure ```
Project: YugabyteDB (App Definition and Development / Database)
File: auth.md

title: AUTH linkTitle: AUTH description: AUTH menu: preview: parent: api-yedis weight: 2020 type: docs `AUTH` authenticates a client connection to Yugabyte YEDIS API. `AUTH password` This command authenticates a client connection to YugabyteDB's YEDIS API. YugabyteDB can be set up to require a password for clients to authenticate themselves. The password verification can be enforced by using the `CONFIG` command to set the intended password (See `CONFIG`). YEDIS allows for multiple passwords (up to 2) to be accepted. If the given `password` matches with any of the server configured password(s), server returns the status string "OK" and begins processing commands from the authenticated client. If the given `password` does not match with any of the server configured password(s), an error is raised Returns a status string if the password is accepted. Returns an error if the password is rejected. ```sh $ CONFIG SET requirepass "yugapass" ``` ``` "OK" ``` ```sh $ AUTH "yugapass" ``` ``` "OK" ``` ```sh $ AUTH "bad" ``` ``` "ERR: Bad Password." ``` ```sh $ CONFIG SET requirepass "yugapassA,yugapassB" ``` ``` "OK" ``` ```sh $ AUTH "yugapassA" ``` ``` "OK" ``` ```sh $ AUTH "yugapassB" ``` ``` "OK" ``` ```sh $ AUTH "yugapassC" ``` ``` "ERR: Bad Password." ```
Project: ShardingSphere (App Definition and Development / Database)
File: show-table-metadata.en.md

+++ title = "SHOW TABLE METADATA" weight = 11 +++ The `SHOW TABLE METADATA` syntax is used to query tabe metadata. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowTableMetadata ::= 'SHOW' 'TABLE' 'METADATA' tableName (',' tableName)* ('FROM' databaseName)? tableName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Columns | Description | |-|| | schema_name | database name | | table_name | table name | | type | metadata type | | name | metadata name | When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. Query matadata of multiple tables from specified database ```sql SHOW TABLE METADATA torder, torder1 FROM shardingdb; ``` ```sql mysql> SHOW TABLE METADATA torder, torder1 FROM shardingdb; +-++--+-+ | schemaname | tablename | type | name | +-++--+-+ | shardingdb | torder1 | COLUMN | orderid | | shardingdb | torder1 | COLUMN | userid | | shardingdb | torder_1 | COLUMN | status | | shardingdb | torder_1 | INDEX | PRIMARY | | shardingdb | torder | COLUMN | order_id | | shardingdb | torder | COLUMN | user_id | | shardingdb | torder | COLUMN | status | | shardingdb | torder | INDEX | PRIMARY | +-++--+-+ 8 rows in set (0.01 sec) ``` Query metadata of one table from specified database ```sql SHOW TABLE METADATA torder FROM shardingdb; ``` ```sql mysql> SHOW TABLE METADATA torder FROM shardingdb; +-++--+-+ | schemaname | tablename | type | name | +-++--+-+ | shardingdb | torder | COLUMN | order_id | | shardingdb | torder | COLUMN | user_id | | shardingdb | torder | COLUMN | status | | shardingdb | torder | INDEX | PRIMARY | +-++--+-+ 4 rows in set (0.00 sec) ``` Query metadata of multiple tables from current database ```sql SHOW TABLE METADATA torder, torder_1; ``` ```sql mysql> SHOW TABLE METADATA torder, torder_1; +-++--+-+ | schemaname | tablename | type | name | +-++--+-+ | shardingdb | torder1 | COLUMN | orderid | | shardingdb | torder1 | COLUMN | userid | | shardingdb | torder_1 | COLUMN | status | | shardingdb | torder_1 | INDEX | PRIMARY | | shardingdb | torder | COLUMN | order_id | | shardingdb | torder | COLUMN | user_id | | shardingdb | torder | COLUMN | status | | shardingdb | torder | INDEX | PRIMARY | +-++--+-+ 8 rows in set (0.00 sec) ``` Query metadata of one table from current database ```sql SHOW TABLE METADATA t_order; ``` ```sql mysql> SHOW TABLE METADATA t_order; +-++--+-+ | schemaname | tablename | type | name | +-++--+-+ | shardingdb | torder | COLUMN | order_id | | shardingdb | torder | COLUMN | user_id | | shardingdb | torder | COLUMN | status | | shardingdb | torder | INDEX | PRIMARY | +-++--+-+ 4 rows in set (0.01 sec) ``` `SHOW`, `TABLE`, `METADATA`, `FROM`
Project: Vitess (App Definition and Development / Database)
File: MAINTAINERS.md

This page lists all active maintainers and their areas of expertise. This can be used for routing PRs, questions, etc. to the right place. The following is the full list, alphabetically ordered. Andres Taylor () andres@planetscale.com Andrew Mason () amason@hey.com Arthur Schreiber () arthurschreiber@github.com Deepthi Sigireddi () deepthi@planetscale.com Derek Perkins () derek@nozzle.io Dirkjan Bussink () dbussink@planetscale.com Florent Poinsard () florent@planetscale.com Frances Thai () frances@planetscale.com Harshit Gangal () harshit.gangal@gmail.com Manan Gupta () manan@planetscale.com Matt Lord () mlord@planetscale.com Rohit Nayak () rohit@planetscale.com Shlomi Noach () shlomi@planetscale.com Tim Vaillancourt () tim@timvaillancourt.com Vicent Marti () vmg@planetscale.com deepthi, mattlord, derekperkins dkhenry, shlomi-noach, ajm188, vmg, GuptaManan100, frouioui rohit-nayak-ps, deepthi, mattlord systay, harshit-gangal, vmg, GuptaManan100, dbussink vmg systay, harshit-gangal, GuptaManan100, frouioui systay, harshit-gangal, GuptaManan100, frouioui, vmg, dbussink shlomi-noach, dbussink vmg deepthi, ajm188, GuptaManan100, dbussink harshit-gangal derekperkins, dkhenry, GuptaManan100, frouioui ajm188, notfelineit derekperkins, mattlord We thank the following past maintainers for their contributions. Alain Jobart () Alkin Tezuysal () Anthony Yeh () Dan Kozlowski () David Weitzman () Jon Tirsen () Leo X. Lin () Mali Akmanalp ( Michael Berlin () Michael Demmer () Michael Pawliszyn () Morgan Tocker () Paul Hemberger () Rafael Chacon () Sara Bee () Sugu Sougoumarane ()
Project: Vald (App Definition and Development / Database)
File: benchmark.md

This document will show and explain the benchmark of an approximate nearest neighbor on the Vald cluster, such as , and also explain how to perform the ann-benchmark test on your Vald cluster. If you want to perform load testing on the Vald cluster, please refer to . <!-- // TODO: uncomment when unit_bench.md is created. We also created a guideline of the unit benchmark testing, please refer to . --> In this document, we will perform the on Vald cluster. The test will perform on the whole Vald cluster, which means the request will broadcast to multiple Vald agents instead of a single Vald agent, and return the aggregated result. The result may be different from your environment due to the network configuration and overhead of the Vald cluster. In this document, we will also explain how to perform the ann-benchmark testing on your environment. Under construction... Under construction... Under construction...
Project: StarRocks (App Definition and Development / Database)
File: st_geometryfromtext.md

displayed_sidebar: "English" Converts a WKT (Well Known Text) to the corresponding memory geometry. ```Haskell GEOMETRY ST_GeometryFromText(VARCHAR wkt) ``` ```Plain Text MySQL > SELECT STAsText(STGeometryFromText("LINESTRING (1 1, 2 2)")); ++ | stastext(stgeometryfromtext('LINESTRING (1 1, 2 2)')) | ++ | LINESTRING (1 1, 2 2) | ++ ``` STGEOMETRYFROMTEXT,STGEOMFROMTEXT,ST,GEOMETRYFROMTEXT,GEOMFROMTEXT
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12561.en.md

Implement HTTP APIs to get the list of client's in-flight and mqueue messages. To get the first chunk of data: GET /clients/{clientid}/mqueue_messages?limit=100 GET /clients/{clientid}/inflight_messages?limit=100 Alternatively: GET /clients/{clientid}/mqueue_messages?limit=100&position=none GET /clients/{clientid}/inflight_messages?limit=100&position=none To get the next chunk of data: GET /clients/{clientid}/mqueue_messages?limit=100&position={position} GET /clients/{clientid}/inflight_messages?limit=100&position={position} Where {position} is a value (opaque string token) of "meta.position" field from the previous response. Mqueue messages are ordered according to their priority and queue (FIFO) order: from higher priority to lower priority. By default, all messages in Mqueue have the same priority of 0. In-flight messages are ordered by time at which they were inserted to the in-flight storage (from older to newer messages).
Project: OpenTofu (Provisioning / Automation & Configuration)
File: CHANGELOG.md

UPGRADE NOTES: NEW FEATURES: ENHANCEMENTS: Added `tofu test -json` types to website Machine-Readable UI documentation () Made `tofu plan` with `generate-config-out` flag replace JSON strings with `jsonencode` functions calls. () BUG FIXES: Fixed crash in gcs backend when using certain commands () Fix inmem backend crash due to missing struct field () Added a check in the `tofu test` to validate that the names of test run blocks do not contain spaces. () `tofu test` now supports accessing module outputs when the module has no resources. () Fixed support for provider functions in tests () Added a better error message on `for_each` block with sensitive value of unsuitable type. () For information on prior major and minor releases, see their changelogs: