cwielenb/CNCF-Dataset huggingface dataset:
Project: StarRocks (App Definition and Development / Database)
File: SHOW_CREATE_MATERIALIZED_VIEW.md

displayed_sidebar: "English" Shows the definition of a specific asynchronous materialized view. :::tip This operation does not require privileges. ::: ```SQL SHOW CREATE MATERIALIZED VIEW [database.]<mv_name> ``` Parameters in brackets [] is optional. | Parameter | Required | Description | | - | | | | mv_name | yes | The name of the materialized view to show. | | Return | Description | | | - | | Materialized View | The name of the materialized view. | | Create Materialized View | The definition of the materialized view. | Example 1: Show the definition of a specific materialized view ```Plain MySQL > SHOW CREATE MATERIALIZED VIEW lo_mv1\G row * Materialized View: lo_mv1 Create Materialized View: CREATE MATERIALIZED VIEW `lo_mv1` COMMENT "MATERIALIZED_VIEW" DISTRIBUTED BY HASH(`lo_orderkey`) REFRESH ASYNC PROPERTIES ( "replication_num" = "3", "storage_medium" = "HDD" ) AS SELECT `wlctest`.`lineorder`.`loorderkey` AS `loorderkey`, `wlctest`.`lineorder`.`locustkey` AS `locustkey`, sum(`wlctest`.`lineorder`.`loquantity`) AS `totalquantity`, sum(`wlctest`.`lineorder`.`lorevenue`) AS `totalrevenue`, count(`wlctest`.`lineorder`.`loshipmode`) AS `shipmodecount` FROM `wlctest`.`lineorder` GROUP BY `wlctest`.`lineorder`.`loorderkey`, `wlctest`.`lineorder`.`locustkey` ORDER BY `wlctest`.`lineorder`.`loorderkey` ASC ; 1 row in set (0.01 sec) ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_projects.md

+++ title = "google_projects resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "google_projects" identifier = "inspec/resources/gcp/googleprojects.md googleprojects resource" parent = "inspec/resources/gcp" +++ A `google_projects` is used to test a Google Project resource ```ruby describe google_projects() do its('count') { should be >= 1 } its('project_ids') { should include 'chef-gcp-inspec' } its('lifecycle_states') { should include 'ACTIVE' } end ``` describe google_projects do its('count') { should be <= 100} end describe google_projects do its('project_names'){ should include "GCP Project Name" } end describe google_projects do its('projectids'){ should include "gcpproject_id" } end describe google_projects do its('project_numbers'){ should include 1122334455 } end googleprojects.where(projectid: /^prod/).projectids.each do |gcpproject_id| describe googleproject(project: gcpproject_id) do it { should exist } its('lifecycle_state') { should eq "ACTIVE" } end end googleprojects.where(projectid: /^prod/, lifecyclestate: 'ACTIVE').projectids.each do |gcpprojectid| describe googleproject(project: gcpproject_id) do it { should exist } end end Properties that can be accessed from the `google_projects` resource: See the resource for more information. `project_numbers` : an array of `google_project` number `lifecycle_states` : an array of `googleproject` lifecyclestate `project_names` : an array of `google_project` name `create_times` : an array of `googleproject` createtime `labels` : an array of `google_project` labels `parents` : an array of `google_project` parent `project_ids` : an array of `googleproject` projectid This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: FOSSA (Provisioning / Security & Compliance)
File: ios.md

The iOS buildtool ecosystem consists of two major toolchains: `Carthage` and `Cocoapods` | Strategy | Direct Deps | Transitive Deps | Edges | Container Scanning | | - | | | | | | | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | | | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :x: | | | :whitecheckmark: | :x: | :x: | :whitecheckmark: |
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: privileged.md

Give extended privileges to this container. The default is false. By default, Podman containers are unprivileged (=false) and cannot, for example, modify parts of the operating system. This is because by default a container is only allowed limited access to devices. A "privileged" container is given the same access to devices as the user launching the container, with the exception of virtual consoles (/dev/tty\d+) when running in systemd mode (--systemd=always). A privileged container turns off the security features that isolate the container from the host. Dropped Capabilities, limited devices, read-only mount points, Apparmor/SELinux separation, and Seccomp filters are all disabled. Due to the disabled security features, the privileged field should almost never be set as containers can easily break out of confinement. Containers running in a user namespace (e.g., rootless containers) cannot have more privileges than the user that launched them.
Project: YDB (App Definition and Development / Database)
File: length.md

Returns the length of the string in bytes. This function is also available under the `LEN` name . Examples ```yql SELECT LENGTH("foo"); ``` ```yql SELECT LEN("bar"); ``` {% note info %} To calculate the length of a string in Unicode characters, you can use the function .<br><br>To get the number of elements in the list, use the function . {% endnote %}
Project: Beam (App Definition and Development / Streaming & Messaging)
File: min.md

title: "Min" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.core" class="CombineGlobally" >}} Gets the element with the minimum value within each aggregation. In the following example, we create a pipeline with a `PCollection`. Then, we get the element with the minimum value in different ways. We use `Combine.Globally()` to get the minimum element from the entire `PCollection`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONMinGlobally" show="minglobally" >}} {{< /playground >}} We use `Combine.PerKey()` to get the minimum element for each unique key in a `PCollection` of key-values. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONMinPerKey" show="minper_key" >}} {{< /playground >}} {{< button-pydoc path="apache_beam.transforms.core" class="CombineGlobally" >}}
Project: YugabyteDB (App Definition and Development / Database)
File: instance-tags.md

title: Create and edit instance tags headerTitle: Create and edit instance tags linkTitle: Configure instance tags description: Use YugabyteDB Anywhere to create and edit instance tags. menu: v2.18_yugabyte-platform: identifier: instance-tags parent: manage-deployments weight: 80 type: docs The instances created on a cloud provider can be assigned special metadata to help manage, bill, or audit the resources. On Amazon Web Services (AWS), they are referred to as . In the context of YugabyteDB Anywhere, these tags are known as user tags. You can define instance tags when you create a new universe, as well as modify or delete tags of an existing universe. These tags are represented by key-value pairs under Instance Configuration > User Tags on the Create Universe or Edit Universe page, as per the following illustration: You can define the tags in any order. Name is the only key that can have `templated` tags, so it can be made of different parts filled in at runtime to determine node and instance names, based on the following guidelines: The parts of the template should be enclosed between `${` and `}`. The reserved keywords that can be specified: `universe`, `instance-id`, `zone`, and `region`. Templated tag value must have `instance-id` at the minimum. Order of the parts of template does not matter. Now open the cloud provider's instances page. The following example uses AWS as the cloud provider, so you need to navigate to EC2 > Running Instances in the correct availability zone and search for instances that have `test-tags` in their name. You should see the following under Tags of those instances: `yb-server-type` and `launched-by` are reserved names. Now suppose you modified the existing user tags, as per the following illustration: The following changes have been made: `Billing` was modified. `MyInfo` was deleted. `NewInfo` was added. `Department` was not changed. Note that you cannot change the Name key field. Once again, you can confirm via the cloud provider list of instances that the tags have been updated correctly, as per the following illustration:
Project: YugabyteDB (App Definition and Development / Database)
File: cr-bucket-dedicated-code.md

title: crbucketdedicated_code.sql linkTitle: crbucketdedicated_code.sql headerTitle: crbucketdedicated_code.sql description: crbucketdedicated_code.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: cr-bucket-dedicated-code parent: analyzing-a-normal-distribution weight: 80 type: docs Save this script as `crbucketdedicated_code.sql`. ```plpgsql -- This approach implements the required "open-closed" interval -- bucket semantics directly. See the test -- -- where scaledval > lb and scaledval <= ub -- -- at the end. -- -- You might consider this to be the better approach, even though -- it means saying "No thank you" to the free gift of the built-in -- "width_bucket()" which -- acutally implements the wrong semantics -- for the present use case. Fixing it up with a trick might feel to be -- too offensive. -- -- This implementation of "bucket()" also passes the rigorous -- acceptance test. create or replace function bucket( val in double precision, lower_bound in double precision default 0, upper_bound in double precision default 1, noofvalues in int default 10) returns int language plpgsql as $body$ begin assert (val between lowerbound and upperbound), 'bucket():'|| ' val '||val|| ' must be between lowerbound '||lowerbound|| ' and upperbound '||upperbound; declare one constant double precision := 1; n constant double precision := noofvalues; scaled_val constant double precision := (val - lowerbound)/(upperbound - lower_bound); begin return ( with series as ( select generate_series::int as s from generateseries(1::int, noof_values)) , buckets as ( select s as bucket, -- (val = 0) is defined to be in (bucket = 1) case s when 1 then -one else ((s::double precision) - one)/n end as lb, (s::double precision)/n as ub from series) select bucket from buckets where scaledval > lb and scaledval <= ub ); end; end; $body$; ```
Project: RBAC Manager (Provisioning / Security & Compliance)
File: code-of-conduct.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Puppet (Provisioning / Automation & Configuration)
File: http_report.md

Report ====== This document describes the Puppet master's report endpoint and the schema for Report Format 12 in technical terms. Also see the . The `report` endpoint allows clients to send reports to the master via `http` or `https`. Once received by the master they are processed by the *report processors* configured to be triggered when a report is received. As an example, storing reports in PuppetDB is handled by one such report processor. Save The http(s) endpoint for sending reports to the master is: PUT /puppet/v3/report/:nodename?environment=:environment PUT `application/json` None The content of a report is typically generated by the Puppet Runtime and consists of a JSON serialization of `Puppet::Transaction::Report` object which in turn contains a structure of objects with of the following runtime types: `Puppet::Util::Log` `Puppet::Util::Metric` `Puppet::Resource::Status` `Puppet::Transaction::Event` This JSON serialization is compliant with the endpoint's report JSON schema. Example Here is an example of a PUT request. (Note that the content-length is not correct as the example is formatted for readability) PUT /puppet/v3/report/kermit.com?environment=production HTTP/1.0 Content-Type: application/json Content-Length: 1428 {"host"=>"kermit.com", "time"=>"2013-09-12T03:50:59.009301000+02:00", "configuration_version"=>1357986, "transaction_uuid"=>"df34516e-4050-402d-a166-05b03b940749", "code_id"=>null, "job_id"=>null, "catalog_uuid"=>"827a74c8-cf98-44da-9ff7-18c5e4bee41e", "catalog_format"=>1, "report_format"=>9, "puppet_version"=>"5.0.0", "status"=>"unchanged", "transaction_completed"=>true, "noop"=>false, "noop_pending"=>false, "environment"=>"test_environment", "logs"=> [{"level"=>"warning", "message"=>"log message", "source"=>"Puppet", "tags"=>["warning"], "time"=>"2013-09-12T03:50:59.009328000+02:00", "file"=>nil, "line"=>nil}], "metrics"=> {"resources"=> {"name"=>"resources", "label"=>"Resources", "values"=> [["total", "Total", 1], ["skipped", "Skipped", 0], ["failed", "Failed", 0], ["failedtorestart", "Failed to restart", 0], ["restarted", "Restarted", 0], ["changed", "Changed", 1], ["outofsync", "Out of sync", 0], ["scheduled", "Scheduled", 0]]}, "time"=> {"name"=>"time", "label"=>"Time", "values"=>[["timing", "Timing", 4], ["total", "Total", 4]]}, "changes"=> {"name"=>"changes", "label"=>"Changes", "values"=>[["total", "Total", 0]]}, "events"=> {"name"=>"events", "label"=>"Events", "values"=> [["total", "Total", 0], ["failure", "Failure", 0], ["success", "Success", 0]]}}, "resource_statuses"=> {"Notify[a resource]"=> {"title"=>"a resource", "file"=>nil, "line"=>nil, "resource"=>"Notify[a resource]", "resource_type"=>"Notify", "provider_used"=>nil, "containment_path"=>["Notify[a resource]"], "evaluation_time"=>nil, "tags"=>["notify"], "time"=>"2013-09-12T03:50:59.009238000+02:00", "failed"=>false, "changed"=>true, "outofsync"=>false, "skipped"=>false, "change_count"=>0, "outofsync_count"=>0, "events"=>[]}}, "cachedcatalogstatus"=> "not_used"} Schema The sent report objects must conform to
Project: KICS (Provisioning / Security & Compliance)
File: 3dd96caa-0b5f-4a85-b929-acfac4646cc2.md

title: Group With Privilege Escalation By Actions 'iam:AttachRolePolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3dd96caa-0b5f-4a85-b929-acfac4646cc2 Query name: Group With Privilege Escalation By Actions 'iam:AttachRolePolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:AttachRolePolicy' 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 "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:AttachRolePolicy", ] 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: Meshery (Provisioning / Automation & Configuration)
File: v0.6.165.md

layout: release date: 2023-10-29 tag: v0.6.165 Bump google.golang.org/grpc from 1.54.0 to 1.56.3 in /scripts/component_updater @dependabot (#9207) Fix links (kubernetes) in README.md @adityadeshpande09 (#9229) Add Section Component and Relationships @aabidsofi19 (#9231) [bug] update github.com/hashicorp/golang-lru/v2 @theBeginner86 (#9232) feat: Update several packages in Meshery @nebula-aac (#9137) [FIXED] mesheryctl app source type comparison bug is fixed @zakisk (#9230) [bug/CI] fix provider-lint @theBeginner86 (#9233) [bug/CI] fix provider-lint @theBeginner86 (#9233) Bump google.golang.org/grpc from 1.57.0 to 1.57.1 in /scripts/component_generation @dependabot (#9205) Bump sigs.k8s.io/controller-runtime from 0.15.1 to 0.16.3 @dependabot (#9223) Added New Script for Generating integration docs @aboobakersiddiqr63 (#9219) Thank you to our contributors for making this release possible: @MUzairS15, @aabidsofi19, @aboobakersiddiqr63, @adityadeshpande09, @dependabot, @dependabot[bot], @l5io, @leecalcote, @nebula-aac, @theBeginner86, @zakisk and l5io
Project: KICS (Provisioning / Security & Compliance)
File: 42e7dca3-8cce-4325-8df0-108888259136.md

title: BOM - AWS SNS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 42e7dca3-8cce-4325-8df0-108888259136 Query name: BOM - AWS SNS Platform: CloudFormation Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of SNS resources specified. Amazon Simple Notification Service (Amazon SNS) is a fully managed messaging service for both application-to-application (A2A) and application-to-person (A2P) communication.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" AWSTemplateFormatVersion: '2010-09-09' Description: '' Resources: SnsTopic: Type: 'AWS::SNS::Topic' Properties: Subscription: Endpoint: email@example.com Protocol: email TopicName: alarm-action KmsMasterKeyId: ididididid StartedTopicPolicy: Type: AWS::SNS::TopicPolicy Properties: Topics: !Ref SnsTopic PolicyDocument: Statement: Effect: Allow Principal: Service: events.amazonaws.com Action: sns:Publish Resource: "*" ``` ```json title="Positive test num. 2 - json file" hl_lines="5" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "", "Resources": { "SnsTopic": { "Type": "AWS::SNS::Topic", "Properties": { "Subscription": [ { "Endpoint": "email@example.com", "Protocol": "email" } ], "TopicName": "alarm-action", "KmsMasterKeyId": "ididididid" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myDistribution: Type: AWS::CloudFront::Distribution Properties: DistributionConfig: Enabled: true ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myDistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "Enabled": "true" } } } } } ```
Project: ClickHouse (App Definition and Development / Database)
File: 35_incomplete_implementation.md

name: Incomplete implementation about: Implementation of existing feature is not finished title: '' labels: unfinished code assignees: '' (you don't have to strictly follow this form) Describe the unexpected behaviour A clear and concise description of what works not as it is supposed to. How to reproduce Which ClickHouse server version to use Which interface to use, if matters Non-default settings, if any `CREATE TABLE` statements for all tables involved Sample data for all these tables, use if necessary Queries to run that lead to unexpected result Expected behavior A clear and concise description of what you expected to happen. Error message and/or stacktrace If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: mllib-classification-regression.md

layout: global title: Classification and Regression - RDD-based API displayTitle: Classification and Regression - 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. The `spark.mllib` package supports various methods for , [multiclass classification](http://en.wikipedia.org/wiki/Multiclass_classification), and . The table below outlines the supported algorithms for each type of problem. <table> <thead> <tr><th>Problem Type</th><th>Supported Methods</th></tr> </thead> <tbody> <tr> <td>Binary Classification</td><td>linear SVMs, logistic regression, decision trees, random forests, gradient-boosted trees, naive Bayes</td> </tr> <tr> <td>Multiclass Classification</td><td>logistic regression, decision trees, random forests, naive Bayes</td> </tr> <tr> <td>Regression</td><td>linear least squares, Lasso, ridge regression, decision trees, random forests, gradient-boosted trees, isotonic regression</td> </tr> </tbody> </table> More details for these methods can be found here: * *