cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 12_basic_timers.md

Prompt: What is a timer in Apache Beam? Response: In Apache Beam, a is a per-key timer callback API that enables delayed processing of data stored using the . Apache Beam provides two : processing time timers and event time timers. Processing time timers are based on the system clock. Event time timers are based on the timestamps of the data elements. Apache Beam also supports dynamically setting a timer tag using `TimerMap` in the Java SDK. This feature lets you set multiple different timers in a `DoFn`. You can set the timer tags to be chosen dynamically, for example, based on data in the input elements. For more information, see the community blog post about . For additional examples of using timers in Apache Beam, see .
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: php-authorization.md

title: PHP OPA Library labels: layer: network category: application software: php tutorials: https://coil.com/p/segra/OPA-for-API-Authorization-with-Slim-PHP/H-7YsQL2m code: https://github.com/segrax/opa-php-examples https://github.com/segrax/openpolicyagent https://github.com/build-security/opa-symfony-middleware inventors: build-security docs_features: rest-api-integration: note: | This library provides a PHP wrapper around the OPA REST API. It can update policies and query for decisions. See the for various examples. These integrations demonstrate using OPA to perform API authorization in PSR-15 and Symfony compliant frameworks.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.17.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | DFS operations fail because of Stream closed error* Fix a bug with HDFS file close() mistakenly introduced by HADOOP-3681. | Blocker | Frequent DiskOutOfSpaceException on almost-full datanodes* NameNode keeps a count of number of blocks scheduled to be written to a datanode and uses it to avoid allocating more blocks than a datanode can hold. | Blocker | Avoid spurious "DataXceiver: java.io.IOException: Connection reset by peer" errors in DataNode log* Avoid spurious exceptions logged at DataNode when clients read from DFS. | Blocker | 1000 concurrent read on a single file failing the task/client* Allows the user to change the maximum number of xceivers in the datanode.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 48_sdk_harness.md

Prompt: What is SDK harness in Apache Beam? Response: Interoperability between Apache Beam SDKs and runners is a key aspect of Apache Beam. The introduces well-defined, language-neutral data structures and protocols between the SDK and runner. This interoperability layer, known as the 'portability API', ensures that SDKs and runners can seamlessly work with each other, reducing the interoperability burden for both SDKs and runners to a constant effort. The portability API consists of a set of smaller contracts that isolate SDKs and runners for job submission, management, and execution. These contracts utilize protocols like `protobuf` and `gRPC` to provide broad language support. Currently, all SDKs support the portability framework. For the latest information on portability support across SDKs, features, and runners, refer to the . The SDK harness is a program responsible for executing user code. This program is provided by an SDK and runs separately from the runner. SDK harness initialization relies on the provision and artifact APIs for obtaining staged files, pipeline options, and environment information. Apache Beam offers configuration options for the SDK harness to cater to diverse cluster setups. These options include: `environment_type`: determines where user code is executed. The `environmentconfig` parameter configures the environment based on the value of `environmenttype`: `DOCKER`: executes user code within a container on each worker node. Docker must be installed on worker nodes. You can specify the Docker image URL using the `environment_config` parameter. Prebuilt SDK container images are available with each Apache Beam release and pushed to . You can also . `PROCESS`: executes user code through processes that are automatically initiated by the runner on each worker node. `EXTERNAL`: dispatches user code to an external service. Use the `environment_config` parameter to specify the service address, for example, `localhost:50000`. `LOOPBACK`: executes user code within the same process that submitted the pipeline. `sdk_worker_parallelism`: determines the number of SDK workers per worker node. The default value is 1, but setting it to 0 enables automatic determination by the runner based on factors like the number of CPU cores on the worker machine.
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_migrate.md

Migrate one or more resources to the stored version. Migrate one or more resources to the stored version. ``` kyverno migrate [flags] ``` ``` kyverno migrate --resource policyexceptions.kyverno.io ``` ``` --context string The name of the kubeconfig context to use -h, --help help for migrate --kubeconfig string path to kubeconfig file with authorization and master location information --resource strings The resource to migrate ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Kubernetes Native Policy Management.
Project: KICS (Provisioning / Security & Compliance)
File: query-page-template.md

title: <QUERY_NAME> hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: <QUERY_ID> Query name: <QUERY_NAME> Platform: <PLATFORM> Severity: <SEVERITY> Category: <CATEGORY> URL: <DESCRIPTION_TEXT><br> <POSITIVE_TESTS> <NEGATIVE_TESTS>
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.124.md

layout: release date: 2023-08-16 tag: v0.6.124 updated link for contributor's journey map @abhijeetgauravm (#8476) Add `api/system/database/reset` endpoint to reset database @Aritra8438 (#8433) lastest enhance after meshkit release @Freedisch (#8437) feat: updated smp link in readme and fixed typo infrastructure @abhijeetgauravm (#8474) [chore] Update Playground Docker Compose @theBeginner86 (#8459) fix: test for delete filter command @Yana-Gupta (#8396) [UI] Send toaster informational notification upon save of design @Chadha93 (#8486) [UI] Enhance Notification Center @aabidsofi19 (#8483) import resources from schema, import filters from schema @Abhishek-kumar09 (#8097) fix crash due to empty response of filter_resource file @sudhanshutech (#8494) [UI] Add Qanelas Soft as Global Font @Chadha93 (#8481) [UI] Connections @senali-d (#8316) [UI] Use name instead of component in service mesh dashboard @Yashsharma1911 (#8484) fixed inconsistency in meshery ui @EraKin575 (#8461) Added Connection Stats Charts @aabidsofi19 (#8472) Dry Run Support in Designs And Applications @aabidsofi19 (#8471) Add mesh version support in Lifecycle management. @MUzairS15 (#8477) [Extensions] Collaborators: Remove spinner @senali-d (#8464) [CI] Update swagger docs workflow for rest api failing in edge and stable release @suhail34 (#8488) Updated go mod sync workflow @abdullah1308 (#8489) [CI] Meshkit error workflow committing on pull request @suhail34 (#8458) feat :removed duplication and fixed typo @Ghat0tkach (#8248) Designs docs : meshmodel user guide @parth721 (#8353) endpoints for user's keys @Freedisch (#8267) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aritra8438, @Chadha93, @EraKin575, @Freedisch, @Ghat0tkach, @MUzairS15, @Yana-Gupta, @Yashsharma1911, @aabidsofi19, @abdullah1308, @abhijeetgauravm, @leecalcote, @parth721, @senali-d, @sudhanshutech, @suhail34 and @theBeginner86
Project: ArangoDB (App Definition and Development / Database)
File: exception_lvalue_const.md

+++ title = "`const exception_type &exception() const &`" description = "Wide contract const lvalue reference observer of the stored exception. Constexpr propagating." categories = ["observers"] weight = 786 +++ Wide contract const lvalue reference observer of the stored exception. `NoValuePolicy::wideexceptioncheck()` is first invoked, then the reference to the exception is returned. As a valid default constructed exception is always present, no undefined behaviour occurs if `NoValuePolicy::wideexceptioncheck()` returns. Note that if `exception_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::wideexceptioncheck()`. Guarantees: None.
Project: FOSSA (Provisioning / Security & Compliance)
File: ingest.md

This subcommand adds an open-source library to the FOSSA knowledge base. For more information on possible options, run `millhone ingest --help`. This subcommand is run by internal FOSSA employees; end users are not able to use this command to ingest matches. This is controlled by the permissions granted to the API keys for the service. First, download the library locally, and determine the locator that FOSSA would use to refer to this library in the future. For example, if the library was at `https://github.com/openssh/libopenssh`, the locator would be something like `git+github.com/openssh/libopenssh$05dfdd5f54d9a1bae5544141a7ee65baa3313ecd`. Once these are both performed, run the program with the appropriate arguments to ingest: ```shell millhone ingest \ --locator 'git+github.com/openssh/libopenssh$05dfdd5f54d9a1bae5544141a7ee65baa3313ecd' \ ~/projects/scratch/libopenssh ``` [!IMPORTANT] Make sure to fill in your own data for these arguments. For more information on possible options, run `millhone ingest --help`. Now that the library is ingested, you can discover matches via `millhone analyze`.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_aks_clusters.md

+++ title = "azurermaksclusters resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermaksclusters" identifier = "inspec/resources/azure/azurermaksclusters.md azurermaksclusters resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azureaks_clusters" >}} Use the `azurermaksclusters` InSpec audit resource to enumerate AKS Clusters. This resource interacts with version `2018-03-31` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . An `azurermaksclusters` resource block identifies AKS Clusters by Resource Group. describe azurermaksclusters(resource_group: 'ExampleGroup') do ... end describe azurermaksclusters(resource_group: 'ExampleGroup') do its('names') { should include('ClusterName') } end `names` The name of the AKS Cluster its('names') { should include('ClusterName') } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the resource returns a result. Use `should_not` if you expect zero matches. describe azurermaksclusters(resource_group: 'ExampleGroup') do it { should exist } end describe azurermaksclusters(resource_group: 'EmptyExampleGroup') do it { should_not exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.15.md

layout: release date: 2021-05-25 tag: v0.5.15 [mesheryctl] (child) View Performance Profiles Configuration @fallmor (#2887) [mesheryctl] Validating versions and gracefully handling invalid versions @metonymic-smokey (#2980) Fix `context create`: Use values from template context @navendu-pottekkat (#2998) Namespace drop box to be responsive @Ayush-Khandelwal-007 (#3006) Added Confirmation when Channel is Set @DARK-art108 (#3008) Config file input box visibility fix @Ayush-Khandelwal-007 (#3014) [Meshery UI] - Updated Meshery Provider UI @adithyaakrishna (#2927) Fixed doc commands in root makefile @dhruv0000 (#2999) [mesheryctl] system context list: improve msg for listing missing contexts @leecalcote (#2995) Tried to rectify the issue of docs build previews trigerring on mesheryctl-changes @chinmaym07 (#2967) [Docs] - Added Release Notes from v0.5.3 to v0.5.14 @adithyaakrishna (#2990) [UI] Navigation Menu Icon Scale with zoom in/out @Ayush-Khandelwal-007 (#2966) Bump nokogiri from 1.11.1 to 1.11.5 in /docs @dependabot (#2987) [CI] Makefile: `make docs` for conveniently building docs @leecalcote (#2993) [CI] Helm: Test of helm chart releaser for remote repo @leecalcote (#2982) [Docs] Contributing / Project / Overview section restructure @leecalcote (#3010) [Docs] Automatic Graphql Docs Generation @dhruv0000 (#2989) Add contributing guidelines for mesheryctl @navendu-pottekkat (#3007) [Docs] Service mesh pattern management @leecalcote (#2988) [Docs]: page for `mesheryctl system update` @Blakelist7 (#2974) [Docs] [WIP] Modify command reference doc pages @alphaX86 (#2985)
Project: ShardingSphere (App Definition and Development / Database)
File: sql-federation.en.md

+++ title = "SQL Federation" weight = 13 +++ This function is an experimental one and is currently not suitable for use in core system production environments. When multiple tables in a join query are distributed across different database instances, enabling federated query allows for cross-database join queries, as well as subqueries. ```yaml sqlFederation: sqlFederationEnabled: # SQL federation enabled configuration allQueryUseSQLFederation: # all query use SQL federation configuration executionPlanCache: # execution plan cache configuration initialCapacity: 2000 # execution plan local cache initial capacity maximumSize: 65535 # execution plan local cache maximum size ``` ```yaml sqlFederation: sqlFederationEnabled: true allQueryUseSQLFederation: false executionPlanCache: initialCapacity: 2000 maximumSize: 65535 ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: sbom-merge-strategy.md

If more than one --sbom-scanner-command value is being used, use the specified method to merge the output from later commands with output from earlier commands. Recognized values include: cat Concatenate the files. merge-cyclonedx-by-component-name-and-version Merge the "component" fields of JSON documents, ignoring values from documents when the combination of their "name" and "version" values is already present. Documents are processed in the order in which they are generated, which is the order in which the commands that generate them were specified. merge-spdx-by-package-name-and-versioninfo Merge the "package" fields of JSON documents, ignoring values from documents when the combination of their "name" and "versionInfo" values is already present. Documents are processed in the order in which they are generated, which is the order in which the commands that generate them were specified.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.9.0.md

Deviceshifu can load password of Telemetry from secret if it exists by @FFFFFaraway in https://github.com/Edgenesis/shifu/pull/421 <BugFix>Solved Unable to use customize deviceshifu normally by @Twpeak in https://github.com/Edgenesis/shifu/pull/369 <BugFix>Fix Plc4x timeout by @leepala in https://github.com/Edgenesis/shifu/pull/391 <BugFix>fix the rtspDeviceShifu restart problem and the problem that the thread is not closed by @cbgz121 in https://github.com/Edgenesis/shifu/pull/433 updates devcontainer config to resolve premission issue, updates plugins by @tomqin93 in https://github.com/Edgenesis/shifu/pull/427 add pipeline config for push images to huawei cloud antomaticly by @Vacant2333 in https://github.com/Edgenesis/shifu/pull/430 add logger to replace klog by @jyyds in https://github.com/Edgenesis/shifu/pull/437 and https://github.com/Edgenesis/shifu/pull/440 design for telemetry to load secret by @FFFFFaraway in https://github.com/Edgenesis/shifu/pull/429 design for deviceshifu-rtsp by @leepala in https://github.com/Edgenesis/shifu/pull/428 @Vacant2333 made their first contribution in https://github.com/Edgenesis/shifu/pull/430 @jyyds made their first contribution in https://github.com/Edgenesis/shifu/pull/437 Bump sigs.k8s.io/controller-runtime from 0.13.1 to 0.14.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/424 Bump github.com/taosdata/driver-go/v3 from 3.0.3 to 3.0.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/432 Bump golang.org/x/crypto from 0.1.0 to 0.4.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/435 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.8.0...v0.9.0
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.50.md

layout: release date: 2024-04-24 tag: v0.7.50 add capabilities to nodegroupwallet @aabidsofi19 (#10763) Fix deployment failures @MUzairS15 (#10767) feat: workspace command @RipulHandoo (#10634) Add proper meshkit sytle error logging for ClearLine function @Aijeyomah (#10556) Fix behavior to display helper function @lekaf974 (#10685) Fix not able to download design @Yashsharma1911 (#10766) [Fix Docs] Tutorial: Exploring Kubernetes CronJobs with Meshery Playground @sandramsc (#10107) Thank you to our contributors for making this release possible: @Aijeyomah, @MUzairS15, @RipulHandoo, @Yashsharma1911, @aabidsofi19, @codeKraken19, @gyohuangxin, @iArchitSharma, @leecalcote, @lekaf974, @sandramsc and l5io
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.38.0.md

Bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.9.1 to 1.9.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/819 Bump golang.org/x/net from 0.20.0 to 0.21.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/820 Bump github.com/taosdata/driver-go/v3 from 3.5.1 to 3.5.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/817 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.37.0...v0.38.0
Project: YDB (App Definition and Development / Database)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Skyscanner Ltd , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Linux Foundation , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Dropbox, Inc. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , LinkedIn , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Hazelcast IMDG (App Definition and Development / Database)
File: 014-batchstage-sort.md

title: 014 - BatchStage.sort() description: Distributed sorting for batch workloads Since: 4.3 Currently, Jet can sort the data only indirectly, through a special aggregate operation, resulting in a single output item that is the whole sorted list. This design implements a transform that affects just the order and not the type of the stream items (`T` vs. `List<T>`), but only for a batch workload. We gain the following methods: ```java BatchStage<T> BatchStage.sort() BatchStage<T> BatchStage.sort(Comparator<? super T>) ``` Example: ```java Pipeline p = Pipeline.create(); BatchStage<String> strings = p.readFrom(stringSource); BatchStage<String> sortedStrings = p.sort(); ``` Distributed sorting happens in two phases: Sort the data on every cluster node locally, using a single `SortP` processor per node Receive the partially sorted data on a single node, using a new type of edge, `ordered(Comparator)` `SortP` is a very simple processor, it just puts all the received data into a `PriorityQueue` with a user-supplied `Comparator`. In the completion phase it drains the priority queue into the output. This is the entire implementation: ```java public class SortP<T> extends AbstractProcessor { private final PriorityQueue<T> priorityQueue; private final Traverser<T> resultTraverser; public SortP(@Nullable Comparator<T> comparator) { this.priorityQueue = new PriorityQueue<>(comparator); this.resultTraverser = priorityQueue::poll; } @Override protected boolean tryProcess0(@Nonnull Object item) { priorityQueue.add((T) item); return true; } @Override public boolean complete() { return emitFromTraverser(resultTraverser); } } ``` The `ordered(Comparator)` edge ensures that it always receives the least item available from all the incoming data streams (one from each node). Even though this is trivially simple high-level logic, implementing the monotonic reception with cooperative multithreading in mind is the most complex part of this work. It is implemented inside `ConcurrentInboundEdgeStream.OrderedDrain`. Apart from the mentioned limitation that this is only for batch stages, a big caveat is that Jet may reorder the data between stages through parallel processing, removing the sort order. There is work in progress that will prevent Jet from reordering the stream items where it would break correctness.