cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2017-03-14-mesos-1-1-1-released.md

layout: post title: Apache Mesos 1.1.1 Released permalink: /blog/mesos-1-1-1-released/ published: true post_author: display_name: AlexR tags: Release The latest Mesos release, 1.1.1, is now available for . This release includes some important bug fixes and improvements on top of 1.1.0. It is highly recommended that users use this version if you are considering using Mesos 1.1. More specifically, this release includes the following major fixes and improvements: - The whiteout file cannot be removed correctly using aufs backend. - Docker registry puller shows decode error "No response decoded". - Frameworks may RESERVE for an arbitrary role. - The handling of whiteout files in provisioner is not correct. - Add documentation for CNI port-mapper plugin. - `mesos-containerizer launch --environment` exposes executor env vars in `ps`. - Add "--task" flag to mesos-execute - Include v1 Operator API protos in generated JAR and python packages. - Reject optimized builds with libcxx before 3.9 - SSL downgrade path will CHECK-fail when using both temporary and persistent sockets - Master WebUI does not work on Firefox 45 - Always re-link with scheduler during re-registration. - The default executor does not exit if a single task pod fails. - Nested container's launch command is not set correctly in docker/runtime isolator. - Segfault when the executor sets an invalid UUID when sending a status update. - Quota not recovered from registry in empty cluster. - mesos-fetcher fails with openssl-related output. Full release notes are available in the release Rolling upgrades from a Mesos 1.1.0 cluster to Mesos 1.1.1 are straightforward. Please refer to the for detailed information on upgrading to Mesos 1.1.1. We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the . Thanks to the 15 contributors who made 1.1.1 possible: Aaron Wood, Alexander Rukletsov, Anand Mazumdar, Avinash sridharan, Benjamin Bannier, Gastn Kleiman, Gilbert Song, Haosdent Huang, Jan Schlicht, Jiang Yan Xu, Jie Yu, Joseph Wu, Michael Park, Neil Conway, Qian Zhang, Till Toenshoff, Vijay Srinivasaraghavan, Vinod Kone, haosdent huang.
Project: k8gb (Orchestration & Management / Coordination & Service Discovery)
File: pull_request_template.md

.. <details> <summary>HOW TO RUN CI</summary> By default, all the checks will be run automatically. Furthermore, when changing website-related stuff, the preview will be generated by the netlify bot. Add the label on this PR if you want full-blown tests that include more than 2-cluster scenarios. If the test suite is failing for you, you may want to try triggering `Re-run all jobs` (top right) with enabled. It will also make the action more verbose. </details>
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: 'heimanba' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.13.1.md

#3410: fixes an issue where global rate limit policies defined at the virtual host level for TLS-secured `HTTPProxies` were being ignored #3412: fixes an issue where changes to the Envoy load balancer address were not immediately being reflected in `HTTPProxies'` status. #3417: updates Envoy from v1.17.0 to v1.17.1. See the for details.
Project: Gloo (Orchestration & Management / API Gateway)
File: matchable_tcp_gateway.proto.sk.md

title: "matchabletcpgateway.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Top-Level Resource A MatchableTcpGateway describes a single FilterChain configured with the TcpProxy network filter and a matcher. A Gateway CR may select one or more MatchableTcpGateways on a single listener. This enables separate teams to own Listener configuration (Gateway CR) and FilterChain configuration (MatchableTcpGateway CR). ```yaml "namespacedStatuses": .core.solo.io.NamespacedStatuses "metadata": .core.solo.io.Metadata "matcher": .gateway.solo.io.MatchableTcpGateway.Matcher "tcpGateway": .gateway.solo.io.TcpGateway ``` | Field | Type | Description | | -- | - | -- | | `namespacedStatuses` | | NamespacedStatuses indicates the validation status of this resource. NamespacedStatuses is read-only by clients, and set by gateway during validation. | | `metadata` | | Metadata contains the object metadata for this resource. | | `matcher` | | Matcher creates a FilterChainMatch and TransportSocket for a FilterChain For each MatchableTcpGateway on a Gateway CR, the matcher must be unique. If there are any identical matchers, the Gateway will be rejected. An empty matcher will produce an empty FilterChainMatch (https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/listener/v3/listener_components.proto#envoy-v3-api-msg-config-listener-v3-filterchainmatch) effectively matching all incoming connections. | | `tcpGateway` | | TcpGateway creates a FilterChain with a TcpProxy. | ```yaml "sourcePrefixRanges": []solo.io.envoy.config.core.v3.CidrRange "sslConfig": .gloo.solo.io.SslConfig "passthroughCipherSuites": []string ``` | Field | Type | Description | | -- | - | -- | | `sourcePrefixRanges` | | CidrRange specifies an IP Address and a prefix length to construct the subnet mask for a CIDR range. See https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/address.proto#envoy-v3-api-msg-config-core-v3-cidrrange. | | `sslConfig` | | Ssl configuration applied to the FilterChain, if using passthrough should not include secrets : - FilterChainMatch: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/listener/v3/listener_components.proto#config-listener-v3-filterchainmatch) - TransportSocket: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/base.proto#envoy-v3-api-msg-config-core-v3-transportsocket. | | `passthroughCipherSuites` | `[]string` | Enterprise-only: Passthrough cipher suites is an allow-list of OpenSSL cipher suite names for which TLS passthrough will be enabled. If a client does not support any ciphers that are natively supported by Envoy, but does support one of the ciphers in the passthrough list, then traffic will be routed via TCP Proxy to a destination specified by the TcpGateway, where TLS can then be terminated. | <!-- Start of HubSpot Embed Code --> <script type="text/javascript" id="hs-script-loader" async defer src="//js.hs-scripts.com/5130874.js"></script> <!-- End of HubSpot Embed Code -->
Project: Flomesh Service Mesh (FSM) (Orchestration & Management / Service Mesh)
File: SECURITY.md

This document outlines security procedures and general policies for the Flomesh Service Mesh open source project as found on https://github.com/flomesh-io/fsm. * IMPORTANT: Please do not open public issues on GitHub for security vulnerabilities The FSM team and community take all security vulnerabilities seriously. Thank you for improving the security of our open source software. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions. Report security vulnerabilities by emailing the FSM security team at: security@flomesh.io Please provide the following: Individual's identity and organization Detailed description of the issue and the consequences of the vulnerability Estimation of the attack surface 3rd party software, if any, used with FSM Detailed steps to reproduce the issue A maintainer will acknowledge your email and send a detailed response within 3 business days indicating the next steps in handling your report. After the initial reply to your report, the team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. Report potential security issues, or known security issues in a third party modules by opening a Github Issue. If you think you have found a vulnerability in a FSM project. Report potential security issues, or known security issues in a third party modules by opening a Github Issue. For guidance on securing FSM please open a or reach out on the FSM Slack Channel within the For guidance on applying security updates When the team receives a security bug report, they will assign it to someone to be a primary handler. This person will coordinate the fix and release process, involving the following steps: Confirm the problem and determine the affected versions. Audit code to find any potential similar problems. Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible. Inspired by the
Project: KEDA (Orchestration & Management / Scheduling & Orchestration)
File: MIGRATING.md

`github.com/Huawei/gophercloud/openstack/compute/v2/extensions/floatingip` is now `github.com/Huawei/gophercloud/openstack/compute/v2/extensions/floatingips` `floatingips.Associate` and `floatingips.Disassociate` have been removed. `floatingips.DisassociateOpts` is now required to disassociate a Floating IP. `secgroups.AddServerToGroup` is now `secgroups.AddServer`. `secgroups.RemoveServerFromGroup` is now `secgroups.RemoveServer`. `servers.Reboot` now requires a `servers.RebootOpts` struct: ```golang rebootOpts := &servers.RebootOpts{ Type: servers.SoftReboot, } res := servers.Reboot(client, server.ID, rebootOpts) ``` `Token.ExpiresAt` is now of type `gophercloud.JSONRFC3339Milli` instead of `time.Time`
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.7.1.md

+++ title = "CoreDNS-1.7.1 Release" description = "CoreDNS-1.7.1 Release Notes." tags = ["Release", "1.7.1", "Notes"] release = "1.7.1" date = 2020-09-21T10:00:00+00:00 author = "coredns" +++ The CoreDNS team has released . This is a small, incremental release that adds some polish and fixes a bunch of bugs. Ben Kochie, Ben Ye, Chris O'Haver, Cricket Liu, Grant Garrett-Grossman, Hu Shuai, Li Zhijian, Maxime Guyot, Miek Gieben, milgradesec, Oleg Atamanenko, Olivier Lemasle, Ricardo Katz, Ruslan Drozhdzh, Yong Tang, Zhou Hao, Zou Nengren. backend: fix root zone usage (https://github.com/coredns/coredns/pull/4039) core: Add timeouts for http server (https://github.com/coredns/coredns/pull/3920) pkg/upstream: set edns0 and Do when required (https://github.com/coredns/coredns/pull/4055) plugin/cache: cache: default to DNSSEC (https://github.com/coredns/coredns/pull/4085) plugin/{clouddns,route53}: fix lingering goroutines after restart (https://github.com/coredns/coredns/pull/4096) plugin/debug: Enable debug globally if enabled in any server config (https://github.com/coredns/coredns/pull/4007) plugin/{etcd,kubernetes}: fix root zone usage (https://github.com/coredns/coredns/pull/4039) plugin/forward: add hit/miss metrics for connection cache (https://github.com/coredns/coredns/pull/4114) plugin/forward: fix panic when `expire` is configured as 0s (https://github.com/coredns/coredns/pull/4115) plugin/forward: init ClientSessionCache in tls.Config (https://github.com/coredns/coredns/pull/4108) plugin/forward: Register HealthcheckBrokenCount (https://github.com/coredns/coredns/pull/4021) plugin/grpc: Improve gRPC Plugin when backend is not available (https://github.com/coredns/coredns/pull/3966) plugins: Using promauto package to ensure all created metrics are properly registered (https://github.com/coredns/coredns/pull/4025). plugin/template: Add client IP data (https://github.com/coredns/coredns/pull/4034) plugin/trace: fix struct allignment (https://github.com/coredns/coredns/pull/4112) plugin/trace: Only with debug* active enable debug mode for tracing - removes extra logging (https://github.com/coredns/coredns/pull/4016) project: Add DCO requirement in Contributing guidelines (https://github.com/coredns/coredns/pull/4008)
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.8.2.md

+++ title = "CoreDNS-1.8.2 Release" description = "CoreDNS-1.8.2 Release Notes." tags = ["Release", "1.8.2", "Notes"] release = "1.8.2" date = 2021-02-23T07:00:00+00:00 author = "coredns" +++ The CoreDNS team has released . This release includes a bunch of bugfixes and a few enhancements, see below. Bob, chantra, Chris O'Haver, Frank Riley, George Shammas, Johnny Bergstrm, Jun Chen, Lars Ekman, Manuel Rger, Maxime Ginters, Miek Gieben, slick-nic, TimYin. core: Also clear `do` and `size` (https://github.com/coredns/coredns/pull/4465) core: Flag blacklisting not needed anymore (https://github.com/coredns/coredns/pull/4420) core: Set http request in writer (https://github.com/coredns/coredns/pull/4445) Makefile.release: Replace manifest-tool with docker manifest (https://github.com/coredns/coredns/pull/4421) plugin/acl: add the ability to filter records (https://github.com/coredns/coredns/pull/4389) plugin/dnstap: Fix out of order messages and fix forward perspective. (https://github.com/coredns/coredns/pull/4395) plugin/forward Add rcode and rtype to requestdurationseconds metric (https://github.com/coredns/coredns/pull/4391) plugin/kubernetes: Corrected detection of K8s minor version (https://github.com/coredns/coredns/pull/4430) plugin/kubernetes: make kubeconfig argument 'context' optional (https://github.com/coredns/coredns/pull/4451) plugin/rewrite: copy msg before rewriting (https://github.com/coredns/coredns/pull/4443) plugin/rewrite: SRV targets and additional names in response (https://github.com/coredns/coredns/pull/4287) plugin/sign: track zone file's mtime (https://github.com/coredns/coredns/pull/4431) plugin/trace: Use compatible tag name for datadog (https://github.com/coredns/coredns/pull/4408) plugin/transfer: only allow outgoing axfr over tcp (https://github.com/coredns/coredns/pull/4452)
Project: Prefect (Orchestration & Management / Scheduling & Orchestration)
File: audit-log.md

description: Monitor user access and activity with Audit Logs in Prefect Cloud. tags: UI dashboard Prefect Cloud enterprise teams workspaces organizations audit logs compliance search: boost: 2 Prefect Cloud's offer enhanced compliance and transparency tools with Audit Log. Audit logs provide a chronological record of activities performed by members in your account, allowing you to monitor detailed Prefect Cloud actions for security and compliance purposes. Audit logs enable you to identify who took what action, when, and using what resources within your Prefect Cloud account. In conjunction with appropriate tools and procedures, audit logs can assist in detecting potential security violations and investigating application errors. Audit logs can be used to identify changes in: Access to workspaces User login activity User API key creation and removal Workspace creation and removal Account member invitations and removal Service account creation, API key rotation, and removal Billing payment method for self-serve pricing tiers See the to learn more about options for supporting audit logs. From your Pro or Custom account settings page, select the Audit Log page to view audit logs. Pro and Custom account tier admins can view audit logs for: Account-level events in Prefect Cloud, such as: Member invites Changing a members role Member login and logout of Prefect Cloud Creating or deleting a service account Workspace-level events in Prefect Cloud, such as: Adding a member to a workspace Changing a members workspace role Creating or deleting a workspace Admins can filter audit logs on multiple dimensions to restrict the results they see by workspace, user, or event type. Available audit log events are displayed in the Events drop-down menu. Audit logs may also be filtered by date range. Audit log retention period varies by .
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-05-12-mesos-0-22-1-released.md

layout: post title: Apache Mesos 0.22.1 Released permalink: /blog/mesos-0-22-1-released/ published: true post_author: display_name: Adam B tags: Release The latest Mesos release, 0.22.1 is now available for . This release includes fixes to containerizer recovery, sandbox permissions, and the Java and Python bindings. Also, certain fields of FrameworkInfo are now updated on reregistration. - Assertion failure in state abstraction crashes JVM. - AbstractState JNI check fails for Marathon framework. - Slave should provide details on processes running in its cgroups - Tasks getting stuck in staging. - The sandbox directory is not chown'ed if the fetcher doesn't run. - Tasks are not removed after recovery from slave and mesos containerizer - Update name, hostname, failovertimeout, and webuiurl in master on framework re-registration - Python scheduler driver disables implicit acknowledgments by default. - Slave fails to recover when there are still processes left in its cgroup Full release notes are available in the release . Upgrading to 0.22.1 can be done seamlessly on a 0.22.0 cluster. If upgrading from an earlier version, please refer to the documentation. Thanks to all the contributors for 0.22.1: Benjamin Hindman, Benjamin Mahler, Ian Downes, Jie Yu, Joris Van Remoortere, Niklas Nielsen, and Timothy Chen.
Project: Skipper (Orchestration & Management / Service Proxy)
File: route-string.md

Route string dataclient can be used to create simple demo applications, for example if you want to show traffic switching or ratelimiting or just need to serve some json in your demo. Serve with `Content-Type: text/plain; charset=utf-8` Example (Open your browser http://localhost:9090/): ``` skipper -inline-routes '* -> inlineContent("Hello, world!") -> <shunt>' ``` Docker Example (Open your browser http://localhost:9090/): ``` docker run -p 9090:9090 -it registry.opensource.zalan.do/teapot/skipper:latest skipper -inline-routes '* -> inlineContent("Hello, world!") -> <shunt>' ``` Serve with `Content-Type: text/html; charset=utf-8` Example (Open your browser http://localhost:9090/): ``` skipper -inline-routes '* -> inlineContent("<html><body style=\"background-color: orange;\"></body></html>") -> <shunt>' ``` Docker Example (Open your browser http://localhost:9090/): ``` docker run -p 9090:9090 -it registry.opensource.zalan.do/teapot/skipper:latest skipper -inline-routes '* -> inlineContent("<html><body style=\"background-color: orange;\"></body></html>") -> <shunt>' ``` Serve with `Content-Type: application/json; charset=utf-8` Example (Open your browser http://localhost:9090/): ``` skipper -inline-routes '* -> inlineContent("{\"foo\": 3}", "application/json; charset=utf-8") -> <shunt>' ``` Docker Example (Open your browser http://localhost:9090/): ``` docker run -p 9090:9090 -it registry.opensource.zalan.do/teapot/skipper:latest skipper -inline-routes '* -> inlineContent("{\"foo\": 3}", "application/json; charset=utf-8") -> <shunt>' ``` If you just have to build a workaround and you do not want to use socat to do a tcp proxy, but proxy http, you can do: ``` % skipper -inline-routes '* -> "https://my-new-backend.example.org/"' ```
Project: SOFARPC (Orchestration & Management / Remote Procedure Call)
File: CONTRIBUTING.md

SOFARPC is released under the Apache 2.0 license, and follows a very standard Github development process, using Github tracker for issues and merging pull requests into master. If you would like to contribute something, or simply want to hack on the code this document should help you get started. Before we accept a non-trivial patch or pull request we will need you to sign the Contributor License Agreement. Signing the contributors agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests. None of these is essential for a pull request, but they will all help. we provided a , it will formatting automatically your project when during process of building. Make sure all new `.java` files to have a simple Javadoc class comment with at least an `@author` tag identifying you, and preferably at least a paragraph on what the class is for. Add the ASF license header comment to all new `.java` files (copy from existing files in the project) Add yourself as an `@author` to the `.java` files that you modify substantially (more than cosmetic changes). Add some Javadocs. A few unit tests would help a lot as wellsomeone has to do it. When writing a commit message please follow , if you are fixing an existing issue please add Fixes gh-XXXX at the end of the commit message (where XXXX is the issue number).
Project: Prefect (Orchestration & Management / Scheduling & Orchestration)
File: testing.md

description: Learn about writing tests for Prefect flows and tasks. tags: testing unit testing development search: boost: 2 Learn how to write tests for Prefect flows and tasks. Prefect provides a simple context manager for unit tests that allows you to run flows and tasks against a temporary local SQLite database. ```python from prefect import flow from prefect.testing.utilities import prefecttestharness @flow def myfavoriteflow(): return 42 def testmyfavorite_flow(): with prefecttestharness(): assert myfavoriteflow() == 42 ``` For more extensive testing, use `prefecttestharness` as a fixture in your unit testing framework. For example, when using `pytest`: ```python from prefect import flow import pytest from prefect.testing.utilities import prefecttestharness @pytest.fixture(autouse=True, scope="session") def prefecttestfixture(): with prefecttestharness(): yield @flow def myfavoriteflow(): return 42 def testmyfavorite_flow(): assert myfavoriteflow() == 42 ``` !!! note Session scoped fixture In this example, the fixture is scoped to run once for the entire test session. In most cases, you will not need a clean database for each test. Just isolate your test runs to a test database. Creating a new test database per test creates significant overhead, so we recommend scoping the fixture to the session. If you need to isolate some tests fully, you can use the test harness again to create a fresh database. To test an individual task, you can access the original function using `.fn`: ```python from prefect import flow, task @task def myfavoritetask(): return 42 @flow def myfavoriteflow(): val = myfavoritetask() return val def testmyfavorite_task(): assert myfavoritetask.fn() == 42 ``` !!! tip "Disable logger" If your task uses a logger, you can disable the logger in order to avoid the `RuntimeError` raised from a missing flow context. ```python from prefect.logging import disablerunlogger def testmyfavorite_task(): with disablerunlogger(): assert myfavoritetask.fn() == 42 ```
Project: Traefik Mesh (Orchestration & Management / Service Mesh)
File: PULL_REQUEST_TEMPLATE.md

This PR: <!-- What does this PR do? --> Fixes #<!-- enter issue number here --> <!-- A brief description of the change being made with this pull request. --> Step 1 Step 2 ... <!-- You can add anything you want here, an explanation on the way you built your implementation, precisions on the origin of the bug, etc. -->