cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: v23.1.5.24-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fix error during server startup on old distros (e.g. Amazon Linux 2) and on ARM that glibc 2.28 symbols are not found. (). Backported in : Fix `SYSTEM UNFREEZE` queries failing with the exception `CANNOTPARSEINPUTASSERTIONFAILED`. (). Backported in : - Fix incorrect alias recursion in QueryNormalizer. (). Backported in : `INSERT` queries through native TCP protocol and HTTP protocol were not canceled correctly in some cases. It could lead to a partially applied query if a client canceled the query, or if a client died or, in rare cases, on network errors. As a result, it could lead to not working deduplication. Fixes and . (). Backported in : - Fix arithmetic operations in aggregate optimization with `min` and `max`. (). Backported in : Fix MSan report in the `maxIntersections` function. This closes . (). Backported in : Fix possible deadlock on distributed query cancellation. (). Use /etc/default/clickhouse in systemd too (). Update typing for a new PyGithub version (). Follow-up to (). Add a manual trigger for release workflow ().
Project: Beam (App Definition and Development / Streaming & Messaging)
File: yaml_combine.md

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> The contents of this file have been moved to the main Beam site at https://beam.apache.org/documentation/sdks/yaml-combine/
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.4.md

layout: release date: 2022-08-31 tag: v0.6.4 language: en Reinstate gowrk2 submodule under `server` directory @alphaX86 (#6126) Fix clone on filters @gr455 (#6117) Upgrade nighthawk @gr455 (#6103) [Server] Backend support for Meshery Catalog @gr455 (#6028) chore(mesheryctl): add loader to mesheryctl pattern apply @pk-218 (#6079) fix(ci): update `docker-compose.yaml` path @pk-218 (#6111) fix(ci/lint): fix failing lint check @pk-218 (#6113) [UI] 50% width for input in RJSF @Chadha93 (#6129) [Extensions] Remote config icon update @Chadha93 (#6124) Bump eslint-plugin-react from 7.30.1 to 7.31.1 in /provider-ui @dependabot (#6116) [RJSF] fixed the size of the input field @harkiratsm (#6101) RJSF Validation @harkiratsm (#6114) [Server] Backend support for Meshery Catalog @gr455 (#6028) Added a textoverflow ellipsis for rjsf @harkiratsm (#6104) [Server] Backend support for Meshery Catalog @gr455 (#6028) [Dependencies] meshkit and meshsync upgrades @leecalcote (#6130) [CI] Issue labeling update @leecalcote (#6122) Bump eslint-plugin-react from 7.30.1 to 7.31.1 in /provider-ui @dependabot (#6116) echo log in core E2E workflow for debugging @Revolyssup (#6121) Addadaptertestsresiliencylogic/#5900 @Zanda256 (#6102) [Docs]refactor: Merge Build and Releases page inside Contributing section @sambit-sankalp (#6074) Thank you to our contributors for making this release possible: @Chadha93, @MUzairS15, @Revolyssup, @Zanda256, @alphaX86, @dependabot, @dependabot[bot], @gr455, @harkiratsm, @l5io, @leecalcote, @pk-218 and @sambit-sankalp
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.25.md

RabbitMQ `3.8.25` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a`3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. New Prometheus metrics for alarms: `rabbitmqalarmsfiledescriptorlimit` 1|0 `rabbitmqalarmsfreediskspace_watermark` 1|0 `rabbitmqalarmsmemoryusedwatermark` 1|0 While some of the alarms have cluster-wide effect, these metrics are node-local. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.25.tar.xz` instead of the source tarball produced by GitHub.
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: RELEASE.md

Prerequisites (one-time setup) Enable "Trusted Publishing" in PyPI project settings Publisher: GitHub Owner: theupdateframework Project: python-tuf Workflow: cd.yml Environment: release Go to [GitHub settings](https://github.com/theupdateframework/python-tuf/settings/environments), create an called `release` and configure [review protection](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#required-reviewers). Ensure `docs/CHANGELOG.md` contains a one-line summary of each [notable change](https://keepachangelog.com/) since the prior release Update `tuf/init.py` to the new version number `A.B.C` Create a PR with updated `CHANGELOG.md` and version bumps &#10132; Review PR on GitHub Once the PR is merged, pull the updated `develop` branch locally Create a signed tag for the version number on the merge commit `git tag --sign vA.B.C -m "vA.B.C"` Push the tag to GitHub `git push origin vA.B.C` *A tag push triggers the [CD workflow](https://github.com/theupdateframework/python-tuf/blob/develop/.github/workflows/cd.yml), which runs the tests, builds source dist and wheel, creates a preliminary GitHub release under `vA.B.C-rc`, and pauses for review.* Run `verify_release --skip-pypi` locally to make sure a build on your machine matches the preliminary release artifacts published on GitHub. &#10132; on GitHub *An approval resumes the CD workflow to publish the release on PyPI, and to finalize the GitHub release (removes `-rc` suffix and updates release notes).* Run `verify_release` to make sure the PyPI release artifacts match the local build as well. When called as `verify_release --sign [<key id>]` the script additionally creates gpg release signatures. When signed by maintainers with a corresponding GPG fingerprint in the MAINTAINERS.md file, these signature files should be made available on the GitHub release page under Assets. Announce the release on Ensure , for the reference implementation, is up-to-date
Project: KICS (Provisioning / Security & Compliance)
File: 895ed0d9-6fec-4567-8614-d7a74b599a53.md

title: BOM - GCP Dataflow hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 895ed0d9-6fec-4567-8614-d7a74b599a53 Query name: BOM - GCP Dataflow Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of Dataflow resources found. Unified stream and batch data processing that's serverless, fast, and cost-effective.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 17" resource "googledataflowjob" "pubsub_stream" { name = "tf-test-dataflow-job1" templategcspath = "gs://my-bucket/templates/template_file" tempgcslocation = "gs://my-bucket/tmp_dir" enablestreamingengine = true parameters = { inputFilePattern = "${googlestoragebucket.bucket1.url}/*.json" outputTopic = googlepubsubtopic.topic.id } transformnamemapping = { name = "test_job" env = "test" } on_delete = "cancel" } resource "googledataflowjob" "pubsub_stream2" { name = "tf-test-dataflow-job1" templategcspath = "gs://my-bucket/templates/template_file" tempgcslocation = "gs://my-bucket/tmp_dir" enablestreamingengine = true parameters = { inputFilePattern = "${googlestoragebucket.bucket1.url}/*.json" outputTopic = googlepubsubtopic.topic.id } transformnamemapping = { name = "test_job" env = "test" } on_delete = "cancel" kmskeyname = "somekey" ipconfiguration = "WORKERIP_PUBLIC" } ``` ```tf title="Negative test num. 1 - tf file" resource "googlebigquerydataset" "negative1" { datasetid = "exampledataset" friendly_name = "test" description = "This is a test description" location = "EU" defaulttableexpiration_ms = 3600000 labels = { env = "default" } access { role = "OWNER" userbyemail = googleserviceaccount.bqowner.email } access { role = "READER" domain = "hashicorp.com" } } ```
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 22] Smartphone (please complete the following information): Device: [e.g. iPhone6] OS: [e.g. iOS8.1] Browser [e.g. stock browser, safari] Version [e.g. 22] Additional context Add any other context about the problem here.
Project: ClickHouse (App Definition and Development / Database)
File: machine-learning-functions.md

slug: /en/sql-reference/functions/machine-learning-functions sidebar_position: 115 sidebar_label: Machine Learning Prediction using fitted regression models uses `evalMLMethod` function. See link in `linearRegression`. The aggregate function implements stochastic gradient descent method using linear model and MSE loss function. Uses `evalMLMethod` to predict on new data. The aggregate function implements stochastic gradient descent method for binary classification problem. Uses `evalMLMethod` to predict on new data.
Project: zot (Provisioning / Container Registry)
File: pprof.md

This project gives the user the posibility to debug and profile the runtime to find relevant data such as CPU intensive function calls. An in-depth article on profiling in Go can be found . A call to http://localhost:8080/v2/_zot/pprof/ would list the following available profiles, wrapped in an HTML file, with count values prior to change due to the runtime: ``` Types of profiles available: Count Profile 95 allocs 0 block 0 cmdline 11 goroutine 95 heap 0 mutex 0 profile 13 threadcreate 0 trace full goroutine stack dump ``` For example, the following can be used to gather the cpu profile for the amount of seconds specified as a query parameter, and then the results are stored in `cpu.prof` file: ``` curl -sK -v http://localhost:8080/v2/_zot/pprof/profile?seconds=30 > cpu.prof ``` Then, the user can use the `go tool pprof` to analyze the information generated previously in `cpu.prof`. The following command boots up an http server with a GUI and multiple charts that represent the data. ``` go tool pprof -http=:9090 cpu.prof ``` A flamegraph example would look like the following: <img src="flamegraph.png" height="50%">
Project: KICS (Provisioning / Security & Compliance)
File: 2f01fb2d-828a-499d-b98e-b83747305052.md

title: No Stack Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2f01fb2d-828a-499d-b98e-b83747305052 Query name: No Stack Policy Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: AWS CloudFormation Stack should have a stack policy in order to protect stack resources from update actions<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awscloudformationstack" "positive1" { name = "networking-stack" parameters = { VPCCidr = "10.0.0.0/16" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awscloudformationstack" "negative1" { name = "networking-stack" parameters = { VPCCidr = "10.0.0.0/16" } policy_url = "somepolicyurl" } resource "awscloudformationstack" "negative2" { name = "networking-stack" parameters = { VPCCidr = "10.0.0.0/16" } policy_body = "somepolicy" } ```
Project: ClickHouse (App Definition and Development / Database)
File: v23.3.12.11-lts.md

sidebar_position: 1 sidebar_label: 2023 Fix async insert with deduplication for ReplicatedMergeTree using merging algorithms (). Fix deadlock on DatabaseCatalog shutdown (). Fix crash in join on sparse column (). Fix rowsbeforelimitatleast for DelayedSource. (). Fix broken `02862sorteddistinctsparsefix` ().
Project: KICS (Provisioning / Security & Compliance)
File: 60bfbb8a-c72f-467f-a6dd-a46b7d612789.md

title: ECR Image Tag Not Immutable hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 60bfbb8a-c72f-467f-a6dd-a46b7d612789 Query name: ECR Image Tag Not Immutable Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: ECR should have an image tag be immutable. This prevents image tags from being overwritten.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2 7" name: create immutable ecr-repo community.aws.ecs_ecr: name: super/cool name: create immutable ecr-repo v2 community.aws.ecs_ecr: name: super/cool imagetagmutability: mutable ``` ```yaml title="Negative test num. 1 - yaml file" name: create immutable ecr-repo v4 community.aws.ecs_ecr: name: super/cool imagetagmutability: immutable ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_backend_services.md

+++ title = "googlecomputebackend_services resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputebackend_services" identifier = "inspec/resources/gcp/googlecomputebackendservices.md googlecomputebackendservices resource" parent = "inspec/resources/gcp" +++ A `googlecomputebackend_services` is used to test a Google BackendService resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputebackend_services(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } its('names') { should include 'inspec-gcp-backend-service' } its('port_names') { should include 'http' } its('protocols') { should include 'HTTP' } its('timeout_secs') { should include '10' } end ``` Properties that can be accessed from the `googlecomputebackend_services` resource: See the resource for more information. `affinitycookiettl_secs` : an array of `googlecomputebackendservice` affinitycookiettlsec `backends` : an array of `googlecomputebackend_service` backends `circuit_breakers` : an array of `googlecomputebackendservice` circuitbreakers `consistent_hashes` : an array of `googlecomputebackendservice` consistenthash `cdn_policies` : an array of `googlecomputebackendservice` cdnpolicy `connection_drainings` : an array of `googlecomputebackendservice` connectiondraining `creation_timestamps` : an array of `googlecomputebackendservice` creationtimestamp `customrequestheaders` : an array of `googlecomputebackendservice` customrequest_headers `fingerprints` : an array of `googlecomputebackend_service` fingerprint `descriptions` : an array of `googlecomputebackend_service` description `enable_cdns` : an array of `googlecomputebackendservice` enablecdn `health_checks` : an array of `googlecomputebackendservice` healthchecks `ids` : an array of `googlecomputebackend_service` id `iaps` : an array of `googlecomputebackend_service` iap `loadbalancingschemes` : an array of `googlecomputebackendservice` loadbalancing_scheme `localitylbpolicies` : an array of `googlecomputebackendservice` localitylb_policy `names` : an array of `googlecomputebackend_service` name `outlier_detections` : an array of `googlecomputebackendservice` outlierdetection `port_names` : an array of `googlecomputebackendservice` portname `protocols` : an array of `googlecomputebackend_service` protocol `security_policies` : an array of `googlecomputebackendservice` securitypolicy `session_affinities` : an array of `googlecomputebackendservice` sessionaffinity `timeout_secs` : an array of `googlecomputebackendservice` timeoutsec `log_configs` : an array of `googlecomputebackendservice` 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: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-clusterby.md

layout: global title: CLUSTER BY Clause displayTitle: CLUSTER BY Clause license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. The `CLUSTER BY` clause is used to first repartition the data based on the input expressions and then sort the data within each partition. This is semantically equivalent to performing a followed by a . This clause only ensures that the resultant rows are sorted within each partition and does not guarantee a total order of output. ```sql CLUSTER BY { expression [ , ... ] } ``` expression* Specifies combination of one or more values, operators and SQL functions that results in a value. ```sql CREATE TABLE person (name STRING, age INT); INSERT INTO person VALUES ('Zen Hui', 25), ('Anil B', 18), ('Shone S', 16), ('Mike A', 25), ('John A', 18), ('Jack N', 16); -- Reduce the number of shuffle partitions to 2 to illustrate the behavior of `CLUSTER BY`. -- It's easier to see the clustering and sorting behavior with less number of partitions. SET spark.sql.shuffle.partitions = 2; -- Select the rows with no ordering. Please note that without any sort directive, the results -- of the query is not deterministic. It's included here to show the difference in behavior -- of a query when `CLUSTER BY` is not used vs when it's used. The query below produces rows -- where age column is not sorted. SELECT age, name FROM person; ++-+ |age| name| ++-+ | 16|Shone S| | 25|Zen Hui| | 16| Jack N| | 25| Mike A| | 18| John A| | 18| Anil B| ++-+ -- Produces rows clustered by age. Persons with same age are clustered together. -- In the query below, persons with age 18 and 25 are in first partition and the -- persons with age 16 are in the second partition. The rows are sorted based -- on age within each partition. SELECT age, name FROM person CLUSTER BY age; ++-+ |age| name| ++-+ | 18| John A| | 18| Anil B| | 25|Zen Hui| | 25| Mike A| | 16|Shone S| | 16| Jack N| ++-+ ```
Project: Meshery (Provisioning / Automation & Configuration)
File: aks.md

layout: page title: AKS permalink: installation/kubernetes/aks type: installation category: kubernetes redirect_from: installation/platforms/aks display-title: "false" language: en list: include image: /assets/img/platforms/aks.svg abstract: Manage your AKS clusters with Meshery. Deploy Meshery in AKS in-cluster or out-of-cluster. <h1>Quick Start with {{ page.title }} <img src="{{ page.image }}" style="width:35px;height:35px;" /></h1> Manage your AKS clusters with Meshery. Deploy Meshery in AKS or outside of AKS . _Note: It is advisable to _ <div class="prereqs"><h4>Prerequisites</h4> <ol> <li>Install the Meshery command line client, <a href="{{ site.baseurl }}/installation/mesheryctl" class="meshery-light">mesheryctl</a>.</li> <li>Install <a href="https://kubernetes.io/docs/tasks/tools/">kubectl</a> on your local machine.</li> <li>Install <a href="https://learn.microsoft.com/en-us/cli/azure/install-azure-cli">Azure CLI</a>, configured for your environment.</li> <li>Access to an active AKS cluster in one of your resource groups.</li> </ol> </div> Also see: - - - Follow the steps below to install Meshery in your AKS cluster. Read through the following considerations prior to deploying Meshery on AKS. Verify you connection to an Azure Kubernetes Services Cluster using Azure CLI. Login to Azure account using . After a successful login, identify the subscription associated with your AKS cluster: {% capture codecontent %} az account set --subscription [SUBSCRIPTIONID] {% endcapture %} {% include code.html code=code_content %} After setting the subscription, set the cluster context. {% capture codecontent %}az aks get-credentials --resource-group [RESOURCEGROUP] --name [AKSSERVICENAME]{% endcapture %} {% include code.html code=code_content %} Use Meshery's CLI to streamline your connection to your AKS cluster. Configure Meshery to connect to your AKS cluster by executing: {% capture code_content %}$ mesheryctl system config aks{% endcapture %} {% include code.html code=code_content %} Once configured, execute the following command to start Meshery. {% capture code_content %}$ mesheryctl system start{% endcapture %} {% include code.html code=code_content %} If you encounter any authentication issues, you can use `mesheryctl system login`. For more information, click to learn more. For detailed instructions on installing Meshery using Helm V3, please refer to the guide. Optionally, you can verify the health of your Meshery deployment, using <a href='/reference/mesheryctl/system/check'>mesheryctl system check</a>. You're ready to use Meshery! Open your browser and navigate to the Meshery UI. {% include_cached installation/accessing-meshery-ui.md display-title="true" %} {% include related-discussions.html tag="meshery" %}
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: documentation.md

name: " Documentation" about: Suggest an update for devfile documentation title: '' labels: '' assignees: '' /area documentation <!-- Uncomment appropriate `/area` lines, and delete the rest. For example, `> /area api` would simply become: `/area api` --> /area ci /area api /area library /area registry /area alizer /area devworkspace /area integration-tests /area test-automation /area releng /area landing-page <!-- Provide a clear and concise description of the changes you are suggesting --> What mistake did you find / what is missing in the documentation?