cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: fixedstring.md

slug: /en/sql-reference/data-types/fixedstring sidebar_position: 10 sidebar_label: FixedString(N) A fixed-length string of `N` bytes (neither characters nor code points). To declare a column of `FixedString` type, use the following syntax: ``` sql <column_name> FixedString(N) ``` Where `N` is a natural number. The `FixedString` type is efficient when data has the length of precisely `N` bytes. In all other cases, it is likely to reduce efficiency. Examples of the values that can be efficiently stored in `FixedString`-typed columns: The binary representation of IP addresses (`FixedString(16)` for IPv6). Language codes (ruRU, enUS ). Currency codes (USD, RUB ). Binary representation of hashes (`FixedString(16)` for MD5, `FixedString(32)` for SHA256). To store UUID values, use the data type. When inserting the data, ClickHouse: Complements a string with null bytes if the string contains fewer than `N` bytes. Throws the `Too large value for FixedString(N)` exception if the string contains more than `N` bytes. When selecting the data, ClickHouse does not remove the null bytes at the end of the string. If you use the `WHERE` clause, you should add null bytes manually to match the `FixedString` value. The following example illustrates how to use the `WHERE` clause with `FixedString`. Lets consider the following table with the single `FixedString(2)` column: ``` text name b ``` The query `SELECT * FROM FixedStringTable WHERE a = 'b'` does not return any data as a result. We should complement the filter pattern with null bytes. ``` sql SELECT * FROM FixedStringTable WHERE a = 'b\0' ``` ``` text a b ``` This behaviour differs from MySQL for the `CHAR` type (where strings are padded with spaces, and the spaces are removed for output). Note that the length of the `FixedString(N)` value is constant. The function returns `N` even if the `FixedString(N)` value is filled only with null bytes, but the function returns `1` in this case.
Project: KICS (Provisioning / Security & Compliance)
File: 2940d48a-dc5e-4178-a3f8-bfbd80720b41.md

title: Kubelet Read Only Port Is Not Set To Zero hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2940d48a-dc5e-4178-a3f8-bfbd80720b41 Query name: Kubelet Read Only Port Is Not Set To Zero Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: When using the kubelet command, the read-only port should be set to zero (--read-only-port=0)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet"] args: ["--read-only-port=1"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet", "--read-only-port=1"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="8" apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration address: "192.168.0.8" port: 20250 serializeImagePulls: false evictionHard: memory.available: "200Mi" readOnlyPort: 1 ``` <details><summary>Positive test num. 4 - json file</summary> ```json hl_lines="5" { "kind": "KubeletConfiguration", "apiVersion": "kubelet.config.k8s.io/v1beta1", "address": "192.168.0.8", "readOnlyPort": 1 } ``` </details> ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: kubelet-demo labels: purpose: kubelet-demo spec: containers: name: kubelet-demo-container image: foo/bar command: ["kubelet"] args: ["--read-only-port=0"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet", "--read-only-port=0"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 3 - yaml file" apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration address: "192.168.0.8" port: 20250 serializeImagePulls: false evictionHard: memory.available: "200Mi" readOnlyPort: 0 ``` <details><summary>Negative test num. 4 - json file</summary> ```json { "kind": "KubeletConfiguration", "apiVersion": "kubelet.config.k8s.io/v1beta1", "address": "192.168.0.8", "readOnlyPort": 0 } ``` </details> <details><summary>Negative test num. 5 - json file</summary> ```json { "kind": "KubeletConfiguration", "apiVersion": "kubelet.config.k8s.io/v1beta1", "address": "192.168.0.8" } ``` </details>
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: migration-guide.md

layout: global title: Migration Guide displayTitle: Migration Guide license: | 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 sections of the migration guide for each component in order for users to migrate effectively.
Project: ArangoDB (App Definition and Development / Database)
File: file_handle.md

+++ title = "A file handle" description = "" weight = 20 +++ Borrowing from which uses this design pattern[^1], here is a simplified `file_handle` implementation: {{% snippet "constructors.cpp" "file_handle" %}} Note the default member initialisers, these are particularly convenient for implementing phase 1 of construction. Note also the `constexpr` constructor, which thanks to the default member initialisers is otherwise empty. File handles are very expensive to copy as they involve a syscall to duplicate the file descriptor, so we enable moves only. The destructor closes the file descriptor if it is not -1, and if the close fails, seeing as there is nothing else we can do without leaking the file descriptor, we fatal exit the process. Finally we declare the phase 2 constructor which is a static member function.
Project: KICS (Provisioning / Security & Compliance)
File: 773116aa-2e6d-416f-bd85-f0301cc05d76.md

title: Security Definitions Allows Password Flow hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 773116aa-2e6d-416f-bd85-f0301cc05d76 Query name: Security Definitions Allows Password Flow Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Security Definition Object should not allow 'password' Flow in OAuth2 authentication<br> ```json title="Positive test num. 1 - json file" hl_lines="27" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "password", "tokenUrl": "https://api.my.company.com/oauth/token" } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="19" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: password tokenUrl: https://api.my.company.com/oauth/token ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "accessCode", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "tokenUrl": "https://api.my.company.com/oauth/token", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: accessCode authorizationUrl: https://api.my.company.com/oauth/authorize tokenUrl: https://api.my.company.com/oauth/token scopes: write:api: modify apis in your account read:api: read your apis ```
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: tricks.md

This code doesn't work since having `&self.contraflow` in the for loop borroes ```rust for idx in &self.contraflow { let res = { let op = self.graph.get_mut(*idx).unwrap(); // We know this exists op.on_signal(&mut signal)? }; self.enqueue_events(*idx, res); returns.append(&mut self.run()?) } ``` Translating it to this works: ```rust for idx in 0..self.contraflow.len() { let i = self.contraflow[idx]; let res = { let op = self.graph.get_mut(i).unwrap(); // We know this exists op.on_signal(&mut signal)? }; self.enqueue_events(i, res); returns.append(&mut self.run()?) } ```
Project: Okteto (App Definition and Development / Application Definition & Image Build)
File: pull_request_template.md

Fixes # (issue) Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. Please provide step-by-step instructions to replicate your validation scenario. For bug fixes, detail how to reproduce both the bug and its fix, along with any observations. For both authors and reviewers: Scrutinize for potential regressions Ensure key automated tests are in place Build the CLI and test using the validation steps Assess Developer Experience impact (log messages, performances, etc) If too broad, consider breaking into smaller PRs Adhere to our and guidelines <!-- Remove comment when okteto/okteto is out of wait list for Copilot for Pull Requests <details> <summary> Copilot generated PR description</summary> copilot:all </details> -->
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.22.md

layout: release date: 2024-02-21 tag: v0.7.22 add: Add description for relationship @RipulHandoo (#10308) updated kompose version @anirudh-hegde (#10354) [Docs] Initialize logical concepts page for Registry @leecalcote (#10349) Fix more SQL injections @gyohuangxin (#10280) fixed the export modal @captain-Akshay (#10342) [Rtk] Migrate meshsync section to rtk @sudhanshutech (#10243) [Server] Fix events API. @MUzairS15 (#10353) [Fix Docs] Improve code formatting @sandramsc (#9911) [Docs] Updated FAQ for design invisibility issues in catalog @saurabh100ni (#9704) Fixed one broken link issue #9957 @neerajmanivarnan (#9958) #9935 changed the link from /guides/configuration-management/creating @muthu9594 (#9938) [Docs] fix: Compatibility Matrix test result for Components and typo's @singh1203 (#10338) [Docs] Modify help text for Meshery Catalog @hamza-mohd (#10341) [DOCS] Missing Abstract added in pages @iArchitSharma (#10336) [Docs] Contributing: Models and Relationships @leecalcote (#10348) suggested reading cache fix @iArchitSharma (#10328) [Docs] Add abstract to the Extensions page @leecalcote (#10322) Fix more SQL injections @gyohuangxin (#10280) Thank you to our contributors for making this release possible: @MUzairS15, @RipulHandoo, @anirudh-hegde, @captain-Akshay, @gyohuangxin, @hamza-mohd, @iArchitSharma, @l5io, @leecalcote, @muthu9594, @neerajmanivarnan, @sandramsc, @saurabh100ni, @singh1203, @sudhanshutech and l5io
Project: Druid (App Definition and Development / Database)
File: problem_report.md

name: Problem Report about: A template for Druid problem reports title: "" labels: Uncategorized problem report assignees: '' Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes"). The Druid version where the problem was encountered. Please include as much detailed information about the problem as possible. Cluster size Configurations in use Steps to reproduce the problem The error message or stack traces encountered. Providing more context, such as nearby log messages or even entire logs, can be helpful. Any debugging that you have already done
Project: YugabyteDB (App Definition and Development / Database)
File: LICENSE.md

The PostgreSQL License =============================================================================== Copyright (c) 2018-2020, DALIBO SCOP Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. IN NO EVENT SHALL DALIBO SCOP BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF DALIBO SCOP HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. DALIBO SCOP SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND DALIBO SCOP HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
Project: YDB (App Definition and Development / Database)
File: SECURITY.md

To report a security issue, please use http://g.co/vulnz. We use http://g.co/vulnz for our intake, and do coordination and disclosure here on GitHub (including using GitHub Security Advisory). The Google Security Team will respond within 5 working days of your report on g.co/vulnz. Select the `I want to report a technical security or an abuse risk related bug in a Google product (SQLi, XSS, etc.)` option and complete the form.
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: segment-containers.md

<!-- Copyright Pravega Authors. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> This document describes the high level design of how we are managing the lifecyle of Segment Containers in a Pravega Cluster. In this document we refer to a Segment Container as Container. The total number of Containers is fixed for a given deployment. Each Container can be owned by only one Pravega host and all Containers in the cluster should be running at any given point in time. A Pravega host is an instance of a Pravega service which owns and executes a set of Containers. Every Pravega host on startup will register itself with Zookeeper using ephemeral nodes. The ephemeral nodes are present in Zookeeper as long as Zookeeper receives appropriate signals from the Pravega host. These ephemeral nodes are used to detect the active Pravega hosts in the cluster. Each Pravega Controller runs a service which monitors the ephemeral nodes on the Zookeeper and detects all active Pravega hosts in the cluster. If any changes are detected to the cluster membership, then all Containers are verified and re-mapped to the available set of Pravega hosts. This information is persisted in the HostStore atomically. This is stored as a single blob and contains a map of Host to set of Containers that a host owns. We use Zookeeper to ensure only one Pravega Controller is monitoring the cluster to avoid multiple simultaneous Writers to the HostStore. This will avoid race conditions and allow the state to converge faster. When a Pravega Host is added or removed from the cluster, rebalancing of the Container ownership happens. As it is an expensive operation, Pravega maintains a configured minimum time interval between any two rebalance operations. It ends up in proportionally increasing more time for performing ownership change in the cluster, if the rebalance operation is delayed due to some reason. Every Pravega host has a long running Segment Manager Service. This constantly polls/watches the HostStore for any changes to the Container ownership. On detecting any ownership changes for itself (identified by the host key in the Map) the Segment Manager triggers addition and removal of Containers accordingly.
Project: ShardingSphere (App Definition and Development / Database)
File: attachments.en.md

title: Attachments description : "The Attachments shortcode displays a list of files attached to a page." The Attachments shortcode displays a list of files attached to a page. {{% attachments /%}} The shortcurt lists files found in a specific folder. Currently, it support two implementations for pages If your page is a markdown file, attachements must be placed in a folder named like your page and ending with .files. > * content > * _index.md > * page.files > * attachment.pdf > * page.md If your page is a folder, attachements must be placed in a nested 'files' folder. > * content > * _index.md > * page > * index.md > * files > * attachment.pdf Be aware that if you use a multilingual website, you will need to have as many folders as languages. That's all! | Parameter | Default | Description | |:--|:--|:--| | title | "Attachments" | List's title | | style | "" | Choose between "orange", "grey", "blue" and "green" for nice style | | pattern | "." | A regular expression, used to filter the attachments by file name. The pattern* parameter value must be a . | For example: To match a file suffix of '.jpg', use `.\.jpg$` (not `*.jpg`). To match file names ending in '.jpg' or '.png', use `.\.(jpg|png)$`. {{%/attachments title="Related files" pattern=".\.(pdf|mp4)$"/*/%}} renders as {{%attachments title="Related files" pattern=".*\.(pdf|mp4)$"/%}} {{%/attachments style="orange" //%}} renders as {{% attachments style="orange" /%}} {{%/attachments style="grey" //%}} renders as {{% attachments style="grey" /%}} {{%/attachments style="blue" //%}} renders as {{% attachments style="blue" /%}} {{%/attachments style="green" //%}} renders as {{% attachments style="green" /%}}
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.26.md

RabbitMQ `3.7.26` is a maintenance release. It focuses on bug fixes and usability improvements. RabbitMQ `3.7.x` series are out of general support and covered by the policy. Please consider to . This release . Previously recent `3.7.x` nodes could start on Erlang 20.3 and to some extent tested on it despite the Erlang `21.3+` requirements in release notes and documentation. Starting with this release, `21.3+` is a hard requirement enforced in the code to . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . "Command" operations such as binding propagation now use a separate channel for all links, preventing latency spikes for asynchronous operations (such as message publishing) (a head-of-line blocking problem). Contributed by Grigory Starinkin. GitHub issue: `rabbitmqadmin` failed with an exception on Python 3 when `-f pretty_json` flag was used. GitHub issue: AMQP 1.0 client used by Shovel now correctly encodes Erlang atoms. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.26.tar.xz`.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.4.md

`3.6.4` is a maintenance release. Nodes on Windows will successfully start if Erlang is installed in a directory with spaces in the path. GitHub issue: Node health check is now node-local, as it was meant to be. GitHub issue: Queue deletion and termination will no longer leave "tomb stone" messages in message store files. This eliminates the confusing behavior when a node or cluster having no messages enqueued could have many thousands of such "marker" messages in the message store. GitHub issue: `rabbitmqctl cluster_status` will now output an accurate error message if invoked shortly after a node was removed from the cluster and the node cannot be contacted. GitHub issue: Contributed by Peter Lemenkov (Red Hat) Erlang VM scheduler binding type default has changed to `db`. This means fewer CPU context switches for some workloads. GitHub issue: HTTP API is now compatible with Erlang 19.0. GitHub issue: Temporary tables are no longer named using atoms, preventing a potential exhaustion of the runtime atom table. GitHub issue: Cluster links and traffic charts are correctly displayed again GitHub issue: Runtime metric charts now have a description pop-up associated with them. GitHub issue: When an AMQP 1.0 specified its own list of source outcomes in a link attachment, it caused a crash of its session on the server. Now a protocol error is raised if the list contains invalid outcomes. GitHub issue: The client will now try to use TLS v1.2 and v1.1 before falling back to v1.0 by default. GitHub issue:
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: elasticsearch-datafiltering.md

title: Elasticsearch Data Filtering labels: layer: data category: filtering software: elasticsearch code: https://github.com/open-policy-agent/contrib/tree/master/datafilterelasticsearch tutorials: https://github.com/open-policy-agent/contrib/blob/master/datafilterelasticsearch/README.md inventors: styra Elasticsearch is a distributed, open source search and analytics engine. This OPA integration lets an elasticsearch client construct queries so that the data returned by elasticsearch obeys OPA-defined policies.