cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: a478af30-8c3a-404d-aa64-0b673cee509a.md

title: Redshift Using Default Port hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a478af30-8c3a-404d-aa64-0b673cee509a Query name: Redshift Using Default Port Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Redshift should not use the default port (5439) because an attacker can easily guess the port<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4 28" Resources: myCluster: Type: "AWS::Redshift::Cluster" Properties: PubliclyAccessible: false DBName: "mydb" MasterUsername: "master" MasterUserPassword: Ref: "MasterUserPassword" NodeType: "ds2.xlarge" ClusterType: "single-node" Tags: Key: foo Value: bar myCluster2: Type: "AWS::Redshift::Cluster" Properties: PubliclyAccessible: false DBName: "mydb" MasterUsername: "master" MasterUserPassword: Ref: "MasterUserPassword" NodeType: "ds2.xlarge" ClusterType: "single-node" Tags: Key: foo Value: bar Port: 5439 ``` ```json title="Positive test num. 2 - json file" hl_lines="5 39" { "Resources": { "myCluster": { "Type": "AWS::Redshift::Cluster", "Properties": { "NodeType": "ds2.xlarge", "ClusterType": "single-node", "Tags": [ { "Key": "foo", "Value": "bar" } ], "PubliclyAccessible": true, "DBName": "mydb", "MasterUsername": "master", "MasterUserPassword": { "Ref": "MasterUserPassword" } } }, "myCluster2": { "Type": "AWS::Redshift::Cluster", "Properties": { "Tags": [ { "Key": "foo", "Value": "bar" } ], "PubliclyAccessible": true, "DBName": "mydb", "MasterUsername": "master", "MasterUserPassword": { "Ref": "MasterUserPassword" }, "NodeType": "ds2.xlarge", "ClusterType": "single-node", "Port": 5439 } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: myCluster: Type: "AWS::Redshift::Cluster" Properties: PubliclyAccessible: false DBName: "mydb" MasterUsername: "master" MasterUserPassword: Ref: "MasterUserPassword" NodeType: "ds2.xlarge" ClusterType: "single-node" Tags: Key: foo Value: bar Port: 1150 ``` ```json title="Negative test num. 2 - json file" { "Resources": { "myCluster": { "Type": "AWS::Redshift::Cluster", "Properties": { "MasterUserPassword": { "Ref": "MasterUserPassword" }, "NodeType": "ds2.xlarge", "ClusterType": "single-node", "Tags": [ { "Value": "bar", "Key": "foo" } ], "PubliclyAccessible": false, "DBName": "mydb", "MasterUsername": "master", "Port": "1150" } } } } ```
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: env-providers.md

All following providers allow a common workflow: `make cluster-up` to create the environment `make cluster-down` to stop the environment `make cluster-build` to build `make cluster-deploy` to (re)deploy the code (no provider support needed) `make cluster-sync` to build and (re)deploy the code `make functests` to run the functional tests against KubeVirt `cluster-up/kubectl.sh` to talk to the k8s installation It is recommended to export the `KUBEVIRT_PROVIDER` variable as part of your `.bashrc` file. Allows provisioning k8s cluster based on kubeadm. Supports an arbitrary amount of nodes. Requires: A working go installation Nested virtualization enabled A running docker daemon Usage: ```bash export KUBEVIRT_PROVIDER=k8s-1.13.3 # choose this provider export KUBEVIRTNUMNODES=3 # control-plane + two nodes make cluster-up ``` Allows provisioning a single-control-plane k8s cluster based on latest upstream k8s code. Requires: A working go installation A running docker daemon Usage: ```bash export KUBEVIRT_PROVIDER=local # choose this provider make cluster-up ``` Uses an existing (external) Kubernetes cluster. Requires: A working Kubernetes cluster with properly configured worker nodes. A running docker daemon Usage: ```bash export KUBEVIRT_PROVIDER=external # choose this provider make cluster-up ``` First add your provider in the repository. After this provider is merged, update our copy of this repository with the following command: ```bash make bump-kubevirtci ```
Project: KICS (Provisioning / Security & Compliance)
File: ed9b3beb-92cf-44d9-a9d2-171eeba569d4.md

title: SQS Policy Allows All Actions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ed9b3beb-92cf-44d9-a9d2-171eeba569d4 Query name: SQS Policy Allows All Actions Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: SQS policy allows ALL (*) actions<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" name: Second SQS queue with policy community.aws.sqs_queue: name: my-queue2 region: ap-southeast-3 defaultvisibilitytimeout: 120 messageretentionperiod: 86400 maximummessagesize: 1024 delivery_delay: 30 receivemessagewait_time: 20 policy: Version: "2012-10-17" Statement: Effect: "Allow" Action: "aws:action" Resource: "*" Effect: "Allow" Action: "*" Resource: "*" make_default: false state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: Create SQS queue with redrive policy community.aws.sqs_queue: name: my-queue region: ap-southeast-2 defaultvisibilitytimeout: 120 messageretentionperiod: 86400 maximummessagesize: 1024 delivery_delay: 30 receivemessagewait_time: 20 policy: Version: '2012-10-17' Statement: Effect: Allow Action: logs:CreateLogGroup Resource: '*' make_default: false state: present ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_list-logs.md

title: kbcli cluster list-logs List supported log files in cluster. ``` kbcli cluster list-logs NAME [flags] ``` ``` kbcli cluster list-logs mycluster kbcli cluster list-logs mycluster --component my-component kbcli cluster list-logs mycluster --instance my-instance-0 ``` ``` --component string Component name. -h, --help help for list-logs -i, --instance string Instance name. ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Cluster command.
Project: YugabyteDB (App Definition and Development / Database)
File: srem.md

title: SREM linkTitle: SREM description: SREM menu: preview: parent: api-yedis weight: 2310 aliases: /preview/api/redis/srem /preview/api/yedis/srem type: docs `SREM key value [value ...]` This command removes one or more specified members from the set that is associated with the given `key`. If the `key` does not exist, the associated set is an empty set, and the return value is zero. If the `key` is associated with a value that is not a set, an error is raised. If a specified `value` does not exist in the given set, that `value` is ignored and not counted toward the total of removed members. Returns the total number of existed members that were removed from the set. ```sh $ SADD yuga_world "America" ``` ``` 1 ``` ```sh $ SADD yuga_world "Moon" ``` ``` 1 ``` ```sh $ SREM yuga_world "Moon" ``` ``` 1 ``` ```sh $ SREM yuga_world "Moon" ``` ``` 0 ``` , , ,
Project: ko (App Definition and Development / Application Definition & Image Build)
File: README.md

Update `.md` files to update content. Update `mkdocs.yml` to update sidebar headers and ordering. To run locally: and run `mkdocs serve`, or `docker run --rm -it -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material` on an M1 Mac, use `ghcr.io/afritzler/mkdocs-material` instead. This will start a local server on localhost:8000 that autoupdates as you make changes. When PRs are merged, the site will be rebuilt and published automatically. The site is powered by . The code and theme are released under the MIT license. Content is licensed . cases where your image contains a single Go application without any/many dependencies on the OS base image (e.g., no cgo, no OS package dependencies). `ko` builds images by effectively executing `go build` on your local machine, and as such doesn't require `docker` to be installed. This can make it a good fit for lightweight CI/CD use cases. `ko` makes easy, produces by default, and includes support for simple YAML templating which makes it a powerful tool for . This work is based heavily on experience from having built the and support for . That work was presented . Questions? Comments? Ideas? Come discuss `ko` with us in the `#ko-build` channel on the ! See you there! You can find all the necessary details about the community meetings in this .
Project: YDB (App Definition and Development / Database)
File: olap-data-types.md

| Data type | Can be used in<br>column-oriented tables | Can be used<br>as primary key | || | `Bool` | | | | `Int8` | | | | `Int16` | | | | `Int32` | | | | `Int64` | | | | `Uint8` | | | | `Uint16` | | | | `Uint32` | | | | `Uint64` | | | | `Float` | | | | `Double` | | | | `Decimal` | | | | `String` | | | | `Utf8` | | | | `Json` | | | | `JsonDocument` | | | | `Yson` | | | | `Uuid` | | | | `Date` | | | | `Datetime` | | | | `Timestamp` | | | | `Interval` | | |
Project: YugabyteDB (App Definition and Development / Database)
File: directed-cyclic-graph.md

title: Using a recursive CTE to traverse a directed cyclic graph headerTitle: Finding the paths in a directed cyclic graph linkTitle: Directed cyclic graph description: This section shows how to use a recursive CTE to traverse a directed cyclic graph. menu: v2.18: identifier: directed-cyclic-graph parent: traversing-general-graphs weight: 40 type: docs Before trying the code in this section, make sure that you have created the "edges" table (see ) and installed all the code shown in the section . First, define a suitable constraint on the "edges" table for representing a directed cyclic graph and populate the table with the data that represents the graph shown in the section. ```plpgsql delete from edges; alter table edges drop constraint if exists edges_chk cascade; alter table edges add constraint edgeschk check(node1 <> node_2); insert into edges(node1, node2) values ('n2', 'n1'), ('n2', 'n4'), ('n4', 'n5'), ('n4', 'n6'), ('n6', 'n4'), ('n5', 'n6'), ('n5', 'n3'), ('n3', 'n2'); ``` Now reinstate the implementation of "findpaths()"_ shown at . Find all the paths from "n2" and create the filtered subset of shortest paths to the distinct terminal nodes: ```plpgsql call findpaths(startnode => 'n2'); call restricttoshortestpaths('rawpaths', 'shortest_paths'); ``` Look at the "rawpaths"_: ```plpgsql \t on select t from listpaths('rawpaths'); \t off ``` This is the result: ``` path # cardinality path -- - 1 2 n2 > n1 2 2 n2 > n4 3 3 n2 > n4 > n5 4 3 n2 > n4 > n6 5 4 n2 > n4 > n5 > n3 6 4 n2 > n4 > n5 > n6 ``` Look at the "filteredpaths"_: ```plpgsql \t on select t from listpaths('shortestpaths'); \t off ``` This is the result: ``` path # cardinality path -- - 1 2 n2 > n1 2 2 n2 > n4 3 3 n2 > n4 > n5 4 3 n2 > n4 > n6 5 4 n2 > n4 > n5 > n3 ```
Project: ShardingSphere (App Definition and Development / Database)
File: alter-encrypt-rule.en.md

+++ title = "ALTER ENCRYPT RULE" weight = 2 +++ The `ALTER ENCRYPT RULE` syntax is used to alter encryption rules. {{< tabs >}} {{% tab name="Grammar" %}} ```sql AlterEncryptRule ::= 'ALTER' 'ENCRYPT' 'RULE' encryptDefinition (',' encryptDefinition)* encryptDefinition ::= ruleName '(' 'COLUMNS' '(' columnDefinition (',' columnDefinition)* ')' ')' columnDefinition ::= '(' 'NAME' '=' columnName ',' 'CIPHER' '=' cipherColumnName (',' 'ASSISTEDQUERY' '=' assistedQueryColumnName)? (',' 'LIKEQUERY' '=' likeQueryColumnName)? ',' encryptAlgorithmDefinition (',' assistedQueryAlgorithmDefinition)? (',' likeQueryAlgorithmDefinition)? ')' encryptAlgorithmDefinition ::= 'ENCRYPT_ALGORITHM' '(' 'TYPE' '(' 'NAME' '=' algorithmType (',' propertiesDefinition)? ')' assistedQueryAlgorithmDefinition ::= 'ASSISTEDQUERYALGORITHM' '(' 'TYPE' '(' 'NAME' '=' algorithmType (',' propertiesDefinition)? ')' likeQueryAlgorithmDefinition ::= 'LIKEQUERYALGORITHM' '(' 'TYPE' '(' 'NAME' '=' algorithmType (',' propertiesDefinition)? ')' propertiesDefinition ::= 'PROPERTIES' '(' key '=' value (',' key '=' value)* ')' ruleName ::= identifier columnName ::= identifier cipherColumnName ::= identifier assistedQueryColumnName ::= identifier likeQueryColumnName ::= identifier algorithmType ::= string key ::= string value ::= literal ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `CIPHER` specifies the cipher column, `ASSISTEDQUERY` specifies the assisted query column`LIKEQUERY` specifies the like query column `algorithmType` specifies the encryption algorithm type, please refer to Alter an encrypt rule ```sql ALTER ENCRYPT RULE t_encrypt ( COLUMNS( (NAME=userid,CIPHER=usercipher,ASSISTEDQUERY=assistedqueryuser,LIKEQUERY=likequeryuser,ENCRYPTALGORITHM(TYPE(NAME='AES',PROPERTIES('aes-key-value'='123456abc'))),ASSISTEDQUERYALGORITHM(TYPE(NAME='MD5')),LIKEQUERYALGORITHM(TYPE(NAME='CHARDIGEST_LIKE'))), (NAME=orderid,CIPHER=ordercipher,ASSISTEDQUERY=assistedqueryorder,LIKEQUERY=likequeryorder,ENCRYPTALGORITHM(TYPE(NAME='AES',PROPERTIES('aes-key-value'='123456abc'))),ASSISTEDQUERYALGORITHM(TYPE(NAME='MD5')),LIKEQUERYALGORITHM(TYPE(NAME='CHARDIGEST_LIKE'))) )); ``` `ALTER`, `ENCRYPT`, `RULE`, `COLUMNS`, `NAME`, `CIPHER`, `ASSISTEDQUERY`, `LIKEQUERY`, `ENCRYPTALGORITHM`, `ASSISTEDQUERYALGORITHM`, `LIKEQUERY_ALGORITHM`, `TYPE`, `TRUE`, `FALSE`
Project: DragonflyDB (App Definition and Development / Database)
File: CONTRIBUTING.md

Thank you for your interest in Dragonfly DB. Feel free to browse our and See Please note that to build a development/debug version, it's better to alter the configure and build steps above with: ```sh ./helio/blaze.sh # without '-release' flag. Creates build-dbg subfolder cd build-dbg && ninja dragonfly ``` ```sh cd dragonfly # project root pip install pre-commit clang-format pre-commit install ``` This step must be done on each machine you wish to develop and contribute from to activate the `commit-msg` and `commit` hooks client-side. Once you have done these things, we look forward to adding your contributions and improvements to the Dragonfly DB project. ``` cd build-dbg && ninja [test_name] ./[test_name] ``` A Golang golden test is included in the dragonfly helm chart. This test will render the chart and compare the output to a golden file. If the output has changed, the test will fail and the golden file will need to be updated. This can be done by running: ```bash cd contrib/charts/dragonfly go test -v ./... -update ``` This makes it easy to see the changes in the rendered output without having to manually run the `helm template` and diff the output. All community submissions must include a signoff. ```bash git commit -s -m '...' ``` Please squash all commits for a change into a single commit (this can be done using "git rebase -i"). Do your best to have a well-formed commit message for the change. This repo uses The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with , by describing the features, fixes, and breaking changes made in commit messages. The commit message should be structured as follows: ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` This repo uses automated tools to standardize the formatting of code, text files, and commits. validate and automatically apply code formatting rules. The Dragonfly DB team has agreed to systematically use several pre-commit hooks to normalize the formatting of code. You need to install and enable pre-commit to have these used when you do your commits. This repo conforms to the Google's C++ Style Guide. Keep in mind we use an older version of the style guide which can be found . Any exceptions to the rules specified in the style guide will be documented here. Please see our
Project: YugabyteDB (App Definition and Development / Database)
File: data-expiry.md

title: Automatic Data Expiration headerTitle: Automatic data expiration linkTitle: Automatic data expiration description: Distribute your time-ordered data and retrieve fast headcontent: Expire data using time-to-live menu: v2.18: identifier: timeseries-automatic-expiration parent: common-patterns-timeseries weight: 300 type: docs Consider a scenario where you only need the last few values and the older data is not of any value and can be purged. Typically, this requires setting up a separate background job. Using YugabyteDB however, you can set an expiration value for columns using the `USING TTL` operator. {{<note title="Note">}} TTL-based expiration is only available in . {{</note>}} {{<cluster-setup-tabs>}} Consider a speed metrics tracking system that tracks the data from the speed sensor of many cars. Create a table and insert data with an example schema as follows: ```sql CREATE KEYSPACE IF NOT EXISTS yugabyte; USE yugabyte; CREATE TABLE exp_demo ( ts timestamp,/ time at which the event was generated / car text, / name of the car / speed int, / speed of your car / PRIMARY KEY(car, ts) ) WITH CLUSTERING ORDER BY (ts DESC); ``` ```sql INSERT INTO exp_demo(ts,car,speed) VALUES('2023-07-01 10:00:01','car-1',50) USING TTL 10; INSERT INTO exp_demo(ts,car,speed) VALUES('2023-07-01 10:00:02','car-2',25) USING TTL 15; INSERT INTO exp_demo(ts,car,speed) VALUES('2023-07-01 10:00:03','car-1',39) USING TTL 15; INSERT INTO exp_demo(ts,car,speed) VALUES('2023-07-01 10:00:04','car-1',49) USING TTL 20; INSERT INTO exp_demo(ts,car,speed) VALUES('2023-07-01 10:00:05','car-2', 3) USING TTL 25; ``` As soon as you insert the data, start selecting all rows over and over. Eventually, you will see all the data disappear. ```sql SELECT * from exp_demo; ``` For more fine-grained expiration, instead of setting the TTL on an entire row, you can set TTL per column. For example, do the following: Add a row. ```sql INSERT INTO exp_demo(ts,car,speed) VALUES('2023-08-01 10:00:01', 'car-5', 50); ``` Fetch the rows. ```sql SELECT * FROM exp_demo WHERE car='car-5'; ``` ```output car | ts | speed -++- car-5 | 2023-08-01 17:00:01.000000+0000 | 50 ``` Set an expiration on the speed column of that row as follows: ```sql UPDATE exp_demo USING TTL 5 SET speed=10 WHERE car='car-5' AND ts ='2023-08-01 10:00:01'; ``` Wait for five seconds and fetch the row for `car-5`. ```sql SELECT * FROM exp_demo WHERE car='car-5'; ``` ```output car | ts | speed -++- car-5 | 2023-08-01 17:00:01.000000+0000 | null ``` Note that the row is present but the value for the `speed` column is `null`. Instead of explicitly setting the TTL at the row or column level, you can set a TTL on the table. This also has the benefit of saving space as the TTL value is stored in only one place and not per row or column. Define table-level TTL using the .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.59.md

layout: release date: 2023-03-02 tag: v0.6.59 language: en Bump golang.org/x/net from 0.5.0 to 0.7.0 in /scripts/component_generation @dependabot (#7250) fix greedy search in /meshmodel/model/{model} @Revolyssup (#7225) Trim whitespace from Meshmodel model names for websites @Revolyssup (#7224) Add links, captions as annotation tags in `mesheryctl` files @alphaX86 (#7205) Made Navigator Icons Consistent @hs05june (#7203) Bump @mui/icons-material from 5.11.0 to 5.11.11 in /provider-ui @dependabot (#7236) Fixed clickable area issue in header settings button. @sidtohan (#7147) Bump eslint from 8.34.0 to 8.35.0 in /ui @dependabot (#7235) Bump jss from 10.9.2 to 10.10.0 in /ui @dependabot (#7234) Corrected background of Metrics in Dark Mode @hs05june (#7251) Bump @emotion/react from 11.10.5 to 11.10.6 in /provider-ui @dependabot (#7242) Bump webpack-cli from 4.10.0 to 5.0.1 in /ui @dependabot (#7241) Bump cypress from 12.4.0 to 12.7.0 in /provider-ui @dependabot (#7237) Bump @emotion/styled from 11.10.5 to 11.10.6 in /provider-ui @dependabot (#7239) Bump immutable from 4.1.0 to 4.2.4 in /ui @dependabot (#7238) removing an non kubernetes exception in Json schema @harkiratsm (#7216) [chore] Fix issues with loading User Account Extension @theBeginner86 (#7153) Feat: add space btw dashboard sections @thisiskaransgit (#7221) [chore] Fix issues with loading User Account Extension @theBeginner86 (#7153) Bump @mui/icons-material from 5.11.0 to 5.11.11 in /provider-ui @dependabot (#7236) Bump github.com/prometheus/common from 0.37.0 to 0.41.0 @dependabot (#7240) Bump eslint from 8.34.0 to 8.35.0 in /ui @dependabot (#7235) Bump jss from 10.9.2 to 10.10.0 in /ui @dependabot (#7234) Bump @emotion/react from 11.10.5 to 11.10.6 in /provider-ui @dependabot (#7242) Bump webpack-cli from 4.10.0 to 5.0.1 in /ui @dependabot (#7241) Bump cypress from 12.4.0 to 12.7.0 in /provider-ui @dependabot (#7237) Bump @emotion/styled from 11.10.5 to 11.10.6 in /provider-ui @dependabot (#7239) Bump immutable from 4.1.0 to 4.2.4 in /ui @dependabot (#7238) Bump github.com/layer5io/meshsync from 0.6.7 to 0.6.9 @dependabot (#7243) [chore] Fix issues with loading User Account Extension @theBeginner86 (#7153) add hover color for hyperlinks @rinkuhasija (#7227) Add docs for setting up development environment on Windows @mohit-marathe (#7209) Add links, captions as annotation tags in `mesheryctl` files @alphaX86 (#7205) Deleted Extra Lines in code @Nikhil26112 (#7217) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Nikhil26112, @Revolyssup, @alphaX86, @asubedy, @dependabot, @dependabot[bot], @harkiratsm, @hs05june, @leecalcote, @mohit-marathe, @rinkuhasija, @sidtohan, @theBeginner86, @thisiskaransgit and l5io
Project: Curiefense (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: 'bug' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 22] Smartphone (please complete the following information): Device: [e.g. iPhone6] OS: [e.g. iOS8.1] Browser [e.g. stock browser, safari] Version [e.g. 22] Additional context Add any other context about the problem here.