cwielenb/CNCF-Dataset huggingface dataset:
Project: TDengine (App Definition and Development / Database)
File: 05-collectd.md

title: collectd writing sidebar_label: collectd description: This document describes how to integrate TDengine with collectd. import CollectD from "../14-reference/_collectd.mdx" collectd is a daemon used to collect system performance metric data. collectd provides various storage mechanisms to store different values. It periodically counts system performance statistics while the system is running and storing information. You can use this information to help identify current system performance bottlenecks and predict future system load. You can write the data collected by collectd to TDengine by simply modifying the configuration of collectd to the domain name (or IP address) and corresponding port of the server running taosAdapter. It can take full advantage of TDengine's efficient storage query performance and clustering capability for time-series data. Writing collectd data to the TDengine requires several preparations. The TDengine cluster is deployed and running properly taosAdapter is installed and running, please refer to for details collectd has been installed. Please refer to the to install collectd <CollectD /> Restart collectd ``` sudo systemctl restart collectd ``` Use the TDengine CLI to verify that collectd's data is written to TDengine and can read out correctly. ``` taos> show databases; name | ================================= information_schema | performance_schema | collectd | Query OK, 3 row(s) in set (0.003266s) taos> use collectd; Database changed. taos> show stables; name | ================================= load_1 | memory_value | df_value | load_2 | load_0 | interface_1 | irq_value | interface_0 | entropy_value | swap_value | Query OK, 10 row(s) in set (0.002236s) taos> select * from collectd.memory_value limit 10; ts | value | host | type_instance | type | ========================================================================================================================================================= 2022-04-20 09:27:45.459653462 | 54689792.000000000 | shuduo-1804 | buffered | memory | 2022-04-20 09:27:55.453168283 | 57212928.000000000 | shuduo-1804 | buffered | memory | 2022-04-20 09:28:05.453004291 | 57942016.000000000 | shuduo-1804 | buffered | memory | 2022-04-20 09:27:45.459653462 | 6381330432.000000000 | shuduo-1804 | free | memory | 2022-04-20 09:27:55.453168283 | 6357643264.000000000 | shuduo-1804 | free | memory | 2022-04-20 09:28:05.453004291 | 6349987840.000000000 | shuduo-1804 | free | memory | 2022-04-20 09:27:45.459653462 | 107040768.000000000 | shuduo-1804 | slab_recl | memory | 2022-04-20 09:27:55.453168283 | 107536384.000000000 | shuduo-1804 | slab_recl | memory | 2022-04-20 09:28:05.453004291 | 107634688.000000000 | shuduo-1804 | slab_recl | memory | 2022-04-20 09:27:45.459653462 | 309137408.000000000 | shuduo-1804 | used | memory | Query OK, 10 row(s) in set (0.010348s) ``` :::note TDengine will automatically create unique IDs for sub-table names by the rule. :::
Project: Dex (Provisioning / Security & Compliance)
File: SECURITY.md

To report a vulnerability, send an email to detailing the issue and steps to reproduce. The reporter(s) can expect a response within 48 hours acknowledging the issue was received. If a response is not received within 48 hours, please reach out to any maintainer directly to confirm receipt of the issue. Once a maintainer has confirmed the relevance of the report, a draft security advisory will be created on GitHub. The draft advisory will be used to discuss the issue with maintainers, the reporter(s). If the reporter(s) wishes to participate in this discussion, then provide reporter GitHub username(s) to be invited to the discussion. If the reporter(s) does not wish to participate directly in the discussion, then the reporter(s) can request to be updated regularly via email. If the vulnerability is accepted, a timeline for developing a patch, public disclosure, and patch release will be determined. The reporter(s) are expected to participate in the discussion of the timeline and abide by agreed upon dates for public disclosure.
Project: ThreatMapper (Provisioning / Security & Compliance)
File: database-export-import.md

title: Database Export and Import Export PostgreSQL data from one management console and import in another console Connect to old management console / database, run following commands to export ```shell mkdir deepfence_export cd deepfence_export docker run --net=host --rm=true --name=postgresql-backup \ -v "$(pwd)":/data:rw \ --entrypoint=/usr/local/bin/pg-export.sh \ -e POSTGRESDBHOST="127.0.0.1" \ -e POSTGRESDBPORT="5432" \ -e POSTGRESDBNAME=users \ -e POSTGRESDBUSERNAME="" \ -e POSTGRESDBPASSWORD="" \ deepfenceio/deepfence_backup:2.1.1 ``` Connect to new management console / database, run following commands to import ```shell docker run --net=host --rm=true --name=postgresql-restore \ -v "$(pwd)":/data:rw \ --entrypoint=/usr/local/bin/pg-import.sh \ -e POSTGRESDBHOST="127.0.0.1" \ -e POSTGRESDBPORT="5432" \ -e POSTGRESDBNAME=users \ -e POSTGRESDBUSERNAME="" \ -e POSTGRESDBPASSWORD="" \ deepfenceio/deepfence_backup:2.1.1 ``` Restart management console once Export Neo4J data from one management console and Import data in another console Step 1: Login to the host running the neo4j docker instance. Step 2: Docker exec into the neo4j instance using the below command: ```shell docker exec -it deepfence-neo4j /bin/bash ``` Step 3: Run the backup script from inside the neo4j docker instance as follows: ```shell /usr/local/bin/backup_neo4j.sh ``` This will create a backup file inside the container. The name of the file will be of the format: `neo4jbackup<YYYY-MM-DD_HOUR-MIN-SEC>` Also, the script will print the name of the file on the stdout. Step 4: Copy the neo4j backup file created above to host or any intermediate location Step 1: Copy the backup file from intermediate location to the target machine using scp (or similar commands) Step 2: Login to the target machine and copy the backup file in to the running neo4j container using below command: ```shell docker cp <BACKUP_FILE> deepfence-neo4j:/ ``` Step 3: Take a bash session of the running neo4j container using the below command: ```shell docker exec -it deepfence-neo4j /bin/bash ``` Step 4: Run the restore script from inside the neo4j docker instance as follows: ```shell /usr/local/bin/loadbackupneo4j.sh /<BACKUP_FILE> ``` e.g.: ```shell /usr/local/bin/loadbackupneo4j.sh /neo4jbackup2023-11-17_10-25-28 ``` The steps for kubernetes remains similar to the above. For Kubernetes, we will have to use `kubectl` utility to: Copy the file from and to the pod. Take a bash session of the pod
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.7-en.md

Do not auto-populate default SSL cipher suites, so that the configs are less bloated. Remove `will_msg` (not used) field from the client API. Fix `$queue` topic name error in management API return. Fix race condition which may cause `client.connected` and `client.disconnected` out of order. Fix quic listener default idle timeout's type.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: override.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: deploy-with-override namespace: examples spec: components: name: nginx-with-override type: webservice properties: image: nginx policies: name: topology-hangzhou-clusters type: topology properties: clusterLabelSelector: region: hangzhou name: topology-local type: topology properties: clusters: ["local"] namespace: examples-alternative name: override-nginx-legacy-image type: override properties: components: name: nginx-with-override properties: image: nginx:1.20 name: override-high-availability type: override properties: components: type: webservice traits: type: scaler properties: replicas: 3 workflow: steps: type: deploy name: deploy-local properties: policies: ["topology-local"] type: deploy name: deploy-hangzhou properties: policies: ["topology-hangzhou-clusters", "override-nginx-legacy-image", "override-high-availability"] ``` ```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: advance-override namespace: examples spec: components: name: nginx-advance-override-legacy type: webservice properties: image: nginx:1.20 name: nginx-advance-override-latest type: webservice properties: image: nginx policies: name: topology-hangzhou-clusters type: topology properties: clusterLabelSelector: region: hangzhou name: topology-local type: topology properties: clusters: ["local"] namespace: examples-alternative name: override-nginx-legacy type: override properties: selector: ["nginx-advance-override-legacy"] name: override-nginx-latest type: override properties: selector: ["nginx-advance-override-latest", "nginx-advance-override-stable"] components: name: nginx-advance-override-stable type: webservice properties: image: nginx:stable workflow: steps: type: deploy name: deploy-local properties: policies: ["topology-local", "override-nginx-legacy"] type: deploy name: deploy-hangzhou properties: policies: ["topology-hangzhou-clusters", "override-nginx-latest"] ```
Project: YugabyteDB (App Definition and Development / Database)
File: analysis-queries-sql.md

title: analysis-queries.sql linkTitle: analysis-queries.sql headerTitle: SQL script to perform linear regression analysis on the COVIDcast data description: SQL script to perform linear regression analysis using regrr2(), regrslope(), regr_intercept() on the COVIDcast data menu: v2.18: identifier: analysis-queries-sql parent: analysis-scripts weight: 10 type: docs Save this script as "analysis-queries.sql" ```plpgsql create or replace view covidcastfbsurveyresultsv as select survey_date, state, maskwearingpct, cmntysymptomspct as symptoms_pct from covidcastfbsurvey_results; \o analysis-results/analysis-queries.txt \t on select 'Symptoms by state for survey date = 2020-10-21.'; \t off select round(maskwearingpct) as "% wearing mask", round(symptoms_pct) as "% with symptoms", state from covidcastfbsurveyresultsv where surveydate = todate('2020-10-21', 'yyyy-mm-dd') order by 1; \t on select 'Symptoms by state, overall average.'; \t off select round(avg(maskwearingpct)) as "% wearing mask", round(avg(symptoms_pct)) as "% with symptoms", state from covidcastfbsurveyresultsv group by state order by 1; \t on select 'Daily regression analysis report.'; \t off with a as ( select survey_date, avg (maskwearingpct) as maskwearingpct, avg (symptomspct) as symptomspct, regrr2 (symptomspct, maskwearingpct) as r2, regrslope (symptomspct, maskwearingpct) as s, regrintercept(symptomspct, maskwearingpct) as i from covidcastfbsurveyresultsv group by survey_date) select tochar(surveydate, 'mm/dd') as survey_date, tochar(maskwearingpct, '90') as maskwearing_pct, tochar(symptomspct, '90') as symptoms_pct, to_char(r2, '0.99') as r2, to_char(s, '90.9') as s, to_char(i, '990.9') as i from a order by survey_date; \t on select 'Regression analysis report for survey date = 2020-10-21.'; \t off with a as ( select max(surveydate) as surveydate, regrslope (symptomspct, maskwearingpct) as s, regrintercept(symptomspct, maskwearingpct) as i from covidcastfbsurveyresultsv where surveydate = todate('2020-10-21', 'yyyy-mm-dd')) select tochar(surveydate, 'mm/dd') as survey_date, to_char(s, '90.9') as s, to_char(i, '990.9') as i from a; with a as ( select regrr2 (symptomspct, maskwearingpct) as r2 from covidcastfbsurveyresultsv group by survey_date) select to_char(avg(r2), '0.99') as "avg(R-squared)" from a; \o \o analysis-results/2020-10-21-mask-symptoms.csv \t on select round(maskwearingpct)::text||','||round(symptoms_pct)::text from covidcastfbsurveyresultsv where surveydate = todate('2020-10-21', 'yyyy-mm-dd') order by 1; \t off \o ```
Project: CloudTTY (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

What type of PR is this? <!-- Add one of the following kinds: /kind api-change /kind bug /kind cleanup /kind deprecation /kind design /kind documentation /kind failing-test /kind feature /kind flake --> What this PR does / why we need it: Which issue(s) this PR fixes: Fixes # Special notes for your reviewer: Does this PR introduce a user-facing change?: <!-- If no, just write "NONE" in the release-note block below. If yes, a release note is required. --> ```release-note ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-volume-unmount.1.md

% podman-volume-unmount 1 podman\-volume\-unmount - Unmount a volume podman volume unmount volume [...] podman volume umount volume [...] Unmounts the specified volume, if there are no other containers using it. Volume storage increments a mount counter each time a volume is mounted. When a volume is unmounted, the mount counter is decremented, and the volume's filesystem is physically unmounted only when the mount counter reaches zero indicating no other processes are using the mount. Unmount volume with a given ID: ``` podman volume unmount volumeID ``` Unmount multiple volumes with given IDs: ``` podman volume unmount volumeID1 volumeID2 volumeID3 ``` , ,
Project: StarRocks (App Definition and Development / Database)
File: right.md

displayed_sidebar: "English" This function returns a specified length of characters from the right side of a given string. Length unit: utf8 character. Note: This function is also named as . ```SQL VARCHAR right(VARCHAR str,INT len) ``` ```SQL MySQL > select right("Hello starrocks",9); +--+ | right('Hello starrocks', 9) | +--+ | starrocks | +--+ ``` RIGHT
Project: LinuxKit (Provisioning / Automation & Configuration)
File: ISSUE_TEMPLATE.md

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information. For more information about reporting issues, see https://github.com/linuxkit/linuxkit/blob/master/CONTRIBUTING.md#reporting-other-issues BUG REPORT INFORMATION Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST --> Description <!-- Briefly describe the problem you are having in a few paragraphs. --> Steps to reproduce the issue: Describe the results you received: Describe the results you expected: Additional information you deem important (e.g. issue happens only occasionally):
Project: KICS (Provisioning / Security & Compliance)
File: 8010e17a-00e9-4635-a692-90d6bcec68bd.md

title: Default Security Groups With Unrestricted Traffic hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8010e17a-00e9-4635-a692-90d6bcec68bd Query name: Default Security Groups With Unrestricted Traffic Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Check if default security group does not restrict all inbound and outbound traffic.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="48 17 83 61 30" name: example ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 awssecretkey: SECRET awsaccesskey: ACCESS rules: proto: all from_port: 10050 # this value is ignored to_port: 10050 # this value is ignored cidr_ip: 0.0.0.0/0 name: example2 ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 awssecretkey: SECRET awsaccesskey: ACCESS rules_egress: proto: tcp from_port: 80 to_port: 80 cidr_ip: 0.0.0.0/0 group_name: example-other group_desc: other example EC2 group name: example3 ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 awssecretkey: SECRET awsaccesskey: ACCESS rules: proto: all from_port: 10050 # this value is ignored to_port: 10050 # this value is ignored cidr_ipv6: ::/0 name: example4 ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 awssecretkey: SECRET awsaccesskey: ACCESS rules_egress: proto: tcp from_port: 80 to_port: 80 cidr_ipv6: ::/0 group_name: example-other group_desc: other example EC2 group name: example5 ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 awssecretkey: SECRET awsaccesskey: ACCESS rules: proto: tcp ports: 22 group_name: example-vpn rules_egress: proto: tcp from_port: 80 to_port: 80 cidr_ipv6: ::/0 group_name: example-other group_desc: other example EC2 group ``` ```yaml title="Negative test num. 1 - yaml file" name: example ec2 group amazon.aws.ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1 awssecretkey: SECRET awsaccesskey: ACCESS rules: proto: all from_port: 10050 # this value is ignored to_port: 10050 # this value is ignored cidr_ip: 10.1.0.0/16 cidr_ipv6: 64:ff9b::/96 rules_egress: proto: tcp from_port: 80 to_port: 80 cidr_ip: 10.1.0.0/16 cidr_ipv6: 64:ff9b::/96 group_name: example-other group_desc: other example EC2 group ```
Project: Flink (App Definition and Development / Streaming & Messaging)
File: join.md

title: "Join" weight: 4 type: docs <!-- 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. --> `JOIN` is used to combine rows from two relations based on join condition. Hive Dialect supports the following syntax for joining tables: ```sql join_table: tablereference [ INNER ] JOIN tablefactor [ join_condition ] | tablereference { LEFT | RIGHT | FULL } [ OUTER ] JOIN tablereference join_condition | tablereference LEFT SEMI JOIN tablereference [ ON expression ] | tablereference CROSS JOIN tablereference [ join_condition ] table_reference: table_factor | join_table table_factor: tbl_name [ alias ] | table_subquery alias | ( table_references ) join_condition: { ON expression | USING ( colName [, ...] ) } ``` `INNER JOIN` returns the rows matched in both join sides. `INNER JOIN` is the default join type. `LEFT JOIN` returns all the rows from the left join side and the matched values from the right join side. It will concat the values from both sides. If there's no match in right join side, it will append `NULL` value. `LEFT JOIN` is equivalent to `LEFT OUTER JOIN`. `RIGHT JOIN` returns all the rows from the right join side and the matched values from the left join side. It will concat the values from both sides. If there's no match in left join side, it will append `NULL` value. `RIGHT JOIN` is equivalent to `RIGHT OUTER JOIN`. `FULL JOIN` returns all the rows from both join sides. It will concat the values from both sides. If there's one side does not match the row, it will append `NULL` value. `FULL JOIN` is equivalent to `FULL OUTER JOIN`. `LEFT SMEI JOIN` returns the rows from the left join side that have matching in right join side. It won't concat the values from the right side. `CROSS JOIN` returns the Cartesian product of two join sides. ```sql -- INNER JOIN SELECT t1.x FROM t1 INNER JOIN t2 USING (x); SELECT t1.x FROM t1 INNER JOIN t2 ON t1.x = t2.x; -- LEFT JOIN SELECT t1.x FROM t1 LEFT JOIN t2 USING (x); SELECT t1.x FROM t1 LEFT OUTER JOIN t2 ON t1.x = t2.x; -- RIGHT JOIN SELECT t1.x FROM t1 RIGHT JOIN t2 USING (x); SELECT t1.x FROM t1 RIGHT OUTER JOIN t2 ON t1.x = t2.x; -- FULL JOIN SELECT t1.x FROM t1 FULL JOIN t2 USING (x); SELECT t1.x FROM t1 FULL OUTER JOIN t2 ON t1.x = t2.x; -- LEFT SEMI JOIN SELECT t1.x FROM t1 LEFT SEMI JOIN t2 ON t1.x = t2.x; -- CROSS JOIN SELECT t1.x FROM t1 CROSS JOIN t2 USING (x); ```
Project: StarRocks (App Definition and Development / Database)
File: to_binary.md

displayed_sidebar: "English" Converts a VARCHAR string to a binary value based on the specified binary format (`binarytype`) of the input string. The following binary formats are supported: `hex`, `encode64`, and `utf8`. If no `binarytype` is specified, `hex` is the default. ```Haskell tobinary(str[, binarytype]) ``` `str`: the string to convert, required. It must be a VARCHAR string. `binary_type`: the binary format for conversion, optional. `hex`(default): `tobinary` assumes the input string is a hex string in which all characters are in '0123456789abcdef'. If the input string is not valid, an empty binary is returned (exceptions will not be thrown). `tobinary` will convert the input string into binary directly. For example, `"abab"` will be converted to `x'abab'`. The input string is not case-sensitive. `encode64`: `tobinary` assumes the input string is a base64-encoded string . If the input string is not valid, an empty binary is returned (exceptions will not be thrown). `tobinary` will decode the base64-encoded string as the binary result. For example, `"YWJhYg=="` will be converted to `x'abab'`. `utf8`: `to_binary` converts the input string as a binary value without any transformation. Returns a VARCHAR value. The following examples assume that the `--binary-as-hex` option is enabled when you access StarRocks from your MySQL client. This way, binary data is displayed using hexadecimal notation. ```Plain mysql> select to_binary('ABAB', 'hex'); +-+ | to_binary('ABAB', 'hex') | +-+ | 0xABAB | +-+ 1 row in set (0.01 sec) mysql> select to_binary('U1RBUlJPQ0tT', 'encode64'); ++ | to_binary('U1RBUlJPQ0tT', 'encode64') | ++ | 0x53544152524F434B53 | ++ 1 row in set (0.00 sec) mysql> select to_binary('STARROCKS', 'utf8'); +-+ | to_binary('STARROCKS', 'utf8') | +-+ | 0x53544152524F434B53 | +-+ 1 row in set (0.00 sec) -- The input string does not match the binary format and an empty binary is returned. mysql> select to_binary('U1RBUlJPQ0tT', 'hex'); +--+ | to_binary('U1RBUlJPQ0tT', 'hex') | +--+ | 0x | +--+ 1 row in set (0.00 sec) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.126.md

layout: release date: 2023-08-17 tag: v0.6.126 [Notification Center] Add Support for Meshmap and little Ui changes @aabidsofi19 (#8510) [UI] Send toaster informational notification upon save of design and send to notification center @Chadha93 (#8509) Revert "[UI] Add Qanelas Soft as Global Font" @leecalcote (#8504) Thank you to our contributors for making this release possible: @Chadha93, @aabidsofi19, @l5io, @leecalcote and l5io