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

To move lua_project to dragonfly from helio (DONE) To limit lua stack to something reasonable like 4096. To inject our own allocator to lua to track its memory. Currently our transactional and locking model is based on an assumption that any READ or WRITE access to objects must be performed in a shard where they belong. However, this assumption can be relaxed to get significant gains for read-only queries. Our transactional framework prevents from READ-locked objects to be mutated. It does not prevent from their PrimaryTable to grow or change, of course. These objects can move to different entries inside the table. However, our CompactObject maintains the following property - its reference CompactObject.AsRef() is valid no matter where the master object moves and it's valid and safe for reading even from other threads. The exception regarding thread safety is SmallString which uses translation table for its pointers. If we change the SmallString translation table to be global and thread-safe (it should not have lots of write contention anyway) we may access primetable keys and values from another thread and write them directly to sockets. Use-case: large strings that need to be copied. Sets that need to be serialized for SMEMBERS/HGETALL commands etc. Additional complexity - we will need to lock those variables even for single hop transactions and unlock them afterwards. The unlocking hop does not need to increase user-visible latency since it can be done after we send reply to the socket.
Project: ArangoDB (App Definition and Development / Database)
File: narrow_error_check.md

+++ title = "`static void narrowerrorcheck(Impl &&) noexcept`" description = "Observer policy performing hard UB if no error is present. Constexpr, never throws." categories = ["observer-policies"] weight = 410 +++ Observer policy performing hard UB if no error is present, by calling {{% api "static void _ub(Impl &&)" %}}. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: Athenz (Provisioning / Key Management)
File: dev_environment.md

* * * * If you would like to build your own copy of Athenz rather than using the pre-built binary packages, then here is the list of development tools you need to have installed on your system. You can replicate the container environment that Athenz users within Screwdriver to build and deploy Athenz packages. You can start a new container using the `openjdk:11` image. Once you check out the Athenz source tree, you can execute the `install_deps.sh` script to install the required development tools: ```shell $ git clone https://github.com/AthenZ/athenz.git $ cd athenz $ sh screwdriver/scripts/install_deps.sh ``` To build Athenz components, you must have Java Platform JDK 11 installed on your machine. The main authorization services - ZMS and ZTS, are written in Java and using embedded Jetty. Make sure you have set the $JAVA_HOME environment variable. ```shell $ java -XshowSettings:properties -version 2>&1 > /dev/null | grep 'java.home' $ export JAVA_HOME=<java-home-directory> ```` Download and install . If you don't have git client installed on your host, you can download one from . 2.x version of the git client is required. Install go 1.22.3 or newer version by following the directions at . Make sure you have set the and that you have `$GOPATH/bin` in your `$PATH`. ```shell $ export GOPATH=<gopath-directory> $ mkdir -p $GOPATH/bin $ export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin ```` Install node 18.x by following the directions at Verify that you have the required minimum version of `node`, `npm` and `nodemon` binaries installed on your system and are included in your runtime path: ```shell $ node --version v18.19.0 $ npm -v 10.3.0 $ npm install -g nodemon $ nodemon --version 3.0.3 ``` To build Athenz components, change to the top level directory where you want to build the Athenz code and execute (skip the first command if you have already checked out the code using git): ```shell $ git clone https://github.com/AthenZ/athenz.git $ cd athenz $ mvn clean install ``` The release packages will be created automatically in the `assembly` subdirectory.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.34.md

layout: release date: 2024-03-19 tag: v0.7.34 fix model registration getting blocked due to error @MUzairS15 (#10584) Feat: Update model generator @Yashsharma1911 (#10576) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911 and @leecalcote
Project: YugabyteDB (App Definition and Development / Database)
File: diagnostics-reporting.md

title: Diagnostics reporting headerTitle: Diagnostics reporting linkTitle: Diagnostics reporting description: Enable diagnostics reporting and set collection levels on YB-Master and YB-TServer nodes. menu: v2.18: identifier: diagnostics-reporting parent: manage weight: 706 type: docs The and nodes report cluster diagnostics to the YugabyteDB diagnostics service every time a new cluster gets created and every hour thereafter. User data stored in YugabyteDB as well as any personally identifiable information regarding the user is never collected or reported. The data collected depends on the collection level set. See below on how to change the collection level. ``` Collection time Cluster uuid Node uuid Node type (tserver or master) Number of masters (yb-master processes) Number of tablet servers (yb-tserver processes) Number of tables Number of tablets Cluster configuration (gflags) Host name (for each node where yb-master and yb-tserver processes are running) Username (for each node where yb-master and yb-tserver processes are running) ``` ``` Everything we collect for level low plus: Performance metrics RPC metrics ``` Same as `medium` level. In other words, no extra information is collected for this level. It will be used in the future to collect additional diagnostics information such as error logs. ``` [ { "type": "tablet", "id": "eca8b3cfb2ee4eca94dde519634e1e38", "attributes": { "partition": "hash_split: [16380, 19110)", "table_name": "redis", "table_id": "82f5f7ab81a44923b5f544fbd0664afe" }, "metrics": [ { "name": "logreaderbytes_read", "value": 0 }, { "name": "logreaderentries_read", "value": 0 }, { "name": "logreaderreadbatchlatency", "total_count": 0, "min": 0, "mean": 0, "percentile_75": 0, "percentile_95": 0, "percentile_99": 0, "percentile999": 0, "percentile9999": 0, "max": 0, "total_sum": 0 } ] } } ``` ``` { "inbound_connections": [ { "remote_ip": "10.150.0.20:41134", "state": "OPEN", "remoteusercredentials": "{realuser=yugabyte, effuser=}", "processedcallcount": 2456 }, { "remote_ip": "10.150.0.20:54141", "state": "OPEN", "remoteusercredentials": "{realuser=yugabyte, effuser=}", "processedcallcount": 2471 } ] } ``` You can add the following configuration flags while starting the and nodes to configure the diagnostics reporting behavior of YugabyteDB. Flag | Default | Description -|| `--callhomecollectionlevel` | `medium` | Collection level with possible values of `low`, `medium`, or `high` `--callhomeintervalsecs` | 3600 | Collection interval in seconds `--callhome_url ` | `http://diagnostics.yugabyte.com` | Endpoint where diagnostics information is reported `--callhome_enabled` | `true` | Controls whether diagnostics information is collected and reported. Set to `false` to disable collection.
Project: KICS (Provisioning / Security & Compliance)
File: f1adc521-f79a-4d71-b55b-a68294687432.md

title: EC2 Instance Using Default Security Group hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f1adc521-f79a-4d71-b55b-a68294687432 Query name: EC2 Instance Using Default Security Group Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: EC2 instances should not use default security group(s)<br> ```tf title="Positive test num. 1 - tf file" hl_lines="9" resource "aws_instance" "positive1" { ami = data.aws_ami.ubuntu.id instance_type = "t3.micro" tags = { Name = "HelloWorld" } securitygroups = [awssecurity_group.default.id] } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="6" resource "aws_instance" "positive2" { ami = "ami-003634241a8fcdec0" instance_type = "t2.micro" vpcsecuritygroupids = [awssecurity_group.default.id] } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_instance" "negative1" { ami = data.aws_ami.ubuntu.id instance_type = "t3.micro" tags = { Name = "HelloWorld" } securitygroups = [awssecurity_group.sg.id] } ``` ```tf title="Negative test num. 2 - tf file" resource "aws_instance" "negative2" { ami = "ami-003634241a8fcdec0" instance_type = "t2.micro" vpcsecuritygroupids = [awssecurity_group.sg.id] } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.71.md

layout: release date: 2021-11-05 tag: v0.5.71 fixed #4571 @Revolyssup (#4572) [Broker] add broker url to handler config @bariqhibat (#4545) [meshery server]Sqlite migration | CU-1h1xjj2 @Revolyssup (#4333) [UI] Counter in Performance Profile fixed @ruhi09 (#4518) Fix issue 4411 (intermittent ci fail on cypress 'search Cluster Deployment & ping k8s cluster' integration test) @MarioArriaga92 (#4568) [UI] custom table header for selected row @theBeginner86 (#4566) Fix JSHint W014 @100mik (#4410) Fix issue 4411 (intermittent ci fail on cypress 'search Cluster Deployment & ping k8s cluster' integration test) @MarioArriaga92 (#4568) Deprication notice for Kubernetes manifests and update Helm install instructions @navendu-pottekkat (#4514) added the same structure for spanish page as it is for english page @shubham-tyagi (#4558) Add the Broker page in spanish @chal-gro (#4378) Updated the Docs @ruhi09 (#4478) Updated Load-generator.md @Rahulkumar2002 (#4548) Add earliest supported service mesh version to each adapter @Shreyas220 (#4524) fix routing for system redirects @sidecodes (#4564) docs: fix language in functionality @sidecodes (#4562) [Security] nats-serverv2 CVE-2021-3127 @leecalcote (#4575) [Security] opencontainers/runc v1.0.0-rc95 // indirect; CVE-2021-30465 @leecalcote (#4574) Fix JSHint W014 @100mik (#4410) Thank you to our contributors for making this release possible: @100mik, @MarioArriaga92, @Rahulkumar2002, @Revolyssup, @Shreyas220, @adithyaakrishna, @bariqhibat, @chal-gro, @leecalcote, @navendu-pottekkat, @ruhi09, @shubham-tyagi, @sidecodes, @theBeginner86, @utkarsh-pro and @warunicorn19
Project: StarRocks (App Definition and Development / Database)
File: SHOW_PIPES.md

displayed_sidebar: "English" Lists the pipes stored in a specified database or in the current database in use. This command is supported from v3.2 onwards. ```SQL SHOW PIPES [FROM <db_name>] [ WHERE [ NAME { = "<pipename>" | LIKE "pipematcher" } ] [ [AND] STATE = { "SUSPENDED" | "RUNNING" | "ERROR" } ] ] [ ORDER BY <field_name> [ ASC | DESC ] ] [ LIMIT { [offset, ] limit | limit OFFSET offset } ] ``` The name of the database for which you want to query pipes. If you do not specify this parameter, the system returns the pipes for the current database in use. The criteria based on which to query pipes. The field by which you want to sort the records returned. The maximum number of records you want the system to return. The command output consists of the following fields. | Field | Description | | - | | | DATABASE_NAME | The name of the database in which the pipe is stored. | | PIPE_ID | The unique ID of the pipe. | | PIPE_NAME | The name of the pipe. | | TABLE_NAME | The name of the destination StarRocks table. | | STATE | The status of the pipe. Valid values: `RUNNING`, `FINISHED`, `SUSPENDED`, and `ERROR`. | | LOAD_STATUS | The overall status of the data files to be loaded via the pipe, including the following sub-fields:<ul><li>`loadedFiles`: the number of data files that have been loaded.</li><li>`loadedBytes`: the volume of data that has been loaded, measured in bytes.</li><li>`LastLoadedTime`: the date and time when the last data file was loaded. Format: `yyyy-MM-dd HH:mm:ss`. Example: `2023-07-24 14:58:58`.</li></ul> | | LAST_ERROR | The details about the last error that occurred during the pipe execution. Default value: `NULL`. | | CREATED_TIME | The date and time when the pipe was created. Format: `yyyy-MM-dd HH:mm:ss`. Example: `2023-07-24 14:58:58`. | Switch to the database named `mydatabase` and show all the pipes in it: ```SQL USE mydatabase; SHOW PIPES \G ``` Switch to the database named `mydatabase` and show the pipe named `userbehaviorreplica` in it: ```SQL USE mydatabase; SHOW PIPES WHERE NAME = 'userbehaviorreplica' \G ```
Project: YugabyteDB (App Definition and Development / Database)
File: subscribe.md

title: SUBSCRIBE linkTitle: SUBSCRIBE description: SUBSCRIBE menu: preview: parent: api-yedis weight: 2552 aliases: /preview/api/redis/subscribe /preview/api/yedis/subscribe type: docs `SUBSCRIBE` `SUBSCRIBE channel [channel ...]` This command subscribes the client to the specified channel(s). The client will receive a message whenever a publisher sends a message to any of the channels that it has subscribed to. , , , , ,
Project: ClickHouse (App Definition and Development / Database)
File: current-roles.md

slug: /en/operations/system-tables/current-roles Contains active roles of a current user. `SET ROLE` changes the contents of this table. Columns: `role_name` ()) Role name. `withadminoption` () Flag that shows whether `current_role` is a role with `ADMIN OPTION` privilege. `isdefault` () Flag that shows whether `currentrole` is a default role.
Project: Stolon (App Definition and Development / Database)
File: postgres_parameters.md

The unique central point for managing the postgresql parameters is the `pgParameters` map. This makes easy to centrally manage and keep in sync the postgresql paramaters of all the db instances in the cluster. The keepers will generate a `postgresql.conf` that contains the parameters defined in the `pgParameters` map. The user can change the parameters at every time and the keepers will update the `postgresql.conf` and reload the instance. If some parameters needs an instance restart to be applied this should be manually done by the user restarting the keepers. These parameters, if defined in the cluster specification, will be ignored since they are managed by stolon and cannot be defined by the user: ``` listen_addresses port unixsocketdirectories walkeepsegments walloghints hot_standby maxreplicationslots maxwalsenders synchronousstandbynames ``` since stolon requires a `wallevel` value of at least `replica` (or `hotstandby` for pg < 9.6) if you leave it unspecificed in the `pgParameters` or if you specify a wrong `wallevel` or a value lesser than `replica` or `hotstandby` (like `minimal`) it'll be overridden by the minimal working value (`replica` or `hot_standby`). i.e. if you want to also save logical replication information in the wal files you can specify a `wal_level` set to `logical`. Actually stolon doesn't do any check on the provided configurations, so, if the provided parameters are wrong this won't create problems at instance reload (just some warning in the postgresql logs) but at the next instance restart, it'll probably fail making the instance not available (thus triggering failover if it's the master or other changes in the clusterview). When , by default, stolon will merge in the cluster spec the parameters that the instance had at the end of the initialization, practically: When initMode is new, it'll merge the initdb generated parameters. When initMode is existing it'll merge the parameters of the existing instance. To disable this behavior just set `mergePgParameters` to false in the cluster spec and manually set all the pgParameters in the cluster specification. Since postgresql.auto.conf overrides postgresql.conf parameters, changing some of them with ALTER SYSTEM could break the cluster (parameters managed by stolon could be overridden) and make pg parameters different between the instances. To avoid this stolon disables the execution of ALTER SYSTEM commands making postgresql.auto.conf a symlink to /dev/null. When an ALTER SYSTEM command is executed it'll return an error. There are some pg parameters which requires postgres restart to take effect after changing. For example, changing `maxconnections` will not take effect till the underlying postgres is restarted. This is disabled by default and can be enabled using the clusterSpecification `automaticPgRestart`. This is achieved using `pendingrestart` in for postgres 9.5 and above and the `context` column of `pg_settings` for lower versions (<= 9.4).
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_service_account.md

+++ title = "googleserviceaccount resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleserviceaccount" identifier = "inspec/resources/gcp/googleserviceaccount.md googleserviceaccount resource" parent = "inspec/resources/gcp" +++ A `googleserviceaccount` is used to test a Google ServiceAccount resource ```ruby describe googleserviceaccount(project: 'chef-gcp-inspec', name: "display-name@project-id.iam.gserviceaccount.com") do it { should exist } its('display_name') { should cmp '' } end describe googleserviceaccount(project: 'chef-gcp-inspec', name: "nonexistent@project-id.iam.gserviceaccount.com") do it { should_not exist } end ``` ```ruby describe googleserviceaccount(project: 'sample-project', name: 'sample-account@sample-project.iam.gserviceaccount.com') do its('unique_id') { should eq 12345678 } end ``` ```ruby describe googleserviceaccount(project: 'sample-project', name: 'sample-account@sample-project.iam.gserviceaccount.com') do its('oauth2clientid') { should eq 12345678 } end ``` ```ruby describe googleserviceaccountkeys(project: 'chef-gcp-inspec', serviceaccount: "display-name@project-id.iam.gserviceaccount.com") do its('keytypes') { shouldnot include 'USER_MANAGED' } end ``` Properties that can be accessed from the `googleserviceaccount` resource: `name` : The name of the service account. `project_id` : Id of the project that owns the service account. `unique_id` : Unique and stable id of the service account `email` : Email address of the service account. `display_name` : User specified description of service account. `oauth2clientid` : OAuth2 client id for the service account. Ensure the is enabled for the current project.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.140.md

layout: release date: 2023-09-16 tag: v0.6.140 [UI] Convert Index.js and settings.js from class-based component to functional component @ShatilKhan (#8705) Fix crash on saving applications @sudhanshutech (#8776) updated filter.js to functional component @abhijeetgauravm (#8785) Updated PromptComponent to support checkbox @Yashsharma1911 (#8672) chore: sort the technology list in alphabetical order @Yana-Gupta (#8708) Refactor /management/index.js to functional component @dhiraj0911 (#8703) [UI] Transparent "WA" Filter Icon @Chadha93 (#8793) Fix infinite publish requests @aabidsofi19 (#8769) Fix crash on saving applications @sudhanshutech (#8776) Fix failing updater test @KiptoonKipkurui (#8791) Thank you to our contributors for making this release possible: @Chadha93, @KiptoonKipkurui, @ShatilKhan, @Yana-Gupta, @Yashsharma1911, @aabidsofi19, @abhijeetgauravm, @dhiraj0911, @leecalcote, @sudhanshutech and l5io
Project: KICS (Provisioning / Security & Compliance)
File: 59ebb4f3-2a6c-46dc-b4f0-cc5418dcddcd.md

title: Serverless Role With Full Privileges hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 59ebb4f3-2a6c-46dc-b4f0-cc5418dcddcd Query name: Serverless Role With Full Privileges Platform: ServerlessFW Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Roles defined in Serverless files should not have policies granting full administrative privileges.<br> ```yml title="Positive test num. 1 - yml file" hl_lines="11" service: service frameworkVersion: '2' provider: name: aws runtime: nodejs12.x iam: role: name: custom-role-name path: /custom-role-path/ statements: Effect: 'Allow' Resource: '*' Action: '*' managedPolicies: 'arn:aws:iam::123456789012:user/*' permissionsBoundary: arn:aws:iam::123456789012:policy/boundaries tags: key: value functions: hello: handler: handler.hello onError: arn:aws:sns:us-east-1:XXXXXX:test tags: foo: bar role: arn:aws:iam::XXXXXX:role/role tracing: Active ``` ```yml title="Negative test num. 1 - yml file" service: service frameworkVersion: '2' provider: name: aws runtime: nodejs12.x iam: role: name: custom-role-name path: /custom-role-path/ statements: Effect: 'Allow' Resource: '*' Action: 'iam:DeleteUser' managedPolicies: 'arn:aws:iam::123456789012:user/*' permissionsBoundary: arn:aws:iam::123456789012:policy/boundaries tags: key: value functions: hello: handler: handler.hello onError: arn:aws:sns:us-east-1:XXXXXX:test tags: foo: bar role: arn:aws:iam::XXXXXX:role/role tracing: Active ```
Project: ClickHouse (App Definition and Development / Database)
File: skipping-index.md

slug: /en/sql-reference/statements/alter/skipping-index tochiddenfolder: true sidebar_position: 42 sidebar_label: INDEX The following operations are available: `ALTER TABLE [db.]table_name [ON CLUSTER cluster] ADD INDEX [IF NOT EXISTS] name expression TYPE type [GRANULARITY value] [FIRST|AFTER name]` - Adds index description to tables metadata. `ALTER TABLE . `ALTER TABLE . If `IN PARTITION` part is omitted then it rebuilds the index for the whole table data. `ALTER TABLE . The commands `ADD`, `DROP`, and `CLEAR` are lightweight in the sense that they only change metadata or remove files. Also, they are replicated, syncing indices metadata via ClickHouse Keeper or ZooKeeper. :::note Index manipulation is supported only for tables with engine (including variants). :::
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.98.md

layout: release date: 2023-06-23 tag: v0.6.98 Add config attribute to meshery filter @MUzairS15 (#7910) [UI]: style fix of few components in dark theme @samyakshah3008 (#7907) Bump @rjsf/material-ui from 5.8.1 to 5.8.2 in /ui @dependabot (#7906) Refactor/dashboard Remove Connection Status Section @aabidsofi19 (#7881) Extentions/GitHub/meshmap : Add GitHub Action for MeshMap Snapshot @aabidsofi19 (#7888) Fix bug in flipcard for filters @sudhanshutech (#7911) upgrade rjsf -> 5.8.1 @harkiratsm (#7901) [UI]: Fix responsiveness of profile card for mobile view @samyakshah3008 (#7895) [UI] RJSF Fixes styles for "name" and "namespace" input fields labels @Chadha93 (#7889) refactor: replaced CreateTable with CreateSelect @vaibhav135 (#7884) [UI] Fixes Notification Center Sneak Peak Behavior onClick @Chadha93 (#7886) Database summary - Add table size/record count to System Reset screen @Meyazhagan (#7686) fix: remove mapping navigator @Udit-takkar (#7806) Fix Cytoscape-to-design conversion process @MUzairS15 (#7922) Fix bug in flipcard for filters @sudhanshutech (#7911) [CI] Update build-and-release-edge.yml @theBeginner86 (#7927) [CI] Update build-and-release-edge.yml @theBeginner86 (#7926) [CI] Update build-and-release-edge.yml @theBeginner86 (#7925) Bump @rjsf/material-ui from 5.8.1 to 5.8.2 in /ui @dependabot (#7906) [CI] Support Edge Releases with Remote Provider @theBeginner86 (#7913) Update `MeshMap-Snapshot` workflow to `v0.0.5` @MUzairS15 (#7899) fix: remove mapping navigator @Udit-takkar (#7806) [Update Dockerfile] Add comment for future reference @Abhishek-kumar09 (#7876) Adding Catalog page in docs @yash37158 (#7732) [CI] GraphQL: Docs Build Target @leecalcote (#7924) Server.go file missing #7887 @vaibhav-xt (#7902) fixed: meshery-docs hover tabs and focus on sidebar option @vaibhav135 (#7831) [Docs] Initialize Extension's user facing documentation | CU-85zrzt5fg @Chadha93 (#7807) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aisuko, @Chadha93, @MUzairS15, @Meyazhagan, @Udit-takkar, @aabidsofi19, @dependabot, @dependabot[bot], @harkiratsm, @l5io, @leecalcote, @samyakshah3008, @sudhanshutech, @theBeginner86, @vaibhav-xt, @vaibhav135, @yash37158 and l5io