cwielenb/CNCF-Dataset huggingface dataset:
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: 03-extension-types.md

id: extension-types title: Frontend System Extension Types sidebar_label: Extension Types description: Extension types provided by the frontend system and core features NOTE: The new frontend system is in alpha and is only supported by a small number of plugins. This section covers many of the available at your disposal when building Backstage frontend plugins. These are the extension types provided by the Backstage frontend framework itself. An API extension is used to add or override in the app. They are commonly used by plugins for both internal and shared APIs. There are also many built-in Api extensions provided by the framework that you are able to override. Components extensions are used to override the component associated with a component reference throughout the app. Navigation item extensions are used to provide menu items that link to different parts of the app. By default nav items are attached to the app nav extension, which by default is rendered as the left sidebar in the app. Page extensions provide content for a particular route in the app. By default pages are attached to the app routes extensions, which renders the root routes. Sign-in page extension have a single purpose - to implement a custom sign-in page. They are always attached to the app root extension and are rendered before the rest of the app until the user is signed in. Theme extensions provide custom themes for the app. They are always attached to the app extension and you can have any number of themes extensions installed in an app at once, letting the user choose which theme to use. Translation extension provide custom translation messages for the app. They can be used both to override the default english messages to custom ones, as well as provide translations for additional languages. These are the extension types provided by the Backstage core feature plugins. Creates entity cards to be displayed on the entity pages of the catalog plugin. Creates entity content to be displayed on the entity pages of the catalog plugin. Creates search result list items for different types of search results, to be displayed in search result lists.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.2.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Minor | publish all exposed ports to random ports when using bridge network* support -p and -P for bridge type network; | Critical | NM and service AM don't have updated status for reinitialized containers* In progress upgrade status may show READY state sooner than actual upgrade operations. External caller to upgrade API is recommended to wait minimum 30 seconds before querying yarn app -status. | Major | Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely* Improve transient container status accuracy for upgrade. | Major | DelegationTokenAuthenticationFilter get wrong doAsUser since it does not decode URL* Fix DelegationTokenAuthentication filter for incorrectly double encode doAs user parameter. | Major | Service AM support for decommissioning component instances* Component instance number is not linear increment when decommission feature is used. Application with assumption of linear increment component instance number maybe impacted by introduction of this feature. | Major | Serial number in BlockTokenSecretManager could overlap between different namenodes* NameNodes rely on independent block token key ranges to communicate block token identities to DataNodes and clients in a way that does not create conflicts between the tokens issued by multiple NameNodes. HDFS-6440 introduced the potential for overlaps in key ranges; this fixes the issue by creating 64 possible key ranges that NameNodes assign themselves to, allowing for up to 64 NameNodes to run safely. This limitation only applies within a single Namespace; there may be more than 64 NameNodes total spread among multiple federated Namespaces. | Blocker | Failed to load image from FSImageFile when downgrade from 3.x to 2.x* During a rolling upgrade from Hadoop 2.x to 3.x, NameNode cannot persist erasure coding information, and therefore a user cannot start using erasure coding feature until finalize is done. | Major | YARN Timeline Service v.2: beta 1 / GA* Application Timeline Server v2 is ready for production. It is GA from 3.2.1 release on wards.
Project: ArangoDB (App Definition and Development / Database)
File: on_outcome_copy_construction.md

+++ title = "`static void onoutcomecopy_construction(T *, U &&) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the converting copy constructors of `basic_outcome`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the converting copy constructors of `basicoutcome` (NOT the standard copy constructor). See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.
Project: TiDB (App Definition and Development / Database)
File: feature-request.md

name: "\U0001F680 Feature Request" about: As a user, I want to request a New Feature on the product. labels: type/feature-request Is your feature request related to a problem? Please describe: <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> Describe the feature you'd like: <!-- A clear and concise description of what you want to happen. --> Describe alternatives you've considered: <!-- A clear and concise description of any alternative solutions or features you've considered. --> Teachability, Documentation, Adoption, Migration Strategy: <!-- If you can, explain some scenarios how users might use this, situations it would be helpful in. Any API designs, mockups, or diagrams are also helpful. -->
Project: ClickHouse (App Definition and Development / Database)
File: v21.11.8.4-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix unexpected projection removal when detaching parts. (). Backported in : Some replication queue entries might hang for `temporarydirectorieslifetime` (1 day by default) with `Directory tmpmerge<part_name>` or `Part ... (state Deleting) already exists, but it will be deleted soon` or similar error. It's fixed. Fixes . (). Backported in : Fix sparse_hashed dict performance with sequential keys (wrong hash function). (). Backported in : Fix table lifetime (i.e. possible use-after-free) in case of parallel DROP TABLE and INSERT. (). Backported in : Fix possible exception at RabbitMQ storage startup by delaying channel creation. (). Backported in : Fix LOGICAL_ERROR when the target of a materialized view is a JOIN or a SET table. (). Backported in : fix crash when used fuzzBits with multiply same FixedString, Close . (). Fix data race in ProtobufSchemas (). Always apply const-condition-if optimization. ().
Project: YDB (App Definition and Development / Database)
File: PKCS11.md

To run the PKCS#11 tests, configure cmake with: `-DENABLEPKCS11TESTS=ON` and set the following environment variables: ``` TESTPKCS11LIB = <path-to-shared-lib> TESTPKCS11TOKEN_DIR = <path-to-softhsm-token-dir> ``` TESTPKCS11LIB is used by the tests to peform pkcs11 operations. TESTPKCS11TOKEN_DIR is used by the tests to clear the softhsm tokens before a test begins. This is achieved by cleaning the token directory <b>NOTE: Any tokens created outside the tests will be cleaned up along with all the objects/keys on it as part of the tests.</b> 1) Install via brew / apt / apt-get / yum: ``` > apt install softhsm ``` Check that it's working: ``` > softhsm2-util --show-slots ``` If this spits out an error message, create a config file: Default location: `~/.config/softhsm2/softhsm2.conf` This file must specify token dir, default value is: ``` directories.tokendir = /usr/local/var/lib/softhsm/tokens/ ``` 2) Set env vars like so: ``` TESTPKCS11LIB = <path to libsofthsm2.so> TESTPKCS11TOKEN_DIR = /usr/local/var/lib/softhsm/tokens/ ``` 3) [Example to import your keys, Not used by tests] Create token and private key You can use any values for the labels, pin, key, cert, CA etc. Here are copy-paste friendly commands for using files available in this repo. ``` > softhsm2-util --init-token --free --label my-test-token --pin 0000 --so-pin 0000 ``` Note which slot the token ended up in ``` > softhsm2-util --import tests/resources/unittests.p8 --slot <slot-with-token> --label my-test-key --id BEEFCAFE --pin 0000 ``` <b>WARN: All tokens created outside the tests would be cleaned up as part of the tests, Use a separate token directory for running the tests if you would like to keep your tokens intact.</b>
Project: StarRocks (App Definition and Development / Database)
File: bit_shift_right.md

displayed_sidebar: "English" Shifts the binary representation of a numeric expression to the right by a specified number of bits. This function performs a logical right shift, during which the bit length does not change, the low bit is dropped, and 0 is appended to the high bit despite whether the original bit is positive or negative. Logical shifts are unsigned shifts. For example, shifting `10101` by one bit results in `00101`. bitshiftright() and bitshiftright_logical() return the same result for a positive value. ```Haskell bitshiftright_logical(value, shift) ``` `value`: the value or numeric expression to shift. Supported data types are TINYINT, SMALLINT, INT, BIGINT, and LARGEINT. `shift`: the number of bits to shift. The supported data type is BIGINT. Returns a value of the same type as `value`. If any input parameter is NULL, NULL is returned. If `shift` is less than 0, 0 is returned. Shifting a `value` by `0` always results in the original `value`. Shifting `0` by a `shift` always results in `0`. If the data type of `value` is numeric but not an integer, that value will be cast to an integer. See . If the data type of `value` is a string, the value will be cast to an integer if possible. For example, the string "2.3" will be cast to 2. If the value cannot be cast to an integer, the value will be treated as NULL. See . Use this function to shift numeric values. ```Plain SELECT bitshiftright_logical(2, 1); +-+ | bitshiftright_logical(2, 1) | +-+ | 1 | +-+ SELECT bitshiftright_logical(2.2, 1); ++ | bitshiftright_logical(2.2, 1) | ++ | 1 | ++ SELECT bitshiftright_logical("2", 1); ++ | bitshiftright_logical('2', 1) | ++ | 1 | ++ SELECT bitshiftright_logical(cast('-2' AS INTEGER(32)), 1); +--+ | bitshiftright_logical(CAST('-2' AS INT), 1) | +--+ | 2147483647 | +--+ ```
Project: KICS (Provisioning / Security & Compliance)
File: 698a464e-bb3e-4ba8-ab5e-e6599b7644a0.md

title: Components Parameter Definition Is Unused hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 698a464e-bb3e-4ba8-ab5e-e6599b7644a0 Query name: Components Parameter Definition Is Unused Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: Components parameters definitions should be referenced or removed from Open API definition<br> ```json title="Positive test num. 1 - json file" hl_lines="22" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/Success" } } } } }, "components": { "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "max records to return", "required": true, "schema": { "type": "integer" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="15" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/components/schemas/Success" components: parameters: limitParam: name: limit in: query description: max records to return required: true schema: type: integer ``` ```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": { "200": { "$ref": "#/components/schemas/Success" } }, "parameters": [ { "$ref": "#/components/parameters/limitParam" } ] } } }, "components": { "parameters": { "limitParam": { "name": "limit", "in": "query", "description": "max records to return", "required": true, "schema": { "type": "integer" } } } } } ``` ```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: '200': "$ref": "#/components/schemas/Success" parameters: "$ref": "#/components/parameters/limitParam" components: parameters: limitParam: name: limit in: query description: max records to return required: true schema: type: integer ```
Project: KICS (Provisioning / Security & Compliance)
File: bb241e61-77c3-4b97-9575-c0f8a1e008d0.md

title: StatefulSet Without Service Name hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bb241e61-77c3-4b97-9575-c0f8a1e008d0 Query name: StatefulSet Without Service Name Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Availability URL: StatefulSets should have an existing headless 'serviceName'. The headless service labels should also be implemented on StatefulSets labels.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="26" apiVersion: v1 kind: Service metadata: name: nginx namespace: nginx labels: app: nginx2 spec: ports: port: 80 name: web clusterIP: All selector: app: nginx apiVersion: apps/v1 kind: StatefulSet metadata: name: web namespace: nginx spec: selector: matchLabels: app: nginx serviceName: "nginx" replicas: 3 template: metadata: labels: app: nginx spec: terminationGracePeriodSeconds: 10 containers: name: nginx image: k8s.gcr.io/nginx-slim:0.8 ports: containerPort: 80 name: web volumeMounts: name: www mountPath: /usr/share/nginx/html volumeClaimTemplates: metadata: name: www spec: accessModes: [ "ReadWriteOnce" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Service metadata: name: nginx2 namespace: nginx2 labels: app: nginx2 spec: ports: port: 80 name: web clusterIP: None selector: app: nginx2 apiVersion: apps/v1 kind: StatefulSet metadata: name: web2 namespace: nginx2 spec: selector: matchLabels: app: nginx2 serviceName: "nginx2" replicas: 3 template: metadata: labels: app: nginx2 foo: bar spec: terminationGracePeriodSeconds: 10 containers: name: nginx2 image: k8s.gcr.io/nginx-slim:0.8 ports: containerPort: 80 name: web volumeMounts: name: www mountPath: /usr/share/nginx/html volumeClaimTemplates: metadata: name: www spec: accessModes: [ "ReadWriteOnce" ] storageClassName: "my-storage-class" resources: requests: storage: 1Gi ```
Project: Percona Server for MySQL (App Definition and Development / Database)
File: LICENSE.md

MIT License Copyright (c) 2014-2017 Pavel Kalvoda Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Kapitan (Provisioning / Automation & Configuration)
File: talk.md

Our project needs your support to get noticed! Please let everyone know that you are using Kapitan :fontawesome-brands-github: Help us grow: Join us on kubernetes.slack.com* () Tweet about us on Twitter* . Remember to add to your tweets Share our website* Write tutorials and blog posts* and join the many who have done it already! Get published on the Share what Kapitan* does for you and for your company Inspire your colleagues and network on LinkedIn*
Project: ThreatMapper (Provisioning / Security & Compliance)
File: cve-2021-44228.md

title: Impact of CVE-2021-4428 As part of our periodic scan of our own images, we detected CVE-2021-44228 Log4j2 vulnerability in `deepfenceio/deepfenceelasticce:latest` image in package `/usr/share/elasticsearch/lib/log4j-core-2.11.1.jar`. Am I affected? If ThreatMapper console is installed as per the instructions and the deployment scripts provided, you are not affected. It assumes that security groups are set to receive traffic from agents/browser on port 443 and all other ports are locked down. However, we have set the appropriate flag (`-Dlog4j2.formatMsgNoLookups=true`) as recommended by . Please use the latest version of the code and update the container image `deepfenceio/deepfenceelasticce:latest` CVE-2021-44228 Exploitability and Attack Path Details Deepfence ThreatMapper can scan your images and hosts for this vulnerability. In addition, ThreatMapper can visually show the attack path for those containers and hosts which have an application that uses the vulnerable log4j library and are receiving external network traffic.
Project: CockroachDB (App Definition and Development / Database)
File: 20151213_dismantle_multiraft.md

Feature Name: dismantle_multiraft Status: completed Start Date: 2015-12-13 RFC PR: Cockroach Issue: Remove the `multiraft` abstraction and move its functionality directly to the `storage` package. The goal of this change is to simplify concurrency-related problems in the current code. The `multiraft` abstraction was originally designed to be reusable outside of cockroach, and to insulate the `storage` package from the details of the raft implementation. Experience has shown that instead, the two packages have become very tightly coupled. Certain information like the set of active raft groups is stored redundantly across the two packages, and keeping things in sync has required some very tricky concurrency code (and we have not yet resolved all such bugs). The move from `raft.MultiNode` to `raft.RawNode` gives us an opportunity to move raft functionality to the `storage.Replica`, making it much easier to synchronize raft operations with other parts of the system. The "multi" part of `multiraft` will be moved to methods on `storage.Store`. This includes routing messages to the right `Replica`, and all functionality related to timers and coalesced heartbeats. The `Store.replicas` map becomes the source of truth for looking up raft groups. `storage.Replica` will contain a `raft.RawNode` directly. Other data contained in the `multiraft.group` struct will be replaced by the corresponding fields of `Replica` (including the range descriptor and the `pendingCmds` map). This change generally means a move away from special goroutines and channels. Instead, the existing `Mutexes` in `Store` and `Replica` will be used for concurrency. This may eventually allow for greater concurrency, although the initial implementation will use fairly coarse locking to ensure correctness. The `Store.processRaft` goroutine will still be used for some things, especially the timer loop. This adds complexity to the already-large `storage` package. This proposal resolves the tension between the `Mutex`-based `storage` package and the channel-based `multiraft` package by emphasizing locks. There may be another equilibrium based on channels instead, although it is probably a greater distance from our current implementation.
Project: Meshery (Provisioning / Automation & Configuration)
File: feature_request.md

name: General Feature Request about: Suggest an enhancement to Meshery. title: '' labels: 'kind/enhancement' assignees: '' <!-- A brief description of what the problem is. (e.g. I need to be able to...) --> <!-- A brief description of the enhancement. --> <!-- [Optional] Specifics on the approach to fulfilling the feature request. --> <!-- [Optional] Stipulations of functional behavior or non-functional items that must be in-place in order for the issue to be closed. --> <!-- [Optional] Any visual diagrams of the desired user interface. --> - Meshery documentation and Wireframes and designs for Meshery UI in Questions: and
Project: YugabyteDB (App Definition and Development / Database)
File: manage-runtime-config.md

title: Manage runtime configuration settings headerTitle: Manage runtime configuration settings linkTitle: Manage runtime configuration description: Manage your universes by setting runtime configuration keys based on different scopes. menu: v2.18_yugabyte-platform: identifier: manage-runtime-config parent: administer-yugabyte-platform weight: 50 type: docs YugabyteDB Anywhere has a runtime configuration mechanism that is fully compatible with the existing format and has the following additional properties: Runtime/Dynamic: The configuration keys can be set or changed at runtime via the API. Persistent: The site-specific configuration changes won't be lost in an install. Backwards compatibility: Fully compatible with the existing mechanism with default values residing in the file `application.conf` or `reference.conf`. Scoped: Configuration can be applied to a smaller scope, for example, even a single universe can be configured to have certain features. Hierarchical: Scopes are nested and allow for overriding outer scope values in the inner scope. Currently, the scopes can be categorized as follows: | Scope | Description | User Access | |: |: | : | | Global | Applies to the entire platform, persists across installs and any value defined in this scope overrides the defaults. | Super Admin | | Customer | Applies to a specific customer, persists across installs and any value defined in this scope overrides defaults in Global scope.| Super Admin, Admin | | Provider | Applies to a specific provider, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin, Admin | | Universe | Applies to a specific universe, persists across installs and any value defined in this scope overrides defaults in Customer scope. | Super Admin, Admin | For more details about the flags and their scopes, refer to the To modify the runtime configuration keys, in YugabyteDB Anywhere, navigate to Admin > Advanced to display the runtime configuration settings, similar to the following illustration: Note that only a Super Admin user has edit or reset access for Global configuration level keys, an Admin user has access for Customer, Provider, and Universe configuration level keys, and all other users only have read-only access. To modify the `Enforce Auth` runtime configuration key (applicable only at Global or Customer scope), perform the following steps: From your YugabyteDB Anywhere UI, navigate to Admin > Advanced and select the Global Configuration or Customer Configuration tab. In the Search bar, enter "Enforce Auth". Click Actions and choose Edit Configuration. Change the Config value to "True" and click Save. To verify the change, navigate to Universes, click Create Universe, and verify that for the Authentication Settings section, "Enable YSQL Auth" is not be displayed and you are must enter a password in the YSQL Password and Confirm Password fields.