cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.53.md

layout: release date: 2023-02-23 tag: v0.6.53 language: en Fix all dryRun errors and change response format @Revolyssup (#7149) Bump github.com/containerd/containerd from 1.6.15 to 1.6.18 in /scripts/component_updation @dependabot (#7122) Bump golang.org/x/net from 0.5.0 to 0.7.0 in /scripts/component_updation @dependabot (#7123) Fix Meshmodel structure @Revolyssup (#7121) [UI] Fix regression issue of notification icon and svg scaling issue @Chadha93 (#7156) Fixed theme colour should be consistent in settings and configuration page for dark mode @Yashsharma1911 (#7152) fixed svg in meshperformance @yash37158 (#7137) fixed: Footer not supporting dark mode @Yashsharma1911 (#7139) Update uidevserver.js @acald-creator (#7130) [chore] Upgrade eslint to v8 @acald-creator (#7124) Fix the regression of playground footer @Chadha93 (#7129) Fixed: Dashboard not quite right in Meshery-UI and MeshMap @Yashsharma1911 (#7118) Remove title from _document.js file in provider-ui @Nikhil-Ladha (#7117) Bump github.com/containerd/containerd from 1.6.15 to 1.6.18 @dependabot (#7101) [chore] Upgrade eslint to v8 @acald-creator (#7124) fixed jquery error @VIKAS0264 (#7134) fix extension points link in api.md file @vishalvivekm (#7136) Update tooltip text @vishalvivekm (#7144) add dark mode styles to table elements and head @rinkuhasija (#7131) Fix the incorrect link @pratik2315 (#7127) Update all code snippets to new style in Meshery Docs @chinu-anand (#7094) Updated Meshery Token UI .png @b0id (#7119) Thank you to our contributors for making this release possible: @Chadha93, @Nikhil-Ladha, @Revolyssup, @VIKAS0264, @Yashsharma1911, @acald-creator, @b0id, @chinu-anand, @dependabot, @dependabot[bot], @leecalcote, @pratik2315, @rinkuhasija, @vishalvivekm and @yash37158
Project: StarRocks (App Definition and Development / Database)
File: CANCEL_RESTORE.md

displayed_sidebar: "English" Cancels an ongoing RESTORE task in a specified database. CAUTION If a RESTORE task is canceled during the COMMIT phase, the restored data will be corrupted and inaccessible. In this case, you can only perform the RESTORE operation again and wait for the job to complete. ```SQL CANCEL RESTORE FROM <db_name> ``` | Parameter | Description | | - | | | db_name | Name of the database that the RESTORE task belongs to. | Example 1: Cancels the RESTORE task under the database `example_db`. ```SQL CANCEL RESTORE FROM example_db; ```
Project: Qdrant (App Definition and Development / Database)
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: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-filter-import.md

layout: default title: mesheryctl-filter-import permalink: reference/mesheryctl/filter/import redirect_from: reference/mesheryctl/filter/import/ type: reference display-title: "false" language: en command: filter subcommand: import Import a WASM filter Import a WASM filter from a URI (http/s) or local filesystem path <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter import [URI] [flags] </div> </pre> Import a filter file from local filesystem <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter import /path/to/filter.wasm </div> </pre> Import a filter file from a remote URI <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter import https://example.com/myfilter.wasm </div> </pre> Add WASM configuration If the string is a valid file in the filesystem, the file is read and passed as a string. Otherwise, the string is passed as is. Use quotes if the string contains spaces <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter import /path/to/filter.wasm --wasm-config [filepath|string] </div> </pre> Specify the name of the filter to be imported. Use quotes if the name contains spaces <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl filter import /path/to/filter.wasm --name [string] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for import -n, --name string (optional) filter name -w, --wasm-config string (optional) WASM configuration filepath/string </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -t, --token string Path to token file default from current context -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.18.md

layout: release date: 2021-06-03 tag: v0.5.18 refactor mesheryctl @navendu-pottekkat (#3115) release notes for v0.5.15,v0.5.16,v0.5.17 @umairnsr87 (#3130) [Patterns] Add support for deploying applications using meshery @utkarsh-pro (#3037) Workflow for deleting current context @metonymic-smokey (#3060) Kumarabd/feature/helm charts @kumarabd (#3076) [ImgBot] Optimize images @imgbot (#3088) Kuma Adapter URL fixed @debjani1413 (#3087) Fix time parsing issue in local provider @utkarsh-pro (#3080) Fix operator lifecycle for update and reset @metonymic-smokey (#3001) Added Filters and removed edit option @Chadha93 (#3073) [mesheryctl] List subcommand under mesheryctl perf @piyushsingariya (#2928) Revert "[Docs] mesheryctl: Create a subcommand for system logs, restart and reset" @adithyaakrishna (#3064) Add filters to database @navendu-pottekkat (#3062) Bump fortio.org/fortio from 1.14.2 to 1.15.2 @dependabot (#3108) Bump @types/react-relay from 7.0.17 to 11.0.1 in /ui @dependabot (#3098) Bump react-relay from 11.0.0 to 11.0.2 in /ui @dependabot (#3101) Bump eslint-plugin-react from 7.23.2 to 7.24.0 in /provider-ui @dependabot (#3104) Bump notistack from 1.0.6 to 1.0.9 in /ui @dependabot (#3106) Bump github.com/vektah/gqlparser/v2 from 2.1.0 to 2.2.0 @dependabot (#3107) Bump github.com/prometheus/common from 0.23.0 to 0.25.0 @dependabot (#3109) Bump github.com/lib/pq from 1.10.1 to 1.10.2 @dependabot (#3111) Bump google.golang.org/grpc from 1.37.0 to 1.38.0 @dependabot (#3114) Bump start-server-and-test from 1.12.1 to 1.12.3 in /provider-ui @dependabot (#3100) Bump cypress from 7.2.0 to 7.4.0 in /provider-ui @dependabot (#3099) Bump eslint-plugin-cypress from 2.11.2 to 2.11.3 in /provider-ui @dependabot (#3096) Bump next from 10.2.0 to 10.2.3 in /provider-ui @dependabot (#3102) Fix "Service Meshes" e2e test @ramrodo (#3119) Bump relay-compiler from 10.1.3 to 11.0.2 in /ui @dependabot (#3092) Bump husky from 5.1.2 to 6.0.0 in /ui @dependabot (#3105) Bump @cypress/code-coverage from 3.9.5 to 3.9.6 in /provider-ui @dependabot (#3097) Bump cypress from 6.8.0 to 7.4.0 in /ui @dependabot (#3095) Bump @fortawesome/free-regular-svg-icons from 5.15.2 to 5.15.3 in /ui @dependabot (#3093) Bump js-yaml from 4.0.0 to 4.1.0 in /ui @dependabot (#3091) Bump eslint-plugin-cypress from 2.11.2 to 2.11.3 in /ui @dependabot (#3090) Bump eslint from 7.25.0 to 7.27.0 in /provider-ui @dependabot (#3094) Bump github.com/layer5io/meshkit from 0.2.10 to 0.2.11 @dependabot (#3112) [CI] Remove unused hooks for Docker image building @leecalcote (#3056) Fix Release Notes Drafter @ramrodo (#3055) [Docs] mesheryctl pattern delete page added @amino19 (#3070) [Docs]Corrected error command in Quick Start Guide @sayantan1413 (#3071) [Docs] Universally append @Patil2099 (#3081) Open API Documentation #1 @piyushsingariya (#3012) [Docs] mesheryctl: Create a subcommand for system logs, restart and reset @Anita-ihuman (#3022) [Docs] - Added Docs for mesheryctl Commands and Updates Title for Doc Pages @adithyaakrishna (#3000)
Project: SPIRE (Provisioning / Key Management)
File: plugin_agent_workloadattestor_unix.md

The `unix` plugin generates unix-based selectors for workloads calling the agent. | Configuration | Description | Default | |--||| | `discoverworkloadpath` | If true, the workload path will be discovered by the plugin and used to provide additional selectors | false | | `workloadsizelimit` | The limit of workload binary sizes when calculating certain selectors (e.g. sha256). If zero, no limit is enforced. If negative, never calculate the hash. | 0 | If configured with `discoverworkloadpath = true`, the plugin will discover the workload path to provide additional selectors. If the plugin cannot discover the workload path or gather selectors based on the path, it will fail the attestation attempt. Discovering the workload path requires the agent to have sufficient platform-specific permissions. For example, on Linux, the agent would need to be able to read `/proc/<WORKLOAD PID>/exe`, likely requiring the agent to either run as root or the same user as the workload. Care must be taken to only enable this option if the agent will be run with sufficient permissions. General selectors: | Selector | Value | |-|--| | `unix:uid` | The user ID of the workload (e.g. `unix:uid:1000`) | | `unix:user` | The user name of the workload (e.g. `unix:user:nginx`) | | `unix:gid` | The group ID of the workload (e.g. `unix:gid:1000`) | | `unix:group` | The group name of the workload (e.g. `unix:group:www-data`) | | `unix:supplementarygid` | **Currently only supported on linux:** The supplementary group ID of the workload (e.g. `unix:supplementarygid:2000`) | | `unix:supplementarygroup` | **Currently only supported on linux:** The supplementary group name of the workload (e.g. `unix:supplementarygroup:www-data`) | Workload path enabled selectors (available when configured with `discoverworkloadpath = true`): | Selector | Value | ||--| | `unix:path` | The path to the workload binary (e.g. `unix:path:/usr/bin/nginx`) | | `unix:sha256` | The SHA256 digest of the workload binary (e.g. `unix:sha256:3a6eb0790f39ac87c94f3856b2dd2c5d110e6811602261a9a923d3bb23adc8b7`) | Security Considerations: Malicious workloads could cause the SPIRE agent to do expensive work calculating a sha256 for large workload binaries, causing a denial-of-service. Defenses against this are: disabling calculation entirely by setting `workloadsizelimit` to a negative value use `workloadsizelimit` to enforce a limit on the binary size the plugin is willing to hash. However, the same attack could be performed by spawning a bunch of processes under the limit. The workload API does not yet support rate limiting, but when it does, this attack can be mitigated by using rate limiting in conjunction with non-negative `workloadsizelimit`. A sample configuration: ```hcl WorkloadAttestor "unix" { } ``` This plugin is only supported on Unix systems.
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: content_bug_report.md

name: Content Bug Report about: Find a typo? Content out of date? Need a clarification? Please list the page or pages this bug is present on. Please file one issue for each bug you find. Only file an issue for a multi-page bug if the bug is indeed the same bug, across the pages. Tell us what content is causing the issue and how it is causing the issue. For example, "The code sample was confusing because it used advanced Rust features", or "The call to action on the community page was vague". (optional) Do you have a suggestion for how to fix the problem? Include your ideas here.
Project: ClickHouse (App Definition and Development / Database)
File: max.md

slug: /en/sql-reference/aggregate-functions/reference/max sidebar_position: 3 title: max Aggregate function that calculates the maximum across a group of values. Example: ``` SELECT max(salary) FROM employees; ``` ``` SELECT department, max(salary) FROM employees GROUP BY department; ``` If you need non-aggregate function to choose a maximum of two values, see `greatest`: ``` SELECT greatest(a, b) FROM table; ```
Project: Clair (Provisioning / Security & Compliance)
File: updatersandairgap.md

Clair utilizes go packages we call "updaters" that encapsulate the logic of fetching and parsing different vulnerability databases. Updaters are usually pared with a matcher to interpret if and how any vulnerability is related to a package. Operators may wish to update the vulnerability database less frequently or not import vulnerabilities from databases that they know will not be used. Updaters can be configured by `updaters` key at the top of the configuration. If updaters are being run automatically within the matcher processes, as is the default, the period for running updaters is configured under the matcher's configuration stanza. Specific sets of updaters can be selected by the `sets` list. If not present, the defaults of all upstream updaters will be used. ```yaml updaters: sets: rhel ``` Configuration for specific updaters can be passed by putting a key underneath the `config` member of the `updaters` object. The name of an updater may be constructed dynamically; users should examine logs to double-check names. The specific object that an updater expects should be covered in the updater's documentation. For example, to have the "rhel" updater fetch a manifest from a different location: ```yaml updaters: config: rhel: url: https://example.com/mirror/oval/PULP_MANIFEST ``` For additional flexibility, Clair supports running updaters in a different environment and importing the results. This is aimed at supporting installations that disallow the Clair cluster from talking to the Internet directly. An update procedure needs to arrange to call the relevant `clairctl` command in an environment with access to the Internet, move the resulting artifact across the airgap according to site policy, and then call the relevant `clairctl` command to import the updates. For example: ```sh clairctl export-updaters updates.json.gz ``` ```sh scp updates.json.gz internal-webserver:/var/www/ ``` ```sh clairctl import-updaters http://web.svc/updates.json.gz ``` Note that a configuration file is needed to run these commands. Matcher processes should have the `disable_updaters` key set to disable automatic updaters running. ```yaml matcher: disable_updaters: true ``` ```yaml indexer: airgap: true ``` ```yaml indexer: scanner: package: name: key: value repo: name: key: value dist: name: key: value ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: hazelcast.md

title: "Hazelcast" icon: /images/logos/powered-by/hazelcast.png hasLink: "https://beam.apache.org/documentation/runners/jet/" <!-- 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: CloudTTY (App Definition and Development / Application Definition & Image Build)
File: RELEASE.md

The `yaml` Project is released on an as-needed basis. The process is as follows: An issue is proposing a new release with a changelog since the last release All must LGTM this release An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION` The release issue is closed An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
Project: ShardingSphere (App Definition and Development / Database)
File: rewrite-test.en.md

+++ title = "SQL Rewrite Test" weight = 2 +++ Facing logic databases and tables cannot be executed directly in actual databases. SQL rewrite is used to rewrite logic SQL into rightly executable ones in actual databases, including two parts, correctness rewrite and optimization rewrite. rewrite tests are for these targets. The rewrite tests are in the test folder under `test/it/rewriter` . Followings are the main part for rewrite tests: test engine environment configuration assert data Test engine is the entrance of rewrite tests, just like other test engines, through Junit , read every and each data in the xml file under the target test type in `test\resources`, and then assert by the engine one by one Environment configuration is the yaml file under test type under `test\resources\yaml`. The configuration file contains dataSources, shardingRule, encryptRule and other info. for example: ```yaml dataSources: db: !!com.zaxxer.hikari.HikariDataSource driverClassName: org.h2.Driver jdbcUrl: jdbc:h2:mem:db;DBCLOSEDELAY=-1;DATABASETOUPPER=false;MODE=MYSQL username: sa password: rules: !SHARDING tables: t_account: actualDataNodes: db.taccount${0..1} tableStrategy: standard: shardingColumn: account_id shardingAlgorithmName: accounttableinline keyGenerateStrategy: column: account_id keyGeneratorName: snowflake taccountdetail: actualDataNodes: db.taccountdetail_${0..1} tableStrategy: standard: shardingColumn: order_id shardingAlgorithmName: accountdetailtable_inline bindingTables: taccount, taccount_detail shardingAlgorithms: accounttableinline: type: INLINE props: algorithm-expression: taccount${account_id % 2} accountdetailtable_inline: type: INLINE props: algorithm-expression: taccountdetail${accountid % 2} keyGenerators: snowflake: type: SNOWFLAKE ``` Assert data are in the xml under test type in `test\resources`. In the xml file, `yaml-rule` means the environment configuration file path, `input` contains the target SQL and parameters, `output` contains the expected SQL and parameters. The `db-type` described the type for SQL parse, default is `SQL92`. For example: ```xml <rewrite-assertions yaml-rule="yaml/sharding/sharding-rule.yaml"> <!-- to change SQL parse type, change db-type --> <rewrite-assertion id="createindexfor_mysql" db-type="MySQL"> <input sql="CREATE INDEX indexname ON taccount ('status')" /> <output sql="CREATE INDEX indexname ON taccount_0 ('status')" /> <output sql="CREATE INDEX indexname ON taccount_1 ('status')" /> </rewrite-assertion> </rewrite-assertions> ``` After set up the assert data and environment configuration, rewrite test engine will assert the corresponding SQL without any Java code modification.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.CommandCompleteEvent.md

/ / CommandCompleteEvent .CommandCompleteEvent | Name | Type | | : | :-- | | `R` | extends = | | `T` | extends `ResponseType` = `ResponseType` | argvNoOptions: `string`[] cancelled: `boolean` command: `string` completeTime: `number` echo: `boolean` evaluatorOptions: execOptions: execType: execUUID: `string` historyIdx: `number` parsedOptions: pipeStages: `Object` | Name | Type | | : | :-- | | `prefix?` | `string` | | `redirect?` | `string` | | `redirector?` | `">"` \| `">>"` \| `"2>&1"` \| `">&"` \| `">>&"` | | `stages` | `string` | response: `R` responseType: `T` tab:
Project: kpt (Provisioning / Automation & Configuration)
File: 03-function-results.md

In kpt, the counterpart to Unix philsophophy of "everything is a file" is "everything is a Kubernetes resource". This also extends to the results of executing functions using `eval` or `render`. In addition to providing a human-readable terminal output, these commands provide structured results which can be consumed by other tools. This enables you to build robust UI layers on top of kpt. For example: Create a custom dashboard that shows the results returned by functions Annotate a GitHub Pull Request with results returned by a validator function at the granularity of individuals fields In both `render` and `eval`, structured results can be enabled using the `--results-dir` flag. For example: ```shell $ kpt fn render wordpress --results-dir /tmp Package "wordpress/mysql": [PASS] "gcr.io/kpt-fn/set-labels:v0.1" Package "wordpress": [PASS] "gcr.io/kpt-fn/set-labels:v0.1" [PASS] "gcr.io/kpt-fn/kubeval:v0.1" Successfully executed 3 function(s) in 2 package(s). For complete results, see /tmp/results.yaml ``` The results are provided as resource of kind `FunctionResultList`: ```yaml apiVersion: kpt.dev/v1 kind: FunctionResultList metadata: name: fnresults exitCode: 0 items: image: gcr.io/kpt-fn/set-labels:v0.1 exitCode: 0 image: gcr.io/kpt-fn/set-labels:v0.1 exitCode: 0 image: gcr.io/kpt-fn/kubeval:v0.1 exitCode: 0 ``` Let's see a more interesting result where the `kubeval` function catches a validation issue. For example, change the value of `port` field in `service.yaml` from `80` to `"80"` and rerun: ```shell $ kpt fn render wordpress --results-dir /tmp Package "wordpress/mysql": [PASS] "gcr.io/kpt-fn/set-labels:v0.1" Package "wordpress": [PASS] "gcr.io/kpt-fn/set-labels:v0.1" [FAIL] "gcr.io/kpt-fn/kubeval:v0.1" Results: [ERROR] Invalid type. Expected: integer, given: string in object "v1/Service/wordpress" in file "service.yaml" in field "spec.ports.0.port" Exit code: 1 For complete results, see /tmp/results.yaml ``` The results resource will now contain failure details: ```yaml apiVersion: kpt.dev/v1 kind: FunctionResultList metadata: name: fnresults exitCode: 1 items: image: gcr.io/kpt-fn/set-labels:v0.1 exitCode: 0 image: gcr.io/kpt-fn/set-labels:v0.1 exitCode: 0 image: gcr.io/kpt-fn/kubeval:v0.1 exitCode: 1 results: message: "Invalid type. Expected: integer, given: string" severity: error resourceRef: apiVersion: v1 kind: Service name: wordpress field: path: spec.ports.0.port file: path: service.yaml ```
Project: ArangoDB (App Definition and Development / Database)
File: try_greedy.md

+++ title = "TRY is greedy" description = "" weight = 40 tags = ["try"] +++ {{< api "BOOSTOUTCOMETRYV(expr)/BOOSTOUTCOMETRY(expr)" >}} has 'greedier' implicit conversion semantics than {{< api "basic_result<T, E, NoValuePolicy>" >}}. For example, this code won't compile: ```c++ outcome::result<int, std::error_code> test(outcome::result<int, std::errc> r) { return r; // you need to use explicit construction here // i.e. return outcome::result<int>(r); } ``` This is chosen because there is a non-trivial conversion between `std::errc` and `std::error_code`, so even though that conversion is implicit for `std::error_code`, Outcome does not expose the implicitness here in order to keep the implicit constructor count low (implicit constructors add significantly to build times). The `TRY` operation is more greedy though: ```c++ outcome::result<int, std::error_code> test(outcome::result<int, std::errc> r) { BOOSTOUTCOMETRY(r); // no explicit conversion needed return r.value(); } ``` This is because `result<int, std::error_code>` will implicitly construct from anything which either `int` or `std::error_code` will implicitly construct from. However, `result<int, std::error_code>` will not implicitly construct from `result<int, std::errc>`. Thus bear this in mind during usage: `TRY` is greedier for implicit conversions than the Outcome types themselves.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.129.md

layout: release date: 2023-08-19 tag: v0.6.129 MeshKit v0.6.59 @leecalcote (#8541) Enhance policies endpoints @Freedisch (#8491) fix: fixed background color in meshmodel relationships tab @Yana-Gupta (#8549) fix validation and deployment issue for comps marked isAnnotaion true @MUzairS15 (#8520) Bump gorm.io/gorm from 1.25.2 to 1.25.3 @dependabot (#8536) [Docs] Remove unncessary file - `Kuma.svg` @abhinandanudupa (#8522) Adding Customization of MeshMap Snapshot in docs @yash37158 (#8452) Thank you to our contributors for making this release possible: @Freedisch, @MUzairS15, @Yana-Gupta, @abhinandanudupa, @dependabot, @dependabot[bot], @l5io, @leecalcote, @theBeginner86 and @yash37158