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

sidebar_position: 1 sidebar_label: 2022 Backport CI checks to 22.1 release branch. (). Backported in : Fix usage of functions `array` and `tuple` with literal arguments in distributed queries. Previously it could lead to `Not found columns` exception. (). Backported in : Fix crash while reading of nested tuples. Fixes . (). Backported in : Fix segfault while parsing ORC file with corrupted footer. Closes . (). Backported in : Fix bug which lead to inability for server to start when both replicated access storage and keeper are used. Introduced two settings for keeper socket timeout instead of settings from default user: `keeperserver.socketreceivetimeoutsec` and `keeperserver.socketsendtimeoutsec`. Fixes . (). Backported in : Fixed minor race condition that might cause "intersecting parts" error in extremely rare cases after ZooKeeper connection loss. (). Backported in : Fix inserts to distributed tables in case of change of native protocol. The last change was in the version version 22.1, so there may be some failures of inserts to distributed tables after upgrade to that version. (). Backported in : Fix bug which can rarely lead to error "Cannot read all data" while reading LowCardinality columns of MergeTree table engines family which stores data on remote file system like S3. (). Backported in : Fix metric `Query`, which shows number of executing queries. In last several releases it was always 0. (). Backported in : Fix progress bar width. It was incorrectly rounded to integer number of characters. (). Backported in : Try to fix rare bug while reading of empty arrays, which could lead to `Data compressed with different methods` error. (). Backported in : Fix segfault in schema inference from url. Closes . ().
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Example_Batch.md

Sending messages in batch improves performance of delivering small messages. Messages of the same batch should have: same topic, same waitStoreMsgOK and no schedule support. You can send messages up to 4MiB at a time, but if you need to send a larger message, it is recommended to divide the larger messages into multiple small messages of no more than 1MiB. If you just send messages of no more than 4MiB at a time, it is easy to use batch: ```java String topic = "BatchTest"; List<Message> messages = new ArrayList<>(); messages.add(new Message(topic, "TagA", "OrderID001", "Hello world 0".getBytes())); messages.add(new Message(topic, "TagA", "OrderID002", "Hello world 1".getBytes())); messages.add(new Message(topic, "TagA", "OrderID003", "Hello world 2".getBytes())); try { producer.send(messages); } catch (Exception e) { e.printStackTrace(); //handle the error } ``` The complexity only grow when you send large batch and you may not sure if it exceeds the size limit (4MiB). At this time, youd better split the lists: ```java public class ListSplitter implements Iterator<List<Message>> { private final int SIZE_LIMIT = 1024 1024 4; private final List<Message> messages; private int currIndex; public ListSplitter(List<Message> messages) { this.messages = messages; } @Override public boolean hasNext() { return currIndex < messages.size(); } @Override public List<Message> next() { int startIndex = getStartIndex(); int nextIndex = startIndex; int totalSize = 0; for (; nextIndex < messages.size(); nextIndex++) { Message message = messages.get(nextIndex); int tmpSize = calcMessageSize(message); if (tmpSize + totalSize > SIZE_LIMIT) { break; } else { totalSize += tmpSize; } } List<Message> subList = messages.subList(startIndex, nextIndex); currIndex = nextIndex; return subList; } private int getStartIndex() { Message currMessage = messages.get(currIndex); int tmpSize = calcMessageSize(currMessage); while(tmpSize > SIZE_LIMIT) { currIndex += 1; Message message = messages.get(curIndex); tmpSize = calcMessageSize(message); } return currIndex; } private int calcMessageSize(Message message) { int tmpSize = message.getTopic().length() + message.getBody().length; Map<String, String> properties = message.getProperties(); for (Map.Entry<String, String> entry : properties.entrySet()) { tmpSize += entry.getKey().length() + entry.getValue().length(); } tmpSize = tmpSize + 20; // Increase the log overhead by 20 bytes return tmpSize; } } // then you could split the large list into small ones: ListSplitter splitter = new ListSplitter(messages); while (splitter.hasNext()) { try { List<Message> listItem = splitter.next(); producer.send(listItem); } catch (Exception e) { e.printStackTrace(); // handle the error } } ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: delete-a-postgresql-cluster.md

title: Delete a PostgreSQL Cluster description: How to delete a PostgreSQL Cluster keywords: [postgresql, delete a cluster] sidebar_position: 7 sidebar_label: Delete protection import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; :::note The termination policy determines how a cluster is deleted. ::: | terminationPolicy | Deleting Operation | |:-|:-| | `DoNotTerminate` | `DoNotTerminate` blocks delete operation. | | `Halt` | `Halt` deletes workload resources such as statefulset, deployment workloads but keep PVCs. | | `Delete` | `Delete` deletes workload resources and PVCs but keep backups. | | `WipeOut` | `WipeOut` deletes workload resources, PVCs and all relevant resources included backups. | To check the termination policy, execute the following command. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```bash kbcli cluster list pg-cluster NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME pg-cluster default postgresql postgresql-14.7.0 Delete Running Mar 03,2023 18:49 UTC+0800 ``` </TabItem> <TabItem value="kubectl" label="kubectl"> ```bash kubectl -n demo get cluster pg-cluster NAME CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS AGE pg-cluster postgresql postgresql-14.8.0 Delete Running 29m ``` </TabItem> </Tabs> Run the command below to delete a specified cluster. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```bash kbcli cluster delete pg-cluster ``` </TabItem> <TabItem value="kubectl" label="kubectl"> If you want to delete a cluster and its all related resources, you can modify the termination policy to `WipeOut`, then delete the cluster. ```bash kubectl patch -n demo cluster pg-cluster -p '{"spec":{"terminationPolicy":"WipeOut"}}' --type="merge" kubectl delete -n demo cluster pg-cluster ``` </TabItem> </Tabs>
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' 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: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: sql-datafiltering.md

title: SQL Database Data Filtering labels: layer: data category: filtering software: sqlite code: https://github.com/open-policy-agent/contrib/tree/master/datafilterexample blogs: https://blog.openpolicyagent.org/write-policy-in-opa-enforce-policy-in-sql-d9d24db93bf4 inventors: styra This integration enables the client of a SQL database to enhance a SQL query so that the results obey an OPA-defined policy.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.19.md

layout: release date: 2022-11-01 tag: v0.6.19 language: en Fix prettification logic @Revolyssup (#6476) [Chore] Delete output directory for component generation @sudo-NithishKarthik (#6456) [Feat] Add support for splitting result into multiple files @sudo-NithishKarthik (#6455) [Fix] Permission issues with creating directory in static components generation script @sudo-NithishKarthik (#6442) [Server] Refactoring of Function Comments @dipankardas011 (#6421) chore: Upgrade meshkit @sudo-NithishKarthik (#6433) chore: Upgrade meshkit @sudo-NithishKarthik (#6432) [mesheryctl] improve the error messages shown to users for "mesheryctl pattern" @legendarykamal (#6323) [extension] Update redux store var for every child ext of useraccount @theBeginner86 (#6462) fixed osm logo @warunicorn19 (#6461) [rjsf] additionalProperties Key/Value @harkiratsm (#6454) Increased Istio logo size @parthn2 (#6452) [UI] Reducing the size of clone Icon @legendarykamal (#6438) [MeshModel] Add workflow and script to generate components | CU-3yvwk9h @sudo-NithishKarthik (#6387) [Fix] update commit permissions for workflow @sudo-NithishKarthik (#6444) [MeshModel] Add workflow and script to generate components | CU-3yvwk9h @sudo-NithishKarthik (#6387) Fix manual chart release @Revolyssup (#6429) Updated adapter and general concept documentation pages @michizhou (#6448) Thank you to our contributors for making this release possible: @Revolyssup, @dipankardas011, @harkiratsm, @l5io, @leecalcote, @legendarykamal, @michizhou, @parthn2, @sudo-NithishKarthik, @theBeginner86, @warunicorn19 and l5io
Project: YugabyteDB (App Definition and Development / Database)
File: array-to-string.md

title: arraytostring() linkTitle: arraytostring() headerTitle: arraytostring() description: arraytostring() menu: v2.18: identifier: array-to-string parent: array-functions-operators type: docs Purpose: Return a `text` value computed by representing each array value, traversing these in row-major order, by its `::text` typecast, using the supplied delimiter between each such representation. (The result, therefore, loses all information about the arrays geometric properties.) Optionally, represent `NULL` by the supplied `text` value. The term "row-major order" is explained in within the section "Functions for reporting the geometric properties of an array". Signature: ``` input value: anyarray, text [, text] return value: text ``` Example: ```plpgsql create type rt as (f1 int, f2 text); create table t(k int primary key, arr rt[]); insert into t(k, arr) values(1, array[ array[ array[(1, 'a')::rt, (2, null)::rt, null, (3, 'c')::rt] ] ]::rt[] ); select arr::text from t where k = 1; ``` It shows this: ``` arr -- {{{"(1,a)","(2,)",NULL,"(3,c)"}}} ``` To understand the syntax of the text of this literal, especially when a field is `NULL`, see . Now do this: ```plpgsql select arraytostring( arr, -- the input array ' | ') -- the delimiter from t where k = 1; ``` It shows this: ``` arraytostring (1,a) | (2,) | (3,c) ``` Notice that the third, `NULL`, array value is not represented. Rather, this implied by the absence of any characters between the comma and the right parenthesis delimiters. Now do this; ```plpgsql select arraytostring( arr, -- the input array ' | ', -- the delimiter '?') -- the null indicator from t where k = 1; ``` It shows this: ``` arraytostring -- (1,a) | (2,) | ? | (3,c) ``` The third array value is now represented by `?`. But the fact that "f2" `IS NULL` within the second array value is not represented by `?`. In other words, this technique for visualizing `NULL` is applied only at the granularity of top-level array values and not within such values when they are composite.
Project: ArangoDB (App Definition and Development / Database)
File: faq.md

<!-- Copyright 2018 Paul Fultz II Distributed under the Boost Software License, Version 1.0. (http://www.boost.org/LICENSE10.txt) --> FAQ === Mutable function objects are not prohibited, they just need to be explicit by using the adaptor . The main reason for this, is that it can lead to many suprising behaviours. Many times function objects are copied by value everywhere. For example, ```cpp struct counter { int i; counter() : i(0) {} template<class... Ts> int operator()(Ts&&...) { return i++; } }; counter c{}; proj(mutable_(c))(1,1); // Prints 0, not 2 std::cout << c.i << std::endl; ``` The example won't ever yield the expected value, because the function mutates a copy of the objects. Instead, `std::ref` should be used: ```cpp counter c{}; proj(std::ref(c))(1,1); // Prints 2 std::cout << c.i << std::endl; ``` Which will print the expected value. Another reason why `const` is required is because of supporting `constexpr` on C++11 compilers. In C++11, `constexpr` implies `const`, so it would be impossible to provide a non-const overload for functions that is `constexpr`. Instead, `constexpr` would have to be made explicit. Considering the pitfalls of mutable function objects, it would be better to make mutability explicit rather than `constexpr`. Not really, since the objects are empty, there is no data access. There is a static assert to guard against this restriction. Now there could be an insane implementation where this doesn't work(perhaps the lambdas are not empty for some strange reason), which the library would have to apply a different technique to make it work. However, this is quite unlikely considering that C++ will probably get constexpr lambdas and inline variables in the future. Alternatively, the factory pattern can be used instead of , which doesn't require an reinterpret cast: ```cpp struct sum_factory { auto operator*() const { return { return x + y; }; } } BOOSTHOFSTATICFUNCTION(sum) = boost::hof::indirect(sumfactory{}); ```
Project: KubeDL (Provisioning / Automation & Configuration)
File: SECURITY.md

The KubeDL community takes all security bugs seriously. Thank you for improving the security quality of KubeDL. We adopt a private disclosure process for security issues. If you find a bug, a security vulnerability or any security related issues, please DO NOT file a public issue. Do not create a Github issue. Instead, send your report privately to . Security reports are greatly appreciated and we will publicly thank you for it. Please provide as much information as possible, so we can react quickly. For instance, that could include: Description of the location and potential impact of the vulnerability; A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed packet captures are all helpful to us) Whatever else you think we might need to identify the source of this vulnerability One of our maintainers will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the maintainers will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-documentdb-controller.md

layout: integration title: AWS DocumentDB subtitle: Collaborative and visual infrastructure as code for AWS DocumentDB image: /assets/img/integrations/aws-documentdb-controller/icons/color/aws-documentdb-controller-color.svg permalink: extensibility/integrations/aws-documentdb-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-documentdb-controller description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: GitHub components: name: db-cluster colorIcon: assets/img/integrations/aws-documentdb-controller/components/db-cluster/icons/color/db-cluster-color.svg whiteIcon: assets/img/integrations/aws-documentdb-controller/components/db-cluster/icons/white/db-cluster-white.svg description: name: db-instance colorIcon: assets/img/integrations/aws-documentdb-controller/components/db-instance/icons/color/db-instance-color.svg whiteIcon: assets/img/integrations/aws-documentdb-controller/components/db-instance/icons/white/db-instance-white.svg description: name: db-subnet-group colorIcon: assets/img/integrations/aws-documentdb-controller/components/db-subnet-group/icons/color/db-subnet-group-color.svg whiteIcon: assets/img/integrations/aws-documentdb-controller/components/db-subnet-group/icons/white/db-subnet-group-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-documentdb-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-documentdb-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: field-export colorIcon: assets/img/integrations/aws-documentdb-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-documentdb-controller/components/field-export/icons/white/field-export-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: Clair (Provisioning / Security & Compliance)
File: indexing.md

The service is responsble for "indexing a manifest". Indexing involves taking a manifest representing a container image and computing its constituent parts. The indexer is trying to discover what packages exist in the image, what distribution the image is derived from, and what package repositories are used within the image. Once this information is computed it is persisted in an IndexReport. The IndexReport is an intermediate data structure describing the contents of a container image. This report can be fed to a node for vulnerability analysis. ClairV4 treats all manifests and layers as . In the context of ClairV4 this means once we index a specific manifest we will not index it again unless it's required, and likewise with individual layers. This allows a large reduction in work. For example, consider how many images in a registry may use "ubuntu:artful" as a base layer. It could be a large majority of images if the developers prefer basing their images off ubuntu. Treating the layers and manifests as content addressable means we will only fetch and scan the base layer once. There are of course conditions where ClairV4 should re-index a manifest. When an internal component such as a package scanner is updated, Clair will know to perform the scan with the new package scanner. Clair has enough information to determine that a component has changed and the IndexReport may be different this time around. A client can track ClairV4's `index_state` endpoint to understand when an internal component has changed and subsequently issue re-indexes. See our guide to learn how to view our api specification. In summary, you should understand that Indexing is the process Clair uses to understand the contents of layers. For a more indepth look at indexing check out the
Project: ClickHouse (App Definition and Development / Database)
File: v21.2.4.6-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fixed the behavior when in case of broken JSON we tried to read the whole file into memory which leads to exception from the allocator. Fixes . (). Backported in : Check if table function `view` is used in expression list and throw an error. This fixes . (). Backported in : Fix `LOGICALERROR` for `joinuse_nulls=1` when JOIN contains const from SELECT. (). Backported in : Fix infinite loop when propagating WITH aliases to subqueries. This fixes . (). Backported in : Add proper checks while parsing directory names for async INSERT (fixes SIGSEGV). (). Backported in : Fix subquery with union distinct and limit clause. close . (). Backported in : Fix usage of `-Distinct` combinator with `-State` combinator in aggregate functions. (). Backported in : `USE database;` query did not work when using MySQL 5.7 client to connect to ClickHouse server, it's fixed. Fixes . ().
Project: StarRocks (App Definition and Development / Database)
File: date_sub.md

displayed_sidebar: "English" Subtracts the specified time interval from a date. ```Haskell DATETIME DATE_SUB(DATETIME|DATE date,INTERVAL expr type) ``` `date`: It must be a valid DATE or DATETIME expression. `expr`: the time interval you want to subtract. It must be of the INT type. `type`: the unit of the time interval. It can only be set to any of the following values: YEAR, QUARTER, MONTH, DAY, HOUR, MINUTE, SECOND, MILLISECOND (since 3.1.7), and MICROSECOND (since 3.1.7). Returns a DATETIME value. If the date does not exist, for example, `2020-02-30`, or if the date is not a DATE or DATETIME value, NULL is returned. ```Plain Text select date_sub('2010-11-30 23:59:59', INTERVAL 2 DAY); +-+ | date_sub('2010-11-30 23:59:59', INTERVAL 2 DAY) | +-+ | 2010-11-28 23:59:59 | +-+ select date_sub('2010-11-30', INTERVAL 2 hour); +--+ | date_sub('2010-11-30', INTERVAL 2 HOUR) | +--+ | 2010-11-29 22:00:00 | +--+ select date_sub('2010-02-30', INTERVAL 2 DAY); +-+ | date_sub('2010-02-30', INTERVAL 2 DAY) | +-+ | NULL | +-+ select date_sub('2010-11-30 23:59:59', INTERVAL 2 QUARTER); +--+ | date_sub('2010-11-30 23:59:59', INTERVAL 2 QUARTER) | +--+ | 2010-05-30 23:59:59 | +--+ select subdate('2010-11-30 23:59:59', INTERVAL 2 millisecond); +--+ | subdate('2010-11-30 23:59:59', INTERVAL 2 MILLISECOND) | +--+ | 2010-11-30 23:59:58.998000 | +--+ select date_sub('2010-11-30 23:59:59', INTERVAL 2 microsecond); ++ | date_sub('2010-11-30 23:59:59', INTERVAL 2 MICROSECOND) | ++ | 2010-11-30 23:59:58.999998 | ++ ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: blog.md

title: "{{ replace .Name "-" " " | title }}" date: "{{ .Date }}" categories: blog authors: "Your Name" <!-- 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: Meshery (Provisioning / Automation & Configuration)
File: v0.7.17.md

layout: release date: 2024-02-09 tag: v0.7.17 [Meshmodel] Update pod,replicaset,job,cronjob to have genealogy parent @aabidsofi19 (#10248) updated pencil node @captain-Akshay (#10225) add: Relationship between Event component and other k8s components @RipulHandoo (#10194) change log severity to debug @MUzairS15 (#10221) [bug] Fix pattern apply @theBeginner86 (#10142) Fix golangci-lint issues in mesheryctl. @gyohuangxin (#10226) Fix icon color @sudhanshutech (#10245) leecalcote/docs/connections delete modal @leecalcote (#10236) [UI] Global Navigation Menu Tooltip Enhancement @ChetanPatil12 (#10219) Reduced font size of Metadata Labels in small viewport @cesartheroman (#10222) [Server] Enhance Design Import Notification @ASK-03 (#10223) [UI] Registry UI issues @Yashsharma1911 (#10208) Update existing queries and add rtk client for `performance-profile` api's @sudhanshutech (#10220) [bug] Fix pattern apply @theBeginner86 (#10142) update: issue_template for model @RipulHandoo (#10188) [Docs] Deleting Environments @leecalcote (#10237) [Docs] Jekyll Build Cache @leecalcote (#10239) suggested reading edit @mgurrie (#10213) #10145 Added two suggeste d reading links to Docs Contributing page @suguslove10 (#10230) Fix SQL injection in /api/system/meshsync/resources @gyohuangxin (#10207) Thank you to our contributors for making this release possible: @ASK-03, @ChetanPatil12, @MUzairS15, @RipulHandoo, @Yashsharma1911, @aabidsofi19, @captain-Akshay, @cesartheroman, @gyohuangxin, @leecalcote, @mgurrie, @sudhanshutech, @suguslove10 and @theBeginner86