cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: cgroup.md

+++ title = "cgroup resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "cgroup" identifier = "inspec/resources/os/cgroup.md cgroup resource" parent = "inspec/resources/os" +++ Use the `cgroup` Chef InSpec audit resource to test the different parameters values of the control group (cgroup) resource controllers. A cgroup is a Linux kernel feature that limits, accounts, and isolates the resource usage (such as CPU, memory, disk I/O, network) of a collection of processes. This resource is distributed with Chef InSpec. describe cgroup("CARROTKING") do its("cpuset.cpus") { should eq 0 } end where `cpuset.cpus` is a property of this resource and a parameter of the cpuset resource controller. `CARROTKING` is the name of cgroup directory. All parameters of the cgroup resource controller are valid properties of this resource. Some of them are: `cpuset.cpus`, `memory.limitinbytes`, `memory.stat`, `freezer.state`, `cpu.stat`, `cpuacct.usage`, `pids.current`, `blkio.throttle.ioservicebytes`. For a full list of available matchers, refer . The matchers applicable for this resource are: `eq`, `cmp`, and `match`. `eq` tests whether the two values are of same data type and includes configuration entries that are numbers. It fails if the types do not match. Use `cmp` for less restrictive comparisons that ignores data type while comparing. Unlike `eq`, `cmp` is a matcher for less-restrictive comparisons. This matcher attempts to fit the actual value to the comparing type and meant to relieve the user from having to write type-casts and resolutions. `match` checks if a string matches a regular expression. Use `match` when the output of `cgget -n -r [subsystem.parameters] [cgroup-name]` is a multi-line output. The following examples show how to use this Chef InSpec audit resource. Use `eq` to test for parameters that have a single line integer value. The value considered is the output obtained on `cgget -n -r [subsystem.parameters] [cgroup-name]`. describe cgroup("CARROTKING") do its("cpuset.cpus") { should eq 0 } end Use `cmp` to test for parameters with less-restrictive comparisons and has a single line integer value. The value considered is the output obtained on `cgget -n -r [subsystem.parameters] [cgroup-name]`. describe cgroup("CARROTKING") do its("memory.limitinbytes") { should cmp 9223372036854771712 } end Use `match` to test for parameters that have multi-line values and can be passed as regex. The value considered is the output obtained on `cgget -n -r [subsystem.parameters] [cgroup-name]`. describe cgroup("CARROTKING") do its("memory.stat") { should match /\bhierarchicalmemorylimit 9223372036854771712\b/ } end
Project: ClickHouse (App Definition and Development / Database)
File: v21.2.10.48-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Set `backgroundfetchespool_size` to 8 that is better for production usage with frequent small insertions or slow ZooKeeper cluster. (). Backported in : Raised the threshold on max number of matches in result of the function `extractAllGroupsHorizontal`. (). Backported in : Fixed a bug with unlimited wait for auxiliary AWS requests. (). Backported in : Fix error `Cannot find column in ActionsDAG result` which may happen if subquery uses `untuple`. Fixes . (). Backported in : Some values were formatted with alignment in center in table cells in `Markdown` format. Not anymore. (). LibraryDictionarySource fix possible leak ().
Project: YugabyteDB (App Definition and Development / Database)
File: opt-yb-build.md

<!-- +++ private = true +++ --> By default, when running build, third-party libraries are not built, and pre-built libraries are downloaded. We also use to provide some of the third-party dependencies. The build scripts automatically install these in directories under `/opt/yb-build`. In order for the build script to write under those directories, it needs proper permissions. One way to do that is as follows: ```sh sudo mkdir /opt/yb-build sudo chown "$USER" /opt/yb-build ``` Alternatively, specify the build options `--no-download-thirdparty` and/or `--no-linuxbrew`. Note that those options may require additional, undocumented steps.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_upgrade_software.md

Software upgrade for a YugabyteDB Anywhere Universe Software upgrade for a YugabyteDB Anywhere Universe ``` yba universe upgrade software [flags] ``` ``` --yb-db-version string [Required] Target YugabyteDB software version. --upgrade-option string [Optional] Upgrade Options, defaults to Rolling. Allowed values (case sensitive): Rolling, Non-Rolling (involves DB downtime) (default "Rolling") --upgrade-system-catalog [Optional] Upgrade System Catalog after software upgrade, defaults to true. (default true) --delay-between-master-servers int32 [Optional] Upgrade delay between Master servers (in miliseconds). (default 18000) --delay-between-tservers int32 [Optional] Upgrade delay between Tservers (in miliseconds). (default 18000) -h, --help help for software ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -f, --force [Optional] Bypass the prompt for non-interactive usage. -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Required] The name of the universe to be ugraded. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") -s, --skip-validations [Optional] Skip validations before running the CLI command. --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Upgrade a YugabyteDB Anywhere universe
Project: Chef InSpec (Provisioning / Security & Compliance)
File: aide_conf.md

+++ title = "aide_conf resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "aide_conf" identifier = "inspec/resources/os/aideconf.md aideconf resource" parent = "inspec/resources/os" +++ Use the `aide_conf` Chef InSpec audit resource to test the rules established for the file integrity tool AIDE. Controlled by the aide.conf file typically at /etc/aide.conf. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.37.6 of InSpec. An `aide_conf` resource block can be used to determine if the selection lines contain one (or more) directories whose files should be added to the aide database: describe aide_conf('path') do its('selection_lines') { should include '/sbin' } end where `'selection_lines'` refers to all selection lines found in the aide.conf file `('path')` is the non-default path to the `aide.conf` file (optional) `should include 'value'` is the value that is expected Use the where clause to match a selection_line to one rule or a particular set of rules found in the aide.conf file: describe aideconf.where { selectionline == '/bin' } do its('rules.flatten') { should include 'r' } end describe aideconf.where { selectionline == '/sbin' } do its('rules') { should include ['p', 'i', 'l', 'n', 'u', 'g', 'sha512'] } end The `rules` property returns the list of rules set in the `aide.conf` file. its('rules') { should include ['r', 'sha512'] } The `allhaverule` property returns the all selected lines from `aide.conf` file e.g. 'p', 'i' etc. aideconf.allhave_rule('sha512') The `selection_lines` property returns the list of lines from `aide.conf` file. its('selection_lines') { should include '/sbin' } The following examples show how to use this Chef InSpec audit resource. describe aideconf.allhave_rule('xattr') do it { should eq true } end describe aideconf.where { selectionline == '/bin' } do its('rules.flatten') { should include 'r' } end describe aideconf.where { selectionline == '/sbin' } do its('rules') { should include ['r', 'sha512'] } end describe aideconf.allhave_rule('sha512') do it { should eq true } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: read-only-tmpfs.md

When running --read-only containers, mount a read-write tmpfs on /dev, /dev/shm, /run, /tmp, and /var/tmp. The default is true. | --read-only | --read-only-tmpfs | / | /run, /tmp, /var/tmp| | -- | -- | - | -- | | true | true | r/o | r/w | | true | false | r/o | r/o | | false | false | r/w | r/w | | false | true | r/w | r/w | When --read-only=true and --read-only-tmpfs=true additional tmpfs are mounted on the /tmp, /run, and /var/tmp directories. When --read-only=true and --read-only-tmpfs=false /dev and /dev/shm are marked Read/Only and no tmpfs are mounted on /tmp, /run and /var/tmp. The directories are exposed from the underlying image, meaning they are read-only by default. This makes the container totally read-only. No writable directories exist within the container. In this mode writable directories need to be added via external volumes or mounts. By default, when --read-only=false, the /dev and /dev/shm are read/write, and the /tmp, /run, and /var/tmp are read/write directories from the container image.
Project: KICS (Provisioning / Security & Compliance)
File: 456b00a3-1072-4149-9740-6b8bb60251b0.md

title: S3 Bucket Allows Restore Actions From All Principals hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 456b00a3-1072-4149-9740-6b8bb60251b0 Query name: S3 Bucket Allows Restore Actions From All Principals Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: S3 Buckets must not allow Restore Actions From All Principals, as to prevent leaking private information to the entire internet or allow unauthorized data tampering / deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is Restore, for all Principals.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="22 7" Resources: SampleBucketPolicy3: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: "RestoreObject" Effect: Allow Resource: "*" Principal: "*" Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' SampleBucketPolicy4: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: "RestoreObject" "GetObject" Effect: Allow Resource: "*" Principal: "*" Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' ``` ```json title="Positive test num. 2 - json file" hl_lines="9 35" { "Resources": { "SampleBucketPolicy5": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": "RestoreObject", "Effect": "Allow", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } }, "SampleBucketPolicy6": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": [ "RestoreObject", "GetObject" ], "Effect": "Allow", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: SampleBucketPolicy1: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: 's3:RestoreObject' Effect: Deny Resource: '*' Principal: '*' Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' ``` ```json title="Negative test num. 2 - json file" { "Resources": { "SampleBucketPolicy2": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": [ "s3:RestoreObject" ], "Effect": "Deny", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } } } } ```
Project: YDB (App Definition and Development / Database)
File: create_topic.md

The `CREATE TOPIC` call creates a . When creating a topic, you can add topic to it and topic settings. ``` CREATE TOPIC topic_path ( CONSUMER consumer1, CONSUMER consumer2 WITH (setting1 = value1) ) WITH ( topic_setting2 = value2 ); ``` All the parameters except the topic name are optional. By default, a topic is created without consumers. All the omitted settings are also set by default (both for the topic and its consumers). Creating a topic without consumers with default settings: ```sql CREATE TOPIC `my_topic`; ``` Creating a topic with a single consumerandthe important option enabled: ```sql CREATE TOPIC `my_topic` ( CONSUMER my_consumer WITH (important = true) ); ``` `important`: Defines an important consumer. No data will be deleted from the topic until all the important consumers read them. Value type: `boolean`, default value: `false`. `read_from`: Sets up the message write time starting from which the consumer will receive data. Data written beforethis timewill not be read. Value type: `Datetime` OR `Timestamp` OR `integer` (unix-timestamp in the numeric format). Default value: `now`. {% if featuretopiccodecs %} `supported_codecs`: List of supported by the consumer. {% endif %} Creating a topicwith the retention period of oneday: ```sql CREATE TOPIC `my_topic` WITH( retention_period = Interval('P1D') ); ``` `minactivepartitions`: Minimum number of topic partitions. During automatic load balancing, the number of active partitions will not decreasebelow this value. Value type: `integer`, default value: `1`. `partitioncountlimit`: Maximum number of active partitions in the topic. `0` is interpreted as unlimited. Value type: `integer`, default value: `0`. `retention_period`: Data retention period in the topic. Value type: `Interval`, default value: `18h`. `retentionstoragemb`: Limit on the maximum disk space occupied by the topic data. When this value is exceeded, the older data is cleared, like under a retention policy. `0` is interpreted as unlimited. Value type: `integer`, default value: `0` `partitionwritespeedbytesper_second`: Maximum allowed write speed per partition. If a write speed for a given partitionexceeds this value, the write speed will be capped. Value type: `integer`, default value: `2097152` (2MB). `partitionwriteburstbytes`: Write quota allocated for write bursts. When set to zero, the actual writeburst value is equalled to the quota value (this allows write bursts ofup to one second). Value type: `integer`, default value: `0`. `meteringmode`: Resource metering mode (`RESERVEDCAPACITY` - based on the allocated resources or `REQUEST_UNITS` - based on actual usage). This option applies to topics in serverless databases. Value type: `String`. {% if featuretopiccodecs %} `supported_codecs`: List of supported by the topic. Value type: `String`. {% endif %}
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.52.md

layout: release date: 2021-08-30 tag: v0.5.52 [UI] Change Pre-commit lint command to allow users to push formatted changes @sudo-NithishKarthik (#4014) [chore] Minor chore @piyushsingariya (#4036) [CI] Upgraded Code Coverage line-by-line @shikharvashistha (#4033) fixing recent mesheryctl system start panic @Revolyssup (#4035) [UI] [Connection Wizard] Add 'Configuration Done' step @sudo-NithishKarthik (#4016) Capitalize Lables and remove margins from RJSF tooltip @killbotXD (#4007) [UI] [Connection Wizard] Fix Metrics icon overlap in Stepper @sudo-NithishKarthik (#4017) [UI] [Connection Wizard] Render adapter icons dynamically @sudo-NithishKarthik (#4018) [UI] [Connection Wizard] Add loading spinner for operator and kubernetes step @sudo-NithishKarthik (#4019) [UI] [Connection Wizard] Use black and white image for meshery logo in adapters page @sudo-NithishKarthik (#4011) [UI] fix continuous subscription initialization @bariqhibat (#4032) Thank you to our contributors for making this release possible: @Revolyssup, @bariqhibat, @killbotXD, @leecalcote, @navendu-pottekkat, @piyushsingariya, @shikharvashistha and @sudo-NithishKarthik
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-cache-uncache-table.md

layout: global title: UNCACHE TABLE displayTitle: UNCACHE TABLE 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. `UNCACHE TABLE` removes the entries and associated data from the in-memory and/or on-disk cache for a given table or view. The underlying entries should already have been brought to cache by previous `CACHE TABLE` operation. `UNCACHE TABLE` on a non-existent table throws an exception if `IF EXISTS` is not specified. ```sql UNCACHE TABLE [ IF EXISTS ] table_identifier ``` table_identifier* Specifies the table or view name to be uncached. The table or view name may be optionally qualified with a database name. Syntax: `[ databasename. ] tablename` ```sql UNCACHE TABLE t1; ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: fix-12814.en.md

Handle several errors in `/clients/{clientid}/mqueuemessages` and `/clients/{clientid}/inflightmessages` APIs: Internal timeout, which means that EMQX failed to get the list of Inflight/Mqueue messages within the default timeout of 5 s. This error may occur when the system is under a heavy load. The API will return 500 `{"code":"INTERNAL_ERROR","message":"timeout"}` response and log additional details. Client shutdown. The error may occur if the client connection is shutdown during the API call. The API will return 404 `{"code": "CLIENT_SHUTDOWN", "message": "Client connection has been shutdown"}` response in this case.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.4.1.en.md

Resolved compatibility issues with Open Telemetry configurations defined in `emqx.conf` from versions before EMQX 5.4.0, ensuring smooth integration of legacy configurations with the latest EMQX release. Fixed client ID generation in MQTT broker data integration to comply with MQTT 3.1 specification of 23-byte limit. Client ID is now prefixed with user-assigned connector name, followed by the first 8 bytes of node name's SHA hash and pool member ID. If the resulting ID exceeds 23 bytes, additional SHA hash and truncation are applied to ensure compliance. Resolved compatibility issue with the error format configurations introduced in the HTTP Action feature of EMQX version 5.3.2. Stopped exposing port 11883 by default in Docker and removed it from Helm charts, as this port is no longer in use. Fixed an issue in the `/configs` API where attempting to modify a read-only configuration value resulted in a garbled response message. Fix rolling upgrade when replica nodes join cluster with core nodes prior to version 5.4.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.41.0-zh.md

pipelinego1.22, : @tomqin93 Bump golang.org/x/crypto from 0.19.0 to 0.21.0 by @dependabot in Bump github.com/microsoft/go-mssqldb from 1.6.0 to 1.7.0 by @dependabot in Bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.9.2 to 1.10.0 by @dependabot in Bump go.uber.org/zap from 1.26.0 to 1.27.0 by @dependabot in Bump github.com/onsi/gomega from 1.30.0 to 1.32.0 by @dependabot in Bump github.com/Azure/azure-sdk-for-go/sdk/ai/azopenai from 0.4.1 to 0.5.0 by @dependabot in Bump github.com/taosdata/driver-go/v3 from 3.5.2 to 3.5.3 by @dependabot in Bump k8s.io/client-go from 0.29.2 to 0.29.3 by @dependabot in Bump github.com/go-sql-driver/mysql from 1.7.1 to 1.8.1 by @dependabot in Bump github.com/onsi/ginkgo/v2 from 2.15.0 to 2.17.1 by @dependabot in Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.40.0...v0.41.0
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.46.md

layout: release date: 2024-04-10 tag: v0.7.46 [Cleanup] Remove unnecessary files added by publish workflow @Yashsharma1911 (#10684) bump meshkit to v0.7.21 @MUzairS15 (#10682) Fix nil pointer error when importing Helm chart @Yashsharma1911 (#10707) remove extra strings from integration docs body @vishalvivekm (#10698) Include Cloud as a Target in the Publish Workflow @Yashsharma1911 (#10683) [mesheryctl] Fix `publish` command failure @MUzairS15 (#10681) MeshModelComponent.js Component search fixed @Aryakoste (#10686) Make tabs `scrollable` for mobile screens @sudhanshutech (#10689) fix improper passing and usage of props @MUzairS15 (#10674) Fix nil pointer error when importing Helm chart @Yashsharma1911 (#10707) fix : Local Provider: Designs fail to load @Adarsh-jaiss (#10692) Include Cloud as a Target in the Publish Workflow @Yashsharma1911 (#10683) Update cleanup script to check for "Terminating" namespaces and patch finalizers field @cpepper96 (#10680) Fix cloud path in integration workflow @Yashsharma1911 (#10696) Include Cloud as a Target in the Publish Workflow @Yashsharma1911 (#10683) Update to contributing-docs for issue #9976 @sangramrath (#10533) update css for mobile view @vishalvivekm (#10706) Update Relationship documentation. @RipulHandoo (#10690) Revert "Create enhanced.html" @vishalvivekm (#10697) update integrations pages to use integration layout @vishalvivekm (#10695) Create enhanced.html @vishalvivekm (#10688) Thank you to our contributors for making this release possible: @Adarsh-jaiss, @Aryakoste, @MUzairS15, @RipulHandoo, @Yashsharma1911, @aabidsofi19, @cpepper96, @leecalcote, @sangramrath, @sudhanshutech, @vishalvivekm and Jerod Culpepper
Project: ClickHouse (App Definition and Development / Database)
File: v21.1.5.4-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Mark distributed batch as broken in case of empty data block in one of files. (). Backported in : The function `greatCircleAngle` returned inaccurate results in previous versions. This closes . (). Backported in : Fixed the behavior when in case of broken JSON we tried to read the whole file into memory which leads to exception from the allocator. Fixes . (). Backported in : Check if table function `view` is used in expression list and throw an error. This fixes . (). Backported in : Fix `LOGICALERROR` for `joinuse_nulls=1` when JOIN contains const from SELECT. (). Backported in : Fix subquery with union distinct and limit clause. close . (). Backported in : Fix usage of `-Distinct` combinator with `-State` combinator in aggregate functions. (). Backported in : `USE database;` query did not work when using MySQL 5.7 client to connect to ClickHouse server, it's fixed. Fixes . ().
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Watcher.md

/ / Watcher .Watcher init(`pusher`): `void` the table renderer will call this function when the DOM is ready to accept updates. when you have updates, please call one or the other of the provided functions | Name | Type | | :- | : | | `pusher` | | `void`