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

+++ title = "`badresultaccess_with<EC>`" description = "Exception type publicly inheriting from `badresultaccess` indicating an incorrect observation of value occurred, supplying the error value." +++ Exception type publicly inheriting from {{% api "badresultaccess" %}}, and thus also {{% api "std::logic_error" %}}, indicating an incorrect observation of value occurred. The error value at the time of the exception throw is moved or copied into this type, and is available using the `.error()` observer which comes in lvalue ref, const lvalue ref, rvalue ref, and const rvalue ref overloads. The primary purpose of this exception type is to enable standing in for {{% api "std::expected<T, E>" %}}'s `badexpectedaccess<E>` which is thrown on incorrect wide value observation. This is why it is only ever `EC` which is thrown with `badresultaccesswith<EC>` on value observation only, and only when there is an error available. See the {{% api "throwbadresultaccess<EC>" %}} policy for more information. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/bad_access.hpp>`
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_node_add.md

Add a node instance to YugabyteDB Anywhere universe Add a node instance to YugabyteDB Anywhere universe. Add a previously removed (or not in-use) node to the cluster and balance data onto it. ``` yba universe node add [flags] ``` ``` -h, --help help for add ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Required] The name of the universe for the corresponding node operations. --node-name string [Optional] The name of the universe node for the corresponding node operations. Required for add, reboot, release, remove, reprovision, start, stop. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere universe nodes
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.41.md

layout: release date: 2024-04-02 tag: v0.7.41 update parent child rels @aabidsofi19 (#10649) Bump postcss from 8.4.31 to 8.4.38 in /ui @dependabot (#10657) Bump @mui/icons-material from 5.14.19 to 5.15.14 in /provider-ui @dependabot (#10660) Bump eslint-config-next from 14.1.3 to 14.1.4 in /provider-ui @dependabot (#10661) Bump gorm.io/gorm from 1.25.5 to 1.25.9 @dependabot (#10655) Bump postcss from 8.4.31 to 8.4.38 in /ui @dependabot (#10657) Bump @mui/icons-material from 5.14.19 to 5.15.14 in /provider-ui @dependabot (#10660) Bump eslint-config-next from 14.1.3 to 14.1.4 in /provider-ui @dependabot (#10661) hide radio buttons on api-ref @vishalvivekm (#10664) fix docs search field @vishalvivekm (#10650) Thank you to our contributors for making this release possible: @MUzairS15, @aabidsofi19, @dependabot, @dependabot[bot], @leecalcote and @vishalvivekm
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: habitat_builder_overview.md

Chef Habitat Builder acts as the core of Chef's Application Delivery Enterprise hub. It provides a repository for all available Chef Habitat packages built by Chef and the supporting community, as well as search and an API for clients. You can store application plans on the Chef Habitat Builder SaaS where the Chef Habitat community can view and access them. You can also deploy the where you can store and maintain your apps in a secure environment.
Project: KICS (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a bug report to help us improve title: 'bug(<scope>): <title starting with lowercase letter>' labels: community, bug assignees: '' Found a bug? You're welcome to ](https://github.com/Checkmarx/kics/discussions) Please make sure to: Describe in details what the problem is Attach a log file with relevant data preferably in DEBUG level (`--log-level=DEBUG`) Attach the scanned sample files, anonymize the data if the original file cannot be provided When attaching files to the issue make sure they are properly formatted (Which results are expected from KICS?) (Formatted logs and samples helps us to better understand the issue) (Command line arguments and flags used) step 1 step 2 step 3 (N/A if not applicable) Version: Platform: Subsystem:
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: env.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: busybox spec: components: name: busybox type: webservice properties: image: busybox cmd: ["sleep", "86400"] traits: type: sidecar properties: name: sidecar-nginx image: nginx type: env properties: containers: containerName: busybox env: keyforbusyboxfirst: valuefirst keyforbusyboxsecond: valuesecond containerName: sidecar-nginx env: keyfornginxfirst: valuefirst keyfornginxsecond: valuesecond ``` ```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: busybox spec: components: name: busybox type: webservice properties: image: busybox cmd: ["sleep", "86400"] traits: type: sidecar properties: name: sidecar-nginx image: nginx type: env properties: containerName: busybox env: keyforbusyboxfirst: valuefirst keyforbusyboxsecond: valuesecond ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_connect_redis.md

title: Kubectl-Dba Connect Redis menu: docs_{{ .version }}: identifier: kubectl-dba-connect-redis name: Kubectl-Dba Connect Redis parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Connect to a redis object's pod Use this cmd to exec into a redis object's primary pod. ``` kubectl-dba connect redis [flags] ``` ``` -h, --help help for redis ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Connect to a database.
Project: Rundeck (Provisioning / Automation & Configuration)
File: SECURITY.md

The PagerDuty Security Team exists to provide help and advice related to Rundeck security issues and to provide coordination of the handling of security vulnerabilities. We strongly encourage the reporting of potential security vulnerabilities with our Vulnerability Report Form. Please note that the Vulnerability Report Form should only be used for reporting undisclosed security vulnerabilities in Rundeck projects. We cannot accept regular bug reports or other security related queries via the Form. All issues submitted via the Form that do not relate to an undisclosed security problem in a Rundeck project will be ignored. The general security mailing list address is: security@pagerduty.com. This is a private mailing list. Please submit one form for each vulnerability you are reporting. Information on the published vulnerabilities for an Rundeck project can usually be found on the project's github wiki. If you can't find the information you are looking for on the project's github wiki, you should ask your question on StackOverflow. The Vulnerability Report Form should not be used to ask questions about : how to configure Rundeck securely; if a published vulnerability applies to specific versions of Rundeck that you are using; if a published vulnerability applies to the configuration of the Rundeck instance you are using; obtaining further information on a published vulnerability; the availability of patches and/or new releases to address a published vulnerability. An overview of the vulnerability handling process is: The reporter reports the vulnerability privately to Rundeck. The appropriate project's security team works privately with the reporter to resolve the vulnerability. A new release of the Rundeck package concerned is made that includes the fix. The vulnerability is publicly announced.
Project: Fabric8 Kubernetes Client (App Definition and Development / Application Definition & Image Build)
File: KubernetesOperatorsInJavaWrittenUsingFabric8.md

You can easily rely on Fabric8 Kubernetes Client to implement your Kubernetes Operators. Here are few examples of already existing Kubernetes Operators which can give you some idea on how to get started with writing Kubernetes Operators in Java using Fabric8 Kubernetes Client: While sometimes simply using the client is enough to create an operator, using a specialized framework to do so might make the task easier. The builds on top of the Fabric8 Kubernetes Client to provide higher-level abstractions, common operator patterns and optimizations, letting developers focus on their operator's logic.
Project: StarRocks (App Definition and Development / Database)
File: CREATE_ROLE.md

displayed_sidebar: "English" import UserManagementPriv from '../../../assets/commonMarkdown/userManagementPriv.md' Creates a role. After a role is created, you can grant privileges to the role and then assign this role to a user or another role. This way, the privileges associated with this role are passed on to users or roles. <UserManagementPriv /> ```sql CREATE ROLE <role_name> ``` `role_name`: the name of the role. For the naming conventions, see . Note that the created role name cannot be the same as : `root`, `clusteradmin`, `dbadmin`, `user_admin`, and `public`. By default, a user can have a maximum of 64 roles. You can adjust this setting by using the FE dynamic parameter `privilegemaxtotalrolesperuser`. A role can have a maximum of 16 inheritance levels. You can adjust this setting by using the FE dynamic parameter `privilegemaxroledepth`. Create a role. ```sql CREATE ROLE role1; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.135.md

layout: release date: 2023-09-05 tag: v0.6.135 REST APIs for events. @MUzairS15 (#8655) Bump Meshkit version from 0.6.63 to 0.6.64 @Yashsharma1911 (#8658) [mesheryctl] handling default port in mesheryctl @suhail34 (#8579) Update package.json @MUzairS15 (#8651) Bump uuid from 8.3.2 to 9.0.0 in /ui @dependabot (#8532) [Events] Notification / Operation Center @MUzairS15 (#8644) [UI] Fix credential Icon color in settings @Yashsharma1911 (#8646) [CI] Playground: --remove-orphans in Meshery deployments @leecalcote (#8652) Bump uuid from 8.3.2 to 9.0.0 in /ui @dependabot (#8532) Bump gorm.io/gorm from 1.25.3 to 1.25.4 @dependabot (#8630) [CI] Meskit Error Utility Workflow Does not fails for duplicacy @suhail34 (#8649) Update MeshModel Issue Template @Boombag0607 (#8637) [Docs] Added how to use token for Meshery API in postman @Freedisch (#8122) Thank you to our contributors for making this release possible: @Boombag0607, @Freedisch, @MUzairS15, @Yashsharma1911, @dependabot, @leecalcote and @suhail34
Project: ArangoDB (App Definition and Development / Database)
File: explicit_inplace_value_constructor.md

+++ title = "`explicit basicresult(inplacetypet<valuetypeif_enabled>, Args ...)`" description = "Explicit inplace value constructor. Available if `predicate::enableinplacevalue_constructor<Args ...>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "inplace-constructors"] weight = 400 +++ Explicit inplace value constructor. Calls {{% api "void onresultinplaceconstruction(T *, inplacetypet<U>, Args &&...) noexcept" %}} with `this`, `inplacetype<valuetype>` and `Args ...`. Requires: `predicate::enableinplacevalue_constructor<Args ...>` is true. Complexity: Same as for the `value_type` constructor which accepts `Args ...`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the Args is left indeterminate.
Project: KubeArmor (Provisioning / Security & Compliance)
File: SECURITY.md

The Maintainers and contributors to KubeArmor take the security of our software seriously. The KubeArmor community has adopted the below security disclosures and response policy to promptly respond to critical issues. Please do not report security vulnerabilities through public GitHub issues. For information regarding the security of this project please join our . You think you discovered a potential security vulnerability in KubeArmor. You are unsure how a vulnerability affects KubeArmor. You think you discovered a vulnerability in the dependency of KubeArmor. For those projects, please leverage their reporting policy. You need assistance in configuring KubeArmor for security - please discuss this is in the . You need help applying security-related updates. Your issue is not security-related. Email the KubeArmor security group at support@accuknox.com Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) Full paths of the source file(s) related to the manifestation of the issue Location of the affected source code (tag/branch/commit or direct URL) Any special configuration required to reproduce the issue Step-by-step instructions to reproduce the issue Proof-of-concept or exploit code (if possible) Impact of the issue, including how an attacker might exploit the issue These information will help us triage your report more quickly. The project security team will send an initial response to the disclosure in 3-5 days. Once the vulnerability and fix are confirmed, the team will plan to release the fix in 7 to 28 days based on the severity and complexity. You may be contacted by a project maintainer to further discuss the reported item. Please bear with us as we seek to understand the breadth and scope of the reported problem, recreate it, and confirm if there is a vulnerability present. KubeArmor versions follow terminology and are expressed as x.y.z: where x is the major version y is the minor version and z is the patch version Security fixes may be backported to some recent minor releases, depending on severity and feasibility. Patch releases are cut from those branches periodically, plus additional urgent releases, when required.
Project: MongoDB (App Definition and Development / Database)
File: hang_analyzer.md

The hang analyzer is a tool to collect cores and other information from processes that are suspected to have hung. Any task which exceeds its timeout in Evergreen will automatically be hang-analyzed, with information being written compressed and uploaded to S3. The hang analyzer can also be invoked locally at any time. For all non-Jepsen tasks, the invocation is `buildscripts/resmoke.py hang-analyzer -o file -o stdout -m exact -p python`. You may need to substitute `python` with the name of the python binary you are using, which may be one of `python`, `python3`, or on Windows: `Python`, `Python3`. For jepsen tasks, the invocation is `buildscripts/resmoke.py hang-analyzer -o file -o stdout -p dbtest,java,mongo,mongod,mongos,python,_test`. The hang analyzer detects and runs against processes which are considered interesting. Tasks whose name contains "jepsen": any process whose name exactly matches one of `dbtest,java,mongo,mongod,mongos,python,_test`. In all other scenarios, including local use of the hang-analyzer, an interesting process is any of: process that starts with `python` or `live-record` one which has been spawned as a child process of resmoke. The resmoke subcommand `hang-analyzer` will send SIGUSR1/use SetEvent to signal resmoke to: Print stack traces for all python threads Collect core dumps and other information for any non-python child processes, see `Data Collection` below Re-signal any python child processes to do the same Data collection occurs in the following sequence: Pause all non-python processes Grab debug symbols on non-Sanitizer builds Signal python Processes Dump cores of as many processes as possible, until the disk quota is exceeded. The default quota is 90% of total volume space. Collect additional, non-core data. Ideally: Print C++ Stack traces Print MozJS Stack Traces Dump locks/mutexes info Dump Server Sessions Dump Recovery Units Dump Storage engine info Dump java processes (Jepsen tests) with jstack SIGABRT (Unix)/terminate (Windows) go processes Note that the list of non-core data collected is only accurate on Linux. Other platforms only perform a subset of these operations. Additionally, note that the hang analyzer is subject to Evergreen post task timeouts, and may not have enough time to collect all information before being terminated by the Evergreen agent. When running locally there is no timeout, and the hang analyzer may ironically hang indefinitely. Platform-specific concerns for data collection are handled by dumper objects in `buildscripts/resmokelib/hang_analyzer/dumper.py`. Linux: See `GDBDumper` MacOS: See `LLDBDumper` Windows: See `WindowsDumper` and `JstackWindowsDumper` Java (non-Windows): `JstackDumper`
Project: YDB (App Definition and Development / Database)
File: scheme-ls.md

The `scheme ls` command lets you get a list of objects in the database: ```bash {{ ydb-cli }} [connection options] scheme ls [path] [-lR1] ``` {% include %} Executing the command without parameters produces a compressed list of object names in the database's root directory. In the `path` parameter, you can specify the you want to list objects in. The following options are available for the command: `-l`: Full details about attributes of each object. `-R`: Recursive traversal of all subdirectories. `-1`: Output a single schema object per row (for example, to be later handled in a script). Examples {% include %} Getting objects from the root database directory in a compressed format ```bash {{ ydb-cli }} --profile quickstart scheme ls ``` Getting objects in all database directories in a compressed format ```bash {{ ydb-cli }} --profile quickstart scheme ls -R ``` Getting objects from the given database directory in a compressed format ```bash {{ ydb-cli }} --profile quickstart scheme ls dir1 {{ ydb-cli }} --profile quickstart scheme ls dir1/dir2 ``` Getting objects in all subdirectories in the given directory in a compressed format ```bash {{ ydb-cli }} --profile quickstart scheme ls dir1 -R {{ ydb-cli }} --profile quickstart scheme ls dir1/dir2 -R ``` Getting complete information on objects in the root database directory ```bash {{ ydb-cli }} --profile quickstart scheme ls -l ``` Getting complete information about objects in a given database directory ```bash {{ ydb-cli }} --profile quickstart scheme ls dir1 -l {{ ydb-cli }} --profile quickstart scheme ls dir2/dir3 -l ``` Getting complete information about objects in all database directories ```bash {{ ydb-cli }} --profile quickstart scheme ls -lR ``` Getting complete information on objects in all subdirectories of a given database directory ```bash {{ ydb-cli }} --profile quickstart scheme ls dir1 -lR {{ ydb-cli }} --profile quickstart scheme ls dir2/dir3 -lR ```
Project: ArangoDB (App Definition and Development / Database)
File: as_failure_rvalue.md

+++ title = "`auto as_failure() &&`" description = "Return the output from free function `failure()` containing a move of any errored state." categories = ["modifiers"] weight = 920 +++ Return the output from free function {{% api "auto failure(T &&, ...)" %}} containing a move from any errored state, thus leaving the result's error value in a moved-from state. Depending on the choice of `errortype`, this function may therefore be destructive. The error state is accessed using {{% api "errortype &&assume_error() && noexcept" %}}. Requires: Always available. Complexity: Whatever that of `error_type`'s move constructor is. Guarantees: None.
Project: Pulumi (Provisioning / Automation & Configuration)
File: build.md

This documentation is generated using [Sphinx] and authored in Markdown. Markdown support for [Sphinx] is provided by [MyST]. [MyST] provides a number of small syntax extensions to support declaring ReStructuredText directives; see for details. In order to build the devloper documentation: Install [PlantUML]. On macOS, this can be done via `brew install plantuml`. Install the requirements for [Sphinx]: ```bash $ pip install requirements.txt ``` Run `make` to build the HTML documentation: ```bash $ make ``` This will regenerate any out-of-date SVGs and build the a local version of the HTML documentation. The documentation can also be built from the repository root by running `make developer_docs`. Note that Sphinx doesn't do a great job of rebuilding output files if only the table-of-contents has changed. If you change the table of contents, you may need to clean the output directory in order to see the effects of your changes: ```bash $ make clean ``` Do use appropriate links wherever possible. Learn to use . If a particular link destination is referenced multiple times, prefer .
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: modulartarget.md

A `ModularTarget` indexes into tremor's module path. In tremor a `module` is a file on the file system. A `module` is also a unit of compilation. A `ModularTarget` is a `::` double-colon delimited set of identifiers. Leading `::` are not supported in a modular target.. Trailing `::` are not supported in a modular target.