cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.3.3.3.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Building MapReduce NativeTask fails on Fedora 34+ | Major | build, nativetask | Kengo Seki | Kengo Seki | | | Improve the description of dfs.block.scanner.volume.bytes.per.second | Minor | documentation, hdfs | guophilipse | guophilipse | | | Refactor tests in TestFileUtil | Trivial | common | Gautham Banasandra | Gautham Banasandra | | | Replace log4j 1.x with reload4j | Major | . | Wei-Chiu Chuang | Wei-Chiu Chuang | | | Print the exception when reporting a bad block | Major | datanode | qinyuren | qinyuren | | | Update BUILDING.txt | Minor | build, documentation | Steve Loughran | | | | Fix typos in distcp | Minor | documentation | guophilipse | guophilipse | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Upgrade commons-codec to 1.15 | Minor | . | Dongjoon Hyun | Dongjoon Hyun | | | Fails to build using Maven 3.8.1 | Major | build | Wei-Chiu Chuang | Viraj Jasani | | | Upgrade jackson to 2.13.2 and jackson-databind to 2.13.2.2 | Major | . | PJ Fanning | PJ Fanning | | | SlotReleaser should reuse the domain socket based on socket paths | Major | hdfs-client | Quanlong Huang | | | | Ensure that default permissions of directories under internal ViewFS directories are the same as directories on target filesystems | Major | viewfs | Chentao Yu | Chentao Yu | | | Fix thread safety of EC decoding during concurrent preads | Critical | dfsclient, ec, erasure-coding | daimin | daimin | | | ReverseXML processor doesn't accept XML files without the SnapshotDiffSection. | Critical | hdfs | yanbin.zhang | yanbin.zhang | | | [SBN read] Avoid purging edit log which is in progress | Critical | . | Tao Li | Tao Li | | | YARN WebAppProxyServlet should support connection timeout to prevent proxy server from hanging | Critical | . | Qi Zhu | Qi Zhu | | | Source path with storagePolicy cause wrong typeConsumed while rename | Major | hdfs, namenode | lei w | lei w | | | YARN incorrectly validates maximum capacity resources on the validation API | Major | . | Benjamin Teke | Benjamin Teke | | | Explicitly declare serialVersionUID in LogMutation class | Major | . | Benjamin Teke | Benjamin Teke | | | Unable to unregister FsDatasetState MBean if DataNode is shutdown twice | Trivial | datanode | Wei-Chiu Chuang | Wei-Chiu Chuang | | | \`org.wildfly.openssl\` should not be shaded by Hadoop build | Major | build | Andr F. | Andr F. | | | create-release fails fatal: unsafe repository ('/build/source' is owned by someone else) | Major | build | Steve Loughran | Steve Loughran | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Utility to identify git commit / Jira fixVersion discrepancies for RC preparation | Major | . | Viraj Jasani | Viraj Jasani |
Project: YugabyteDB (App Definition and Development / Database)
File: func_currval.md

title: currval() function [YSQL] headerTitle: currval() linkTitle: currval() description: Returns the last value returned by the nextval() function for the specified sequence in the current session. menu: v2.18: identifier: api-ysql-exprs-currval parent: api-ysql-exprs type: docs Use the `currval( sequencename )` function to return the last value returned by the `nextval( sequencename )` function for the specified sequence in the current session. Specify the name of the sequence. An error is raised if `nextval( sequence_name )` has not been called for the specified sequence in the current session. ```plpgsql yugabyte=# CREATE SEQUENCE s; ``` ``` CREATE SEQUENCE ``` Call `nextval()`. ```plpgsql yugabyte=# SELECT nextval('s'); ``` ``` nextval 1 (1 row) ``` ```plpgsql yugabyte=# SELECT currval('s'); ``` ``` currval 1 (1 row) ``` Call `currval()` before `nextval()` is called. ```plpgsql yugabyte=# CREATE SEQUENCE s2; ``` ``` CREATE SEQUENCE ``` ```plpgsql SELECT currval('s2'); ``` ``` ERROR: currval of sequence "s2" is not yet defined in this session ```
Project: ArangoDB (App Definition and Development / Database)
File: tryv_failure_likely.md

+++ title = "`BOOSTOUTCOMETRYVFAILURELIKELY(expr)/BOOSTOUTCOMETRYFAILURELIKELY(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 . The difference between the `BOOSTOUTCOMETRYV(expr)` and `BOOSTOUTCOMETRY(expr)` editions is that the latter will set a variable if two or more macro arguments are present (see {{% api "BOOSTOUTCOMETRY(var, expr)" %}}). The former requires the `T` to be `void`. Hints are given to the compiler that the expression will be unsuccessful. If you expect success, you should use {{% api "BOOSTOUTCOMETRYV(expr)" %}} instead. An internal temporary to hold the value of the expression is created, which generally invokes a copy/move. Overridable: Not overridable. Definition: Firstly the expression's temporary is bound to a uniquely named, stack allocated, `auto &&`. 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: StarRocks (App Definition and Development / Database)
File: SHOW_SQLBLACKLIST.md

displayed_sidebar: "English" Shows the SQL regular expressions in the SQL blacklist. For more about SQL Blacklist, see . :::tip This operation requires the SYSTEM-level BLACKLIST privilege. You can follow the instructions in to grant this privilege. ::: ```SQL SHOW SQLBLACKLIST ``` | Return | Description | | - | | | Index | The index number of the SQL regular expression that has been added to the blacklist. | | Forbidden SQL | The SQL regular expression that has been added to the blacklist. | ```Plain mysql> SHOW SQLBLACKLIST; +-+--+ | Index | Forbidden SQL | +-+--+ | 1 | select count\(\*\) from .+ | | 2 | select idint \* 4, idtinyint, idvarchar from testalltypenullable except select idint, idtinyint, idvarchar from testbasic except select \(idint \* 9 \- 8\) \/ 2, idtinyint, idvarchar from testalltypenullable2 except select idint, idtinyint, idvarchar from testbasic_nullable | | 3 | select idint from testalltypeselect1 order by id_int limit [1-7], [5-7] | | 4 | select count\(distinct .+\) from .+ | +-+--+ ```
Project: ClickHouse (App Definition and Development / Database)
File: asynchronous_insert_log.md

slug: /en/operations/system-tables/asynchronousinsertlog Contains information about async inserts. Each entry represents an insert query buffered into an async insert query. To start logging configure parameters in the section. The flushing period of data is set in `flushintervalmilliseconds` parameter of the server settings section. To force flushing, use the query. ClickHouse does not delete data from the table automatically. See for more details. Columns: `hostname` () Hostname of the server executing the query. `event_date` () The date when the async insert happened. `event_time` () The date and time when the async insert finished execution. `eventtimemicroseconds` () The date and time when the async insert finished execution with microseconds precision. `query` () Query string. `database` () The name of the database the table is in. `table` () Table name. `format` () Format name. `query_id` () ID of the initial query. `bytes` () Number of inserted bytes. `exception` () Exception message. `status` () Status of the view. Values: `'Ok' = 1` Successful insert. `'ParsingError' = 2` Exception when parsing the data. `'FlushError' = 3` Exception when flushing the data. `flush_time` () The date and time when the flush happened. `flushtimemicroseconds` () The date and time when the flush happened with microseconds precision. `flushqueryid` () ID of the flush query. Example Query: ``` sql SELECT * FROM system.asynchronousinsertlog LIMIT 1 \G; ``` Result: ``` text hostname: clickhouse.eu-central1.internal event_date: 2023-06-08 event_time: 2023-06-08 10:08:53 eventtimemicroseconds: 2023-06-08 10:08:53.199516 query: INSERT INTO public.dataguess (userid, datasource_id, timestamp, path, type, num, str) FORMAT CSV database: public table: data_guess format: CSV query_id: b46cd4c4-0269-4d0b-99f5-d27668c6102e bytes: 133223 exception: status: Ok flush_time: 2023-06-08 10:08:55 flushtimemicroseconds: 2023-06-08 10:08:55.139676 flushqueryid: cd2c1e43-83f5-49dc-92e4-2fbc7f8d3716 ``` See Also Description of the `query_log` system table which contains common information about queries execution. This table contains information about pending asynchronous inserts in queue.
Project: MongoDB (App Definition and Development / Database)
File: task_ownership_tags.md

This document describes task ownership tags that are used in `mongodb-mongo-master` and `mongodb-mongo-master-nightly` projects. Every task in in `mongodb-mongo-master` and `mongodb-mongo-master-nightly` projects should be tag with exactly one `assignedtojirateam.+` tag. Team names (the part after `assignedtojirateam`) should match `evergreentagname` from team configurations in . This is enforced by linter. YAML linter configuration could be found . If the linter configuration is missing your team: Make sure that your team configuration exists or add it in mothra Make sure that your team configuration in mothra has `evergreentagname` Update the tag list with `assignedtojirateam{evergreentagname}` tag for your team
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.54.md

layout: release date: 2023-02-23 tag: v0.6.54 language: en [RJSF] Handle Non-RJSF compliant fields @Abhishek-kumar09 (#7176) [chore] Clean up Makefile @acald-creator (#7162) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @acald-creator and @leecalcote
Project: Druid (App Definition and Development / Database)
File: human-readable-byte.md

id: human-readable-byte title: "Human-readable Byte Configuration Reference" <!-- ~ 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 page documents configuration properties related to bytes. These properties can be configured through 2 ways: a simple number in bytes a number with a unit suffix Given that cache size is 3G, there's a configuration as below ```properties druid.cache.sizeInBytes=3000000000 ``` When you have to put a large number for some configuration as above, it is easy to make a mistake such as extra or missing 0s. Druid supports a better way, a number with a unit suffix. Given a disk of 1T, the configuration can be ```properties druid.segmentCache.locations=[{"path":"/segment-cache-00","maxSize":"1t"},{"path":"/segment-cache-01","maxSize":"1200g"}] ``` Note: in above example, both `1t` and `1T` are acceptable since it's case-insensitive. Also, only integers are valid as the number part. For example, you can't replace `1200g` with `1.2t`. In the world of computer, a unit like `K` is ambiguous. It means 1000 or 1024 in different contexts, for more information please see . To make it clear, the base of units are defined in Druid as below | Unit | Description | Base | |||| | K | Kilo Decimal Byte | 1_000 | | M | Mega Decimal Byte | 1000000 | | G | Giga Decimal Byte | 1000000_000 | | T | Tera Decimal Byte | 1000000000000 | | P | Peta Decimal Byte | 1000000000000_000 | | Ki | Kilo Binary Byte | 1024 | | Mi | Mega Binary Byte | 1024 * 1024 | | Gi | Giga Binary Byte | 1024 1024 1024 | | Ti | Tera Binary Byte | 1024 1024 1024 * 1024 | | Pi | Peta Binary Byte | 1024 1024 1024 1024 1024 | | KiB | Kilo Binary Byte | 1024 | | MiB | Mega Binary Byte | 1024 * 1024 | | GiB | Giga Binary Byte | 1024 1024 1024 | | TiB | Tera Binary Byte | 1024 1024 1024 * 1024 | | PiB | Peta Binary Byte | 1024 1024 1024 1024 1024 | Unit is case-insensitive. `k`, `kib`, `ki`, `KiB`, `Ki`, `kiB` are all acceptable. Here are some examples ```properties druid.cache.sizeInBytes=1g ``` ```properties druid.cache.sizeInBytes=256MiB ``` ```properties druid.cache.sizeInBytes=256Mi ```
Project: Rundeck (Provisioning / Automation & Configuration)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <community@rundeck.org>. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Meshery (Provisioning / Automation & Configuration)
File: pixie.md

layout: integration title: Pixie subtitle: Collaborative and visual infrastructure as code for Pixie image: /assets/img/integrations/pixie/icons/color/pixie-color.svg permalink: extensibility/integrations/pixie docURL: https://docs.meshery.io/extensibility/integrations/pixie description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: KICS (Provisioning / Security & Compliance)
File: 228c4c19-feeb-4c18-848c-800ac70fdfb7.md

title: Image Without Digest hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 228c4c19-feeb-4c18-848c-800ac70fdfb7 Query name: Image Without Digest Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Images should be specified together with their digests to ensure integrity<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8 113 60" resource "kubernetes_pod" "positive1" { metadata { name = "terraform-example" } spec { container { image = "uses-private-image" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } resource "kubernetes_pod" "positive2" { metadata { name = "terraform-example" } spec { container { name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } resource "kubernetes_pod" "positive3" { metadata { name = "terraform-example" } spec { container = [ { image = "uses-private-image" name = "example" env = { name = "environment" value = "test" } port = { container_port = 8080 } liveness_probe = { http_get = { path = "/nginx_status" port = 80 http_header = { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } ] dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "negative" { metadata { name = "terraform-example" } spec { container { image = "image@sha256:45b23dee08af5e43a7fea6c4cf9c25ccf269ee113168c19722f87876677c5cb" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ```
Project: Apache StreamPipes (App Definition and Development / Streaming & Messaging)
File: documentation.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. ~ --> <p align="center"> <img src="icon.png" width="150px;"/> </p> ${pipelineElementDescription} Add a detailed description here Describe the configuration parameters here
Project: KICS (Provisioning / Security & Compliance)
File: 7a01dfbd-da62-4165-aed7-71349ad42ab4.md

title: Response JSON Reference Does Not Exists (v3) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7a01dfbd-da62-4165-aed7-71349ad42ab4 Query name: Response JSON Reference Does Not Exists (v3) Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Response reference should exists on components field<br> ```json title="Positive test num. 1 - json file" hl_lines="14" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "404": { "$ref": "#/components/responses/NotRight" } } } } }, "components": { "schemas": { "Error": { "type": "object", "properties": { "code": { "type": "string" }, "message": { "type": "string" }, "required": [ "code", "message" ] } } }, "responses": { "NotFound": { "description": "Resource not found", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/Error" } } } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="12" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '404': "$ref": "#/components/responses/NotRight" components: schemas: Error: type: object properties: code: type: string message: type: string required: code message responses: NotFound: description: Resource not found content: application/json: schema: "$ref": "#/components/schemas/Error" ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "404": { "$ref": "#/components/responses/NotFound" } } } } }, "components": { "schemas": { "Error": { "type": "object", "properties": { "code": { "type": "string" }, "message": { "type": "string" }, "required": [ "code", "message" ] } } }, "responses": { "NotFound": { "description": "Resource not found", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/Error" } } } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '404': "$ref": "#/components/responses/NotFound" components: schemas: Error: type: object properties: code: type: string message: type: string required: code message responses: NotFound: description: Resource not found content: application/json: schema: "$ref": "#/components/schemas/Error" ```