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

title: DROP OPERATOR statement [YSQL] headerTitle: DROP OPERATOR linkTitle: DROP OPERATOR description: Use the DROP OPERATOR statement to remove an operator. menu: v2.18: identifier: ddldropoperator parent: statements type: docs Use the `DROP OPERATOR` statement to remove an operator. {{%ebnf%}} drop_operator, operator_signature {{%/ebnf%}} See the semantics of each option in the . Basic example. ```plpgsql yugabyte=# CREATE OPERATOR @#@ ( rightarg = int8, procedure = numeric_fac ); yugabyte=# DROP OPERATOR @#@ (NONE, int8); ```
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-conf-mgmt-set-timezone.md

layout: global title: SET TIME ZONE displayTitle: SET TIME ZONE 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. The SET TIME ZONE command sets the time zone of the current session. ```sql SET TIME ZONE LOCAL SET TIME ZONE 'timezone_value' SET TIME ZONE INTERVAL interval_literal ``` LOCAL* Set the time zone to the one specified in the java `user.timezone` property, or to the environment variable `TZ` if `user.timezone` is undefined, or to the system time zone if both of them are undefined. timezone_value* The ID of session local timezone in the format of either region-based zone IDs or zone offsets. Region IDs must have the form 'area/city', such as 'America/Los_Angeles'. Zone offsets must be in the format '`(+|-)HH`', '`(+|-)HH:mm`' or '`(+|-)HH:mm:ss`', e.g '-08', '+01:00' or '-13:33:33'. Also, 'UTC' and 'Z' are supported as aliases of '+00:00'. Other short names are not recommended to use because they can be ambiguous. interval_literal* The represents the difference between the session time zone to the 'UTC'. It must be in the range of [-18, 18] hours and max to second precision, e.g. `INTERVAL 2 HOURS 30 MINUTES` or `INTERVAL '15:40:32' HOUR TO SECOND`. ```sql -- Set time zone to the system default. SET TIME ZONE LOCAL; -- Set time zone to the region-based zone ID. SET TIME ZONE 'America/Los_Angeles'; -- Set time zone to the Zone offset. SET TIME ZONE '+08:00'; -- Set time zone with intervals. SET TIME ZONE INTERVAL 1 HOUR 30 MINUTES; SET TIME ZONE INTERVAL '08:30:00' HOUR TO SECOND; ```
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-281.md

In function framework, when method throw an exception, it will trigger close function instance. If it is in the k8s environment, it will be restarted, you can use the class and extend it to quickly implement the push message model. It overrides the `read` method and provides the `consume` method for the user to call. However, if the source connector extends from the class, it cannot notify the function framework if it encounters an exception while consuming data internally, in other words, the function call `source.read()` never triggers an exception and never exits the process. Add `notifyError` method on PushSource, This method can receive an exception and put the exception in the queue. The next time an exception is `read`, will throws exception. ```java public Record<T> read() throws Exception { Record<T> record = queue.take(); if (record instanceof ErrorNotifierRecord) { throw ((ErrorNotifierRecord) record).getException(); } return record; } / Allows the source to notify errors asynchronously. @param ex */ public void notifyError(Exception ex) { consume(new ErrorNotifierRecord(ex)); } } ``` Just like the implementation of the current This PIP is to provide a method for users rather than introducing a new interface. So it is forward compatible However, connectors using this method are not backward compatible. For example, If a Kafka source connector built upon pulsar-io v3.1 (including features introduced in this PIP) and uses the `notifyError` method, when it switches back to pulsar-io v3.0 (excluding features introduced in this PIP), it will encounter errors during compilation. After this PIP, the source connectors can extends the `PushSource`, and use `notifyError` method to throw exception. Such as: etc. None Abstract BatchPushSource logic to AbstractPushSource. Let PushSource to extends AbstractPushSource to extend a new method(notifyError). Please refer this PR: https://github.com/apache/pulsar/pull/20791 None Not possible ```java public class PushSourceTest { PushSource testBatchSource = new PushSource() { @Override public void open(Map config, SourceContext context) throws Exception { } @Override public void close() throws Exception { } }; @Test(expectedExceptions = RuntimeException.class, expectedExceptionsMessageRegExp = "test exception") public void testNotifyErrors() throws Exception { testBatchSource.notifyError(new RuntimeException("test exception")); testBatchSource.readNext(); } } ``` None
Project: StarRocks (App Definition and Development / Database)
File: ALTER_VIEW.md

displayed_sidebar: "English" Modifies the definition of a view. ```sql ALTER VIEW [dbname.]viewname (column1) AS query_stmt ``` Note: View is logical, where the data isn't stored in the physical medium. The view will be used as a subquery in the statement when queried. Therefore, modifying the definition of views is equivalent to modifying query_stmt. query_stmt is arbitrarily supported SQL. Alter `exampleview` on `exampledb`. ```sql ALTER VIEW exampledb.exampleview ( c1 COMMENT "column 1", c2 COMMENT "column 2", c3 COMMENT "column 3" ) AS SELECT k1, k2, SUM(v1) FROM example_table GROUP BY k1, k2 ```
Project: FOSSA (Provisioning / Security & Compliance)
File: path-dependency.md

Path dependency is a dependency, which is sourced from filesystem, as opposed to a package manager registry or URL. A path dependency may or may not have transitive dependencies. Path dependency is also referred to as `local` or `vendor` dependency by some package managers. For example, in the following `go.mod` file, with `gomod` analysis and the `--experimental-analyze-path-dependencies` flag, `fossa-cli` would consider `../vendor/squirrel`, to be a path dependency. If path dependency analysis is disabled, `fossa-cli` would ignore this dependency completely and only show transitive dependencies originating from `../vendor/squirrel`. In such a case, license and copyright obligations originating from `../vendor/squirrel` will not be captured in FOSSA's findings, and subsequent software bill of materials generated. ```go // Example go.mod file module tester go 1.14 replace github.com/Masterminds/squirrel => ../vendor/squirrel require github.com/Masterminds/squirrel v1.4.0 ``` In the FOSSA UI, path dependencies are shown with the `Local` tag. Path dependencies are scanned using the "CLI license scan," similar to how are scanned by default. A "CLI license scan" performs a license scan at the path and uploads the results of these scans to the provided FOSSA endpoint. For performance reasons, the FOSSA service caches the results of a path dependency by the combination of its `(project id, path, hash of path's content)`. Due to this caching setup, it is normal for the first analysis to take some time, especially for larger projects, but future analyses of dependencies with the same information should be fast. In the event that caching is causing problems, FOSSA can be made to rescan this kind of dependency by: Running `fossa analyze` with the `--force-vendored-dependency-rescans` flag, or Setting `vendoredDependencies.forceRescans` to `true` in `.fossa.yml` at the root of the project. Currently, path dependencies do not support vulnerability scanning. Currently, path dependencies are only supported in: `golang` using the . PDM (Python) projects via the . Run `fossa analyze` with the `--experimental-analyze-path-dependencies` flag. By default, path dependency analysis is disabled. Note that, in the future, `fossa-cli` will enable path dependency analysis by default. `fossa-cli` only uploads the portions of the file that contain matches to licenses, not the entire file. If `cliLicenseScanRequireFullFileUpload` is enabled in FOSSA endpoint for your organization, `fossa-cli` will upload the full contents of any file that has licensing data. By default, `cliLicenseScanRequireFullFileUpload` is disabled for all organizations. Please contact to enable, this functionality. Path dependencies, unlike , can be either direct or transitive in the dependency graph. Furthermore, path dependencies are scoped to the project in FOSSA, as opposed to the entire organization.
Project: GreptimeDB (App Definition and Development / Database)
File: SECURITY.md

| Version | Supported | | - | | | >= v0.1.0 | :whitecheckmark: | | < v0.1.0 | :x: | We place great importance on the security of GreptimeDB code, software, and cloud platform. If you come across a security vulnerability in GreptimeDB, we kindly request that you inform us immediately. We will thoroughly investigate all valid reports and make every effort to resolve the issue promptly. To report any issues or vulnerabilities, please email us at info@greptime.com, rather than posting publicly on GitHub. Be sure to provide us with the version identifier as well as details on how the vulnerability can be exploited.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.24.md

RabbitMQ `3.11.24` is a maintenance release in the `3.11.x` . This release series . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Stream replication connections configured to use exclusively TLSv1.3 failed. GitHub issue: On startup, stream replicas will handle one more potential case of segment file corruption after an unclean shutdown. Contributed by @gomoripeti (CloudAMQP). GitHub issue: `default_policies..queue_pattern` definition in `rabbitmq.conf` was incorrectly parsed. Contributed by @SimonUnge (AWS). GitHub issue: Optimized stream index scans. Longer scans could result in some replicas stopping with a timeout. GitHub issue: Classic queue storage version is now a supported key for . Contributed by @SignalWhisperer (AWS). GitHub issue: Nodes now log boot time at info level instead of debug. This piece of information can be useful during root cause analysis. Contributed by @johanrhodin (CloudAMQP). GitHub issue: HTTP API request body size is now limited to 10 MiB by default. Two endpoints, one that accepts messages for publishing (note: publishing over the HTTP API is greatly discouraged) and another for , will now reject larger transfers with a `400 Bad Request` response. GitHub issue: `DELETE /api/queues/{vhost}/{name}` now can delete exclusive queues. GitHub issue: `osiris` has been upgraded to To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.24.tar.xz` instead of the source tarball produced by GitHub.
Project: MariaDB (App Definition and Development / Database)
File: pull_request_template.md

<!-- Thank you for contributing to the MariaDB Server repository! You can help us review your changes faster by filling in this template <3 If you have any questions related to MariaDB or you just want to hang out and meet other community members, please join us on https://mariadb.zulipchat.com/ . --> <!-- If you've already identified a https://jira.mariadb.org/ issue that seems to track this bug/feature, please add its number below. --> [x] The Jira issue number for this PR is: MDEV-______ <!-- An amazing description should answer some questions like: What problem is the patch trying to solve? If some output changed that is not visible in a test case, what was it looking like before the change and how it's looking with this patch applied? Do you think this patch might introduce side-effects in other parts of the server? --> TODO: fill description here TODO: What should the release notes say about this change? Include any changed system variables, status variables or behaviour. Optionally list any https://mariadb.com/kb/ pages that need changing. TODO: modify the automated test suite to verify that the PR causes MariaDB to behave as intended. Consult the documentation on . <!-- In many cases, this will be as simple as modifying one `.test` and one `.result` file in the `mysql-test/` subdirectory. Without automated tests, future regressions in the expected behavior can't be automatically detected and verified. --> If the changes are not amenable to automated testing, please explain why not and carefully describe how to test manually. <!-- Tick one of the following boxes [x] to help us understand if the base branch for the PR is correct. see for the latest versions. --> [ ] This is a new feature and the PR is based against the latest MariaDB development branch. [ ] This is a bug fix and the PR is based against the earliest maintained branch in which the bug can be reproduced. <!-- All code merged into the MariaDB codebase must meet a quality standard and codying style. Maintainers are happy to point out inconsistencies but in order to speed up the review and merge process we ask you to check the CODING standards. --> file and my PR conforms to this where appropriate. [ ] For any trivial modifications to the PR, I am ok with the reviewer making the changes themselves.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: packages.md

+++ title = "packages resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "packages" identifier = "inspec/resources/os/packages.md packages resource" parent = "inspec/resources/os" +++ Use the `packages` Chef InSpec audit resource to test the properties of multiple packages on the system. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.51.15 of InSpec. A `packages` resource block declares a regular expression search to select packages describe packages(/name/) do its('statuses') { should cmp 'installed' } end The `statuses` property tests if packages are installed on the system: its('statuses') { should cmp 'installed' } The `versions` property tests the versions of the packages installed on the system its('versions') { should cmp '3.4.0.2-4.el7' } The `architectures` property tests the architecture of packages installed on the system its('architectures') { should include 'i686' } The following examples show how to use this Chef InSpec audit resource. describe packages(/xserver/) do its('statuses') { should_not cmp 'installed' } end describe packages(/openssl/) do its('versions') { should cmp '1.0.1e-42.el7' } end describe packages(/libgcc/) do its('architectures') { should include 'x86_64' } its('architectures') { should include 'i686' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: StackRox (Provisioning / Security & Compliance)
File: 0000-adopt-adrs.md

Author(s): J. Victor Martins <jvdm@sdf.org> Created: [2023-08-23 Wed] Accepted. Currently, decisions about Stackrox Scanner are made using informal slack threads, ad-hoc discussions, and occasionally when the problem is considered complex, design documents. They are: Hard to Navigate: Finding discussions, decisions, and their context can sometimes be challenging. There is no decision log providing context on the implementation and design information. Opportunistic: Decisions might be made too fast without all relevant consideration. Overlooks Long-Term Impact: Quick decisions might only partially evaluate the long-term effects on the project. Lacks a Well-Defined Lifecycle: There's no structured review process to guarantee why a decision was accepted or rejected at the end. Unclear Boundaries: There's no clear framework to help us understand when the overhead of design documents is worth it. ADRs for long-term impact decisions: ADRs will be used to document decisions that have a long-term impact on the project. This process is considered more mature and reliable than other methods (e.g., slack threads). We will continue to use informal methods for trivial decisions. ADRs for smaller and larger decisions: ADRs can be used for smaller and larger decisions, whether public or not, depending on the context. Design docs to aid complex contexts: Design documents can be used when the context is ambiguous and requires an in-depth analysis of options available. ADRs will still be used to formally record the decision.[^1] ADRs are public and local by default: ADRs will be kept in a specific directory within the code repo to correlate decisions with code changes and make them widely available, even to external parties. The ADR will be stored in a private location when the context is sensitive (e.g., security, customer information). ADR template: ADRs will use a well-defined template. Additional overhead: ADRs are now required when a few slack threads would be OK. That creates some overhead to long-term discussions and decisions that did not exist before. Improved Clarity and Velocity: This approach will bring clear communication, faster onboarding time, a better context for discussions, and reduce unnecessary back-and-forths in other contexts (e.g., PR). Transparency and Accessibility: By making ADRs accessible, internal team members and external stakeholders will benefit from increased visibility into the decision-making process. Flexibility between ADRs and Design Docs: A better understanding of when a design document will add value, providing flexibility to adapt to the evaluated problem. Public vs. Private: Private ADRs need to exist when the decision is sensitive to happen in public. Even though the number of private decisions will be significantly lower, having two ADR locations will still be painful.
Project: Meshery (Provisioning / Automation & Configuration)
File: database.md

layout: default title: Database permalink: concepts/architecture/database type: components redirect_from: architecture/database abstract: "Meshery offers support for internal caching with the help of file databases. This has been implemented with several libraries that supports different kinds of data formats." language: en list: include Meshery Databases function as repositories for , user preferences and system settings. Both databases are considered ephemeral and should be treated as caches. Data retention is tethered to the lifetime of their Meshery Server instance. may offer long-term data persistence. Meshery's APIs offer mechanisms for clients, like and Meshery UI to retrieve data. See the figure below for additional details of the data formats supported and type of data stored. ]({{ site.baseurl }}/assets/img/architecture/meshery-database.svg) Meshery Database has several kinds of database implementations to support various usecases. They are listed below: {% assign sorted = site.adapters | sort: "project_status" | reverse %} | Component | Library | | :- | : | | Bitcask | git.mills.io/prologic/bitcask | | SQLite | gorm.io/gorm, gorm.io/driver/sqlite |
Project: APIClarity (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' 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: YugabyteDB (App Definition and Development / Database)
File: deletedb.md

title: DELETEDB linkTitle: DELETEDB description: DELETEDB menu: preview: parent: api-yedis weight: 2034 aliases: /preview/api/yedis/deletedb type: docs `DELETEDB` is used to delete a yedis database that is no longer needed. A client can issue the `DELETEDB` command through the redis-cli. Returns a status string upon success. ```sh $ LISTDB ``` ``` 1) "0" ``` ```sh $ CREATEDB "second" ``` ``` "OK" ``` ```sh $ CREATEDB "3.0" ``` ``` "OK" ``` ```sh $ LISTDB ``` ``` 1) "0" 2) "3.0" 3) "second" ``` ```sh $ DELETEDB "3.0" ``` ``` "OK" ``` ```sh $ LISTDB ``` ``` 1) "0" 2) "second" ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: 2.11.0.md

lagoon lagoon-ui lagoon-build-deploy lagoon-core chart You must upgrade to Lagoon v2.10.x before upgrading to v2.11.0. Ensure you read all the linked . Ensure you have a local backup of the api-db and keycloak-db before you commence this update, as there are complex migrations taking place in preparation for the v2.12.0 release. The storage-calculator service was removed from core in this release, and the service is now included in lagoon-remote.
Project: ShardingSphere (App Definition and Development / Database)
File: unsupported.en.md

+++ title = "Unsupported Items" weight = 6 +++ Do not support timeout related operations Do not support operations of stored procedure, function and cursor Do not support native SQL Do not support savepoint related operations Do not support Schema/Catalog operation Do not support self-defined type mapping Do not support statements that return multiple result sets (stored procedures, multiple pieces of non-SELECT data) Do not support the operation of international characters Do not support getting result set pointer position Do not support changing result pointer position through none-next method Do not support revising the content of result set Do not support acquiring international characters Do not support getting Array Do not support new functions of JDBC 4.1 interface For all the unsupported methods, please read `org.apache.shardingsphere.driver.jdbc.unsupported` package.
Project: StarRocks (App Definition and Development / Database)
File: host_name.md

displayed_sidebar: "English" Obtains the hostname of the node on which the computation is performed. ```Haskell host_name(); ``` None Returns a VARCHAR value. ```Plaintext select host_name(); +-+ | host_name() | +-+ | sandbox-sql | +-+ 1 row in set (0.01 sec) ```
Project: CloudTTY (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.