cwielenb/CNCF-Dataset huggingface dataset:
Project: Tetragon (Provisioning / Security & Compliance)
File: making-changes.md

title: "Making changes" weight: 2 description: "Learn how to make your first changes to the project" Make sure the main branch of your fork is up-to-date: ```shell git fetch upstream git checkout main git merge upstream/main ``` For further reference read documentation. Create a PR branch with a descriptive name, branching from main: ```shell git switch -c pr/${GITHUBUSERNAMEOR_ORG}/changes-to-something main ``` Make the changes you want. Separate the changes into logical commits. Describe the changes in the commit messages. Focus on answering the question why the change is required and document anything that might be unexpected. If any description is required to understand your code changes, then those instructions should be code comments instead of statements in the commit description. For submitting PRs, all commits need to be signed off `(git commit -s)`. See the section Make sure your changes meet the following criteria: New code is covered by Integration Testing. End to end integration / runtime tests have been extended or added. If not required, mention in the commit message what existing test covers the new code. Follow-up commits are squashed together nicely. Commits should separate logical chunks of code and not represent a chronological list of changes. Run `git diff --check` to catch obvious white space violations Build Tetragon with your changes included. See how to . See how to .
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-330.md

The `org.apache.pulsar.client.admin.Topics` provides `getMessageById(java.lang.String, long, long)` method to get the message, which returns one message. If the message id refers to a batch message, we can only get the first message, not all messages. This behavior affects our analysis of messages by the message id. Add a method that returns all messages by message id to the `org.apache.pulsar.client.admin.Topics` interface. Add a set of methods to the `org.apache.pulsar.client.admin.Topics` interface: ```java public interface Topics { List<Message<byte[]>> getMessagesById(String topic, long ledgerId, long entryId) throws PulsarAdminException; CompletableFuture<List<Message<byte[]>>> getMessagesByIdAsync(String topic, long ledgerId, long entryId); } ``` Deprecate the following methods in the `org.apache.pulsar.client.admin.Topics` interface: ```java public interface Topics { / @deprecated Use {@link #getMessagesById(String, long, long)} instead. */ @Deprecated Message<byte[]> getMessageById(String topic, long ledgerId, long entryId) throws PulsarAdminException; / @deprecated Use {@link #getMessagesByIdAsync(String, long, long)} instead. */ @Deprecated CompletableFuture<Message<byte[]>> getMessageByIdAsync(String topic, long ledgerId, long entryId); } ``` This PIP doesn't change the output of `bin/pulsar-admin topics get-message-by-id`, which still outputs one message. Mailing List discussion thread: https://lists.apache.org/thread/vqyh3mvtvovd383sd8zxnlzsspdr863z Mailing List voting thread: https://lists.apache.org/thread/n1f91v46tct6o5o72pd53hcyvr9xx9qr
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.43.md

layout: release date: 2023-01-13 tag: v0.6.43 language: en [Conversion] name, namespace, labels and annotations as root field @Abhishek-kumar09 (#6878) [MeshModel] Fix problem with #6875 @sudo-NithishKarthik (#6876) [MeshModel] Update API Routes to Allow Optional URL Vars @sudo-NithishKarthik (#6875) [mesheryctl] improve error message shown to users for "mesheryctl system channel" command #6274 @devkapilbansal (#6430) [Playground] Redirect to playground based on capabilities, remove multiple api calls for capability query @Abhishek-kumar09 (#6879) correction in numbering of steps @AnnuCode (#6874) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @AnnuCode, @Revolyssup, @alphaX86, @devkapilbansal, @leecalcote and @sudo-NithishKarthik
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-workspace.md

layout: default title: mesheryctl-exp-workspace permalink: reference/mesheryctl/exp/workspace redirect_from: reference/mesheryctl/exp/workspace/ type: reference display-title: "false" language: en command: exp subcommand: workspace View list of workspaces and detail of workspaces View list of workspaces and detailed information of a specific workspaces <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp workspace [flags] </div> </pre> To view a list workspaces <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp workspace list --orgId [orgId] </div> </pre> To create a workspace <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp workspace create --orgId [orgId] --name [name] --description [description] </div> </pre> Documentation for workspace can be found at: <pre class='codeblock-pre'> <div class='codeblock'> https://docs.layer5.io/cloud/spaces/workspaces/ </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for workspace </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Meshery (Provisioning / Automation & Configuration)
File: flux.md

layout: integration title: Flux subtitle: Collaborative and visual infrastructure as code for Flux image: /assets/img/integrations/flux/icons/color/flux-color.svg permalink: extensibility/integrations/flux docURL: https://docs.meshery.io/extensibility/integrations/flux description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery 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: Apache Heron (App Definition and Development / Streaming & Messaging)
File: client-api-docs-overview.md

id: version-0.20.0-incubating-client-api-docs-overview title: Client API Docs sidebar_label: Client API Docs original_id: client-api-docs-overview <!-- 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. --> You can view JavaDocs You can view Pydocs
Project: Rudder (Provisioning / Security & Compliance)
File: SECURITY.md

Our , all linked to the main `rudder` repository. You can report any security vulnerability affecting Rudder sources, packages, or infrastructure (repositories, websites, etc.) you have found by contacting the Rudder security team either: By email at You can encrypt your messages using our (fingerprint: `340C 9645 2F9A 816C 330A 99B7 C854 668E 3617 3DB3`) By using on GitHub If you have not received a reply to your report within 48 hours, you can ask for updates on our . As it is a public channel, please don't discuss specific details there, simply say you are waiting for a response from the security team. Security issues are treated in priority. Depending on its severity, an issue may be fixed in the next planned patch release or trigger a quick dedicated patch release. When the fixed version is published, we mention the presence of security fixes (without specifics) in the change log. We later publish a detailed advisory, after an embargo period which depends on the vulnerability severity (but never more than 3 months). The list of currently supported versions, receiving security updates, is available .
Project: Chef InSpec (Provisioning / Security & Compliance)
File: cran.md

+++ title = "cran resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "cran" identifier = "inspec/resources/os/cran.md cran resource" parent = "inspec/resources/os" +++ Use the `cran` Chef InSpec audit resource to test R modules that are installed from CRAN package repository. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.43.5 of InSpec. A `cran` resource block declares a package and (optionally) a package version: describe cran('package_name') do it { should be_installed } end where `'package_name'` is the name of the package, such as `'DBI'` `be_installed` tests to see if the package described above is installed The following examples show how to use this Chef InSpec audit resource. describe cran('DBI') do it { should be_installed } end describe cran('DBI') do it { should be_installed } its('version') { should eq '0.5.1' } end The `version` property tests if the named package version is on the system: its('version') { should eq '1.2.3' } This Chef InSpec audit resource has the following matchers: The `be_installed` matcher tests if the named package is installed on the system: it { should be_installed }
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_delete-account.md

title: kbcli cluster delete-account Delete account for a cluster ``` kbcli cluster delete-account [flags] ``` ``` kbcli cluster delete-account CLUSTERNAME --component COMPNAME --name USERNAME kbcli cluster delete-account CLUSTERNAME --name USERNAME kbcli cluster delete-account --instance INSTANCE --name USERNAME ``` ``` --auto-approve Skip interactive approval before deleting account --component string Specify the name of component to be connected. If not specified, pick the first one. -h, --help help for delete-account -i, --instance string Specify the name of instance to be connected. --name string Required user name, please specify it. ``` ``` --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/.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 --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 --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 ``` - Cluster command.
Project: SPIFFE (Provisioning / Key Management)
File: volunteers.md

This page lists members of the SPIFFE community who have signalled a willigness to represent the SPIFFE project at various public fora, which may include public events (such as KubeCon maintainers talks or conference booths), virtual events (such as CNCF Webinars), or other events. Some notes: If you are coordinating an event and looking for a speaker or other support on SPIFFE, feel free to reach out to any of those listed below. Inclusion on this list is for the convienence of event organizers, and does not imply a commitment by any of the speakers to participate in any particular event.* While we strive to ensure all speakers listed below respect and closely follow our , and will remove those that do not, inclusion in this list does not represent an endorsement of that individual from the SPIFFE community. Please conduct your own due diligence before inviting anyone from this list to an event.* | Who | Contact | Location | Preferred speaking topics | Preferred duties | Volunteer Notes | | | - | -- | - | - | | | Andrew Jessup | | Ann Arbor, USA | Introduction, project history, use cases | Webinars, Speaking or supporting local events | | Daniel Feldman | | Minneapolis, USA | Please ask | Please ask | | Andrew Moore | | Seattle, USA | Introduction, use cases, operational experience | Webinars, Speaking | | Sunil Ravipati | - | Santa Clara, USA | Please ask | Please ask | | Matthew Bates | | UK | Please ask | Please ask | | Andrew Martin | | London, UK | Security, consulting, training, operational experience, use cases | Webinars, speaking or supporting local events | | Ric Featherstone | | UK | Security, consulting, training, operational experience, use cases | Webinars, speaking or supporting local events | | James Callaghan | | UK | Security, consulting, training, operational experience, use cases | Webinars, speaking or supporting local events | | Eli Nesterov | | SF Bay Area, USA | Anything from history, use cases, architecture, produciton use, scalability, integraiton, federation, etc... | Speaking, organizing or supporting events. | In addition to the speakers listed below, you may wish to reach out to on the SPIFFE Slack Workspace. To add yourself to, or remove yourself from, this list, submit a pull request to modify this page. If you are nominating someone else, please be sure to demonstrate you have their permission.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.10.2.md

This release does not address any known issue. The Dapr 1.10.1 hotfix contained additional commits from the `master` branch that were not part of the 1.10 release branch. The 1.10.2 hotfix guarantees that all changes in the release are tested and validated. There are no known issues or regressions. The impact is having additional code changes in the 1.10.1 version that did not go through proper release tests. The v1.10.1 tag pulled in additional code changes from the `master` branch, that were not scheduled to be included in the 1.10.x release. We are releasing Dapr v1.10.2 with the correct set of changes from the Dapr 1.10 branch. Dapr 1.10.1 artifacts will be deleted.
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.10.43-lts.md

sidebar_position: 1 sidebar_label: 2024 Backported in : Add `SYSTEM JEMALLOC PURGE` for purging unused jemalloc pages, `SYSTEM JEMALLOC (). Backported in : Copy S3 file GCP fallback to buffer copy in case GCP returned `Internal Error` with `GATEWAY_TIMEOUT` HTTP error code. (). Backported in : If you want to run initdb scripts every time when ClickHouse container is starting you shoud initialize environment varible CLICKHOUSEALWAYSRUNINITDBSCRIPTS. (). Background merges correctly use temporary data storage in the cache (). MergeTree mutations reuse source part index granularity (). Fix double destroy call on exception throw in addBatchLookupTable8 (). Fix JSONExtract function for LowCardinality(Nullable) columns (). Fix: LIMIT BY and LIMIT in distributed query (). Fix translate() with FixedString input (). Fix error "Read beyond last offset" for AsynchronousBoundedReadBuffer (). Fix query start time on non initial queries (). Fix leftPad / rightPad function with FixedString input (). rabbitmq: fix having neither acked nor nacked messages (). Fix cosineDistance crash with Nullable (). Fix rare race in external sort/aggregation with temporary data in cache (). Fix possible race in ManyAggregatedData dtor. (). Fix 02720rowpolicycolumnwith_dots (). Pin python dependencies in stateless tests (). Make ZooKeeper actually sequentialy consistent (). Remove broken test while we fix it ().
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: YDB (App Definition and Development / Database)
File: static-group-move.md

To decommission a {{ ydb-short-name }} cluster host that accommodates a part of a , you need to move the group to another host. {% include %} As an example, let's take a {{ ydb-short-name }} cluster where you set up and launched a on a host with `node_id:1`. This node serves a part of the static group. Fragment of the static group configuration: ```yaml ... blobstorageconfig: ... service_set: ... groups: ... rings: ... fail_domains: vdisk_locations: node_id: 1 path: /dev/vda pdisk_category: SSD ... ... ... ... ... ``` To replace `nodeid:1`, we to the cluster a new host with `nodeid:10` and a static node in it. To move a part of the static group from the `nodeid:1` host to the `nodeid:10` host: Stop the static cluster node on the host with `node_id:1`. {% include %} In the `config.yaml` configuration file, change `node_id`, replacing the ID of the removed host by the ID of the added host: ```yaml ... blobstorageconfig: ... service_set: ... groups: ... rings: ... fail_domains: vdisk_locations: node_id: 10 path: /dev/vda pdisk_category: SSD ... ... ... ... ... ``` Edit the `path` and `pdiskcategory` for the disk if these parameters are different on the host with `nodeid: 10`. Update the `config.yaml` configuration files for all the cluster nodes, including dynamic nodes. Use the procedure to restart all the static cluster nodes. Go to the Embedded UI monitoring page and make sure that the VDisk of the static group is visible on the target physical disk and its replication is in progress. For details, see . Use the procedure to restart all the dynamic cluster nodes.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: natwest.md

title: "NatWest" icon: /images/logos/powered-by/natwest.png hasLink: "https://www.natwest.com/corporates.html" <!-- 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. -->