cwielenb/CNCF-Dataset huggingface dataset:
Project: Shifu (Provisioning / Automation & Configuration)
File: design-deviceShifu-refactor.md

citing From design-shifu.md: *deviceShifu is an structural of the edgeDevice*. We call it structural because it's not only a virtual presentation of the *edgeDevice* but also it's capable of driving the corresponding *edgeDevice* towards its goal state. For example, if you want your robot to move a box but it's currently busy on something else, *deviceShifu* will cache your instructions and tell your robot to move the box whenever it's available. For the basic part, *deviceShifu provides some general functionalities such as edgeDevice* health monitoring, state caching, etc. By implementing the interface of *deviceShifu, your edgeDevice* can achieve everything its designed for, and much more! Currently we implement a completely new deviceShifu struct for each new protocol, which doesn't utilize golang's feature and need to update every deviceShifu struct when we try to add new features. Thus, we need to decouple current deviceShifu implementation to strip out the common part of each deviceShifu and create a base-deviceShifu struct, and whenever we need to create new deviceShifu, we only need to focus on the protocol specific part. Factor out the common parts of current existing *shifuDevices and configs into a common base-shifuDevice* struct to reduce duplicate codes and decouple some common device creation logic to the *base-shifuDevice* struct and config from each specific shifuDevice. Create a *deviceShifu interface as the guideline for adding new deviceShifu* and let current main.go use the general *deviceShifu interface to perform the actions needed to start a deviceShifu*. Create a general universal *deviceShifu* to represent every edge device. ```go type BaseDeviceShifu struct { Name string server *http.Server deviceShifuConfig *DeviceShifuConfig edgeDevice *v1alpha1.EdgeDevice restClient *rest.RESTClient } type BaseDeviceShifuMetaData struct { Name string ConfigFilePath string KubeConfigPath string Namespace string } ``` We currently use *BaseDeviceShifu and BaseDeviceShifuMetaData as examples of common part for each deviceShifu*. For specific *deviceShifu such as deviceShifuSocket* we will use a composite struct like: ```go type DeviceShifuSocket struct { baseDeviceShifu *BaseDeviceShifu socketConnection *net.Conn } ``` In such a way, we can reuse *baseDeviceShifu* for all the common functionalities of that all edge devices share, and add fields like *socketConnection* to handle protocol specific logics. ```go interface DeviceShifu { Start(stopCh <-chan struct{}) error Stop() error } ``` The interface would only contain the basic methods that each edge device would share in common, which is just start and stop. However, in order to create each different edge device base on the provided metadata, we need to use a factory pattern ```go func createDeviceShifu(metaData BaseDeviceShifuMetaData) (DeviceShifu, error) ``` The factory method would take a metadata and create a concrete deviceShifu instance base on the metadata provided.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.14.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | keyToPath in Jets3tFileSystemStore needs to return absolute path | Major | fs/s3 | Ahad Rana | Tom White | | | Spurious error message during block crc upgrade. | Blocker | . | Raghu Angadi | Raghu Angadi | | | hadoop job -kill , -status causes NullPointerException | Blocker | . | Lohit Vijayarenu | Enis Soztutar | | | LzoCompressor.finished doesn't check whether the user actually wants to finish compressing | Blocker | . | Arun C Murthy | Arun C Murthy | | | tasktracker hang in reduce. Deadlock between main and comm thread | Blocker | . | Koji Noguchi | Vivek Ratan | | | reduces are getting stuck trying to find map outputs | Blocker | . | Owen O'Malley | Arun C Murthy | | | Name-node should remove edits.new during startup rather than renaming it to edits. | Blocker | . | Konstantin Shvachko | Konstantin Shvachko | | | Corrupted block replication retries for ever | Blocker | . | Koji Noguchi | Raghu Angadi | | | -get, -copyToLocal fail when single filename is passed | Blocker | . | Koji Noguchi | Raghu Angadi | | | TestCheckpoint fails on Windows | Blocker | . | Konstantin Shvachko | Konstantin Shvachko |
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: VFS_Architecture.md

The architecture has this stack: ``` -- Client Controller e.g. a command registration for /mkdir -- VFS Delegation dispatch filepaths to the owning VFS impl -- VFS Impls e.g. interpret mkdir against local filesystem -- Server Controller implement portions that cannot be run in a browser ``` Thus, to add a new VFS API, you must currently add a controller (if one does not already exist) for the command, code the delegation that knows which positional parameters correspond to filepaths, implement the client-side and any needed server-side portions of the VFS impl. The interface consists cd, ls, mkdir, etc. e.g. /mkdir -> which invokes the next layer: Delegates These resolve filepaths to VFS impl. ``` mkdir /a/b/c ^^^^ -> VFS Impl lookup based on path ``` Then call `impl.mkdir(args)`. These can't assume they are running on the Kui proxy side Examples local.ts for local filesystem If a client VFS impl requires execution of code that cannot safely run in a browser, it must manage routing this code to the Kui proxy. For example: `vfs _ls` for `ls` (because we handle ls without a pty, so ls needs its own server-side handler) `sendtopty` for`mkdir`, and most everything else These are command handlers that facilitate the server-side of the browser-unsafe logic. `/vfs/_ls` handler or generic `pty` handling for mkdir
Project: MongoDB (App Definition and Development / Database)
File: platforms.md

The TCMalloc code is supported on the following platforms. By "platforms", we mean the union of operating system, architecture (e.g. little-endian vs. big-endian), compiler, and standard library. TCMalloc requires a code base that supports C++17 and our code is C++17-compliant. C code is required to be compliant to C11. We guarantee that our code will compile under the following compilation flags: Linux: gcc 9.2+, clang 9.0+: `-std=c++17` (TL;DR; All code at this time must be built under C++17. We will update this list if circumstances change.) The document below lists each platform, broken down by Operating System, Architecture, Specific Compiler, and Standard Library implementation. Supported <table width="80%"> <col width="360"> <col width="120"> <tbody> <tr> <th>Operating System</th> <th>Endianness/Word Size</th> <th>Processor Architectures</th> <th>Compilers*</th> <th>Standard Libraries</th> </tr> <tr> <td>Linux</td> <td>little-endian, 64-bit</td> <td>x86, AArch64</td> <td>gcc 9.2+<br/>clang 9.0+</td> <td>libstdc++<br/>libc++</td> </tr> </tbody> </table> \* We test on gcc 9.2, though gcc versions (which support C++17) prior to that release should also work. Best Effort <table width="80%"> <col width="360"> <col width="120"> <tbody> <tr> <th>Operating System</th> <th>Endianness/Word Size</th> <th>Processor Architectures</th> <th>Compilers*</th> <th>Standard Libraries</th> </tr> <tr> <td>Linux</td> <td>little-endian, 64-bit</td> <td>PPC</td> <td>gcc 9.2+<br/>clang 9.0+</td> <td>libstdc++<br/>libc++</td> </tr> </tbody> </table>
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.11.28-lts.md

sidebar_position: 1 sidebar_label: 2024 Backported in : Update tzdata to 2024a. (). Fix buffer overflow in CompressionCodecMultiple (). Remove nonsense from SQL/JSON (). Fix crash in arrayEnumerateRanked (). Fix crash when using input() in INSERT SELECT JOIN (). Remove recursion when reading from S3 (). NO CL ENTRY: 'Use the current branch test-utils to build cctools'. (). Cancel PipelineExecutor properly in case of exception in spawnThreads (). Detect io_uring in tests (). Cancel PipelineExecutor properly in case of exception in spawnThreads ().
Project: Clair (Provisioning / Security & Compliance)
File: whatis.md

Clair is an application for parsing image contents and reporting vulnerabilities affecting the contents. This is done via static analysis and not at runtime. Clair supports the extraction of contents and assignment of vulnerabilities from the following official base containers: Ubuntu Debian RHEL Suse Oracle Alpine AWS Linux VMWare Photon Python The above list defines Clair's current support matrix. Clair v4 utilizes the library as its engine for examining contents and reporting vulnerabilities. At a high level you can consider Clair a service wrapper to the functionality provided in the ClairCore library. The above diagram expresses the separation of concerns between Clair and the ClairCore library. Most development involving new distributions, vulnerability sources, and layer indexing will occur in ClairCore. Clair's analysis is broken into three distinct parts. Indexing starts with submitting a Manifest to Clair. On receipt, Clair will fetch layers, scan their contents, and return an intermediate representation called an IndexReport. Manifests are Clair's representation of a container image. Clair leverages the fact that OCI Manifests and Layers are content-addressed to reduce duplicated work. Once a Manifest is indexed, the IndexReport is persisted for later retrieval. Matching is taking an IndexReport and correlating vulnerabilities affecting the manifest the report represents. Clair is continually ingesting new security data and a request to the matcher will always provide you with the most up to date vulnerability analysis of an IndexReport. How we implement indexing and matching in detail is covered in documentation. Clair implements a notification service. When new vulnerabilities are discovered, the notifier service will determine if these vulnerabilities affect any indexed Manifests. The notifier will then take action according to its configuration. At this point you'll probably want to check out .
Project: Meshery (Provisioning / Automation & Configuration)
File: spire.md

layout: integration title: SPIRE subtitle: Collaborative and visual infrastructure as code for SPIRE image: /assets/img/integrations/spire/icons/color/spire-color.svg permalink: extensibility/integrations/spire docURL: https://docs.meshery.io/extensibility/integrations/spire description: integrations-category: Security & Compliance integrations-subcategory: Key Management registrant: Artifact Hub components: name: cluster-federated-trust-domain colorIcon: assets/img/integrations/spire/components/cluster-federated-trust-domain/icons/color/cluster-federated-trust-domain-color.svg whiteIcon: assets/img/integrations/spire/components/cluster-federated-trust-domain/icons/white/cluster-federated-trust-domain-white.svg description: name: cluster-spiffeid colorIcon: assets/img/integrations/spire/components/cluster-spiffeid/icons/color/cluster-spiffeid-color.svg whiteIcon: assets/img/integrations/spire/components/cluster-spiffeid/icons/white/cluster-spiffeid-white.svg description: name: controller-manager-config colorIcon: assets/img/integrations/spire/components/controller-manager-config/icons/color/controller-manager-config-color.svg whiteIcon: assets/img/integrations/spire/components/controller-manager-config/icons/white/controller-manager-config-white.svg description: featureList: [ "SPIRE design and deployment best practices", "Configure SPIRE to securely issue and renew SVIDs.", "Design workloads to establish trust between each other by establishing an mTLS connection or by signing and verifying a JWT token." ] howItWorks: "Configure your signing framework" howItWorksDetails: "Simplify access from identified services to secret stores, databases, services meshes and cloud provider services." language: en list: include type: extensibility category: integrations
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_commands_receive.md

Command receive a body from 'commands' channel command Command receive (Subscribe) command allows to consume a body from 'commands' channel and response with appropriate reply ``` kubemq commands receive [flags] ``` ``` kubemq commands receive some-channel kubemq commands receive some-channel -g G1 ``` ``` -a, --auto-response set auto response executed command for each command received -g, --group string set 'commands' channel consumer group (load balancing) -h, --help help for receive ``` - Execute Kubemq 'commands'
Project: Harbor (Provisioning / Container Registry)
File: 9-05-DB-user-delete-signed-images.md

Test 9-05 User delete signed images(DB mode) ======= To verify whether user can delete signed images. User guide This test requires one Harbor instance is running and available. A Linux host with Docker CLI(Docker client) installed. NOTE: In below test,<harborip> should be replaced by your harbor's ip or FQDN. If you are using a self-signed certificate,make sure to copy the CA root cert into ```/etc/docker/certs.d/<harborip>``` and ```$HOME/.docker/tls/<harbor_ip>:4443/``` Login UI and create a project. On a Docker client,run ```sh export DOCKERCONTENTTRUST=1 export DOCKERCONTENTTRUSTSERVER=https://<harborip>:4443 ``` and login Harbor. Push an image to project created in step1. Delete the pushed image. Delete notary tag according to message from UI in step4. Delete the image again. In step4, image cannot be deleted. In step6, image can be deleted. None
Project: YugabyteDB (App Definition and Development / Database)
File: docs-editor-setup.md

title: Set up your editor headerTitle: 'Optional: editor setup' linkTitle: Editor setup description: Optional setup steps for selected text editors menu: preview: identifier: docs-editor-setup parent: docs-build weight: 2913 type: docs {{< tip title="Visual Studio Code-specific" >}} A lot of the information on this page is specific to Visual Studio Code. If you use another editor, and would like to update this page to include it, please do so! {{< /tip >}} To install an extension in Visual Studio Code, click the Extensions icon in the left nav, or press Cmd-Shift-X, and search for the extension by name. GitHub Pull Requests and Issues*, by GitHub: Pretty good pull request support. Not perfect, and can get confused with large PRs, but handy on a regular basis. GitLens Git supercharged*, by Eric Amodio: Useful Git tooling, including per-line blame/history. Markdown Preview Enhanced*, by Yiyi Wang: Even nicer Markdown previews. markdownlint*, by David Anson: Lints your markdown formatting to catch errors and inconsistencies. Vale*, by errata-ai: Prose linter. Very powerful, very extensible. (Also available ). Be sure to turn on "Vale > Core: Use CLI" in your Visual Studio Code settings. Sort Lines*, by Daniel Imms: Adds better sorting options. In particular, natural sort order for strings makes [10] come after [9]. Use these as necessary. If you don't need a particular extension, don't install it. Better TOML*, by bungcip: Makes reading Netlify configuration files nicer. Dart*, by Dart Code Docker*, by Microsoft ESLint*, by Dirk Baeumer: The JavaScript linter. Flutter*, by Dart Code Spectral*, by Stoplight: Lints OpenAPI specs and any other YAML/JSON you want. YAML*, by Red Hat !
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: proposal.md

name: Proposal about: Create a technical proposal for Dapr title: '' labels: kind/proposal assignees: '' <!-- If you need to report a security issue please visit https://docs.dapr.io/operations/support/support-security-issues --> <!-- Remove the '> ' to select --> /area runtime /area operator /area placement /area docs /area test-and-release <!-- Please use this for a concrete design proposal for functionality. --> <!-- If you just want to request a new feature and discuss the possible business value, create a Feature Request. -->
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

<!-- Please make sure the target branch is right. In most case, the target branch should be `develop`. --> <!-- Please ensure that the related issue has already been created, and to ensure automatic closure. --> Fixes #issue_id <!-- Write a brief description for your pull request to help the maintainer understand the reasons behind your changes. --> <!-- In order to ensure the code quality of Apache RocketMQ, we expect every pull request to have undergone thorough testing. -->
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-296.md

A consumer is a process that attaches to a topic via a subscription and then receives messages. The reader interface for Pulsar enables applications to manually manage cursors. More knowledge of the Reader and Consumer interface can be found in the . Add the `getLastMessageIds` API for Reader. This will help to increase the flexibility of reader usage. Add the `getLastMessageIds` API for Reader. None. Implement the `getLastMessageIds` method for Reader by internally invoking the Consumer interface. ```java @Override public List<TopicMessageId> getLastMessageIds() throws PulsarClientException { return consumer.getLastMessageIds(); } @Override public CompletableFuture<List<TopicMessageId>> getLastMessageIdsAsync() { return consumer.getLastMessageIdsAsync(); } ``` ```java / Get all the last message id of the topics the reader subscribed. * @return the list of TopicMessageId instances of all the topics that the reader subscribed @throws PulsarClientException if failed to get last message id. @apiNote It's guaranteed that the owner topic of each TopicMessageId in the returned list is different from owner topics of other TopicMessageId instances */ List<TopicMessageId> getLastMessageIds() throws PulsarClientException; / The asynchronous version of {@link Reader#getLastMessageIds()}. */ CompletableFuture<List<TopicMessageId>> getLastMessageIdsAsync(); ``` <!-- Updated afterwards --> Mailing List discussion thread: Mailing List voting thread:
Project: YugabyteDB (App Definition and Development / Database)
File: zadd.md

title: ZADD linkTitle: ZADD description: ZADD menu: preview: parent: api-yedis weight: 2500 aliases: /preview/api/redis/zadd /preview/api/yedis/zadd type: docs `ZADD key [NX|XX] [CH] [INCR] score member [score member ...]` This command sets all specified `members` with their respective `scores` in the sorted set specified by `key`, with multiple `score` `member` pairs possible. If a specified `member` is already in the sorted set, this command updates that `member` with the new `score`. If the `key` does not exist, a new sorted set is created, with the specified pairs as the only elements in the set. A `score` should be a double, while a `member` can be any string. The number of new `members` added to the sorted set, unless the `CH` option is specified (see below). XX: Only update `members` that already exist. Do not add new `members`. NX: Do not update `members` that already exist. Only addd new `members`. CH: Modify the return value from new `members` added to `members` added or updated. INCR: Increment the specified `member` by `score`. Only one `score` `member` pair can be specified. Add two elements into the sorted set. ```sh $ ZADD z_key 1.0 v1 2.0 v2 ``` ``` (integer) 2 ``` Update an element in the set. Note the return value is 0, since you do not add a new member. ```sh $ ZADD z_key 3.0 v1 ``` ``` (integer) 0 ``` Now you add a new member with an existing score. This is fine, since multiple members can have the same score. ```sh $ ZADD z_key 3.0 v3 ``` ``` (integer) 1 ``` Now, see the members in the sorted set. Note the sort order by score. Since both v1 and v3 have the same score, you use comparison on the members themselves to determine order. ```sh $ ZRANGEBYSCORE z_key -inf +inf WITHSCORES ``` ``` 1) "v2" 2) "2.0" 3) "v1" 4) "3.0" 5) "v3" 6) "3.0" ``` With the `XX` option specified, only update exiting members. Here, only v1 is modified. ```sh $ ZADD z_key XX 1.0 v1 4.0 v4 ``` ``` (integer) 0 ``` With the `NX` option specified, only add new members. Here only v4 is added. ```sh $ ZADD z_key NX 0.0 v1 4.0 v4 ``` ``` (integer) 1 ``` With the CH option specified, return number of new and updated members. ```sh $ ZADD z_key CH 0.0 v1 5.0 v5 ``` ``` (integer) 2 ``` With the INCR option specified, increment by score. Score of v5 should now be 6.0. ```sh $ ZADD z_key INCR 1.0 v5 ``` Let us now see the updated sorted set. ```sh $ ZRANGEBYSCORE z_key -inf +inf ``` ``` 1) "v1" 2) "0.0" 3) "v2" 4) "2.0" 5) "v3" 6) "3.0" 7) "v4" 8) "4.0" 9) "v5" 10) "6.0" ``` , , , ,
Project: Beam (App Definition and Development / Streaming & Messaging)
File: chrome.md

title: "Google Chrome" icon: /images/logos/powered-by/chrome.png hasLink: "https://www.google.com/chrome/" <!-- 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. -->
Project: YugabyteDB (App Definition and Development / Database)
File: type_frozen.md

title: FROZEN data type [YCQL] headerTitle: FROZEN data type linkTitle: FROZEN description: Use the FROZEN data type to specify columns of binary strings that result from serializing collections, tuples, or user-defined types. menu: v2.18: parent: api-cassandra weight: 1401 type: docs Use the `FROZEN` data type to specify columns of binary strings that result from serializing collections, tuples, or user-defined types. ``` type_specification ::= FROZEN<type> ``` Where `type` is a well-formed YCQL data type (additional restrictions for `type` are covered in the Semantics section below). Columns of type `FROZEN` can be part of the `PRIMARY KEY`. Type parameters of `FROZEN` type must be either (`LIST`, `MAP`, or `SET`) or . `FROZEN` types can be parameters of collection types. For any valid frozen type parameter `type`, values of `type` are convertible into `FROZEN<type>`. ```sql ycqlsh:example> CREATE TABLE directory(file FROZEN<LIST<TEXT>> PRIMARY KEY, value BLOB); ``` ```sql ycqlsh:example> INSERT INTO directory(file, value) VALUES([ 'home', 'documents', 'homework.doc' ], 0x); ``` ```sql ycqlsh:example> INSERT INTO directory(file, value) VALUES([ 'home', 'downloads', 'textbook.pdf' ], 0x12ab21ef); ``` ```sql ycqlsh:example> UPDATE directory SET value = 0xab00ff WHERE file = [ 'home', 'documents', 'homework.doc' ]; ``` ```sql ycqlsh:example> SELECT * FROM directory; ``` ``` file | value ['home', 'downloads', 'textbook.pdf'] | 0x12ab21ef ['home', 'documents', 'homework.doc'] | 0xab00ff ```
Project: Vault (Provisioning / Key Management)
File: FYI.md

These templates parent form components that render within a modal to create inline items via SearchSelectWithModal. The modal opens when a user searches for an item that doesn't exist and clicks 'No results found for "${term}". Click here to create it.' The templates are rendered using the {{component}} helper in 'search-select-with-modal.hbs' and are responsible for creating the model passed to the form.