cwielenb/CNCF-Dataset huggingface dataset:
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: migrationguide.md

This guide is intended to assist in the migration from the `azure-storage-blob-go` module, or previous betas of `azblob`, to the latest releases of the `azblob` module. The redesign of the `azblob` module separates clients into various sub-packages. In previous versions, the public surface area was "flat", so all clients and supporting types were in the `azblob` package. This made it difficult to navigate the public surface area. In `azure-storage-blob-go` a client constructor always requires a `url.URL` and `Pipeline` parameters. In `azblob` a client constructor always requires a `string` URL, any specified credential type, and a `*ClientOptions` for optional values. You pass `nil` to accept default options. ```go // new code client, err := azblob.NewClient("<my storage account URL>", cred, nil) ``` In `azure-storage-blob-go` you created a `Pipeline` with the required credential type. This pipeline was then passed to the client constructor. In `azblob`, you pass the required credential directly to the client constructor. ```go // new code. cred is an AAD token credential created from the azidentity module client, err := azblob.NewClient("<my storage account URL>", cred, nil) ``` The `azure-storage-blob-go` module provided limited support for OAuth token authentication via `NewTokenCredential`. This been replaced by using Azure Identity credentials from . Authentication with a shared key via `NewSharedKeyCredential` remains unchanged. In `azure-storage-blob-go` you created a `Pipeline` with `NewAnonymousCredential` to support anonymous or SAS authentication. In `azblob` you use the construtor `NewClientWithNoCredential()` instead. ```go // new code client, err := azblob.NewClientWithNoCredential("<public blob or blob with SAS URL>", nil) ``` In `azure-storage-blob-go` you explicitly created a `Marker` type that was used to page over results (). In `azblob`, operations that return paginated values return a `*runtime.Pager[T]`. ```go // new code pager := client.NewListBlobsFlatPager("my-container", nil) for pager.More() { page, err := pager.NextPage(context.TODO()) // process results } ``` In `azure-storage-blob-go` you explicitly created a HTTP pipeline with configuration before creating a client. This pipeline instance was then passed as an argument to the client constructor (). In `azblob` a HTTP pipeline is created during client construction. The pipeline is configured through the `azcore.ClientOptions` type. ```go // new code client, err := azblob.NewClient(account, cred, &azblob.ClientOptions{ ClientOptions: azcore.ClientOptions{ // configure HTTP pipeline options here }, }) ```
Project: ArangoDB (App Definition and Development / Database)
File: explicit_result_copy_converting_constructor.md

+++ title = "`explicit basicoutcome(const basicresult<A, B, C> &)`" description = "Explicit converting copy constructor from compatible `basicresult`. Available if `predicate::enablecompatible_conversion<A, B, void, C>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 330 +++ Explicit converting copy constructor from compatible `basicresult`. Calls {{% api "void onoutcomecopyconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablecompatibleconversion<A, B, void, C>` is true. Complexity: Same as for the copy constructors of the underlying types. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.
Project: StarRocks (App Definition and Development / Database)
File: bitmap_from_binary.md

displayed_sidebar: "English" Converts a binary string with a specific format to a bitmap. This function can be used to load bitmap data to StarRocks. This function is supported from v3.0. ```Haskell BITMAP bitmapfrombinary(VARBINARY str) ``` `str`: The supported data type is VARBINARY. Returns a value of the BITMAP type. Example 1: Use this function with other Bitmap functions. ```Plain mysql> select bitmaptostring(bitmapfrombinary(bitmaptobinary(bitmapfromstring("0,1,2,3")))); ++ | bitmaptostring(bitmapfrombinary(bitmaptobinary(bitmapfromstring('0,1,2,3')))) | ++ | 0,1,2,3 | ++ 1 row in set (0.01 sec) ```
Project: KUDO (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: If this is your first time, please read our contributor guidelines: https://github.com/kudobuilder/kudo/blob/main/CONTRIBUTING.md Make sure you have added and ran the tests before submitting your PR If the PR is unfinished, start it as a Draft PR: https://github.blog/2019-02-14-introducing-draft-pull-requests/ --> What this PR does / why we need it: <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes #
Project: Shifu (Provisioning / Automation & Configuration)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: ... ... ... ... Expected behavior A clear and concise description of what you expected to happen. Log Output If applicable, add logs to help explain your problem. Server (please complete the following information): Shifu Version: [e.g. v0.0.5] Kubernetes distro [e.g. K8s, K3s] Version [e.g. v1.24.0] CPU Architecture [e.g. amd64, arm64w] Additional context Add any other context about the problem here.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_set_analytics.md

title: "Command - devspace set analytics" sidebar_label: devspace set analytics Update analytics settings ``` devspace set analytics [flags] ``` ``` Example: devspace set analytics disabled true ``` ``` -h, --help help for analytics ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: YugabyteDB (App Definition and Development / Database)
File: visualstudioworkbench.md

title: Use Visual Studio Code with YugabyteDB YCQL headerTitle: Cassandra Workbench linkTitle: Cassandra Workbench description: Configure Visual Studio Code to work with YCQL. menu: v2.18: identifier: visualstudioworkbench parent: tools weight: 80 type: docs is a free Visual Studio Code extension for browsing and querying Cassandra databases. It also features autocomplete and syntax highlighting. This tutorial shows how to install Cassandra Workbench and configure a connection. To use Cassandra Workbench with YugabyteDB, you need to have the following YugabyteDB up and running. Refer to . Visual Studio Code . To install the extension, do the following: Start Visual Studio Code and from the Go menu, choose Go to File. Enter the following command. ```sh ext install kdcro101.vscode-cassandra ``` Cassandra Workbench is now available in the Activity bar. For more information on managing extensions in Visual Studio Code, refer to . Click the Cassandra Workbench icon in the Activity bar in Visual Studio Code.\ \ Open the Command Palette (View>Command Palette) and enter the following command to generate the .cassandraWorkbench.jsonc configuration file: ```sh Cassandra Workbench: Generate configuration ``` In the Cassandra Workbench, click Edit configuration to open the configuration file. Replace `contactPoints` with the host address, and username and password with your credentials (the default user and password is `cassandra`). ```json // name must be unique! [ // AllowAllAuthenticator { "name": "Cluster AllowAllAuthenticator", "contactPoints": ["127.0.0.1"] }, //PasswordAuthenticator { "name": "Cluster PasswordAuthenticator", "contactPoints": ["127.0.0.1"], "authProvider": { "class": "PasswordAuthenticator", "username": "cassandra", "password": "cassandra" } } ] ``` You can now explore your YCQL schema and data. For more details, refer to .
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: groups.md

Groups are made up of users who have roles. An organization can have one or more groups. Each project can be assigned one or more groups. Groups can be assigned to multiple projects. Groups are created independently of projects, and then assigned to them. Organizations have a quota to limit the number of groups assigned to it. If you need to change the quota, please contact your Lagoon administrator.
Project: ClickHouse (App Definition and Development / Database)
File: v21.6.3.14-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix Zero-Copy replication with several S3 volumes (Fixes ). (). Backported in : Avoid hiding errors like `Limit for rows or bytes to read exceeded` for scalar subqueries. (). Backported in : In "multipart/form-data" message consider the CRLF preceding a boundary as part of it. Fixes . (). Backported in : - Fixed the deadlock that can happen during LDAP role (re)mapping, when LDAP group is mapped to a nonexistent local role. (). Backported in : - If ZooKeeper connection was lost and replica was cloned after restoring the connection, its replication queue might contain outdated entries. It's fixed. - Fixed crash when replication queue contains intersecting virtual parts. It may rarely happen if some data part was lost. Print error in log instead of terminating. (). Backported in : Fix bug when exception `Mutation was killed` can be thrown to the client on mutation wait when mutation not loaded into memory yet. (). Backported in : Fix extremely rare bug on low-memory servers which can lead to the inability to perform merges without restart. Possibly fixes . (). Backported in : Fix possible heap-buffer-overflow in Arrow. ().
Project: Dragonfly (Provisioning / Container Registry)
File: dfstore.md

% DFCACHE(1) Version v2.1.0 | Frivolous "Dfstore" Documentation dfstore object storage client of dragonfly Dfstore is a storage client for dragonfly. It can rely on different types of object storage, such as S3 or OSS, to provide stable object storage capabilities dfstore uses the entire P2P network as a cache when storing objects. Rely on S3 or OSS as the backend to ensure storage reliability. In the process of object storage, P2P Cache is effectively used for fast read and write storage. ```shell -h, --help help for rm ``` - copies a local file or dragonfly object to another location locally or in dragonfly object storage - remove object from P2P storage system - show version See GitHub Issues: <https://github.com/dragonflyoss/Dragonfly2/issues>
Project: ShardingSphere (App Definition and Development / Database)
File: shadow.en.md

+++ title = "Shadow DB" weight = 7 +++ Please refer to the following configuration in order to use the ShardingSphere shadow DB feature in ShardingSphere-Proxy. ```yaml rules: !SHADOW dataSources: shadowDataSource: productionDataSourceName: # production data source name shadowDataSourceName: # shadow data source name tables: <table_name>: dataSourceNames: # shadow table associates shadow data source name list <shadowdatasource> shadowAlgorithmNames: # shadow table associates shadow algorithm name list <shadowalgorithmname> defaultShadowAlgorithmName: # default shadow algorithm name (option) shadowAlgorithms: <shadowalgorithmname> (+): # shadow algorithm name type: # shadow algorithm type props: # shadow algorithm attribute configuration ``` Please refer to for more details. Configure shadow DB rules in the YAML file, including data sources, shadow library rules, global properties and other configuration items; Call the `createDataSource()` method of the `YamlShardingSphereDataSourceFactory` object to create a ShardingSphereDataSource based on the configuration information in the YAML file. The YAML configuration sample of shadow DB is as follows: ```yaml dataSources: ds: url: jdbc:mysql://127.0.0.1:3306/ds?serverTimezone=UTC&useSSL=false username: root password: connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 shadow_ds: url: jdbc:mysql://127.0.0.1:3306/shadow_ds?serverTimezone=UTC&useSSL=false username: root password: connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 rules: !SHADOW dataSources: shadowDataSource: productionDataSourceName: ds shadowDataSourceName: shadow_ds tables: t_order: dataSourceNames: shadowDataSource shadowAlgorithmNames: useridinsertmatchalgorithm sqlhintalgorithm shadowAlgorithms: useridinsertmatchalgorithm: type: REGEX_MATCH props: operation: insert column: user_id regex: "[1]" sqlhintalgorithm: type: SQL_HINT ```
Project: Harbor (Provisioning / Container Registry)
File: 7-05-Trigger-manual.md

Test 7-05 - Manual trigger ======= To verify admin user can trigger a replication manually. User guide This test requires that at least two Harbor instances are running and available. Create a new replication rule whose triggering condition is set to manual and no filter is configured. Need at least one image is pushed to the project that the rule is applied to Login UI as admin user. In `Administration->Replications` page, choose the rule and click the `REPLICATE` button. Repeat steps 1-2 under `Projects->Project_Name->Replication` page. In step 2, the operation should success and a few jobs should be started. All the images under the project should be replicated to the remote registry. None
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: e5.5.1.en.md

Improved MongoDB connector performance, resulting in more efficient database interactions. This enhancement is supported by improvements in the MongoDB Erlang driver as well (). Fixed an issue that data integration configurations failed to load correctly during upgrades from EMQX version 5.0.2 to newer releases. Fixed an issue that users were unable to subscribe to or unsubscribe from shared topic filters via HTTP API. The affected APIs include: `/clients/:clientid/subscribe` `/clients/:clientid/subscribe/bulk` `/clients/:clientid/unsubscribe` `/clients/:clientid/unsubscribe/bulk` Fixed an issue where logs of the LDAP driver were not being captured. Now, all logs are recorded at the `info` level. The Prometheus API experienced crashes when the specified SSL certificate file did not exist in the given path. Now, when an SSL certificate file is missing, the `emqxcertexpiry_at` metric will report a value of 0, indicating the non-existence of the certificate. Redacted sensitive information in HTTP headers to exclude authentication and authorization credentials from `debug` level logs in the HTTP Server connector, mitigating potential security risks. Fixed an issue where the rule engine's SQL built-in function `datetounix_ts` produced incorrect results for dates starting from March 1st on leap years. Fixed a `function_clause` error in the IoTDB action caused by the absence of a `payload` field in query data. Fixed an issue where connections to the LDAP connector could unexpectedly disconnect after a certain period of time.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-07-19.md

Time: 9am PDT (12pm EDT, 5pm BST) Meeting location: https://docker.zoom.us/j/779801882 Announcement: Video recording: https://www.youtube.com/watch?v=04TsF72o-V4 Previous meeting notes: Introductions & Administrivia (5 min) WireGuard deep dive - @zx2c4 (45 min) Differences from other VPNs Cryptography Usage with network namespaces demo Project updates (10 min) Next meeting: 2017-08-02 deep dive TBD we can propose additional deep dives and discussion topics! WireGuard intro; are comprehensive, below is a small discussion of questions that occurred Jason Donenfeld the author and maintainer Patches for traditional userspace tools (ifupdown, OpenWRT/LEDE, OpenRC netifrc, NixOS, systemd-networkd WIP, NetworkManager WIP) available to allow ease of interface configuration demo ip and wg tools used to configure and inspect WireGuard interfaces no patches needed for iproute2, since the string "WireGuard" just gets passed to the kernel via netlink when doing `ip link add type wireguard` WireGuard can live in one netns, physical interface can live in another so you can put wg0 in a container as the only interface, and it must connect to the world via this interface No additional traffic necessary when packets are successfully sent/received When a unidirectional packet is sent, WireGuard sends back an empty ack packet Kernel networking stack is the one allocating the packet buffers, WireGuard doesn't allocate anything on top of this WireGuard overhead: ipv4 header (20 bytes) + udp header (8 bytes) + wireguard header (4 byte type, 4 byte keyid, 8 byte nonce, 16 byte authtag = 32 bytes) = 60 bytes performance fast, no copies across \*space ChaChaPoly is fast upstreaming status: no v1 posted need to move from ioctl => netlink need to improve kernel crypto API to remove allocations maturity officially "experimental" formally verified, "pretty damn stable" :) may break protocol, but hopefully not now that it's verified Next meeting August 2nd, please propose topics!
Project: KICS (Provisioning / Security & Compliance)
File: ea0ed1c7-9aef-4464-b7c7-94c762da3640.md

title: DB Security Group Open To Large Scope hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ea0ed1c7-9aef-4464-b7c7-94c762da3640 Query name: DB Security Group Open To Large Scope Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: The IP address in a DB Security Group must not have more than 256 hosts.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="22" name: create minimal aurora instance in default VPC and default subnet group community.aws.rds_instance: engine: aurora dbinstanceidentifier: ansible-test-aurora-db-instance instance_type: db.t2.small password: "{{ password }}" username: "{{ username }}" cluster_id: ansible-test-cluster dbsecuritygroups: ["example"] name: example ec2 group ec2_group: name: example description: an example EC2 group vpc_id: 12345 region: eu-west-1a awssecretkey: SECRET awsaccesskey: ACCESS rules: proto: tcp from_port: 80 to_port: 80 cidr_ip: 0.0.0.0/0 proto: tcp from_port: 22 to_port: 22 cidr_ip: 10.0.0.0/8 proto: tcp from_port: 443 to_port: 443 group_id: amazon-elb/sg-87654321/amazon-elb-sg proto: tcp from_port: 3306 to_port: 3306 group_id: 123412341234/sg-87654321/exact-name-of-sg proto: udp from_port: 10050 to_port: 10050 cidr_ip: 10.0.0.0/8 proto: udp from_port: 10051 to_port: 10051 group_id: sg-12345678 proto: icmp from_port: 8 # icmp type, -1 = any type to_port: -1 # icmp subtype, -1 = any subtype cidr_ip: 192.168.1.0/24 proto: all group_name: example ``` ```yaml title="Negative test num. 1 - yaml file" name: example ec2 group2 ec2_group: name: example1 description: an example EC2 group vpc_id: 12345 region: eu-west-1a awssecretkey: SECRET awsaccesskey: ACCESS rules: proto: tcp from_port: 80 to_port: 80 cidr_ip: 10.1.1.1/32 ```
Project: YDB (App Definition and Development / Database)
File: base_hierarchy.md

To host databases in {{ ydb-short-name }}, use the following directory structure: `/domain/account/directory/database`, where: A domain is the first-level element where all cluster resources are located. There can only be one domain per cluster. An account is a second-level element that defines the owner of a DB group. A directory is a third-level element defined by an account owner for grouping his or her databases. A database is a fourth-level element that corresponds to a DB. At the top hierarchy level, the cluster contains a single domain that hosts one or more accounts, while accounts host one or more directories that host databases. Using the hierarchy of entities, you can grant access rights and get aggregate or filtered monitoring indicators for the elements of any hierarchy level.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_remove_context.md

title: "Command - devspace remove context" sidebar_label: devspace remove context Removes a kubectl-context ``` devspace remove context [flags] ``` ``` Removes a kubectl-context Example: devspace remove context myspace ``` ``` -h, --help help for context ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```