cwielenb/CNCF-Dataset huggingface dataset:
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.15.0.md

update pipeline to push demo file to shifu dev by @leepala in https://github.com/Edgenesis/shifu/pull/550 update user metrics endpoint to shifu dev by @leepala in https://github.com/Edgenesis/shifu/pull/559 Bump go 1.20 by @leepala in https://github.com/Edgenesis/shifu/pull/567 Bump github.com/imdario/mergo from 0.3.13 to 0.3.14 by @dependabot in https://github.com/Edgenesis/shifu/pull/546 Bump k8s.io/client-go from 0.26.2 to 0.26.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/554 Bump github.com/gopcua/opcua from 0.3.11 to 0.3.13 by @dependabot in https://github.com/Edgenesis/shifu/pull/562 Bump github.com/onsi/gomega from 1.27.4 to 1.27.5 by @dependabot in https://github.com/Edgenesis/shifu/pull/560 Bump github.com/imdario/mergo from 0.3.14 to 0.3.15 by @dependabot in https://github.com/Edgenesis/shifu/pull/565 Bump github.com/minio/minio-go/v7 from 7.0.49 to 7.0.50 by @dependabot in https://github.com/Edgenesis/shifu/pull/564 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.14.0...v0.15.0
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: no-forbidden-package-imports.md

Disallow internal monorepo imports from package subpaths that are not exported. Add the rules as follows, it has no options: ```js "@backstage/no-forbidden-package-imports": ["error"] ``` Given the following two target packages: ```json { "name": "@backstage/plugin-foo", "files": ["dist", "type-utils"] } ``` ```json { "name": "@backstage/plugin-bar", "exports": { ".": "./src/index.ts", "./testUtils": "./src/testUtils/index.ts", "./package.json": "./package.json" } } ``` ```ts import { FooCard } from '@backstage/plugin-foo/src/components'; import { BarCard } from '@backstage/plugin-bar/src/components'; ``` ```ts import { FooCard } from '@backstage/plugin-foo'; import { FooType } from '@backstage/plugin-foo/type-utils'; import fooPkg from '@backstage/plugin-foo/package.json'; import { BarCard } from '@backstage/plugin-bar'; import { renderBarCardExtension } from '@backstage/plugin-bar/testUtils'; import barPkg from '@backstage/plugin-bar/package.json'; ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.5.6.6-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix a rare bug that could lead to a partially initialized table that can serve write requests (insert/alter/so on). Now such tables will be in readonly mode. (). Backported in : Set `max_threads = 1` to fix mutation fail of StorageMemory. Closes . (). Backported in : Allow empty HTTP headers. Fixes . (). Backported in : Fixed a bug in moving Materialized View from Ordinary to Atomic database (`RENAME TABLE` query). Now inner table is moved to new database together with Materialized View. Fixes . (). Backported in : Fix drop partition with intersect fake parts. In rare cases there might be parts with mutation version greater than current block number. (). Backported in : Fix incorrect monotonicity of toWeek function. This fixes . This bug was introduced in https://github.com/ClickHouse/ClickHouse/pull/5212 , and was exposed later by smarter partition pruner. (). Backported in : Fixed the behavior when query `SYSTEM RESTART REPLICA` or `SYSTEM SYNC REPLICA` is being processed infinitely. This was detected on server with extremely little amount of RAM. (). Backported in : Fix usage of tuples in `CREATE .. AS SELECT` queries. (). Backported in : Enable reading of subcolumns for distributed tables. (). Backported in :. (). Fix segfault in TSan on _exit (). Use memmove in PODArray::insert to handle memory overlapping. (). Fix cli argument in clickhouse-server.init ().
Project: Meshery (Provisioning / Automation & Configuration)
File: 1.11.3.md

component: 1.11.3 integrations: consulmesh.meshery consulmesh_definition.json exportedservices.meshery exportedservices.meshery ingressgateway.meshery ingressgateway.meshery mesh.meshery mesh.meshery proxydefaults.meshery proxydefaults.meshery servicedefaults.meshery servicedefaults.meshery serviceintentions.meshery serviceintentions.meshery serviceresolver.meshery serviceresolver.meshery servicerouter.meshery servicerouter.meshery servicesplitter.meshery servicesplitter.meshery terminatinggateway.meshery terminatinggateway.meshery
Project: KICS (Provisioning / Security & Compliance)
File: b7bca5c4-1dab-4c2c-8cbe-3050b9d59b14.md

title: RBAC Roles with Read Secrets Permissions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b7bca5c4-1dab-4c2c-8cbe-3050b9d59b14 Query name: RBAC Roles with Read Secrets Permissions Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Roles and ClusterRoles with get/watch/list RBAC permissions on Kubernetes secrets are dangerous and should be avoided. In case of compromise, attackers could abuse these roles to access sensitive data, such as passwords, tokens and keys<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9 18" apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: namespace: default name: role-secret-reader rules: apiGroups: [""] resources: ["secrets"] verbs: ["get", "watch", "list"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: cluster-role-secret-reader rules: apiGroups: [""] resources: ["secrets"] verbs: ["get", "watch", "list"] ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: namespace: default name: role-pod-and-logs-reader rules: apiGroups: [""] resources: ["pods", "pods/logs"] verbs: ["get", "watch", "list"] apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: cluster-role-pod-and-pod-logs-reader rules: apiGroups: [""] resources: ["pods", "pods/log"] verbs: ["get", "list"] ```
Project: Timescale (App Definition and Development / Database)
File: README.module.md

We link module loading and activation to the license GUC itself. We have a single GUC, the license, and load submodules based on what capabilities the license enables, i.e., an `apache` license-key does not load this module, while `timescale` key does. This ensures that the loader "does the right thing" with respect to the license, and a user cannot accidentally activate features they aren't licensed to use. The actual loading and activation is done through `check` and `assign` hooks on the license GUC. On `check` we validate the license type and on `assign` we set the capabilities-struct in this module, if needed. The `check` and `assign` functions can be found in in the Apache-Licensed src. To enable binaries which only contain Apache-Licensed code, we dynamically link in Timescale-Licensed code on license activation, and handle all function calls into the module via function pointers. The registry in `tscmfunctions` of type `CrossModuleFunctions` (declared in and defined in ) stores all of the cross-module functions. To add a new cross-module function you must: Add a struct member `CrossModuleFunctions.<function name>`. Add default function to `tscmfunctionsdefault` that will be called from the Apache version, usually this function should just call `errornodefaultfn`. NOTE Due to function-pointer casting rules, the default function must have the exact same signature as the function pointer; you may not cast another function pointer of another type. Add the overriding function to `tslcmfunctions`in `init.c` in this module. To call a cross-module functions use `tscmfunctions-><function name>(args)`.
Project: StarRocks (App Definition and Development / Database)
File: split_part.md

displayed_sidebar: "English" This function splits a given string according to the separators and returns the requested part. (start counting from the beginning) ```Haskell VARCHAR split_part(VARCHAR content, VARCHAR delimiter, INT field) ``` ```Plain Text MySQL > select split_part("hello world", " ", 1); +-+ |split_part('hello world', ' ', 1) | +-+ | hello | +-+ MySQL > select split_part("hello world", " ", 2); +--+ | split_part('hello world', ' ', 2) | +--+ | world | +--+ MySQL > select split_part("hello world", " ", -1); +-+ |split_part('hello world', ' ', -1) | +-+ | world | +-+ MySQL > select split_part("hello world", " ", -2); +--+ | split_part('hello world', ' ', -2) | +--+ | hello | +--+ MySQL > select split_part("abca", "a", 1); +-+ | split_part('abca', 'a', 1) | +-+ | | +-+ select split_part("abca", "a", -1); +--+ | split_part('abca', 'a', -1) | +--+ | | +--+ select split_part("abca", "a", -2); +--+ | split_part('abca', 'a', -2) | +--+ | bc | +--+ ``` SPLIT_PART,SPLIT,PART
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-components-view.md

layout: default title: mesheryctl-exp-components-view permalink: reference/mesheryctl/exp/components/view redirect_from: reference/mesheryctl/exp/components/view/ type: reference display-title: "false" language: en command: exp subcommand: components view registered components view a component registered in Meshery Server <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp components view [flags] </div> </pre> View details of a specific component <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp components view [component-name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for view -o, --output-format string (optional) format to display in [json|yaml] (default "yaml") </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Meshery (Provisioning / Automation & Configuration)
File: cd-pipeline-operator.md

layout: integration title: CD Pipeline Operator subtitle: Collaborative and visual infrastructure as code for CD Pipeline Operator image: /assets/img/integrations/cd-pipeline-operator/icons/color/cd-pipeline-operator-color.svg permalink: extensibility/integrations/cd-pipeline-operator docURL: https://docs.meshery.io/extensibility/integrations/cd-pipeline-operator description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery registrant: Artifact Hub components: name: cd-pipeline colorIcon: assets/img/integrations/cd-pipeline-operator/components/cd-pipeline/icons/color/cd-pipeline-color.svg whiteIcon: assets/img/integrations/cd-pipeline-operator/components/cd-pipeline/icons/white/cd-pipeline-white.svg description: name: stage colorIcon: assets/img/integrations/cd-pipeline-operator/components/stage/icons/color/stage-color.svg whiteIcon: assets/img/integrations/cd-pipeline-operator/components/stage/icons/white/stage-white.svg description: featureList: [ "Provides a pre-defined set of CI/CD patterns and tools.", "Allows shortening the time that is passed before an active development.", "Security covers authentication, authorization, and SSO for platform services." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-context-list.md

layout: default title: mesheryctl-system-context-list permalink: reference/mesheryctl/system/context/list redirect_from: reference/mesheryctl/system/context/list/ type: reference display-title: "false" language: en command: system subcommand: context list contexts List current context and available contexts <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context list [flags] </div> </pre> List all contexts present <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context list </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for list </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Fluvio (App Definition and Development / Streaming & Messaging)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: "[Bug]:" labels: bug assignees: '' What happened A clear and concise description of what the bug is. Expected behavior A clear and concise description of what you expected to happen. Describe the setup Are you using a local Fluvio install? Minikube? Fluvio Cloud? What version of Fluvio are you using? `fluvio version` How to reproduce it (as minimally and precisely as possible) Steps to reproduce the behavior: Run the command '...' Type the input '...' Log output It helps to have logs from Fluvio's SC and SPU processes. Depending on your setup, here's how you can get the logs: For a local Fluvio installation on Mac & Linux: Run `cat ~/.fluvio/log/flv_sc.log` for SC logs Run `cat ~/.fluvio/log//spulogXXXX.log` for each SPU E.g. when running 1 SPU, there will be `spulog5001.log` For a Fluvio installation on Minikube: Run `kubectl logs fluvio-sc` for SC logs Run `kubectl logs fluvio-spg-main-X` for each SPU Environment (please complete the following information): OS: [e.g. Linux, Mac] Fluvio Version [e.g. 22] Kubernetes version: use `kubectl version` Minikube or other k8 version (if used): use `minikube version` Optional Debugging: Another trace which may be useful is re-running the command with RUST_LOG specified at a higher level `RUSTLOG=info fluvio ...` or `RUSTLOG=debug fluvio ...` Additional context Add any other context about the problem here.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: docker-machine.md

title: Docker controls via OPA Policies software: docker labels: layer: server category: container code: https://github.com/open-policy-agent/opa-docker-authz tutorials: https://www.openpolicyagent.org/docs/latest/docker-authorization/ inventors: styra Docker's out of the box authorization model is all or nothing. This integration demonstrates how to use OPA's context-aware policies to exert fine-grained control over Docker.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: identity.md

id: identity title: Identity Service sidebar_label: Identity description: Documentation for the Identity service When working with backend plugins, you might find that you will need to interact with the `auth-backend` plugin to both authenticate backstage tokens, and to deconstruct them to get the user's entity ref and/or ownership claims out of them. The following example shows how to get the identity service in your `example` backend plugin and retrieve the user's entity ref and ownership claims for the incoming request. ```ts import { coreServices, createBackendPlugin, } from '@backstage/backend-plugin-api'; import { Router } from 'express'; createBackendPlugin({ pluginId: 'example', register(env) { env.registerInit({ deps: { identity: coreServices.identity, http: coreServices.httpRouter, }, async init({ http, identity }) { const router = Router(); router.get('/test-me', (request, response) => { // use the identity service to pull out the header from the request and get the user const { identity: { userEntityRef, ownershipEntityRefs }, } = await identity.getIdentity({ request, }); // send the decoded and validated things back to the user response.json({ userEntityRef, ownershipEntityRefs, }); }); http.use(router); }, }); }, }); ``` There's additional configuration that you can optionally pass to setup the `identity` core service. `issuer` - Set an optional issuer for validation of the JWT token `algorithms` - `alg` header for validation of the JWT token, defaults to `ES256`. More info on supported algorithms can be found in the You can configure these additional options by adding an override for the core service when calling `createBackend` like follows: ```ts import { identityServiceFactory } from '@backstage/backend-app-api'; const backend = createBackend(); backend.add( identityServiceFactory({ issuer: 'backstage', algorithms: ['ES256', 'RS256'], }), ); ```
Project: Meshery (Provisioning / Automation & Configuration)
File: tanzu-sm.md

layout: default title: Meshery Adapter for Tanzu Service Mesh name: Meshery Adapter for Tanzu Service Mesh component: Tanzu Service Mesh earliest_version: pre-GA port: 10011/gRPC project_status: alpha github_link: https://github.com/meshery/meshery-tanzu-sm image: /assets/img/service-meshes/tanzu.svg white_image: /assets/img/service-meshes/tanzu.svg permalink: extensibility/adapters/tanzu-sm redirect_from: service-meshes/adapters/tanzu-sm language: en {% assign sortedtestsgroup = site.compatibility | group_by: "meshery-component" %} {% for group in sortedtestsgroup %} {% if group.name == "meshery-tanzu-mesh" %} {% assign items = group.items | sort: "meshery-component-version" | reverse %} {% for item in items %} {% if item.meshery-component-version != "edge" %} {% if item.overall-status == "passing" %} {% assign adapterversiondynamic = item.meshery-component-version %} {% break %} {% elsif item.overall-status == "failing" %} {% continue %} {% endif %} {% endif %} {% endfor %} {% endif %} {% endfor %} {% include compatibility/adapter-status.html %} The {{page.name}} can install {{page.earliest_version}} of {{page.component}}. A number of sample applications for {{page.component}} can also be installed using Meshery. The {{ page.name }} is currently under construction ({{ page.project_status }} state), which means that the adapter is not functional and cannot be interacted with through the <a href="{{ site.baseurl }}/installation#6-you-will-now-be-directed-to-the-meshery-ui"> Meshery UI </a>at the moment. Check back here to see updates. Want to contribute? Check our . Examine and how adapters fit in as a component. Learn more about .
Project: StarRocks (App Definition and Development / Database)
File: to_json.md

displayed_sidebar: "English" Converts a Map or Struct value into a JSON string. If the input value is NULL, NULL is returned. If you want to cast values of other data types, see . This function is supported from v3.1 onwards. ```Haskell tojson(anyvalue) ``` `any_value`: the Map or Struct expression you want to convert. If the input value is invalid, an error is returned. The value in each key-value pair of the Map or Struct value is nullable. See the last example. Returns a JSON value. ```Haskell select to_json(map{1:'a',2:'b'}); ++ | to_json(map{1:'a',2:'b'}) | ++ | {"1": "a", "2": "b"} | ++ select to_json(row('asia','eu')); +--+ | to_json(row('asia', 'eu')) | +--+ | {"col1": "asia", "col2": "eu"} | +--+ select tojson(map('a', namedstruct('b', 1))); +-+ | tojson(map{'a':namedstruct('b', 1)}) | +-+ | {"a": {"b": 1}} | +-+ select tojson(namedstruct("k1", cast(null as string), "k2", "v2")); +--+ | tojson(namedstruct('k1', CAST(NULL AS VARCHAR(65533)), 'k2', 'v2')) | +--+ | {"k1": null, "k2": "v2"} | +--+ ```
Project: MongoDB (App Definition and Development / Database)
File: gperftools.md

There are two projects on Github that are based on Googles internal TCMalloc: This repository and . Both are fast C/C++ memory allocators designed around a fast path that avoids synchronizing with other threads for most allocations. This repository is Google's current implementation of TCMalloc, used by ~all of our C++ programs in production. The code is limited to the memory allocator implementation itself. Google open-sourced its memory allocator as part of "Google Performance Tools" in 2005. At the time, it became easy to externalize code, but more difficult to keep it in-sync with our internal usage, as discussed by Titus Winters in and the "Software Engineering at Google" book. Subsequently, our internal implementation diverged from the code externally. This project eventually was adopted by the community as "gperftools." Since , we have invested in improving application productivity via optimizations to the implementation (per-CPU caches, sized delete, fast/slow path improvements, ). Because this repository reflects our day-to-day usage, we've focused on the platforms we regularly use and can see extensive testing and optimization. This implementation is based on . Like Abseil, we do not attempt to provide ABI stability. Providing a stable ABI could require compromising performance or adding otherwise unneeded complexity to maintain stability. These caveats are noted in our . In addition to a memory allocator, the gperftools project contains a number of other tools: An All-Allocation Memory Profiler: We have found this prohibitively costly to use regularly, and instead focus on using low-overhead, always-on sampling profilers. This sampling based profiler is exposed in our `malloc_extension.h`. A SIGPROF-based CPU Profiler: The Linux `perf` tool is decreasing our internal need for signal-based profiling. Additionally, with restartable sequences, signals interrupt the fastpath, leading to skew between the observed instruction pointer and where we actually spend CPU time. A Heap Checker/Debug Allocator: The LeakSanitizer, AddressSanitizer, and MemorySanitizer suite provide higher accuracy and better performance. A perl-based `pprof` tool: This project is now developed in Go and is . The configuration on Github mirrors our production defaults, with two notable exceptions: Many of our production servers start a background thread (via `tcmalloc::MallocExtension::ProcessBackgroundActions`) to regularly call `tcmalloc::MallocExtension::ReleaseMemoryToSystem`, while others never release memory in favor of better CPU performance. These tradeoffs are discussed in our . We do not activate by default, but can be activated via `MallocExtension`. Over time, we have found that configurability carries a maintenance burden. While a knob can provide immediate flexibility, the increased complexity can cause subtle problems for more rarely used combinations.
Project: GraphScope (App Definition and Development / Database)
File: installation.md

Interactive relies solely on Docker and does not have a strong dependency on the operating system, so in theory, a single installation package could be applicable to all systems. In practical tests, we have successfully tested it on Ubuntu and macOS, as well as on ARM64 and x86_64 architectures. Docker Installation: Ensure you have Docker installed and configured on a Mac or Linux machine. If you haven't installed Docker yet, you can find the installation guide . Download Required Files: Download the compressed file containing Docker configuration files, example data, and other necessary resources from . Extract the contents to a suitable location on your machine: Just unzip the zip file. ```bash unzip interactive-latest.zip cd interactive export INTERACTIVE_HOME=`pwd` ``` To explore the usage of GraphScope Interactive, please follow .