cwielenb/CNCF-Dataset huggingface dataset:
Project: Gradle Build Tool (App Definition and Development / Application Definition & Image Build)
File: Development.md

This is a collection of best practices for Gradle implementation. Should and should not do's. Traditionally, if an error occurred, the error message and the possible solution were provided to the console via a single String in the corresponding exception. That meant possible solutions for Problems could be scattered all over the console output. To improve the user experience, we introduced a new way to provide suggestions. The idea is to provide a list of suggestions for a problem in the console output. The suggestions are displayed in the separate "Try"- section of the console output. The suggestions are collected in the `BuildExceptionReporter` and printed to the console. In some cases, you still want to keep the old behavior and display the suggestions in the error message. To add a custom suggestion in the "Try" section of the console output, your exception needs to implement the `ResolutionProvider` interface. That should be it. The suggestion will be displayed in the "Try" section. For some scenarios, it doesn't make sense to display all the generic suggestions we currently have. E.g. `--stacktrace` for a compilation error is not helpful. To influence the generic suggestions Gradle displays, the NonGradleCause interface was introduced. If an exception implements this interface, Gradle will not display the `--stacktrace` option. Another more targeted interface is `CompilationFailedIndicator`. This interface is used to indicate that the exception is caused by a compilation failure. This will not show the `--stacktrace` option, but it will show the `--info` option since this can help with parameters passed to the compiler.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-where.md

layout: global title: SELECT displayTitle: WHERE clause 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 `WHERE` clause is used to limit the results of the `FROM` clause of a query or a subquery based on the specified condition. ```sql WHERE boolean_expression ``` boolean_expression* Specifies any expression that evaluates to a result type `boolean`. Two or more expressions may be combined together using the logical operators ( `AND`, `OR` ). ```sql CREATE TABLE person (id INT, name STRING, age INT); INSERT INTO person VALUES (100, 'John', 30), (200, 'Mary', NULL), (300, 'Mike', 80), (400, 'Dan', 50); -- Comparison operator in `WHERE` clause. SELECT * FROM person WHERE id > 200 ORDER BY id; ++-++ | id|name|age| ++-++ |300|Mike| 80| |400| Dan| 50| ++-++ -- Comparison and logical operators in `WHERE` clause. SELECT * FROM person WHERE id = 200 OR id = 300 ORDER BY id; ++-+-+ | id|name| age| ++-+-+ |200|Mary|null| |300|Mike| 80| ++-+-+ -- IS NULL expression in `WHERE` clause. SELECT * FROM person WHERE id > 300 OR age IS NULL ORDER BY id; ++-+-+ | id|name| age| ++-+-+ |200|Mary|null| |400| Dan| 50| ++-+-+ -- Function expression in `WHERE` clause. SELECT * FROM person WHERE length(name) > 3 ORDER BY id; ++-+-+ | id|name| age| ++-+-+ |100|John| 30| |200|Mary|null| |300|Mike| 80| ++-+-+ -- `BETWEEN` expression in `WHERE` clause. SELECT * FROM person WHERE id BETWEEN 200 AND 300 ORDER BY id; ++-+-+ | id|name| age| ++-+-+ |200|Mary|null| |300|Mike| 80| ++-+-+ -- Scalar Subquery in `WHERE` clause. SELECT * FROM person WHERE age > (SELECT avg(age) FROM person); ++-++ | id|name|age| ++-++ |300|Mike| 80| ++-++ -- Correlated Subquery in `WHERE` clause. SELECT * FROM person AS parent WHERE EXISTS ( SELECT 1 FROM person AS child WHERE parent.id = child.id AND child.age IS NULL ); ++-+-+ |id |name|age | ++-+-+ |200|Mary|null| ++-+-+ ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2023-02-26-10_69667807.md

timestamp: "2023-10-12 02:25:43 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.23.9" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: userver (App Definition and Development / Streaming & Messaging)
File: lru_cache.md

A Least Recently Used (LRU) Cache organizes items in order of use. It drops items not used for the longest amount of time in favor of caching new items. There are also expirable LRU caches that drop expired records and may prolong record lifetime on usage. To implement those caches userver provides a base component class cache::LruCacheComponent that manages an instance of cache::ExpirableLruCache. LRU cache is useful for reducing the network interactions while working with data that does not fit into service memory and rarely changes. Examples: caching user ids by their emails caching localized strings by their ids Expirable LRU cache is useful for reducing the network interactions while working with data does not fit into service memory and changes in predetermined intervals. Examples: caching tokens that expire in an hour caching road average traffic situation for an area for a few minutes caching cab rating for a median travel time Using cache::LruCacheComponent is quite straightforward. Write a component that derives from it: @snippet cache/lrucachecomponentbasetest.hpp Sample lru cache component After that, get the component using the components::ComponentContext::FindComponent() and call cache::LruCacheComponent::GetCache(). Use the returned cache::LruCacheWrapper. cache::LruCacheComponent should be your choice by default for implementing all the LRU caches. However, in some cases there is a need to avoid using the @ref scripts/docs/en/userver/component_system.md "component system", or to avoid synchronization, or to control the expiration logic more precisely. Here's a brief introduction into LRU types: Concurrency-safe expirable component cache::LruCacheComponent. Call cache::LruCacheComponent::GetCache() to get a cache::LruCacheWrapper that provides actual interface to work with the cache. Concurrency-safe expirable cache::LruCacheWrapper is a smart pointer that provides simplified interface to the cache::ExpirableLruCache. Concurrency-safe expirable container cache::ExpirableLruCache with precise control over the expiration logic. Concurrency-safe non-expirable container cache::NWayLRU. Non-expirable container cache::LruMap that provides the same concurrency guarantees as the standard library containers. Non-expirable cache::LruSet that provides the same concurrency guarantees as the standard library containers. @htmlonly <div class="bottom-nav"> @endhtmlonly @ref pgcache | @ref pgdriver @htmlonly </div> @endhtmlonly
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_restore.md

title: "Command - devspace restore" sidebar_label: devspace restore Restore configuration ``` ``` ``` -h, --help help for restore ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: Plural (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

We take security very seriously at Plural, we welcome any review of our open source code to ensure no application or infrastructure deployed by Plural is compromised. In order to give the community time to respond and upgrade we strongly urge you report all security issues privately. Please use our to provide details and repro steps and we will respond ASAP. If you prefer not to use Hacker One, email us directly at `support@plural.sh` with details and repro steps. Security issues always take precedence over bug fixes and feature work. We can and do mark releases as "urgent" if they contain serious security fixes. Plural uses Argon2 for password hashing. This has been proven to be the most robust hashing algorithm. Plural stores some user provided secrets in postgres. These are symmetrically encrypted using AES-256 Plural's frontend communicates with its server-side exclusively using a gql api, with authentication managed by a hmac signed jwt. Details on how that works can be found in the guardian configuration in `apps/core`
Project: Rundeck (Provisioning / Automation & Configuration)
File: pull_request_template.md

<!-- IMPORTANT: Before submitting your Pull Request, please review the following instructions: Please follow the document. Are you implementing a feature or enhancement? Please search the existing Issues and look at the for your idea before posting. If your enhancement is not listed, it is better to and get feedback from maintainers and the community before submitting an Pull request to implement it. Please be sure the issue you are addressing is referenced in a commit, or the body of your PR, using , e.g. "fixes #123". --> Is this a bugfix, or an enhancement? Please describe. <!-- Include a clear and concise description of the bug you are fixing (reference issue number), or enhancement you are implementing. --> Describe the solution you've implemented <!-- 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 change here. -->
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_remove_deployment.md

title: "Command - devspace remove deployment" sidebar_label: devspace remove deployment Removes one or all deployments from devspace configuration ``` devspace remove deployment [deployment-name] [flags] ``` ``` Removes one or all deployments from the devspace configuration (If you want to delete the deployed resources, run 'devspace purge -d deployment_name'): devspace remove deployment devspace-default devspace remove deployment --all ``` ``` --all Remove all deployments -h, --help help for deployment ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: external-secrets (Provisioning / Security & Compliance)
File: feature_request.md

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

id: overview title: "Developing on Apache Druid" sidebar_label: "Developing on Druid" <!-- ~ 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. --> Druid's codebase consists of several major components. For developers interested in learning the code, this document provides a high level overview of the main components that make up Druid and the relevant classes to start from to learn the code. Data in Druid is stored in a custom column format known as a . Segments are composed of different types of columns. `Column.java` and the classes that extend it is a great place to looking into the storage format. Raw data is ingested in `IncrementalIndex.java`, and segments are created in `IndexMerger.java`. Druid segments are memory mapped in `IndexIO.java` to be exposed for querying. Most of the logic related to Druid queries can be found in the Query* classes. Druid leverages query runners to run queries. Query runners often embed other query runners and each query runner adds on a layer of logic. A good starting point to trace the query logic is to start from `QueryResource.java`. Most of the coordination logic for Historical processes is on the Druid Coordinator. The starting point here is `DruidCoordinator.java`. Most of the coordination logic for (real-time) ingestion is in the Druid indexing service. The starting point here is `OverlordResource.java`. Druid loads data through `FirehoseFactory.java` classes. Firehoses often wrap other firehoses, where, similar to the design of the query runners, each firehose adds a layer of logic, and the persist and hand-off logic is in `RealtimePlumber.java`. The two main Hadoop indexing classes are `HadoopDruidDetermineConfigurationJob.java` for the job to determine how many Druid segments to create, and `HadoopDruidIndexerJob.java`, which creates Druid segments. At some point in the future, we may move the Hadoop ingestion code out of core Druid. Druid currently has two internal UIs. One is for the Coordinator and one is for the Overlord. At some point in the future, we will likely move the internal UI code out of core Druid. We welcome contributions for new client libraries to interact with Druid. See the page for links to existing client libraries.
Project: Percona Server for MySQL (App Definition and Development / Database)
File: Bazel.md

To use libcbor in your project, first add the following section to your project's `WORKSPACE` file. Note the location of the `third_party/libcbor.BUILD` file - you may use a different location if you wish, but you the file must be make available to `WORKSPACE`. Note, this imports version `0.8.0` - you may need to update the version and the sha256 hash. ```python http_archive( name = "libcbor", buildfile = "//thirdparty:libcbor.BUILD", sha256 = "dd04ea1a7df484217058d389e027e7a0143a4f245aa18a9f89a5dd3e1a4fcc9a", strip_prefix = "libcbor-0.8.0", urls = ["https://github.com/PJK/libcbor/archive/refs/tags/v0.8.0.zip"], ) ``` Bazel will unzip the libcbor zip file, then copy this file in as `BUILD`. Bazel will then use this file to compile libcbor. is used in two passes: to create the Makefiles, and then to invoke Make to build the `libcbor.a` static library. `libcbor.a` and the `.h` files are then made available for other packages to use. ```python genrule( name = "cbor_cmake", srcs = glob([""]), outs = ["libcbor.a", "cbor.h", "cbor/arrays.h", "cbor/bytestrings.h", "cbor/callbacks.h", "cbor/cbor_export.h", "cbor/common.h", "cbor/configuration.h", "cbor/data.h", "cbor/encoding.h", "cbor/floats_ctrls.h", "cbor/ints.h", "cbor/maps.h", "cbor/serialization.h", "cbor/streaming.h", "cbor/strings.h", "cbor/tags.h"], cmd = " && ".join([ "INITIAL_WD=`pwd`", "cd `dirname $(location CMakeLists.txt)`", "cmake -DCMAKEBUILDTYPE=Release .", "cmake --build .", "cp src/libcbor.a src/cbor.h $$INITIAL_WD/$(RULEDIR)", "cp src/cbor/*h cbor/configuration.h $$INITIAL_WD/$(RULEDIR)/cbor"]), visibility = ["//visibility:private"], ) cc_import( name = "cbor", hdrs = ["cbor.h", "cbor/arrays.h", "cbor/bytestrings.h", "cbor/callbacks.h", "cbor/cbor_export.h", "cbor/common.h", "cbor/configuration.h", "cbor/data.h", "cbor/encoding.h", "cbor/floats_ctrls.h", "cbor/ints.h", "cbor/maps.h", "cbor/serialization.h", "cbor/streaming.h", "cbor/strings.h", "cbor/tags.h"], static_library = "libcbor.a", visibility = ["//visibility:public"], ) ``` The `libcbor.BUILD` file must be make available to the top-level `WORKSPACE` file: ```python exports_files(["libcbor.BUILD"])) ``` Add libcbor dependency to your package's `BUILD` file like so: ```python cc_library( name = "...", srcs = [ ... ], hdrs = [ ... ], deps = [ ... "@libcbor//:cbor", ], ) ``` Now you may simply include `cbor.h`: ```c static const uint8t version = cbormajor_version; ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.3.15.33-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fixed backward incompatibility in (de)serialization of states of `min`, `max`, `any`, `argMin`, `argMax` aggregate functions with `String` argument. The incompatibility was introduced in https://github.com/ClickHouse/ClickHouse/pull/41431 and affects 22.9, 22.10 and 22.11 branches (fixed since 22.9.6, 22.10.4 and 22.11.2 correspondingly). Some minor releases of 22.3, 22.7 and 22.8 branches are also affected: 22.3.13...22.3.14 (fixed since 22.3.15), 22.8.6...22.8.9 (fixed since 22.8.10), 22.7.6 and newer (will not be fixed in 22.7, we recommend to upgrade from 22.7.* to 22.8.10 or newer). This release note does not concern users that have never used affected versions. Incompatible versions append extra `'\0'` to strings when reading states of the aggregate functions mentioned above. For example, if an older version saved state of `anyState('foobar')` to `statecolumn` then incompatible version will print `'foobar\0'` on `anyMerge(statecolumn)`. Also incompatible versions write states of the aggregate functions without trailing `'\0'`. Newer versions (that have the fix) can correctly read data written by all versions including incompatible versions, except one corner case. If an incompatible version saved a state with a string that actually ends with null character, then newer version will trim trailing `'\0'` when reading state of affected aggregate function. For example, if an incompatible version saved state of `anyState('abrac\0dabra\0')` to `statecolumn` then incompatible versions will print `'abrac\0dabra'` on `anyMerge(statecolumn)`. The issue also affects distributed queries when an incompatible version works in a cluster together with older or newer versions. (). Backported in : Update tzdata to 2022f. Mexico will no longer observe DST except near the US border: https://www.timeanddate.com/news/time/mexico-abolishes-dst-2022.html. Chihuahua moves to year-round UTC-6 on 2022-10-30. Fiji no longer observes DST. See https://github.com/google/cctz/pull/235 and https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1995209. (). Backported in : Wait for all files are in sync before archiving them in integration tests. (). Backported in : Before the fix, the user-defined config was preserved by RPM in `$file.rpmsave`. The PR fixes it and won't replace the user's files from packages. (). Backported in : Add a CI step to mark commits as ready for release; soft-forbid launching a release script from branches but master. (). Backported in : Fixed queries with `SAMPLE BY` with prewhere optimization on tables using `Merge` engine. (). Backported in : Fixed primary key analysis with conditions involving `toString(enum)`. (). Always run `BuilderReport` and `BuilderSpecialReport` in all CI types (). Update SECURITY.md on new stable tags (). Use all parameters with prefixes from ssm (). Temporarily disable `testhivequery` (). Do not checkout submodules recursively (). Use docker images cache from merged PRs in master and release branches ().