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

sidebar_position: 1 sidebar_label: 2024 Backported in : Add `SYSTEM JEMALLOC PURGE` for purging unused jemalloc pages, `SYSTEM JEMALLOC (). Backported in : If you want to run initdb scripts every time when ClickHouse container is starting you shoud initialize environment varible CLICKHOUSEALWAYSRUNINITDBSCRIPTS. (). Fix working with read buffers in StreamingFormatExecutor (). Fix double destroy call on exception throw in addBatchLookupTable8 (). Fix: LIMIT BY and LIMIT in distributed query (). Fix translate() with FixedString input (). Fix leftPad / rightPad function with FixedString input (). Fix cosineDistance crash with Nullable (). Fix possible race in ManyAggregatedData dtor. (). Make ZooKeeper actually sequentialy consistent ().
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_debug_redis.md

title: Kubectl-Dba Debug Redis menu: docs_{{ .version }}: identifier: kubectl-dba-debug-redis name: Kubectl-Dba Debug Redis parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Debug helper for redis database ``` kubectl-dba debug redis [flags] ``` ``` kubectl dba debug redis -n demo sample-redis --operator-namespace kubedb ``` ``` -h, --help help for redis -o, --operator-namespace string the namespace where the kubedb operator is installed (default "kubedb") ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Debug any Database issue
Project: BigchainDB (App Definition and Development / Database)
File: report-a-bug.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > How to contribute? ================== To report a bug, go to the relevant GitHub repository, click on the Issues tab, click on the New issue button, and read the instructions. To write an issue, go to the relevant GitHub repository, click on the Issues tab, click on the New issue button, and read the instructions. People ask questions about BigchainDB in the following places: Gitter - Feel free to hang out and answer some questions. People will be thankful. If you have an idea for a new feature or enhancement, and you want some feedback before you write a full BigchainDB Enhancement Proposal (BEP), then feel free to: ask in the or and give it the label BEP idea. If you want to discuss an existing BEP, then and give it the label discuss existing BEP. Look at the structure of existing BEPs in the . Note the section headings. (our variant of the consensus-oriented specification system [COSS]) says more about the expected structure and process. Write a first draft of your BEP. It doesn't have to be long or perfect. Push your BEP draft to the and make a pull request. (our variant of C4) outlines the process we use to handle all pull requests. In particular, we try to merge all pull requests quickly. Your BEP can be revised by pushing more pull requests.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_node_reboot.md

Reboot a node instance in YugabyteDB Anywhere universe Reboot a node instance in YugabyteDB Anywhere universe. ``` yba universe node reboot [flags] ``` ``` -h, --help help for reboot ``` ``` -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") -n, --name string [Required] The name of the universe for the corresponding node operations. --node-name string [Optional] The name of the universe node for the corresponding node operations. Required for add, reboot, release, remove, reprovision, start, stop. -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 universe nodes
Project: ClickHouse (App Definition and Development / Database)
File: v22.10.4.23-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fixed backward incompatibility in (de)serialization of states of `min`, `max`, `any`, `argMin`, `argMax` aggregate functions with `String` argument. The incompatibility was introduced in https://github.com/ClickHouse/ClickHouse/pull/41431 and affects 22.9, 22.10 and 22.11 branches (fixed since 22.9.6, 22.10.4 and 22.11.2 correspondingly). Some minor releases of 22.3, 22.7 and 22.8 branches are also affected: 22.3.13...22.3.14 (fixed since 22.3.15), 22.8.6...22.8.9 (fixed since 22.8.10), 22.7.6 and newer (will not be fixed in 22.7, we recommend to upgrade from 22.7.* to 22.8.10 or newer). This release note does not concern users that have never used affected versions. Incompatible versions append extra `'\0'` to strings when reading states of the aggregate functions mentioned above. For example, if an older version saved state of `anyState('foobar')` to `statecolumn` then incompatible version will print `'foobar\0'` on `anyMerge(statecolumn)`. Also incompatible versions write states of the aggregate functions without trailing `'\0'`. Newer versions (that have the fix) can correctly read data written by all versions including incompatible versions, except one corner case. If an incompatible version saved a state with a string that actually ends with null character, then newer version will trim trailing `'\0'` when reading state of affected aggregate function. For example, if an incompatible version saved state of `anyState('abrac\0dabra\0')` to `statecolumn` then incompatible versions will print `'abrac\0dabra'` on `anyMerge(statecolumn)`. The issue also affects distributed queries when an incompatible version works in a cluster together with older or newer versions. (). Backported in : Wait for all files are in sync before archiving them in integration tests. (). Backported in : An issue with the following exception has been reported while trying to read a Parquet file from S3 into ClickHouse:. (). Backported in : Fix possible `Cannot create non-empty column with type Nothing` in functions if/multiIf. Closes . (). Backported in : Fix a bug when row level filter uses default value of column. (). Backported in : Fixed primary key analysis with conditions involving `toString(enum)`. (). Temporarily disable `testhivequery` (). Do not checkout submodules recursively (). Use docker images cache from merged PRs in master and release branches (). Fix pagination issue in GITHUBJOBID() ().
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.3.16.md

layout: release date: 2020-6-22 tag: v0.3.16 language: en Mesheryctl Feature: Addition of `mesheryctl system` as the new command for lifecycle management of Meshery. All Meshery lifecycle management commands like `start`, `stop`, `reset`, `logs` and so on are now found under `system`. Feature: Addition of `mesheryctl system config` as a new subcommand to assist with configuring Meshery to communicate with Kubernetes deployments in GKE, AKS, and EKS.
Project: YugabyteDB (App Definition and Development / Database)
File: create_foreign_data_wrapper.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="1228" height="70" viewbox="0 0 1228 70"><path class="connector" d="M0 22h15m67 0h10m75 0h10m52 0h10m78 0h10m83 0h30m78 0h10m107 0h20m-225 25q0 5 5 5h5m38 0h10m78 0h74q5 0 5-5m-220-25q5 0 5 5v33q0 5 5 5h205q5 0 5-5v-33q0-5 5-5m5 0h30m89 0h10m113 0h20m-242 25q0 5 5 5h5m38 0h10m89 0h80q5 0 5-5m-237-25q5 0 5 5v33q0 5 5 5h222q5 0 5-5v-33q0-5 5-5m5 0h30m74 0h10m25 0h10m92 0h10m25 0h20m-281 0q5 0 5 5v8q0 5 5 5h256q5 0 5-5v-8q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="67" height="25" rx="7"/><text class="text" x="25" y="22">CREATE</text><rect class="literal" x="92" y="5" width="75" height="25" rx="7"/><text class="text" x="102" y="22">FOREIGN</text><rect class="literal" x="177" y="5" width="52" height="25" rx="7"/><text class="text" x="187" y="22">DATA</text><rect class="literal" x="239" y="5" width="78" height="25" rx="7"/><text class="text" x="249" y="22">WRAPPER</text><a xlink:href="../../../syntaxresources/grammardiagrams#fdw-name"><rect class="rule" x="327" y="5" width="83" height="25"/><text class="text" x="337" y="22">fdwname</text></a><rect class="literal" x="440" y="5" width="78" height="25" rx="7"/><text class="text" x="450" y="22">HANDLER</text><a xlink:href="../../../syntaxresources/grammardiagrams#handler-name"><rect class="rule" x="528" y="5" width="107" height="25"/><text class="text" x="538" y="22">handlername</text></a><rect class="literal" x="440" y="35" width="38" height="25" rx="7"/><text class="text" x="450" y="52">NO</text><rect class="literal" x="488" y="35" width="78" height="25" rx="7"/><text class="text" x="498" y="52">HANDLER</text><rect class="literal" x="685" y="5" width="89" height="25" rx="7"/><text class="text" x="695" y="22">VALIDATOR</text><a xlink:href="../../../syntaxresources/grammardiagrams#validator-name"><rect class="rule" x="784" y="5" width="113" height="25"/><text class="text" x="794" y="22">validatorname</text></a><rect class="literal" x="685" y="35" width="38" height="25" rx="7"/><text class="text" x="695" y="52">NO</text><rect class="literal" x="733" y="35" width="89" height="25" rx="7"/><text class="text" x="743" y="52">VALIDATOR</text><rect class="literal" x="947" y="5" width="74" height="25" rx="7"/><text class="text" x="957" y="22">OPTIONS</text><rect class="literal" x="1031" y="5" width="25" height="25" rx="7"/><text class="text" x="1041" y="22">(</text><a xlink:href="../../../syntaxresources/grammardiagrams#fdw-options"><rect class="rule" x="1066" y="5" width="92" height="25"/><text class="text" x="1076" y="22">fdwoptions</text></a><rect class="literal" x="1168" y="5" width="25" height="25" rx="7"/><text class="text" x="1178" y="22">)</text><polygon points="1224,29 1228,29 1228,15 1224,15" style="fill:black;stroke-width:0"/></svg>
Project: StarRocks (App Definition and Development / Database)
File: covar_samp.md

displayed_sidebar: "English" Returns the sample covariance of two expressions. This function is supported from v2.5.10. It can also be used as a window function. ```Haskell COVAR_SAMP(expr1, expr2) ``` `expr1` and `expr2` must evaluate to TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, or DECIMAL. If `expr1` and `expr2` are table columns, this function calculates the sample covariance of these two columns. Returns a DOUBLE value. The formula is as follows, where `n` represents the row count of the table: <!--$$ \frac{\sum{i=1}^{n} (xi - \bar{x})(y_i - \bar{y})}{n-1} $$--> A data row is counted only when the two columns in this row are non-null values. Otherwise, this data row is eliminated from the result. 0 is returned if `n` is 1. NULL is returned in any input is NULL. Suppose table `agg` has the following data: ```plaintext mysql> select * from agg; ++-+-+ | no | k | v | ++-+-+ | 1 | 10.00 | NULL | | 2 | 10.00 | 11.00 | | 2 | 20.00 | 22.00 | | 2 | 25.00 | NULL | | 2 | 30.00 | 35.00 | ++-+-+ ``` Calculate the sample covariance of the `k` and `v`` columns: ```plaintext mysql> select no,COVAR_SAMP(k,v) from agg group by no; ++--+ | no | covar_samp(k, v) | ++--+ | 1 | NULL | | 2 | 119.99999999999999 | ++--+ ```
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: SPECIAL_INTEREST_GROUPS.md

OpenAPI Special Interest Groups, or "SIGs", are the OpenAPI Initiative's way of focusing work in particular areas. SIGs may start with just a Slack channel to guage interest. SIGs with enough traction to produce work may have their own GitHub repositories and regular Zoom calls, and ultimately produce work that becomes part of, or a companion to, the OpenAPI Specification. Code Generation JSON Schema vocabulary special interest (working) group channel: #sig-codegen Focusing on finance topics such as Open Banking / Open Finance channel: #sig-finance Focusing on the efforts. channel: #sig-formats Work Items: , Focusing on how industry standards groups make use of OpenAPI specifications. channel: #sig-industry-standards A place to discuss how to represent how APIs change in time in the context of OpenAPI. channel: #sig-lifecycle Working group for the next major (post-3.x) version of the OpenAPI Specification GitHub: Zoom Meetings: Tuesdays at 9AM US-Pacific The Overlay specification defines a way of creating documents that contain information to be merged with an OpenAPI description at some later point in time, for the purpose of updating the OpenAPI description with additional information. GitHub: channel: #sig-overlays Workgroup to shape security components of the OpenAPI Specification. channel: #sig-security Service level agreements and APIs. GitHub: channel: #sig-sla An OpenAPI Initiative workgroup to address industry specific connective/API concerns of the travel industry. channel: #sig-travel The OpenAPI Specification provides a way to document individual API calls and how to use them, but it doesn't give insight into the common ways to sequence those operations. While all APIs can benefit from formally describing these workflows, this is particularly important when considering more complex or more secure APIs. The OpenAPI Workflows Special Interest Group was created to address this common problem. The goal is to construct a formal way to describe these sequences and support documentation of flows, such as a multi-part OAuth flow with JSON signing and refresh token behavior. GitHub: channel: #sig-workflows Zoom Meetings: Wednesdays at 9AM US-Pacific
Project: StarRocks (App Definition and Development / Database)
File: DROP_ROLE.md

displayed_sidebar: "English" Drops a role. If a role has been granted to a user, the user still has the privileges associated with this role even after the role is dropped. :::tip Only users with the `user_admin` role can drop a role. cannot be dropped. ::: ```sql DROP ROLE <role_name> ``` Drop a role. ```sql DROP ROLE role1; ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.8.7.22-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Better check for connection usability and also catch any exception in RabbitMQ shutdown just in case. (). Backported in : Fix the number of threads used in `GLOBAL IN` subquery (it was executed in single threads since bugfix). (). Backported in : Fix segfault while inserting into column with type LowCardinality(Nullable) in Avro input format. (). Do not add const group by key for query with only having. (). Merging (). Fix terminate on uncaught exception ().
Project: external-secrets (Provisioning / Security & Compliance)
File: ownership-deletion-policy.md

The External Secrets Operator manages the lifecycle of secrets in Kubernetes. With `creationPolicy` and `deletionPolicy` you get fine-grained control of its lifecycle. !!! note "Creation/Deletion Policy Combinations" Some combinations of creationPolicy/deletionPolicy are not allowed as they would delete existing secrets: <br/>- `deletionPolicy=Delete` & `creationPolicy=Merge` <br/>- `deletionPolicy=Delete` & `creationPolicy=None` <br/>- `deletionPolicy=Merge` & `creationPolicy=None` The field `spec.target.creationPolicy` defines how the operator creates the a secret. The External Secret Operator creates secret and sets the `ownerReference` field on the Secret. This secret is subject to if the initial `ExternalSecret` is absent. If a secret with the same name already exists that is not owned by the controller it will result in a conflict. The operator will just error out, not claiming the ownership. !!! note "Secrets with `ownerReference` field not found" If the secret exists and the ownerReference field is not found, the controller treats this secret as orphaned. It will take ownership of this secret by adding an `ownerReference` field and updating it. The operator creates the secret but does not set the `ownerReference` on the Secret. That means the Secret will not be subject to garbage collection. If a secret with the same name already exists it will be updated. The operator does not create a secret. Instead, it expects the secret to already exist. Values from the secret provider will be merged into the existing secret. Note: the controller takes ownership of a field even if it is owned by a different entity. Multiple ExternalSecrets can use `creationPolicy=Merge` with a single secret as long as the fields don't collide - otherwise you end up in an oscillating state. The operator does not create or update the secret, this is basically a no-op. DeletionPolicy defines what should happen if a given secret gets deleted from the provider. DeletionPolicy is only supported on the specific providers, please refer to our . Retain will retain the secret if all provider secrets have been deleted. If a provider secret does not exist the ExternalSecret gets into the SecretSyncedError status. Delete deletes the secret if all provider secrets are deleted. If a secret gets deleted on the provider side and is not accessible anymore this is not considered an error and the ExternalSecret does not go into SecretSyncedError status. This is also true for new ExternalSecrets mapping to non-existing secrets in the provider. Merge removes keys in the secret, but not the secret itself. If a secret gets deleted on the provider side and is not accessible anymore this is not considered an error and the ExternalSecret does not go into SecretSyncedError status.
Project: Meshery (Provisioning / Automation & Configuration)
File: publishing-a-design.md

layout: default title: Publishing a Design abstract: Publishing a design lets you make your content visible to any anonymous visitor with the link. permalink: extensions/publishing-a-design language: en display-title: "false" list: include type: extensions category: meshmap Publishing a design lets you make your content visible to any anonymous visitor of meshery.io/catalog and any Meshery Cloud user. Anyone with the link can view the design. You can publish design into Meshery's Catalog using Extensions. Let's discuss the process below. Step 1: Access the Extensions UI Note: To publish a design you must be the author of the design. Step 2: Navigate to the Designs Tab and Select your Design Once you have accessed the Extension's UI, navigate to the Designs tab. In this tab you can see all your designs with their "<b>Name</b>" and "<b>Date Modified</b>". From the designs table, you can click or drag and drop your design onto the canvas. <a href="{{ site.baseurl }}/assets/img/meshmap/design.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/design.png" /></a> Step 3: Select Publish actions on the design To select actions, hover over your design in the table and choose <b>publish</b>. <a href="{{ site.baseurl }}/assets/img/meshmap/action-publish.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/action-publish.png" /></a> Step 4: Confirm additional information about your design Catalog curation involves a process of review by Meshery Maintainers. In order to facilitate this review process, add details about your design. Indentify the most appropriate design type by selecting from the predefined list, and also, identify technologies included in your design by checkmarking one or more of them. Click "Publish" in order to send your design for review by Meshery Maintainers. You will receive an email confirming your submission. <a href="{{ site.baseurl }}/assets/img/meshmap/publish-modal.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/publish-modal.png" /></a> Step 5: Congratulations on publishing your first design You are all set. Your request to publish this design is sent to Meshery Maintainers. Create more designs! <div style="max-width: 800px"> <div class="iframe-container"> <iframe src="https://www.youtube.com/embed/UCKS4eSB7AY" title="How to Publish Designs using Meshery Extension" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> </div> </div>
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: kubeshield.md

title: KubeShield subtitle: Secure Kubernetes using eBPF & Open Policy Agent software: linux kubernetes ebpf labels: layer: application category: filtering code: https://github.com/kubeshield/bpf-opa-demo blogs: https://blog.byte.builders/post/bpf-opa/ docs_features: kubernetes: note: | KubeShield implements runtime policy for containers in a Kubernetes cluster using eBPF. Follow the to get up and running. Ensure runtime security in any linux machine by combining Extended Berkeley Packet Filter(eBPF) and Open Policy Agent.