cwielenb/CNCF-Dataset huggingface dataset:
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: 2023-06-14-jet-engine-in-hazelcast.md

title: Jet engine lives on in Hazelcast 5.x description: Hazelcast Jet as standalone product reached end-of-life on April 21, 2023. author: Frantiek Hartman authorURL: https://www.linkedin.com/in/frantisek-hartman/ authorImageURL: https://i.stack.imgur.com/3X7wE.png At Hazelcast we have a policy of supporting a minor version for two years since the initial release. For Hazelcast Jet 4.5 this period expired at the end of April, marking an end of Hazelcast Jet as a standalone product. Since 2021 our Jet engine, a stream processing system that can do stateful computations over massive amounts of data with consistent low latency, has been part of Hazelcast Platform 5.x. We encourage every Hazelcast Jet user still using any of the Jet 4.x versions to upgrade to Hazelcast 5.x. There are some minor incompatibilities in how a Hazelcast instance is started, but e.g. the Pipeline API is fully backward compatible. See the for details. Furthermore, here are a few more useful links: documentation for latest Hazelcast. GitHub repository where you can report issues or contribute. the right place to interact with other members of Hazelcast community and Hazelcast developers. if you have a question regarding use of Hazelcast or the Jet engine, this is the place to ask. another place where you can ask questions. our website with information about our products and services.
Project: YugabyteDB (App Definition and Development / Database)
File: extension-hypopg.md

title: HypoPG extension headerTitle: HypoPG extension linkTitle: HypoPG description: Using the HypoPG extension in YugabyteDB menu: v2.18: identifier: extension-hypopg parent: pg-extensions weight: 20 type: docs The PostgreSQL extension adds support for hypothetical indexes. Use hypothetical indexes to test whether adding an index improves the performance of problematic queries, without expending resources to create them. To enable the extension: ```sql CREATE EXTENSION hypopg; ``` Create a table as follows: ```sql CREATE TABLE upanddown (up int primary key, down int); INSERT INTO upanddown SELECT a AS up, 10001-a AS down FROM generate_series(1,10000) a; ``` The `upanddown` table has no indexes, but is defined with a primary key. As a result, when using the primary key, records are retrieved directly: ```sql EXPLAIN SELECT * FROM upanddown WHERE up = 999; ``` ```output QUERY PLAN Index Scan using upanddownpkey on upand_down (cost=0.00..4.11 rows=1 width=8) Index Cond: (up = 999) ``` However, because it doesn't have an index, fetching a value from the `down` column results in a sequential scan: ```sql EXPLAIN SELECT * FROM upanddown WHERE down = 999; ``` ```output QUERY PLAN Seq Scan on upanddown (cost=0.00..102.50 rows=1000 width=8) Filter: (down = 999) ``` To see what would happen if you were to create an index for the `down` column without actually creating the index, use HypoPG as follows: ```sql SELECT * FROM hypopgcreateindex('create index on upanddown(down)'); ``` ```output indexrelid | indexname +-- 13283 | <13283>lsmupanddowndown ``` Explain now shows that the planner would use the index: ```sql EXPLAIN SELECT * FROM upanddown WHERE down = 999; ``` ```output QUERY PLAN -- Index Scan using <13283>lsmupanddowndown on upanddown (cost=0.00..4.01 rows=1000 width=8) Index Cond: (down = 999) ``` As the index is not really created, if you use `EXPLAIN ANALYZE`, the hypothetical index is ignored: ```sql EXPLAIN ANALYZE SELECT * FROM upanddown WHERE down = 999; ``` ```output QUERY PLAN Seq Scan on upanddown (cost=0.00..102.50 rows=1000 width=8) (actual time=35.678..35.687 rows=1 loops=1) Filter: (down = 999) Rows Removed by Filter: 9999 Planning Time: 0.041 ms Execution Time: 35.735 ms Peak Memory Usage: 0 kB ``` You can query the hypothetical indexes you created using the `hypopg()` function: ```sql SELECT * FROM hypopg(); ``` ```output indexname | indexrelid | indrelid | innatts | indisunique | indkey | indcollation | indclass | indoption | indexprs | indpred | amid --++-++-+--+--+-+--+-++ <13283>lsmupanddowndown | 13283 | 16927 | 1 | f | 2 | 0 | 9942 | | | | 9900 ``` If you create multiple hypothetical indexes, you can drop a single hypothetical index using its `indexrelid` as follows: ```sql SELECT * FROM hypopgdropindex(13283); ``` ```output hypopgdropindex t ``` To remove all hypothetical indexes, log out or quit your session. ```sql \q ``` For more information, refer to the .
Project: Harbor (Provisioning / Container Registry)
File: 10-09-User-can-pull-scaned-images.md

10-09 ======= To test normal user can pull scanned images. User guide. This test requires that one Harbor instance is running and available. Harbor is installed with trivy enable. A Linux host with Docker client installed. Trivy has been updated to the latest. Vulnerability severity limit is disabled. Note: In below test, user A is a non-admin user. User A should be replaced by meaningful names. Login as user A. Create a project and push an image. Login as admin and scan the image. On a Docker client, user A pull the scanned image. Step 4 user can pull the image. None
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: bug_report.md

name: Bug report about: Create a report to help us improve labels: "bug" Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: .... .... .... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Environment (please complete the following information): Kubernetes: [e.g. v1.18.6] Numaflow: [e.g. v0.5.1] Additional context Add any other context about the problem here. <!-- Issue Author: Don't delete this message to encourage other users to support your issue! --> Message from the maintainers: Impacted by this bug? Give it a . We often sort issues this way to know what to prioritize. For quick help and support, join our channel.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_access_context_manager_access_policy.md

+++ title = "googleaccesscontextmanageraccess_policy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleaccesscontextmanageraccess_policy" identifier = "inspec/resources/gcp/googleaccesscontextmanageraccesspolicy.md googleaccesscontextmanageraccesspolicy resource" parent = "inspec/resources/gcp" +++ A `googleaccesscontextmanageraccess_policy` is used to test a Google AccessPolicy resource ```ruby describe.one do googleaccesscontextmanageraccesspolicies(orgid: '190694428152').names.each do |policy_name| describe googleaccesscontextmanageraccesspolicy(name: policyname) do it { should exist } its('title') { should cmp 'policytitle' } its('parent') { should match '190694428152' } end end end ``` Properties that can be accessed from the `googleaccesscontextmanageraccess_policy` resource: `name` : Resource name of the AccessPolicy. Format: accessPolicies/{policy_id} `create_time` : Time the AccessPolicy was created in UTC. `update_time` : Time the AccessPolicy was updated in UTC. `parent` : The parent of this AccessPolicy in the Cloud Resource Hierarchy. Format: organizations/{organization_id} `title` : Human readable title. Does not affect behavior.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-container-cleanup.1.md

% podman-container-cleanup 1 podman\-container\-cleanup - Clean up the container's network and mountpoints podman container cleanup [options] container [container ...] podman container cleanup cleans up exited containers by removing all mountpoints and network configurations from the host. The container name or ID can be used. The cleanup command does not remove the containers. Running containers are not cleaned up.\ Sometimes container mount points and network stacks can remain if the podman command was killed or the container ran in daemon mode. This command is automatically executed when containers are run in daemon mode by the `conmon process` when the container exits. Clean up all containers.\ The default is false.\ IMPORTANT: This OPTION does not need a container name or ID as input argument. Clean up an exec session for a single container. It can only be specified if a single container is being cleaned up (conflicts with --all as such). If --rm is not specified, temporary files for the exec session are cleaned up; if it is, the exec session is removed from the container.\ IMPORTANT: Conflicts with --rmi as the container is not being cleaned up so the image cannot be removed. Instead of providing the container ID or name, use the last created container. The default is false. IMPORTANT: This OPTION is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines. This OPTION does not need a container name or ID as input argument. After cleanup, remove the container entirely.\ The default is false. After cleanup, remove the image entirely.\ The default is false. Clean up the container "mywebserver". ``` $ podman container cleanup mywebserver ``` Clean up the containers with the names "mywebserver", "myflaskserver", "860a4b23". ``` $ podman container cleanup mywebserver myflaskserver 860a4b23 ``` , , Jun 2018, Originally compiled by Dan Walsh <dwalsh@redhat.com>
Project: ClickHouse (App Definition and Development / Database)
File: v20.12.8.5-stable.md

Backported in : Fixed inconsistent behavior of dictionary in case of queries where we look for absent keys in dictionary. (). Backported in : Fix usage of `-Distinct` combinator with `-State` combinator in aggregate functions. (). Backported in : Fixed behaviour, when `ALTER MODIFY COLUMN` created mutation, that will knowingly fail. (). Backported in : - Block parallel insertions into storage join. (). Backported in : Fixes . Fixed bug that could cause duplicates with insert query (if one of the callbacks came a little too late). ().
Project: Athenz (Provisioning / Key Management)
File: local_ui_development.md

In this guide, you will be able to start a local ZMS server and do local ui development from your favorite IDE. Docker, Make toolchain, Node v14.x, nodemon v2.x Checkout Athenz from GitHub ```shell git clone https://github.com/AthenZ/athenz ``` `cd` into the docker directory ```shell cd docker ``` Run following command to download ZMS & ZMS DB docker images, and set it up with meaningful defaults for local development: ```shell make prepare-ui-dev-env ``` !!! Note If you are using macOS, then the script prints out a command at the end, which you can execute to add the generated self-signed certificate to your login keychain so that you can access Athenz UI in the browser without certificate warning. If you don't want to do that, please follow appropriate instructions for your workstation and / or browser so that you can access Athenz UI in the browser. Now `cd` into the ui directory & run `npm install` to download UI dependencies ```shell cd ../ui npm install ``` Once dependencies are downloaded, start the UI server using following ```shell sudo nodemon -r dotenv/config app.js ``` !!! Note `sudo` is required because UI is using privileged port 443. If you don't have nodemon installed, you can install it using ```shell npm install nodemon -g ``` Access the UI at https://localhost. For your convenience, local set up uses a TestUserAuthority which accepts any username and password as far as it's a same string. To look at a pre-created "athenz" domain during start up, login with "athenz-admin" as username and password. Now you can keep the UI instance running in the terminal, make changes to the code using your IDE and UI dev server will reload with your changes. It is possible for build to fail if Athenz was previously built. To clean old artifacts run: `./stop-local-athenz.sh` When you open https://localhost you might get a certificate error as the self-signed certificate isn't trusted. To fix it, please follow the steps in
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_completion_powershell.md

Generate the autocompletion script for powershell Generate the autocompletion script for powershell. To load completions in your current shell session: veinmind-runner completion powershell | Out-String | Invoke-Expression To load completions for every new session, add the output of the above command to your powershell profile. ``` veinmind-runner completion powershell [flags] ``` ``` -h, --help help for powershell --no-descriptions disable completion descriptions ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` - Generate the autocompletion script for the specified shell
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: go-md2man.1.md

go-md2man 1 "January 2015" go-md2man "User Manual" ================================================== go-md2man - Convert markdown files into manpages go-md2man [-in=/path/to/md/file] [-out=/path/to/output] go-md2man converts standard markdown formatted documents into manpages. It is written purely in Go so as to reduce dependencies on 3rd party libs. By default, the input is stdin and the output is stdout. Convert the markdown file go-md2man.1.md into a manpage: ``` go-md2man < go-md2man.1.md > go-md2man.1 ``` Same, but using command line arguments instead of shell redirection: ``` go-md2man -in=go-md2man.1.md -out=go-md2man.1 ``` January 2015, Originally compiled by Brian Goff (cpuguy83@gmail.com).
Project: YDB (App Definition and Development / Database)
File: column_order.md

The standard SQL is sensitive to the order of columns in projections (that is, in `SELECT`). While the order of columns must be preserved in the query results or when writing data to a new table, some SQL constructs use this order. This applies, for example, to and positional (ORDER BY ordinal). The column order is ignored in YQL by default: The order of columns in the output tables and query results is undefined The data scheme of the `UNION ALL` result is output by column names rather than positions If you enable `PRAGMA OrderedColumns;`, the order of columns is preserved in the query results and is derived from the order of columns in the input tables using the following rules: `SELECT`: an explicit column enumeration dictates the result order. `SELECT` with an asterisk (`SELECT FROM ...`) inherits the order from its input. {% if feature_join %}* The order of columns after : First output the left-hand columns, then the right-hand ones. If the column order in any of the sides in the `JOIN` output is undefined, the column order in the result is also undefined.{% endif %} The order in `UNION ALL` depends on the execution mode. The column order for is undefined. {% note warning %} In the YT table schema, key columns always precede non-key columns. The order of key columns is determined by the order of the composite key. When `PRAGMA OrderedColumns;` is enabled, non-key columns preserve their output order. {% endnote %}
Project: StarRocks (App Definition and Development / Database)
File: map_size.md

displayed_sidebar: "English" Returns the number of elements in a MAP value. MAP is an unordered collection of key-value pairs, for example, `{"a":1, "b":2}`. One key-value pair constitutes one element, for example, `{"a":1, "b":2}` contains two elements. This function has an alias . It is supported from v2.5. ```Haskell INT mapsize(anymap) ``` `any_map`: the MAP value from which you want to retrieve the number of elements. Returns a value of the INT type. If the input is NULL, NULL is returned. If a key or value in the MAP value is NULL, NULL is processed as a normal value. From v3.1 onwards, StarRocks supports defining MAP columns when you create a table. This example uses table `test_map`, which contains the following data: ```Plain CREATE TABLE test_map( col_int INT, col_map MAP<VARCHAR(50),INT> ) DUPLICATE KEY(col_int); INSERT INTO test_map VALUES (1,map{"a":1,"b":2}), (2,map{"c":3}), (3,map{"d":4,"e":5}); SELECT * FROM testmap ORDER BY colint; +++ | colint | colmap | +++ | 1 | {"a":1,"b":2} | | 2 | {"c":3} | | 3 | {"d":4,"e":5} | +++ 3 rows in set (0.05 sec) ``` Obtain the number of elements in each row of the `col_map` column. ```Plaintext select mapsize(colmap) from testmap order by colint; +-+ | mapsize(colmap) | +-+ | 2 | | 1 | | 2 | +-+ 3 rows in set (0.05 sec) ``` This example uses Hive table `hive_map`, which contains the following data: ```Plaintext SELECT * FROM hivemap ORDER BY colint; +++ | colint | colmap | +++ | 1 | {"a":1,"b":2} | | 2 | {"c":3} | | 3 | {"d":4,"e":5} | +++ ``` After a is created in your cluster, you can use this catalog and the mapsize() function to obtain the number of elements in each row of the `colmap` column. ```Plaintext select mapsize(colmap) from hivemap order by colint; +-+ | mapsize(colmap) | +-+ | 2 | | 1 | | 2 | +-+ 3 rows in set (0.05 sec) ```
Project: ArangoDB (App Definition and Development / Database)
File: hook_outcome_copy_construction.md

+++ title = "`void hookoutcomecopy_construction(T *, U &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the converting copy constructors of `basic_outcome`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onoutcomecopy_construction(T *, U &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the converting copy constructors of `basicoutcome` (NOT the standard copy constructor). See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_outcome.hpp>`
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: well-known-statuses.md

id: well-known-statuses title: Well-known Status fields of Catalog Entities sidebar_label: Well-known Statuses description: Lists a number of well known entity statuses, that have defined semantics. They can be attached to catalog entities and consumed by plugins as needed. This section lists well known , that have defined semantics. They can be attached to catalog entities and consumed by plugins as needed. If you are looking to extend the statuses, see . The `status` object of an entity is currently left unrestricted, except for the `items` field. Its structure is defined in the section. We reserve the right to extend this model in the future. This status is in active development and its format will change unexpectedly. Do not consume it in your own code until such a time that this documentation has been updated. This is a (non-exhaustive) list of `status.items.[].type` values that are known to be in active use. Expresses an aspect of the current status of the catalog's ingestion of this entity. Errors that may appear here include inability to read from the remote SCM provider, syntax errors in the YAML file, and similar. Note that the entity data itself may be of an older version, when errors are present. The ingestion system keeps the old valid entity data untouched when possible, so the errors described in this state may not seem to align with the rest of the entity, because they pertain to a remote that could not be successfully ingested. This is normal. ```yaml status: items: type: backstage.io/catalog-processing level: error message: 'NotFoundError: File not found' error: name: NotFoundError message: File not found stack: ... ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.SaveError.md

/ / SaveError .SaveError `Error` `SaveError` message: `string` Error.message node_modules/typescript/lib/lib.es5.d.ts:1023 name: `string` Error.name node_modules/typescript/lib/lib.es5.d.ts:1022 `Optional` revealLine: `number` `Optional` stack: `string` Error.stack node_modules/typescript/lib/lib.es5.d.ts:1024
Project: StarRocks (App Definition and Development / Database)
File: schemata.md

displayed_sidebar: "English" `schemata` provides information about databases. The following fields are provided in `schemata`: | Field | Description | | -- | | | CATALOG_NAME | The name of the catalog to which the schema belongs. This value is always `NULL`. | | SCHEMA_NAME | The name of the schema. | | DEFAULTCHARACTERSET_NAME | The schema default character set. | | DEFAULTCOLLATIONNAME | The schema default collation. | | SQL_PATH | This value is always `NULL`. |
Project: KICS (Provisioning / Security & Compliance)
File: 562952e4-0348-4dea-9826-44f3a2c6117b.md

title: Zypper Install Without Version hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 562952e4-0348-4dea-9826-44f3a2c6117b Query name: Zypper Install Without Version Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Supply-Chain URL: Not specifying the package version can cause failures due to unanticipated changes in required packages<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2 3" FROM opensuse/leap:15.2 RUN zypper install -y httpd && zypper clean RUN ["zypper", "install", "http"] HEALTHCHECK CMD curl --fail http://localhost:3000 || exit 1 ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM opensuse/leap:15.2 RUN zypper install -y httpd=2.4.46 && zypper clean HEALTHCHECK CMD curl --fail http://localhost:3000 || exit 1 ```
Project: KICS (Provisioning / Security & Compliance)
File: b9380fd3-5ffe-4d10-9290-13e18e71eee1.md

title: Insecure Bind Address Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b9380fd3-5ffe-4d10-9290-13e18e71eee1 Query name: Insecure Bind Address Set Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: When using kube-apiserver command, the '--insecure-bind-address' flag should not be set<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver", "--insecure-bind-address=127.0.0.1"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--insecure-bind-address=127.0.0.1"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: [] restartPolicy: OnFailure ```
Project: YDB (App Definition and Development / Database)
File: select_full_join_output.md

``` name | lastname | socialcardnumber +-+-- Liam | Martinez | 1323456789 Eve | Martin | 623456789 Hank | Miller | 923456789 Molly | Robinson | 1423456789 Sam | Walker | Paul | Harris | 1723456789 Kara | Thompson | 1223456789 | | 1923456789 ... ```