cwielenb/CNCF-Dataset huggingface dataset:
Project: Notary (Provisioning / Security & Compliance)
File: RELEASE_CHECKLIST.md

This document describes the checklist to publish a release via GitHub workflow. NOTE: Make sure the dependencies in `go.mod` file are expected by the release. For example, if there are dependencies on certain version of notation library (notation-go or notation-core-go) or ORAS library (oras-go), make sure that version of library is released first, and the version number is updated accordingly in `go.mod` file. After updating go.mod file, run `go mod tidy` to ensure the go.sum file is also updated with any potential changes. Determine a -valid version prefixed with the letter `v` for release. For example, `version="v1.0.0-alpha.1"`. Bump up the `Version` in and open a PR for the changes. Wait for the PR merge. Be on the main branch connected to the actual repository (not a fork) and `git pull`. Ensure `git log -1` shows the latest commit on the main branch. Create a tag `git tag -am $version $version` `git tag` and ensure the name in the list added looks correct, then push the tag directly to the repository by `git push --follow-tags`. Wait for the completion of the GitHub action . Check the new draft release, revise the release description, and publish the release. Announce the release in the community.
Project: Stolon (App Definition and Development / Database)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at sgotti@sorint.it. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Meshery (Provisioning / Automation & Configuration)
File: metallb.md

layout: integration title: Metallb subtitle: Collaborative and visual infrastructure as code for Metallb image: /assets/img/integrations/metallb/icons/color/metallb-color.svg permalink: extensibility/integrations/metallb docURL: https://docs.meshery.io/extensibility/integrations/metallb description: integrations-category: Cloud Native Network integrations-subcategory: Service Proxy registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.131.md

layout: release date: 2023-08-22 tag: v0.6.131 change the location where binded node info is captured @MUzairS15 (#8562) [CI] Swagger docs build failing @suhail34 (#8551) [Lifecycle] mesheryctl: slim profile with no adapters by default @leecalcote (#8566) [UI] Fix issue with button alignment @abhinandanudupa (#8539) [connections] Migrate K8sCtx to Connections @theBeginner86 (#8321) Bump eslint from 8.46.0 to 8.47.0 in /provider-ui @dependabot (#8525) Refactor drawer links @aabidsofi19 (#8558) Bump cypress from 12.17.1 to 12.17.4 in /provider-ui @dependabot (#8529) Bump eslint-plugin-cypress from 2.13.3 to 2.14.0 in /provider-ui @dependabot (#8523) Meshmodel Browser @UsmanDev09 (#8466) Fixed height consistency in design cards @EraKin575 (#8492) [Notification Center] Refactor EVENT_TYPES and Icons @aabidsofi19 (#8546) [Notification Center] Refactor EVENT_TYPES and Icons @aabidsofi19 (#8546) Bump eslint from 8.46.0 to 8.47.0 in /provider-ui @dependabot (#8525) Bump cypress from 12.17.1 to 12.17.4 in /provider-ui @dependabot (#8529) Bump eslint-plugin-cypress from 2.13.3 to 2.14.0 in /provider-ui @dependabot (#8523) Fixed email-on-failure job in stable release @VaibhavMalik4187 (#8554) Scrolling error in meshery docs for small screen fixed @Aayush987 (#8550) Fixing Documentation issues @thisiskaransgit (#8128) Thank you to our contributors for making this release possible: @Aayush987, @Aisuko, @Chadha93, @EraKin575, @MUzairS15, @UsmanDev09, @VaibhavMalik4187, @aabidsofi19, @abhinandanudupa, @alphaX86, @dependabot, @dependabot[bot], @l5io, @leecalcote, @suhail34, @theBeginner86, @thisiskaransgit and l5io
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_report_kubeblocks.md

title: kbcli report kubeblocks Report KubeBlocks information, including deployments, events, logs, etc. ``` kbcli report kubeblocks [-f file] [--with-logs] [--mask] [flags] ``` ``` kbcli report kubeblocks kbcli report kubeblocks -f filename kbcli report kubeblocks --with-logs kbcli report kubeblocks --with-logs --mask ``` ``` --all-containers Get all containers' logs in the pod(s). Byt default, only the main container (the first container) will have logs recorded. -f, --file string zip file for output -h, --help help for kubeblocks --mask mask sensitive info for secrets and configmaps (default true) -o, --output string Output format. One of: json|yaml. (default "json") --since duration Only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used. --since-time string Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used. --with-logs include pod logs ``` ``` --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 --cluster string The name of the kubeconfig cluster to use --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 ``` - report kubeblocks or cluster info.
Project: TiDB (App Definition and Development / Database)
File: ci.md

The CI pipeline will automatically trigger when you submit a PR or push new commits. There are also some CI pipelines that support manual triggering, usually for integration testing, which will give you more confidence in the quality of PR. You can obtain the trigger command for all supported CI pipelines by commenting `/test ?` in a PR. | ci pipeline | Commands | Tests | Auto Trigger | | - | | | | | build | `/test build` | Build binaries. | Yes | | check-dev | `/test check-dev` | Some common check tasks including `lint`, `tidy` etc | Yes | | check-dev2 | `/test check-dev2` | All realtikv tests in `tests/realtikvtest` | Yes | | mysql-test | `/test mysql-test` | All mysql tests in PingCAP-QE/tidb-test `mysql_test` | Yes | | unit-test | `/test unit-test` | All unit tests | Yes | | pull-integration-ddl-test | `/test pull-integration-ddl-test` | All ddl tests in PingCAP-QE/tidb-test `ddl_test` | Yes | | pull-mysql-client-test | `/test pull-mysql-client-test` | MySQL client tests in PingCAP-QE/tidb-test | Yes | | pull-br-integration-test | `/test pull-br-integration-test` | All br integration test in `br/tests` | No | | pull-lightning-integration-test | `/test pull-lightning-integration-test` | All lightning integration tests in `br/tests` | No | | pull-common-test | `/test pull-common-test` | Some ORM tests performed through the unistore. | No | | pull-e2e-test | `/test pull-e2e-test` | E2e tests in `tests/globalkilltest` and `tests/graceshutdown` | No | | pull-integration-common-test | `/test pull-integration-common-test` | Some ORM tests performed through the tikv | No | | pull-integration-copr-test | `/test pull-integration-copr-test` | Coprocessor tests in | No | | pull-integration-nodejs-test | `/test pull-integration-nodejs-test` | Node.js ORM tests in PingCAP-QE/tidb-test | No | | pull-integration-jdbc-test | `/test pull-integration-jdbc-test` | All JDBC tests in PingCAP-QE/tidb-test | No | | pull-integration-mysql-test | `/test pull-integration-mysql-test` | All mysql tests in PingCAP-QE/tidb-test performed through the tikv | No | | pull-sqllogic-test | `/test pull-sqllogic-test` | SQL logic tests in PingCAP-QE/tidb-test | No | | pull-tiflash-test | `/test pull-tiflash-test` | TiFlash tests in pingcap/tiflash `tests/docker/` | No |
Project: StarRocks (App Definition and Development / Database)
File: user_privileges.md

displayed_sidebar: "English" `user_privileges` provides information about user privileges. The following fields are provided in `user_privileges`: | Field | Description | | -- | | | GRANTEE | The name of the user to which the privilege is granted. | | TABLE_CATALOG | The name of the catalog. This value is always `def`. | | PRIVILEGE_TYPE | The privilege granted. The value can be any privilege that can be granted at the global level. | | ISGRANTABLE | `YES` if the user has the `GRANT OPTION` privilege, `NO` otherwise. The output does not list `GRANT OPTION` as a separate row with `PRIVILEGETYPE='GRANT OPTION'`. |
Project: YDB (App Definition and Development / Database)
File: blockdevice.md

{{ ydb-short-name }} can be used as a platform for creating a wide range of data storage and processing systems, for example, by implementing a on {{ ydb-short-name }}. Network block devices implement an interface for a local block device, as well as ensure fault-tolerance (through redundancy) and good scalability in terms of volume size and the number of input/output operations per unit of time. The downside of a network block device is that any input/output operation on such device requires network interaction, which might increase the latency of the network device compared to the local device. You can deploy a common file system on a network block device and/or run an application directly on the block device, such as a database management system.
Project: KubeDL (Provisioning / Automation & Configuration)
File: startup_flags.md

| Flag Name | Description | Default | |- |-| --| |controller-metrics-addr|The prometheus metrics endpoint for job stats| 8088 enable-leader-election | Enable leader election for controller manager. Enabling this will ensure there is only one active controller manager. | false gang-scheduler-name | The name of gang scheduler, by default it is set to empty meaning not enalbing gang scheduling | "" max-reconciles | The number of max concurrent reconciles of each controller | 1
Project: StarRocks (App Definition and Development / Database)
File: ADMIN_CANCEL_REPAIR.md

displayed_sidebar: "English" This statement is used to cancel repairing specified tables or partitions with high priority. :::tip This operation requires the SYSTEM-level OPERATE privilege. You can follow the instructions in to grant this privilege. ::: ```sql ADMIN CANCEL REPAIR TABLE table_name[ PARTITION (p1,...)] ``` Note This statement only indicates that the system will no longer repair sharding replicas of specified tables or partitions with high priority. It still repairs these copies by default scheduling. Cancel high priority repair ```sql ADMIN CANCEL REPAIR TABLE tbl PARTITION(p1); ```
Project: YugabyteDB (App Definition and Development / Database)
File: create_operator,operator_option.grammar.md

```output.ebnf createoperator ::= CREATE OPERATOR operatorname ( { FUNCTION = subprogram_name | PROCEDURE = subprogram_name } [ , operator_option [ ... ] ] ) operatoroption ::= LEFTARG = lefttype | RIGHTARG = right_type | COMMUTATOR = com_op | NEGATOR = neg_op | RESTRICT = res_proc | JOIN = join_proc | HASHES | MERGES ```
Project: ClickHouse (App Definition and Development / Database)
File: v24.1.3.31-stable.md

sidebar_position: 1 sidebar_label: 2024 Backported in : Now dashboard understands both compressed and uncompressed state of URL's #hash (backward compatibility). Continuation of . (). Backported in : Added settings `splitpartsrangesintointersectingandnonintersectingfinal` and `splitintersectingpartsrangesintolayersfinal`. This settings are needed to disable optimizations for queries with `FINAL` and needed for debug only. (). Fix `ASTAlterCommand::formatImpl` in case of column specific settings (). Make MAX use the same rules as permutation for complex types (). Fix corner case when passing `updateinsertdeduplicationtokenindependentmaterialized_views` (). Fix incorrect result of arrayElement / map (). Fix crash in topK when merging empty states (). Maintain function alias in RewriteSumFunctionWithSumAndCountVisitor (). Fix leftPad / rightPad function with FixedString input (). NO CL ENTRY: 'Revert "Backport to 24.1: MergeTree FINAL optimization diagnostics and settings"'. (). Fix 02720rowpolicycolumnwith_dots (). Refactoring of dashboard state encoding (). MergeTree FINAL optimization diagnostics and settings (). Pin python dependencies in stateless tests ().
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.14.md

layout: release date: 2024-02-01 tag: v0.7.14 [chore] upgrade meshkit to v0.7.11 @MUzairS15 (#10144) [relationships] update selectors to represent correct path @MUzairS15 (#10103) [docs/mesheryctl] Fix annotations of exp command @theBeginner86 (#10113) [docs] Fix mesheryctl exp @theBeginner86 (#10112) [mesheryctl] Registry command init @theBeginner86 (#10053) [RTK] Settings - Reset database @senali-d (#10135) [RTK] Environments and Workspaces @senali-d (#10131) [chore] upgrade relay-compiler to 16.2.0 @MUzairS15 (#10127) [Bug] Transfer list component @senali-d (#10124) fix text case style in modal @sudhanshutech (#10123) Alter icon @sudhanshutech (#10121) Descriptive info inside tooltip @sudhanshutech (#10120) Prevent lossing technology in infoModal @Yashsharma1911 (#10098) Fix casing for displayName in publish payload @Yashsharma1911 (#10095) [Bug] Transfer list component @senali-d (#10124) [docs/mesheryctl] Fix annotations of exp command @theBeginner86 (#10113) Bump github.com/opencontainers/runc from 1.1.9 to 1.1.12 @dependabot (#10139) Update meshmap.yml @MUzairS15 (#10136) [CI] fixes E2E Test workflow. @singh1203 (#10114) Update integrations-updater.yml @theBeginner86 (#10097) Update integrations-updater.yml @theBeginner86 (#10096) [Docs] Components: remove source hyperlink @leecalcote (#10140) Add: Managing Events with Notification Center abstract @RipulHandoo (#10134) [Docs] Concepts: Logical policies @leecalcote (#10138) Redirects @vishalvivekm (#10132) readd-meshmodel-folder @vishalvivekm (#10129) add-redirect @vishalvivekm (#10115) [docs] Fix mesheryctl exp @theBeginner86 (#10112) docs fix quick start copy to clipboard button @ranjeetxsingh (#10100) [Docs] Relocate Contrib-Community location in TOC @leecalcote (#10093) Feature/add selectors documentation @RipulHandoo (#10035) [bug] Fix broken links for /concepts/<concept> to /concept/logical/<concept> @theBeginner86 (#10101) Thank you to our contributors for making this release possible: @MUzairS15, @RipulHandoo, @Yashsharma1911, @dependabot, @dependabot[bot], @iArchitSharma, @l5io, @leecalcote, @ranjeetxsingh, @senali-d, @singh1203, @sudhanshutech, @theBeginner86, @vishalvivekm and l5io
Project: ClickHouse (App Definition and Development / Database)
File: query_cache.md

slug: /en/operations/system-tables/query_cache Shows the content of the . Columns: `query` () Query string. `result_size` () Size of the query cache entry. `stale` () If the query cache entry is stale. `shared` () If the query cache entry is shared between multiple users. `compressed` () If the query cache entry is compressed. `expires_at` () When the query cache entry becomes stale. `key_hash` () A hash of the query string, used as a key to find query cache entries. Example ``` sql SELECT * FROM system.query_cache FORMAT Vertical; ``` ``` text Row 1: query: SELECT 1 SETTINGS usequerycache = 1 result_size: 128 stale: 0 shared: 0 compressed: 1 expires_at: 2023-10-13 13:35:45 key_hash: 12188185624808016954 1 row in set. Elapsed: 0.004 sec. ```
Project: ShardingSphere (App Definition and Development / Database)
File: show-sharding-table-rules-used-key-generator.en.md

+++ title = "SHOW SHARDING TABLE RULES USED KEY GENERATOR" weight = 11 +++ `SHOW SHARDING TABLE RULES USED ALGORITHM` syntax is used to query sharding rules used specified sharding key generator in specified logical database {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowShardingTableRulesUsedKeyGenerator::= 'SHOW' 'SHARDING' 'TABLE' 'RULES' 'USED' 'KEY' 'GENERATOR' keyGeneratorName ('FROM' databaseName)? keyGeneratorName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When databaseName is not specified, the default is the currently used DATABASE. If DATABASE is not used, No database selected will be prompted. | Columns | Descriptions | ||--| | type | Sharding rule type | | name | Sharding rule name | Query sharding table rules for the specified sharding key generator in spicified logical database ```sql SHOW SHARDING TABLE RULES USED KEY GENERATOR snowflakekeygenerator FROM sharding_db; ``` ```sql mysql> SHOW SHARDING TABLE RULES USED KEY GENERATOR snowflakekeygenerator FROM sharding_db; +-+--+ | type | name | +-+--+ | table | torderitem | +-+--+ 1 row in set (0.00 sec) ``` Query sharding table rules for specified sharding key generator in the current logical database ```sql SHOW SHARDING TABLE RULES USED KEY GENERATOR snowflakekeygenerator; ``` ```sql mysql> SHOW SHARDING TABLE RULES USED KEY GENERATOR snowflakekeygenerator; +-+--+ | type | name | +-+--+ | table | torderitem | +-+--+ 1 row in set (0.01 sec) ``` `SHOW`, `SHARDING`, `TABLE`, `USED`, `KEY`, `GENERATOR`, `FROM`
Project: KICS (Provisioning / Security & Compliance)
File: b69247e5-7e73-464e-ba74-ec9b715c6e12.md

title: User With Privilege Escalation By Actions 'lambda:UpdateFunctionCode' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b69247e5-7e73-464e-ba74-ec9b715c6e12 Query name: User With Privilege Escalation By Actions 'lambda:UpdateFunctionCode' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: User with privilege escalation by actions 'lambda:UpdateFunctionCode' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamuser" "cosmic" { name = "cosmic" } resource "awsiamuserpolicy" "testinline_policy" { name = "testinlinepolicy" user = awsiamuser.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "lambda:UpdateFunctionCode", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.cosmic.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: ClickHouse (App Definition and Development / Database)
File: groupbitxor.md

slug: /en/sql-reference/aggregate-functions/reference/groupbitxor sidebar_position: 127 Applies bit-wise `XOR` for series of numbers. ``` sql groupBitXor(expr) ``` Arguments `expr` An expression that results in `UInt` or `Int` type. Return value Value of the `UInt` or `Int` type. Example Test data: ``` text binary decimal 00101100 = 44 00011100 = 28 00001101 = 13 01010101 = 85 ``` Query: ``` sql SELECT groupBitXor(num) FROM t ``` Where `num` is the column with the test data. Result: ``` text binary decimal 01101000 = 104 ```