cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeArmor (Provisioning / Security & Compliance)
File: icmp-con.md

```sh kubectl exec -it nginx-77b4fdf86c-x7sdm -- bash root@nginx-77b4fdf86c-x7sdm:/# hping3 www.google.com Unable to resolve 'www.google.com' root@nginx-77b4fdf86c-x7sdm:/# hping3 127.0.0.1 Warning: Unable to guess the output interface [getifname] socket(AFINET, SOCKDGRAM, 0): Permission denied [main] no such device root@nginx-77b4fdf86c-x7sdm:/# ping google.com PING google.com (216.58.200.206) 56(84) bytes of data. 64 bytes from nrt12s12-in-f206.1e100.net (216.58.200.206): icmp_seq=1 ttl=109 time=51.9 ms 64 bytes from nrt12s12-in-f206.1e100.net (216.58.200.206): icmp_seq=2 ttl=109 time=60.1 ms ^C google.com ping statistics 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 51.917/56.005/60.094/4.088 ms ``` ``` { "Action": "Block", "ClusterName": "0-trust", "ContainerID": "20a6333c6a46e0da32b3062f0ba76e9aed4fc5ef51f5ee8aec5b980963cedea3", "ContainerImage": "docker.io/library/nginx:latest@sha256:32da30332506740a2f7c34d5dc70467b7f14ec67d912703568daff790ab3f755", "ContainerName": "nginx", "Data": "syscall=SYS_SOCKET", "Enforcer": "AppArmor", "HostName": "aditya", "HostPID": 86904, "HostPPID": 86860, "Labels": "app=nginx", "NamespaceName": "default", "Operation": "Network", "Owner": { "Name": "nginx", "Namespace": "default", "Ref": "Deployment" }, "PID": 1064, "PPID": 1058, "ParentProcessName": "/usr/bin/bash", "PodName": "nginx-77b4fdf86c-x7sdm", "PolicyName": "DefaultPosture", "ProcessName": "/usr/sbin/hping3", "Resource": "domain=AFINET type=SOCKDGRAM|SOCKNONBLOCK|SOCKCLOEXEC protocol=0", "Result": "Permission denied", "Source": "/usr/sbin/hping3 www.google.com", "Timestamp": 1696593032, "Type": "MatchedPolicy", "UpdatedTime": "2023-10-06T11:50:32.098937Z", "cluster_id": "4291", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "tenant_id": "167", "workload": "1" } ```
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: README.md

Here you can find the JSON Schema for validating OpenAPI definitions of versions 3.1.X. As a reminder, the JSON Schema is not the source of truth for the Specification. In cases of conflicts between the Specification itself and the JSON Schema, the Specification wins. Also, some Specification constraints cannot be represented with the JSON Schema so it's highly recommended to employ other methods to ensure compliance. The iteration version of the JSON Schema can be found in the `$id` field. For example, the value of `$id: https://spec.openapis.org/oas/3.1/schema/2021-03-02` means this iteration was created on March 2nd, 2021. The `schema.yaml` schema doesn't validate the JSON Schemas in your OpenAPI document because 3.1 allows you to use any JSON Schema dialect you choose. We have also included `schema-base.yaml` that extends the main schema to validate that all schemas use the default OAS base vocabulary. To submit improvements to the schema, modify the schema.yaml file only. The TSC will then: Run tests on the updated schema Update the iteration version Convert the schema.yaml to schema.json Publish the new version The test suite is included as a git submodule of https://github.com/Mermade/openapi3-examples. ```bash npx mocha --recursive tests ``` You can also validate a document individually. ```bash scripts/validate.js path/to/document/to/validate.yaml ```
Project: ManageIQ (Provisioning / Automation & Configuration)
File: README.md

To collect logs manually, please use the collectarchivelogs.sh and/or collectcurrentlogs.sh scripts within this collect_logs directory depending on the information that is requested. Use the exclude_files file to add any files you don't want included in log collection. : ```ruby namespace <%= raketasknamespace %> do desc "Explaining what the task does" task :your_task do end end ``` Tasks places in the lib/tasks_private directory will be private to the plugin and not available in the ManageIQ app.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-resource-mgmt-add-file.md

layout: global title: ADD FILE displayTitle: ADD FILE license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. `ADD FILE` can be used to add a single file as well as a directory to the list of resources. The added resource can be listed using . ```sql ADD { FILE | FILES } resource_name [ ... ] ``` resource_name* The name of the file or directory to be added. ```sql ADD FILE /tmp/test; ADD FILE "/path/to/file/abc.txt"; ADD FILE '/another/test.txt'; ADD FILE "/path with space/abc.txt"; ADD FILE "/path/to/some/directory"; ADD FILES "/path with space/cde.txt" '/path with space/fgh.txt'; ```
Project: Trivy (Provisioning / Security & Compliance)
File: travis-ci.md

``` $ cat .travis.yml services: docker env: global: COMMIT=${TRAVIS_COMMIT::8} before_install: docker build -t trivy-ci-test:${COMMIT} . export VERSION=$(curl --silent "https://api.github.com/repos/aquasecurity/trivy/releases/latest" | grep '"tag_name":' | sed -E 's/."v([^"]+)"./\1/') wget https://github.com/aquasecurity/trivy/releases/download/v${VERSION}/trivy${VERSION}Linux-64bit.tar.gz tar zxvf trivy${VERSION}Linux-64bit.tar.gz script: ./trivy image --exit-code 0 --severity HIGH --no-progress trivy-ci-test:${COMMIT} ./trivy image --exit-code 1 --severity CRITICAL --no-progress trivy-ci-test:${COMMIT} cache: directories: $HOME/.cache/trivy ```
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2019-02-28.md

This report covers the development in the [linuxkit/linuxkit] [linuxkit/lcow] [linuxkit/kubernetes] [linuxkit/virtsock] [linuxkit/rtf] [linuxkit/homebrew-linuxkit] repositories. There were 38 contributions (PRs/Issues/Comments) from 8 individual contributors. 9 new PRs were opened and 10 PRs were merged. 5 new issues were opened and 2 issues were closed. We updated `containerd` to v1.2.4 and WireGuard to 0.0.20190227 and added `binfmt` support for s390x and named pipe support for `init` containers. Add support for named pipes to init ([linuxkit/linuxkit#3238] [@kppk] [@rn] [@justincormack]) Add s390x support to binfmt_misc ([linuxkit/linuxkit#3253] [@johanneswuerbach] [@rn]) Update kernels to 4.20.6/4.19.19/4.14.97/4.9.154 ([linuxkit/linuxkit#3281] [@rn] [@ijc]) Update Authors ([linuxkit/linuxkit#3283] [@rn] [@deitch]) January 2019 development report ([linuxkit/linuxkit#3284] [@rn] [@justincormack]) Kernel update to 4.20.7/4.19.20/4.14.98/4.9.155 ([linuxkit/linuxkit#3285] [@rn] [@justincormack]) Containerd v1.2.3 ([linuxkit/linuxkit#3286] [@ijc] [@justincormack]) Containerd v1.2.4 ([linuxkit/linuxkit#3290] [@ijc] [@rn]) Update kernels to 4.20.12/4.19.25/4.14.103/4.9.160 ([linuxkit/linuxkit#3292] [@rn] [@justincormack]) wireguard: upgrade to 0.0.20190227 ([linuxkit/linuxkit#3293] [@zx2c4] [@rn]) containerised kubelet going away ([linuxkit/kubernetes#88] [@justincormack] [@deitch]) add support for named pipes to init ([linuxkit/linuxkit#3237] [@kppk] [@justincormack] [@tjfontaine]) Setup the bond interfaces with proper default routes ([linuxkit/linuxkit#2479] [@TheOriginalAlex] [@justincormack]) linuxkit bake ([linuxkit/linuxkit#2648] [@w9n] [@ijc] [@rn]) Create README.md ([linuxkit/linuxkit#3219] [@montao] [@rn]) Feature/logging compression ([linuxkit/linuxkit#3261] [@teeg82] [@djs55]) Update to Alpine 3.9 and cut a release ([linuxkit/linuxkit#3282] [@rn] [@masterzen]) testing CI: DO NOT MERGE ([linuxkit/linuxkit#3287] [@justincormack]) CI logs are listing thousands of kprobes ([linuxkit/linuxkit#3288] [@justincormack] [@rn]) linuxkit run failing recently with d4m edge/stable on high sierra and mojave ([linuxkit/linuxkit#3289] [@dweomer] [@justincormack]) "sidecar" containers ([linuxkit/linuxkit#3291] [@justincormack])
Project: ClickHouse (App Definition and Development / Database)
File: replicated_fetches.md

slug: /en/operations/system-tables/replicated_fetches Contains information about currently running background fetches. Columns: `database` () Name of the database. `table` () Name of the table. `elapsed` () The time elapsed (in seconds) since showing currently running background fetches started. `progress` () The percentage of completed work from 0 to 1. `resultpartname` () The name of the part that will be formed as the result of showing currently running background fetches. `resultpartpath` () Absolute path to the part that will be formed as the result of showing currently running background fetches. `partition_id` () ID of the partition. `totalsizebytes_compressed` () The total size (in bytes) of the compressed data in the result part. `bytesreadcompressed` () The number of compressed bytes read from the result part. `sourcereplicapath` () Absolute path to the source replica. `sourcereplicahostname` () Hostname of the source replica. `sourcereplicaport` () Port number of the source replica. `interserver_scheme` () Name of the interserver scheme. `URI` () Uniform resource identifier. `to_detached` () The flag indicates whether the currently running background fetch is being performed using the `TO DETACHED` expression. `thread_id` () Thread identifier. Example ``` sql SELECT * FROM system.replicated_fetches LIMIT 1 FORMAT Vertical; ``` ``` text Row 1: database: default table: t elapsed: 7.243039876 progress: 0.41832135995612835 resultpartname: all00_0 resultpartpath: /var/lib/clickhouse/store/700/70080a04-b2de-4adf-9fa5-9ea210e81766/all00_0/ partition_id: all totalsizebytes_compressed: 1052783726 bytesreadcompressed: 440401920 sourcereplicapath: /clickhouse/test/t/replicas/1 sourcereplicahostname: node1 sourcereplicaport: 9009 interserver_scheme: http URI: http://node1:9009/?endpoint=DataPartsExchange%3A%2Fclickhouse%2Ftest%2Ft%2Freplicas%2F1&part=all000&clientprotocol_version=4&compress=false to_detached: 0 thread_id: 54 ``` See Also
Project: ClickHouse (App Definition and Development / Database)
File: uniqcombined64.md

slug: /en/sql-reference/aggregate-functions/reference/uniqcombined64 sidebar_position: 193 Calculates the approximate number of different argument values. It is the same as , but uses a 64-bit hash for all data types rather than just for the String data type. ``` sql uniqCombined64(HLL_precision)(x[, ...]) ``` Parameters `HLLprecision`: The base-2 logarithm of the number of cells in . Optionally, you can use the function as `uniqCombined64(x[, ...])`. The default value for `HLLprecision` is 17, which is effectively 96 KiB of space (2^17 cells, 6 bits each). `X`: A variable number of parameters. Parameters can be `Tuple`, `Array`, `Date`, `DateTime`, `String`, or numeric types. Returned value A number -type number. Implementation details The `uniqCombined64` function: Calculates a hash (64-bit hash for all data types) for all parameters in the aggregate, then uses it in calculations. Uses a combination of three algorithms: array, hash table, and HyperLogLog with an error correction table. For a small number of distinct elements, an array is used. When the set size is larger, a hash table is used. For a larger number of elements, HyperLogLog is used, which will occupy a fixed amount of memory. Provides the result deterministically (it does not depend on the query processing order). :::note Since it uses 64-bit hash for all types, the result does not suffer from very high error for cardinalities significantly larger than `UINT_MAX` like does, which uses a 32-bit hash for non-`String` types. ::: Compared to the function, the `uniqCombined64` function: Consumes several times less memory. Calculates with several times higher accuracy. Example In the example below `uniqCombined64` is run on `1e10` different numbers returning a very close approximation of the number of different argument values. Query: ```sql SELECT uniqCombined64(number) FROM numbers(1e10); ``` Result: ```response uniqCombined64(number) 9998568925 -- 10.00 billion ``` By comparison the `uniqCombined` function returns a rather poor approximation for an input this size. Query: ```sql SELECT uniqCombined(number) FROM numbers(1e10); ``` Result: ```response uniqCombined(number) 5545308725 -- 5.55 billion ``` See Also
Project: Koperator (App Definition and Development / Streaming & Messaging)
File: SECURITY.md

This document outlines security procedures and general policies for the Koperator project. The Koperator team and community take all security bugs in Koperator seriously. Thank you for improving the security of Koperator. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions. Report security bugs by emailing `oss-security@cisco.com`. The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps: Confirm the problem and determine the affected versions. Audit code to find any potential similar problems. Prepare fixes for all releases still under maintenance. These fixes will be released as quickly as possible. If you have suggestions on how this process could be improved please submit a pull request.
Project: ArangoDB (App Definition and Development / Database)
File: result.md

+++ title = "`result<T, E = varies, NoValuePolicy = policy::default_policy<T, E, void>>`" description = "A type alias to a `stdresult<T, E, NoValuePolicy>` (standalone edition) or `boostresult<T, E, NoValuePolicy>` (Boost edition)." +++ A type alias to either {{% api "stdresult<T, E = std::errorcode, NoValuePolicy = policy::defaultpolicy<T, E, void>>" %}} (standalone edition) or {{% api "boostresult<T, E = boost::system::errorcode, NoValuePolicy = policy::defaultpolicy<T, E, void>>" %}} (Boost edition), and `policy::`{{% api "default_policy" %}}. This means that `result<T>` uses the appropriate default alias depending on which edition of Outcome is in use. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/result.hpp>`
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubedb-webhook-server.md

title: Kubedb-Webhook-Server menu: docs_{{ .version }}: identifier: kubedb-webhook-server name: Kubedb-Webhook-Server parent: reference-webhook-server weight: 0 menuname: docs{{ .version }} sectionmenuid: reference url: /docs/{{ .version }}/reference/webhook-server/ aliases: /docs/{{ .version }}/reference/webhook-server/kubedb-webhook-server/ ``` --bypass-validating-webhook-xray if true, bypasses validating webhook xray checks --default-seccomp-profile-type string Default seccomp profile -h, --help help for kubedb-webhook-server --use-kubeapiserver-fqdn-for-aks if true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522 (default true) ``` - Launch KubeDB Webhook Server - Prints binary version number.
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_upstreamauthority_spire.md

The `spire` plugin uses credentials fetched from the Workload API to call an upstream SPIRE server in the same trust domain, requesting an intermediate signing certificate to use as the server's X.509 signing authority. The SVIDs minted in a nested configuration are valid in the entire trust domain, not only in the scope of the server that originated the SVID. In the case of X509-SVID, this is easily achieved because of the chaining semantics that X.509 has. On the other hand, for JWT-SVID, this capability is accomplished by propagating every JWT-SVID public signing key to the whole topology. The plugin accepts the following configuration options: | Configuration | Description | ||| | server_address | IP address or DNS name of the upstream SPIRE server in the same trust domain | | server_port | Port number of the upstream SPIRE server in the same trust domain | | workloadapisocket | Path to the Workload API socket (Unix only; e.g. the SPIRE Agent API socket) | | experimental | The experimental options that are subject to change or removal | These are the current experimental configurations: | experimental | Description | Default | ||--|| | workloadapinamedpipename | Pipe name of the Workload API named pipe (Windows only; e.g. pipe name of the SPIRE Agent API named pipe) | Sample configuration (Unix): ```hcl UpstreamAuthority "spire" { plugin_data { server_address = "upstream-spire-server", server_port = "8081", workloadapisocket = "/tmp/spire-agent/public/api.sock" } } ``` Sample configuration (Windows): ```hcl UpstreamAuthority "spire" { plugin_data { server_address = "upstream-spire-server", server_port = "8081", experimental { workloadapinamedpipename = "\\spire-agent\\public\\api" } } } ```
Project: Scylla (App Definition and Development / Database)
File: row_cache.md

This document assumes familiarity with the mutation model and . Cache is always paired with its underlying mutation source which it mirrors. That means that from the outside it appears as containing the same set of writes. Internally, it keeps a subset of data in memory, together with information about which parts are missing. Elements which are fully represented are called "complete". Complete ranges of elements are called "continuous". Eviction is about removing parts of the data from memory and recording the fact that information about those parts is missing. Eviction doesn't change the set of writes represented by cache as part of its `mutation_source` interface. The smallest object which can be evicted, called eviction unit, is currently a single row (`rowsentry`). Eviction units are linked in an LRU owned by a `cachetracker`. The LRU determines eviction order. The LRU is shared among many tables. Currently, there is one per `database`. All `rowsentry` objects which are owned by a `cachetracker` are assumed to be either contained in a cache (in some `rowcache::partitionstype`) or be owned by a (detached) `partitionsnapshot`. When the last row from a `partitionentry` is evicted, the containing `cache_entry` is evicted from the cache. We never evict individual `partitionversion` objects independently of the containing `partitionentry`. When the latest version becomes fully evicted, we evict the whole `partitionentry` together with all unreferenced versions. Snapshots become detached. `partitionsnapshots` go away on their own, but eviction can make them contain no rows. Snapshots can undergo eviction even after they were detached from its original `partition_entry`. The static row is not evictable, it goes away together with the partition. Partition reads which only read from the static row keep it alive by touching the last dummy `rows_entry`. Every `partitionversion` has a dummy entry after all rows (`positioninpartition::afterallclusteringrows()`) so that the partition can be tracked in the LRU even if it doesn't have any rows and so that it can be marked as fully discontinuous when all of its rows get evicted. `rowsentry` objects in memtables are not owned by a `cachetracker`, they are not evictable. Data referenced by `partition_snapshots` created on non-evictable partition entries is not transferred to cache, so unevictable snapshots are not made evictable.
Project: Vald (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

<! Provide a general summary of your changes in the Title above --> <!-- Describe your changes in detail --> <!-- It would be better to describe the details especially What changed and Why you changed --> <!-- This project mainly accepts pull requests related to open issues --> <!-- NOTE: If suggesting a new feature or change, please discuss it in an issue first --> <!-- NOTE: If fixing a bug, there should be an issue describing it with steps to reproduce --> <!-- Please link to the issue here: --> <! Please change the versions below along with your environment --> Go Version: 1.22.3 Rust Version: 1.77.2 Docker Version: 20.10.8 Kubernetes Version: v1.30.0 NGT Version: 2.2.1 <!-- For completed items, change [ ] to [x]. --> <!-- NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. --> document and completed . for the similar feature or fixes? <!-- Please tell us anything you would like to share to reviewers related this PR -->
Project: Infinispan (App Definition and Development / Database)
File: README-i18n.md

Documentation for Infinispan is maintained on http://www.infinispan.org If you are interested in contributing a translation of the documentation, please get in touch with the Infinispan development team. Details on how to do so are on http://www.jboss.org/infinispan/community Infinispan logs fully support internationalization. The following is a list of modules and their message id reservation ranges: 0001 - 1000 core 1001 - 2000 tree 2001 - 3000 bdbje cache store 3001 - 4000 cassandra cache store 4001 - 5000 hotrod client 5001 - 6000 server core 6001 - 7000 server hotrod 7001 - 8000 cloud cache store 8001 - 9000 jdbc cache store 9001 - 10000 jdbm cache store 10001 - 11000 remote cache store 11001 - 12000 server memcached 12001 - 13000 server rest 13001 - 14000 server websocket 14001 - 14800 query 14801 - 15000 query-dsl 15001 - 16000 lucene directory 16001 - 17000 <no longer used> 17001 - 18000 cdi integration 18001 - 19000 hbase cache store 19001 - 20000 cli interpreter 20001 - 21000 cli client 21001 - 22000 mongodb cachestore 22001 - 23000 rest cache store 23001 - 24000 leveldb cache store [unused] 24001 - 25000 couchbase cache store 25001 - 26000 extended statistics 26001 - 27000 infinispan directory provider 26001 - 27000 scripting 27001 - 28000 tasks 28001 - 28500 remote query server 28501 - 29000 object filter 29001 - 29500 soft-index file store 29501 - 30000 clustered counter 30001 - 30501 anchored keys 30501 - 31000 cloudevents integration
Project: ShardingSphere (App Definition and Development / Database)
File: tags.en.md

date: 2018-11-29T08:41:44+01:00 title: Tags weight: 40 tags: ["documentation", "tutorial"] Learn theme support one default taxonomy of gohugo: the tag feature. Just add tags to any page: ```markdown date: 2018-11-29T08:41:44+01:00 title: Theme tutorial weight: 15 tags: ["tutorial", "theme"] ``` The tags are displayed at the top of the page, in their insertion order. Each tag is a link to a Taxonomy page displaying all the articles with the given tag. In the `config.toml` file you can add a shortcut to display all the tags ```toml [[menu.shortcuts]] name = "<i class='fas fa-tags'></i> Tags" url = "/tags" weight = 30 ```