cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: ericsson.md

title: "Ericsson" icon: /images/logos/powered-by/ericsson.png hasLink: "https://www.ericsson.com/en" <!-- 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: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.1.0.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | move up to Jackson 1.8.8 | Minor | util | Steve Loughran | Enis Soztutar | | | Binary tarball does not preserve platform info for native builds, and RPMs fail to provide needed symlinks for libhadoop.so | Blocker | build | Matt Foley | Matt Foley | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Improve handling of fetch failures when a tasktracker is not responding on HTTP | Major | jobtracker | Todd Lipcon | Todd Lipcon | | | Port missing new API mapreduce lib classes to 1.x | Major | client | Tom White | Tom White | | | Support setting the run-as user in unsecure mode | Major | security | Devaraj Das | Jitendra Nath Pandey | | | NamenodeMXBean does not account for svn revision in the version information | Minor | . | Hitesh Shah | Hitesh Shah | | | Create hadoop-client and hadoop-minicluster artifacts for downstream projects | Critical | build | Alejandro Abdelnur | Alejandro Abdelnur | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | TaskTracker Out of Memory because of distributed cache | Major | mrv1 | Ahmed Radwan | yunjiong zhao | | | Port HADOOP-5203 to branch-1, build version comparison is too restrictive | Major | . | Giridharan Kesavan | Matt Foley | | | Deadlock in class init. | Blocker | security, util | Kihwal Lee | Daryn Sharp | | | Upper case in hostname part of the principals doesn't work with kerberos. | Major | . | Jitendra Nath Pandey | Jitendra Nath Pandey | | | hadoop-config.sh spews error message when HADOOP\HOME\WARN\SUPPRESS is set to true and HADOOP\HOME is present | Minor | scripts | Roman Shaposhnik | Roman Shaposhnik | | | 0.20: Allow block reports to proceed without holding FSDataset lock | Critical | datanode | Todd Lipcon | Todd Lipcon | | | Hadoop Metrics2 should emit Float.MAX\VALUE (instead of Double.MAX\VALUE) to avoid making Ganglia's gmetad core | Major | metrics | Varun Kapoor | Varun Kapoor |
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: high-availability.md

title: High Availability for Redis description: High availability for a Redis cluster keywords: [redis, high availability] sidebar_position: 1 KubeBlocks integrates to realize high availability and adopts Noop as the switch policy. Redis Sentinel is the high availability solution for a Redis Replication Cluster, which is recommended by Redis and is also the main-stream solution in the community. In the RedisReplication Cluster provided by KubeBlocks, Sentinel is deployed as an independent component. Install KubeBlocks: You can install KubeBlocks by or by . . Check the Switch Policy and the role probe. Check whether the switch policy is `Noop`. ```bash kubectl get cluster redis-cluster -o yaml > spec: componentSpecs: name: redis componentDefRef: redis switchPolicy: type: Noop ``` Check whether the following role probe parameters exist to verify the role probe is enabled. ```bash kubectl get cd redis -o yaml > probes: roleProbe: failureThreshold: 3 periodSeconds: 2 timeoutSeconds: 1 ``` View the initial status of the Redis cluster. ```bash kbcli cluster describe redis-cluster ``` Currently, `redis-cluster-redis-0` is the primary pod and `redis-cluster-redis-1` is the secondary pod. Simulate a primary pod exception. ```bash kubectl exec -it redis-cluster-redis-0 -- bash root@redis-redis-0:/# redis-cli debug sleep 30 ``` Open the Redis Sentinel log to view the failover. ```bash kubectl logs redis-cluster-redis-sentinel-0 ``` In the logs, we can view when a high-availability switch occurs. ```bash 1:X 18 Apr 2023 06:13:17.072 # +switch-master redis-cluster-redis-sentinel redis-cluster-redis-0.redis-cluster-redis-headless.default.svc 6379 redis-cluster-redis-1.redis-cluster-redis-headless.default.svc 6379 1:X 18 Apr 2023 06:13:17.074 * +slave slave redis-cluster-redis-0.redis-cluster-redis-headless.default.svc:6379 redis-cluster-redis-0.redis-cluster-redis-headless.default.svc 6379 @ redis-cluster-redis-sentinel redis-cluster-redis-1.redis-cluster-redis-headless.default.svc 6379 1:X 18 Apr 2023 06:13:17.077 * Sentinel new configuration saved on disk ``` Connect to the Redis cluster to view the primary pod information after the exception simulation. ```bash kbcli cluster connect redis-cluster ``` ```bash 127.0.0.1:6379> info replication ``` From the output, `redis-cluster-redis-1` has been assigned as the primary's pod. Describe the cluster and check the instance role. ```bash kbcli cluster describe redis-cluster ``` After the failover, `redis-cluster-redis-0` becomes the secondary pod and `redis-cluster-redis-1` becomes the primary pod.
Project: KICS (Provisioning / Security & Compliance)
File: f30ee711-0082-4480-85ab-31d922d9a2b2.md

title: Global Schemes Uses HTTP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f30ee711-0082-4480-85ab-31d922d9a2b2 Query name: Global Schemes Uses HTTP Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Global Schemes should use 'https' protocol instead of 'http'<br> ```json title="Positive test num. 1 - json file" hl_lines="8" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "http" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="6" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: http paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response ```
Project: StarRocks (App Definition and Development / Database)
File: dayname.md

displayed_sidebar: "English" Returns the day corresponding to a date. The `date` parameter must be of the DATE or DATETIME type. ```Haskell VARCHAR DAYNAME(date) ``` ```Plain Text MySQL > select dayname('2007-02-03 00:00:00'); +--+ | dayname('2007-02-03 00:00:00') | +--+ | Saturday | +--+ ``` DAYNAME
Project: StarRocks (App Definition and Development / Database)
File: ADMIN_REPAIR.md

displayed_sidebar: "English" This statement is used to try and fix the specified tables or partitions first. :::tip This operation requires the SYSTEM-level OPERATE privilege. You can follow the instructions in to grant this privilege. ::: ```sql ADMIN REPAIR TABLE table_name[ PARTITION (p1,...)] ``` Note: This statement only means that the system attempts to repair sharding replicas of specified tables or partitions with high priority without the guarantee that the repair will be successful. Users can view the repair status through ADMIN SHOW REPLICA STATUS command. The default timeout is 14400 seconds (4 hours). Timeout means the system will not repair sharding replicas of specified tables or partitions with high priority. In case of timeout, the command needs to be used again for the intended settings. Attempt to repair specified tables ```sql ADMIN REPAIR TABLE tbl1; ``` Attempt to fix specified partition ```sql ADMIN REPAIR TABLE tbl1 PARTITION (p1, p2); ```
Project: YugabyteDB (App Definition and Development / Database)
File: type_number.md

title: Non-integer data types (FLOAT, DOUBLE, and DECIMAL) [YCQL] headerTitle: Non-integer linkTitle: Non-integer description: Use the non-integer (floating-point and fixed-point) data types to specify non-integer numbers. menu: v2.18: parent: api-cassandra weight: 1430 type: docs Use the non-integer (floating-point and fixed-point) data types to specify non-integer numbers. Different floating point data types represent different precision numbers. Data type | Description | Decimal precision | |--|--| `FLOAT` | Inexact 32-bit floating point number | 7 | `DOUBLE` | Inexact 64-bit floating point number | 15 | `DECIMAL` | Arbitrary-precision number | no upper-bound | ``` type_specification ::= { FLOAT | DOUBLE | DOUBLE PRECISION | DECIMAL } nonintegerfloatingpointliteral ::= nonintegerfixedpointliteral | "NaN" | "Infinity" | "-Infinity" nonintegerfixedpointliteral ::= [ + | - ] { digit [ digit ...] '.' [ digit ...] | '.' digit [ digit ...] } ``` Where Columns of type `FLOAT`, `DOUBLE`, `DOUBLE PRECISION`, or `DECIMAL` can be part of the `PRIMARY KEY`. `DOUBLE` and `DOUBLE PRECISION` are aliases. `nonintegerfloatingpointliteral` is used for values of `FLOAT`, `DOUBLE` and `DOUBLE PRECISION` types. `nonintegerfixedpointliteral` is used for values of `DECIMAL` type. Values of different floating-point and fixed-point data types are comparable and convertible to one another. Conversion from floating-point types into `DECIMAL` will raise an error for the special values `NaN`, `Infinity`, and `-Infinity`. Values of non-integer numeric data types are neither comparable nor convertible to integer although integers are convertible to them. The ordering for special floating-point values is defined as (in ascending order): `-Infinity`, all negative values in order, all positive values in order, `Infinity`, and `NaN`. ```sql ycqlsh:example> CREATE TABLE sensordata (sensorid INT PRIMARY KEY, floatval FLOAT, dblval DOUBLE, dec_val DECIMAL); ``` ```sql ycqlsh:example> INSERT INTO sensordata(sensorid, floatval, dblval, dec_val) VALUES (1, 321.0456789, 321.0456789, 321.0456789); ``` Integers literals can also be used (Using upsert semantics to update a non-existent row). ```sql ycqlsh:example> UPDATE sensordata SET floatval = 1, dblval = 1, decval = 1 WHERE sensor_id = 2; ``` ```sql ycqlsh:example> SELECT * FROM sensor_data; ``` ``` sensorid | floatval | dblval | decval --+--+--+- 2 | 1 | 1 | 1 1 | 321.04568 | 321.04568 | 321.0456789 ```
Project: YugabyteDB (App Definition and Development / Database)
File: download-the-covidcast-data.md

title: Download the COVIDcast data linkTitle: Download the COVIDcast data headerTitle: Finding and downloading the COVIDcast data description: How to download data from Carnegie Mellon's COVIDcast project for linear regression analysis using YSQL menu: stable: identifier: download-the-covidcast-data parent: covid-data-case-study weight: 10 type: indexpage Simply follow these step-by-step instructions: Create a directory on the computer where you run `ysqlsh` to hold the files for this case study. Call it, for example, "covid-data-case-study". Go to the and select the Export Data tab. That will bring you to this screen: In Section #1, Select Signal, select Facebook Survey Results in the Data Sources list and select People Wearing Masks in the Signals list. In Section #2, Specify Parameters, choose the range that interests you for Date Range (This case study used "2020-09-13 - 2020-11-01".) Select States for the Geographic Level. In Section #3, "Get Data hit the CSV button. Then repeat, leaving all choices unchanged except for the choice in the Signals list. Select COVID-Like Symptoms here. Then repeat again, again leaving all choices unchanged except for the choice in the Signals list. Select COVID-Like Symptoms in Community here. This will give you three files with names like these: ``` covidcast-fb-survey-smoothedwearingmask-2020-09-13-to-2020-11-01.csv covidcast-fb-survey-smoothed_cli-2020-09-13-to-2020-11-01.csv covidcast-fb-survey-smoothedhhcmnty_cli-2020-09-13-to-2020-11-01.csv ``` The naming convention is obvious. The names will reflect your choice of date range. Create a directory called "csv-files" on your "covid-data-case-study" directory and move the `.csv` files to this from your "downloads" directory. Because you will not edit these files, you might like to make them all read-only to be sure that you don't make any accidental changes when you use a text editor or a spreadsheet app to inspect them.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_target_http_proxy.md

+++ title = "googlecomputetargethttpproxy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputetargethttpproxy" identifier = "inspec/resources/gcp/googlecomputetargethttpproxy.md googlecomputetargethttpproxy resource" parent = "inspec/resources/gcp" +++ A `googlecomputetargethttpproxy` is used to test a Google TargetHttpProxy resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputetargethttpproxy(project: 'chef-gcp-inspec', name: 'inspec-gcp-http-proxy') do it { should exist } its('description') { should eq 'A HTTP proxy' } its('url_map') { should match /\/inspec-gcp-url-map$/ } end describe googlecomputetargethttpproxy(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlecomputetargethttpproxy` resource: `creation_timestamp` : Creation timestamp in RFC3339 text format. `description` : An optional description of this resource. `id` : The unique identifier for the resource. `name` : Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. `url_map` : A reference to the UrlMap resource that defines the mapping from URL to the BackendService. Ensure the is enabled for the current project.
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV046.md

vid: KHV046 title: Exposed Kubelet Cmdline categories: [Information Disclosure] severity: high When the Kubelet is run in debug mode, a Pod running in the cluster is able to access the Kubelet's `debug/pprof/cmdline` endpoint and examine how the kubelet was executed on the node, specifically the command line flags that were used, which tells the attacker about what capabilities the kubelet has which might be exploited. Disable `--enable-debugging-handlers` kubelet flag.
Project: Curiefense (Provisioning / Security & Compliance)
File: SECURITY.md

The Curiefense maintainers are committed to protecting the security and integrity of this project. Information you submit under this process is only used to mitigate or remediate vulnerabilities. If you believe you have found a security vulnerability, notify us as soon as possible after you discover it. Please submit your report to us by email at . You can submit reports anonymously. We do not support PGP-encrypted emails at this time. In your report: Write in English. Describe the vulnerability, where it was discovered, and the potential impact of exploitation. Offer a detailed description of the steps to reproduce the vulnerability (proof of concept scripts or screenshots are helpful). These should be benign, non-destructive, proofs of concept so we can triage your report quickly and accurately. Do not submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with best practice, for example missing security headers, or a high volume of low-quality reports (for example, from an automated scanner). Do not communicate any vulnerabilities or associated details other than by means described in the published `SECURITY.md` file. Do not expect or demand financial compensation for your research and testing to disclose vulnerabilities. When you choose to share your contact information with us, we commit to communicating with you as openly and as quickly as possible. Within 3 business days, we will acknowledge that your report has been received. To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution. We will prioritize fixing the vulnerability by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. Youre welcome to ask the status but please no more than once every 14 days. That way, our teams can focus on the remediation. We will do our best to maintain an open dialogue with you to discuss issues and will work with you to determine whether and how the flaw reported will be made public. We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately. Add your Name/Handle on curiefense.io <br> <br><br> <small> Adapted from <a href="https://github.com/cds-snc/covid-alert-documentation">COVID Alert documentation</a> </small>
Project: KICS (Provisioning / Security & Compliance)
File: 6b5b0313-771b-4319-ad7a-122ee78700ef.md

title: Serverless API Endpoint Config Not Private hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6b5b0313-771b-4319-ad7a-122ee78700ef Query name: Serverless API Endpoint Config Not Private Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: AWS Serverless API should set API Endpoint Config type to 'PRIVATE'. This way, it's not exposed to the public internet<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi: Type: AWS::Serverless::Api Properties: StageName: prod TracingEnabled: true CacheClusterEnabled: true ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi2: Type: AWS::Serverless::Api Properties: StageName: prod TracingEnabled: true CacheClusterEnabled: true EndpointConfiguration: VpcEndpointIds: !Ref ApiGatewayVPCEndpoint ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="12" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi3: Type: AWS::Serverless::Api Properties: StageName: prod TracingEnabled: true CacheClusterEnabled: true EndpointConfiguration: Types: EDGE ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: ApiGatewayApi4: Type: AWS::Serverless::Api Properties: StageName: prod TracingEnabled: true CacheClusterEnabled: true EndpointConfiguration: Types: PRIVATE ```
Project: KICS (Provisioning / Security & Compliance)
File: 663062e9-473d-4e87-99bc-6f3684b3df40.md

title: SQL Server Predictable Admin Account Name hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 663062e9-473d-4e87-99bc-6f3684b3df40 Query name: SQL Server Predictable Admin Account Name Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Azure SQL Server's Admin account login must avoid using names like 'Admin', that are too predictable, which means the attribute 'admin_username' must be set to a name that is not easy to predict<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="21 14 7" name: Create (or update) SQL Server1 azurermsqlserver: resource_group: myResourceGroup name: server_name1 location: westus admin_username: "" admin_password: Testpasswordxyz12! name: Create (or update) SQL Server2 azurermsqlserver: resource_group: myResourceGroup name: server_name2 location: westus admin_username: admin_password: Testpasswordxyz12! name: Create (or update) SQL Server3 azurermsqlserver: resource_group: myResourceGroup name: server_name3 location: westus admin_username: admin admin_password: Testpasswordxyz12! ``` ```yaml title="Negative test num. 1 - yaml file" name: Create (or update) SQL Server azurermsqlserver: resource_group: myResourceGroup name: server_name location: westus admin_username: mylogin admin_password: Testpasswordxyz12! ```
Project: KubeLinter (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Thank you for your interest in contributing to KubeLinter! We welcome code contributions from the community. Anyone is welcome to create a pull request, and request a review from any of the project maintainers. By default, your pull requests should be linked to an . If you're addressing an existing issue, great! If your change is unrelated to an existing issue, please file an issue first, and make sure you get buy-in from the maintainers. However, if your change is relatively trivial (say, a documentation update, or a simple bugfix), feel free to directly create a pull request, and explain your changes in the pull request. If you find a bug, or have a request for a feature, please .
Project: YDB (App Definition and Development / Database)
File: balancing-prefer-location.md

{% include %} Below are examples of the code for setting the "prefer the availability zone" balancing algorithm option in different {{ ydb-short-name }} SDKs. {% list tabs %} Go (native) ```go package main import ( "context" "os" "github.com/ydb-platform/ydb-go-sdk/v3" "github.com/ydb-platform/ydb-go-sdk/v3/balancers" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() db, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithBalancer( balancers.PreferLocations( balancers.RandomChoice(), "a", "b", ), ), ) if err != nil { panic(err) } defer db.Close(ctx) ... } ``` Go (database/sql) Client load balancing in the {{ ydb-short-name }} `database/sql` driver is performed only when establishing a new connection (in `database/sql` terms), which is a {{ ydb-short-name }} session on a specific node. Once the session is created, all queries in this session are passed to the node where the session was created. Queries in the same {{ ydb-short-name }} session are not balanced between different {{ ydb-short-name }} nodes. Example of the code for setting the "prefer the availability zone": ```go package main import ( "context" "database/sql" "os" "github.com/ydb-platform/ydb-go-sdk/v3" "github.com/ydb-platform/ydb-go-sdk/v3/balancers" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() nativeDriver, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithBalancer( balancers.PreferLocations( balancers.RandomChoice(), "a", "b", ), ), ) if err != nil { panic(err) } defer nativeDriver.Close(ctx) connector, err := ydb.Connector(nativeDriver) if err != nil { panic(err) } db := sql.OpenDB(connector) defer db.Close() ... } ``` {% endlist %}