cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_list-backup-policy.md

title: kbcli cluster list-backup-policy List backups policies. ``` kbcli cluster list-backup-policy [flags] ``` ``` kbcli cluster list-backup-policy kbcli cluster list-bp mycluster ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. -h, --help help for list-backup-policy -o, --output format prints the output in the specified format. Allowed values: table, json, yaml, wide (default table) -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. --show-labels When printing, show all labels as the last column (default hide labels column) ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Cluster command.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.3.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | bin/hadoop dfs -rm \<dir\> crashes in log4j code | Major | . | Owen O'Malley | Owen O'Malley | | | The new logging framework puts application logs into server directory in hadoop.log | Major | . | Owen O'Malley | Owen O'Malley | | | the reduce tasks do not report progress if they the map output locations is empty. | Major | . | Mahadev konar | Mahadev konar | | | record io translator doesn't strip path names | Major | record | Owen O'Malley | Milind Bhandarkar | | | No appenders could be found for logger | Major | . | Owen O'Malley | Owen O'Malley |
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Example_Delay.md

```java import org.apache.rocketmq.client.consumer.DefaultMQPushConsumer; import org.apache.rocketmq.client.consumer.listener.ConsumeConcurrentlyContext; import org.apache.rocketmq.client.consumer.listener.ConsumeConcurrentlyStatus; import org.apache.rocketmq.client.consumer.listener.MessageListenerConcurrently; import org.apache.rocketmq.common.message.MessageExt; import java.util.List; public class ScheduledMessageConsumer { public static void main(String[] args) throws Exception { // Instantiate message consumer DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("ExampleConsumer"); // Specify name server addresses consumer.setNamesrvAddr("localhost:9876"); // Subscribe topics consumer.subscribe("TestTopic", "*"); // Register message listener consumer.registerMessageListener(new MessageListenerConcurrently() { @Override public ConsumeConcurrentlyStatus consumeMessage(List<MessageExt> messages, ConsumeConcurrentlyContext context) { for (MessageExt message : messages) { // Print approximate delay time period System.out.println("Receive message[msgId=" + message.getMsgId() + "] " (System.currentTimeMillis() - message.getStoreTimestamp()) + "ms later"); } return ConsumeConcurrentlyStatus.CONSUME_SUCCESS; } }); // Launch consumer consumer.start(); } } ``` ```java import org.apache.rocketmq.client.producer.DefaultMQProducer; import org.apache.rocketmq.common.message.Message; public class ScheduledMessageProducer { public static void main(String[] args) throws Exception { // Instantiate a producer to send scheduled messages DefaultMQProducer producer = new DefaultMQProducer("ExampleProducerGroup"); // Specify name server addresses producer.setNamesrvAddr("localhost:9876"); // Launch producer producer.start(); int totalMessagesToSend = 100; for (int i = 0; i < totalMessagesToSend; i++) { Message message = new Message("TestTopic", ("Hello scheduled message " + i).getBytes()); // This message will be delivered to consumer 10 seconds later. message.setDelayTimeLevel(3); // Send the message producer.send(message); } // Shutdown producer after use. producer.shutdown(); } } ``` You should see messages are consumed about 10 seconds later than their storing time. For example, in e-commerce, if an order is submitted, a delay message can be sent, and the status of the order can be checked after 1 hour. If the order is still unpaid, the order can be cancelled and the inventory released. ```java // org/apache/rocketmq/store/config/MessageStoreConfig.java private String messageDelayLevel = "1s 5s 10s 30s 1m 2m 3m 4m 5m 6m 7m 8m 9m 10m 20m 30m 1h 2h"; ``` Nowadays RocketMq does not support any time delay. It needs to set several fixed delay levels, which correspond to level 1 to 18 from 1s to 2h. Message consumption failure will enter the delay message queue. Message sending time is related to the set delay level and the number of retries. See `SendMessageProcessor.java`
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.14.md

RabbitMQ `3.7.14` is a maintenance release. It focuses on bug fixes and minor usability improvements. This release or later. Per the new Erlang version support policy in effect starting with January 2019, this release . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `20.3.x` and `21.x`. This release requires Erlang/OTP 20.3 or later. When upgrading to this release and upgrading Erlang to 21.x at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . TCP and TLS listeners are started later to reduce the probability of clients connecting to and performing operations on a node that's not fully initialised. GitHub issue: Reduced schema data store locking for binding operations. GitHub issue: More informative and user-friendly help messages produced by `help` and `help [command]` commands. GitHub issue: Groups of upstream URIs were not formatted correctly. Contributed by . GitHub issue: `management.load_definitions` now can point at a directory of definition files, not just a single file. GitHub issue: Federation links could fail to start with an `{error, already_started}`. GitHub issues: , RPM package post-install scripts now restart the node in case it was running before the upgrade. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-3.7.14.tar.gz`.
Project: ClickHouse (App Definition and Development / Database)
File: blob_storage_log.md

slug: /en/operations/system-tables/blobstoragelog Contains logging entries with information about various blob storage operations such as uploads and deletes. Columns: `hostname` () Hostname of the server executing the query. `event_date` () Date of the event. `event_time` () Time of the event. `eventtimemicroseconds` () Time of the event with microseconds precision. `event_type` () Type of the event. Possible values: `'Upload'` `'Delete'` `'MultiPartUploadCreate'` `'MultiPartUploadWrite'` `'MultiPartUploadComplete'` `'MultiPartUploadAbort'` `query_id` () Identifier of the query associated with the event, if any. `thread_id` () Identifier of the thread performing the operation. `thread_name` () Name of the thread performing the operation. `disk_name` () Name of the associated disk. `bucket` () Name of the bucket. `remote_path` () Path to the remote resource. `local_path` () Path to the metadata file on the local system, which references the remote resource. `data_size` () Size of the data involved in the upload event. `error` () Error message associated with the event, if any. Example Suppose a blob storage operation uploads a file, and an event is logged: ```sql SELECT * FROM system.blobstoragelog WHERE queryid = '7afe0450-504d-4e4b-9a80-cd9826047972' ORDER BY eventdate, eventtimemicroseconds \G ``` ```text Row 1: hostname: clickhouse.eu-central1.internal event_date: 2023-10-31 event_time: 2023-10-31 16:03:40 eventtimemicroseconds: 2023-10-31 16:03:40.481437 event_type: Upload query_id: 7afe0450-504d-4e4b-9a80-cd9826047972 thread_id: 2381740 diskname: disks3 bucket: bucket1 remote_path: rrr/kxo/tbnqtrghgtnxkzgtcrlutwuslgawe localpath: store/654/6549e8b3-d753-4447-8047-d462df6e6dbe/tmpinsertall110/checksums.txt data_size: 259 error: ``` In this example, upload operation was associated with the `INSERT` query with ID `7afe0450-504d-4e4b-9a80-cd9826047972`. The local metadata file `store/654/6549e8b3-d753-4447-8047-d462df6e6dbe/tmpinsertall110/checksums.txt` refers to remote path `rrr/kxo/tbnqtrghgtnxkzgtcrlutwuslgawe` in bucket `bucket1` on disk `disks3`, with a size of 259 bytes. See Also
Project: ko (App Definition and Development / Application Definition & Image Build)
File: go-packages.md

`ko`'s functionality can be consumed as a library in a Go application. To build an image, use , and publish it with . This is a minimal example of using the packages together, to implement the core subset of `ko`'s functionality: ```go package main import ( "context" "fmt" "log" "github.com/google/go-containerregistry/pkg/authn" "github.com/google/go-containerregistry/pkg/name" "github.com/google/go-containerregistry/pkg/v1/remote" "github.com/google/ko/pkg/build" "github.com/google/ko/pkg/publish" ) const ( baseImage = "cgr.dev/chainguard/static:latest" targetRepo = "example.registry/my-repo" importpath = "github.com/my-org/miniko" commitSHA = "deadbeef" ) func main() { ctx := context.Background() b, err := build.NewGo(ctx, ".", build.WithPlatforms("linux/amd64"), // only build for these platforms. build.WithBaseImages(func(ctx context.Context, _ string) (name.Reference, build.Result, error) { ref := name.MustParseReference(baseImage) base, err := remote.Index(ref, remote.WithContext(ctx)) return ref, base, err })) if err != nil { log.Fatalf("NewGo: %v", err) } r, err := b.Build(ctx, importpath) if err != nil { log.Fatalf("Build: %v", err) } p, err := publish.NewDefault(targetRepo, // publish to example.registry/my-repo publish.WithTags([]string{commitSHA}), // tag with :deadbeef publish.WithAuthFromKeychain(authn.DefaultKeychain)) // use credentials from ~/.docker/config.json if err != nil { log.Fatalf("NewDefault: %v", err) } ref, err := p.Publish(ctx, r, importpath) if err != nil { log.Fatalf("Publish: %v", err) } fmt.Println(ref.String()) } ```
Project: KICS (Provisioning / Security & Compliance)
File: ee3b1557-9fb5-4685-a95d-93f1edf2a0d7.md

title: ALB Listening on HTTP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ee3b1557-9fb5-4685-a95d-93f1edf2a0d7 Query name: ALB Listening on HTTP Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Application Load Balancer (alb) Listener should not listen on HTTP<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" resource "alicloudalblistener" "positive" { loadbalancerid = alicloudalbloadbalancer.default3.id listener_protocol = "HTTP" listener_port = 443 listener_description = "createdByTerraform" default_actions { type = "ForwardGroup" forwardgroupconfig { servergrouptuples { servergroupid = alicloudalbserver_group.default.id } } } certificates { certificateid = join("", [alicloudsslcertificatesservice_certificate.default.id, "-cn-hangzhou"]) } acl_config { acl_type = "White" acl_relations { aclid = alicloudalb_acl.example.id } } } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudalblistener" "negative" { loadbalancerid = alicloudalbloadbalancer.default3.id listener_protocol = "HTTPS" listener_port = 443 listener_description = "createdByTerraform" default_actions { type = "ForwardGroup" forwardgroupconfig { servergrouptuples { servergroupid = alicloudalbserver_group.default.id } } } certificates { certificateid = join("", [alicloudsslcertificatesservice_certificate.default.id, "-cn-hangzhou"]) } acl_config { acl_type = "White" acl_relations { aclid = alicloudalb_acl.example.id } } } ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: 2.17.0.md

lagoon lagoon-ui lagoon-build-deploy lagoon-core chart lagoon-remote chart There are no required actions or considerations with this release. As always, we suggest upgrading all minor versions. This release introduces a new active/standby task image that does not require the use of the . Dioscuri is deprecated and will eventually be removed from the `lagoon-remote` helm chart. If you use active/standby functionality in your clusters, you should upgrade to lagoon v2.17.0 and update your remote clusters to the version of the `lagoon-remote` helm chart the v2.17.0 release says to use (see release notes for v2.17.0) Support for Harbor in the API will be removed in a future release. If you currently have your core installation with Harbor support, you should move to using the integration within lagoon-remote instead. See the documentation and read the section about Harbor. Support for Harbor 2.1.x (chart version 1.5.x) and older in `lagoon-remote` will be removed in a future release. You should consider upgrading Harbor to a newer version (currently Lagoon supports up to v2.9.x (chart version 1.13.x)), following any recommended upgrade paths from Harbor.
Project: YugabyteDB (App Definition and Development / Database)
File: metacat.md

title: Metacat linkTitle: Metacat description: Use Metacat with YSQL aliases: menu: preview_integrations: parent: data-discovery identifier: metacat weight: 571 type: docs is a metadata service for discovering, processing, and managing data. It provides a unified REST/Thrift interface to access metadata of various data stores. Metacat supports various data sources including PostgreSQL. Because YugabyteDB's YSQL API is wire-compatible with PostgreSQL, Metacat can connect to YugabyteDB as a data source using the . You can run the provided in the README of the Metacat GitHub repository against YugabyteDB. To do this, you need to make the following configuration changes: Replace the PostgreSQL Docker image with that of YugabyteDB. Specify the entrypoint command for the YugabyteDB Docker container. Change port from 5432 to 5433. Change username and password to yugabyte. Make changes in the following four files: Create a script file named `yb-init.sh` with the following content and place it under `metacat-functional-tests/metacat-test-cluster/datastores/postgres/docker-entrypoint-initdb.d/` in the repository. The script runs during container initialization to launch the YugabyteDB cluster. ```sh bin/yugabyted start sleep 5 bin/ysqlsh -h `hostname -i` -f /docker-entrypoint-initdb.d/world/world.sql tail -f /dev/null ``` In the `metacat-functional-tests/metacat-test-cluster/docker-compose.yml` file, change the following: Change the `image` to a YugabyteDB image. Add the `command` and set it to the location of the script file you created. Change the `POSTGRESUSER` and `POSTGRESPASSWORD`. Change the port number under `environment` for `storage-barrier` configuration. For example: ```yaml postgresql: image: yugabytedb/yugabyte:{{<yb-version version="preview" format="build">}} command: /bin/bash /docker-entrypoint-initdb.d/yb-init.sh volumes: ./datastores/postgres/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d:ro environment: POSTGRES_USER=yugabyte POSTGRES_PASSWORD=yugabyte POSTGRES_DB=metacat labels: "com.netflix.metacat.oss.test" ... storage-barrier: image: martin/wait:latest depends_on: hive-metastore-db postgresql polaris-crdb-init environment: TARGETS=postgresql:5433,hive-metastore-db:3306 labels: "com.netflix.metacat.oss.test" ``` In the `metacat-functional-tests/metacat-test-cluster/etc-metacat/catalog/postgresql-96-db.properties` file, change the port, username, and password as follows: ```java javax.jdo.option.url=jdbc:postgresql://postgresql:5433/world javax.jdo.option.username=yugabyte javax.jdo.option.driverClassName=org.postgresql.Driver javax.jdo.option.password=yugabyte ``` In `metacat-functional-tests/metacat-test-cluster/datastores/postgres/docker-entrypoint-initdb.d/world/world.sql`, comment out the `SET client_encoding` SQL command by prefixing it with `--`, as it is not supported in YugabyteDB: ```sql -- SET client_encoding = 'LATIN1'; ```
Project: Chef Infra (Provisioning / Automation & Configuration)
File: license_acceptance.md

Starting with Chef Client 15 users are required to accept the [Chef EULA](https://www.chef.io/end-user-license-agreement/) to use the Chef Software distribution. This document aims to explain how the `license-acceptance` gem and the `chef` gem interact. The overall goal is that the license acceptance flow is invoked as early as possible in the binary (EG, `chef-client`) execution. Failure to accept the license causes the binary to immediately exit with code `172`. For an explanation of how this is achieved please see the [Ruby README](https://github.com/chef/license-acceptance/tree/main/components/ruby) in the license-acceptance repo. For an overall view of how the license-acceptance gem works, its specification, how marker files are stored, etc. please see the .
Project: ClickHouse (App Definition and Development / Database)
File: svg.md

slug: /en/sql-reference/functions/geo/svg sidebar_label: SVG title: "Functions for Generating SVG images from Geo data" Returns a string of select SVG element tags from Geo data. Syntax ``` sql Svg(geometry,[style]) ``` Aliases: `SVG`, `svg` Parameters `geometry` Geo data. . `style` Optional style name. . Returned value The SVG representation of the geometry: SVG circle SVG polygon SVG path Type: Examples Circle Query: ```sql SELECT SVG((0., 0.)) ``` Result: ```response <circle cx="0" cy="0" r="5" style=""/> ``` Polygon Query: ```sql SELECT SVG([(0., 0.), (10, 0), (10, 10), (0, 10)]) ``` Result: ```response <polygon points="0,0 0,10 10,10 10,0 0,0" style=""/> ``` Path Query: ```sql SELECT SVG([[(0., 0.), (10, 0), (10, 10), (0, 10)], [(4., 4.), (5, 4), (5, 5), (4, 5)]]) ``` Result: ```response <g fill-rule="evenodd"><path d="M 0,0 L 0,10 L 10,10 L 10,0 L 0,0M 4,4 L 5,4 L 5,5 L 4,5 L 4,4 z " style=""/></g> ```
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_generate.md

Generate relevant information ``` -h, --help help for generate ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` - -
Project: ClickHouse (App Definition and Development / Database)
File: storage_policies.md

slug: /en/operations/system-tables/storage_policies Contains information about storage policies and volumes defined in the . Columns: `policy_name` () Name of the storage policy. `volume_name` () Volume name defined in the storage policy. `volumepriority` () Volume order number in the configuration, the data fills the volumes according this priority, i.e. data during inserts and merges is written to volumes with a lower priority (taking into account other rules: TTL, `maxdatapartsize`, `move_factor`). `disks` () Disk names, defined in the storage policy. `volume_type` () Type of volume. Can have one of the following values: `JBOD` `SINGLE_DISK` `UNKNOWN` `maxdatapart_size` () Maximum size of a data part that can be stored on volume disks (0 no limit). `move_factor` () Ratio of free disk space. When the ratio exceeds the value of configuration parameter, ClickHouse start to move data to the next volume in order. `prefernottomerge` () Value of the `prefernottomerge` setting. Should be always false. When this setting is enabled, you did a mistake. `performttlmoveoninsert` () Value of the `performttlmoveoninsert` setting. Disables TTL move on data part INSERT. By default if we insert a data part that already expired by the TTL move rule it immediately goes to a volume/disk declared in move rule. This can significantly slowdown insert in case if destination volume/disk is slow (e.g. S3). `load_balancing` () Policy for disk balancing. Can have one of the following values: `ROUND_ROBIN` `LEAST_USED` If the storage policy contains more then one volume, then information for each volume is stored in the individual row of the table.
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-11-2022-22-23-10_79781888.md

timestamp: "2022-10-11 22:22:55 UTC Tue" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.15" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"