cwielenb/CNCF-Dataset huggingface dataset:
Project: Harbor (Provisioning / Container Registry)
File: 2-34-admin-role-delete-projects.md

Test 2-34 - Admin User Delete Projects (DB Mode) ======= To verify that a user with system admin role can delete other user's projects when users are managed locally by Harbor (DB mode). User guide This test requires that two(2) Harbor instances are running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least two non-admin users. NOTE: The below non-admin user M should NOT be the same as the non-admin user in Test 2-24. Assign an non-admin user M with system admin role and act as an admin user. Repeat all steps in Test 2-24. A user with system admin role can perform all operations the same as the admin user. Same as Test 2-24. None
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-pivot.md

layout: global title: PIVOT Clause displayTitle: PIVOT Clause license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. The `PIVOT` clause is used for data perspective. We can get the aggregated values based on specific column values, which will be turned to multiple columns used in `SELECT` clause. The `PIVOT` clause can be specified after the table name or subquery. ```sql PIVOT ( { aggregateexpression [ AS aggregateexpression_alias ] } [ , ... ] FOR columnlist IN ( expressionlist ) ) ``` aggregate_expression* Specifies an aggregate expression (SUM(a), COUNT(DISTINCT b), etc.). aggregate_expression_alias* Specifies an alias for the aggregate expression. column_list* Contains columns in the `FROM` clause, which specifies the columns we want to replace with new columns. We can use brackets to surround the columns, such as `(c1, c2)`. expression_list* Specifies new columns, which are used to match values in `column_list` as the aggregating condition. We can also add aliases for them. ```sql CREATE TABLE person (id INT, name STRING, age INT, class INT, address STRING); INSERT INTO person VALUES (100, 'John', 30, 1, 'Street 1'), (200, 'Mary', NULL, 1, 'Street 2'), (300, 'Mike', 80, 3, 'Street 3'), (400, 'Dan', 50, 4, 'Street 4'); SELECT * FROM person PIVOT ( SUM(age) AS a, AVG(class) AS c FOR name IN ('John' AS john, 'Mike' AS mike) ); ++--+++++ | id | address | johna | johnc | mikea | mikec | ++--+++++ | 200 | Street 2 | NULL | NULL | NULL | NULL | | 100 | Street 1 | 30 | 1.0 | NULL | NULL | | 300 | Street 3 | NULL | NULL | 80 | 3.0 | | 400 | Street 4 | NULL | NULL | NULL | NULL | ++--+++++ SELECT * FROM person PIVOT ( SUM(age) AS a, AVG(class) AS c FOR (name, age) IN (('John', 30) AS c1, ('Mike', 40) AS c2) ); ++--+-+-+-+-+ | id | address | c1a | c1c | c2a | c2c | ++--+-+-+-+-+ | 200 | Street 2 | NULL | NULL | NULL | NULL | | 100 | Street 1 | 30 | 1.0 | NULL | NULL | | 300 | Street 3 | NULL | NULL | NULL | NULL | | 400 | Street 4 | NULL | NULL | NULL | NULL | ++--+-+-+-+-+ ```
Project: Druid (App Definition and Development / Database)
File: insert-segment-to-db.md

id: insert-segment-to-db title: "insert-segment-to-db tool" <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. --> In older versions of Apache Druid, `insert-segment-to-db` was a tool that could scan deep storage and insert data from there into Druid metadata storage. It was intended to be used to update the segment table in the metadata storage after manually migrating segments from one place to another, or even to recover lost metadata storage by telling it where the segments are stored. In Druid 0.14.x and earlier, Druid wrote segment metadata to two places: the metadata store's `druid_segments` table, and `descriptor.json` files in deep storage. This practice was stopped in Druid 0.15.0 as part of , for the following reasons: If any segments are manually dropped or re-enabled by cluster operators, this information is not reflected in deep storage. Restoring metadata from deep storage would undo any such drops or re-enables. Ingestion methods that allocate segments optimistically (such as native Kafka or Kinesis stream ingestion, or native batch ingestion in 'append' mode) can write segments to deep storage that are not meant to actually be used by the Druid cluster. There is no way, while purely looking at deep storage, to differentiate the segments that made it into the metadata store originally (and therefore should be used) from the segments that did not (and therefore should not be used). Nothing in Druid other than the `insert-segment-to-db` tool read the `descriptor.json` files. After this change, Druid stopped writing `descriptor.json` files to deep storage, and now only writes segment metadata to the metadata store. This meant the `insert-segment-to-db` tool is no longer useful, so it was removed in Druid 0.15.0. It is highly recommended that you take regular backups of your metadata store, since it is difficult to recover Druid clusters properly without it.
Project: ClickHouse (App Definition and Development / Database)
File: settings-profiles.md

slug: /en/operations/settings/settings-profiles sidebar_position: 61 sidebar_label: Settings Profiles A settings profile is a collection of settings grouped under the same name. :::note ClickHouse also supports for managing settings profiles. We recommend using it. ::: The profile can have any name. You can specify the same profile for different users. The most important thing you can write in the settings profile is `readonly=1`, which ensures read-only access. Settings profiles can inherit from each other. To use inheritance, indicate one or multiple `profile` settings before the other settings that are listed in the profile. In case when one setting is defined in different profiles, the latest defined is used. To apply all the settings in a profile, set the `profile` setting. Example: Install the `web` profile. ``` sql SET profile = 'web' ``` Settings profiles are declared in the user config file. This is usually `users.xml`. Example: ``` xml <!-- Settings profiles --> <profiles> <!-- Default settings --> <default> <!-- The maximum number of threads when running a single query. --> <maxthreads>8</maxthreads> </default> <!-- Settings for queries from the user interface --> <web> <maxrowstoread>1000000000</maxrowstoread> <maxbytestoread>100000000000</maxbytestoread> <maxrowstogroupby>1000000</maxrowstogroupby> <groupbyoverflowmode>any</groupbyoverflowmode> <maxrowstosort>1000000</maxrowstosort> <maxbytestosort>1000000000</maxbytestosort> <maxresultrows>100000</maxresultrows> <maxresultbytes>100000000</maxresultbytes> <resultoverflowmode>break</resultoverflowmode> <maxexecutiontime>600</maxexecutiontime> <minexecutionspeed>1000000</minexecutionspeed> <timeoutbeforecheckingexecutionspeed>15</timeoutbeforecheckingexecutionspeed> <maxcolumnstoread>25</maxcolumnstoread> <maxtemporarycolumns>100</maxtemporarycolumns> <maxtemporarynonconstcolumns>50</maxtemporarynonconstcolumns> <maxsubquerydepth>2</maxsubquerydepth> <maxpipelinedepth>25</maxpipelinedepth> <maxastdepth>50</maxastdepth> <maxastelements>100</maxastelements> <maxsessionsforuser>4</maxsessionsforuser> <readonly>1</readonly> </web> </profiles> ``` The example specifies two profiles: `default` and `web`. The `default` profile has a special purpose: it must always be present and is applied when starting the server. In other words, the `default` profile contains default settings. The `web` profile is a regular profile that can be set using the `SET` query or using a URL parameter in an HTTP query.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.11.md

RabbitMQ `3.7.11` is a maintenance release. It focuses on bug fixes and minor usability improvements. This is the first release to require Erlang/OTP 20.3+. 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. Default CLI command exit code has changed from 70 (`EXUNAVAILABLE`) to 69 (`EXSOFTWARE`). This does not affect all commands and all error conditions, e.g. argument validation still uses code 64 (`EX_USAGE`) 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. This release requires Erlang/OTP `20.3.x`* or `21.x`. GitHub issue: Number of socket file descriptors used is now correctly incremented. GitHub issue: Configuration schema file was not copied during upgrades. GitHub issues: First heartbeat frame on a successfully negotiated connection is now sent after a half of the negotiated heartbeat timeout. Previously it was sent after a complete timeout. Since most connections have other activity after connection handshake is complete, this didn't have any visible effects on most systems. GitHub issue: If Syslog was configured to use TCP, the node could fail to start. GitHub issue: Several new `rabbitmq-diagnostics` commands useful for diagnostics and health checks. GitHub issues: , , All CLI tools now can display command-specific help with `[command name] --help`, e.g. `rabbitmqctl set_policy --help` GitHub issue: `rabbitmqadmin` now defines an exception not available in Python 2, making TCP connection error reporting more similar with that on Python 3. GitHub issue: When an EC2 API endpoint could not be reached, the plugin terminated in a way that brought down the entire node with it. GitHib issue: Avoid using a private socket API function that's likely going away in Erlang 22. GitHub issue: Default topic exchange used by the plugin is now configurable. GitHub issue: Avoid using a private socket API function that's likely going away in Erlang 22. GitHub issue: The new style config format did not support `authcache.cacherefusals` GitHub issue: Avoid using a private socket API function that's likely going away in Erlang 22. 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.11.tar.gz`.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.8.md

RabbitMQ `3.11.8` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Stream throughput improvements for workloads with a lot of very small (say, less than 10 bytes) messages. GitHub issue: `rabbitmqctl hash_password` is a new command that produces a of the provided password. Contributed by @SimonUnge (AWS). GitHub issue: `rabbitmq-diagnostics checkportconnectivity` now supports a new optional flag, `--address`, that makes the check connect to a specific IP address instead of resolving node's hostname. This is useful when target node is configured to only listen for connections on one interface but not others: ``` shell rabbitmq-diagnostics checkportconnectivity --address 127.0.0.1 rabbitmq-diagnostics checkportconnectivity --address "::1" ``` GitHub issue: User filtering combined with pagination in the management UI did not work as expected. GitHub issue: Correctly format JSON field value in channel detail API response. Contributed @Syuparn. GitHub issue: AMQP 1.0 connection churn resulted in a memory leak. GitHub issue: STOMP client subscriptions to a destination that is an AMQP 0-9-1 exchange now declares auto-delete, exclusive queues (previously only auto-delete) as promised in the docs. Contributed by @csicar. GitHub issue: `osiris` was upgraded `thoas` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.8.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: 6ea57c8b-f9c0-4ec7-bae3-bd75a9dee27d.md

title: SDB Domain Declared As A Resource hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6ea57c8b-f9c0-4ec7-bae3-bd75a9dee27d Query name: SDB Domain Declared As A Resource Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: SimpleDB Domain resource should not be declared<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" AWSTemplateFormatVersion: "2010-09-09" Description: "SDB Domain declared" Resources: HostedZone: Type: AWS::Route53::HostedZone Properties: Name: "HostedZone" SBDDomain: Type: AWS::SDB::Domain Properties: Description: "Some information" ``` ```json title="Positive test num. 2 - json file" hl_lines="11" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "SDB Domain declared", "Resources": { "HostedZone": { "Type": "AWS::Route53::HostedZone", "Properties": { "Name": "HostedZone" } }, "SBDDomain": { "Type": "AWS::SDB::Domain", "Properties": { "Description": "Some information" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: "SDB Domain declared" Resources: HostedZone: Type: AWS::Route53::HostedZone Properties: Name: "HostedZone" ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "SDB Domain declared", "Resources": { "HostedZone": { "Type": "AWS::Route53::HostedZone", "Properties": { "Name": "HostedZone" } } } } ```
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_CloudWatch_Events.md

The following is a Lambda function that receives Amazon CloudWatch event record data as input and writes event detail 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, event events.CloudWatchEvent) { fmt.Printf("Detail = %s\n", event.Detail) } ``` If you have a constant JSON text in a CloudWatch Scheduled Event, it can be accessed either by explicitly defining a structure for the json payload you would expect: ```go type MyRequest struct { Name string `json:"name"` } func handler(ctx context.Context, req MyRequest) { } ``` or by accepting raw json blob as is: ```go func handler(ctx context.Context, b json.RawMessage) { // json.RawMessage is basically []byte which can be unmarshalled } ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: create-a-component.md

id: create-a-component title: Create a Component description: Leverage the scaffolder to start creating components with best practices. Audience: Developers This guide will walk you through how to use Software Templates to create new components with baked in best practices. :::note If you're running Backstage with Node 20 or later, you'll need to pass the flag `--no-node-snapshot` to Node in order to use the templates feature. One way to do this is to specify the `NODEOPTIONS` environment variable before starting Backstage: `export NODEOPTIONS=--no-node-snapshot` ::: You should already have . You will also need to register the before moving forward. Go to `create` and choose to create a website with the `Example Node.js Template` Type in a name, let's use `tutorial` and click `Next Step` You should see the following screen: For host, it should default to github.com As owner, type your GitHub username For the repository name, type `tutorial`. Go to the next step Review the details of this new service, and press `Create` if you want to deploy it like this. You can follow along with the progress, and as soon as every step is finished, you can take a look at your new service
Project: ShardingSphere (App Definition and Development / Database)
File: format-sql.en.md

+++ title = "FORMAT SQL" weight = 2 +++ The `FORMAT SQL` syntax is used to parse `SQL` and output formatted `SQL` statement. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ParseSql ::= 'FORMAT' sqlStatement ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Column | Description | ||-| | formatted_result | formatted SQL statement | Parse `SQL` and output formatted `SQL` statement ```sql FORMAT SELECT * FROM t_order; ``` ```sql mysql> FORMAT SELECT * FROM t_order; +-+ | formatted_result | +-+ | SELECT * FROM t_order; | +-+ 1 row in set (0.00 sec) ``` `FORMAT`
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_sync.md

title: "Command - devspace list sync" sidebar_label: devspace list sync Lists sync configuration ``` devspace list sync [flags] ``` ``` Lists the sync configuration ``` ``` -h, --help help for sync ``` ``` --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") ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.20.0.md

id: v1.20.0 title: v1.20.0 description: Backstage Release v1.20.0 These are the release notes for the v1.20.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. The `--experimental-type-build` option is no longer supported by any commands in the Backstage CLI. Existing usage should be migrated to using instead. Due to some concerns about performance in larger monorepo setups and hot-reloading times, were looking to replace with longer term, and in this release were shipping experimental support for Vite behind an `EXPERIMENTAL_VITE` environment variable flag when running `yarn start` in the frontend. Please reach out by with any problems that you might be running into when using this experimental feature. Its finally here. Weve shipped support for `react-jsonschema-form@v5` which should be a completely non-breaking change for end users. Weve also tweaked some of the designs for some of the new Scaffolder Pages. You can read more in the The Catalog plugin now uses the `EntityPresentationApi` to decide how entities are rendered in the UI. This includes fetching catalog data in the background in order to show entities using their `metadata.title`. For more information, including how to customize the presentation, see , (documentation is in the works!). This release does not contain any security fixes. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.