cwielenb/CNCF-Dataset huggingface dataset:
Project: TiDB (App Definition and Development / Database)
File: 2018-12-11-sql-plan-management.md

Author(s): Last updated: 2018-12-11 Discussion at: This proposal aims to support the SQL plan management. With the help of it, we can force the optimizer to choose a certain plan without modifying the SQL text. The optimizer chooses a plan based on several environmental factors, such as statistics, optimizer parameters, schema definitions and so on. Once the environment changes, we cannot guarantee that the newly optimized plan is always better than the old plan. Therefore we need to provide ways to bind the plan for applications that cannot take the risk of a changed plan. The following proposal mainly focuses on two parts: how to bind the plan and what is the syntax to manage it. In order to bind the plan, we need to maintain a mapping from normalized SQL text to plan. To normalize the SQL text, we can remove all the blank space, replace the parameters with placement markers, and convert remaining parts to lower cases. The most difficult problem is how we represent and store the plan. One way to represent the plan is using the optimized physical plan. However, it is difficult to perform the parameters replacement for later SQLs, because some parameters may already be rewritten in the optimized physical plan when doing logical and physical optimizations. Since the parameters replacement is hard, it is better not doing it. Another way to represent the plan is using the AST of hinted SQL, so the only thing needs to do for later SQLs is to traverse the AST and copy hints. To manage the SQL bindings, we need to support basic operations like create, show and drop. We can also support SQL bindings that only exist in the current session. The syntax will be like the following: CREATE [GLOBAL|SESSION] BINDING_NAME BINDING FOR `SQL` USING `HINTED SQL` DROP [GLOBAL|SESSION] BINDINGS DROP [GLOBAL|SESSION] BINDING BINDING_NAME SHOW [GLOBAL|SESSION] BINDINGS [SHOWLIKEOR_WHERE] In Oracle, they only store the hints of the optimized query, instead of the whole AST. For TiDB, it requires more work to do it now because we need to generate unique identifiers for the subqueries and lift all hints to the outer most queries. Storing the AST is the simplest way now. MySQL does not support SQL plan management, so this will add syntaxes that not supported by MySQL. To implement it, we need the following main steps: Normalize the SQL text. We can take this https://github.com/pingcap/parser/pull/32 as an example. Support the syntax in the parser. Store the binding SQL and AST of the hinted SQL in a system table. Since there is a unique mapping from SQL text to AST, we can just store the SQL and parse it to AST for later use. A background goroutine will check if there are new bindings and update the local cache. When another SQL comes, we first check if there is a matched SQL in the cache. If so, we can traverse the AST to add hints. Since comparing text for every SQL may affect unrelated SQLs a lot, we can calculate a hash value and first check if there is matching hash values.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.19.0.md

fix: changed directory name from testdir to shifudemos by @SuperAayush in https://github.com/Edgenesis/shifu/pull/604 bump sigs.k8s.io/controller-runtime to v0.15.0 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/608 bump kind to v0.19.0, Kubernetes to v1.27.1 in demo by @tomqin93 in https://github.com/Edgenesis/shifu/pull/610 @SuperAayush made their first contribution in https://github.com/Edgenesis/shifu/pull/604 Bump golang.org/x/net from 0.9.0 to 0.10.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/600 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.18.0...v0.19.0
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-04-2022-11-47-10_3c92d085.md

timestamp: "2022-10-04 11:47:23 UTC Tue" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.10" k8s-distro: minikube k8s-version: "v1.23.9" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

Please describe the big picture of your changes here to communicate to the RabbitMQ team why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. A pull request that doesn't explain why the change was made has a much lower chance of being accepted. What types of changes does your code introduce to this project? Put an `x` in the boxes that apply [ ] Bug fix (non-breaking change which fixes issue #NNNN) [ ] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems) [ ] Documentation improvements (corrections, new content, etc) [ ] Cosmetic change (whitespace, formatting, etc) [ ] Build system and/or CI _Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask on the mailing list. We're here to help! This is simply a reminder of what we are going to look for before merging your code._ [ ] I have read the `CONTRIBUTING.md` document [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq) [ ] I have added tests that prove my fix is effective or that my feature works [ ] All tests pass locally with my changes [ ] If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website [ ] If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.
Project: YugabyteDB (App Definition and Development / Database)
File: txn_end.md

title: END statement [YSQL] headerTitle: END linkTitle: END description: Use the `END` statement to commit the current transaction. menu: v2.18: identifier: txn_end parent: statements type: docs Use the `END` statement to commit the current transaction. All changes made by the transaction become visible to others and are guaranteed to be durable if a crash occurs. {{%ebnf%}} end {{%/ebnf%}} ```sql END [ TRANSACTION | WORK ] ``` Add optional keyword has no effect. Add optional keyword has no effect.
Project: YugabyteDB (App Definition and Development / Database)
File: nutanix-ahv.md

title: Nutanix AHV linkTitle: Nutanix AHV description: Use Nutanix AHV with YugabyteDB and YugabyteDB Anywhere menu: preview_integrations: identifier: nutanix-ahv parent: integrations-platforms weight: 571 type: docs is a modern and secure virtualization platform that powers VMs and containers for applications and cloud-native workloads on-premises and in public clouds. The following steps describe how to deploy YugabyteDB Anywhere (YBA) and YugabyteDB using Nutanix AHV VMs: Choose an operating system from the for deploying YugabyteDB. on Nutanix Prism with Network Interface Controller (NIC). on the AHV VMs. to the AHV VMs. Install YBA software using . Create an . Create additional to act as on-premises database nodes. Configure . database VMs. Create an . {{< note title="Tip" >}} For high availability, create an on the Prism side that hosts AHV nodes (database nodes) on separate controller VMs. {{< /note >}}
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_logging_organization_log_sink.md

+++ title = "googleloggingorganizationlogsink resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleloggingorganizationlogsink" identifier = "inspec/resources/gcp/googleloggingorganizationlogsink.md googleloggingorganizationlogsink resource" parent = "inspec/resources/gcp" +++ A `googleloggingorganizationlogsink` is used to test a Google OrganizationLogSink resource ```ruby describe googleloggingorganizationlogsink(organization: '190694428152', name: 'inspec-gcp-org-sink') do it { should exist } its('filter') { should cmp 'resource.type = gce_instance' } end describe googleloggingorganizationlogsink(organization: '190694428152', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googleloggingorganizationlogsink` resource: `organization` : Id of the organization that this sink belongs to. `name` : Name of the log sink. `filter` : An advanced logs filter. The only exported log entries are those that are in the resource owning the sink and that match the filter. `destination` : The export destination. `writer_identity` : An IAM identitya service account or groupunder which Logging writes the exported log entries to the sink's destination. This field is set by sinks.create and sinks.update based on the value of uniqueWriterIdentity in those methods. `include_children` : If the field is false, the default, only the logs owned by the sink's parent resource are available for export. If the field is true, then logs from all the projects, folders, and billing accounts contained in the sink's parent resource are also available for export. Whether a particular log entry from the children is exported depends on the sink's filter expression. Ensure the is enabled for the current project.
Project: ArangoDB (App Definition and Development / Database)
File: throw_bad_result_access.md

+++ title = "`throwbadresult_access<EC>`" description = "Policy class defining that `badresultaccess_with<EC>` should be thrown on incorrect wide value observation. Inherits publicly from `base`." +++ Policy class defining that {{% api "badresultaccesswith<EC>" %}} should be thrown on incorrect wide value observation. The primary purpose of this policy is to enable standing in for {{% api "std::expected<T, E>" %}} which throws a `badexpectedaccess<E>` on incorrect wide value observation. This is why it is only ever `EC` which is thrown with `badresultaccesswith<EC>` on value observation only, and only when there is an error available. If used in `basic_outcome`, and the outcome is exceptioned and so no error is available, incorrect wide value observation performs instead: ```c++ BOOSTOUTCOMETHROWEXCEPTION(badresult_access("no value")); ``` Incorrect wide error observation performs: ```c++ BOOSTOUTCOMETHROWEXCEPTION(badresult_access("no error")); ``` Incorrect wide exception observation performs: ```c++ BOOSTOUTCOMETHROWEXCEPTION(badoutcome_access("no exception")); ``` Inherits publicly from {{% api "base" %}}, and its narrow value, error and exception observer policies are inherited from there. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::policy` Header: `<boost/outcome/policy/throwbadresult_access.hpp>`
Project: Harbor (Provisioning / Container Registry)
File: 2-33-admin-role-delete-images.md

Test 2-33 - Admin Role User Delete Images (DB Mode) ======= To verify that a user with system admin role can delete images owned by other users when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least tow non-admin users. NOTE: The below non-admin user M should NOT be the same as the non-admin user in Test 2-23. Assign an non-admin user M with system admin role and act as an admin user. Repeat all steps in Test 2-23. A user with system admin role can perform all operations the same as the admin user. Same as Test 2-23. None
Project: KICS (Provisioning / Security & Compliance)
File: 15e6ad8c-f420-49a6-bafb-074f5eb1ec74.md

title: Group With Privilege Escalation By Actions 'ec2:RunInstances' And 'iam:PassRole' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 15e6ad8c-f420-49a6-bafb-074f5eb1ec74 Query name: Group With Privilege Escalation By Actions 'ec2:RunInstances' And 'iam:PassRole' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'ec2:RunInstances' and 'iam:PassRole' 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 "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:RunInstances", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" groups = [awsiamgroup.cosmic.name] policyarn = awsiam_policy.policy.arn } resource "awsiampolicy" "policy" { name = "test-policy" description = "A test policy" policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PassRole", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```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: YugabyteDB (App Definition and Development / Database)
File: pgmigrate.md

title: Use PGmigrate with YugabyteDB YSQL headerTitle: PGmigrate linkTitle: PGmigrate description: Use PGmigrate to work with distributed SQL databases in YugabyteDB. menu: preview_integrations: identifier: pgmigrate parent: data-migration weight: 571 type: docs is a database migration tool with following key features: Transactional and non-transactional migrations. Callbacks: You can run some DDL on specific steps of the migration process (for example, drop some code before executing migrations, and create it back after migrations were applied). Online migrations: You can execute series of transactional migrations and callbacks in a single transaction. So, if something goes wrong, a basic ROLLBACK will bring back the transaction to a consistent state. Because YugabyteDB's YSQL API is wire-compatible with PostgreSQL, PGmigrate can connect to YugabyteDB just like with PostgreSQL. To run the , do the following: Start a YugabyteDB cluster. Refer to . Use the following configuration file for PGmigrate: ```properties callbacks: beforeAll: callbacks/beforeAll beforeEach: callbacks/beforeEach afterEach: callbacks/afterEach afterAll: callbacks/afterAll grants conn: host=ybtserverip dbname=foodb user=yugabyte password=yugabyte port=5433 ``` Proceed with the tutorial using the preceding configuration.
Project: Vitess (App Definition and Development / Database)
File: release_notes.md

Restore: Check disableactivereparents properly before waiting for position update #8114 Fix informationschema query with system schema in tableschema filter #8095 Fix for issue with information_schema queries with both table name and schema name predicates #8096 Fix for transactions not allowed to finish during PlannedReparentShard #8098 PRIMARY in index hint list #8158 Release 9.0.1 #8065 9.0.0: update release notes with known issue #8080 #8082 Added release script to the makefile #8182 Update do_release to work in the 9.0 branch #8184 Revert "backup: Use pargzip instead of pgzip for compression." #8174 The release includes 17 commits (excluding merges) Thanks to all our contributors: @GuptaManan100, @deepthi, @Harshit, @rafael, @systay
Project: Harbor (Provisioning / Container Registry)
File: 2-13-LDAP-user-push-multiple-projects.md

Test 2-13 - User Create Multiple Projects (LDAP Mode) ======= To verify that a non-admin user can create multiple projects in LDAP mode. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. A linux host with Docker CLI installed (Docker client). At least a non-admin user. Same as Test 2-03 except that users are from LDAP/AD. Same as Test 2-03. None
Project: ArangoDB (App Definition and Development / Database)
File: result_print.md

+++ title = "`std::string print(const basic_result<T, E, NoValuePolicy> &)`" description = "Returns a string containing a human readable rendition of the `basic_result`." +++ Returns a string containing a human readable rendition of the `basic_result`. Overridable: Not overridable. Requires: Always available. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/iostream_support.hpp>` (must be explicitly included manually).
Project: external-secrets (Provisioning / Security & Compliance)
File: pushsecret.md

The `PushSecret` is namespaced and it describes what data should be pushed to the secret provider. tells the operator what secrets should be pushed by using `spec.selector`. you can specify what secret keys should be pushed by using `spec.data`. you can also template the resulting property values using . ``` yaml {% include 'full-pushsecret.yaml' %} ``` When the controller reconciles the `PushSecret` it will use the `spec.template` as a blueprint to construct a new property. You can use golang templates to define the blueprint and use template functions to transform the defined properties. You can also pull in `ConfigMaps` that contain golang-template data using `templateFrom`. See for details.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.45.md

layout: release date: 2024-04-06 tag: v0.7.45 feat: Relationship cmd @RipulHandoo (#10640) Thank you to our contributors for making this release possible: @MUzairS15, @RipulHandoo, @aabidsofi19 and @leecalcote
Project: YugabyteDB (App Definition and Development / Database)
File: DUMP_FORMAT.md

The version 1 RocksDB dump format is fairly simple: 1) The dump starts with the magic 8 byte identifier "ROCKDUMP" 2) The magic is followed by an 8 byte big-endian version which is 0x00000001. 3) Next are arbitrarily sized chunks of bytes prepended by 4 byte little endian number indicating how large each chunk is. 4) The first chunk is special and is a json string indicating some things about the creation of this dump. It contains the following keys: database-path: The path of the database this dump was created from. hostname: The hostname of the machine where the dump was created. creation-time: Unix seconds since epoc when this dump was created. 5) Following the info dump the slices paired into are key/value pairs.
Project: KICS (Provisioning / Security & Compliance)
File: 295acb63-9246-4b21-b441-7c1f1fb62dc0.md

title: Missing Dnf Clean All hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 295acb63-9246-4b21-b441-7c1f1fb62dc0 Query name: Missing Dnf Clean All Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Cached package data should be cleaned after installation to reduce image size<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="2" FROM fedora:27 RUN set -uex && \ dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo && \ sed -i 's/\$releasever/26/g' /etc/yum.repos.d/docker-ce.repo && \ dnf install -vy docker-ce HEALTHCHECK CMD curl --fail http://localhost:3000 || exit 1 ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM fedora:27 RUN set -uex && \ dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo && \ sed -i 's/\$releasever/26/g' /etc/yum.repos.d/docker-ce.repo && \ dnf install -vy docker-ce && \ dnf clean all HEALTHCHECK CMD curl --fail http://localhost:3000 || exit 1 ``` ```dockerfile title="Negative test num. 2 - dockerfile file" FROM golang:1.16 AS builder WORKDIR /go/src/github.com/foo/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go ./ RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app . RUN set -uex && \ dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo && \ sed -i 's/\$releasever/26/g' /etc/yum.repos.d/docker-ce.repo && \ dnf install -vy docker-ce FROM alpine:latest RUN apk --no-cache add ca-certificates WORKDIR /root/ COPY --from=builder /go/src/github.com/foo/href-counter/app ./ CMD ["./app"] RUN useradd -ms /bin/bash patrick USER patrick ```
Project: NebulaGraph (App Definition and Development / Database)
File: feature_request.md

name: Feature Request about: Suggest a feature for this project. title: '' labels: type/feature req assignees: '' Is your feature request related to a problem? Please describe. <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> Describe the solution you'd like <!-- A clear and concise description of what you want to happen. --> Describe alternatives you've considered <!-- A clear and concise description of any alternative solutions or features you've considered. --> Additional context <!-- Add any other context or screenshots about the feature request here. -->
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.0.0.md

id: v1.0.0 title: v1.0.0 description: Backstage Release v1.0.0 These are the release notes for the v1.0.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. Several packages have reached version 1.0, you can read more about the effect of this in our . The default SQLite3 driver has been switched to , as many users were running into issues with installation of `@vscode/sqlite3`. The new `@backstage/plugin-gcalendar` plugin provides a home page widget that shows your Google Calendar events. Contributed by () The scaffolder page now provides a editor and preview page for templates, where you can see a live preview of the template form. The preview page can be found under the `/preview` sub route, typically at `/create/preview`. Contributed by () The following packages have been renamed, be sure to update your usage: `@backstage/search-common` -> `@backstage/plugin-search-common` `@backstage/techdocs-common` -> `@backstage/plugin-techdocs-node` This release does not contain any security fixes. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support for this release Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.