cwielenb/CNCF-Dataset huggingface dataset:
Project: ArangoDB (App Definition and Development / Database)
File: basic_outcome.md

+++ title = "`basic_outcome<T>`" description = "A boolean concept matching types which are convertible to a `basic_outcome<T, EC, EP, NoValuePolicy>`." +++ If on C++ 20 or the Concepts TS is enabled, a boolean concept matching types which have `valuetype`, `errortype` and `novaluepolicytype` member typedefs; that the type is convertible to `basicresult<valuetype, errortype, novaluepolicytype>`; that `basicresult<valuetype, errortype, novaluepolicy_type>` is a base of the type. If without Concepts, a static constexpr bool which is true for types matching the same requirements, using a SFINAE based emulation. This concept matches any type which provides the same typedefs as a {{% api "basicresult<T, E, NoValuePolicy>" %}}, has that `basicresult` as a base class, and is implicitly convertible to `basicresult`. Whilst not guaranteed, it is very likely that the type is a `basicresult`, or inherits publicly from a `basicresult`. If you want something which matches any value-or-error type, consider {{% api "valueorerror<T>" %}}. If you want something which exactly matches `basicoutcome`, use {{% api "isbasicoutcome<T>" %}}. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::concepts` Header: `<boost/outcome/basic_result.hpp>`
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-show-columns.md

layout: global title: SHOW COLUMNS displayTitle: SHOW COLUMNS 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. Returns the list of columns in a table. If the table does not exist, an exception is thrown. ```sql SHOW COLUMNS table_identifier [ database ] ``` table_identifier* Specifies the table name of an existing table. The table may be optionally qualified with a database name. Syntax: `{ IN | FROM } [ databasename . ] tablename` Note: Keywords `IN` and `FROM` are interchangeable. database* Specifies an optional database name. The table is resolved from this database when it is specified. When this parameter is specified then table name should not be qualified with a different database name. Syntax: `{ IN | FROM } database_name` Note: Keywords `IN` and `FROM` are interchangeable. ```sql -- Create `customer` table in `salesdb` database; USE salesdb; CREATE TABLE customer( cust_cd INT, name VARCHAR(100), cust_addr STRING); -- List the columns of `customer` table in current database. SHOW COLUMNS IN customer; ++ | col_name| ++ | cust_cd| | name| |cust_addr| ++ -- List the columns of `customer` table in `salesdb` database. SHOW COLUMNS IN salesdb.customer; ++ | col_name| ++ | cust_cd| | name| |cust_addr| ++ -- List the columns of `customer` table in `salesdb` database SHOW COLUMNS IN customer IN salesdb; ++ | col_name| ++ | cust_cd| | name| |cust_addr| ++ ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: flink.md

Flink is a powerful high-performance distributed stream processing engine,More information about it you can,You can search for `Apache Flink` Begin with `flink.` Example: I set a precise Checkpoint for this job ``` env { parallelism = 1 flink.execution.checkpointing.unaligned.enabled=true } ``` Enumeration types are not currently supported, you need to specify them in the Flink conf file ,Only these types of Settings are supported for the time being:<br/> Integer/Boolean/String/Duration This is a simple job that runs on Flink Randomly generated data is printed to the console ``` env { parallelism = 1 checkpoint.interval = 5000 flink.execution.checkpointing.mode = "EXACTLY_ONCE" flink.execution.checkpointing.timeout = 600000 } source { FakeSource { row.num = 16 resulttablename = "fake_table" schema = { fields { c_map = "map<string, string>" c_array = "array<int>" c_string = string c_boolean = boolean c_int = int c_bigint = bigint c_double = double c_bytes = bytes c_date = date c_decimal = "decimal(33, 18)" c_timestamp = timestamp c_row = { c_map = "map<string, string>" c_array = "array<int>" c_string = string c_boolean = boolean c_int = int c_bigint = bigint c_double = double c_bytes = bytes c_date = date c_decimal = "decimal(33, 18)" c_timestamp = timestamp } } } } } transform { } sink{ Console{} } ``` After you pull the code to the local, go to the `seatunnel-examples/seatunnel-flink-connector-v2-example` module find `org.apache.seatunnel.example.flink.v2.SeaTunnelApiExample` To complete the operation of the job
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: 2019-01-01-Proposal-Template.md

|Tag |Value | |- | - | |Proposal || |Authors|, | |Review Manager | TBD | |Status |Proposal, Draft, Promoted, or Abandoned| |Implementations || |Issues || |Previous Revisions | | |Date |Responsible Party |Description | |- | - | - | A short description of what the feature is. Try to keep it to a single-paragraph "elevator pitch" so the reader understands what problem this proposal is addressing. Describe the problems that this proposal seeks to address. If the problem is that some common pattern is currently hard to express, show how one can currently get a similar effect and describe its drawbacks. If it's completely new functionality that cannot be emulated, motivate why this new functionality would help OpenAPI developers create better code. Describe your solution to the problem. Provide examples and describe how they work. Show how your solution is better than current workarounds: is it cleaner, safer, or more efficient? Describe the design of the solution in detail. This should include an exact description of the changes to the contents of the OpenAPI specification. That description should include a extract of each section of the OpenAPI specification which is impacted by the proposal with all proposed modifications applied. These extracts may be provided through additional files which are identified and described in this section. Proposals should be structure so that they can be handled by existing OAS compliant software. Any potential issues should be identified and discussed. Describe alternative approaches to addressing the same problem, and why you chose this approach instead.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: 2.18.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. The standard drupal based tasks that Lagoon ships with (Drush ....) have been flagged as deprecated and should not be used anymore. These will need to be replaced with . Example replacement tasks will be provided prior to their removal. This release introduces a deprecation of the `setEnvironmentServices` mutation to updated services for an environment, it is being replaced with `addOrUpdateEnvironmentService` and `deleteEnvironmentService`. This is because the type is being refactored to support additional information, and eventually additional functionality. For now, the actions-handler service will still support the older `setEnvironmentServices` for backwards compatibility for a short period to allow older versions of `lagoon-remote` to still work, but a new version of `lagoon-remote` will be available that will no longer provides the payload that the actions-handler uses. The value for `registry` which was previously required by the `lagoon-core` chart is no longer required. If you are using this, you will need to add it under the new `unauthenticatedRegistry` setting when installing `lagoon-remote` in the `lagoon-build-deploy` section of your values file. If you aren't using an actual registry and have the example `disabled-only-use-harbor-via-deploy-controller.invalid` value, then you do not need to do anything except you can now remove the `registry` setting from your core values file. The environment storage return field named `bytesUsed` is deprecated. The actual value stored is `kibibytes`. A new return field called `kibUsed` exists and should be used, the returned data is the same and both fields are still returned. `bytesUsed` will be removed in a future release, make any adjustments now to use `kibUsed`. This will be a breaking change in a future release. `addOrUpdateEnvironmentStorage` is deprecated, `addOrUpdateStorageOnEnvironment` is the replacement to use as it supports the updated input value for `kibUsed`. `addOrUpdateEnvironmentStorage` will be completely removed in a future release. The ability to configure projects to use different subsystems for managing deployments/tasks has been removed. Setting any values for the `activeSystems` fields on the project will have no effect and the fields will be removed in a future release.
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: templates.md

Cyclops renders the New Module form based on your Helm templates. We have a public where we created a couple of charts you can use. Alternatively, you can create your own Helm charts and use them as templates. Although we have a GitHub repository to store our charts, there are other ways of storing them. Cyclops can access charts stored in three different ways: 1. GitHub Repository 2. Helm Chart Repository 3. OCI Repository The `values.schema.json` is a necessary component in your templates. This file is usually used to impose a structure on the `values.yaml` file, but it is also crucial for rendering the GUI in Cyclops. You can learn more about it and how to create one by following . The schema is represented as a You can find a list of all the fields you can set below for each field type. In addition to the usual schema, we added more fields to help our users get as much from the UI as possible. | Name | Type | Description | Valid input | | :-- | | :-- | - | | `order` | string array | Defines the order of the fields in an object type property. <br/> Each time you use `properties`, you should also define the order of those properties | - | | `fileExtension` | string | Sometimes, you would like your text field not just to be a field but also to get some highlighting based on the type of string you are saving. You can specify that in this field | `text`, `sh`, `json`, `yaml`, `toml`, `javascript`, `typescript` |
Project: Stolon (App Definition and Development / Database)
File: forcefailover.md

You can force a "master" keeper failover using the This commands forces a keeper as "temporarily" failed. It's just a one shot operation, the sentinel will compute a new clusterdata considering the keeper as failed and then restore its state to the real one. For example, if the force failed keeper is a master, the sentinel will try to elect a new master. If no new master can be elected, the force failed keeper, if really healthy, will be re-elected as master To avoid losing any transaction when using asynchronous replication take a look at this recipe:
Project: YugabyteDB (App Definition and Development / Database)
File: custom_fake_data.md

Custom Fake Data ============================================================================== This extension is delivered with a small set of fake data by default. For each fake function ( `fakeemail()`, `fakefirst_name()`) we provide only 1000 unique values, and they are only in English. Here's how you can create your own set of fake data! Alternative fake data packages -- The projet is offering alternative fake datasets (currently only French). You can download the zip file containing the dataset and load it into the extension like this: Go to <https://gitlab.com/dalibo/postgresql_anonymizer/-/packages> Click on "data" Choose your prefered zip file and download it on your server Unzip the file into a folder (for example `/path/to/customcsvfiles/`) Run `SELECT anon.init('/path/to/customcsvfiles/')` Generate your own fake dataset -- As an example, here's a python script that will generate fake data for you: <https://gitlab.com/dalibo/postgresql_anonymizer/-/blob/master/python/populate.py> To produce 5000 emails in French & German, you'd call the scripts like this: ```shell populate.py --table email --locales fr,de --lines 5000 ``` This will output the fake data in `CSV` format. Use `populate.py --help` for more details about the script parameters. You can load the fake data directly into the extension like this: ```sql TRUNCATE anon.email; COPY anon.email FROM PROGRAM 'populate.py --table email --locales fr,de --lines 5000'; SELECT setval('anon.emailoidseq', max(oid)) FROM anon.email; CLUSTER anon.email; ``` IMPORTANT : This script is provided as an example, it is not officially supported. Load your own fake data If you want to use your own dataset, you can import custom CSV files with : ```sql SELECT anon.init('/path/to/customcsvfiles/') ``` Look at the `data` folder to find the format of the CSV files. Using the PostgreSQL Faker extension If you need more specialized fake data sets, please read the [Advanced Faking] section.
Project: Konveyor (App Definition and Development / Application Definition & Image Build)
File: installation-macos.md

Initialize `podman machine` using the below config ``` podman machine init --cpus 2 --memory 10240 --disk-size 20 podman machine set --rootful podman machine start ``` Create a Minikube cluster with podman as the driver option `minikube start --memory=9g --driver podman` Install ingress addon `minikube addons enable ingress` Install OLM to manage Konveyor operator `curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.21.2/install.sh | bash -s v0.21.2` Install Konveyor operator `kubectl create -f https://operatorhub.io/install/konveyor-operator.yaml` Verify if the Konveyor operator pod is running or not `kubectl get pods -n my-konveyor-operator` Once the operator pod is running, create a Tackle instance using the following ``` cat << EOF | kubectl apply -f - kind: Tackle apiVersion: tackle.konveyor.io/v1alpha1 metadata: name: tackle namespace: my-konveyor-operator spec: featureauthrequired: false EOF ``` Wait until Tackle pods are in running state ``` $ kubectl get pods -n my-konveyor-operator NAME READY STATUS RESTARTS AGE tackle-hub-7f7cc9d574-b5kkl 1/1 Running 0 109m tackle-operator-56c574d689-jmvs7 1/1 Running 0 111m tackle-ui-5bdb565bcd-g6gsr 1/1 Running 0 109m task-1-x6fmv 0/1 Completed 0 4m6s ``` Once they are running, access the Tackle UI, `kubectl port-forward service/tackle-ui 8080:8080 -n my-konveyor-operator` Note: add `--address` param if using aws ec2 instances
Project: StarRocks (App Definition and Development / Database)
File: DROP_ANALYZE.md

displayed_sidebar: "English" Deletes a custom collection task. By default, StarRocks automatically collects full statistics of a table. It checks for any data updates every 5 minutes. If data change is detected, data collection will be automatically triggered. If you do not want to use automatic full collection, you can set the FE configuration item `enablecollectfull_statistic` to `false` and customize a collection task. This statement is supported from v2.4. ```SQL DROP ANALYZE <ID> ``` The task ID can be obtained by using the SHOW ANALYZE JOB statement. ```SQL DROP ANALYZE 266030; ``` : customize an automatic collection task. : view the status of an automatic collection task. : cancel a custom collection task that is running. For more information about collecting statistics for CBO, see .
Project: ArangoDB (App Definition and Development / Database)
File: copy_file.md

+++ title = "The Filesystem TS" description = "" weight = 10 tags = ["dual-api"] +++ Something which has long annoyed the purists in the C++ leadership is the problem of dual overloads in `error_code` capable standard library APIs. Consider the API from the Filesystem TS: {{% snippet "outcomepayload.cpp" "filesystemapi_problem" %}} Before Outcome, the common design pattern was to provide throwing and non-throwing overloads of every API. As you can see above, the throwing API throws a exception type which carries additional information, specifically two paths. These paths may refer to the files which were the source of any failure. However the non-throwing overload does not provide this additional information, which can make it more annoying to use the non-throwing overload sometimes. What if we could replace these two overloads of every API in the Filesystem TS with a single API, and additionally have the non-throwing edition return the exact same additional information as the throwing edition?
Project: Harbor (Provisioning / Container Registry)
File: 9-14-LDAP-user-pull-unsigned-images.md

Test 9-14 User pull unsigned images(LDAP images) ======= To verify whether user can pull unsigned images with content trust enabled. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a LDAP or AD server. A Linux host with Docker CLI(Docker client)installed. A non-admin user that has at least one project as project admin. Same as Test 9-04 except that users are from LDAP/AD. Same as Test 9-04. None
Project: Harbor (Provisioning / Container Registry)
File: 6-01-OVA-upgrade.md

Test 6-01 - OVA Upgrade ======= To verify that an OVA version of Harbor can be upgraded when no changes to the number of OVA params. User guide, installation guide of Harbor OVA version. This test requires an upgrade binary of Harbor. A running version of older version of Harbor OVA version. A vCenter, at least an ESX host. A linux host with Docker CLI installed (Docker client). TBD Normal flow should include rollback steps. TBD None
Project: YugabyteDB (App Definition and Development / Database)
File: execute_statement.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="413" height="80" viewbox="0 0 413 80"><path class="connector" d="M0 52h15m76 0h10m54 0h30m25 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h34m24 0h35q5 0 5 5v20q0 5-5 5m-5 0h30m25 0h20m-228 0q5 0 5 5v8q0 5 5 5h203q5 0 5-5v-8q0-5 5-5m5 0h15"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="76" height="25" rx="7"/><text class="text" x="25" y="52">EXECUTE</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="101" y="35" width="54" height="25"/><text class="text" x="111" y="52">name</text></a><rect class="literal" x="185" y="35" width="25" height="25" rx="7"/><text class="text" x="195" y="52">(</text><rect class="literal" x="269" y="5" width="24" height="25" rx="7"/><text class="text" x="279" y="22">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#expression"><rect class="rule" x="240" y="35" width="83" height="25"/><text class="text" x="250" y="52">expression</text></a><rect class="literal" x="353" y="35" width="25" height="25" rx="7"/><text class="text" x="363" y="52">)</text><polygon points="409,59 413,59 413,45 409,45" style="fill:black;stroke-width:0"/></svg>
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.14.md

RabbitMQ `3.9.14` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 23.2, and supports Erlang 24. has more details on Erlang version requirements for RabbitMQ. Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and a more consistent release schedule. Restart of a node that hosted one or more stream leaders resulted in their consumers not "re-attaching" to the newly elected leader. GitHub issue: Large fanouts experienced a performance regression when streams were not enabled using a feature flag. GitHub issue: Stream management plugin did not support mixed version clusters. GitHub issue: Stream deletion did not result in a `basic.cancel` being sent to AMQP 0-9-1 consumers. GitHub issue: Stream clients did not receive a correct stream unavailability error in some cases. GitHub issue: It is again possible to clear user tags and update the password in a single operation. GitHub issue: Forward compatibility with Erlang 25. GitHub issue: File handle cache efficiency improvements. Contributed by @felixhuettner. GitHub issue: Uknown stream properties (e.g. those requested by a node that runs a newer version) are now handled gracefully. GitHub issue: Temporary hostname resolution issues (attempts that fail with `nxdomain`) are now handled more gracefully and with a delay of several seconds. GitHub issue: Build time compatibility with Elixir 1.13. GitHub issue: `authoauth2.additionalscopes_key` in `rabbitmq.conf` was not converted correctly during configuration translation and thus had no effect. Contributed by @luos. GitHub issue: Adapt to a breaking Erlang 24.3 LDAP client change. GitHub issue: Shovels now can be declared with `delete-after` parameter set to `0`. Such shovels will immediately stop instead of erroring and failing to start after a node restart. Contributed by @luos. GitHub issue: Support for Consul 1.1 when an operation is attempted on a non-existent health check. Suggested by @maestroes. GitHub issue: Ra was `genbatchserver` was To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.14.tar.xz` instead of the source tarball produced by GitHub.
Project: Chef Infra (Provisioning / Automation & Configuration)
File: ENHANCEMENT_REQUEST_TEMPLATE.md

name: Enhancement Request about: I have a suggestion (and may want to implement it )! labels: "Status: Untriaged" <! What you are trying to achieve that you can't? --> <! What kind of user do you believe would utilize this enhancement, and how many users might want this functionality --> <! Is there a current alternative that you can utilize to workaround the lack of this enhancement --> <! The best way to ensure your enhancement is built is to help implement the enhancement yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->
Project: ClickHouse (App Definition and Development / Database)
File: v23.5.3.24-stable.md

sidebar_position: 1 sidebar_label: 2023 Fix Log family table return wrong rows count after truncate (). Fix bug in `uniqExact` parallel merging (). Revert recent grace hash join changes (). Avoid storing logs in Keeper containing unknown operation (). Add compat setting for non-const timezones (). Fix iceberg V2 optional metadata parsing (). Fix subtly broken copy-on-write of ColumnLowCardinality dictionary (). Generate safe IVs (). Don't mark a part as broken on `Poco::TimeoutException` (). Fix a versions' tweak for tagged commits, improve version_helper (). Sqlancer has changed master to main ().