cwielenb/CNCF-Dataset huggingface dataset:
Project: FOSSA (Provisioning / Security & Compliance)
File: perl.md

| Strategy | Direct Deps | Transitive Deps | Edges | Classifies Dev Dependencies | Container Scanning | | | | | -- | | | | `*META.{yml, json} | :whitecheckmark: | :whitecheckmark: | :x: | :whitecheckmark: | :whitecheckmark: | Find a file named `MYMETA.json`, `MYMETA.yml`, `META.json`, or `META.yml`. Parse `MYMETA.{yml, json}` or `META.{yml, json}` to identify dependencies. Dependency required for `runtime` only will be reported. Reported analysis will not have any edges. Build your perl target. When you do this, you should have `MYMETA.yml` and `MYMETA.json`. Execute `fossa analyze -o` on the project to print analyzed dependency graphing (this will not upload any analysis to any endpoint) Explicitly specify an analysis target in `.fossa.yml` file. The example below excludes all other analysis targets: ```yaml version: 3 targets: only: type: perl ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.6.6.16-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : fix HashMethodOneNumber get wrong key value when column is const. (). Backported in : Fix bug in collectFilesToSkip() by adding correct file extension(.idx or idx2) for indexes to be recalculated, avoid wrong hard links. Fixed . (). Backported in : Fix insufficient argument check for encryption functions (found by query fuzzer). This closes . (). Backported in : Fix possible segfault in CapnProto input format. This bug was found and send through ClickHouse bug-bounty by kiojj*. (). Backported in : Fix rare bug with column TTL for MergeTree engines family: In case of repeated vertical merge the error `Cannot unlink file ColumnName.bin ... No such file or directory.` could happen. (). fix heap buffer overflow by limiting http chunk size (). Reduce changelog verbosity in CI (). DNSResolver remove AIV4MAPPED, AIALL hints ().
Project: Meshery (Provisioning / Automation & Configuration)
File: 02-17-2023-07-51-02_b48319c7.md

timestamp: "2023-02-17 07:51:04 UTC Fri" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.51" k8s-distro: minikube k8s-version: "v1.24.7" service-mesh: Consul service-mesh-version: "v1.0.4" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Checkov (Provisioning / Security & Compliance)
File: Visualizing Checkov Output.md

layout: default published: true title: Visualizing Checkov Output nav_order: 6 You can integrate Checkov with Prisma Cloud to view the results of Checkov scans in Prisma Cloud. To get a Prisma Cloud issued Access Key and Secret Key token, follow the steps in the . After acquiring the Access Key and Secret Key token, run Checkov as follows: ```shell checkov -d <directory> --bc-api-key <access key>::<secret key> --prisma-api-url <prisma api url> --repo-id <repo_id> --branch <branch> ``` Or by using the `-f` file flag: ```shell checkov -f <file1> <file2> ... <filen> --bc-api-key <access key>::<secret key> --prisma-api-url <prisma api url> --repo-id <repoid> --branch <branch> ``` The table below details the arguments used when executing the API token: | Argument | Description | | -- | -- | | `<access key>::<secret key>` | Prisma cloud API key in the following format `ACCESSKEY::SECRETKEY` | | `<repo_id>` | Identifying string of the scanned repository, following the standard Git repository naming scheme: `<owner>/<name>` | | `<branch>` | Branch name to be persisted on platform. Defaults to the master branch. NOTE: Ensure the scanned directory (supplied in the `-d` flag) is currently checked out from the given branch name. | To enrich Prisma Cloud's context with CI/CD systems data, we strongly recommend that Checkov uses environment variables. | Environment Variable | Description | Example | ||--|--| | BCFROMBRANCH | Source branch | feature/foo | | BCTOBRANCH | Target branch | main | | BCPRID | Pull request identifier | 825 | | BCPRURL | Link to pull request/merge request | https://github.com/bridgecrewio/checkov/pull/825 | | BCCOMMITHASH | Commit identifier | 5df50ab857e7a255e4e731877748b539915ad489 | | BCCOMMITURL | Link to commit in CI/VCS system | https://github.com/bridgecrewio/checkov/commit/5df50ab857e7a255e4e731877748b539915ad489 | | BCAUTHORNAME | User associated with the CI trigger | schosterbarak | | BCAUTHORURL | Link to the user profile page | https://github.com/schosterbarak | | BCRUNID | CI run identifier | 525220526 | | BCRUNURL | Link to the run in the CI system | https://github.com/bridgecrewio/checkov/actions/runs/525220526 | | BCREPOSITORYURL | Link to the GitHub repository | https://github.com/bridgecrewio/checkov/ | | BC_SOURCE | Name of CI system being integrated | githubActions | | PRISMAAPIURL | URL of Prisma app for platform integration | https://app3.prismacloud.io | | SLSFILEMASK | File names mask for all serverless files | serverless.yaml,serverless.yml | | CHECKOVREQUESTCONNECT_TIMEOUT | Number of seconds requests will wait to establish a connection to the platform | 3.1 | | CHECKOVREQUESTREAD_TIMEOUT | Number of seconds requests will wait for the platform to send a response. This duration matches our timeout settings, so changes are likely unnecessary. | 30 | | CHECKOVREQUESTRETRIES | Number of retries requests will do towards the platform | 3 | After successfully executing, scan results are persisted in , and can be seen in Projects.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: losetup.md

Image to setup a loop device backed by a regular file in a -generated image. The typical use case is to have a portable storage location which can be used to persist settings or other files. Can be combined with the `linuxkit/dm-crypt` package for protection. The setup is a one time step during boot: ```yaml onboot: name: losetup image: linuxkit/losetup:<hash> command: ["/usr/bin/loopy", "-c", "/var/test.img"] ``` The above will associate the file `/var/test.img` with `/dev/loop0` and will also create it if it's not present. The container by default bind-mounts `/var:/var` and `/dev:/dev`. Usually the loop-file will reside on external storage which should be typically mounted under `/var` hence the choice of the defaults. If the loop-file is located somewhere else and you need a different bind-mount for it then do not forget to explicitly bind-mount `/dev:/dev` as well or else `losetup` will fail. |Option|Default|Required|Notes| ||||| |`-c` or `--create`||No|Creates the file if not present. If `--create` is not specified and the file is missing then the loop setup will obviously fail.| |`-s` or `--size`|10|No|If `--create` was specified and the file is not present then this sets the size in MiB of the created file. The file will be filled from `/dev/zero`.| |`-d` or `--dev`|`/dev/loop0`|No|Loop device which should be associated with the file.| |`<file>`||Yes|The file to use as backing storage.|
Project: FOSSA (Provisioning / Security & Compliance)
File: packagesconfig.md

The `packages.config` XML file is used in some project types to maintain the list of packages referenced by the project. Note: projects that use `PackageReference` do not use `packages.config`. Walk the directory and find all files names `packages.config` Parse the XML file, and collect dependency data from all `package` tags within the `packages` section: ``` <?xml version="1.0" encoding="utf-8"?> <packages> <package id="jQuery" version="3.1.1" targetFramework="net46" /> <package id="NLog" version="4.3.10" targetFramework="net46" /> </packages> ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.16.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | JobClient.submitJob(...) should not use "Dr Who" as a default username | Major | . | Tsz Wo Nicholas Sze | Tsz Wo Nicholas Sze | | | Distcp deleting target directory | Blocker | util | Koji Noguchi | Chris Douglas | | | Datanode fails write to DFS file with exception message "Trying to change block file offset" | Major | . | dhruba borthakur | dhruba borthakur | | | JobHistory log format for COUNTER is ambigurous | Major | . | Runping Qi | Runping Qi | | | LocalJobRunner gets NullPointerException if there is no output directory | Critical | . | Owen O'Malley | Amareshwari Sriramadasu | | | FileSystem cache key should be updated after a FileSystem object is created | Major | fs | Tsz Wo Nicholas Sze | Tsz Wo Nicholas Sze | | | Update the Javadoc in JobConf.getOutputPath to reflect the actual temporary path | Major | documentation | Devaraj Das | Amareshwari Sriramadasu | | | DataNode pipelining : failure on mirror results in failure on upstream datanode | Blocker | . | Raghu Angadi | Raghu Angadi | | | redesigned plugin has missing functionality | Major | contrib/eclipse-plugin | Chris Dyer | Christophe Taton | | | MultithreadedMapRunner eats RuntimeExceptions | Blocker | . | Alejandro Abdelnur | Alejandro Abdelnur | | | Runtime exceptions not killing job | Blocker | . | Amareshwari Sriramadasu | Amareshwari Sriramadasu | | | JobTracker shuts down during initialization if the NameNode is down | Blocker | . | Amareshwari Sriramadasu | Amareshwari Sriramadasu | | | distcp seems to be broken in 0.16.1 | Blocker | util | Christian Kunz | Chris Douglas | | | Trash not being expunged, Trash Emptier thread gone by NPE | Blocker | fs | Koji Noguchi | Koji Noguchi | | | distcp fails for files with zero length | Blocker | util | Mukund Madhugiri | Chris Douglas | | | fsck failing with NPE | Blocker | . | Koji Noguchi | dhruba borthakur | | | compile-core-test fails for branch 0.16 | Blocker | . | Amareshwari Sriramadasu | Alejandro Abdelnur | | | [HOD] Hadoop.tmp.dir should not be set to cluster directory | Blocker | contrib/hod | Vinod Kumar Vavilapalli | Vinod Kumar Vavilapalli | | | dfs -chown does not like "\_" underscore in user name | Blocker | fs | Koji Noguchi | Raghu Angadi | | | NPE in FSDirectory.unprotectedSetPermission | Blocker | . | Koji Noguchi | Konstantin Shvachko | | | MultithreadMapRunner keeps consuming records even if trheads are not available | Critical | . | Alejandro Abdelnur | Alejandro Abdelnur | | | TestDFSPermission due to not throwing exception. | Major | . | Konstantin Shvachko | Konstantin Shvachko | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Remove HBase from Hadoop contrib | Major | . | Jim Kellerman | Jim Kellerman |
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Example_Filter.md

In most cases, tag is a simple and useful design to select messages you want. For example: ```java DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("CID_EXAMPLE"); consumer.subscribe("TOPIC", "TAGA || TAGB || TAGC"); ``` The consumer will receive messages that contains TAGA or TAGB or TAGC. But the limitation is that one message only can have one tag, and this may not work for sophisticated scenarios. In this case, you can use SQL expression to filter out messages. SQL feature could do some calculation through the properties you put in when sending messages. Under the grammars defined by RocketMQ, you can implement some interesting logic. Here is an example: ``` | message | |-| a > 5 AND b = 'abc' | a = 10 | --> Gotten | b = 'abc'| | c = true | | message | |-| a > 5 AND b = 'abc' | a = 1 | --> Missed | b = 'abc'| | c = true | ``` RocketMQ only defines some basic grammars to support this feature. You could also extend it easily. Numeric comparison, like >, >=, <, <=, BETWEEN, =; Character comparison, like =, <>, IN; IS NULL or IS NOT NULL; Logical AND, OR, NOT; Constant types are: Numeric, like 123, 3.1415; Character, like abc, must be made with single quotes; NULL, special constant; Boolean, TRUE or FALSE; Only push consumer could select messages by SQL92. The interface is: ``` public void subscribe(finalString topic, finalMessageSelector messageSelector) ``` You can put properties in message through method putUserProperty when sending. ```java DefaultMQProducer producer = new DefaultMQProducer("pleaserenameuniquegroupname"); producer.start(); Message msg = new Message("TopicTest", tag, ("Hello RocketMQ " + i).getBytes(RemotingHelper.DEFAULT_CHARSET) ); // Set some properties. msg.putUserProperty("a", String.valueOf(i)); SendResult sendResult = producer.send(msg); producer.shutdown(); ``` Use `MessageSelector.bySql` to select messages through SQL when consuming. ```java DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("pleaserenameuniquegroupname_4"); // only subscribe messages have property a, also a >=0 and a <= 3 consumer.subscribe("TopicTest", MessageSelector.bySql("a between 0 and 3")); consumer.registerMessageListener(new MessageListenerConcurrently() { @Override public ConsumeConcurrentlyStatus consumeMessage(List<MessageExt> msgs, ConsumeConcurrentlyContext context) { return ConsumeConcurrentlyStatus.CONSUME_SUCCESS; } }); consumer.start(); ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: youtube.md

title: "YouTube" icon: /images/logos/powered-by/youtube.png hasLink: "http://youtube.com" <!-- 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: Glasskube (App Definition and Development / Application Definition & Image Build)
File: 01_client.md

The client is an executable binary written in Go. This is the component the user primarily interacts with. It accepts user inputs via a Web UI and CLI. Both kinds of user interface are supposed to provide the same functionality, and it's up to the user to choose their favorite way of doing things. The client's tasks revolve around handling user input and consequently managing the required operations with the cluster (via the Kubernetes API) and the package repository. For example, when installing a package, the client creates a `Package` custom resource via the Kubernetes API. When listing the available packages, it fetches the package list from the repository. The CLI commands make use of the , which helps in crafting easy to use command line applications. The GUI itself is contained in the `glasskube serve` command, which spins up a local webserver. For the technical preview we decided to render the pages server side with Go templates. The web technology stack might change in future versions.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_gcp_delete.md

Delete a GCP YugabyteDB Anywhere provider Delete a GCP provider in YugabyteDB Anywhere ``` yba provider gcp delete [flags] ``` ``` -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for delete ``` ``` -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 provider for the action. 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 GCP provider
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 03_basic_configuring_pipelines.md

Prompt: How do I configure pipeline in Apache Beam? Response: Configuring pipeline options in Apache Beam is crucial for specifying the execution environment, managing resources, and tailoring the pipeline's behavior to meet specific data processing needs and performance requirements. You can set pipeline options programmatically or pass them in using the command line. These options include runner-specific settings, job name, project ID (for cloud runners), machine types, number of workers, and more. Apache Beam offers a variety of that allow you to customize and optimize your data processing pipelines. Beam SDKs include a command-line parser that you can use to set pipeline options. Use command-line arguments in the format `--<option>=<value>`. For example, the following command sets the `--runner` option `DirectRunner` and the `--project` option `my-project-id`: ```bash python my-pipeline.py --runner=DirectRunner --project=my-project-id ``` To set the pipeline options programmatically, use the `PipelineOptions` class. For example, the following code sets the `--runner` option to `DirectRunner` and the `--project` option to `my-project-id`: ```python from apache_beam import Pipeline from apachebeam.options.pipelineoptions import PipelineOptions options = PipelineOptions( project='my-project-id', runner='DirectRunner' ) `````` In addition to the standard pipeline options, you can add custom pipeline options. For a common pattern for configuring pipeline options, see . The demonstrates how to set pipeline options at runtime by using command-line options.
Project: Pinniped (Provisioning / Key Management)
File: configure-concierge-webhook.md

title: Configure the Pinniped Concierge to validate webhook tokens description: Set up webhook-based token authentication on an individual Kubernetes cluster. cascade: layout: docs menu: docs: name: Webhook Authentication weight: 50 parent: howto-configure-concierge aliases: /docs/howto/configure-concierge-webhook/ The Concierge can validate arbitrary tokens via an external webhook endpoint using the . Before starting, you should have the locally and . You should also have a custom TokenReview webhook endpoint: Your webhook endpoint must handle the `authentication.k8s.io/v1` . Your webhook must be accessible from the Concierge pod over HTTPS. Create a WebhookAuthenticator describing how to validate tokens using your webhook: ```yaml apiVersion: authentication.concierge.pinniped.dev/v1alpha1 kind: WebhookAuthenticator metadata: name: my-webhook-authenticator spec: endpoint: https://my-webhook.example.com/any/path tls: certificateAuthorityData: "LS0tLS1CRUdJTi[...]" ``` If you've saved this into a file `my-webhook-authenticator.yaml`, then install it into your cluster using: ```sh kubectl apply -f my-webhook-authenticator.yaml ``` Generate a kubeconfig file to target the WebhookAuthenticator: ```sh pinniped get kubeconfig \ --static-token-env MYCLUSTERACCESS_TOKEN \ > my-cluster.yaml ``` This creates a kubeconfig YAML file `my-cluster.yaml` that targets your WebhookAuthenticator using `pinniped login static` as an . It should look something like below: ```yaml apiVersion: v1 kind: Config current-context: pinniped clusters: cluster: certificate-authority-data: LS0tLS[...] server: https://my-kubernetes-api-endpoint.example.com:59986 name: pinniped contexts: context: cluster: pinniped user: pinniped name: pinniped users: name: pinniped user: exec: apiVersion: client.authentication.k8s.io/v1beta1 command: /usr/local/bin/pinniped args: login oidc login static --enable-concierge --concierge-api-group-suffix=pinniped.dev --concierge-authenticator-name=my-webhook-authenticator --concierge-authenticator-type=webhook --concierge-endpoint=https://127.0.0.1:59986 --concierge-ca-bundle-data=LS0tLS[...] --token-env=MYCLUSTERACCESS_TOKEN ``` Set the `$MYCLUSTERACCESS_TOKEN` environment variable and use the kubeconfig with `kubectl` to access your cluster: ```sh MYCLUSTERACCESS_TOKEN=secret-token kubectl --kubeconfig my-cluster.yaml get namespaces ``` You should see: The `pinniped login static` command is silently executed automatically by `kubectl`. The command-line tool sends your token to the Concierge which validates it by making a request to your webhook endpoint. In your shell, you see your clusters namespaces. If instead you get an access denied error, you may need to create a ClusterRoleBinding for the username/groups returned by your webhook, for example: ```sh kubectl create clusterrolebinding my-user-admin --clusterrole edit --user my-username ```
Project: YugabyteDB (App Definition and Development / Database)
File: create_sequence,sequence_name,sequence_options.grammar.md

```output.ebnf createsequence ::= CREATE SEQUENCE [ IF NOT EXISTS ] sequencename sequence_options sequencename ::= qualifiedname sequence_options ::= [ INCREMENT [ BY ] increment ] [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ] [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ] ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_client_common.md

/ @kui-shell/plugin-client-common InputProviderProps: `InputOptions` & `InputProps` & `BlockViewTraits` KuiProps: `Partial`<`KuiConfiguration`\> & `GuidebookProps` & `CommonClientProps` & { `bottomInput?`: `true` \| `React.ReactNode` ; `initialTabTitle?`: `string` ; `noBootstrap?`: `boolean` ; `quietExecCommand?`: `boolean` ; `toplevel?`: `React.ReactNode` \| `React.ReactNode`[] } SplitPosition: `NewSplitRequest` ViewLevel: `"loading"` \| `"removed"` \| `"hidden"` \| `"normal"` \| `"obscured"` \| `"ok"` \| `"warn"` \| `"error"` \| `"info"` variants of how the information should be presented KuiContext: `Context`<`KuiConfiguration`\> Alert: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> Ansi: `LazyExoticComponent`<(`props`: `Props`) => `Element`\> Button: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> Card: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> DropDown: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> Icons: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> LeftNavSidecar: `LazyExoticComponent`<typeof `default`\> Markdown: `LazyExoticComponent`<typeof `default`\> Popover: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> Select: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> Tag: `LazyExoticComponent`<(`props`: `Props`) => `React.ReactElement`\> TagWidget: `LazyExoticComponent`<(`props`: `Props`) => `Element`\> TopNavSidecar: `LazyExoticComponent`<typeof `default`\> DropdownWidget(`props`): `Element` | Name | Type | | : | : | | `props` | `Props` | `Element` Loading(`props`): `React.ReactElement` | Name | Type | | : | :-- | | `props` | `default` | `React.ReactElement` SpaceFiller(): `Element` This components can be used as a space filler in your StatusStripe. `Element` Tooltip(`props`): `React.ReactElement` | Name | Type | | : | : | | `props` | `Props` | `React.ReactElement` allocateTabUUID(): `string` `string` defaultOnKeyDown(`event`): `void` | Name | Type | | : | :-- | | `event` | `KeyboardEvent` | `void` defaultOnKeyPress(`event`): `Promise`<`void`\> | Name | Type | | : | :-- | | `event` | `KeyboardEvent` | `Promise`<`void`\> defaultOnKeyUp(`evt`): `Promise`<`void`\> Listen for ctrl+R | Name | Type | | :- | :-- | | `evt` | `KeyboardEvent`<`Element`\> | `Promise`<`void`\> inDebugMode(): `string` \| `true` `string` \| `true`