cwielenb/CNCF-Dataset huggingface dataset:
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: DISTRO_PACKAGE.md

This document is currently written with Fedora as a reference, intended for use by packagers of other distros as well as package users. Podman v4 is available as an official Fedora package on Fedora 36 and rawhide. This version of Podman brings with it a new container stack called Netavark which serves as a replacement for CNI plugins (containernetworking-plugins on Fedora), as well as Aardvark-dns, the authoritative DNS server for container records. Both Netavark and Aardvark-dns are available as official Fedora packages on Fedora 35 and newer versions and form the default network stack for new installations of Podman 4.0. On Fedora 36 and newer, fresh installations of Podman v4 will automatically install Aardvark-dns along with Netavark. To install Podman v4: ```console $ sudo dnf install podman ``` To update Podman from an older version to v4: ```console $ sudo dnf update podman ``` NOTE: Fedora 35 users will not be able to install Podman v4 using the default yum repositories and are recommended to use the COPR repo below: ```console $ sudo dnf copr enable rhcontainerbot/podman4 $ sudo dnf install podman ``` After installation, if you would like to migrate all your containers to use Netavark, you will need to set `network_backend = "netavark"` under the `[network]` section in your containers.conf, typically located at: `/usr/share/containers/containers.conf` If you would like to test the latest unreleased upstream code, try the podman-next COPR ```console $ sudo dnf copr enable rhcontainerbot/podman-next $ sudo dnf install podman ``` CAUTION: The podman-next COPR provides the latest unreleased sources of Podman, Netavark and Aardvark-dns as rpms which would override the versions provided by the official packages. The Fedora packaging sources for Podman are available at the [Podman dist-git](https://src.fedoraproject.org/rpms/podman). The main `podman` package no longer explicitly depends on containernetworking-plugins. The network stack dependencies are now handled in the package which allows for a single point of dependency maintenance for Podman and Buildah. containers-common ``` Requires: container-network-stack Recommends: netavark ``` netavark ``` Provides: container-network-stack = 2 ``` containernetworking-plugins ``` Provides: container-network-stack = 1 ``` This configuration ensures: New installations of Podman will always install netavark by default. The containernetworking-plugins package will not conflict with netavark and users can install them together. If you need to list the bundled dependencies in your packaging sources, you can process the `go.mod` file in the upstream source. For example, Fedora's packaging source uses: ``` $ awk '{print "Provides: bundled(golang("$1")) = "$2}' go.mod | sort | uniq | sed -e 's/-/_/g' -e '/bundled(golang())/d' -e '/bundled(golang(go\|module\|replace\|require))/d' ```
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: 0008-accept-unrecognised-fields.md

Status: accepted Date: 2021-04-08 Technical Story: https://github.com/theupdateframework/python-tuf/issues/1266 The current reference implementation will ignore unrecognized fields in a metadata file when loading it. This leads to the side effect that if you read a metadata file with unrecognized fields and immediately write it back to the disk, this file will be modified. Furthermore, some TAPs like: are relying on that unrecognized fields will be accepted to introduce new fields to the specification without making the metadata invalid for older clients who don't recognize the field. The TUF specification implies support for unrecognized attribute-value fields, see If we perform the following operations on a metadata file with no intermediate operations: read the metadata file write the metadata file back to the disk then, the checksum (the content) of the file must not be changed. Flexibility to add new fields in the spec without adding breaking changes. Don't store unrecognized fields when it is not allowed by the specification. Ignore and drop unrecognized fields. Ignore, but store unrecognized fields as an additional attribute. Ignore, but store unrecognized fields as an additional attribute except for a couple of places where it's not allowed by the specification. Chosen option: "Ignore, but store unrecognized fields as an additional attribute except for a couple of places where it's not allowed by the specification." The motivation for this decision is that the TUF specification already implies that we should accept unrecognized fields for backward compatibility and easier future extensibility. Additionally, it seems unacceptable to change a metadata file content just by reading and writing it back. There are exceptions however for places in the metadata format when it is not allowed by specification: keys, roles, meta, hashes, and targets are actual dictionaries (vs JSON objects that most structures in the format are) where `unrecognized field` is not a meaningful concept.
Project: secureCodeBox (Provisioning / Security & Compliance)
File: scheduled-scan.md

title: "ScheduledScan" sidebar_position: 3 The ScheduledScan Custom Resource Definition (CRD) lets you define a which gets repeated in a specific time interval. E.g. every 24 hours or every 7 days. The `interval` specifies the interval between two scans. Either or need to be set, they are mutually exclusive. Specified as a . :::caution The biggest duration golang time strings support is hours. Longer durations e.g. days / weeks need to specified as multiples of hours. We plan to improve this in the future, by providing a custom format which also supports days and weeks. ::: Schedule let's you define a to control precisely when the scan is executed. Either or need to be set, they are mutually exclusive. The `scanSpec` contains the specification of the scan which should be repeated. See the `spec` field of the for all supported attributes. The `successfulJobsHistoryLimit` controls how many completed scans are supposed to be kept until the oldest one will be deleted. Defaults to 3 if not set. When set to `0`, scans will be deleted directly after their completion. The `failedJobsHistoryLimit` controls how many failed scans are supposed to be kept until the oldest one will be deleted. Defaults to 1 if not set. When set to `0`, scans will be deleted directly after failure. ```yaml apiVersion: "execution.securecodebox.io/v1" kind: ScheduledScan metadata: name: "nmap-scanme.nmap.org-daily" spec: interval: 24h scanSpec: scanType: "nmap" parameters: "-sV" scanme.nmap.org successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 5 ``` ```yaml apiVersion: "execution.securecodebox.io/v1" kind: ScheduledScan metadata: name: "nmap-scanme.nmap.org-daily-noon" spec: schedule: "0 12 *" scanSpec: scanType: "nmap" parameters: "-sV" scanme.nmap.org successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 5 ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.17.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | failed tasks may stay forever in TaskTracker.runningJobs | Critical | . | Zheng Shao | Zheng Shao | | | Uncaught exception in DataXceiveServer | Blocker | . | Koji Noguchi | Konstantin Shvachko | | | Infinite loop in dfs close | Blocker | . | Koji Noguchi | Lohit Vijayarenu | | | HDFS should not remove blocks while in safemode. | Blocker | . | Konstantin Shvachko | Konstantin Shvachko | | | Unbalanced replication target | Blocker | . | Koji Noguchi | Hairong Kuang | | | Excessive exceptions in HDFS namenode log file | Blocker | . | Jim Huang | Lohit Vijayarenu | | | DFS operations fail because of Stream closed error | Blocker | . | Amar Kamat | Lohit Vijayarenu | | | Frequent DiskOutOfSpaceException on almost-full datanodes | Blocker | . | Koji Noguchi | Raghu Angadi | | | Avoid spurious "DataXceiver: java.io.IOException: Connection reset by peer" errors in DataNode log | Blocker | . | Raghu Angadi | Raghu Angadi | | | RPC queue overload of JobTracker | Major | . | Christian Kunz | Amareshwari Sriramadasu | | | 1000 concurrent read on a single file failing the task/client | Blocker | . | Koji Noguchi | Johan Oskarsson | | | Bug in MapTask.MapOutputBuffer.collect leads to an unnecessary and harmful 'reset' | Blocker | . | Arun C Murthy | Chris Douglas | | | namenode startup error, hadoop-user-namenode.pid permission denied. | Critical | . | Focus | |
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: K8S.md

Provides a pre-deployed Kubernetes with version 1.x purely in docker containers with qemu. The provided VMs are completely ephemeral and are recreated on every cluster restart. There's a docker registry available which is exposed at `localhost:5000`. The env variable `KUBEVIRT_PROVIDER` tells kubevirtci what cluster version to spin up. ```bash export KUBEVIRT_PROVIDER=k8s-1.22 # choose kubevirtci provider version by subdirectory name ``` ```bash export KUBEVIRTNUMNODES=2 # control-plane + one node make cluster-up ``` The cluster can be accessed as usual: ```bash $ cluster/kubectl.sh get nodes NAME STATUS ROLES AGE VERSION node01 NotReady control-plane 31s v1.22.1 node02 NotReady <none> 5s v1.22.1 ``` Note: for further configuration environment variables please see ```bash export KUBEVIRTWITHCNAO=true make cluster-up ``` To get more info about CNAO you can check the github project documentation here https://github.com/kubevirt/cluster-network-addons-operator ```bash export KUBEVIRT_CGROUPV2=true make cluster-up ``` ```bash export KUBEVIRT_SLIM=true make cluster-up ``` In order to be able to reach from the cluster to the host's IPv6 network, IPv6 has to be enabled on your Docker. Add following to your `/etc/docker/daemon.json` and restart docker service: ```json { "ipv6": true, "fixed-cidr-v6": "2001:db8:1::/64" } ``` ```bash systemctl restart docker ``` With an IPv6-connected host, you may want the pods to be able to reach the rest of the IPv6 world, too. In order to allow that, enable IPv6 NAT on your host: ```bash ip6tables -t nat -A POSTROUTING -s 2001:db8:1::/64 -j MASQUERADE ``` ```bash make cluster-down ``` This destroys the whole cluster. Recreating the cluster is fast, since k8s is already pre-deployed. The only state which is kept is the state of the local docker registry. The docker registry survives a `make cluster-down`. It's state is stored in a docker volume called `kubevirt_registry`. If the volume gets too big or the volume contains corrupt data, it can be deleted with ```bash docker volume rm kubevirt_registry ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_insert.md

title: Kubectl-Dba Data Insert menu: docs_{{ .version }}: identifier: kubectl-dba-data-insert name: Kubectl-Dba Data Insert parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Insert random data in a database Insert random data in a database. ``` kubectl-dba data insert ``` ``` kubectl dba data insert mysql mysql-demo -n demo --rows=100 kubectl dba data insert rd sample-redis -n demo --rows=100 Valid resource types include: elasticsearch mongodb mariadb mysql postgres redis ``` ``` -h, --help help for insert ``` ``` --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 ``` - Insert, Drop or Verify data in a database - Insert data to a elasticsearch database - Insert data to mariadb - Insert data to mongodb - Insert data to mysql - Insert data to a postgres object's pod - Insert data to a redis database
Project: ClickHouse (App Definition and Development / Database)
File: urlCluster.md

slug: /en/sql-reference/table-functions/urlCluster sidebar_position: 201 sidebar_label: urlCluster Allows processing files from URL in parallel from many nodes in a specified cluster. On initiator it creates a connection to all nodes in the cluster, discloses asterisk in URL file path, and dispatches each file dynamically. On the worker node it asks the initiator about the next task to process and processes it. This is repeated until all tasks are finished. Syntax ``` sql urlCluster(cluster_name, URL, format, structure) ``` Arguments `cluster_name` Name of a cluster that is used to build a set of addresses and connection parameters to remote and local servers. `URL` HTTP or HTTPS server address, which can accept `GET` requests. Type: . `format` of the data. Type: . `structure` Table structure in `'UserID UInt64, Name String'` format. Determines column names and types. Type: . Returned value A table with the specified format and structure and with data from the defined `URL`. Examples Getting the first 3 lines of a table that contains columns of `String` and type from HTTP-server which answers in format. Create a basic HTTP server using the standard Python 3 tools and start it: ```python from http.server import BaseHTTPRequestHandler, HTTPServer class CSVHTTPServer(BaseHTTPRequestHandler): def do_GET(self): self.send_response(200) self.send_header('Content-type', 'text/csv') self.end_headers() self.wfile.write(bytes('Hello,1\nWorld,2\n', "utf-8")) if name == "main": server_address = ('127.0.0.1', 12345) HTTPServer(serveraddress, CSVHTTPServer).serveforever() ``` ``` sql SELECT * FROM urlCluster('cluster_simple','http://127.0.0.1:12345', CSV, 'column1 String, column2 UInt32') ``` Patterns in curly brackets `{ }` are used to generate a set of shards or to specify failover addresses. Supported pattern types and examples see in the description of the function. Character `|` inside patterns is used to specify failover addresses. They are iterated in the same order as listed in the pattern. The number of generated addresses is limited by setting. See Also
Project: CloudTTY (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: examples.md

The following text is to be inserted after the Alternative Schema Object section. Minimalist usage of alternative schema: schema: x-oas-draft-alternativeSchema: type: jsonSchema location: ./real-jsonschema.json Combination of OAS schema and alternative: schema: type: object nullable: true x-oas-draft-alternativeSchema: type: jsonSchema location: ./real-jsonschema.json Multiple different versions of alternative schema: schema: anyOf: x-oas-draft-alternativeSchema: type: jsonSchema location: ./real-jsonschema-08.json x-oas-draft-alternativeSchema: type: jsonSchema location: ./real-jsonschema-07.json Combined alternative schemas: schema: allOf: x-oas-draft-alternativeSchema: type: xmlSchema location: ./xmlSchema.xsd x-oas-draft-alternativeSchema: type: schematron location: ./schema.sch Mixed OAS schema and alternative schema: schema: type: array items: x-oas-draft-alternativeSchema: type: jsonSchema location: ./real-jsonschema.json
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.65.md

layout: release date: 2023-03-15 tag: v0.6.65 Changed integrations filetype for meshery.io repo from json to js @asubedy (#7350) Bump webpack from 5.70.0 to 5.76.1 in /install/docker-extension/ui @dependabot (#7354) All Meshmodel-categories Icons Added @ritiksaxena124 (#7345) Fixed pattern bug @asubedy (#7360) Bump webpack from 5.75.0 to 5.76.0 in /ui @dependabot (#7353) Bump webpack from 5.75.0 to 5.76.1 in /provider-ui @dependabot (#7352) Bump webpack from 5.75.0 to 5.76.0 in /ui @dependabot (#7353) Bump webpack from 5.75.0 to 5.76.1 in /provider-ui @dependabot (#7352) [Docs] Improve dark mode visibility of code snippet and click feedback to copy button. @chinu-anand (#7166) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @adithyaakrishna, @asubedy, @chinu-anand, @dependabot, @dependabot[bot], @leecalcote and @ritiksaxena124
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.18.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Update log4j from 1.2.13 to 1.2.15 | Blocker | . | Don Kim | Owen O'Malley | | | [HOD] Support an accounting plugin script for HOD | Blocker | contrib/hod | Hemanth Yamijala | Hemanth Yamijala | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Reduce often attempts in memory merge with no work | Minor | . | Chris Douglas | Chris Douglas | | | SequenceFile's Reader.decompressorPool or Writer.decompressorPool gets into an inconsistent state when calling close() more than once | Major | io | Peter Voss | Arun C Murthy | | | renameTo(src, dst) does not restore src name in case of quota failure. | Blocker | . | Raghu Angadi | Raghu Angadi | | | HadoopQA contrib -1 comments due to inconsistency in eclipse plugin declared jars | Blocker | . | Nigel Daley | Nigel Daley | | | Remove the hardcoded ipc.client.connection.maxidletime setting from the TaskTracker.Child.main() | Blocker | . | Devaraj Das | Devaraj Das | | | WritableComparator's constructor should be protected instead of private | Major | io | Owen O'Malley | Chris Douglas | | | [HOD] Make HOD to roll log files on the client | Blocker | contrib/hod | Hemanth Yamijala | Vinod Kumar Vavilapalli | | | [HOD] Uncaught exceptions can potentially hang hod-client. | Major | contrib/hod | Vinod Kumar Vavilapalli | Vinod Kumar Vavilapalli |
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_foreign_data_wrapper.md

title: CREATE FOREIGN DATA WRAPPER statement [YSQL] headerTitle: CREATE FOREIGN DATA WRAPPER linkTitle: CREATE FOREIGN DATA WRAPPER description: Use the CREATE FOREIGN DATA WRAPPER statement to create a foreign-data wrapper. menu: v2.18: identifier: ddlcreateforeigndatawrapper parent: statements type: docs Use the `CREATE FOREIGN DATA WRAPPER` statement to create a foreign data wrapper. Only superusers or users with the yb_fdw role can create foreign data wrappers. {{%ebnf%}} createforeigndata_wrapper {{%/ebnf%}} Create a FDW named fdw_name. The handler_function will be called to retrieve the execution functions for foreign tables. These functions are required by the planner and executor. The handler function takes no arguments and its return type should be `fdw_handler`. If no handler function is provided, foreign tables that use the wrapper can only be declared (and not accessed). The validator_function is used to validate the options given to the foreign-data wrapper, and the foreign servers, user mappings and foreign tables that use the foreign-data wrapper. The validator function takes two arguments: a text array (type text[]) that contains the options to be validated, and an OID of the system catalog that the object associated with the options is stored in. If no validator function is provided (or `NO VALIDATOR` is specified), the options will not be checked at the time of creation. The `OPTIONS` clause specifies options for the foreign-data wrapper. The permitted option names and values are specific to each foreign data wrapper. The options are validated using the FDWs validator function. Basic example. ```plpgsql yugabyte=# CREATE FOREIGN DATA WRAPPER my_wrapper HANDLER myhandler OPTIONS (dummy 'true'); ```
Project: Meshery (Provisioning / Automation & Configuration)
File: consul-past-results.md

layout: past-results-layout title: Meshery-Consul Past Results permalink: installation/compatibility-matrix/meshery-consul-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude type: "project" service-mesh: "meshery-consul" subheading: "Meshery-Consul"
Project: StarRocks (App Definition and Development / Database)
File: last_day.md

displayed_sidebar: "English" Returns the last day of an input DATE or DATETIME expression based on the specified date part. For example, `last_day('2023-05-10', 'month')` returns the last day of the month in which '2023-05-10' falls. If the date part is not specified, this function returns the last day of the month for a given date. This function is supported from v3.1. ```SQL DATE lastday(DATETIME|DATE dateexpr[, VARCHAR unit]) ``` `date_expr`: a DATE or DATETIME expression, required. `unit`: the date part, optional. Valid values include `month`, `quarter`, and `year`, default to `month`. If `unit` is invalid, an error is returned. Returns a DATE value. ```Plain MySQL > select last_day('2023-05-10', 'month'); +-+ | last_day('2023-05-10', 'month') | +-+ | 2023-05-31 | +-+ MySQL > select last_day('2023-05-10'); ++ | last_day('2023-05-10') | ++ | 2023-05-31 | ++ MySQL > select last_day('2023-05-10', 'quarter'); +--+ | last_day('2023-05-10', 'quarter') | +--+ | 2023-06-30 | +--+ MySQL > select last_day('2023-05-10', 'year'); ++ | last_day('2023-05-10', 'year') | ++ | 2023-12-31 | ++ ``` LAST_DAY, LAST