cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_tpcc_run.md

title: kbcli bench tpcc run Run workload. ``` kbcli bench tpcc run [flags] ``` ``` -h, --help help for run --max-measure-latency duration max measure latency in milliseconds (default 16s) --wait including keying & thinking time described on TPC-C Standard Specification --weight ints Weight for NewOrder, Payment, OrderStatus, Delivery, StockLevel (default [45,43,4,4,4]) ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --check-all Run all consistency checks --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 --count int Total execution count, 0 means infinite -D, --db string Database name (default "kb_test") --disable-compression If true, opt-out of response compression for all requests to the server -d, --driver string Database driver: mysql (default "mysql") --dropdata Cleanup data before prepare -H, --host string Database host (default "127.0.0.1") --ignore-error Ignore error when running workload --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --interval duration Output interval time (default 5s) --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version --max-procs int runtime.GOMAXPROCS -n, --namespace string If present, the namespace scope for this CLI request --partition-type int Partition type (1 - HASH, 2 - RANGE, 3 - LIST (like HASH), 4 - LIST (like RANGE) (default 1) --parts int Number to partition warehouses (default 1) -p, --password string Database password (default "sakila") -P, --port int Database port (default 3306) --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 --silence Don't print error when running workload -T, --threads int Thread concurrency (default 1) --time duration Total execution time (default 2562047h47m16.854775807s) --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 -U, --user string Database user (default "root") --warehouses int Number of warehouses (default 4) ``` - Run a TPCC benchmark.
Project: Harbor (Provisioning / Container Registry)
File: Configure_mirror.md

Harbor runs as a local registry by default. It can also be configured as a registry mirror, which caches downloaded images for subsequent use. Note that under this setup, the Harbor registry only acts as a mirror server and no longer accepts image pushing requests. Edit `Deploy/templates/registry/config.yml` before executing `./prepare`, and append a `proxy` section as follows: ``` proxy: remoteurl: https://registry-1.docker.io ``` In order to access private images on the Docker Hub, a username and a password can be supplied: ``` proxy: remoteurl: https://registry-1.docker.io username: [username] password: [password] ``` You will need to pass the `--registry-mirror` option to your Docker daemon on startup: ``` docker --registry-mirror=https://<my-docker-mirror-host> daemon ``` For example, if your mirror is serving on `http://reg.yourdomain.com`, you would run: ``` docker --registry-mirror=https://reg.yourdomain.com daemon ``` Refer to the for detailed information.
Project: Meshery (Provisioning / Automation & Configuration)
File: strimzi-kafka-operator.md

layout: integration title: Strimzi Kafka Operator subtitle: Collaborative and visual infrastructure as code for Strimzi Kafka Operator image: /assets/img/integrations/strimzi-kafka-operator/icons/color/strimzi-kafka-operator-color.svg permalink: extensibility/integrations/strimzi-kafka-operator docURL: https://docs.meshery.io/extensibility/integrations/strimzi-kafka-operator description: integrations-category: App Definition and Development integrations-subcategory: Streaming & Messaging registrant: Artifact Hub components: 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: Tetragon (Provisioning / Security & Compliance)
File: install-docker.md

title: "Quick Local Docker Install" weight: 2 description: "Discover and experiment with Tetragon on your local Linux host" aliases: ["/docs/tutorials/try-tetragon-linux"] {{< note >}} This guide has been tested on Ubuntu 22.04 and 22.10 with respectively kernel `5.15.0` and `5.19.0` on amd64 and arm64 but shipping with a relatively recent kernel should work. See the FAQ for further details on the . Note that you cannot run Tetragon using Docker Desktop on macOS because of a limitation of the Docker Desktop Linux virtual machine. Learn more about this issue and how to run Tetragon on a Mac computer in . {{< /note >}} The easiest way to start experimenting with Tetragon is to run it via Docker using the released container images. ```shell docker run --name tetragon-container --rm --pull always \ --pid=host --cgroupns=host --privileged \ -v /sys/kernel/btf/vmlinux:/var/lib/tetragon/btf \ quay.io/cilium/tetragon-ci:latest ``` This will start Tetragon in a privileged container. Priviliges are required to load and attach BPF programs. See Installation section for more details. Check for .
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_s3_describe.md

Describe a S3 YugabyteDB Anywhere storage configuration Describe a S3 storage configuration in YugabyteDB Anywhere ``` yba storage-config s3 describe [flags] ``` ``` -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -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 a YugabyteDB Anywhere S3 storage configuration
Project: Paralus (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug Report about: Report a bug or unexpected behavior title: "" labels: "bug, needs-triage" assignees: "" You can check your version by running `helm ls|grep '^<deployment-name>'` or using , `pctl version`, and provide the output. <!-- Please make sure you have have filled out all sections of the template --> [ ] I've described the bug, included steps to reproduce it, and included my environment setup with all customizations. [ ] I'm using the latest version of the project.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_playground_destroy.md

title: kbcli playground destroy Destroy the playground KubeBlocks and kubernetes cluster. ``` kbcli playground destroy [flags] ``` ``` kbcli playground destroy ``` ``` --auto-approve Skip interactive approval before destroying the playground -h, --help help for destroy --purge Purge all resources before destroying kubernetes cluster, delete all clusters created by KubeBlocks and uninstall KubeBlocks. (default true) --timeout duration Time to wait for destroying KubeBlocks, such as --timeout=10m (default 5m0s) ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Bootstrap or destroy a playground KubeBlocks in local host or cloud.
Project: StarRocks (App Definition and Development / Database)
File: url_extract_host.md

displayed_sidebar: "English" Extracts the host section from a URL. This function is supported from v3.3 onwards. ```haskell VARCHAR urlextracthost(VARCHAR str) ``` `str`: the string to extract its host string. If `str` is not a string, this function will try implicit cast first. Returns the host string. ```plaintext mysql> select urlextracthost('httpa://starrocks.com/test/api/v1'); +-+ | urlextracthost('httpa://starrocks.com/test/api/v1') | +-+ | starrocks.com | +-+ ```
Project: Harbor (Provisioning / Container Registry)
File: pull_request_template.md

Thank you for contributing to Harbor! Fixes #(issue) Please indicate you've done the following: [ ] Well Written Title and Summary of the PR [ ] Label the PR as needed. "release-note/ignore-for-release, release-note/new-feature, release-note/update, release-note/enhancement, release-note/community, release-note/breaking-change, release-note/docs, release-note/infra, release-note/deprecation" [ ] Accepted the DCO. Commits without the DCO will delay acceptance. [ ] Made sure tests are passing and test coverage is added if needed. .
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: setup-project.md

!!! Note We are working hard on getting our CLI and GraphQL API set up to allow everyone using Lagoon to set up and configure their projects themselves. Right now, it needs more testing before we can release those features, so hold tight! Until then, the setup of a new project involves talking to your Lagoon administrator, which is ok, as they are much friendlier than APIs. Please have the following information ready for your Lagoon administrator: A name you would like the project to be known by This name can only contain lowercase characters, numbers and dashes Double dashes (`--`) are not allowed within a project name SSH public keys, email addresses and the names of everybody that will work on this project. Here are instructions for generating and copying SSH keys for , , and . The URL of the Git repository where your code is hosted \(`git@example.com:test/test.git`\). The name of the Git branch you would like to use for your production environment \(see for details about the environments\). Which branches and pull requests you would like to deploy to your additional environments. With Lagoon, you can filter branches and pull requests by name with regular expressions, and your Lagoon administrator can get this set up for you. We suggest deploying specific important branches \(like `develop` and `main`\) and pull requests. But that's all up to you! \(see for some more information\) This means that the `.lagoon.yml` and `docker-compose.yml` files are available in your Git repository and configured accordingly. If this is not the case, check out the list of on how to do so before proceeding. In order to deploy your code, Lagoon needs access to it. By design and for security, Lagoon only needs read access to your Git repository. Your Lagoon administrator will tell you the SSH public key or the Git account to give read access to. Lagoon needs to be informed about a couple of events that are happening to your Git repository. Currently these are pushes and pull requests, but we may add more in the future. As Lagoon supports many different Git hosts, we have split off those instructions into this documentation: . Congratulations, you are now ready to run your .
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_bundle.md

title: "operator-sdk bundle" Manage operator bundle metadata Manage bundle builds, bundle metadata generation, and bundle validation. An operator bundle is a portable operator packaging format understood by Kubernetes native software, like the Operator Lifecycle Manager. More information about operator bundles and metadata: https://github.com/operator-framework/operator-registry/blob/master/docs/design/operator-bundle.md More information about the integration with OLM via SDK: https://sdk.operatorframework.io/docs/olm-integration ``` -h, --help help for bundle ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - - Validate an operator bundle
Project: ArangoDB (App Definition and Development / Database)
File: swap.md

+++ title = "`void swap(basic_result &)`" description = "Swap one basic_result with another, with the strong guarantee. Noexcept propagating." categories = ["modifiers"] weight = 900 +++ Swap one basicresult with another, with the strong guarantee. Constexpr if move constructors and move assignments of `valuetype` and `error_type` are noexcept. Requires: Always available. Complexity: If the move constructor and move assignment for `valuetype` and `errortype` are noexcept, the complexity is the same as for the `swap()` implementations of the `valuetype` and `errortype`. Otherwise, complexity is not preserved, as {{% api "strongswap(bool &allgood, T &a, T &b)" %}} is used instead of `swap()`. This function defaults to using one move construction and two assignments, and it will attempt extra move assignments in order to restore the state upon entry if a failure occurs. Guarantees: If an exception is thrown during the swap operation, the state of both operands on entry is attempted to be restored, in order to implement the strong guarantee. If that too fails, the flag bits are forced to something consistent such that there can be no simultaneously valued and errored state, or valueless and errorless. The flag {{% api "haslostconsistency()" %}} becomes true for both operands, which are now likely in an inconsistent state.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc.5v.md

layout: release date: 2022-06-10 tag: v0.6.0-rc.5v language: en [dde] UI Change to adapt to the exposed server version @sudo-NithishKarthik (#5596) fix: Service mesh provisioning @sudo-NithishKarthik (#5595) exposed meshery server version in dde @warunicorn19 (#5591) Fix panic @Revolyssup (#5593) Fix NATS connectivity test @MUzairS15 (#5583) Multi context refactor @Revolyssup (#5528) Ci/marioarriaga92/5592 fix cypress v10 legacy config file error @MarioArriaga92 (#5597) [UI] Pattern file bug fixes @Chadha93 (#5587) [UI] Settings button style fix for lifecycle @Chadha93 (#5588) material-ui/core from 4.12.3 to 4.12.4 @Harshit-Dandriyal (#5585) [UI] Pattern file bug fixes @Chadha93 (#5587) Bump google.golang.org/grpc from 1.46.0 to 1.47.0 @dependabot (#5560) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @MUzairS15, @MarioArriaga92, @Revolyssup, @dependabot, @l5io, @leecalcote, @sudo-NithishKarthik, @warunicorn19 and Nithish
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.DirectReplEval.md

/ / DirectReplEval .DirectReplEval Directly apply the given evaluator to the given arguments. This is the default evaluator implementation. new DirectReplEval() name: `string` = `'DirectReplEval'` . apply<`T`, `O`\>(`commandUntrimmed`, `execOptions`, `evaluator`, `args`): `T` \| `Promise`<`T`\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `commandUntrimmed` | `string` | | `execOptions` | | | `evaluator` | <`T`, `O`\> | | `args` | <`O`\> | `T` \| `Promise`<`T`\> .
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: LICENSE.md

The MIT License (MIT) Copyright (c) 2013-19 by Carlos Cobo and contributors. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: ClickHouse (App Definition and Development / Database)
File: v23.1.7.30-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fixed `UNKNOWN_TABLE` exception when attaching to a materialized view that has dependent tables that are not available. This might be useful when trying to restore state from a backup. (). Backported in : Update time zones. The following were updated: Africa/Cairo, Africa/Casablanca, Africa/ElAaiun, America/Bogota, America/CambridgeBay, America/CiudadJuarez, America/Godthab, America/Inuvik, America/Iqaluit, America/Nuuk, America/Ojinaga, America/Pangnirtung, America/RankinInlet, America/Resolute, America/Whitehorse, America/Yellowknife, Asia/Gaza, Asia/Hebron, Asia/Kuala_Lumpur, Asia/Singapore, Canada/Yukon, Egypt, Europe/Kirov, Europe/Volgograd, Singapore. (). Backported in : After the recent update, the `dockerd` requires `--tlsverify=false` together with the http port explicitly. (). Fix race in grace hash join with limit (). Fix explain graph with projection (). Fix crash in polygonsSymDifferenceCartesian (). Remove a feature (). ClickHouse startup error when loading a distributed table that depends on a dictionary (). Fix possible segfault in cache (). Fix nested map for keys of IP and UUID types (). Fix bug in Keeper when a node is not created with scheme `auth` in ACL sometimes. (). Fix IPv4 comparable with UInt ().
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: testliteral.md

The `TestLiteral` rule specifies an extractor microformat block. An extractor takes the general form: ```ebnf Ident '|' MicroFormat '|' ``` Where The `ident` is the name of a builtin extractor such as `json` or `base64`. The `Microformat` content depends on the extractor being used
Project: StarRocks (App Definition and Development / Database)
File: next_day.md

displayed_sidebar: "English" Returns the date of the first specified day of week (DOW) that occurs after the input date (DATE or DATETIME). For example, `next_day('2023-04-06', 'Monday')` returns the date of the next Monday that occurred after '2023-04-06'. This function is supported from v3.1. It is the opposite of . ```SQL DATE nextday(DATETIME|DATE dateexpr, VARCHAR dow) ``` `date_expr`: the input date. It must be a valid DATE or DATETIME expression. `dow`: the day of week. Valid values include a number of abbreviations which are case-sensitive: | DOWFULL | DOW2 | DOW_3 | | | -- |:--:| | Sunday | Su | Sun | | Monday | Mo | Mon | | Tuesday | Tu | Tue | | Wednesday | We | Wed | | Thursday | Th | Thu | | Friday | Fr | Fri | | Saturday | Sa | Sat | Returns a DATE value. Any invalid `dow` will cause an error. `dow` is case-sensitive. Returns NULL if an invalid date or a NULL argument is passed in. ```Plain -- Return the date of the next Monday that occurred after 2023-04-06. 2023-04-06 is Thursday and the date of the next Monday is 2023-04-10. MySQL > select next_day('2023-04-06', 'Monday'); +-+ | next_day('2023-04-06', 'Monday') | +-+ | 2023-04-10 | +-+ MySQL > select next_day('2023-04-06', 'Tue'); +-+ | next_day('2023-04-06', 'Tue') | +-+ | 2023-04-11 | +-+ MySQL > select next_day('2023-04-06 20:13:14', 'Fr'); ++ | next_day('2023-04-06 20:13:14', 'Fr') | ++ | 2023-04-07 | ++ ``` NEXT_DAY, NEXT