cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: cloud-queries-live.md

title: View live queries in YugabyteDB Managed headerTitle: View live queries linkTitle: Live queries description: View live queries running on your cluster. headcontent: View live queries running on your cluster menu: preview_yugabyte-cloud: identifier: cloud-queries-live parent: cloud-monitor weight: 200 type: docs Evaluate the performance of running queries on your cluster using the Live Queries on the cluster Performance tab. You can use this data to: Visually identify relevant database operations. Evaluate query execution times. Discover potential queries for . Live queries only shows queries "in-flight" (that is, currently in progress); queries that execute quickly might not show up by the time the display loads. There is no significant performance overhead on databases because the queries are fetched on-demand and are not tracked in the background. You can choose between displaying YSQL and YCQL queries. To filter the query list, enter query text in the filter field. To sort the list by column, click the column heading. Click Edit Options to select the columns to display. To view query details, click the right-arrow button for the query in the list to display the Query Details sheet. The following table describes the Live Queries column values. | Column | Description | | | | | Node Name | The name of the node where the query executed. | | Database /Keyspace | The YCQL keyspace or YSQL database used by the query. | | Elapsed Time | The duration (in milliseconds) of the query handling. | | Status (YSQL) | The YSQL session status: idle, active, idle in transaction, fastpath function call, idle in transaction (aborted), or disabled. | | Type (YCQL) | The YCQL query type: PREPARE, EXECUTE, QUERY, or BATCH | | Client Host | The address of the client that sent this query. | | Client Port | The port of the client that sent this query. |
Project: Keylime (Provisioning / Security & Compliance)
File: RELEASE.md

Keylime uses a semantic versioning process: Major.Minor.Patch When a bug fix is made: ``` v0.0.3 // Before bugfix v0.0.4 // After bugfix ``` When you add functionality and your code stays backwards compatible, you increase the minor component and reset the patch component to zero: ``` v0.2.4 // Before addition of new functionality v0.3.0 // After addition of new functionality ``` When you implement changes and your code becomes backwards incompatible (e.g. API change), you increase the major component and reset the minor and patch components to zero: ``` v7.3.5 // Before implementing backwards incompatible changes v8.0.0 // After implementing backwards incompatible changes ``` Semver is realised using git tags: $ git tag -a v3.0.2 -m 'Keylime version 3.0.2' Alternatively, you can use the github UI to create a tag, at the same time as the release. Go to the and enter a Tag, provide a title (Keylime vx.x.x) and list the changes in the release, linking to commits. More details about
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_role_definitions.md

+++ title = "azurermroledefinitions resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermroledefinitions" identifier = "inspec/resources/azure/azurermroledefinitions.md azurermroledefinitions resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurerole_definitions" >}} Use the `azurermroledefinitions` InSpec audit resource to test properties of some or all Azure Role Definitions. This resource interacts with version `2015-07-01` of the Azure Graph API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.3.7 of the inspec-azure resource pack. An `azurermroledefinitions` resource block returns all Role definitions within a subscription and allows testing of them. describe azurermroledefinitions do ... end The following examples show how to use this InSpec audit resource. ```ruby describe azurermroledefinitions.where{name.eql?('Custom-Admin')} do its ('properties.first.permissions.first') { should have_attributes(actions: ['*']) } end ``` describe azurermroledefinitions do its ('properties.first.permissions.first') { should have_attributes(notActions: [ 'Microsoft.Authorization/*/Delete', 'Microsoft.Authorization/*/Write', 'Microsoft.Authorization/elevateAccess/Action', 'Microsoft.Blueprint/blueprintAssignments/write', 'Microsoft.Blueprint/blueprintAssignments/delete' ]) } end Filters the results to include only those resource groups that match the given name. This is a string value. describe azurermroledefinitions.where{name.eql?('Custom-Admin') } do it { should exist } end `ids` `names` `properties` The Object IDs of the Roles. The names of the Roles. For a built-in role this will be an Azure generated UUID. For a CustomRole this will be the name you specified on creation. Additional properties available for the Roles. May be accessed with dot notation in controls. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermroledefinitions do it { should exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.4.0.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | HTTP Browsing interface for DFS Health/Status | Major | . | Devaraj Das | | | | mini map/reduce cluster for junit tests | Major | . | Owen O'Malley | Milind Bhandarkar | | | Do not assign blocks to a datanode with \< x mb free | Major | . | Johan Oskarsson | Johan Oskarsson | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | nicer reports of progress for distcp | Minor | util | Owen O'Malley | Owen O'Malley | | | add links to task tracker http server from task details and failure pages | Minor | . | Owen O'Malley | Owen O'Malley | | | remove the append phase in sorting the reduce inputs | Major | . | Owen O'Malley | Owen O'Malley | | | the randomwriter example will clobber the output file | Major | . | Owen O'Malley | Owen O'Malley | | | tasktracker waits for 10 seconds for asking for a task. | Minor | . | Mahadev konar | Mahadev konar | | | support generic command-line options | Minor | conf | Doug Cutting | Hairong Kuang | | | cleanup of dead field (map ouput port) | Minor | . | Owen O'Malley | Owen O'Malley | | | add a -i option to distcp to ignore read errors of the input files | Major | util | Owen O'Malley | Owen O'Malley | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | maps from second jobs will not run until the first job finishes completely | Major | . | Owen O'Malley | Owen O'Malley | | | Namenode not able to accept connections | Major | . | Mahadev konar | Devaraj Das | | | dfs client timeout on read kills task | Major | . | Owen O'Malley | Owen O'Malley | | | job tracker has a deadlock | Major | . | Owen O'Malley | Owen O'Malley | | | "connection was forcibly closed" Exception in RPC on Windows | Major | ipc | Konstantin Shvachko | Doug Cutting | | | FileSystem "close" does not remove the closed fs from the fs map | Major | fs | Hairong Kuang | Hairong Kuang | | | Potential deadlock in JobTracker. | Major | . | Konstantin Shvachko | Owen O'Malley | | | a missing map/reduce input directory does not produce a user-visible error message | Major | . | Owen O'Malley | Owen O'Malley | | | UnregisteredDatanodeException message correction | Trivial | . | Konstantin Shvachko | Konstantin Shvachko | | | ClassNotFoundException under jvm 1.6 | Major | ipc | Owen O'Malley | Owen O'Malley | | | MapRed tries to allocate tasks to nodes that have no available disk space | Major | . | Mike Cafarella | | | | task trackers can only be assigned one task every heartbeat | Major | . | Owen O'Malley | Owen O'Malley | | | Progress in writing a DFS file does not count towards Job progress and can make the task timeout | Major | . | Milind Bhandarkar | Milind Bhandarkar |
Project: KICS (Provisioning / Security & Compliance)
File: 3b30e3d6-c99b-4318-b38f-b99db74578b5.md

title: Private Cluster Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3b30e3d6-c99b-4318-b38f-b99db74578b5 Query name: Private Cluster Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Kubernetes Clusters must be created with Private Clusters enabled, meaning the 'privateclusterconfig' must be defined and the attributes 'enableprivateendpoint' and 'enableprivatenodes' must be true.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2 66 48 85 31" name: create a cluster1 google.cloud.gcpcontainercluster: name: my-cluster1 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present name: create a cluster2 google.cloud.gcpcontainercluster: name: my-cluster2 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present privateclusterconfig: enableprivateendpoint: yes name: create a cluster3 google.cloud.gcpcontainercluster: name: my-cluster3 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present privateclusterconfig: enableprivatenodes: yes name: create a cluster4 google.cloud.gcpcontainercluster: name: my-cluster4 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present privateclusterconfig: enableprivateendpoint: no enableprivatenodes: yes name: create a cluster5 google.cloud.gcpcontainercluster: name: my-cluster5 initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present privateclusterconfig: enableprivateendpoint: yes enableprivatenodes: no ``` ```yaml title="Negative test num. 1 - yaml file" name: create a cluster google.cloud.gcpcontainercluster: name: my-cluster initialnodecount: 2 master_auth: username: cluster_admin password: my-secret-password node_config: machine_type: n1-standard-4 disksizegb: 500 location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present privateclusterconfig: enableprivateendpoint: yes enableprivatenodes: yes ```
Project: Grafeas (Provisioning / Security & Compliance)
File: grafeas_image.md

Grafeas server images are available in `us.gcr.io/grafeas/grafeas-server`. If you've never pulled/pushed images from GCR, you can find . The Grafeas server image can be built via its : ```bash docker build --tag=grafeas . ``` Make sure you have access to push new Grafeas server images. At this point, only official maintainers of the Grafeas project have such access. To push a new Grafeas server image, you'll need to build it first: ```bash ... inside go/src/github.com/grafeas/grafeas ... docker build --tag=grafeas . ``` Set the `gcloud` project: ```bash PROJECT=grafeas gcloud config set project $PROJECT ... if needed, update... gcloud components update ``` Ensure docker auth is configured: ``` gcloud auth configure-docker gcloud credential helpers already registered correctly. ``` Then, tag and push it to GCR: ```bash docker tag grafeas us.gcr.io/grafeas/grafeas-server docker push us.gcr.io/grafeas/grafeas-server The push refers to repository [us.gcr.io/grafeas/grafeas-server] a4d748b5fa54: Pushed a464c54f93a9: Layer already exists latest: digest: sha256:be16348fd0444426af195b33935fbf8b1479c971eda5ef5ebeb265129cfa6538 size: 739 ```
Project: ScalarDB (App Definition and Development / Database)
File: index.md

](https://github.com/scalar-labs/scalardb/actions/workflows/ci.yaml) ScalarDB is a universal transaction manager that achieves: database/storage-agnostic ACID transactions in a scalable manner even if an underlying database or storage is not ACID-compliant. multi-storage/database/service ACID transactions that can span multiple (possibly different) databases, storages, and services. The library is available on . You can install it in your application using your build tool such as Gradle and Maven. To add a dependency on ScalarDB using Gradle, use the following: ```gradle dependencies { implementation 'com.scalar-labs:scalardb:3.12.2' } ``` To add a dependency using Maven: ```xml <dependency> <groupId>com.scalar-labs</groupId> <artifactId>scalardb</artifactId> <version>3.12.2</version> </dependency> ``` Slides at ApacheCon@Home 2020 at Database Lounge Tokyo #6 2020 at Next Generation Cassandra Conference / ApacheCon NA 2019 Javadoc - ScalarDB: A universal transaction manager that achieves database-agnostic transactions and distributed transactions that span multiple databases - ScalarDB RPC libraries - ScalarDB Server: A gRPC interface of ScalarDB - ScalarDB Schema Loader: A tool for schema creation and schema deletion in ScalarDB This library is mainly maintained by the Scalar Engineering Team, but of course we appreciate any help. For asking questions, finding answers and helping other users, please go to and use tag. For filing bugs, suggesting improvements, or requesting new features, help us out by opening an issue. Here are the contributors we are especially thankful for: - created for ScalarDB - reported bugs around Serializable and proposed a new Serializable strategy (now named Extra-Read) This project uses to automate code format and so on as much as possible. If you're interested in the development of ScalarDB, please and the git hook script as follows. ``` $ ls -a .pre-commit-config.yaml .pre-commit-config.yaml $ pre-commit install ``` The code formatter is automatically executed when committing files. A commit will fail and be formatted by the formatter when any invalid code format is detected. Try to commit the change again. ScalarDB is dual-licensed under both the Apache 2.0 License (found in the LICENSE file in the root directory) and a commercial license. You may select, at your option, one of the above-listed licenses. The commercial license includes several enterprise-grade features such as management tools and declarative query interfaces like GraphQL and SQL interfaces. Regarding the commercial license, please for more information.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: clair-datasource.md

title: Kubernetes Admission Control using Vulnerability Scanning software: kubernetes clair labels: layer: orchestration category: containers datasource: clair code: https://github.com/open-policy-agent/contrib/tree/master/image_enforcer tutorials: https://github.com/open-policy-agent/contrib/blob/master/image_enforcer/README.md docs_features: rest-api-integration: note: | This example project in uses OPA over the REST API to enforce admission policy based on vulnerability scanning results. kubernetes: note: | This example project in uses OPA to enforce admission policy in Kubernetes. Admission control policies in Kubernetes can be augmented with vulnerability scanning results to make more informed decisions. This integration demonstrates how to integrate CoreOS Clair with OPA and run it as an admission controller.
Project: ShardingSphere (App Definition and Development / Database)
File: show-sharding-algorithm-plugins.en.md

+++ title = "SHOW SHARDING ALGORITHM PLUGINS" weight = 2 +++ The `SHOW SHARDING ALGORITHM PLUGINS` syntax is used to query all the plugins of the interface `org.apache.shardingsphere.sharding.spi.ShardingAlgorithm`. {{< tabs >}} {{% tab name="Grammar" %}} ```sql showShardingAlgorithmPlugins ::= 'SHOW' 'SHARDING' 'ALGORITHM' 'PLUGINS' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Columns | Description | |--|--| | type | type | | type_aliases | type aliases | | description | description | Query all the plugins for `org.apache.shardingsphere.sharding.spi.ShardingAlgorithm` interface ```sql SHOW SHARDING ALGORITHM PLUGINS ``` ```sql SHOW SHARDING ALGORITHM PLUGINS; +-+--+-+ | type | type_aliases | description | +-+--+-+ | MOD | | | | HASH_MOD | | | | VOLUME_RANGE | | | | BOUNDARY_RANGE | | | | AUTO_INTERVAL | | | | INTERVAL | | | | CLASS_BASED | | | | INLINE | | | | COMPLEX_INLINE | | | | HINT_INLINE | | | +-+--+-+ 10 rows in set (0.27 sec) ``` `SHOW`, `SHARDING`, `ALGORITHM`, `PLUGINS`
Project: BigchainDB (App Definition and Development / Database)
File: ntp-notes.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > There are several NTP daemons available, including: The reference NTP daemon (`ntpd`) from ntp.org; see Maybe , once it's production-ready Maybe , once it's production-ready We suggest you run your NTP daemon in a mode which will tell your OS kernel to handle leap seconds in a particular way: the default NTP way, so that system clock adjustments are localized and not spread out across the minutes, hours, or days surrounding leap seconds (e.g. "slewing" or "smearing"). There's . Use the default mode with `ntpd` and `chronyd`. For another NTP daemon, consult its documentation. It's tricky to make an NTP daemon setup secure. Always install the latest version and read the documentation about how to configure and run it securely. See the . If your BigchainDB node is running on an Amazon Linux instance (i.e. a Linux instance packaged by Amazon, not Canonical, Red Hat, or someone else), then an NTP daemon should already be installed and configured. See the EC2 documentation on . That said, you should check which NTP daemon is installed. Is it recent? Is it configured securely? The are based on the reference implementation of NTP. The following commands will uninstall the `ntp` and `ntpdate` packages, install the latest `ntp` package (which might not be based on the latest ntpd code), and start the NTP daemon (a local NTP server). (`ntpdate` is not reinstalled because it's and you shouldn't use it.) ```text sudo apt-get --purge remove ntp ntpdate sudo apt-get autoremove sudo apt-get update sudo apt-get install ntp sudo service ntp restart ``` You can check if `ntpd` is running using `sudo ntpq -p`. You may want to use different NTP time servers. You can change them by editing the NTP config file `/etc/ntp.conf`. Note: A server running an NTP daemon can be used by others for DRDoS amplification attacks. The above installation procedure should install a default NTP configuration file `/etc/ntp.conf` with the lines: ```text restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery ``` Those lines should prevent the NTP daemon from being used in an attack. (The first line is for IPv4, the second for IPv6.) There are additional things you can do to make NTP more secure. See the for more details.
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: CHANGELOG.md

Releases ======== v1.11.0 (2023-03-28) ==================== `Errors` now supports any error that implements multiple-error interface. Add `Every` function to allow checking if all errors in the chain satisfies `errors.Is` against the target error. v1.10.0 (2023-03-08) ==================== Comply with Go 1.20's multiple-error interface. Drop Go 1.18 support. Per the support policy, only Go 1.19 and 1.20 are supported now. Drop all non-test external dependencies. v1.9.0 (2022-12-12) =================== Add `AppendFunc` that allow passsing functions to similar to `AppendInvoke`. Bump up yaml.v3 dependency to 3.0.1. v1.8.0 (2022-02-28) =================== `Combine`: perform zero allocations when there are no errors. v1.7.0 (2021-05-06) =================== Add `AppendInvoke` to append into errors from `defer` blocks. v1.6.0 (2020-09-14) =================== Actually drop library dependency on development-time tooling. v1.5.0 (2020-02-24) =================== Drop library dependency on development-time tooling. v1.4.0 (2019-11-04) =================== Add `AppendInto` function to more ergonomically build errors inside a loop. v1.3.0 (2019-10-29) =================== Switch to Go modules. v1.2.0 (2019-09-26) =================== Support extracting and matching against wrapped errors with `errors.As` and `errors.Is`. v1.1.0 (2017-06-30) =================== Added an `Errors(error) []error` function to extract the underlying list of errors for a multierr error. v1.0.0 (2017-05-31) =================== No changes since v0.2.0. This release is committing to making no breaking changes to the current API in the 1.X series. v0.2.0 (2017-04-11) =================== Repeatedly appending to the same error is now faster due to fewer allocations. v0.1.0 (2017-31-03) =================== Initial release
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.8-en.md

Print a warning message when boot with the default (insecure) Erlang cookie. Change the `/gateway` API path to plural form. Don't allow updating config items when they already exist in `local-override.conf`. Remove `node.etc_dir` from emqx.conf, because it is never used. Also allow user to customize the logging directory Added a new API `POST /listeners` for creating listener. Close ExProto client process immediately if it's keepalive timeouted. Upgrade grpc-erl driver to 0.6.7 to support batch operation in sending stream. Fix exhook `client.authorize` never being execauted. Fix JWT plugin don't support non-integer timestamp claims. Avoid publishing will message when client fails to auhtenticate. Speed up dispatching of shared subscription messages in a cluster Fix the extra / prefix when CoAP gateway parsing client topics. Speed up updating the configuration, When some nodes in the cluster are down. Fix delayed publish inaccurate caused by os time change. Fix that EMQX can't start when the retainer is disabled Fix that redis authn will deny the unknown users Fix ExProto UDP client keepalive checking error. This causes the clients to not expire as long as a new UDP packet arrives Fix that MQTT Bridge message payload could be empty string.