cwielenb/CNCF-Dataset huggingface dataset:
Project: YDB (App Definition and Development / Database)
File: workload-tpch.md

The workload is based on the TPC-H , and the queries and table schema are adapted for {{ ydb-short-name }}. The test generates a typical decision support workload. Before running the benchmark, create a table: ```bash {{ ydb-cli }} workload tpch init ``` See the description of the command to run the data load: ```bash {{ ydb-cli }} workload tpch init --help ``` | Option name | Option description | | | `--path <value>` | Directory to create tables in. Default value - empty string. | | `--store <value>` | Type of table storage. Acceptable values: `row`, `column`. Default value: `row`. | You can download the dataset generator for the TPC-H benchmark by the . Then follow the instructions from README. In the `dss.h` file, you can specifya field separator: Default: `#define SEPARATOR '|'`. In the sample data upload script, `'\t'` is used as a separator. ```bash for table in region nation supplier customer part partsupp orders lineitem; do echo "Start data load to $table" {{ ydb-cli }} import file tsv --header --path "$table" --input-file $table.tsv --newline-delimited echo "Finish data load to $table" done ``` Run the load: ```bash {{ ydb-cli }} workload tpch run ``` During this test, workload statistics for each query are displayed on the screen. See the description of the command to run the data load: ```bash {{ ydb-cli }} workload tpch run --help ``` | Option name | Option description | | | `--path <value>` | Directory to create tables in. Default value - empty string. | | `--output <value>` | The name of the file in which the query execution results will be saved. The default value is `results.out`. | | `--iterations <value>` | The number of executions of each load generating query. The default value is `1`. | | `--json` | The name of the file in which the query execution statistics will be saved in `json` format. By default, the file is not saved. | | `--ministat` | The name of the file in which the query execution statistics will be saved in `ministat` format. By default, the file is not saved. | | `--query-settings` | Query execution settings. By default, not specified. | | `--ext-queries-dir` | Name of the directory with external queries used to apply the workload. | | `--include` | The numbers or number sections of the queries to be executed as part of the load. By default, all queries are executed. Separated by commas, for example, `1,2,4-6`. | | `--exclude` | The numbers or number sections of the queries to be excluded as part of the load. By default, all queries are executed. Separated by commas, for example, `1,2,4-6`. |
Project: ClickHouse (App Definition and Development / Database)
File: 80_backward-compatibility.md

name: Backward compatibility issue about: Report the case when the behaviour of a new version can break existing use cases title: '' labels: backward compatibility assignees: '' (you don't have to strictly follow this form) Describe the issue A clear and concise description of what works not as it is supposed to. How to reproduce Which ClickHouse server versions are incompatible 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 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: Meshery (Provisioning / Automation & Configuration)
File: armory-spinnaker-operator.md

layout: integration title: Armory Spinnaker Operator subtitle: Collaborative and visual infrastructure as code for Armory Spinnaker Operator image: /assets/img/integrations/armory-spinnaker-operator/icons/color/armory-spinnaker-operator-color.svg permalink: extensibility/integrations/armory-spinnaker-operator docURL: https://docs.meshery.io/extensibility/integrations/armory-spinnaker-operator description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery registrant: Artifact Hub components: name: armory-account colorIcon: assets/img/integrations/armory-spinnaker-operator/components/armory-account/icons/color/armory-account-color.svg whiteIcon: assets/img/integrations/armory-spinnaker-operator/components/armory-account/icons/white/armory-account-white.svg description: name: spinnaker-service colorIcon: assets/img/integrations/armory-spinnaker-operator/components/spinnaker-service/icons/color/spinnaker-service-color.svg whiteIcon: assets/img/integrations/armory-spinnaker-operator/components/spinnaker-service/icons/white/spinnaker-service-white.svg description: featureList: [ "Stop using Halyard commands: just kubectl apply your Spinnaker configuration.", "Expose Spinnaker to the outside world (via LoadBalancer).", "Keep secrets separate from your config." ] 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: Apollo (Provisioning / Automation & Configuration)
File: _coverpage.md

<img src="https://cdn.jsdelivr.net/gh/apolloconfig/apollo@master/doc/images/logo/logo-simple.png" alt="apollo-logo" width="30%"> A reliable configuration management system Multiple environments and clusters support Configuration changes take effect in real time Versioned and grayscale releases management Great authentication, authorization and audit control
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 32_data_encoding.md

Prompt: How does data encoding work in the Apache Beam model and why is it needed? Response: In Apache Beam, data encoding is a fundamental aspect of processing data in distributed environments. The model operates on the principle of encoding each element of a `PCollection` as a byte string. Data encoding is necessary to pass elements efficiently between distributed workers during the execution of an Apache Beam pipeline. Apache Beam is designed for distributed processing, where a pipeline may be executed on multiple VMs (workers) concurrently. During pipeline execution, workers collaborate to process data and often need to materialize the intermediate data in your `PCollection`. Communication between workers involves the exchange of encoded data over a network. The process of serialization converts data into byte strings for transmission, while deserialization restores byte strings into object form. Apache Beam offers a data encoding mechanism with built-in support for commonly used types, as well as the flexibility to specify custom encodings. The Beam SDKs use the `Coder` objects to define how elements in a `PCollection` are encoded and decoded. These objects ensure type consistency and safety, guaranteeing that the encoding and decoding processes correctly interpret data based on its original data types. Every `PCollection` in an Apache Beam pipeline requires a corresponding `Coder`. In most cases, the Apache Beam SDKs can automatically infer a `Coder` for a `PCollection` based on its element type or the transform that produces it. However, in some cases, the pipeline author will need to specify a `Coder` explicitly or develop a `Coder` for their custom type. Apache Beam comes with many inbuilt `Coder` objects that work with a variety of standard data types. Users can also build custom coders or register a new default coder for a given type using the `CoderRegistry` object in their pipeline.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.13.md

RabbitMQ `3.11.13` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . `3.11.12` introduced a regression that caused client connections to fail with an exception when TCP or TLS listeners were bound to a particular interface. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.13.tar.xz` instead of the source tarball produced by GitHub.
Project: ClickHouse (App Definition and Development / Database)
File: v23.2.6.34-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Formatter '%M' in function formatDateTime() now prints the month name instead of the minutes. This makes the behavior consistent with MySQL. The previous behavior can be restored using setting "formatdatetimeparsedatetimemismonth_name = 0". (). Backported in : Update time zones. The following were updated: Africa/Cairo, Africa/Casablanca, Africa/ElAaiun, America/Bogota, America/CambridgeBay, America/CiudadJuarez, America/Godthab, America/Inuvik, America/Iqaluit, America/Nuuk, America/Ojinaga, America/Pangnirtung, America/RankinInlet, America/Resolute, America/Whitehorse, America/Yellowknife, Asia/Gaza, Asia/Hebron, Asia/Kuala_Lumpur, Asia/Singapore, Canada/Yukon, Egypt, Europe/Kirov, Europe/Volgograd, Singapore. (). Backported in : After the recent update, the `dockerd` requires `--tlsverify=false` together with the http port explicitly. (). Fix race in grace hash join with limit (). Fix explain graph with projection (). Fix crash in polygonsSymDifferenceCartesian (). Remove a feature (). Fix cpu usage in rabbitmq (was worsened in 23.2 after ) (). ClickHouse startup error when loading a distributed table that depends on a dictionary (). Fix possible segfault in cache (). Fix nested map for keys of IP and UUID types (). Fix bug in Keeper when a node is not created with scheme `auth` in ACL sometimes. (). Fix IPv4 comparable with UInt ().
Project: KICS (Provisioning / Security & Compliance)
File: 338b6cab-961d-4998-bb49-e5b6a11c9a5c.md

title: EC2 Not EBS Optimized hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 338b6cab-961d-4998-bb49-e5b6a11c9a5c Query name: EC2 Not EBS Optimized Platform: Ansible Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: It's considered a best practice for an EC2 instance to use an EBS optimized instance. This provides the best performance for your EBS volumes by minimizing contention between Amazon EBS I/O and other traffic from your instance<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2" name: example amazon.aws.ec2: key_name: mykey instance_type: t2.micro image: ami-123456 wait: yes group: default count: 3 vpcsubnetid: subnet-29e63245 ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10" name: example2 amazon.aws.ec2: key_name: mykey instance_type: t2.micro image: ami-123456 wait: yes group: default count: 3 vpcsubnetid: subnet-29e63245 ebs_optimized: false ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="2" name: example3 amazon.aws.ec2: key_name: mykey image: ami-123456 wait: yes group: default count: 3 vpcsubnetid: subnet-29e63245 ``` ```yaml title="Negative test num. 1 - yaml file" name: example4 amazon.aws.ec2: key_name: mykey image: ami-123456 wait: yes group: my_sg count: 3 vpcsubnetid: subnet-29e63245 ebs_optimized: true ``` ```yaml title="Negative test num. 2 - yaml file" name: example5 amazon.aws.ec2: key_name: mykey instance_type: t3.nano image: ami-123456 wait: yes group: my_sg count: 3 vpcsubnetid: subnet-29e63245 ``` ```yaml title="Negative test num. 3 - yaml file" name: example5 amazon.aws.ec2: key_name: mykey instance_type: t3.nano image: ami-123456 wait: yes group: my_sg count: 3 vpcsubnetid: subnet-29e63245 ebs_optimized: false ```
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: server.md

A Server is a OAM core workload type to define long-running, scalable workloads that have a network endpoint with a stable name to receive network traffic for the component as a whole. Common use cases include web applications and services that expose APIs. The Server workload type has the following characteristics: Defines a container runtime where zero or more replicas of the same container may be run simultaneously. An application operator can increase or decrease the number of component replicas by applying and configuring traits when available. A Server is daemonized. A runtime MUST attempt to restart replicas that exit regardless of error code. A Server has a network endpoint with an automatically assigned virtual IP address (VIP) and DNS name addressable within the network scope to which the component belongs. If a Server does not provide at least one port on at least one container, implementations SHOULD emit an error. Install below workload definition in your OAM based platform: ```yaml apiVersion: core.oam.dev/v1beta1 kind: WorkloadDefinition metadata: name: Server spec: definitionRef: name: containerizedworkloads.core.oam.dev # the reference of schema for this workload type. In Kubernetes it should be a full name of API resource ``` > Note: this workload references as schema. Define a component references `Server` as workloads: ```yaml apiVersion: core.oam.dev/v1beta1 kind: ComponentDefinition metadata: name: webserver annotations: definition.oam.dev/description: "webserver is a combo of Deployment + Service" spec: workload: type: Server # reference above workload definition by name. schematic: ... # CUE code to define user schematic. ```
Project: Pinniped (Provisioning / Key Management)
File: proposal_tracking.md

name: Proposal tracking about: A tracking issue for a proposal document title: '[Proposal] Your proposal title' labels: 'proposal-tracking' assignees: '' <!-- Hey! Thanks for opening an issue! This type of issue should only be opened if you intend to create a formal proposal document. Please refer to the proposal process in . Please title this issue starting with `[Proposal]` followed by a title for what you are going to propose. For example: `[Proposal] Lunar landing module authentication via Pinniped`. --> Proposal: <!-- this starts empty, then please update to link to proposal PR, then also link to proposal doc file after it is merged --> Discussion Links: <!-- link to any mailing list threads, Slack conversations, community meetings, or other places where the proposal was discussed, if any --> <!-- A --> <!-- B --> Pull requests: <!-- link to all PRs related to this proposal such as updates to the proposal doc, implementation PRs, etc. - keep this list up to date --> <!-- #123: briefly describe this PR --> <!-- #456: briefly describe this PR -->
Project: KICS (Provisioning / Security & Compliance)
File: 8320826e-7a9c-4b0b-9535-578333193432.md

title: RBAC Roles Allow Privilege Escalation hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8320826e-7a9c-4b0b-9535-578333193432 Query name: RBAC Roles Allow Privilege Escalation Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Roles or ClusterRoles with RBAC permissions 'bind' or 'escalate' allow subjects to create new bindings with other roles. This is dangerous, as users with these privileges can bind to roles that may exceed their own privileges<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: rbac-binder rules: apiGroups: ["rbac.authorization.k8s.io"] resources: ["clusterroles"] verbs: ["bind"] apiGroups: ["rbac.authorization.k8s.io"] resources: ["clusterrolebindings"] verbs: ["create"] ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: not-rbac-binder rules: apiGroups: ["rbac.authorization.k8s.io"] resources: ["clusterrolebindings"] verbs: ["create"] ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.85.md

layout: release date: 2023-04-24 tag: v0.6.85 [mesheryctl] Adding support for operator flag @suhail34 (#7363) Enable toggling of theme in Meshery-extensions @Abhishek-kumar09 (#7527) fix logic for kubernetes version @MUzairS15 (#7587) Add workflow to reboot equinix metal servers every 20 hours @Revolyssup (#7590) typo fix @santosh-sankranthi (#7595) updated opengraph image's address @vishalvivekm (#7600) updated opengraph image @vishalvivekm (#7599) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @MUzairS15, @Revolyssup, @alphaX86, @leecalcote, @santosh-sankranthi, @suhail34, @theBeginner86, @vishalvivekm, MUzairS15 and l5io
Project: Hazelcast IMDG (App Definition and Development / Database)
File: 01-per-entry-stats.md

| Since: 4.2| |-| After implementing per config record creation, we managed to break tight coupling between features and record metadata. Based on this, now we have a chance to enable/disable record metadata to reduce memory usage of a record. We categorize stats in two types: map-level and entry-level. Map level is enabled by default but entry-level is not. Map-level stats are: hits: total hits of map lastAccessTime: last access time to map lastUpdateTime: last update time of map Entry-level stats are: hits: total hits to entry lastAccessTime: last access time to entry lastUpdateTime: last update time of entry creationTime: creation time of entry lastStoredTime: last store time of entry Map-level stats are created per map's partition. They are replicated to new nodes to be safe from partition ownership changes. Entry-level stats are already replicated when enabled. No change is needed for them. Custom eviction policies Entry-views For Some Split brain merge policies
Project: Meshery (Provisioning / Automation & Configuration)
File: jaeger.md

layout: integration title: Jaeger subtitle: Collaborative and visual infrastructure as code for Jaeger image: /assets/img/integrations/jaeger/icons/color/jaeger-color.svg permalink: extensibility/integrations/jaeger docURL: https://docs.meshery.io/extensibility/integrations/jaeger description: integrations-category: Observability and Analysis integrations-subcategory: Tracing 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: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_health_checks.md

+++ title = "googlecomputehealth_checks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputehealth_checks" identifier = "inspec/resources/gcp/googlecomputehealthchecks.md googlecomputehealthchecks resource" parent = "inspec/resources/gcp" +++ A `googlecomputehealth_checks` is used to test a Google HealthCheck resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputehealth_checks(project: 'chef-gcp-inspec') do its('names') { should include 'inspec-gcp-health-check' } its('timeout_secs') { should include '10' } end ``` Properties that can be accessed from the `googlecomputehealth_checks` resource: See the resource for more information. `checkintervalsecs` : an array of `googlecomputehealthcheck` checkinterval_sec `creation_timestamps` : an array of `googlecomputehealthcheck` creationtimestamp `descriptions` : an array of `googlecomputehealth_check` description `healthy_thresholds` : an array of `googlecomputehealthcheck` healthythreshold `ids` : an array of `googlecomputehealth_check` id `names` : an array of `googlecomputehealth_check` name `timeout_secs` : an array of `googlecomputehealthcheck` timeoutsec `unhealthy_thresholds` : an array of `googlecomputehealthcheck` unhealthythreshold `types` : an array of `googlecomputehealth_check` type `httphealthchecks` : an array of `googlecomputehealthcheck` httphealth_check `httpshealthchecks` : an array of `googlecomputehealthcheck` httpshealth_check `tcphealthchecks` : an array of `googlecomputehealthcheck` tcphealth_check `sslhealthchecks` : an array of `googlecomputehealthcheck` sslhealth_check `http2healthchecks` : an array of `googlecomputehealthcheck` http2health_check `log_configs` : (Beta only) an array of `googlecomputehealthcheck` logconfig 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: ArangoDB (App Definition and Development / Database)
File: assume_error_lvalue.md

+++ title = "`errortype &assumeerror() & noexcept`" description = "Narrow contract lvalue reference observer of the stored error. Constexpr propagating, never throws." categories = ["observers"] weight = 700 +++ Narrow contract lvalue reference observer of the stored error. `NoValuePolicy::narrowerrorcheck()` is first invoked, then the reference to the error is returned. As a valid default constructed error is always present, no undefined behaviour occurs unless `NoValuePolicy::narrowerrorcheck()` does that. Note that if `error_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowerrorcheck()`. Guarantees: An exception is never thrown.
Project: Project Syn (Provisioning / Automation & Configuration)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thank you for your pull request. Please provide a description above and review the checklist below. Contributors guide: ./CONTRIBUTING.md --> <!-- Remove items that do not apply. For completed items, change [ ] to [x]. --> [ ] Keep pull requests small so they can be easily reviewed. [ ] Update the documentation. [ ] Update tests. [ ] Categorize the PR by setting a good title and adding one of the labels: `bug`, `enhancement`, `documentation`, `change`, `breaking`, `dependency`, `internal` as they show up in the changelog [ ] Link this PR to related issues. <!-- NOTE: these things are not required to open a PR and can be done afterwards, while the PR is open. -->
Project: ShardingSphere (App Definition and Development / Database)
File: drop-encrypt-rule.en.md

+++ title = "DROP ENCRYPT RULE" weight = 3 +++ The `DROP ENCRYPT RULE` syntax is used to drop an existing encryption rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropEncryptRule ::= 'DROP' 'ENCRYPT' 'RULE' ifExists? ruleName (',' ruleName)* ifExists ::= 'IF' 'EXISTS' ruleName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `ifExists` clause is used for avoid `Encrypt rule not exists` error. Drop an encrypt rule ```sql DROP ENCRYPT RULE tencrypt, tencrypt_2; ``` Drop encrypt with `ifExists` clause ```sql DROP ENCRYPT RULE IF EXISTS tencrypt, tencrypt_2; ``` `DROP`, `ENCRYPT`, `RULE`
Project: ClickHouse (App Definition and Development / Database)
File: v24.3.2.23-lts.md

sidebar_position: 1 sidebar_label: 2024 Fix logical error in groupbyuse_nulls + grouping set + analyzer + materialize/constant (). Fix external table cannot parse data type Bool (). Revert "Merge pull request from liuneng1994/optimizeinsingle_value" (). Backported in :. (). Backported in : ... (). Backported in :. (). Fix some crashes with analyzer and groupbyuse_nulls. (). Fix scalars create as select (). Ignore IfChainToMultiIfPass if returned type changed. (). Fix type for ConvertInToEqualPass (). Revert output Pretty in tty ().