cwielenb/CNCF-Dataset huggingface dataset:
Project: kpt (Provisioning / Automation & Configuration)
File: errors.md

Validation error messages and documentation are an important part of the UX in kpt. In fact, validation error messages are most likely the first thing users experience. The general philosophy here is to have precise, actionable, and consistent error messages. In most cases, the error message should provide enough information to resolve the issue. Prefer short descriptions that explain what caused the specific error and what to do to fix it. More extensive explanations and general rules (if they take more than a sentence to describe) are for documentation (which is automatically linked in error messages). Generally, documentation should expand on what the error message says and help the reader understand how to prevent future mistakes. In the table below, origin and scope of rules are denoted with a prefix K is inherited from ; rules with prefix R are specific to Kpt. <!-- prettier-ignore --> | Rule | Description | Examples | | | | | | K1 | Where possible, tell users what they CAN instead of what they CANNOT do. | | | K2 | When asserting a requirement in the positive, use "must". Avoid words like "should" as they imply that the assertion is optional. | a) "must be greater than 0" b) "must match regex '[a-z]+'" | | K3 | When asserting a formatting requirement in the negative, use "must not". Avoid words like "should not" as they imply that the assertion is optional. | "must not contain '..'" | | K5 | When referencing a user-provided string value, indicate the literal in quotes. N Use quotes (%q format specifier in Go) around user-provided values. This includes file paths. | "must not contain '..'" | | K6 | When referencing a field name, indicate the name in back-quotes. Where it's unclear from the message, reference the full field path. | "must be greater than `spec.request.size`" | | K7 | When specifying inequalities, use words rather than symbols. Do not use words like "larger than", "bigger than", "more than", "higher than", etc. | a) "must be less than 256" b) "must be greater than or equal to 0". | | K8 | When specifying numeric ranges, use inclusive ranges when possible. | | | R1 | If wrapping a runtime error, such as the result of a failed API Server call, use %w formatting verb in fmt.Errorf()(err) to include the root cause error. Refer to . | |
Project: StarRocks (App Definition and Development / Database)
File: CANCEL_DECOMMISSION.md

displayed_sidebar: "English" This statement is used to undo a node decommission. :::tip Only the `cluster_admin` role has the privilege to perform this operation. You can follow the instructions in to grant this privilege. ::: Syntax: ```sql CANCEL DECOMMISSION BACKEND "<host>:<heartbeatport>"[,"<host>:<heartbeatport>"...] ``` Cancel decommission of two nodes. ```sql CANCEL DECOMMISSION BACKEND "host1:port", "host2:port"; ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubedb.md

title: Uninstall KubeDB description: Uninstallation guide for KubeDB menu: docs_{{ .version }}: identifier: uninstall-kubedb-enterprise name: KubeDB parent: uninstallation-guide weight: 20 product_name: kubedb menuname: docs{{ .version }} sectionmenuid: setup To uninstall KubeDB, run the following command: <ul class="nav nav-tabs" id="installerTab" role="tablist"> <li class="nav-item"> <a class="nav-link active" id="helm3-tab" data-toggle="tab" href="#helm3" role="tab" aria-controls="helm3" aria-selected="true">Helm 3</a> </li> <li class="nav-item"> <a class="nav-link" id="script-tab" data-toggle="tab" href="#script" role="tab" aria-controls="script" aria-selected="false">YAML</a> </li> </ul> <div class="tab-content" id="installerTabContent"> <div class="tab-pane fade show active" id="helm3" role="tabpanel" aria-labelledby="helm3-tab"> In Helm 3, release names are . So, provide the namespace you used to install the operator when installing. ```bash $ helm uninstall kubedb --namespace kubedb ``` Helm does not delete CRD objects. You can delete the ones KubeDB created with the following commands: ```bash $ kubectl get crd -o name | grep kubedb.com | xargs kubectl delete ``` </div> <div class="tab-pane fade" id="script" role="tabpanel" aria-labelledby="script-tab"> If you prefer to not use Helm, you can generate YAMLs from KubeDB chart and uninstall using `kubectl`. ```bash $ helm template kubedb oci://ghcr.io/appscode-charts/kubedb \ --namespace kubedb | kubectl delete -f - ``` </div> </div>
Project: Meshery (Provisioning / Automation & Configuration)
File: kuberhealthy.md

layout: integration title: Kuberhealthy subtitle: Collaborative and visual infrastructure as code for Kuberhealthy image: /assets/img/integrations/kuberhealthy/icons/color/kuberhealthy-color.svg permalink: extensibility/integrations/kuberhealthy docURL: https://docs.meshery.io/extensibility/integrations/kuberhealthy description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.8.md

RabbitMQ `3.6.8` is a maintenance release that restores Erlang/OTP R16B03 and 17.x compatibility that was unintentionally affected in by producing that release on a significantly newer Erlang/OTP version. See the for general documentation on upgrades. This release has no incompatibilities with 3.6.7. See upgrade and compatibility nodes if upgrading from an earlier release. Erlang/OTP R16B03 and 17.x are supported again by producing this release on R16B03. Note that may require a later version. We recommend all users to upgrade to a 19.x series release if possible. See and guides for some Erlang/OTP installation options. GitHub issues: , Certain user permission violations were resulting in a 500 response and scary log entries. GitHub issue: Single atom proplist values no longer break JSON serialisation for endpoints such as `GET /api/overview`. GitHub issue: Web STOMP now accepts the same TCP listener options as core RabbitMQ and other plugins. GitHub issue: To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained. When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html. To upgrade a RabbitMQ cluster, follow the instructions . 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.6.8.tar.gz`.
Project: JReleaser (App Definition and Development / Application Definition & Image Build)
File: custom.md

name: Issue about: Report an issue title: '' labels: 'bug' assignees: '' <!-- Thank you for reporting an issue, please review the task list below before submitting the issue. Your issue report may be closed if the issue is incomplete and the below tasks not completed. NOTE: If you are unsure about something and the issue is more of a question a better place to ask questions is on our Discussions space (https://github.com/jreleaser/jreleaser/discussions) or at Stack Overflow (https://stackoverflow.com/tags/jreleaser. Please DO NOT use the issue tracker to ask questions. Documentation issues should be posted to https://github.com/jreleaser/jreleaser.github.io/issues --> [ ] Steps to reproduce provided [ ] Stacktrace (if present) provided [ ] Example that reproduces the problem (link to git repository is ideal) [ ] Full description of the issue provided (see below) TODO TODO TODO Tell us what should happen Tell us what happens instead Operating System: TODO JReleaser Version: TODO JDK Version: TODO Please paste stacktraces from `[out|build|target]/jreleaser/trace.log`.
Project: YugabyteDB (App Definition and Development / Database)
File: table-t2.md

title: table t2 linkTitle: table t2 headerTitle: Create and populate table t2 description: Creates and populate table t2 with data that allows the demonstration of the YSQL window functions. menu: v2.18: identifier: table-t2 parent: data-sets weight: 30 type: docs {{< note title=" " >}} Make sure that you read the section before running the script to create table "t2". In particular, it's essential that you have installed the extension. {{< /note >}} The rows in table "t2" are inserted in random order. It is used for demonstrating these window functions: , , , , , and . It contains eighteen rows. It has primary key "k" (`int`) whose values are the dense sequence from 1 through 18. The column "class" (`int`) has two distinct values, 1 and 2, and there are nine rows with each "class" value. The values for the column "score", for "class = 1", are the dense sequence from 1 through 9. And for "class = 2", there are deliberate duplicates so the 2 and 8 each occur twice and 1 and 9 are missing. This scheme allows the difference between `rank()` and `dense_rank()` to be seen. For maximum pedagogic effect, it uses the same technique that uses to ensure that, with no window `ORDER BY` clause, a `SELECT` will return rows in a random order. This `ysqlsh` script creates and populates able "t2". Save it as `t2.sql`. ```plpgsql -- Suppress the spurious warning that is raised -- when the to-be-deleted table doesn't yet exist. set clientminmessages = warning; drop type if exists rt cascade; drop table if exists t2; create table t2( surrogate_pk uuid primary key, class int not null, k int not null, score int not null, constraint t2_pk unique(class, k), constraint t2kpositive check(k > 0), constraint t2classpositive check(class > 0)); insert into t2(surrogate_pk, class, k, score) with v1 as ( values (1, 1, 1), (1, 2, 2), (1, 3, 3), (1, 4, 4), (1, 5, 5), (1, 6, 6), (1, 7, 7), (1, 8, 8), (1, 9, 9), (2, 10, 2), (2, 11, 2), (2, 12, 2), (2, 13, 4), (2, 14, 5), (2, 15, 6), (2, 16, 7), (2, 17, 7), (2, 18, 9)), v2 as ( select genrandomuuid() as r, column1, column2, column3 from v1) select r, column1, column2, column3 from v2 order by r; ``` Now inspect its contents: ```plpgsql -- Notice the absence of "ORDER BY". select class, k, score from t2; select class, k, score from t2 order by class, k; ``` Here is the result of the second `SELECT`. To make it easier to see the pattern, several blank lines have been manually inserted here between each successive set of rows with the same value for "class". And in the second set, which has ties, one blank line has been inserted between each tie group. ``` class | k | score -+-+- 1 | 1 | 1 1 | 2 | 2 1 | 3 | 3 1 | 4 | 4 1 | 5 | 5 1 | 6 | 6 1 | 7 | 7 1 | 8 | 8 1 | 9 | 9 2 | 10 | 2 2 | 11 | 2 2 | 12 | 2 2 | 13 | 4 2 | 14 | 5 2 | 15 | 6 2 | 16 | 7 2 | 17 | 7 2 | 18 | 9 ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_pubsub_subscription_iam_policy.md

+++ title = "googlepubsubsubscriptioniampolicy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlepubsubsubscriptioniampolicy" identifier = "inspec/resources/gcp/googlepubsubsubscriptioniampolicy.md googlepubsubsubscriptioniampolicy resource" parent = "inspec/resources/gcp" +++ A `googlepubsubsubscriptioniampolicy` is used to test a Google Subscription Iam Policy resource ```ruby describe googlepubsubsubscriptioniampolicy(project: "project", name: "name") do it { should exist } end googlepubsubsubscriptioniampolicy(project: "project", name: "name").bindings.each do |binding| describe binding do its('role') { should eq 'roles/editor'} its('members') { should include 'user:testuser@example.com'} end end ``` Properties that can be accessed from the `googlepubsubsubscriptioniampolicy` resource: `iambindingroles` : The list of roles that exist on the policy. `bindings` : Associates a list of members to a role. `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. `audit_configs` : Specifies cloud audit logging configuration for this policy. `service` : Specifies a service that will be enabled for audit logging. For example, `storage.googleapis.com`, `cloudsql.googleapis.com`. `allServices` is a special value that covers all services. `auditlogconfigs` : The configuration for logging of each type of permission. `log_type` : The log type that this config enables. For example, ADMINREAD, DATAWRITE or DATA_READ `exempted_members` : Specifies the identities that do not cause logging for this type of permission. Ensure the is enabled for the current project.
Project: FOSSA (Provisioning / Security & Compliance)
File: ruby.md

Ruby projects use a buildtool called `bundler` to manage their dependencies. We parse a lockfile or run the `bundle` cli to determine dependencies. | Strategy | Direct Deps | Transitive Deps | Edges | Tags | Container Scanning | | -- | | | | - | | | gemfilelock | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | | :whitecheckmark: | | bundleshow | :whitecheckmark: (unlabeled) | :whitecheckmark: (unlabeled) | :x: | | :x: | `gemfilelock`: Find all files named `Gemfile.lock` `bundleshow`: Find directories containing a `Gemfile` or `Gemfile.lock` TLDR: A perfect dependency graph will be found and dependencies location will also be known. The lockfile strategy attempts to parse Bundler's `Gemfile.lock` lockfile. This file is created by bundler itself after a build is completed and can be distributed in order to maintain reproducible builds. It contains the following information about a Ruby project: The location for each dependency. These locations are each separate sections and the ones of note are `GIT`, `PATH`, and `GEM` which provide their remote in the `remote: <location>` line. `GIT` and `GEM` type dependencies are supported. `PATH` and any others are not and will show up as `GEM` type dependencies. Each dependencies required dependencies. These required dependencies are listed in the remote sections directly following each dependency from that remote. All direct dependencies, listed in the `DEPENDENCIES` section. Platforms that this ruby project is compatible with, listed in the `PLATFORMS` sections. Version of `bundler` that was used to create the lockfile. The Lockfile strategy relies on parsing this `Gemfile.lock` file and extracting information from each of these sections. This strategy takes the following steps to create an accurate dependency graph. Example `Gemfile.lock`: ``` GIT remote: https://github.com/matthewd/rb-inotify.git revision: 856730aad4b285969e8dd621e44808a7c5af4242 branch: close-handling specs: rb-inotify (0.9.9) ffi (~> 1.0) PATH remote: . specs: activesupport (6.0.0.alpha) concurrent-ruby (~> 1.0, >= 1.0.2) i18n (>= 0.7, < 2) minitest (~> 5.1) rails (6.0.0.alpha) sprockets-rails (>= 2.0.0) GEM remote: https://rubygems.org/ specs: concurrent-ruby (1.0.5) ffi (1.9.21) i18n (1.0.1) concurrent-ruby (~> 1.0) minitest (5.11.3) rack (2.0.5) sprockets-rails (3.2.1) actionpack (>= 4.0) activesupport (>= 4.0) sprockets (>= 3.0.0) PLATFORMS java ruby x64-mingw32 x86-mingw32 DEPENDENCIES rails! rake (>= 11.1) rb-inotify! BUNDLED WITH 1.16.2 ``` Running `bundle show` displays information about all dependencies used by a project, and their pinned versions. It doesn't label which dependencies are direct or transitive, and doesn't tell us edges between dependencies Example output: ``` Gems included by the bundle: CFPropertyList (3.0.1) addressable (2.7.0) ast (2.4.0) atomos (0.1.3) babosa (1.0.2) bindingofcaller (0.8.0) builder (3.2.3) bundler (1.17.2) byebug (11.0.1) claide (1.0.3) claide-plugins (0.9.2) coderay (1.1.2) ```
Project: OAuth2 Proxy (Provisioning / Key Management)
File: welcome.md

id: welcome title: Welcome hidetableof_contents: true slug: / A reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. :::note This repository was forked from on 27/11/2018. Versions v3.0.0 and up are from this fork and will have diverged from any changes in the original fork. A list of changes can be seen in the . :::
Project: FOSSA (Provisioning / Security & Compliance)
File: packagejson.md

package.json is a common build manifest used by both yarn and npmcli. `npm`: Find all files named `package.json`, not descending into directories named `node_modules` `package.json` is a user modified file that specifies which dependencies are mandatory in order to run your project. This file lists dependencies with their version specifier. These dependencies are user specified and map nearly 1:1 with direct dependencies, however users may also specify their desired version for transitive dependencies which would invalidate the assumption that all dependencies specified here are direct. There is also a different block for development dependencies which allows us to accurately determine part of the tags available for node. As of v2.19.x, we also combine `package.json` files that are members of the same workspace. The files are treated as though all dependencies were found from the same file, though we report the origins of the deps as a set of all files.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: bahwancybertek.md

title: "Bahwan Cybertek" icon: /images/logos/powered-by/bahwancybertek.png hasLink: "https://bahwancybertek.com/home/" <!-- Licensed 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. -->
Project: ClickHouse (App Definition and Development / Database)
File: hdfs.md

slug: /en/sql-reference/table-functions/hdfs sidebar_position: 80 sidebar_label: hdfs Creates a table from files in HDFS. This table function is similar to and ones. ``` sql hdfs(URI, format, structure) ``` Input parameters `URI` The relative URI to the file in HDFS. Path to file support following globs in readonly mode: `*`, `?`, `{abc,def}` and `{N..M}` where `N`, `M` numbers, \``'abc', 'def'` strings. `format` The of the file. `structure` Structure of the table. Format `'column1name column1type, column2name column2type, ...'`. Returned value A table with the specified structure for reading or writing data in the specified file. Example Table from `hdfs://hdfs1:9000/test` and selection of the first two rows from it: ``` sql SELECT * FROM hdfs('hdfs://hdfs1:9000/test', 'TSV', 'column1 UInt32, column2 UInt32, column3 UInt32') LIMIT 2 ``` ``` text column1column2column3 1 2 3 3 2 1 ``` Paths may use globbing. Files must match the whole path pattern, not only the suffix or prefix. `*` Represents arbitrarily many characters except `/` but including the empty string. `?` Represents an arbitrary single character. `{somestring,anotherstring,yetanotherone}` Substitutes any of strings `'somestring', 'anotherstring', 'yetanotherone'`. The strings can contain the `/` symbol. `{N..M}` Represents any number `>= N` and `<= M`. Constructions with `{}` are similar to the and table functions. Example Suppose that we have several files with following URIs on HDFS: hdfs://hdfs1:9000/somedir/somefile_1 hdfs://hdfs1:9000/somedir/somefile_2 hdfs://hdfs1:9000/somedir/somefile_3 hdfs://hdfs1:9000/anotherdir/somefile_1 hdfs://hdfs1:9000/anotherdir/somefile_2 hdfs://hdfs1:9000/anotherdir/somefile_3 Query the amount of rows in these files: <!-- --> ``` sql SELECT count(*) FROM hdfs('hdfs://hdfs1:9000/{some,another}dir/somefile_{1..3}', 'TSV', 'name String, value UInt32') ``` Query the amount of rows in all files of these two directories: <!-- --> ``` sql SELECT count(*) FROM hdfs('hdfs://hdfs1:9000/{some,another}_dir/*', 'TSV', 'name String, value UInt32') ``` :::note If your listing of files contains number ranges with leading zeros, use the construction with braces for each digit separately or use `?`. ::: Example Query the data from files named `file000`, `file001`, , `file999`: ``` sql SELECT count(*) FROM hdfs('hdfs://hdfs1:9000/big_dir/file{0..9}{0..9}{0..9}', 'CSV', 'name String, value UInt32') ``` `_path` Path to the file. Type: `LowCardinalty(String)`. `_file` Name of the file. Type: `LowCardinalty(String)`. `_size` Size of the file in bytes. Type: `Nullable(UInt64)`. If the size is unknown, the value is `NULL`. - allows to truncate file before insert into it. Disabled by default. - allows to create a new file on each insert if format has suffix. Disabled by default. - allows to skip empty files while reading. Disabled by default. - allows to ignore permission denied errors for multi-directory globs. See Also
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: no-undeclared-imports.md

Forbid imports of external packages that have not been declared in the appropriate dependencies field in `package.json`. Add the rules as follows, it has no options: ```js "@backstage/no-undeclared-imports": ["error"] ``` The following patterns are considered files used during development, and only need dependencies to be declared in devDependencies: ```python !src/ # Any files outside of src are considered dev files src//.test. src//.stories. src//__testUtils__/ src//__mocks__/ src/setupTests.* ``` Given the following `package.json`: ```json { "name": "@backstage/plugin-foo", "backstage": { "role": "frontend-plugin" }, "dependencies": { "react": "^17.0.0" }, "devDependencies": { "@backstage/core-plugin-api": "^1.0.0" }, "peerDependencies": { "@backstage/config": "*" } } ``` Inside `src/my-plugin.ts`: ```ts // Should be declared as a dependency const _ = require('lodash'); import _ from 'lodash'; // React should be a peer dependency in frontend plugins import react from 'react'; // Should be declared as a dependency, not a dev dependency import { useApi } from '@backstage/core-plugin-api'; ``` Inside `src/my-plugin.test.ts` (a test file): ```ts // Should be declared as a dev dependency const _ = require('lodash'); import _ from 'lodash'; ``` Inside `src/my-plugin.ts`: ```ts // Declared in peerDependencies, so it is allowed import { ConfigReader } from '@backstage/config'; ``` Inside `src/my-plugin.test.ts` (a test file): ```ts // Declared as a dev dependency inside a test file import { useApi } from '@backstage/core-plugin-api'; ```