cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-pyspark-pandas-with-arrow.md

layout: global title: PySpark Usage Guide for Pandas with Apache Arrow displayTitle: PySpark Usage Guide for Pandas with Apache Arrow 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 Arrow usage guide is now archived on .
Project: ClickHouse (App Definition and Development / Database)
File: v22.10.7.13-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Another fix for `Cannot read all data` error which could happen while reading `LowCardinality` dictionary from remote fs. Fixes . (). Backported in : Fix `SELECT ... FROM system.dictionaries` exception when there is a dictionary with a bad structure (e.g. incorrect type in xml config). (). Automatically merge green backport PRs and green approved PRs (). Improve release scripts (). Fix wrong approved_at, simplify conditions (). Get rid of artifactory in favor of r2 + ch-repos-manager ().
Project: FOSSA (Provisioning / Security & Compliance)
File: pomxml.md

Maven projects use `pom.xml` files to declare dependencies and multi-project relationships. In a multi-project maven structure, sub-projects usually inherit dependencies, or can reference other sub-projects as dependencies. Do a complete directory traversal looking for files named `pom.xml`. There's no guarantee that a maven pom will be called `pom.xml`. To accomodate for this, we use `<relativePath>` directives in `<parent>` declarations to include additional poms. poms are linked together by their `<parent>` references into multi-project projects. Each project in the single- or multi-project structure has its pom information overlayed on top of parent poms, and a dependency graph is gathered from each project. We have limited support for naive `${property}` interpolation.
Project: Hazelcast IMDG (App Definition and Development / Database)
File: bug_report.md

name: Bug about: Create a report to help us improve labels: 'Type: Defect' <!-- Thanks for reporting your issue. Please share with us the following information, to help us resolve your issue quickly and efficiently. --> Describe the bug A clear and concise description of what the bug is. Expected behavior A clear and concise description of what you expected to happen. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' ... Additional context <!-- Add any other context about the problem here. Common details that we're often interested in: Detailed description of the steps to reproduce your issue Logs and stack traces, if available Hazelcast version that you use (e.g. 3.4, also specify whether it is a minor release or the latest snapshot) If available, integration module versions (e.g. Tomcat, Jetty, Spring, Hibernate). Also, include their detailed configuration information such as web.xml, Hibernate configuration and `context.xml` for Spring Cluster size, i.e. the number of Hazelcast cluster members Number of the clients Version of Java. It is also helpful to mention the JVM parameters Operating system. If it is Linux, kernel version is helpful Unit test with the `hazelcast.xml` file. If you could include a unit test which reproduces your issue, we would be grateful -->
Project: Chef Infra (Provisioning / Automation & Configuration)
File: RESOURCE_REQUEST.md

name: Resource Request about: I have a suggestion for a new resource in Chef (and may want to implement it )! labels: "Status: Untriaged" Before suggesting a resource for inclusion please make sure your suggestion meets these criteria for resources built into Chef: [ ] Automates an operating system component that ships by default on systems such as authentication, raid, disk partitions, firewalls, containers, or virtualization systems. [ ] Does not attempt automate 3rd party applications such as database, web, or application servers, which are best suited for cookbooks due to their fast moving nature. <! Tell us about the resource --> <! Why do you believe this is best suited to be included in the chef-client vs. a cookbook? --> <! Is this a general purpose resource that would run on every operating systems or is it specific to an OS such as Linux, macOS, or Windows? --> <! Is there currently a cookbook that ships with this resource? If so please let us know. We'll need full permission from the authors and a compatible license in order to move a resource from a cookbook. --> <! The best way to move a resource into Chef is to help move it yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->
Project: CloudMatos (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. Examples of behavior that contributes to a positive environment for our community include: Demonstrating empathy and kindness toward other people Being respectful of differing opinions, viewpoints, and experiences Giving and gracefully accepting constructive feedback Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: The use of sexualized language or imagery, and sexual attention or advances of any kind Trolling, insulting or derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or email address, without their explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at . All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. This Code of Conduct is adapted from the , version 2.1, available at . For answers to common questions about this code of conduct, see the FAQ at . Translations are available at .
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: RELEASES.md

| Specification Group | Version | Release Date | Release Notes | | : | :--: | :-- | :--: | | CloudEvents | | 2022/02/05 | | | CloudEvents | | 2020/12/12 | | | CloudEvents | | 2019/10/24 | | | CloudEvents | | 2019/06/13 | | | CloudEvents | | 2018/12/06 | | | CloudEvents | | 2018/04/20 | |
Project: YDB (App Definition and Development / Database)
File: count_distinct_estimate.md

Approximating the number of unique values using the algorithm. Logically, it does the same thing as , but runs much faster at the cost of some error. Arguments: Estimated value Accuracy (4 to 18 inclusive, 14 by default). By selecting accuracy, you can trade added resource and RAM consumption for decreased error. All the three functions are aliases at the moment, but `CountDistinctEstimate` may start using a different algorithm in the future. Examples ```yql SELECT CountDistinctEstimate(my_column) FROM my_table; ``` ```yql SELECT HyperLogLog(my_column, 4) FROM my_table; ```
Project: ArangoDB (App Definition and Development / Database)
File: limitations.md

+++ title = "Limitations" description = "" weight = 10 +++ C++ has excellent two-way compatibility with the C ABI, but there are some limitations you must observe to write C++ code which C code can call without marshalling at the ABI boundary: A C++ function may not throw exceptions if it is safe to call from C, and so should always be marked `noexcept`. A C++ function should be annotated with `extern "C"` to prevent its symbol being mangled, and thus give it the C rather than C++ ABI. You cannot use overloading in your `extern "C"` functions. You may only use types in your C++ function declaration for which these traits are both true: - (Note that `std::istriviallycopyable_v<T>` requires trivial destruction, but NOT trivial construction. This means that C++ can do non-trivial construction of otherwise trivial types) The above is what the standard officially requires for well defined C and C++ interop. However, all of the three major compilers MSVC, GCC and clang are considerably more relaxed. In those three major compilers, "almost-standard-layout" C++ types work fine in C. "Almost-standard-layout" C++ types have these requirements: No virtual functions or virtual base classes i.e. must be false. This is because the vptrs offset the proper front of the data layout in an unknowable way to C. Non-static data members of reference type appear to C as pointers. You must never supply from C to C++ a non-null pointer which is seen as a reference in C++. C++ inheritance is seen in C data layout as if the most derived class has nested variables of the inherited types at the top, in order of inheritance. Types with non-trivial destructors work fine so long as at least move construction and assignment is the same as copying bits like `memcpy()`. You just need to make sure instances of the type return to C++, and don't get orphaned in C. This was referred to in previous pages in this section as "move relocating" types. Experimental Outcome's support for being used from C does not meet the current strict requirements, and thus relies on the (very common) implementation defined behaviour just described (it is hoped that future C++ standards can relax the requirements to those just described). Specifically, proposed `status_code` is an almost-standard-layout type, and thus while it can't be returned from `extern "C"` functions as the compiler will complain, it is perfectly safe to return from C++ functions to C code on the three major compilers, as it is an "almost-standard-layout" C++ type if `T` is an "almost-standard-layout" C++ type.
Project: Teleport (Provisioning / Security & Compliance)
File: 0045-ssh_session-where-condition.md

authors: Andrej Tokark (andrej@goteleport.com) state: implemented Manage access to active sessions (resource kind `ssh_session`) by RBAC `where` conditions, in the same manner as the RFD 44 *RBAC `where` conditions for session recordings list/read* provides access management for session recordings (resource kind `session`). These deny checks are to be employed on top of the new RBAC rules for listing and joining sessions introduced in . This means that the user must pass both the resource checks introduced in this RFD and the RBAC `join_policy` checks from RFD 43 in order to join a session. To be able to restrict access of certain users to only a subset of active sessions, notably only their own active sessions. Unlike `session`, the `ssh_session` kind is referred to by an [implicit rule]( https://github.com/gravitational/teleport/blob/066f0dbbad801ad822b81482948732641773d8fe/lib/services/role.go#L57) granting unrestricted list/read privileges to all users: ```go types.NewRule(types.KindSSHSession, RO()), ``` Adding a `where` section to an explicit allow rule for `ssh_session` would therefore take no effect. To restrict access to active sessions, one has to add (the negation of) the desired condition to a deny rule, as those are applied earlier than allow rules: ```yaml spec: deny: rules: resources: [ssh_session] verbs: [list, read] where: '!contains(ssh_session.participants, user.metadata.name)' ``` The `ssh_session` identifier exposes the private `lib.session.ctxSession` struct. `ctxSession` is a subset of [`session.Session`]( https://github.com/gravitational/teleport/blob/066f0dbbad801ad822b81482948732641773d8fe/lib/session/session.go#L84) with the addition of the `participants` field. In general, the RBAC `contains` predicate can only be used to detect the occurrence of a string in a slice of strings. However, the `Parties` field of `session.Session` is a slice of more complex `Party` objects, not strings. To support `where` conditions as above, a list of usernames is extracted from the original `Party` slice in order that the usernames be then bound to `ssh_session.participants` instead.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: filesystem.md

+++ title = "filesystem resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "filesystem" identifier = "inspec/resources/os/filesystem.md filesystem resource" parent = "inspec/resources/os" +++ Use the `filesystem` Chef InSpec resource to audit filesystem disk space usage. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.51.0 of InSpec. The `freekb`, `sizekb`, and `type` properties became available in v3.6 of InSpec. Versions of this resource in Chef InSpec prior to 3.5.x offered a property `size`, which returned a value in GB when on Windows and a value in KB on Linux, though it was documented to always return KB. All new code should use `size_kb` which is unit-stable. The property `size` will remain available in Chef InSpec v3 and 4, but will be deprecated in the future. A `filesystem` resource block declares tests for disk space in a partition: describe filesystem('/') do its('size_kb') { should be >= 32 1024 1024} its('free_kb') { should be >= 50 * 1024 } its('percent_free') { should be >= 20 } its('type') { should cmp 'ext4' } end where `filesystem('/')` states that the resource will look at the root (/) partition. `size_kb` is the total partition size and is measured in kilobytes (KB). `free_kb` is the available space on the partition and is measured in kilobytes (KB). `percent_free` is the percentage of available free space, and ranges from 0 to 100. The `size_kb` property returns the total partition size in kb. its('size_kb') { should be >= 32000 } The `free_kb` property returns the size of available space on the partition in kb. its('size_kb') { should be >= 32000 } The `percent_free` property returns the available free space on the partition, ranges from 0 to 100. its('percent_free') { should be >= 20 } The `type` property returns the type of the file system. its('type') { should cmp 'NTFS' } describe filesystem('/') do its('size_kb') { should be >= 32000 } end describe filesystem('/') do its('free_kb') { should be >= 5000000 } end Note that Windows filesystems (drives) are referred to without any slashes: describe filesystem('c:') do its('type') { should cmp 'NTFS' } end describe filesystem('/var') do its('percent_free') { should be >= 20 } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Strimzi (App Definition and Development / Streaming & Messaging)
File: README-s390x.md

Nightly builds will be running on s390x VM to build the artifacts and run `acceptance` profile of system test on master branch at 12:00 am EST each day. The below link can be used to access the Jenkins builds on s390x VMs: https://148.100.84.211/job/strimzi-kafka-operator/job/StrimziKafkaOperator_ST/ **Note: This link may change in the future.**
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

<!-- PR title format should be . Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review. Each pull request should address only one issue, not mix up code from multiple issues. Each commit in the pull request has a meaningful commit message Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below. --> <!-- Either this PR fixes an issue, --> Fixes #xyz <!-- or this PR is one task of an issue --> Main Issue: #xyz <!-- If the PR belongs to a PIP, please add the PIP link here --> PIP: #xyz <!-- Details of when a PIP is required and how the PIP process work, please see: https://github.com/apache/pulsar/blob/master/pip/README.md --> <!-- Explain here the context, and why you're making that change. What is the problem you're trying to solve. --> <!-- Describe the modifications you've done. --> [ ] Make sure that the change passes the CI checks. (Please pick either of the following options) This change is a trivial rework / code cleanup without any test coverage. (or) This change is already covered by existing tests, such as (please describe tests). (or) This change added tests and can be verified as follows: (example:) Added integration tests for end-to-end deployment with large payloads (10MB) Extended integration test for recovery after broker failure <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> If the box was checked, please highlight the changes [ ] Dependencies (add or upgrade a dependency) [ ] The public API [ ] The schema [ ] The default values of configurations [ ] The threading model [ ] The binary protocol [ ] The REST endpoints [ ] The admin CLI options [ ] The metrics [ ] Anything that affects deployment <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> [ ] `doc` <!-- Your PR contains doc changes. --> [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> [ ] `doc-not-needed` <!-- Your PR changes do not impact docs --> [ ] `doc-complete` <!-- Docs have been already added --> PR in forked repository: <!-- ENTER URL HERE --> <!-- After opening this PR, the build in apache/pulsar will fail and instructions will be provided for opening a PR in the PR author's forked repository. apache/pulsar pull requests should be first tested in your own fork since the apache/pulsar CI based on GitHub Actions has constrained resources and quota. GitHub Actions provides separate quota for pull requests that are executed in a forked repository. The tests will be run in the forked repository until all PR review comments have been handled, the tests pass and the PR is approved by a reviewer. -->
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_ApiGatewayCustomAuthorizer.md

The following is a simple TOKEN authorizer example to demonstrate how to use an authorization token to allow or deny a request. In this example, the caller named "user" is allowed to invoke a request if the client-supplied token value is "allow". The caller is not allowed to invoke the request if the token value is "deny". If the token value is "Unauthorized", the function returns the "Unauthorized" error with an HTTP status code of 401. For any other token value, the authorizer returns an "Invalid token" error. This example is based on the from the API Gateway documentation ```go package main import ( "context" "errors" "strings" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" ) // Help function to generate an IAM policy func generatePolicy(principalId, effect, resource string) events.APIGatewayCustomAuthorizerResponse { authResponse := events.APIGatewayCustomAuthorizerResponse{PrincipalID: principalId} if effect != "" && resource != "" { authResponse.PolicyDocument = events.APIGatewayCustomAuthorizerPolicy{ Version: "2012-10-17", Statement: []events.IAMPolicyStatement{ { Action: []string{"execute-api:Invoke"}, Effect: effect, Resource: []string{resource}, }, }, } } // Optional output with custom properties of the String, Number or Boolean type. authResponse.Context = map[string]interface{}{ "stringKey": "stringval", "numberKey": 123, "booleanKey": true, } return authResponse } func handleRequest(ctx context.Context, event events.APIGatewayCustomAuthorizerRequest) (events.APIGatewayCustomAuthorizerResponse, error) { token := event.AuthorizationToken switch strings.ToLower(token) { case "allow": return generatePolicy("user", "Allow", event.MethodArn), nil case "deny": return generatePolicy("user", "Deny", event.MethodArn), nil case "unauthorized": return events.APIGatewayCustomAuthorizerResponse{}, errors.New("Unauthorized") // Return a 401 Unauthorized response default: return events.APIGatewayCustomAuthorizerResponse{}, errors.New("Error: Invalid token") } } func main() { lambda.Start(handleRequest) } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: approximatequantiles.md

title: "ApproximateQuantiles" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.stat" class="ApproximateQuantile" >}} {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_ApproximateQuantiles" show="approximatequantiles" >}} {{< /playground >}}
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.10.22-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix seeking while reading from encrypted disk. This PR fixes . (). Backported in : Fix reading of sparse columns from `MergeTree` tables that store their data in S3. (). Backported in : Fixed error `Not found column Type in block` in selects with `PREWHERE` and read-in-order optimizations. (). Backported in : Fix data race and possible heap-buffer-overflow in Avro format. Closes Closes . (). Backported in : Fix bug with maxsplit argument for splitByChar, which was not working correctly. (). Backported in : Fix `CANNOTREADALLDATA` exception with `localfilesystemreadmethod=pread_threadpool`. This bug affected only Linux kernel version 5.9 and 5.10 according to . (). Backported in : Fix performance regression of scalar query optimization. (). Backported in : Fix some issues with async reads from remote filesystem which happened when reading low cardinality. (). Replace MemoryTrackerBlockerInThread to LockMemoryExceptionInThread (). Change mysql-odbc url ().