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

name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: '' Please note that GitHub issues are only meant for bug reports/feature requests. If you have questions on how to use Neo4j, please ask on instead of creating an issue here. Before creating a new issue, please check whether someone else has raised the same issue. You may be able to add context to that issue instead of duplicating the report. However, each issue should also only be focussed on a single problem, so do not describe new problems within an existing thread - these are very hard to track and manage, and your problem may be ignored. Finally, do not append comments to closed issues; if the same problem re-occurs, open a new issue, and include a link to the old one. To help us understand your issue, please specify important details, primarily: Neo4j version: X.Y.Z Operating system: (for example Windows 95/Ubuntu 16.04) API/Driver: (for example Cypher/Java API/Python driver vX.Y.Z) Steps to reproduce Expected behavior Actual behavior Additionally, include (as appropriate) log-files, stacktraces, and other debug output. I discovered that when I mount `data/` to a volume on my host, and then stop the container, the `write.lock` is not removed as well as a number of other files not being cleaned up properly. Neo4j Version: 3.0M03 Operating System: Ubuntu 15.10 API: Docker Pull the image: `docker pull neo4j/neo4j:3.0.0-M03` Create a directory on the host that will be a mount for the data: `mkdir /home/neo4j-data` Start a new container that mounts to this directory: `docker run -d --name neo4j-test -p 7474:7474 -v /home/neo4j-data:/data neo4j/neo4j:3.0.0-M03` Navigate to the `write.lock` file located in the directory: `/data/databases/graph.db/schema/label/lucene/labelStore/1/` Stop the container: `docker stop neo4j-test` `write.lock` should be removed now. `write.lock` is still present and preventing access by other programs.
Project: SuperEdge (Provisioning / Automation & Configuration)
File: tutorial.md

format, build and test: `make` build: `make build` build some cmd: `make build BINS="lite-apiserver edgeadm"` build multi arch cmd: `make build.multiarch BINS="lite-apiserver edgeadm" PLATFORMS="linuxamd64 linuxarm64"` build docker image: `make image IMAGES="application-grid-controller application-grid-wrapper"` build multi arch docker image: `make image.multiarch IMAGES="application-grid-controller application-grid-wrapper" PLATFORMS="linuxamd64 linuxarm64" VERSION="v2.0.0"` push mainfest: `make manifest.multiarch IMAGES="application-grid-wrapper application-grid-controller" PLATFORMS="linuxamd64 linuxarm64" REGISTRY_PREFIX="docker.io/superedge" VERSION="v2.0.0"` clean: `make clean`
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_fix.md

Fix inconsistencies and deprecated usage of Kyverno resources. Fix inconsistencies and deprecated usage of Kyverno resources. The fix command provides a command-line interface to fix inconsistencies and deprecated usage of Kyverno resources. It can be used to fix Kyverno test files. NOTE: This is an experimental command, use `KYVERNO_EXPERIMENTAL=true` to enable it. ``` kyverno fix [flags] ``` ``` KYVERNO_EXPERIMENTAL=true kyverno fix test . --save ``` ``` -h, --help help for fix ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Kubernetes Native Policy Management. - Fix inconsistencies and deprecated usage in Kyverno policy files. - Fix inconsistencies and deprecated usage in Kyverno test files.
Project: Vault (Provisioning / Key Management)
File: bug_report.md

name: Bug report about: Let us know about a bug! title: '' labels: '' assignees: '' <!-- Please reserve GitHub issues for bug reports and feature requests. For questions, the best place to get answers is on our , as they will get more visibility from experienced users than the issue tracker. Please note: We take Vault's security and our users' trust very seriously. If you believe you have found a security issue in Vault, please responsibly disclose by contacting us at security@hashicorp.com. Our PGP key is available at . --> Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Run `vault write ...` Run `vault login....` See error Expected behavior A clear and concise description of what you expected to happen. Environment: Vault Server Version (retrieve with `vault status`): Vault CLI Version (retrieve with `vault version`): Server Operating System/Architecture: Vault server configuration file(s): ```hcl ``` Additional context Add any other context about the problem here.
Project: Salt Project (Provisioning / Automation & Configuration)
File: 0003-job-retry.md

Feature Name: Job retry Start Date: 2018-10-16 RFC PR: https://github.com/saltstack/salt/compare/develop...cachedout:job_retry Salt Issue: (leave this empty) This feature enables Salt to detect when a minion did not run a job and when the minion comes back online, the job is published to that minion. For a long time, people have complained that Salt has no way to send a job to a minion that was not available to receive it at the time that it was published. Doing so would allow Salt administrators to publish a job and not worry about whether or not a minion that was down at the time did not receive the job. At a high level, the way that this feature operates is relatively simple and only minor extensions to the core of salt itself are necessary. All operations will be gated behind a configuration option called `job_retry` which will default to being disabled. We propose a `job_retry` engine be created which can run on the master. The purpose of this engine is to detect minion "start" events and then to check a master cache for any jobs which might be enqueued and, if found, pull those pending jobs from the queue and publish them to the minion. Jobs are enqueued on the master using the masterapi cache subsystem. There shall be an individual cache for each minion which is found not to respond. In this cache will be a list of JIDs which the master believes were not sent. Jobs to be retried are inserted into the cache by the LocalClient when it deterermines that a minion which it expected to return did not. Please see https://github.com/saltstack/salt/compare/develop...cachedout:job_retry for a POC. No alternatives considered but ideas welcome. May not work with anything that interacts with the master but bypasses the LocalClient. Should minions also check to see if they have run the job? Probably. The main drawback is the risk of running a job twice. Additionally, failure to clear a cache may cause a job to be run in a loop which would be pretty bad. ;-/
Project: YDB (App Definition and Development / Database)
File: first_last_value.md

Access values from the first and last rows (using the `ORDER BY` clause for the window) of the . The only argument is the expression that you need to access. Optionally, `OVER` can be preceded by the additional modifier `IGNORE NULLS`. It changes the behavior of functions to the first or last non-empty (i.e., non-`NULL`) value among the window frame rows. The antonym of this modifier is `RESPECT NULLS`: it's the default behavior that can be omitted. Signature ``` FIRST_VALUE(T)->T? LAST_VALUE(T)->T? ``` Examples ```yql SELECT FIRSTVALUE(mycolumn) OVER w FROM my_table WINDOW w AS (ORDER BY key); ``` ```yql SELECT LASTVALUE(mycolumn) IGNORE NULLS OVER w FROM my_table WINDOW w AS (ORDER BY key); ```
Project: Harbor (Provisioning / Container Registry)
File: deploying_using_docker_machine.md

Docker Machine allows you to deploy your containers to several cloud providers or on premises using a unified interface. To deploy Harbor using Docker Machine, first create a virtual machine using Docker Machine. This example will use DigitalOcean, but you can use VMware vCloud Air, AWS or Azure as well. Please see the list of supported drivers in the . ``` $ docker-machine create --driver digitalocean --digitalocean-access-token <youraccesstoken> harbor.mydomain.com ``` After the machine has been created successfully, you need to create a DNS entry at your provider for e.g. harbor.mydomain.com using the IP address for the machine we just created. You can get this IP address using: ``` $ docker-machine ip harbor.mydomain.com ``` Copy `Deploy/harbor.yml.tmp` to `Deploy/harbor.yml` and make sure to change the `hostname` in `Deploy/harbor.yml` to `harbor.mydomain.com`, configure everything else according to the and run `prepare`. Now, activate the created Docker Machine instance: `$ eval $(docker-machine env harbor.mydomain.com)` From within the `Deploy` directory, next copy the contents of the `config` directory to the machine. First, get your local path to the `Deploy` directory: ``` $ echo $PWD ``` This will give you something like this: ``` /home/<yourusername>/src/harbor/Deploy ``` Then create this directory structure on the remote machine and copy the local files to the remote folders: ``` $ docker-machine ssh harbor.mydomain.com 'mkdir -p /home/<yourusername>/src/harbor/Deploy/config $ docker-machine scp -r ./config harbor.mydomain.com:$PWD ``` Next, build your Harbor images: ``` $ docker-compose build ``` And finally, spin up your Harbor containers: ``` $ docker-compose up -d ``` Now you should be able to browse `http://harbor.mydomain.com`.
Project: Trivy (Provisioning / Security & Compliance)
File: discussion.md

Thank you for taking interest in contributing to Trivy! Trivy uses for bug reports, feature requests, and questions. If maintainers decide to accept a new feature or confirm that it is a bug, they will close the discussion and create a associated with that discussion. Feel free to open discussions for any reason. When you open a new discussion, you'll have to select a discussion category as described below. Please spend a small amount of time giving due diligence to the issue/discussion tracker. Your discussion might be a duplicate. If it is, please add your comment to the existing issue/discussion. Remember that users might search for your issue/discussion in the future, so please give it a meaningful title to help others. The issue should clearly explain the reason for opening, the proposal if you have any, and any relevant technical information. There are 4 categories: - Share ideas for new features - Report false positives/negatives - Report something that is not working as expected - Ask the community for help !!! note If you find any false positives or false negatives, please make sure to report them under the "False Detection" category, not "Bugs". Trivy depends on . Sometime these databases contain mistakes. If Trivy can't detect any CVE-IDs or shows false positive result, at first please follow the next steps: Run Trivy with `-f json` that shows data sources. According to the shown data source, make sure that the security advisory in the data source is correct. If the data source is correct and Trivy shows wrong results, please raise an issue on Trivy. Visit and search CVE-ID. If you find a problem, it'll be nice to fix it: Visit and search CVE-ID. If you find a problem, it'll be nice to fix it: Visit and search CVE-ID.
Project: Harbor (Provisioning / Container Registry)
File: 3-06-LDAP-user-search-project-members.md

Test 3-06 - Search Project Members (LDAP Mode) ======= To verify that a non system admin user can search members of a project 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 five(5) non-admin users are in Harbor. Same as Test 3-03. Same as Test 3-03. None
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 1.7.md

We cannot wait for you to try the new features: Monokle now brings policy validation directly into your editor by integrating the Open Policy Agent The list of Helm Templates is now visible in the Helm Pane References to Values files in Helm Templates are now highlighted in the code editor You can now disable editing resources in Cluster Mode The "Getting Started" page has been redesigned for easier interaction Added a new Walkthrough tutorial to get you started with the core features And some more!
Project: ClickHouse (App Definition and Development / Database)
File: v23.2.4.12-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Fix IPv4/IPv6 serialization/deserialization in binary formats that was broken in https://github.com/ClickHouse/ClickHouse/pull/43221. Closes . (). Backported in : `INSERT` queries through native TCP protocol and HTTP protocol were not canceled correctly in some cases. It could lead to a partially applied query if a client canceled the query, or if a client died or, in rare cases, on network errors. As a result, it could lead to not working deduplication. Fixes and . (). Backported in : Fix possible deadlock on distributed query cancellation. (). Follow-up to (). Add a manual trigger for release workflow ().
Project: StarRocks (App Definition and Development / Database)
File: to_bitmap.md

displayed_sidebar: "English" The input is unsigned bigint with the value ranging from 0 to 18446744073709551615, and the output is bitmap containing this element. This function is mainly used for the stream load task to import integer fields into the bitmap field of the StarRocks table. For example: ```bash cat data | curl --location-trusted -u user:passwd -T - \ -H "columns: dt,page,userid, userid=tobitmap(userid)" \ http://host:8410/api/test/testDb/streamload ``` ```Haskell BITMAP TO_BITMAP(expr) ``` ```Plain Text MySQL > select bitmapcount(tobitmap(10)); +--+ | bitmapcount(tobitmap(10)) | +--+ | 1 | +--+ select bitmaptostring(to_bitmap(10)); ++ | bitmaptostring(to_bitmap(10)) | ++ | 10 | ++ select bitmaptostring(to_bitmap(-5)); ++ | bitmaptostring(to_bitmap(-5)) | ++ | NULL | ++ select bitmaptostring(to_bitmap(null)); +--+ | bitmaptostring(to_bitmap(NULL)) | +--+ | NULL | +--+ ``` TO_BITMAP,BITMAP
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.25.md

RabbitMQ `3.10.25` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang versions older than 24.3 have reached . This release of RabbitMQ or later versions. Nodes will fail to start on older Erlang releases. Erlang 25.3 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Declaration of a classic queue could run into an exception. GitHub issue: Stream client connections that authenticated using x.509 certificates failed. GitHub issue: It was not possible to close a table column selection pane on screens that had little vertical space. Contributed by @Antsthebul. GitHub issue: `oauth2` is now an accepted alias for the OAuth 2 authentication and authorization backend: ``` auth_backends.1 = oauth2 ``` Previously the only option for OAuth 2 was using a full module name, `rabbitauthbackend_oauth2`. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.25.tar.xz` instead of the source tarball produced by GitHub.
Project: Paladin Cloud (Provisioning / Security & Compliance)
File: --questions.md

name: " Questions" about: " Have any questions regarding how PaladinCloud works?" title: "[Question]" labels: question assignees: '' <! Provide your question here --> <! How has this issue affected you? What are you trying to accomplish? --> <! Providing context helps us come up with a solution that is most useful in the real world --> <!-- If you are seeing an error, please provide a code repository, gist or sample files to reproduce the issue -->
Project: external-secrets (Provisioning / Security & Compliance)
File: create_release.md

name: Create Release about: Release template to track the next release title: Release x.y labels: area/release assignees: '' This Issue tracks the next ESO release. Please follow the guideline below. If anything is missing or unclear, please add a comment to this issue so this can be improved after the release. [ ] ask in `#external-secrets-dev` if we're ready for a release cut-off or if something needs to get urgently in is up to date [ ] version table [ ] Provider Stability and Support table [ ] Provider Feature Support table - [ ] move issues to next milestone [ ] close milestone [ ] Announce release on `#external-secrets` in Slack
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: envoy-debugging.md

title: Debugging Tips kind: envoy weight: 110 This page provides some pointers that could assist in addressing issues encountered while using the OPA-Envoy plugin. If none of these tips work, feel free to join and ask for help. The `opa bench` command evaluates a Rego query multiple times and reports metrics. You can also profile your polices using `opa eval` to understand expression evaluation time. More information on improving policy performance can be found . The OPA-Envoy plugin logs every decision that it makes. These logs contain lots of useful information including metrics like gRPC server handler time and Rego query evaluation time which can help in measuring the OPA-Envoy plugin's performance. To enable local console logging of decisions see . Envoy's External authorization gRPC service configuration uses either Envoys in-built gRPC client, or the Google C++ gRPC client. From the results, lower latency numbers are seen while using Envoys gRPC client versus Google's. Experimenting with the gRPC service configuration may help in improving performance. The filter configuration also has a `statusonerror` field that can be used to indicate a network error between the filter and the OPA-Envoy plugin. The default status on such an error is HTTP `403 Forbidden`. Changing the default value of this field will help uncover potential network issues as `403 Forbidden` is also generated when a request is denied. This section provides examples of interacting with the Envoy External Authorization gRPC server using the tool. List all services exposed by the server ```bash $ grpcurl -plaintext localhost:9191 list ``` Output: ```bash envoy.service.auth.v2.Authorization envoy.service.auth.v3.Authorization grpc.reflection.v1alpha.ServerReflection ``` Invoke a v3 Check RPC on the server ```bash $ grpcurl -plaintext -d ' { "attributes": { "request": { "http": { "method": "GET", "path": "/api/v1/products" } } } }' localhost:9191 envoy.service.auth.v3.Authorization/Check ``` Output: ```json { "status": { }, "okResponse": { "headers": [ { "header": { "key": "x-ext-auth-allow", "value": "yes" } } ] } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: flink-runner.md

title: "Flink Runner Roadmap" <!-- Licensed 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. --> This roadmap is in progress. In the meantime, here are available resources: - Issues:
Project: StarRocks (App Definition and Development / Database)
File: Lambda_expression.md

displayed_sidebar: "English" Lambda expressions are anonymous functions that can be passed as parameters into higher-order SQL functions. Lambda expressions allow you to develop code that is more concise, elegant, and extensible. Lambda expressions are written with the `->` operator, which reads "goes to". The left side of `->` is the input parameters (if any) and the right side is an expression. From v2.5 onwards, StarRocks supports using lambda expressions in the following higher-order SQL functions: , , , and . ```Haskell parameter -> expression ``` `parameter`: the input parameters for the lambda expression, which can accept zero, one, or more parameters. Two or more input parameters are enclosed in parentheses. `expression`: a simple expression that references `parameter`. The expression must be valid for the input parameters. The type of the return value is determined by the result type of `expression`. Almost all scalar functions can be used in a lambda body. But there are a few exceptions: Subqueries are not supported, for example, `x -> 5 + (SELECT 3)`. Aggregate functions are not supported, for example, `x -> min(y)`. Window functions are not supported. Table functions are not supported. Correlated columns cannot occur in lambda functions. Simple examples of lambda expressions: ```SQL -- Accepts no parameters and returns 5. () -> 5 -- Takes x and returns the value of (x + 2). x -> x + 2 -- Takes x and y, and returns their sum. (x, y) -> x + y -- Takes x and applies a function to x. x -> COALESCE(x, 0) x -> day(x) x -> split(x,",") x -> if(x>0,"positive","negative") ``` An example of using lambda expressions in higher-order functions: ```Haskell select array_map((x,y,z) -> x + y, [1], [2], [4]); +-+ | array_map((x, y, z) -> x + y, [1], [2], [4]) | +-+ | [3] | +-+ 1 row in set (0.01 sec) ```