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

displayed_sidebar: "English" Views the last RESTORE task in a specified database. NOTE Only the information of the last RESTORE task is saved in StarRocks. ```SQL SHOW RESTORE [FROM <db_name>] ``` | Parameter | Description | | - | | | db_name | Name of the database that the RESTORE task belongs to. | | Return | Description | | -- | | | JobId | Unique job ID. | | Label | Name of the data snapshot. | | Timestamp | Backup timestamp. | | DbName | Name of the database that the RESTORE task belongs to. | | State | Current state of the RESTORE task:<ul><li>PENDING: Initial state after submitting a job.</li><li>SNAPSHOTING: Executing the local snapshot.</li><li>DOWNLOAD: Submitting snapshot download task.</li><li>DOWNLOADING: Downloading the snapshot.</li><li>COMMIT: To commit the downloaded snapshot.</li><li>COMMITTING: Committing the downloaded snapshot.</li><li>FINISHED: RESTORE task finished.</li><li>CANCELLED: RESTORE task failed or cancelled.</li></ul> | | AllowLoad | If loading data is allowed during the RESTORE task. | | ReplicationNum | Number of replicas to be restored. | | RestoreObjs | The restored objects (tables and partitions). | | CreateTime | Task submission time. | | MetaPreparedTime | Local metadata completion time. | | SnapshotFinishedTime | Snapshot completion time. | | DownloadFinishedTime | Snapshot download completion time. | | FinishedTime | Task completion Time. | | UnfinishedTasks | Unfinished subtask IDs in the SNAPSHOTTING, DOWNLOADING, and COMMITTING phases. | | Progress | The progress of snapshot downloading tasks. | | TaskErrMsg | Error messages. | | Status | Status information. | | Timeout | Task timeout. Unit: second. | Example 1: Views the last RESTORE task in the database `example_db`. ```SQL SHOW RESTORE FROM example_db; ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.17.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | JavaSerialization can throw java.io.StreamCorruptedException | Major | . | Tom White | Tom White | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Namenode stuck in safemode | Major | . | Christian Kunz | Hairong Kuang | | | MapFile.Reader getClosest() function returns incorrect results when before is true | Major | io | Todd Lipcon | stack | | | QuickSort may get into unbounded recursion | Blocker | . | Runping Qi | Chris Douglas | | | release tar.gz contains duplicate files | Major | build | Adam Heath | Adam Heath | | | MapOutputBuffer allocates 4x as much space to record capacity as intended | Major | . | Chris Douglas | Chris Douglas | | | ValuesIterator.next() doesn't return a new object, thus failing many equals() tests. | Major | . | Spyros Blanas | Owen O'Malley | | | Reduce tasks failing with OOM | Blocker | . | Arun C Murthy | Chris Douglas | | | contrib/data\_join doesn't work | Blocker | . | Spyros Blanas | Spyros Blanas | | | fsck on namenode without datanodes takes too much time | Minor | . | Koji Noguchi | Lohit Vijayarenu |
Project: StarRocks (App Definition and Development / Database)
File: SHOW_VARIABLES.md

displayed_sidebar: "English" Shows the system variables of StarRocks. For details about system variables, see . :::tip This operation does not require privileges. ::: ```SQL SHOW [ GLOBAL | SESSION ] VARIABLES [ LIKE <pattern> | WHERE <expr> ] ``` | Parameter | Description | | - | | | Modifier:<ul><li>GLOBAL</li><li>SESSION</li></ul> | <ul><li>With a `GLOBAL` modifier, the statement displays global system variable values. These are the values used to initialize the corresponding session variables for new connections to StarRocks. If a variable has no global value, no value is displayed.</li><li>With a `SESSION` modifier, the statement displays the system variable values that are in effect for the current connection. If a variable has no session value, the global value is displayed. `LOCAL` is a synonym for `SESSION`.</li><li>If no modifier is present, the default is `SESSION`.</li></ul> | | pattern | The pattern used to match the variable by the variable name with the LIKE clause. You can use the % wildcard in this parameter. | | expr | The expression used to match the variable by the variable name `variable_name` or the variable value `value` with the WHERE clause. | | Return | Description | | - | -- | | Variable_name | The name of the variable. | | Value | The value of the variable. | Example 1: Show a variable by exactly matching the variable name with the LIKE clause. ```Plain mysql> SHOW VARIABLES LIKE 'wait_timeout'; ++-+ | Variable_name | Value | ++-+ | wait_timeout | 28800 | ++-+ 1 row in set (0.01 sec) ``` Example 2: Show variables by approximately matching the variable name with the LIKE clause and the wildcard (%). ```Plain mysql> SHOW VARIABLES LIKE '%imeou%'; ++-+ | Variable_name | Value | ++-+ | interactive_timeout | 3600 | | netreadtimeout | 60 | | netwritetimeout | 60 | | newplanneroptimize_timeout | 3000 | | querydeliverytimeout | 300 | | queryqueuependingtimeoutsecond | 300 | | query_timeout | 300 | | txvisiblewait_timeout | 10 | | wait_timeout | 28800 | ++-+ 9 rows in set (0.00 sec) ``` Example 3: Show a variable by exactly matching the variable name with the WHERE clause. ```Plain mysql> show variables where variablename = 'waittimeout'; ++-+ | Variable_name | Value | ++-+ | wait_timeout | 28800 | ++-+ 1 row in set (0.17 sec) ``` Example 4: Show a variable by exactly matching the value of the variable with the WHERE clause. ```Plain mysql> show variables where value = '28800'; ++-+ | Variable_name | Value | ++-+ | wait_timeout | 28800 | ++-+ 1 row in set (0.70 sec) ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: minor-patch-release.md

name: Minor Patch Release about: Minor Patch Release title: 'Minor Patch Release Checklist' labels: kind/bug assignees: '' [ ] Dapr maintainer(s) communicate out the discovery of issues that require a patch release and the reason why to the Discord Maintainers and Release channels. Patch releases are made for one of categories below: [ ] Security vulnerability <> [ ] Regression that does not have a work around: <> [ ] Broken mainline scenario that has a missing test case: <> [ ] Create Tag [ ] <> [ ] Performance tests passing [ ] End to End tests passing on Linux and Windows [ ] New test case written to catch future occurrences [ ] Notify users to try RC (Announce on Discord Announcements channel) [ ] <> [ ] Update the longhaul tests to use RC [ ] <> [ ] Write release notes [ ] <> [ ] Review release notes [@dapr/maintainers-dapr] [ ] Create Tag [@dapr/maintainers-dapr] [ ] Backport fixes into master branch [@dapr/maintainers-dapr] [ ] Update the documentation: Latest version & versions in supported releases [ ] Push new tag in installer-bundle repo [ ] Announce the patch release on Discord Announcements channel
Project: StarRocks (App Definition and Development / Database)
File: day_of_week_iso.md

displayed_sidebar: "English" Returns the ISO standard day of the week for the specified date as an integer within the range of `1` to `7`. In this standard, `1` represents Monday, and `7` represents Sunday. ```Haskell INT DAYOFWEEK_ISO(DATETIME date) ``` `date`: the date you want to convert. It must be of the DATE or DATETIME type. The following example returns the ISO standard day of the week for the date `2023-01-01`: ```SQL MySQL > select dayofweek_iso('2023-01-01'); +--+ | dayofweek_iso('2023-01-01') | +--+ | 7 | +--+ ``` DAYOFWEEK_ISO
Project: KICS (Provisioning / Security & Compliance)
File: bf36b900-b5ef-4828-adb7-70eb543b7cfb.md

title: Kubelet Hostname Override Is Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bf36b900-b5ef-4828-adb7-70eb543b7cfb Query name: Kubelet Hostname Override Is Set Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Hostnames should not be overrided<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet"] args: ["--hostname-override=host"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet","--hostname-override=host"] args: [] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: foo/bar command: ["kubelet"] args: [] restartPolicy: OnFailure ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: auditd.md

+++ title = "auditd resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "auditd" identifier = "inspec/resources/os/auditd.md auditd resource" parent = "inspec/resources/os" +++ Use the `auditd` Chef InSpec audit resource to test the rules for logging that exist on the system. The audit.rules file is typically located under /etc/audit/ and contains the list of rules that define what is captured in log files. These rules are output using the `auditctl -l` command. This resource supports versions of `audit` >= 2.3. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.38.8 of InSpec. An `auditd` resource block declares one (or more) rules to be tested, and then what that rule should do: describe auditd do its('lines') { should include %r(-w /etc/ssh/sshd_config) } end or test that multiple individual rules are defined: describe auditd do its('lines') { should include %r(-a always,exit -F arch=.* -S initmodule,deletemodule -F key=modules) } its('lines') { should include %r(-a always,exit -F arch=.* -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -F key=.+) } end where each test must declare one (or more) rules to be tested. The following examples show how to use this Chef InSpec audit resource. For `audit` >= 2.3: describe auditd do its('lines') { should include %r(-a always,exit -F arch=. -S chown. -F auid>=1000 -F auid!=-1 -F key=perm_mod) } end describe auditd.status('backlog') do it { should cmp 0 } end describe auditd.syscall('open') do its('action.uniq') { should eq ['always'] } its('list.uniq') { should eq ['exit'] } end describe auditd.file('/etc/sudoers') do its('permissions') { should include ['x'] } end The where accessor can be used to filter on fields. For example: describe auditd.syscall('chown').where { arch == "b32" } do its('action') { should eq ['always'] } its('list') { should eq ['exit'] } its('exit') { should include ['-EACCES'] } its('exit') { should include ['-EPERM'] } end The key filter may be useful in evaluating rules with particular key values: describe auditd.where { key == "privileged" } do its('permissions') { should include ['x'] } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Druid (App Definition and Development / Database)
File: deep-storage-migration.md

id: deep-storage-migration title: "Deep storage migration" <!-- ~ 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. --> If you have been running an evaluation Druid cluster using local deep storage and wish to migrate to a more production-capable deep storage system such as S3 or HDFS, this document describes the necessary steps. Migration of deep storage involves the following steps at a high level: Copying segments from local deep storage to the new deep storage Exporting Druid's segments table from metadata Rewriting the load specs in the exported segment data to reflect the new deep storage location Reimporting the edited segments into metadata To ensure a clean migration, shut down the non-coordinator services to ensure that metadata state will not change as you do the migration. When migrating from Derby, the coordinator processes will still need to be up initially, as they host the Derby database. Before migrating, you will need to copy your old segments to the new deep storage. For information on what path structure to use in the new deep storage, please see . Druid provides an for exporting metadata from Derby into CSV files which can then be reimported. By setting , the `export-metadata` tool will export CSV files where the segment load specs have been rewritten to load from your new deep storage location. Run the `export-metadata` tool on your existing cluster, using the migration options appropriate for your new deep storage location, and save the CSV files it generates. After a successful export, you can shut down the coordinator. After generating the CSV exports with the modified segment data, you can reimport the contents of the Druid segments table from the generated CSVs. Please refer to for examples. Only the `druid_segments` table needs to be imported. After importing the segment table successfully, you can now restart your cluster.
Project: ClickHouse (App Definition and Development / Database)
File: v22.11.3.47-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Bring sha512 sums back to the building step. (). Backported in : Kill stress tests after 2.5h in case of hanging process. (). Backported in : In rare cases, we don't rebuild binaries, because another task with a similar prefix succeeded. E.g. `binarydarwin` didn't restart because `binarydarwin_aarch64`. (). Backported in : Retry the integration tests on compressing errors. (). Backported in : . (). Backported in : Fix incorrect UserTimeMicroseconds/SystemTimeMicroseconds accounting. (). Backported in : Fix sumMap() for Nullable(Decimal()). (). Backported in : fix s3Cluster function returns NOTFOUNDCOLUMNINBLOCK error. Closes . (). Backported in : - Fix using multipart upload for large S3 objects in AWS S3. (). Backported in : Fixed `ALTER ... RESET SETTING` with `ON CLUSTER`. It could be applied to one replica only. Fixes . (). Backported in : Fix undefined behavior in the `quantiles` function, which might lead to uninitialized memory. Found by fuzzer. This closes . (). Backported in : Prevent `ReadonlyReplica` metric from having negative values. (). Backported in : Fix possible crash in case function `IN` with constant arguments was used as a constant argument together with `LowCardinality`. Fixes . (). Yet another fix for AggregateFunctionMinMaxAny (). Use only PRs to our repository in pr_info on push (). Fix tags workflow (). Assign release PRs (). Fix another bug in AggregateFunctionMinMaxAny (). Bump libdivide (to gain some new optimizations) (). Add check for submodules sanity (). Implement a custom central checkout action (). Fix crash on delete from materialized view (). Do not check read result consistency when unwinding ().
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: 0004-extent-of-OOP-in-metadata-model.md

Status: accepted Date: 2020-11-30 Technical Story: https://github.com/theupdateframework/python-tuf/issues/1133 Custom classes for the TUF signed metadata wrapper (Metadata) and metadata payload containers (Root, Timestamp, Snapshot, Targets) were added recently. Complex attributes on these classes are still represented as dictionaries. Should we add classes for these attributes too? Transition to class-based role metadata containers in progress (see "class model"* links below) Harden in-memory representation of metadata model Replace `securesystemslib` schema validation (see "schema checker"* link below) Use custom classes for complex attributes Use dictionaries for complex attributes Chosen option: "Use custom classes for complex attributes", to provide a consistently object-oriented, well-defined, single source of truth about the TUF metadata model (not only its containers). In addition to convenience update methods, the model may be extended with self-validation behavior (see "validation guidelines" link below) to replace `securesystemslib` schema checks. Implementation overhead Less flexibility in usage and development (this is actually desired) Maybe less idiomatic than dictionaries
Project: kpt (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

We'd love to accept your patches and contributions to this project. There are just a few small guidelines you need to follow. Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. Head over to <https://cla.developers.google.com/> to see your current agreements on file or to sign a new one. You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again. All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult for more information on using pull requests. This project follows .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.39.md

layout: release date: 2024-03-26 tag: v0.7.39 Revert "Bump react-dom from 17.0.2 to 18.2.0 in /ui" @Yashsharma1911 (#10622) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911 and @leecalcote
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backup_delete.md

title: kbcli backup delete Delete a backup. ``` kbcli backup delete [flags] ``` ``` kbcli backup delete mybackup ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. --auto-approve Skip interactive approval before deleting --cluster string The cluster name. --force If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation. --grace-period int Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion). (default -1) -h, --help help for delete --now If true, resources are signaled for immediate shutdown (same as --grace-period=1). -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Backup command.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-components-search.md

layout: default title: mesheryctl-exp-components-search permalink: reference/mesheryctl/exp/components/search redirect_from: reference/mesheryctl/exp/components/search/ type: reference display-title: "false" language: en command: exp subcommand: components search registered components search components registered in Meshery Server <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp components search [flags] </div> </pre> Search for components using a query <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp components search [query-text] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for search </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: register-a-component.md

id: register-a-component title: Registering a Component description: Start populating your Backstage app with your data. Audience: Developers This guide will walk you through how to pull Backstage data from other locations manually. There are integrations that will automatically do this for you. You should have already . Register a new component, by going to `create` and choose `Register existing component` <!-- todo: Needs zoomable plugin --> For repository URL, use `https://github.com/backstage/backstage/blob/master/catalog-info.yaml`. This is used in our catalog. Hit `Analyze` and review the changes. If the changes from `Analyze` are correct, click `Apply`. You should receive a message that your entities have been added. If you go back to `Home`, you should be able to find `backstage`. You can click it and see the details for this new entity.