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

Fixed windows (sometimes called tumbling windows) are defined by a static window size, e.g. 30 second windows, one minute windows, etc. They are generally aligned, i.e. every window applies across all the data for the corresponding period of time. It has a fixed size measured in time and does not overlap. The element which belongs to one window will not belong to any other tumbling window. For example, a window size of 20 seconds will include all entities of the stream which came in a certain 20-second interval. To enable Fixed window, we use `fixed` under `window` section. ```yaml vertices: name: my-udf udf: groupBy: window: fixed: length: duration ``` NOTE: A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "1.5h" or "2h45m". Valid time units are "ns", "us" (or "s"), "ms", "s", "m", "h". The `length` is the window size of the fixed window. A 60-second window size can be defined as following. ```yaml vertices: name: my-udf udf: groupBy: window: fixed: length: 60s ``` The yaml snippet above contains an example spec of a reduce vertex that uses fixed window aggregation. As we can see, the length of the window is 60s. This means only one window will be active at any point in time. It is also possible to have multiple inactive and non-empty windows (based on out-of-order arrival of elements). The window boundaries for the first window (post bootstrap) are determined by rounding down from `time.now()` to the nearest multiple of `length` of the window. So considering the above example, if the `time.now()` corresponds to `2031-09-29T18:46:30Z`, then the start-time of the window will be adjusted to `2031-09-29T18:46:00Z` and the end-time is set accordingly to `2031-09-29T18:47:00Z`. Windows are left inclusive and right exclusive which means an element with event time (considering event time characteristic) of `2031-09-29T18:47:00Z` will belong to the window with boundaries `[2031-09-29T18:47:00Z, 2031-09-29T18:48:00Z)` It is important to note that because of this property, for a constant throughput, the first window may contain fewer elements than other windows. Check the links below to see the UDF examples for different languages. Reduce can be enabled on streaming mode to stream messages or forward partial responses to the next vertex. This is useful for custom triggering, where we want to forward responses to the next vertex quickly, even before the fixed window closes. The close-of-book and a final triggering will still happen even if partial results have been emitted. To enable reduce streaming, set the `streaming` flag to `true` in the fixed window configuration. ```yaml vertices: name: my-udf udf: groupBy: window: fixed: length: duration streaming: true # set streaming to true to enable reduce streamer ``` Note: UDFs should use the ReduceStreamer functionality in the SDKs to use this feature. Check the links below to see the UDF examples in streaming mode for different languages.
Project: ClickHouse (App Definition and Development / Database)
File: theilsu.md

slug: /en/sql-reference/aggregate-functions/reference/theilsu sidebar_position: 353 The `theilsU` function calculates the , a value that measures the association between two columns in a table. Its values range from 1.0 (100% negative association, or perfect inversion) to +1.0 (100% positive association, or perfect agreement). A value of 0.0 indicates the absence of association. Syntax ``` sql theilsU(column1, column2) ``` Arguments `column1` and `column2` are the columns to be compared Returned value a value between -1 and 1 Return type is always . Example The following two columns being compared below have a small association with each other, so the value of `theilsU` is negative: ``` sql SELECT theilsU(a ,b) FROM ( SELECT number % 10 AS a, number % 4 AS b FROM numbers(150) ); ``` Result: ```response theilsU(a, b) -0.30195720557678846 ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: MAINTAINERS.md

describes governance guidelines and maintainer responsibilities. | Maintainer | GitHub ID | Affiliation | |-|--|| | Nash Tsai | | | | L.Dongming | | | | Ziang Guo | | | | Songlu Tsai | | | | Wei Cao | | | | Xueqiang Wu | | |
Project: CockroachDB (App Definition and Development / Database)
File: hotranges-other.md

<a name="cockroach.server.serverpb.HotRangesResponse.HotRangesByNodeIdEntry"></a> | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | key | | | | | | value | | | | | <a name="cockroach.server.serverpb.HotRangesResponse.NodeResponse"></a> NodeResponse is a hot range report for a single target node. Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | error_message | | | ErrorMessage is set to a non-empty string if this target node was unable to produce a hot range report.<br><br>The contents of this string indicates the cause of the failure. | | | stores | | repeated | Stores contains the hot ranges report if no error was encountered. There is one part to the report for each store in the target node. | | <a name="cockroach.server.serverpb.HotRangesResponse.StoreResponse"></a> StoreResponse contains the part of a hot ranges report that pertains to a single store on a target node. Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | store_id | | | StoreID identifies the store for which the report was produced. | | | hot_ranges | | repeated | HotRanges is the hot ranges report for this store on the target node. | | <a name="cockroach.server.serverpb.HotRangesResponse.HotRange"></a> HotRange is a hot range report for a single store on one of the target node(s) selected in a HotRangesRequest. Support status: | Field | Type | Label | Description | Support status | | -- | - | -- | -- | -- | | desc | | | Desc is the descriptor of the range for which the report was produced.<br><br>TODO(knz): This field should be removed. See: https://github.com/cockroachdb/cockroach/issues/53212 | | | queriespersecond | | | QueriesPerSecond is the recent number of queries per second on this range. | | | leaseholdernodeid | | | LeaseholderNodeID indicates the Node ID that is the current leaseholder for the given range. | | | requestspersecond | | | Requests per second is the recent number of requests received per second on this range. | | | writespersecond | | | Writes per second is the recent number of keys written per second on this range. | | | readspersecond | | | Reads per second is the recent number of keys read per second on this range. | | | writebytesper_second | | | Write bytes per second is the recent number of bytes written per second on this range. | | | readbytesper_second | | | Read bytes per second is the recent number of bytes read per second on this range. | | | cputimeper_second | | | CPU time per second is the recent cpu usage in nanoseconds of this range. | |
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_options.md

title: Kubectl-Dba Options menu: docs_{{ .version }}: identifier: kubectl-dba-options name: Kubectl-Dba Options parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Print the list of flags inherited by all commands Print the list of flags inherited by all commands ``` kubectl-dba options [flags] ``` ``` kubectl dba options ``` ``` -h, --help help for options ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - kubectl plugin for KubeDB
Project: Topaz (Provisioning / Security & Compliance)
File: SLACK.md

The [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) applies in all areas in addition to these rules: Outside of the issue queues, Slack is our best communication medium for projects. Please keep your messages on topic for each channel, and please use the appropriate channel. Please do not cross-post. Spamming channels with unsolicited or frequent messages is not allowed. This workspace is intended for conversations related to Topaz projects. Please do not use the Slack to advertise proprietary vendor products, services, webinars, blogs, etc. Please report issues to Vlad Iovanov (dani@aserto.com or @carabasdaniel) or Gert Drapers (gert@aserto.com or @gertd). Unacceptable behavior from any community member will not be tolerated. If a community member engages in unacceptable behavior, an admin may take any action deemed appropriate, up to and including a warning or temporary 30 day ban, along with a permanent ban for repeated violation of these guidelines. Admins may also remove content that violates the above guidelines.
Project: KICS (Provisioning / Security & Compliance)
File: d6cabc3a-d57e-48c2-b341-bf3dd4f4a120.md

title: Cloud Storage Bucket Logging Not Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d6cabc3a-d57e-48c2-b341-bf3dd4f4a120 Query name: Cloud Storage Bucket Logging Not Enabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Cloud storage bucket should have logging enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "googlestoragebucket" "positive1" { name = "auto-expiring-bucket" location = "US" force_destroy = true lifecycle_rule { condition { age = 3 } action { type = "Delete" } } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlestoragebucket" "negative1" { name = "auto-expiring-bucket" location = "US" force_destroy = true logging { logBucket = "example-logs-bucket" } lifecycle_rule { condition { age = 3 } action { type = "Delete" } } } ```
Project: Sonobuoy (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Tell us about a problem you are experiencing What steps did you take and what happened: [A clear and concise description of what the bug is.] What did you expect to happen: Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] Environment: Sonobuoy version: Kubernetes version: (use `kubectl version`): Kubernetes installer & version: Cloud provider or hardware configuration: OS (e.g. from `/etc/os-release`): Sonobuoy tarball (which contains * below)
Project: KICS (Provisioning / Security & Compliance)
File: fd8da341-6760-4450-b26c-9f6d8850575e.md

title: Redis Entirely Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: fd8da341-6760-4450-b26c-9f6d8850575e Query name: Redis Entirely Accessible Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Networking and Firewall URL: Firewall rule allowing unrestricted access to Redis from the Internet<br> ```tf title="Positive test num. 1 - tf file" hl_lines="22" resource "azurermrediscache" "positive1" { name = "redis${random_id.server.hex}" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name capacity = 1 family = "P" sku_name = "Premium" enablenonssl_port = false redis_configuration { maxclients = 256 maxmemory_reserved = 2 maxmemory_delta = 2 maxmemory_policy = "allkeys-lru" } } resource "azurermredisfirewall_rule" "positive2" { name = "someIPrange" rediscachename = azurermrediscache.example.name resourcegroupname = azurermresourcegroup.example.name start_ip = "0.0.0.0" end_ip = "0.0.0.0" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermrediscache" "negative1" { name = "redis${random_id.server.hex}" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name capacity = 1 family = "P" sku_name = "Premium" enablenonssl_port = false redis_configuration { maxclients = 256 maxmemory_reserved = 2 maxmemory_delta = 2 maxmemory_policy = "allkeys-lru" } } resource "azurermredisfirewall_rule" "negative2" { name = "someIPrange" rediscachename = azurermrediscache.example.name resourcegroupname = azurermresourcegroup.example.name start_ip = "10.2.3.4" end_ip = "10.3.4.5" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: hget.md

title: HGET linkTitle: HGET description: HGET menu: preview: parent: api-yedis weight: 2120 aliases: /preview/api/redis/hget /preview/api/yedis/hget type: docs `HGET key field` This command fetches the value for the given `field` in the hash that is specified by the given `key`. If the given `key` or `field` does not exist, nil is returned. If the given `key` is associated with non-hash data, an error is raised. Returns the value for the given `field` ```sh $ HSET yugahash area1 "America" ``` ``` 1 ``` ```sh $ HGET yugahash area1 ``` ``` "America" ``` , , , , , , , , , ,
Project: YugabyteDB (App Definition and Development / Database)
File: ingest-the-data-sql.md

title: ingest-the-data-master-script SQL script linkTitle: ingest-the-data.sql headerTitle: ingest-the-data.sql description: One of a set of SQL scripts for analyzing the correlation between COVID-like symptoms and mask-wearing using data from Carnegie Mellon's COVIDcast menu: v2.18: identifier: ingest-the-data-sql parent: ingest-scripts weight: 100 type: docs Save this script as "ingest-the-data.sql" ```plpgsql -- Set up the infrastructure and create the tables. drop table if exists covidcast_names cascade; create table covidcastnames(csvfile text primary key, staging_table text not null, signal text not null); -- Each of these files contains 50 days of observations. insert into covidcastnames(csvfile, staging_table, signal) values ('csv-files/covidcast-fb-survey-smoothed'|| 'wearingmask' ||'-2020-09-13-to-2020-11-01.csv', 'maskwearers', 'smoothedwearing_mask'), ('csv-files/covidcast-fb-survey-smoothed'|| 'cli' ||'-2020-09-13-to-2020-11-01.csv', 'symptoms', 'smoothedcli'), ('csv-files/covidcast-fb-survey-smoothed'|| 'hhcmntycli' ||'-2020-09-13-to-2020-11-01.csv', 'cmntysymptoms', 'smoothedhhcmnty_cli'); create unique index covidcastnamesstagingtableunq on covidcastnames(stagingtable); create unique index covidcastnamessignalunq on covidcastnames(signal); \i cr-cr-staging-tables.sql \i cr-cr-copy-from-csv-scripts.sql call crstagingtables(); -- -- Import the CSV files into the staging tables; \t on \o copyfromcsv.sql select crcopyfrom_scripts(1); \o \i copyfromcsv.sql \o copyfromcsv.sql select crcopyfrom_scripts(2); \o \i copyfromcsv.sql \o copyfromcsv.sql select crcopyfrom_scripts(3); \o \i copyfromcsv.sql \t off -- -- Check that the imported data are consistent with what was assumed about its -- format and content. If the checks pass, then merge it into the single -- "covidcastfbsurvey_results" table. \i cr-assert-assumptions-ok.sql \i cr-xform-to-covidcast-fb-survey-results.sql do $body$ begin -- If "assertassumptionsok()" aborts with an assert failure, -- then "crcovidcastfbsurveyresults()" will not be called. call assertassumptionsok( startsurveydate => to_date('2020-09-13', 'yyyy-mm-dd'), endsurveydate => to_date('2020-11-01', 'yyyy-mm-dd')); call xformtocovidcastfbsurvey_results(); end; $body$; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.116.md

layout: release date: 2023-08-03 tag: v0.6.116 Revert "Specify additional specific load generator options in mesheryctl perf" @leecalcote (#8363) Thank you to our contributors for making this release possible: @MUzairS15, @abdullah1308 and @leecalcote
Project: YugabyteDB (App Definition and Development / Database)
File: managed-cli-user.md

title: ybm CLI user resource headerTitle: ybm user linkTitle: user description: YugabyteDB Managed CLI reference user resource. headcontent: Manage users menu: preview_yugabyte-cloud: identifier: managed-cli-user parent: managed-cli-reference weight: 20 type: docs Use the `user` resource to invite and manage YugabyteDB Managed account . ```text Usage: ybm user [command] [flags] ``` List users in YugabyteDB Managed: ```sh ybm user list ``` Invite a user to YugabyteDB Managed: ```sh ybm user invite --email developer@mycompany.com --role Developer ``` Delete a specified user. | Flag | Description | | : | : | | --email | Required. Email of the user. | Invite a user to your YugabyteDB Managed account. | Flag | Description | | : | : | | --email | Required. Email of the user. | | --role-name | Required. Name of the role to assign. | List the users in your YugabyteDB Managed account. | Flag | Description | | : | : | | --email | Email of a user. | Modify the role of a user in your YugabyteDB Managed account. | Flag | Description | | : | : | | --email | Required. Email of the user. | | --role-name | Required. Name of the role to assign. |
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.27.md

layout: release date: 2021-06-30 tag: v0.5.27 test meshery build code @nehaLohia27 (#3301) netlify build code for meshery repo @nehaLohia27 (#3300) [mesheryctl] Minor fix for `mesheryctl system status` @piyushsingariya (#3298) REST API and GraphQL docs @kaushambisharma (#3294) contributing meshery errors updated @kumarabd (#3289) update workflows to reflect meshery repo change @navendu-pottekkat (#3290) Refactor some part of helpers and split into related packages @anirudhjain75 (#3259) Open API Docs #3 @piyushsingariya (#3173) [mesheryctl] `perf apply` Performance-id replaced with performance-name @piyushsingariya (#3254) Add support for JSONSchema Draft4 in RJSF @utkarsh-pro (#3278) Adds a New Line for the finalMSG @DantrazTrev (#3264) Bump normalize-url from 4.5.0 to 4.5.1 in /provider-ui @dependabot (#3292) Open API Docs #2 @piyushsingariya (#3075) Thank you to our contributors for making this release possible: @DantrazTrev, @Nikhil-Ladha, @anirudhjain75, @dependabot, @dependabo[bot], @dhruv0000, @kaushambisharma, @kumarabd, @leecalcote,@navendu-pottekkat, @nehaLohia27, @piyushsingariya and @utkarsh-pro
Project: Beam (App Definition and Development / Streaming & Messaging)
File: arquivei.md

title: "Arquivei" icon: /images/logos/powered-by/arquivei.png hasLink: "https://arquivei.com.br/" <!-- 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: Meshery (Provisioning / Automation & Configuration)
File: longhorn.md

layout: integration title: Longhorn subtitle: Collaborative and visual infrastructure as code for Longhorn image: /assets/img/integrations/longhorn/icons/color/longhorn-color.svg permalink: extensibility/integrations/longhorn docURL: https://docs.meshery.io/extensibility/integrations/longhorn description: integrations-category: Cloud Native Storage integrations-subcategory: Cloud Native Storage registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: YugabyteDB (App Definition and Development / Database)
File: return-statement.md

title: The PL/pgSQL "return" statement [YSQL] headerTitle: The PL/pgSQL "return" statement linkTitle: > "return" statement description: Describes the syntax and semantics various PL/pgSQL "return" statement variants[YSQL]. menu: stable: identifier: return-statement parent: basic-statements weight: 40 type: docs showRightNav: true {{%ebnf%}} plpgsqlreturnstmt {{%/ebnf%}} You can use the bare return statement to exit from any top-level PL/pgSQL block statement (even if it is invoked within a deeply-nested block statement). In particular, you can use it to exit from a procedure or a do statement. However, this use is very rarely seenand many programers would consider it to be a bad practice. Rather, the preferred practice is to let the point of execution simply reach the final end; by virtue of the use of "proper" flow control with the if statement or the case statement. Then the procedure is automatically exited just as if the bare return were written here (and only here). This is legal only in a regular function (but not in a table function). In fact every regular function must have at least one such statement and the point of execution must reach one of these. If you fail to satisfy this rule, then there's no syntax error. But you'll get the 2F005 run-time error saying that the function finished without executing a return expression statement. The expression must match what the returns clause, in the function's header, specifies. This is legal only in a table function. In fact every table function must have at least one such statement and the point of execution must reach one of these. Often, the return next statement is written within a loop so that the table function returns many rows. Notice that the return next statement takes no argument. Rather, you must assign value(s) ordinarily before invoking it, just as if these identified ordinary in out formal arguments, using the identifier(s) that the returns table(...) clause, in the function's header, specifies. These are legal only in a DML trigger function. In fact every DML trigger function must have at least one such statement and the point of execution must reach one of these. A DML trigger function is created as such by using the returns trigger clause in the function's header. <! todo_ > {{< note title="Coming soon" >}} More detail, and code examples, about these uses will follow. {{< /note >}}