cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: sharding-cache.en.md

+++ title = "Cache for Sharding Route" weight = 11 +++ This feature is experimental and needs to be used with the data sharding rule. The cache for sharding route will put the logical SQL, the parameter value of the shard key, and the routing result into the cache, exchange space for time, and reduce CPU usage of the routing logic. We recommend enabling it only if the following conditions are met: Pure OLTP scenarios. The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck. Most of the CPUs are used by ShardingSphere routing logic. All SQLs are optimized and each SQL execution could be routed to a single data node. If the above conditions are not met, the execution delay of SQL may not be significantly improved, and the memory pressure will be increased. ```yaml rules: !SHARDING tables: shardingAlgorithms: shardingCache: allowedMaxSqlLength: 512 # Allow cached SQL length limit routeCache: initialCapacity: 65536 # Initial capacity maximumSize: 262144 # Maximum capacity softValues: true # Whether to use soft references ```
Project: Harbor (Provisioning / Container Registry)
File: 10-07-Non-admin-can-not-scan.md

Test 10-07 non-admin can not scan ======= To verify a non-admin user can not execute scan action. User guide This test requires that a Harbor instance is running and available. Harbor is installed with trivy enable. A linux host with Docker CLI installed. Login harbor as non admin user. Create a project. Push an image. Go to project and expand repo. Click tag menu. Step 5 user can not see scan button. None
Project: NATS (App Definition and Development / Streaming & Messaging)
File: README.md

<p align="center"> <img src="logos/nats-horizontal-color.png" width="300" alt="NATS Logo"> </p> is a simple, secure and performant communications system for digital systems, services and devices. NATS is part of the Cloud Native Computing Foundation (). NATS has over , and its server can run on-premise, in the cloud, at the edge, and even on a Raspberry Pi. NATS can secure and simplify design and operation of modern distributed systems. ]]]]]]]][ArtifactHub-Url] Watch of NATS. Watch to learn more about its origin story and design philosophy. : Follow us on Twitter! : Where you can ask questions : Click to join. You can ask question to our maintainers and to the rich and active community. If you are interested in contributing to NATS, read about our... The NATS product roadmap can be found . Who uses NATS? See our on . A third party security audit was performed by Cure53, you can see the full report . If you've found a vulnerability or a potential vulnerability in the NATS server, please let us know at . Unless otherwise noted, the NATS source files are distributed under the Apache Version 2.0 license found in the LICENSE file.
Project: FOSSA (Provisioning / Security & Compliance)
File: nodejs.md

The nodejs buildtool ecosystem consists of three major toolchains: the `npm` cli, `pnpm` and `yarn`. | Strategy | Direct Deps | Transitive Deps | Edges | Container Scanning | | -- | | | | | | | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | | | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | | | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | | | :whitecheckmark: | :x: | :x: | :whitecheckmark: |
Project: KICS (Provisioning / Security & Compliance)
File: 57b12981-3816-4c31-b190-a1e614361dd2.md

title: Public Lambda via API Gateway hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 57b12981-3816-4c31-b190-a1e614361dd2 Query name: Public Lambda via API Gateway Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Allowing to run lambda function using public API Gateway<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" AWSTemplateFormatVersion: "2010-09-09" Description: "BatchJobDefinition" Resources: s3Permission3: Type: AWS::Lambda::Permission Properties: FunctionName: !GetAtt function.Arn Action: lambda:InvokeFunction Principal: apigateway.amazonaws.com SourceAccount: !Ref 'AWS::AccountId' SourceArn: arn:aws:s3:eu-central-1:123456789012// ``` ```json title="Positive test num. 2 - json file" hl_lines="18" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "s3Permission": { "Type": "AWS::Lambda::Permission", "Properties": { "FunctionName": { "Fn::GetAtt": [ "function", "Arn" ] }, "Action": "lambda:InvokeFunction", "Principal": "apigateway.amazonaws.com", "SourceAccount": { "Ref": "AWS::AccountId" }, "SourceArn": "arn:aws:s3:eu-central-1:123456789012//" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: "BatchJobDefinition" Resources: s3Permission3: Type: AWS::Lambda::Permission Properties: FunctionName: !GetAtt function.Arn Action: lambda:InvokeFunction Principal: s3.amazonaws.com SourceAccount: !Ref 'AWS::AccountId' SourceArn: arn:aws:s3:eu-central-1:123456789012:bucketname ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "s3Permission": { "Type": "AWS::Lambda::Permission", "Properties": { "FunctionName": { "Fn::GetAtt": [ "function", "Arn" ] }, "Action": "lambda:InvokeFunction", "Principal": "s3.amazonaws.com", "SourceAccount": { "Ref": "AWS::AccountId" }, "SourceArn": "arn:aws:s3:eu-central-1:123456789012:bucketname" } } } } ```
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_CloudWatch_Logs.md

The following is a Lambda function that receives Amazon CloudWatch Logs event record data as input and writes message part to Lambda's CloudWatch Logs. Note that by default anything written to Console will be logged as CloudWatch Logs events. ```go import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" ) func handler(ctx context.Context, logsEvent events.CloudwatchLogsEvent) { data, _ := logsEvent.AWSLogs.Parse() for _, logEvent := range data.LogEvents { fmt.Printf("Message = %s\n", logEvent.Message) } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.5.md

layout: release date: 2020-9-2 tag: v0.4.5 General [ImgBot] Optimize images @IMGBOT (#1514) added kuma service mesh @kumarabd (#1473) ADDED SAMPLE APPLICATION @was-coder (#1511) Updated citrix adapter to reflect supported operations" @KarenEfereyan (#1513) Sample application edited @was-coder (#1503) Udoka vrede branch @UdokaVrede (#1500) Added SMI conformance capability as a feature to KUMA adapter" @KarenEfereyan (#1492) Update README.mb @NorbertLuszkiewicz (#1480) fix wsl 404s @thegagne (#1497) Added the Correct Slack link in contributing.md @akashgp09 (#1484) removed 'common issues' heading and fixed typo @tim-hanke (#1477) Merge master into meshmap @kushthedude (#1472) Maintenance Bump github.com/gorilla/mux from 1.7.4 to 1.8.0 @dependabot-preview (#1508) Bump google.golang.org/grpc from 1.31.0 to 1.31.1 @dependabot-preview (#1507) Bump fortio.org/fortio from 1.6.4 to 1.6.8 @dependabot-preview (#1509) Bump github.com/prometheus/common from 0.10.0 to 0.13.0 @dependabot-preview (#1506) CI: improvise actions executed & remove tool configs @kushthedude (#1494)
Project: KICS (Provisioning / Security & Compliance)
File: 3ef8696c-e4ae-4872-92c7-520bb44dfe77.md

title: Public Lambda via API Gateway hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3ef8696c-e4ae-4872-92c7-520bb44dfe77 Query name: Public Lambda via API Gateway Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Allowing to run lambda function using public API Gateway<br> ```tf title="Positive test num. 1 - tf file" hl_lines="9" resource "awslambdapermission" "apigw" { statement_id = "AllowAPIGatewayInvoke" action = "lambda:InvokeFunction" functionname = awslambdafunction.example.functionname principal = "apigateway.amazonaws.com" sourcearn = "${awsapigatewayrestapi.example.executionarn}//" } resource "awslambdafunction" "example" { function_name = "ServerlessPerson" handler = "MyHandler::handleRequest" runtime = "java11" role = awsiamrole.lambda_exec.arn } ``` ```tf title="Negative test num. 1 - tf file" resource "awslambdapermission" "apigw" { statement_id = "AllowAPIGatewayInvoke" action = "lambda:InvokeFunction" functionname = awslambdafunction.example.functionname principal = "apigateway.amazonaws.com" sourcearn = "${awsapigatewayrestapi.example.executionarn}/test/test" } resource "awslambdafunction" "example" { function_name = "ServerlessPerson" handler = "MyHandler::handleRequest" runtime = "java11" role = awsiamrole.lambda_exec.arn } ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.3.1.en.md

Added extra diagnostic checks to help debug issues when mnesia is stuck waiting for tables. Library Updates: `ekka` has been upgraded to version 0.15.15, and `mria` to version 0.6.4. Upgraded jq library from v0.3.10 to v0.3.11. In this version, jqport programs are initiated on-demand and will not appear in users' processes unless the jq function in EMQX is used. Additionally, idle jqport programs will auto-terminate after a set period. Note: Most EMQX users are running jq in NIF mode and will not be affected by this update. Hid a few pieces of sensitive information from debug-level logs. Disabled outdated TLS versions and cipher suites in the EMQX backplane network (`genrpc`). Added support for tlsv1.3 on the backplane and introduced new configuration parameters: `EMQXRPCTLS_VERSIONS` and `EMQX_RPCCIPHERS`. The corresponding `genrpc` PR: https://github.com/emqx/genrpc/pull/36 Fixed clustering in IPv6 network. Added new configurations `rpc.listenaddress` and `rpc.ipv6only` to allow EMQX cluster RPC server and client to use IPv6. Updated QUIC stack to msquic 2.2.3. Fixed rpc schema to ensure that client/server uses same transport driver. Fixed the issue where the node could not start after executing `./bin/emqx data import [FILE]`. The connection between `apikeykey` and `apikeyname` is also enhanced for better consistency and unique identification. `apikeykey`: When generating an API key via the dashboard, `apikeykey` will now create a unique value derived from the provided human-readable `apikey_name`. `apikeyname` Conversely, when using a bootstrap file to generate an API key, `apikeyname` will be generated as a unique value based on the associated `apikey_key`. Fixed the schema to ensure that RPC client SSL port aligns with the configured server port. This fix also guarantees that the RPC ports are correctly opened in the Helm chart. Upgraded opentelemetry library to v1.3.1-emqx. This opentelemetry release fixes invalid metrics timestamps in the exported metrics. Fixed excessive warning message printed in remote console shell. Resolved an incompatibility issue that caused crashes during session takeover or channel eviction when the session was located on a remote node running EMQX v5.2.x or an earlier version. Eliminated logging and tracing of HTTP request bodies in HTTP authentification and HTTP bridges. Fixed backward plugin compatibility. Currently, EMQX validates hookpoint names, so invalid hookspoints cannot be used for registering hooks. However, older versions of plugin templates used some misspelled hookpoints, and so could the real plugins. We allow the old hookpoints to be used for registering hooks, but issue a warning that they are deprecated. As before, these hooks are never called. Fix config sync wait-loop race condition when cluster nodes boot around the same time.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.0.3.md

Fix missing "deviceshifu" namespace error when installing Shifu by @tomqin93 in https://github.com/Edgenesis/shifu/pull/156 Fix typo in OPC UA deviceShifu by @tomqin93 in https://github.com/Edgenesis/shifu/pull/163 [Issue #133]Support password/x509 authentication for OPCUA by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/142 Update deviceShifu Dockerfile, Go mod tidy project by @tomqin93 in https://github.com/Edgenesis/shifu/pull/154 Bump sigs.k8s.io/controller-runtime from 0.12.2 to 0.12.3 in /k8s/crd by @dependabot in https://github.com/Edgenesis/shifu/pull/161 [Issue #157]New update_shifu by @13316272689 in https://github.com/Edgenesis/shifu/pull/158 add two files of using shifu by @13316272689 in https://github.com/Edgenesis/shifu/pull/159 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.0.2...v0.0.3
Project: ArangoDB (App Definition and Development / Database)
File: hook_result_move_construction.md

+++ title = "`void hookresultmove_construction(T *, U &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the converting move constructors of `basic_result`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onresultmove_construction(T *, U &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the converting move constructors of `basicresult` (NOT the standard move constructor). See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_result.hpp>`
Project: secureCodeBox (Provisioning / Security & Compliance)
File: adr_0006.md

title: "ADR-0006: Provide versioned documentation" sidebar_label: "ADR-0006" | <!-- --> | <!-- --> | |-|-| | Status: | REJECTED | | Date: | 2020-10-12 | | Author(s): | Yannik Fuhrmeister , Sven Strittmatter | :::info Since nearly two years no one cared about versioned documentation, so we reject this proposal. ::: We want to introduce versioning to be able to provide documentation for multiple versions of the secureCodeBox. The tool that we are currently using for documentation is . Docusaurus provides the possibility to maintain multiple versions [out of the box](https://v2.docusaurus.io/docs/versioning/. We will need to specify how many versions of the documentation we want to maintain to avoid inconsistencies and overhead. Furthermore, we need to decide which version increments need to have their own branch of documentation. We introduce a new documentation version for every minor version () to ensure that the documentation is up-to-date. We maintain the latest 3 major versions (previous, current, next). We maintain the latest minor version for each major version. We do not maintain patch versions nor multiple minor versions for each major version! Example: For secureCodeBox versions 1.9.9, 2.3.2, 2.3.3 and 3.0.0 the documentation versions would be 1.9.x, 2.3.x, and 3.0.x. TL;DR We maintain 3 versions of the documentation. We need to update the documentation version everytime we increment minor or major versions of the secureCodeBox (manually or with action). Maintaining the documentation could be more difficult due to now increased number of documentation files. Documentation has to be maintained in two repositories because when creating a new version Docusaurus creates a copy of all files in this repository (see )
Project: ArangoDB (App Definition and Development / Database)
File: is_move_bitcopying.md

+++ title = "`ismovebitcopying<T>`" description = "(>= Outcome v2.2.0) A customisable integral constant type true for `T` types which are move bitcopying safe." +++ A customisable integral constant type true for `T` types which are move bitcopying safe. As per , these are types for which: There is an inline, constexpr-available, default constructor. The move constructor has side effects equivalent to `memcpy` of source to destination, followed by a `memcpy` of a default constructed instance to source. That the destruction of a default constructed instance has no visible side effects. This implies that if you move from a bit copying type, you need not call its destructor, even if that is a virtual destructor. If you opt your types into this trait, Outcome will track moved-from state and not call the destructor for your type on moved-from instances. Obviously enough this is, in current C++ standards, undefined behaviour. However it very significantly improves the quality of codegen during inlining. Overridable: By template specialisation into the `trait` namespace. Default: False. Default specialisations exist for: `<boost/outcome/experimental/status_result.hpp>` True for `BOOSTOUTCOMESYSTEMERROR2NAMESPACE::status_code<DomainType>` if trait `BOOSTOUTCOMESYSTEMERROR2NAMESPACE::traits::ismovebitcopying<BOOSTOUTCOMESYSTEMERROR2NAMESPACE::status_code<DomainType>>::value` is true. True for `BOOSTOUTCOMESYSTEMERROR2NAMESPACE::erroredstatuscode<DomainType>` if trait `BOOSTOUTCOMESYSTEMERROR2NAMESPACE::traits::ismovebitcopying<BOOSTOUTCOMESYSTEMERROR2NAMESPACE::erroredstatuscode<DomainType>>::value` is true. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::trait` Header: `<boost/outcome/trait.hpp>`
Project: kiosk (Provisioning / Automation & Configuration)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at oss-conduct@uber.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at .
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2020.11.11.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2020.11.11 name: Changelog-v2020.11.11 parent: welcome weight: 20201111 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2020.11.11/ aliases: /docs/{{.version}}/CHANGELOG-v2020.11.11/ Prepare for release v0.2.0 (#95) Add default resource limit (#650) Rename MasterServiceName to MasterDiscoveryServiceName Remove ElasticsearchMetricsPortName Add HasServiceTemplate & GetServiceTemplate helpers (#649) Enable separate serviceTemplate for each service (#648) Remove replicaServiceTemplate from Postgres CRD (#646) Add `ReplicationModeDetector` Image for MongoDB (#645) Update Elasticsearch constants (#639) Remove version label from database labels (#644) Prepare for release v0.15.0 (#549) Update KubeDB api (#548) Update KubeDB api (#547) Update KubeDB api (#546) Prepare for release v0.15.0 (#414) Update KubeDB api (#413) Allow stats service patching Use separate ServiceTemplate for each service (#412) Use container name as constant (#402) Update KubeDB api (#411) Prepare for release v0.15.0 (#204) Add `ReplicationModeDetector` Image for MongoDB (#202) Add permissions to evict pods (#201) Prepare for release v0.8.0 (#243) Update KubeDB api (#242) Use separate ServiceTemplate for each service (#241) Update KubeDB api (#240) Prepare for release v0.8.0 (#318) Update KubeDB api (#317) Allow stats service patching Use separate ServiceTemplate for each service (#315) Fix Health Check (#305) Add `ReplicationModeDetector` (#316) Update KubeDB api (#314) Prepare for release v0.8.0 (#305) Update KubeDB api (#304) Allow stats service patching Use separate ServiceTemplate for each service (#303) Fix MySQL args (#295) Prepare for release v0.15.0 (#349) Prepare for release v0.2.0 (#138) Update KubeDB api (#137) Use separate ServiceTemplate for each service (#136) Update KubeDB api (#135) Prepare for release v0.2.0 (#108) Update KubeDB api (#107) Use separate ServiceTemplate for each service (#106) Update KubeDB api (#105) Prepare for release v0.15.0 (#424) Update KubeDB api (#423) Allow stats service patching Use separate ServiceTemplate for each service (#422) Update KubeDB api (#421) Prepare for release v0.2.0 (#120) Update KubeDB api (#119) Use separate ServiceTemplate for each service (#118) Update KubeDB api (#117) Prepare for release v0.8.0 (#262) Update KubeDB api (#261) Use separate ServiceTemplate for each service (#260) Update KubeDB api (#259) Prepare for release v0.2.0 (#92) Update KubeDB api (#91) Add MongoDB `ReplicationModeDetector` (#90) Drop mysql from repo name (#89)