cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeArmor (Provisioning / Security & Compliance)
File: pull_request_template.md

Purpose of PR?: Fixes # Does this PR introduce a breaking change? If the changes in this PR are manually verified, list down the scenarios covered:: Additional information for reviewer? : Mention if this PR is part of any design or a continuation of previous PRs Checklist: [ ] Bug fix. Fixes #<issue number> [ ] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) [ ] This change requires a documentation update [ ] PR Title follows the convention of `<type>(<scope>): <subject>` [ ] Commit has unit tests [ ] Commit has integration tests <!-- The PR title message must follow convention: `<type>(<scope>): <subject>`. Where: <br /> `type` is to define what type of PR is this. Most common types are: `feat` - for new features, not a new feature for build script `fix` - for bug fixes or improvements, not a fix for build script `chore` - changes not related to production code `docs` - changes related to documentation `style` - formatting, missing semi colons, linting fix etc; no significant production code changes `test` - adding missing tests, refactoring tests; no production code change `refactor` - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes `scope` is a single word that best describes where the changes fit. feature(`monitor`,`enforcer`) test(`tests`, `bdd`) chore(`build`) `subject` is a single line brief description of the changes made in the pull request. -->
Project: ArangoDB (App Definition and Development / Database)
File: explicit_inplace_exception_constructor.md

+++ title = "`explicit basicoutcome(inplacetypet<exceptiontypeif_enabled>, Args ...)`" description = "Explicit inplace exception constructor. Available if `predicate::enableinplaceexception_constructor<Args ...>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "inplace-constructors"] weight = 434 +++ Explicit inplace exception constructor. Calls {{% api "void onoutcomeinplaceconstruction(T *, inplacetypet<U>, Args &&...) noexcept" %}} with `this`, `inplacetype<exceptiontype>` and `Args ...`. Requires: `predicate::enableinplaceexception_constructor<Args ...>` is true. Complexity: Same as for the `exception_type` constructor which accepts `Args ...`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the Args is left indeterminate.
Project: YugabyteDB (App Definition and Development / Database)
File: ttl.md

title: TTL linkTitle: TTL description: TTL menu: preview: parent: api-yedis weight: 2470 aliases: /preview/api/redis/ttl /preview/api/yedis/ttl type: docs `TTL key` Returns the remaining time to live of a key that has a timeout, in seconds. Returns TTL in seconds, encoded as integer response. You can do this as shown below. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ EXPIRE yugakey 10 ``` ``` (integer) 1 ``` ```sh $ TTL yugakey ``` ``` (integer) 10 ``` , , ,
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: container-empty-disks.md

KubeVirt in combination with use-cases like the cluster-autoscaler can be used to scale and provision vm pools. With the VirtualMachineInstanceReplicaSet and cloud-init stateless pools can be instantiated and provisioned. Many of the used cloud images for these use-cases are booted with small disks with no additional free space, and/or run in read-only mode. A common pattern to store temporary data which should survive restarts or temporary data which is too big to fit in memory on temporary disks. The `emptyDir` in k8s provides a similar functionality. To provide a similar functionality for our `VirtualMachineInstances` an `emptyDisk` volume type will be introduced. A new volume type `emptyDisk` is introduced. The only parameter it supports is `capacity`. The `emptyDisk` will be placed by `virt-launcher` in an `emptyDir`, to make sure that the kubelet can take care of clean-up and that `ephemeral-store` resource definitions apply to the `emptyDisks` too. The definition looks like this: ```golang // EmptyDisk represents a temporary disk which shares the vms lifecycle type EmptyDiskSource struct { // Capacity of the sparse disk. Capacity resource.Quantity `json:"capacity"` } ``` A usage example: ```yaml apiVersion: kubevirt.io/v1alpha2 kind: VirtualMachineInstance metadata: name: testvm spec: terminationGracePeriodSeconds: 0 domain: resources: requests: memory: 512M devices: disks: name: disk1 volumeName: containerDisk disk: dev: vda name: disk2 volumeName: emptyDisk disk: dev: vdb volumes: name: containerDisk containerDisk: image: kubevirt/cirros-container-disk-demo:devel name: emptyDisk emptyDisk: capacity: 20G ``` This example will boot cirros (which traditionally boots read-only) and attach a 20 GB temporary disk which can be used to write temporary data. How and if this will be tied into the pods `resources.requests.ephemeral-storage` or `resources.limits.ephemeral-storage` is not yet clear and not part of this implementation.
Project: ClickHouse (App Definition and Development / Database)
File: v23.3.2.37-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Formatter '%M' in function formatDateTime() now prints the month name instead of the minutes. This makes the behavior consistent with MySQL. The previous behavior can be restored using setting "formatdatetimeparsedatetimemismonth_name = 0". (). Backported in : Fix some mysql related settings not being handled with mysql dictionary source + named collection. Closes . (). Backported in : Add fallback to password authentication when authentication with SSL user certificate has failed. Closes . (). Backported in : Update time zones. The following were updated: Africa/Cairo, Africa/Casablanca, Africa/ElAaiun, America/Bogota, America/CambridgeBay, America/CiudadJuarez, America/Godthab, America/Inuvik, America/Iqaluit, America/Nuuk, America/Ojinaga, America/Pangnirtung, America/RankinInlet, America/Resolute, America/Whitehorse, America/Yellowknife, Asia/Gaza, Asia/Hebron, Asia/Kuala_Lumpur, Asia/Singapore, Canada/Yukon, Egypt, Europe/Kirov, Europe/Volgograd, Singapore. (). Backported in : After the recent update, the `dockerd` requires `--tlsverify=false` together with the http port explicitly. (). Remove a feature (). Fix cpu usage in rabbitmq (was worsened in 23.2 after ) (). Fix ThreadPool for DistributedSink and use StrongTypedef for CurrentMetrics/ProfileEvents/StatusInfo to avoid further errors (). Reset downloader for cache file segment in TemporaryFileStream (). ClickHouse startup error when loading a distributed table that depends on a dictionary (). Fix possible segfault in cache (). Fix nested map for keys of IP and UUID types (). Fix bug in Keeper when a node is not created with scheme `auth` in ACL sometimes. (). Fix IPv4 comparable with UInt (). Batch fix for projections analysis with analyzer. (). Fix a confusing warning about interserver mode ().
Project: SPIFFE (Provisioning / Key Management)
File: MOHAMED_OMAR.md

Mohamed Omar leads SPIFFE/SPIRE efforts at Confluent. He has participated in the SPIFFE community for over 2 years and would be an excellent member of the steering committee. Email: momar@confluent.io GitHub: https://github.com/moe-omar LinkedIn Profile: https://www.linkedin.com/in/moeomar/ Current Affiliation: Confluent Recent presentation: https://www.youtube.com/watch?v=cKEQy0Vi8wc
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.26.md

layout: release date: 2024-03-01 tag: v0.7.26 [GraphQL Plugin] Extract plugin related logic @MUzairS15 (#10441) Revert "store token and session on domain instead of subdomain" @MUzairS15 (#10448) Docs :- information regarding a new command. @surajvast1 (#10407) [Add]: Relationship between PriorityClass and other k8s components @pandeyshubham03 (#10376) fix incorrect design save events @MUzairS15 (#10424) [Chore] Code base cleanup of "service mesh" @leecalcote (#10429) append comps at end to ensure core model sourceuri stays the same @MUzairS15 (#10447) [Server] Eliminate dead code and Improvements for controllers/dataHandlers. @MUzairS15 (#10389) Migrate registration stepper api to rtk @sudhanshutech (#10451) Add empty state for no result found in Registry @Yashsharma1911 (#10443) Inject structured data formatter in Remote Extension @codeKraken19 (#10439) Support ignoring models in Registry @Yashsharma1911 (#10171) [Chore] Code base cleanup of "service mesh" @leecalcote (#10429) Bump rails from 7.0.5 to 7.0.8.1 in /docs @dependabot (#10428) Vishalvivekm patch 1 @vishalvivekm (#10425) Tutorials layout @vishalvivekm (#9868) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @aabidsofi19, @codeKraken19, @dependabot, @dependabot[bot], @leecalcote, @pandeyshubham03, @sudhanshutech, @surajvast1 and @vishalvivekm
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-healthcheck-run.1.md

% podman-healthcheck-run 1 podman\-healthcheck\-run - Run a container healthcheck podman healthcheck run container Runs the healthcheck command defined in a running container manually. The resulting error codes are defined as follows: 0 = healthcheck command succeeded 1 = healthcheck command failed 125 = an error has occurred Possible errors that can occur during the healthcheck are: unable to find the container container has no defined healthcheck container is not running Print usage statement Run healthchecks in specified container: ``` $ podman healthcheck run mywebapp ``` , Feb 2019, Originally compiled by Brent Baude <bbaude@redhat.com>
Project: StarRocks (App Definition and Development / Database)
File: ANALYZE_PROFILE.md

displayed_sidebar: "English" Analyzes a specific query profile on a per-fragment basis, and displays it in a tree structure. For more information about query profile, see . This feature is supported from v3.1 onwards. CAUTION Only users with the SELECT privilege on a specific table can perform this operation. ```SQL ANALYZE PROFILE FROM '<queryid>', [<plannode_id>[, ...] ] ``` | Parameter | Description | | - | | | query_id | The ID of the query. You can obtain it using . | | plannodeid | The ID of the plan node in the profile. You can specify this parameter to view the detailed metrics of the corresponding plan node(s). If this parameter is not specified, only the summary metrics of all plan nodes are displayed. | Example 1: Querying the Query Profile without specifying node ID. Example 2: Querying the Query Profile and specifying node ID as `0`. StarRocks returns all detailed metrics for Node ID `0` and highlights metrics with high usage for easier problem identification.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.103.md

layout: release date: 2023-06-30 tag: v0.6.103 [CI] mesheryctl: replace goreleaser deprecations @leecalcote (#8004) [chore] Add save button in edit modal for filters @theBeginner86 (#7992) [UI] Remove deploy/undeploy from UI @theBeginner86 (#7991) [UI] Add support to download, publish, unpublish, and clone wasm support @Chadha93 (#7969) Fix: goreleaser halting the release process @Abhishek-kumar09 (#8003) Bump github.com/jinzhu/copier from 0.0.0-20190924061706-b57f9002281a to 0.3.5 @dependabot (#7942) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @dependabot, @leecalcote and @theBeginner86
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: service_group_updates.md

+++ title = "Service Group Updates" description = "Update service groups with supervisor configuration" gh_repo = "habitat" [menu] [menu.habitat] title = "Service Group Updates" identifier = "habitat/services/Service Group Updates" parent = "habitat/services" weight = 50 +++ The Chef Habitat Supervisor can be configured to leverage an optional update strategy, which describes how the Supervisor and its peers within a service group should respond when a new version of a package is available. To use an update strategy, configure the Supervisor to subscribe to Chef Habitat Builder, and more specifically, a channel for new versions. Chef Habitat supports three update strategies: `none`, `rolling`, and `at-once`. To start a Supervisor with the auto-update strategy, pass the `--strategy` argument to a Supervisor run command, and optionally specify the depot URL: ```bash hab sup run --strategy rolling --url https://bldr.habitat.sh hab svc load <ORIGIN>/<NAME> ``` This strategy means your package will not automatically be updated when a newer version is available. By default, Supervisors start with their update strategy set to `none` unless explicitly set to one of the other two update strategies. This strategy requires Supervisors to update to a newer version of their package one at a time in their service group. An update leader is elected which all Supervisors within a service group will update around. All update followers will first ensure they are running the same version of a service that their leader is running, and then the leader will poll Builder for a newer version of the service's package. Once the update leader finds a new version, it will update and wait until all other alive members in the service group have also been updated before once again attempting to find a newer version of software to update to. Updates will happen more or less one at a time until completion with the exception of a new node being introduced into the service group during the middle of an update. If your service group is also running with the `--topology leader` flag, the leader of that election will never become the update leader, so all followers within a leader topology will update first. It's important to note that because we must perform a leader election to determine an update leader, *you must have at least 3 Supervisors running a service group to take advantage of the rolling update strategy*. This strategy does no peer coordination with other Supervisors in the service group; it merely updates the underlying Chef Habitat package whenever it detects that a new version has either been published to a depot or installed to the local Chef Habitat `pkg` cache. No coordination between Supervisors is done, each Supervisor will poll Builder on their own.
Project: FOSSA (Provisioning / Security & Compliance)
File: fortran.md

Currently, we only support analysis of fortran project which are using . | Strategy | Direct Deps | Transitive Deps | Edges | Classifies Dev & Test Deps | Container Scanning | | -- | | | -- | -- | | | fpm | :whitecheckmark: | :x: | :x: | :whitecheckmark: | :whitecheckmark: | Find a file named `fpm.toml`. If `fpm.toml` is found, we do not scan in the `build` directory for more Fortran projects. Parse `fpm.toml` file to identify direct dependencies. We do not report . We do not report test or . We only report direct dependencies. Create a Fortran project managed by `fpm`. Execute `fpm new projectname`. This will create a directory named projectname with a manifest file, and a few example source files. Modify `fpm.toml` file to include direct dependency: ```toml name = "fortran_example" version = "0.1.0" license = "license" author = "Jane Doe" maintainer = "jane.doe@example.com" copyright = "Copyright 2021, Jane Doe" [build] auto-executables = true auto-tests = true auto-examples = true [install] library = false [dependencies] toml-f = { git = "https://github.com/toml-f/toml-f", tag = "v0.2.1" } ``` Now modify `app/main.f90` to use `tomlf`: ```fortran program main use tomlf, only: gettomlfversion implicit none integer :: major integer :: minor integer :: patch call gettomlfversion(major, minor, patch) print *, "tomlf's major version is: ", major print *, "tomlf's minor version is: ", minor print *, "tomlf's patch version is: ", patch end program main ``` Execute `fpm build` to build the fortran project. Now you can call `fpm run` to execute the built application, here is an example output from this application: ``` tomlf's major version is: 0 tomlf's minor version is: 2 tomlf's patch version is: 1 ``` To analyze this project using fossa CLI, execute `fossa analyze --output --debug`. This will print identified dependency graphs and debug logs only. It will not upload the performed analysis to any endpoint.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_addresses.md

+++ title = "googlecomputeaddresses resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeaddresses" identifier = "inspec/resources/gcp/googlecomputeaddresses.md googlecomputeaddresses resource" parent = "inspec/resources/gcp" +++ A `googlecomputeaddresses` is used to test a Google Address resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeaddresses(project: 'chef-gcp-inspec', location: 'europe-west2') do its('addresses') { should include '10.2.0.3' } its('names') { should include 'inspec-gcp-global-address' } end ``` Properties that can be accessed from the `googlecomputeaddresses` resource: See the resource for more information. `addresses` : an array of `googlecomputeaddress` address `address_types` : an array of `googlecomputeaddress` address_type `creation_timestamps` : an array of `googlecomputeaddress` creation_timestamp `descriptions` : an array of `googlecomputeaddress` description `ids` : an array of `googlecomputeaddress` id `names` : an array of `googlecomputeaddress` name `purposes` : an array of `googlecomputeaddress` purpose `network_tiers` : an array of `googlecomputeaddress` network_tier `subnetworks` : an array of `googlecomputeaddress` subnetwork `users` : an array of `googlecomputeaddress` users `labels` : (Beta only) an array of `googlecomputeaddress` labels `label_fingerprints` : (Beta only) an array of `googlecomputeaddress` label_fingerprint `statuses` : an array of `googlecomputeaddress` status `regions` : an array of `googlecomputeaddress` region This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.32.md

layout: release date: 2021-07-09 tag: v0.5.32 Fix RJSF stale state issue @utkarsh-pro (#3418) Add login and logout command to mesheryctl @utkarsh-pro (#3396) Bump github.com/layer5io/meshsync from 0.1.21 to 0.1.23 @dhruv0000 (#3416) Changed the port , added prefix and the namespace into the istio yml @samirparhi-dev (#3232) broker connection issue fixed for plugins @kumarabd (#3403) [UI] New Notification Design implementation @jeantiston (#3197) Gracefully handling invalid meshconfig errors @metonymic-smokey (#3198) E2E demo plugins @killbotXD (#3404) [Chore] Update in roadmap @piyushsingariya (#3392) Actions Enhancement for Meshery Patterns @Chadha93 (#3345) Updated the meshkit error for schedule_handler.go @Shreyas220 (#3384) Updated the meshkit error for loadtestmeshes_handler.go @debjani1413 (#3381) [Docs] Release Notes for Meshery v0.5.32 @l5io (#3388) [Unit Testing] Unit Testing for @piyushsingariya (#3288) move codecov from root to .github @suhaniii (#3377) [README] add: Community Forum @amino19 (#3272) Thank you to our contributors for making this release possible: @Aisuko, @Chadha93, @Nikhil-Ladha, @Shreyas220, @amino19, @debjani1413, @dhruv0000, @hexxdump, @jeantiston, @killbotXD, @kumarabd, @l5io, @leecalcote, @metonymic-smokey, @navendu-pottekkat, @piyushsingariya, @samirparhi-dev, @suhaniii, @utkarsh-pro and l5io
Project: ArangoDB (App Definition and Development / Database)
File: equality_basic_result.md

+++ title = "`bool operator==(const basic_result<A, B, C> &) const`" description = "Returns true if this result compares equal to the other result. Constexpr and noexcept propagating." categories = ["comparisons"] weight = 800 +++ Returns true if this result compares equal to the other result. Comparison is done using `operator==` on either `valuetype` or `errortype` if the currently chosen state is the same for both results, otherwise false is returned. Requires: `operator==` must be a valid expression between `valuetype` and `A`, and between `errortype` and `B`. If `valuetype` is `void`, then so must be `A`; similarly for `errortype` and `B`. Complexity: Whatever the underlying `operator==` have. Constexpr and noexcept of underlying operations is propagated. Guarantees: None. Free function alias: There is a free function `bool operator==(const basicresult<A, B, C> &, const basicoutcome<A, B, C, D> &)` which forwards perfectly to this function, by reversing the operands.
Project: ArangoDB (App Definition and Development / Database)
File: hook_outcome_construction.md

+++ title = "`void hookoutcomeconstruction(T *, U &&) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the implicit constructors of `basic_outcome`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onoutcomeconstruction(T *, U &&) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the implicit constructors of `basicoutcome`. See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_outcome.hpp>`
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_filestore_instance.md

+++ title = "googlefilestoreinstance resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlefilestoreinstance" identifier = "inspec/resources/gcp/googlefilestoreinstance.md googlefilestoreinstance resource" parent = "inspec/resources/gcp" +++ A `googlefilestoreinstance` is used to test a Google Instance resource ```ruby describe googlefilestoreinstance(project: 'chef-gcp-inspec', zone: 'us-central1-b', name: 'inspecgcp') do it { should exist } its('tier') { should cmp 'PREMIUM' } its('file_shares.count') { should cmp 1 } its('fileshares.first.capacitygb') { should cmp '2660' } its('file_shares.first.name') { should cmp 'inspecgcp' } its('networks.count') { should cmp 1 } its('networks.first.network') { should cmp 'default' } its('networks.first.modes') { should include 'MODE_IPV4' } end describe googlefilestoreinstance(project: 'chef-gcp-inspec', zone: 'us-central1-b', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlefilestoreinstance` resource: `name` : The resource name of the instance. `description` : A description of the instance. `create_time` : Creation timestamp in RFC3339 text format. `tier` : The service tier of the instance. Possible values: TIER_UNSPECIFIED STANDARD PREMIUM `labels` : Resource labels to represent user-provided metadata. `file_shares` : File system shares on the instance. For this version, only a single file share is supported. `name` : The name of the fileshare (16 characters or less) `capacity_gb` : File share capacity in GiB. This must be at least 1024 GiB for the standard tier, or 2560 GiB for the premium tier. `networks` : VPC networks to which the instance is connected. For this version, only a single network is supported. `network` : The name of the GCE VPC network to which the instance is connected. `modes` : IP versions for which the instance has IP addresses assigned. `reservediprange` : A /29 CIDR block that identifies the range of IP addresses reserved for this instance. `ip_addresses` : A list of IPv4 or IPv6 addresses. `etag` : Server-specified ETag for the instance resource to prevent simultaneous updates from overwriting each other. `zone` : The name of the Filestore zone of the instance.