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

displayed_sidebar: "English" Returns an empty bitmap. It is mainly used to fill in the default value during insert or stream load. For example: ```bash cat data | curl --location-trusted -u user:passwd -T - \ -H "columns: dt,page,v1,v2=bitmap_empty()" \ http://host:8410/api/test/testDb/streamload ``` ```Haskell BITMAP BITMAP_EMPTY() ``` ```Plain Text MySQL > select bitmapcount(bitmapempty()); ++ | bitmapcount(bitmapempty()) | ++ | 0 | ++ ``` BITMAP_EMPTY,BITMAP
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: documentation.md

We have pretty similar workflows for each OS. Runs for every created reelase on Github `Context` `Checkout Project` `Verify Runner Resources` `Install Tools` jq is needed for adding these environment inside the application and defining the release version `Add MacOS certs` `Electron mac os security identities` `Get Node Version` `Use Node.js` `Install Dependencies` `Install dmg-license` `Build` This step is need to add our ENV variables for the application. We need to add into this step, it will inject ENV into electron/env.json file `Package` `Create release and upload artifacts` If we add new release, we need to extend its extension here. ` Archive Binary` `Context` `Install Tools` jq is needed for adding these environment inside the application and defining the release version `Checkout Project` `Get Node Version` `Use Node.js` `Install Dependencies` `Build` This step is need to add our ENV variables for the application. We need to add into this step, it will inject ENV into electron/env.json file `Package` `Create release and upload artifacts` If we add new release, we need to extend its extension here. `Archive Binary` `Context` `Checkout Project` `Get Node Version` `Use Node.js` `Install Dependencies` `Install Tools` jq is needed for adding these environment inside the application and defining the release version `Build` This step is need to add our ENV variables for the application. We need to add into this step, it will inject ENV into electron/env.json file `Package` `Create release and upload artifacts` If we add new release, we need to extend its extension here. `Archive Binary` Runs on every push to `auto-updater` branch `Delete release` Rest is same with [Monokle publish] `Delete release` Rest is same with [Monokle publish] `Delete release` Rest is same with [Monokle publish] Runs on every push to `auto-updater` branch `Delete release` Rest is same with [Monokle publish] `Delete release` Rest is same with [Monokle publish] `Delete release` Rest is same with [Monokle publish] Runs every day with pattern of `0 2 *` same with [Monokle publish] Runs every day with pattern of `0 2 *` same with [Monokle publish] Runs every day with pattern of `0 2 *` same with [Monokle publish] These workflows uses the same steps and they can be merged with the new feature Github intruced. https://docs.github.com/en/actions/using-workflows/reusing-workflows
Project: Beam (App Definition and Development / Streaming & Messaging)
File: where-in-event-time.md

type: runners title: "Where in event time?" layout: "capability-template" <!-- 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. --> <!-- Summary table --> {{< documentation/capability-matrix-big cap-data="capability-matrix" cap-view="full" cap-index=3 >}}
Project: Goldilocks (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: [triage, enhancement] assignees: '' 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 solution 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. Additional context Add any other context or screenshots about the feature request here.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: how-to-navigate-and-edit-manifests.md

In this Monokle tutorial, we will illustrate the steps to help you navigate K8s resources and edit their manifests. Lets get started! <em>Note: Please follow this guide to install Monokle </em> Launch Monokle and, on the welcome screen, there are three option to start working with projects: Select an exisiting folder. Create an empty project. Start from a template. Click Select an existing project to add your project folder containing K8 resources. Select your folder to parse its manifest in the file explorer. In the file explorer, you can view manifests, including their resources, and their relationships. Scroll up & down to navigate and select the required manifests. Once you select a manifest, its related resources will be highlighted automatically in the navigator. See for more information on how to navigate resources. Click on outgoing and incoming links to navigate the corresponding resources. The warning triangle reflects that the link refers to broken resource links - see Select the required resource in the Navigator. Once you select a resource, its source code will be launched and highlighted in the editor. Now you can edit the resource in the editor and any changes you make will be automatically saved. See for more information on how to edit resources. Right-click on the editor to launch the editing menu. The editing menu includes the following options: Go to Symbols: Select the Go to Symbol option to perform a focused search of code for finding specified symbols quickly. Change All occurrences: Select the Change All Occurrences option to replace all string occurrences in the code with any other regular expression. Format Document: Select the Format Document option to organize the source code for better readability. It addresses font size, spacing, margins, alignment, columns, indentation, and lists. Cut: Select the Cut option to delete the unnecessary data. After you cut the text, it gets stored in the clipboard so you can use it later. Copy: Select the Copy option to copy a piece of code and reuse the code to save development time. Paste: Select the Paste option to paste a piece of code. This reduces the repetition of efforts required to write and test code. Command Palette: Select the Command Palette option to access keyboard shortcuts quickly for the most common operations. <em>Note: The editor provides autocomplete and autosave options.</em> Please feel free to join our open source community on Discord with this and start your discussion.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: emissary-ingress.md

title: Emissary-Ingress labels: category: network layer: gateway software: emissary-ingress blogs: https://www.infracloud.io/blogs/emissary-ingress-opa-integration/ Emissary-Ingress is an open-source Kubernetes-native API Gateway, Layer 7 load balancer and Kubernetes Ingress built on Envoy Proxy. OPA can be integrated with Emissary as an external authorization service to enforce authorization policies over APIs.
Project: StarRocks (App Definition and Development / Database)
File: be_cloud_native_compactions.md

displayed_sidebar: "English" `becloudnativecompactions` provides information on compaction transactions running on CNs (or BEs for v3.0) of a shared-data cluster. A compaction transaction is divided into multiple tasks on the tablet level, and each row in `becloudnativecompactions` corresponds to a task in the compaction transaction. The following fields are provided in `becloudnative_compactions`: | Field | Description | | -- | | | BE_ID | ID of the CN (BE). | | TXN_ID | ID of the compaction transaction. It can be duplicated because each compaction transaction may have multiple tasks. | | TABLET_ID | ID of the tablet the task corresponds to. | | VERSION | Version of the data that is input to the task. | | SKIPPED | Whether the task is skipped. | | RUNS | Number of task executions. A value greater than `1` indicates that retries have occurred. | | START_TIME | Task start time. | | FINISH_TIME | Task finish time. `NULL` is returned if the task is still in progress. | | PROGRESS | Percentage of progress, ranging from 0 to 100. | | STATUS | Task status. |
Project: YugabyteDB (App Definition and Development / Database)
File: setrange.md

title: SETRANGE linkTitle: SETRANGE description: SETRANGE menu: preview: parent: api-yedis weight: 2280 aliases: /preview/api/redis/setrange /preview/api/yedis/setrange type: docs `SETRANGE key offset value` This command overwrites the string that is associated with the given `key` with the given `value`, starting from the given `offset`. The `offset` cannot exceed 536870911. If the `offset` is larger than the length of the specified string, the string will be padded with zeros up to the `offset`. If the `key` does not exist, its associated string is an empty string. The resulted new string is constructed with zeros up to the given `offset` and then appended with the given `value`. If the `key` is associated with a non-string value, an error is raised. Returns the length of the resulted string after overwriting. ```sh $ SET yugakey "YugaKey" ``` ``` "OK" ``` ```sh $ SETRANGE yugakey 4 "Byte" ``` ``` 8 ``` ```sh $ GET yugakey ``` ``` "Yugabyte" ``` , , , , , , ,
Project: Meshery (Provisioning / Automation & Configuration)
File: postgres-controller.md

layout: integration title: Postgres Controller subtitle: Collaborative and visual infrastructure as code for Postgres Controller image: /assets/img/integrations/postgres-controller/icons/color/postgres-controller-color.svg permalink: extensibility/integrations/postgres-controller docURL: https://docs.meshery.io/extensibility/integrations/postgres-controller description: integrations-category: Database integrations-subcategory: App Definition and Development registrant: Artifact Hub components: name: postgres-database colorIcon: assets/img/integrations/postgres-controller/components/postgres-database/icons/color/postgres-database-color.svg whiteIcon: assets/img/integrations/postgres-controller/components/postgres-database/icons/white/postgres-database-white.svg description: 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: ArangoDB (App Definition and Development / Database)
File: std_outcome.md

+++ title = "`stdoutcome<T, EC = std::errorcode, EP = std::exceptionptr, NoValuePolicy = policy::defaultpolicy<T, EC, EP>>`" description = "A type alias to a `basicoutcome` configured with `std::errorcode`, `std::exceptionptr` and `policy::defaultpolicy`." +++ A type alias to a {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}} configured with {{% api "std::errorcode" %}}, {{% api "std::exceptionptr" %}} and `policy::`{{% api "defaultpolicy" %}}. This type alias always references the `std` edition of things, unlike {{% api "outcome<T, EC = varies, EP = varies, NoValuePolicy = policy::defaultpolicy<T, EC, EP>>" %}} which references either this alias or {{% api "boostoutcome<T, EC = boost::system::errorcode, EP = boost::exceptionptr, NoValuePolicy = policy::default_policy<T, EC, EP>>" %}}. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/std_outcome.hpp>`
Project: Kapitan (Provisioning / Automation & Configuration)
File: kapitan_dotfile.md

Kapitan allows you to coveniently override defaults by specifying a local `.kapitan` file in the root of your repository (relative to the kapitan configuration): This comes handy to make sure Kapitan runs consistently for your specific setup. !!! info Any Kapitan command can be overridden in the `.kapitan` dotfile, but here are some of the most common examples. To enforce the Kapitan version used for compilation (for consistency and safety), you can add `version` to `.kapitan`: ```yaml version: 0.30.0 ... ``` This constrain can be relaxed to allow minor versions to be also accepted: ```yaml version: 0.30 # Allows any 0.30.x release to run ... ``` You can also permanently define all command line flags in the `.kapitan` config file. For example: ```yaml ... compile: indent: 4 parallelism: 8 ``` would be equivalent to running: ```shell kapitan compile --indent 4 --parallelism 8 ``` For flags which are shared by multiple commands, you can either selectively define them for single commmands in a section with the same name as the command, or you can set any flags in section `global`, in which case they're applied for all commands. If you set a flag in both the `global` section and a command's section, the value from the command's section takes precedence over the value from the global section. As an example, you can configure the `inventory-path` in the `global` section of the Kapitan dotfile to make sure it's persisted across all Kapitan runs. ```yaml ... global: inventory-path: ./some_path ``` which would be equivalent to running any command with `--inventory-path=./some_path`. Another flag that you may want to set in the `global` section is `inventory-backend` to select a non-default inventory backend implementation. ```yaml global: inventory-backend: reclass ``` which would be equivalent to always running Kapitan with `--inventory-backend=reclass`. Please note that the `inventory-backend` flag currently can't be set through the command-specific sections of the Kapitan config file.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_describe.md

Describe a YugabyteDB Anywhere storage configuration Describe a storage configuration in YugabyteDB Anywhere ``` yba storage-config describe [flags] ``` ``` -n, --name string [Required] The name of the storage configuration to get details. -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere storage configurations
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_restart.md

title: kbcli cluster restart Restart the specified components in the cluster. ``` kbcli cluster restart NAME [flags] ``` ``` kbcli cluster restart mycluster kbcli cluster restart mycluster --components=mysql ``` ``` --auto-approve Skip interactive approval before restarting the cluster --components strings Component names to this operations --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") -h, --help help for restart --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Cluster command.
Project: Qdrant (App Definition and Development / Database)
File: roadmap-2023.md

Hi! This document is our plan for Qdrant development in 2023. Previous year roadmap is available here: Goals of the release: Maintain easy upgrades* - we plan to keep backward compatibility for at least one minor version back. That means that you can upgrade Qdrant without any downtime and without any changes in your client code within one minor version. Storage should be compatible between any two consequent versions, so you can upgrade Qdrant with automatic data migration between consecutive versions. Make billion-scale serving cheap* - qdrant already can serve billions of vectors, but we want to make it even more affordable. Easy scaling* - our plan is to make it easy to dynamically scale Qdrant, so you could go from 1 to 1B vectors seamlessly. Various similarity search scenarios* - we want to support more similarity search scenarios, e.g. sparse search, grouping requests, diverse search, etc. If you are a Qdrant user - Data Scientist, ML Engineer, or MLOps, the best contribution would be the feedback on your experience with Qdrant. Let us know whenever you have a problem, face an unexpected behavior, or see a lack of documentation. You can do it in any convenient way - create an , start a , or drop up a . If you use Qdrant or Metric Learning in your projects, we'd love to hear your story! Feel free to share articles and demos in our community. For those familiar with Rust - check out our . If you have problems with code or architecture understanding - reach us at any time. Feeling confident and want to contribute more? - Come to ! :atom_symbol: Quantization support [x] Scalar quantization f32 -> u8 (4x compression) [x] Product quantization (4x, 8x, 16x, 32x, and 64x compression) [x] Binary quantization (32x compression, 40x speedup) [x] Support for binary vectors :arrowdoubleup: Scalability [ ] Automatic replication factor adjustment [ ] Automatic shard distribution on cluster scaling [x] Repartitioning support :eyes: Search scenarios [ ] Diversity search - search for vectors that are different from each other [x] Discovery search - constrain the space in which the search is performed [x] Sparse vectors search - search for vectors with a small number of non-zero values [x] Grouping requests - search within payload-defined groups [x] Different scenarios for recommendation API Additionally [ ] Extend full-text filtering support [ ] Support for phrase queries [ ] Support for logical operators [x] Simplify update of collection parameters