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

title: kbcli cluster list-components List cluster components. ``` kbcli cluster list-components [flags] ``` ``` kbcli cluster list-components kbcli cluster list-components mycluster ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. -h, --help help for list-components -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --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 ``` - Cluster command.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: inference-overview.md

title: "Prediction and inference overview" <!-- 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. --> Beam provides different ways to implement inference as part of your pipeline. You can run your ML model directly in your pipeline and apply it on big scale datasets, both in batch and streaming pipelines. <table> <tr> <td> <a> {{< button-pydoc path="apache_beam.ml.inference" class="RunInference" >}} </a> </td> <td> <a target="_blank" class="button" href="https://beam.apache.org/releases/javadoc/current/index.html?org/apache/beam/sdk/extensions/python/transforms/RunInference.html"> <img src="https://beam.apache.org/images/logos/sdks/java.png" width="20px" height="30px" alt="Javadoc" /> Javadoc </a> </td> </tr> </table> The RunInference API is available with the Beam Python SDK versions 2.40.0 and later. You can use Apache Beam with the RunInference API to use machine learning (ML) models to do local and remote inference with batch and streaming pipelines. Starting with Apache Beam 2.40.0, PyTorch and Scikit-learn frameworks are supported. Tensorflow models are supported through `tfx-bsl`. For more deatils about using RunInference with Python, see . The RunInference API is available with the Beam Java SDK versions 2.41.0 and later through Apache Beam's . For information about the Java wrapper transform, see . To try it out, see the . You can create multiple types of transforms using the RunInference API: the API takes multiple types of setup parameters from model handlers, and the parameter type determines the model implementation. {{< table >}} | Task | Example | | - | | | I want to use the RunInference transform | | | I want to use RunInference with PyTorch | | | I want to use RunInference with Sklearn | | | I want to use pre-trained models (PyTorch, Scikit-learn, or TensorFlow) | |: {{< /table >}} {{< table >}} | Task | Example | | - | | | I want to build a pipeline with multiple models | | | I want to build a custom model handler with TensorRT | | | I want to use LLM inference | |: {{< /table >}}
Project: BigchainDB (App Definition and Development / Database)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' 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. Logs or terminal output If applicable, add add textual content to help explain your problem. Desktop (please complete the following information): Distribution: [e.g. Ubuntu 18.04] Bigchaindb version: Tendermint version: Mongodb version: Python full version: [e.g. Python 3.6.6] Additional context Add any other context about the problem here.
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.6.16-lts.md

sidebar_position: 1 sidebar_label: 2023 Fix rare case of CHECKSUMDOESNTMATCH error (). Fix: avoid using regex match, possibly containing alternation, as a key condition. (). Fix a crash during table loading on startup (). Fix segfault in signal handler for Keeper (). Fix buffer overflow in T64 (). Improve enrich image ().
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: notification.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: first-vela-workflow namespace: default spec: components: name: express-server type: webservice properties: image: oamdev/hello-world port: 8000 traits: type: ingress properties: domain: testsvc.example.com http: /: 8000 workflow: steps: name: dingtalk-message type: notification properties: dingding: url: value: <url> message: msgtype: text text: content: Workflow starting... name: application type: apply-application name: slack-message type: notification properties: slack: url: secretRef: name: <secret-key> key: <secret-value> message: text: Workflow ended. lark: url: value: <lark-url> message: msg_type: "text" content: "{\"text\":\" Hello KubeVela\"}" email: from: address: <sender-email-address> alias: <sender-alias> password: value: <sender-password> host: <email host like smtp.gmail.com> port: <email port, optional, default to 587> to: kubevela1@gmail.com kubevela2@gmail.com content: subject: test-subject body: test-body ``` Expected outcome We can see that before and after the deployment of the application, the messages can be seen in the corresponding group chat.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.20.md

layout: release date: 2020-11-12 tag: v0.4.20 General Overview page spanish translation @Drake8710 (#1742) Ccoss2020 fixes1803 @Drake8710 (#1804) Add partial translation of functionality section @jlcastrogro (#1793) Add meshery adaptor chart for networking service mesh @Aisuko (#1900) Add service mesh control plane dashboard for Consul, OSM, NSM, Citrix @utkarsh-pro (#1902) Revert "add new mesheryctl command" @kumarabd (#1910) add new mesheryctl command @chandrashritii (#1908) Updated 'Signed Commits' URL in PR_Template #1905 @Aniruddha-Shriwant (#1906) [Docs] Add lightbox plugin @chandrashritii (#1903) [provider-ui] Add e2e test to provider-ui to test modal @ramrodo (#1901) Maintenance Bump @fortawesome/fontawesome-svg-core from 1.2.30 to 1.2.32 in /ui @dependabot-preview (#1888) Bump notistack from 0.8.9 to 1.0.1 in /ui @dependabot-preview (#1850) Bump react-dom from 16.13.1 to 16.14.0 in /provider-ui @dependabot-preview (#1884) Bump mui-datatables from 3.6.0 to 3.7.1 in /ui @dependabot-preview (#1883) Bump @fortawesome/free-regular-svg-icons from 5.14.0 to 5.15.1 in /ui @dependabot-preview (#1885) Bump billboard.js from 1.11.0 to 2.1.3 in /ui @dependabot-preview (#1887) Bump @babel/traverse from 7.9.6 to 7.12.5 in /ui @dependabot-preview (#1892) Bump caniuse-lite from 1.0.30001109 to 1.0.30001157 in /ui @dependabot-preview (#1891) Bump @fortawesome/free-brands-svg-icons from 5.14.0 to 5.15.1 in /ui @dependabot-preview (#1889) Bump react-jss from 10.3.0 to 10.4.0 in /ui @dependabot-preview (#1890) Bump eslint-plugin-jsx-a11y from 6.3.1 to 6.4.1 in /ui @dependabot-preview (#1886) Bump eslint from 7.12.1 to 7.13.0 in /provider-ui @dependabot-preview (#1882) chore: meshery workflow fires up on release @kushthedude (#1898)
Project: StarRocks (App Definition and Development / Database)
File: SHOW_FRONTENDS.md

displayed_sidebar: "English" This statement is used to view FE nodes. :::tip Only users with the SYSTEM-level OPERATE privilege or the `cluster_admin` role can perform this operation. ::: ```sql SHOW FRONTENDS ``` Note: Name represents the name of FE node in BDBJE. Join being true means this node has already joined the cluster. But it does not mean that the node is still in the cluster, as it may be missing. Alive indicates whether the node survives. ReplayedJournalId represents the maximum metadata log ID that the node has currently replayed. LastHeartbeat is the latest heartbeat. IsHelper indicates whether the node is a helper node from BDBJE. ErrMsg is used to display error messages when the heartbeat fails.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: ulimit.image.md

Specifies resource limits to apply to processes launched when processing `RUN` instructions. This option can be specified multiple times. Recognized resource types include: "core": maximum core dump size (ulimit -c) "cpu": maximum CPU time (ulimit -t) "data": maximum size of a process's data segment (ulimit -d) "fsize": maximum size of new files (ulimit -f) "locks": maximum number of file locks (ulimit -x) "memlock": maximum amount of locked memory (ulimit -l) "msgqueue": maximum amount of data in message queues (ulimit -q) "nice": niceness adjustment (nice -n, ulimit -e) "nofile": maximum number of open files (ulimit -n) "nproc": maximum number of processes (ulimit -u) "rss": maximum size of a process's (ulimit -m) "rtprio": maximum real-time scheduling priority (ulimit -r) "rttime": maximum amount of real-time execution between blocking syscalls "sigpending": maximum number of pending signals (ulimit -i) "stack": maximum stack size (ulimit -s)
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: custom-library-microservice-authorization.md

title: Library-based Microservice Authorization labels: category: servicemesh layer: library videos: title: How Netflix is Solving Authorization Across Their Cloud speakers: name: Manish Mehta organization: netflix name: Torin Sandall organization: styra venue: Kubecon Austin 2017 link: https://www.youtube.com/watch?v=R6tUNpRpdnY allowmissingimage: true Microservice authorization can be enforced through a network proxy like Envoy/Istio/Linkerd/... or can be enforced by modifying the microservice code to use a common library. In both cases OPA makes the authorization decision that the network proxy or the library enforce.
Project: KICS (Provisioning / Security & Compliance)
File: be1d8733-3731-40c7-a845-734741c6871d.md

title: Constraining Enum Property hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: be1d8733-3731-40c7-a845-734741c6871d Query name: Constraining Enum Property Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: There is a constraining keyword in a property which is already restricted by enum values<br> ```json title="Positive test num. 1 - json file" hl_lines="24 49 38" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "category", "in": "body", "description": "max records to return", "required": true, "schema": { "$ref": "#/definitions/Category" } } ] } } }, "definitions": { "Category": { "type": "object", "properties": { "id": { "type": "integer", "format": "int64", "minimum": 1, "enum": [ 2, 3, 4, 5, 6 ] }, "name": { "type": "string", "maxLength": 10, "enum": [ "Foo", "Bar" ] } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="19 27 36" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: 200 response parameters: name: category in: body description: max records to return required: true schema: "$ref": "#/definitions/Category" definitions: Category: type: object properties: id: type: integer format: int64 minimum: 1 enum: 2 3 4 5 6 name: type: string maxLength: 10 enum: Foo Bar ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "category", "in": "body", "description": "max records to return", "required": true, "schema": { "$ref": "#/definitions/Category" } } ] } } }, "definitions": { "Category": { "type": "object", "properties": { "id": { "type": "integer", "format": "int64", "minimum": 1 }, "name": { "type": "string", "enum": [ "Foo", "Bar" ] } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: 200 response parameters: name: category in: body description: max records to return required: true schema: "$ref": "#/definitions/Category" definitions: Category: type: object properties: id: type: integer format: int64 minimum: 1 name: type: string enum: Foo Bar ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_exec.md

title: Kubectl-Dba Exec menu: docs_{{ .version }}: identifier: kubectl-dba-exec name: Kubectl-Dba Exec parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Execute script or command to a database. Execute commands or scripts to a database. ``` kubectl-dba exec ``` ``` -h, --help help for exec ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - kubectl plugin for KubeDB - Execute SQL commands to a mariadb resource - Execute commands to a mongodb resource - Execute SQL commands to a mysql resource - Execute SQL commands to a postgres resource - Execute SQL commands to a redis resource
Project: ArangoDB (App Definition and Development / Database)
File: metaprogrammg2.md

+++ title = "construct<T>" description = "" weight = 50 +++ First, we need a base definition for `make<T>`: {{% snippet "constructors.cpp" "construct-declaration" %}} This fails a static assert if the type is ever instantiated unspecialised. We then specialise for `make<file_handle>`: {{% snippet "constructors.cpp" "construct-specialisation" %}} Because this is a struct, we can list initialise `make`, and use default member initialisers to implement default arguments. This can get you surprisingly far before you need to start writing custom constructors. But in more complex code, you will usually provide all the initialisation overloads that you would for the constructors of your main type. You then implement a single phase 2 constructing function which accepts `make<YOURTYPE>` as input, and construct solely from that source.
Project: Meshery (Provisioning / Automation & Configuration)
File: kube-prometheus.md

layout: integration title: Kube Prometheus subtitle: Collaborative and visual infrastructure as code for Kube Prometheus image: /assets/img/integrations/kube-prometheus/icons/color/kube-prometheus-color.svg permalink: extensibility/integrations/kube-prometheus docURL: https://docs.meshery.io/extensibility/integrations/kube-prometheus description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring 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: Pomerium (Provisioning / Key Management)
File: RELEASING.md

Generate changelog Update docs/upgrading.md for major/minor releases Create a new release branch for major/minor releases, eg `0-15-0`, off main. Patch releases use existing release branches. Create Github release with name and tag matching `v[version]` on the appropriate release branch. Copy/paste changelog from generated output into Github release notes GH automation should take it from there and build/upload artifacts Update default branch on netlify to new release branch (new release branch only) `./scripts/changelog.sh [previous version] [next version] [branch]` This script requires docker running and GITHUB_TOKEN set with a PAT. The changelog will be written to changelog.md ```bash GITHUB_TOKEN=XXXXXX ./changelog.sh v0.14.0 v0.15.0 main changelog.md ``` ```bash GITHUB_TOKEN=XXXXXX ./changelog.sh v0.14.6 v0.14.7 main changelog.md ``` For each major or minor release, we create a release branch `[major]-[minor]-0`. This is to allow feature freeze ahead of actual release and provide a stable branch to apply patches onto for bug fixes. These branches are to be protected and may receive updates via backport or direct PR.
Project: NomsDB (App Definition and Development / Database)
File: NBS-on-AWS.md

How to use S3 and DynamoDB as the persistent storage layer for a Noms Block Store (NBS). When running atop AWS, NBS stores immutable chunk data in S3 objects and mutable state -- a 'manifest' indicating which S3 objects are live, essentially -- in DynamoDB. It is possible to have many separate Noms Block Stores backed by a single bucket/table as long as you give each a distinct name. You could also choose to spin up a separate bucket/table pair for each NBS, though this is not required -- and, indeed, probably overkill. This assumes a setup in a single AWS region. There are no special requirements on the S3 bucket you create. Just choose a name and, once it's created, remember the ARN for use later. The DynamoDB table you create, on the other hand, does need to have a particular structure. It must have a primary partition key that is a string with the name db. Again, remember its ARN for later use. The NBS code honors AWS credentials files, so when running on your development machine the easiest thing to do is drop the creds of the user that created the bucket and table above into `~/.aws/credentials` and run that way. This isn't a great approach for running in on an EC2 instance in production, however. The right way to do that is to create an IAM Role, and run your instance as that role. Create such a role using the IAM Management Console (or command line tool of your choice) and make sure it has a policy with at least the following permissions: ```json { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1453230562000", "Effect": "Allow", "Action": [ "dynamodb:BatchGetItem", "dynamodb:BatchWriteItem", "dynamodb:DeleteItem", "dynamodb:GetItem", "dynamodb:PutItem", ], "Resource": [ "[ARN for your DynamoDB table]", ] }, { "Sid": "Stmt1454457944000", "Effect": "Allow", "Action": [ "s3:AbortMultipartUpload" "s3:CompleteMultipartUpload", "s3:CreateMultipartUpload", "s3:GetObject", "s3:PutObject", "s3:UploadPart", "s3:UploadPartCopy", ], "Resource": [ "[ARN for your S3 bucket]", ] } ] } ``` This is where the ARN for your bucket and table come in. ```shell noms ds aws:dynamo-table/s3-bucket/store-name ``` If your code only needs to create a store pointing to a single named stores, you can write code similar to the following: ```go sess := session.Must(session.NewSession(aws.NewConfig().WithRegion("us-west-2"))) store := nbs.NewAWSStore("dynamo-table", "store-name", "s3-bucket", s3.New(sess), dynamodb.New(sess), 1<<28)) ``` If you find yourself wanting to create NBS instances pointing to multiple, different named stores, you can use `nbs.NewAWSStoreFactory()`, which also supports caching Noms data on disk in some cases: ```go sess := session.Must(session.NewSession(aws.NewConfig().WithRegion("us-west-2"))) fact := nbs.NewAWSStoreFactory( sess, "dynamo-table", "s3-bucket", 128 / Maximum number of open files in cache /, 1 << 28 / Amount of index data to cache in memory /, 1 << 30 / Amount of Noms data to cache on disk /, "/path/to/cache" / Directory in which to cache Noms data /, ) store := fact.CreateStore("store-name") ```