cwielenb/CNCF-Dataset huggingface dataset:
Project: LinuxKit (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

We definitely welcome your patches and contributions to gRPC! Please read the gRPC organization's and before proceeding. If you are new to github, please start by reading In order to protect both you and ourselves, you will need to sign the . How to get your contributions merged smoothly and quickly. Create small PRs that are narrowly focused on addressing a single concern. We often times receive PRs that are trying to fix several things at a time, but only one fix is considered acceptable, nothing gets merged and both author's & review's time is wasted. Create more PRs to address different concerns and everyone will be happy. The grpc package should only depend on standard Go packages and a small number of exceptions. If your contribution introduces new dependencies which are NOT in the , you need a discussion with gRPC-Go authors and consultants. For speculative changes, consider opening an issue and discussing it first. If you are suggesting a behavioral or API change, consider starting with a [gRFC proposal](https://github.com/grpc/proposal). Provide a good PR description as a record of what change is being made and why it was made. Link to a github issue if it exists. Don't fix code style and formatting unless you are already changing that line to address an issue. PRs with irrelevant changes won't be merged. If you do want to fix formatting or style, do that in a separate PR. Unless your PR is trivial, you should expect there will be reviewer comments that you'll need to address before merging. We expect you to be reasonably responsive to those comments, otherwise the PR will be closed after 2-3 weeks of inactivity. Maintain clean commit history and use meaningful commit messages. PRs with messy commit history are difficult to review and won't be merged. Use `rebase -i upstream/master` to curate your commit history and/or to bring in latest changes from master (but avoid rebasing in the middle of a code review). Keep your PR up to date with upstream/master (if there are merge conflicts, we can't really merge your change). All tests need to be passing before your change can be merged. We recommend you run tests locally before creating your PR to catch breakages early on. `VETSKIPPROTO=1 ./vet.sh` to catch vet errors `go test -cpu 1,4 -timeout 7m ./...` to run the tests `go test -race -cpu 1,4 -timeout 7m ./...` to run tests in race mode Exceptions to the rules can be made if there's a compelling reason for doing so.
Project: YugabyteDB (App Definition and Development / Database)
File: cr-histogram.md

title: cr_histogram.sql linkTitle: cr_histogram.sql headerTitle: cr_histogram.sql description: cr_histogram.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: cr-histogram parent: analyzing-a-normal-distribution weight: 100 type: docs Save this script as `cr_histogram.sql`. ```plpgsql -- "scale_factor" controls the histogram height. -- Use 10 for 10,000 rows, 100 for 100,000 rows. create or replace function histogram( noofbukets in int, scale_factor in numeric) returns SETOF text language sql as $body$ with bucket_assignments as ( select bucket(dpscore, 0::double precision, 100::double precision, noof_bukets) as bucket from t4) select to_char(count(*), '9999')||' | '|| rpad('=', (count(*)/scale_factor)::int, '=') from bucket_assignments group by bucket order by bucket; $body$; ```
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Trident-RAS-API.md

title: Trident RAS API layout: documentation documentation: true The Trident RAS (Resource Aware Scheduler) API provides a mechanism to allow users to specify the resource consumption of a Trident topology. The API looks exactly like the base RAS API, only it is called on Trident Streams instead of Bolts and Spouts. In order to avoid duplication and inconsistency in documentation, the purpose and effects of resource setting are not described here, but are instead found in the First, an example: ```java TridentTopology topo = new TridentTopology(); topo.setResourceDefaults(new DefaultResourceDeclarer(); .setMemoryLoad(128) .setCPULoad(20)); TridentState wordCounts = topology .newStream("words", feeder) .parallelismHint(5) .setCPULoad(20) .setMemoryLoad(512,256) .each( new Fields("sentence"), new Split(), new Fields("word")) .setCPULoad(10) .setMemoryLoad(512) .each(new Fields("word"), new BangAdder(), new Fields("word!")) .parallelismHint(10) .setCPULoad(50) .setMemoryLoad(1024) .each(new Fields("word!"), new QMarkAdder(), new Fields("word!?")) .groupBy(new Fields("word!")) .persistentAggregate(new MemoryMapState.Factory(), new Count(), new Fields("count")) .setCPULoad(100) .setMemoryLoad(2048); ``` Resources can be set for each operation (except for grouping, shuffling, partitioning). Operations that are combined by Trident into single Bolts will have their resources summed. Every Bolt is given at least the default resources, regardless of user settings. In the above case, we end up with a spout and spout coordinator with a CPU load of 20% each, and a memory load of 512MiB on-heap and 256MiB off-heap. a bolt with 80% cpu load (10% + 50% + 20%) and a memory load of 1664MiB (1024 + 512 + 128) on-heap from the combined `Split` and `BangAdder` and the `QMarkAdder` which used the default resources contained in the DefaultResourceDeclarer a bolt with 100% cpu load and a memory load of 2048MiB on-heap, with default value for off-heap. Resource declarations may be called after any operation. The operations without explicit resources will get the defaults. If you choose to set resources for only some operations, defaults must be declared, or topology submission will fail. Resource declarations have the same boundaries as parallelism hints. They don't cross any groupings, shufflings, or any other kind of repartitioning. Resources are declared per operation, but get combined within boundaries.
Project: ArangoDB (App Definition and Development / Database)
File: configurations.md

<!-- Copyright 2018 Paul Fultz II Distributed under the Boost Software License, Version 1.0. (http://www.boost.org/LICENSE10.txt) --> Configurations ============== There are several configuration macros that control the behavior of Boost.HigherOrderFunctions library. ```eval_rst +--+--+ | Name | Description | +=========================================+================================================================================+ | ``BOOSTHOFCHECKUNPACKSEQUENCE`` | Unpack has extra checks to ensure that the function will be invoked with the | | | sequence. This extra check can help improve error reporting but it can slow | | | down compilation. This is enabled by default. | +--+--+ | ``BOOSTHOFNOEXPRESSIONSFINAE`` | This controls whether the library will use expression SFINAE to detect the | | | callability of functions. On MSVC, this is enabled by default, since it does | | | not have full support for expression SFINAE. | +--+--+ | ``BOOSTHOFRECURSIVECONSTEXPRDEPTH`` | Because C++ instantiates `constexpr` functions eagerly, recursion with | | | `constexpr` functions can cause the compiler to reach its internal limits. The | | | setting is used by the library to set a limit on recursion depth to avoid | | | infinite template instantiations. The default is 16, but increasing the limit | | | can increase compile times. | +--+--+ ```
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_events_send.md

Events send messages to an 'events' channel command Events send command allows to send (publish) one or many messages to an 'events' channel ``` kubemq events send [flags] ``` ``` kubemq events send some-channel some-body kubemq events send some-channel some-body --metadata some-metadata kubemq events send some-channel some-body -m 10 kubemq events send some-channel some-body -m 100 -s ``` ``` -h, --help help for send -m, --messages int set how many 'events' messages to send (default 1) --metadata string set body metadata field ``` - Execute Kubemq 'events' Pub/Sub commands
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.3.0.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Apache Hadoop release 3.0.2 to fix deploying shaded jars in artifacts. | Major | . | Lei (Eddy) Xu | Lei (Eddy) Xu |
Project: Trivy-Operator (Provisioning / Security & Compliance)
File: kubectl.md

The Kubernetes Yaml Deployment files are available on GitHub in under `/deploy/static`. This will install the operator in the `trivy-system` namespace and configure it to scan all namespaces, except `kube-system` and `trivy-system`: ```bash kubectl apply -f https://raw.githubusercontent.com/aquasecurity/trivy-operator/{{ git.tag }}/deploy/static/trivy-operator.yaml ``` To confirm that the Operator is running, check that the `trivy-operator` Deployment in the `trivy-system` namespace is available and all its containers are ready: ```bash $ kubectl get deployment -n trivy-system NAME READY UP-TO-DATE AVAILABLE AGE trivy-operator 1/1 1 1 11m ``` If for some reason it's not ready yet, check the logs of the `trivy-operator` Deployment for errors: ```bash kubectl logs deployment/trivy-operator -n trivy-system ``` You can configure Trivy-Operator to control it's behavior and adapt it to your needs. Aspects of the operator machinery are configured using environment variables on the operator Pod, while aspects of the scanning behavior are controlled by ConfigMaps and Secrets. To learn more, please refer to the [Configuration] documentation. !!! danger Uninstalling the operator and deleting custom resource definitions will also delete all generated security reports. You can uninstall the operator with the following command: ``` kubectl delete -f https://raw.githubusercontent.com/aquasecurity/trivy-operator/{{ git.tag }}/deploy/static/trivy-operator.yaml ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_resourcemanager_folder_iam_binding.md

+++ title = "googleresourcemanagerfolderiambinding resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleresourcemanagerfolderiambinding" identifier = "inspec/resources/gcp/googleresourcemanagerfolderiambinding.md googleresourcemanagerfolderiambinding resource" parent = "inspec/resources/gcp" +++ A `googleresourcemanagerfolderiambinding` is used to test a Google Folder Iam Bindings ```ruby describe googleresourcemanagerfolderiambinding(name: "name", role: "roles/editor") do it { should exist } its('members') { should include 'user:testuser@example.com' } end ``` Properties that can be accessed from the `googleresourcemanagerfolderiambinding` resource: `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. Ensure the is enabled for the current project.
Project: StarRocks (App Definition and Development / Database)
File: RESUME_ROUTINE_LOAD.md

displayed_sidebar: "English" import RoutineLoadPrivNote from '../../../assets/commonMarkdown/RoutineLoadPrivNote.md' Resumes a Routine load job. The job will temporarily enter NEED_SCHEDULE state because the job is being re-scheduled. And after some time, the job will be resumed to RUNNING state, continuing consuming messages from the data source and loading data. You can check the job's information using the statement. <RoutineLoadPrivNote /> ```SQL RESUME ROUTINE LOAD FOR [dbname.]<jobname> ``` | Parameter | Required | Description | | - | | | | db_name | | The name of the database to which the Routine Load job belongs. | | job_name | | The name of the Routine Load job. | Resume the Routine Load job `exampletbl1ordertest1` in the database `example_db`. ```SQL RESUME ROUTINE LOAD FOR exampledb.exampletbl1_ordertest1; ```
Project: KICS (Provisioning / Security & Compliance)
File: f906113d-cdc0-415a-ba60-609cc6daaf4d.md

title: Role With Privilege Escalation By Actions 'iam:AttachGroupPolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f906113d-cdc0-415a-ba60-609cc6daaf4d Query name: Role With Privilege Escalation By Actions 'iam:AttachGroupPolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:AttachGroupPolicy' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:AttachGroupPolicy", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: mllib-pmml-model-export.md

layout: global title: PMML model export - RDD-based API displayTitle: PMML model export - RDD-based API license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You 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. Table of contents {:toc} `spark.mllib` supports model export to Predictive Model Markup Language (). The table below outlines the `spark.mllib` models that can be exported to PMML and their equivalent PMML model. <table> <thead> <tr><th>spark.mllib model</th><th>PMML model</th></tr> </thead> <tbody> <tr> <td>KMeansModel</td><td>ClusteringModel</td> </tr> <tr> <td>LinearRegressionModel</td><td>RegressionModel (functionName="regression")</td> </tr> <tr> <td>RidgeRegressionModel</td><td>RegressionModel (functionName="regression")</td> </tr> <tr> <td>LassoModel</td><td>RegressionModel (functionName="regression")</td> </tr> <tr> <td>SVMModel</td><td>RegressionModel (functionName="classification" normalizationMethod="none")</td> </tr> <tr> <td>Binary LogisticRegressionModel</td><td>RegressionModel (functionName="classification" normalizationMethod="logit")</td> </tr> </tbody> </table> <div class="codetabs"> <div data-lang="scala" markdown="1"> To export a supported `model` (see table above) to PMML, simply call `model.toPMML`. As well as exporting the PMML model to a String (`model.toPMML` as in the example above), you can export the PMML model to other formats. Refer to the and for details on the API. Here a complete example of building a KMeansModel and print it out in PMML format: {% include_example scala/org/apache/spark/examples/mllib/PMMLModelExportExample.scala %} For unsupported models, either you will not find a `.toPMML` method or an `IllegalArgumentException` will be thrown. </div> </div>
Project: ShardingSphere (App Definition and Development / Database)
File: data-source.en.md

+++ title = "Data Source" weight = 4 chapter = true +++ ShardingSphere-Proxy supports common data source connection pools: HikariCP, C3P0, DBCP (C3P0, DBCP need download plugin from repository). The connection pool can be specified through the parameter `dataSourceClassName`. When not specified, the default data source connection pool is HikariCP. ```yaml dataSources: # Data sources configuration, multiple <data-source-name> available <datasourcename>: # Data source name dataSourceClassName: # Data source connection pool full class name url: # The database URL connection username: # Database username password: # The database password ``` ```yaml dataSources: ds_1: url: jdbc:mysql://localhost:3306/ds_1 username: root password: ds_2: dataSourceClassName: com.mchange.v2.c3p0.ComboPooledDataSource url: jdbc:mysql://localhost:3306/ds_2 username: root password: ds_3: dataSourceClassName: org.apache.commons.dbcp2.BasicDataSource url: jdbc:mysql://localhost:3306/ds_3 username: root password: ```
Project: StarRocks (App Definition and Development / Database)
File: bitmap_to_base64.md

displayed_sidebar: "English" Converts a bitmap to a Base64-encoded string. This function is supported from v2.5. ```Haskell VARCHAR bitmaptobase64(BITMAP bitmap) ``` `bitmap`: the bitmap to convert. This parameter is required. If the input value is invalid, an error is returned. Returns a value of the VARCHAR type. Example 1: Use this function with other bitmap functions. ```Plain select bitmaptobase64(bitmapfromstring("0, 1, 2, 3")); +-+ | bitmaptobase64(bitmapfromstring('0, 1, 2, 3')) | +-+ | AjowAAABAAAAAAADABAAAAAAAAEAAgADAA== | +-+ 1 row in set (0.00 sec) select bitmaptobase64(to_bitmap(1)); +--+ | bitmaptobase64(to_bitmap(1)) | +--+ | AQEAAAA= | +--+ 1 row in set (0.00 sec) select bitmaptobase64(bitmap_empty()); +-+ | bitmaptobase64(bitmap_empty()) | +-+ | AA== | +-+ 1 row in set (0.00 sec) ``` Example 2: Convert each value in a BITMAP column into Base64-encoded strings. Create an Aggregate table `pageuv` where the `AGGREGATE KEY` is (`pageid`, `visitdate`). This table contains a BITMAP column `visitusers` whose values are to be aggregated. ```SQL CREATE TABLE `page_uv` (`page_id` INT NOT NULL, `visit_date` datetime NOT NULL, `visitusers` BITMAP BITMAPUNION NOT NULL ) ENGINE=OLAP AGGREGATE KEY(`pageid`, `visitdate`) DISTRIBUTED BY HASH(`page_id`) PROPERTIES ( "replication_num" = "3", "storage_format" = "DEFAULT" ); ``` Insert data into this table. ```SQL insert into page_uv values (1, '2020-06-23 01:30:30', to_bitmap(13)), (1, '2020-06-23 01:30:30', to_bitmap(23)), (1, '2020-06-23 01:30:30', to_bitmap(33)), (1, '2020-06-23 02:30:30', to_bitmap(13)), (2, '2020-06-23 01:30:30', to_bitmap(23)); select * from pageuv order by pageid; +++-+ | pageid | visitdate | visit_users | +++-+ | 1 | 2020-06-23 01:30:30 | NULL | | 1 | 2020-06-23 02:30:30 | NULL | | 2 | 2020-06-23 01:30:30 | NULL | +++-+ ``` Convert each value in the `visit_users` column into a Base64-encoded string. ```Plain select pageid, bitmaptobase64(visitusers) from page_uv; +++ | pageid | bitmaptobase64(visitusers) | +++ | 1 | CgMAAAANAAAAAAAAABcAAAAAAAAAIQAAAAAAAAA= | | 1 | AQ0AAAA= | | 2 | ARcAAAA= | +++ ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_run-pipeline.md

title: "devspace run-pipeline --help" sidebar_label: devspace run-pipeline Starts a DevSpace pipeline ``` devspace run-pipeline [flags] ``` ``` Execute a pipeline: devspace run-pipeline my-pipeline devspace run-pipeline dev ``` ``` --build-sequential Builds the images one after another instead of in parallel --dependency strings Deploys only the specified named dependencies -b, --force-build Forces to build every image -d, --force-deploy Forces to deploy every deployment --force-purge Forces to purge every deployment even though it might be in use by another DevSpace project -h, --help help for run-pipeline --max-concurrent-builds int The maximum number of image builds built in parallel (0 for infinite) --pipeline string The pipeline to execute --render If true will render manifests and print them instead of actually deploying them --sequential-dependencies If set set true dependencies will run sequentially --show-ui Shows the ui server --skip-build Skips building of images --skip-dependency strings Skips the following dependencies for deployment --skip-deploy If enabled will skip deploying --skip-push Skips image pushing, useful for minikube deployment --skip-push-local-kube Skips image pushing, if a local kubernetes environment is detected (default true) -t, --tag strings Use the given tag for all built images ``` ``` --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems --kube-context string The kubernetes context to use --kubeconfig string The kubeconfig path to use -n, --namespace string The kubernetes namespace to use --no-colors Do not show color highlighting in log output. This avoids invisible output with different terminal background colors --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before --override-name string If specified will override the DevSpace project name provided in the devspace.yaml -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```