text:
# novi-plugin-background-image
Novi Builder Plugin for changing backgrounds

## How to Install
You should follow several simple steps to intall this plugin:
* Copy the novi-plugin-background-image.js file to your path/to/novibuilder/plugins folder.
* Launch NoviBuilder

## What you are able to do
* Change background image

## Developer Settings
* querySelector — contains a css selector which defines the Plugin container.

## Usage
For use plugin your element must match the CSS selector of querySelector setting.

For example querySelector value is ".section".
In this case you need to add element with class .section:
```html
<section class="section">
    ...
</section>
```


text:
# drones
The JJRC H47 ELFIE+ is a cheap drone with on-board colored camera. The code in the repository allowes to fully control the movment of the drone using a joystick, and to receive the image from the drone's camera as a python object (which can be used for image-prosessing). The code is written in python 3 and tested on Ubunto 16.04.

# needed-packages:
1) opencv
2) numpy
3) gstreamer
4) pygame - for controling the drone using joystick
5) tkinter - for minimal GUI
# how to run:
1) connect to the wifi network of your drone
2) run the file: run_me.py
# what's in this repository:
the scripts are orgnized in folders:
1) camera - all the scripts that hendle reciving and displaying the images from the camera
2) control - all the scripts that hendle the movment of the drone
3) general - general scripst such: displaying minimal GUI and state machin of the program
4) sniffes - examples for sniffes of the communication between the drone and it's custom app

license: MIT

branch_name: refs/heads/master

extension: md

gha_language: Python

gha_license_id: MIT

license_type: permissive


text:
# shout-api

*shout-api* is the API server [shout](https://github.com/derhuerst/shout).

work in progress!

## Contributing

If you **have a question**, **found a bug** or want to **propose a feature**, have a look at [the issues page](https://github.com/derhuerst/shout-api/issues).

repository: derhuerst/shout-api

gha_language: CoffeeScript

repo_name: derhuerst/shout-api


text:
## COMPILATION

This Coq theory compiles under Coq 8.3pl5, available from https://coq.inria.fr/distrib/V8.3pl5/files/ .
Earlier patch levels should also work; I have tested with 8.3pl2.

Create a Makefile by calling
```bash
$ coq_makefile -f Make > Makefile
```
and compile by calling
```bash
$ make
```

WARNING : The compilation of some of the files consumes up to 2GB of memory. Make sure you dispose of sufficient reserves of ram before compiling the code.

## WORK WITH THE CODE

Call coqide as follows from the root of the library:
```bash
$ coqide -R . CatSem
```

## CONTENT

Read the file "./DESCRIPTION" for a description of the content of each file.

## BRANCHES

Each branch below, printed in **boldface**, corresponds to an article, printed in _italic_.

* [**JFR**](https://github.com/benediktahrens/monads/tree/JFR): [_Initial Semantics for higher-order typed syntax in Coq_](http://jfr.cib.unibo.it/article/view/2066)
* [**MSCS**](https://github.com/benediktahrens/monads/tree/MSCS): [_Modules over relative monads for syntax and semantics_](http://dx.doi.org/10.1017/S0960129514000103)
* [**REDUCTION_RULES**](https://github.com/benediktahrens/monads/tree/REDUCTION_RULES): [_Initial Semantics for Reduction Rules_](http://arxiv.org/abs/1212.5668)

All the articles are also available from my [webpage](http://benedikt-ahrens.de/publications).

license: Unlicense

repository: benediktahrens/monads

branch_name: refs/heads/trunk

gha_language: Coq

repo_name: benediktahrens/monads


text:
# Upload-Service

[![Go Report Card](https://goreportcard.com/badge/github.com/meateam/upload-service)](https://goreportcard.com/report/github.com/meateam/upload-service)
[![GoDoc](https://godoc.org/github.com/meateam/upload-service?status.svg)](https://godoc.org/github.com/meateam/upload-service)

S3 file Upload Service

## Compile proto

In order to compile the proto file make sure you have `protobuf` and `protoc-gen-go`

### Installing protobuf on Linux

`./install_protoc.sh`

### Installing protoc-gen-go

`go get -u github.com/golang/protobuf/protoc-gen-go`

[example guide to gRPC and protobuf](https://grpc.io/docs/quickstart/go.html)

**Compiling Protobuf To Golang:**
`protoc -I proto/ proto/upload_service.proto --go_out=plugins=grpc:./proto`

repository: meateam/upload-service

gha_language: Go

repo_name: meateam/upload-service


text:
# match4
The generic [worse] version of Connect 4 in C

## Installation

``` git clone https://github.com/manila/match4 && cd match4 && make ```

## Playing

Enter the number of the column you want to drop your piece, then allow the second player to do the same. First one to get 4 in a row vertically, horizontally, or diagonally wins!

## TODO

- Comments!
- Better error checking for bad player input
- ~~Malloc null pointer checks~~


text:
# How to contribute

In order to contribute to this repository, please consult with the main contributors.

If you have write permission to the repo, please follow the instructions below to make contributions. Use forks of the repo _only when necessary_ to make your contributions. A properly labelled branch is preferred over a fork (see below under __feature branches__). This allows people within the team to more easily track the work being done, especially in regards to issues.

## Branches

### master

This branch is the stable branch that is used for creating releases.

In order to create a release, the developer should ensure all changes are pushed to this branch and create a tag.

### develop

Changes should not be made _directly_ to this branch (rather, via pull requests using __feature branches__). Changes in this branch are intended for preview purposes and, when ready, to be merged into the master branch.

### feature branches

In order to contribute a new feature or to fix a bug, please follow these recommended rules:

- Create a new branch from `develop`.
     * Use the naming convention `feature/<relevant name>`.
     * The name of the branch should reflect the work being done on the branch.
     * If you've created the branch locally, be sure to push your branch to GitHub.
- Once the branch has been created, associate a GitHub issue with the branch and assign a developer to the issue.
     * Please create an issue if one does not exist.
- Once the feature is deemed ready, a pull request should be created and used to pull the changes into develop.


text:
# Step 2/4 - Using database's data
### Estimated time: 3 hours

In this step, you'll connect your code with the database and create your first table using only Typescript 😎.

## Connecting with the database

Do we have a library to access our database? Of course we do. For this, we use the [TypeORM](https://typeorm.io/#/) library. It helps us to make database operations (create tables, access data and so on) in a very simple way.

1. Take some time to learn how this library works. It's super cool, but it's also a lot of abstraction.
1. Follow their docs to add it to your project (remember that we're using postgres).
1. Choose an option provided by typeorm to connect to your database. The credentials are the ones you set on `docker-compose.yml`.
1. Try to connect with database before running the apollo-server `start` code. For now, you can connect only with your **local** database, leaving the test connection for later.

**Note:** don't forget to check if your docker container is running before connecting to the DB, otherwise it will fail.

Now you can ask: "Do they have a tool to manage the data inside the database without code?" Of course we do, young padawan. Actually, we recommend these two apps:
- [Tableplus](https://tableplus.io/)
- [PopSQL](https://popsql.com/)

Feel free to choose one of these above, or any other app you want :D

## Creating your first entity

After successfully connecting TypeORM to your database, it's time to see it working by creating your first table. Guess what? It will be called `User` (we told you so)

1. Check on TypeORM docs how to create a [TypeORM entity](https://github.com/typeorm/typeorm/blob/master/docs/entities.md#what-is-entity)
1. After creating the table, try creating a row (an user 🙆). You can do this either coding (it's possible) or directly on Tableplus, whatever you prefer.

**Note 2:** too much for one step? Don't get stuck and feel free to ask anything to any Taqtiler 👍

## Open a Pull Request

Now open a pull request for your `feature/setup-database` branch.

license: ISC

repository: indigotech/taq-github-bot

branch_name: refs/heads/main

gha_language: TypeScript

gha_license_id: ISC

repo_name: indigotech/taq-github-bot


text:
VERSIONATOR.ECLASS
Section: eclass-manpages (5)
Updated: Sep 2020
Index Return to Main Contents
NAME
versionator.eclass - functions which simplify manipulation of ${PV} and similar version strings
DESCRIPTION
This eclass provides functions which simplify manipulating $PV and similar variables. Most functions default to working with $PV, although other values can be used.
SUPPORTED EAPIS
0 1 2 3 4 5 6
EXAMPLE
Simple Example 1: $PV is 1.2.3b, we want 1_2.3b:
    MY_PV=$(replace_version_separator 1 '_' )
Simple Example 2: $PV is 1.4.5, we want 1:
    MY_MAJORV=$(get_major_version )

Rather than being a number, the index parameter can be a separator character such as '-', '.' or '_'. In this case, the first separator of this kind is selected.

There's also:
    version_is_at_least             want      have
 which may be buggy, so use with caution.

FUNCTIONS
get_all_version_components [version]
Split up a version string into its component parts. If no parameter is supplied, defaults to $PV.
    0.8.3       ->  0 . 8 . 3
    7c          ->  7 c
    3.0_p2      ->  3 . 0 _ p2
    20040905    ->  20040905
    3.0c-r1     ->  3 . 0 c - r1
get_version_components [version]
Get the important version components, excluding '.', '-' and '_'. Defaults to $PV if no parameter is supplied.
    0.8.3       ->  0 8 3
    7c          ->  7 c
    3.0_p2      ->  3 0 p2
    20040905    ->  20040905
    3.0c-r1     ->  3 0 c r1
get_major_version [version]
Get the major version of a value. Defaults to $PV if no parameter is supplied.
    0.8.3       ->  0
    7c          ->  7
    3.0_p2      ->  3
    20040905    ->  20040905
    3.0c-r1     ->  3
get_version_component_range <range> [version]
Get a particular component or range of components from the version. If no version parameter is supplied, defaults to $PV.
   1      1.2.3       -> 1
   1-2    1.2.3       -> 1.2
   2-     1.2.3       -> 2.3
get_after_major_version [version]
Get everything after the major version and its separator (if present) of a value. Defaults to $PV if no parameter is supplied.
    0.8.3       ->  8.3
    7c          ->  c
    3.0_p2      ->  0_p2
    20040905    ->  (empty string)
    3.0c-r1     ->  0c-r1
replace_version_separator <search> <replacement> [subject]
Replace the $1th separator with $2 in $3 (defaults to $PV if $3 is not supplied). If there are fewer than $1 separators, don't change anything.
    1 '_' 1.2.3       -> 1_2.3
    2 '_' 1.2.3       -> 1.2_3
    1 '_' 1b-2.3      -> 1b_2.3 Rather than being a number, $1 can be a separator character such as '-', '.' or '_'. In this case, the first separator of this kind is selected.
replace_all_version_separators <replacement> [subject]
Replace all version separators in $2 (defaults to $PV) with $1.
    '_' 1b.2.3        -> 1b_2_3
delete_version_separator <search> [subject]
Delete the $1th separator in $2 (defaults to $PV if $2 is not supplied). If there are fewer than $1 separators, don't change anything.
    1 1.2.3       -> 12.3
    2 1.2.3       -> 1.23
    1 1b-2.3      -> 1b2.3 Rather than being a number, $1 can be a separator character such as '-', '.' or '_'. In this case, the first separator of this kind is deleted.
delete_all_version_separators [subject]
Delete all version separators in $1 (defaults to $PV).
    1b.2.3        -> 1b23
get_version_component_count [version]
How many version components are there in $1 (defaults to $PV)?
    1.0.1       ->  3
    3.0c-r1     ->  4
get_last_version_component_index [version]
What is the index of the last version component in $1 (defaults to $PV)? Equivalent to get_version_component_count - 1.
    1.0.1       ->  2
    3.0c-r1     ->  3
version_is_at_least <want> [have]
Is $2 (defaults to $PVR) at least version $1? Intended for use in eclasses only. May not be reliable, be sure to do very careful testing before actually using this.
version_compare <A> <B>
Takes two parameters (A, B) which are versions. If A is an earlier version than B, returns 1. If A is identical to B, return 2. If A is later than B, return 3. You probably want version_is_at_least rather than this function. May not be very reliable. Test carefully before using this.
version_sort <version> [more versions...]
Returns its parameters sorted, highest version last. We're using a quadratic algorithm for simplicity, so don't call it with more than a few dozen items. Uses version_compare, so be careful.
version_format_string <format> [version]
Reformat complicated version strings. The first argument is the string to reformat with while the rest of the args are passed on to the get_version_components function. You should make sure to single quote the first argument since it'll have variables that get delayed expansions.
MAINTAINERS
Jonathan Callen<EMAIL_ADDRESS><EMAIL_ADDRESS>REPORTING BUGS
Please report bugs via https://bugs.gentoo.org/
FILES
versionator.eclass
SEE ALSO
ebuild(5)
https://gitweb.gentoo.org/repo/gentoo.git/log/eclass/versionator.eclass
Index
NAME
DESCRIPTION
SUPPORTED EAPIS
EXAMPLE
FUNCTIONS
MAINTAINERS
REPORTING BUGS
FILES
SEE ALSO
This document was created by man2html, using the manual pages.
Time: 00:27:03 GMT, October 11, 2020

gha_language: HTML


text:
  docsify-link-preview

  a plugin to render link previews in docsify

---

## 💾 Install

1. Get your API key from https://www.linkpreview.net/

1. Configure

   ```html
   <script>
     window.$docsify = {
       linkpreview: {
         key: "YOUR_API_KEY",
       },
     };
   </script>
   ```

1. Insert script into docsify document:

   ```html
   <script src="//unpkg.com/docsify-link-preview/src/index.js"></script>
   ```

1. Insert the style
   ```html
   <link
     rel="stylesheet"
     href="//unpkg.com/docsify-link-preview/src/style.css"
   />
   ```

---

## 🎮 Usage

When you want to render a preview just put your link into a:

````markdown
```link-preview
link.com
```
````

---

## 🔥 Example

- [index.html](docs/index.html)
- [README.md](https://raw.githubusercontent.com/puria/docsify-link-preview/master/docs/README.md)

---

## 👤 Contributing

1.  🔀 [FORK IT](../../fork)
2.  Create your feature branch `git checkout -b feature/branch`
3.  Commit your changes `git commit -am 'Add some fooBar'`
4.  Push to the branch `git push origin feature/branch`
5.  Create a new Pull Request
6.  🙏 Thank you

---

## 💼 License

    Copyright © 2020 - present, Puria Nafisi Azizi<EMAIL_ADDRESS>
    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to deal
    in the Software without restriction, including without limitation the rights
    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
    copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in all
    copies or substantial portions of the Software.

     IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    SOFTWARE.

**[🔝 back to top](#-install)**

repository: FAKER-A/docsify-link-preview

repo_name: FAKER-A/docsify-link-preview


text:
git-alias
=========

A command line tool that will display all registered git aliases.

`git-alias` runs with python 2 & 3 and should be compatible with macOS [tested], Linux, and Windows.

![screenshot](screenshot.png)

Example
-------
Try yourself:
```
python3 git-alias.py example.config
```

Or with the `gitconfig` from [GitAlias.com][1] (options used: `-vvq`)

![screenshot](screenshot_vvq.png)

Install
-------
Copy the `git-alias.py` to any path of your choosing, e.g., `/usr/local/bin`.

Extend your global `~/.gitconfig` file `alias` section:

```
[alias]
  # Show this message (help: -h)
  # !: ignore, inline
  alias = !python3 /usr/local/bin/git-alias.py
```

Python version and paths may differ!

Done.

Usage
-----
Run `git alias [options] [FILE]` or simply `git alias`.

### Output Options
- `-a`         Print all aliases, including hidden ones
- `--color`    Force colorful output
- `--no-color` Disable colorful output

### Verbosity Options
- `-q`    Don't print alias descriptions
- `-qq`   Also don't print section titles
- `-qqq`  Also don't print (inline) commands
- `-qqqq` Also don't print usage help
- `-v`    Print all multiline commands (unmodified)
- `-vv`   Print multiline commands using pretty print
- `-vvqq` Print just the alias and command in pretty format

### Config file
- If `[FILE]` not provided, will default to `~/.gitconfig`

[1]: https://github.com/gitalias/gitalias/blob/master/gitalias.txt

repository: relikd/git-alias

repo_name: relikd/git-alias


text:
# Spring Insight Framework
The Spring Insight Framework causes an application to be automatically configured to work with a bound [Spring Insight Service][]. This feature will only work with Spring Insight versions of 2.0.0.x or above.

    Detection Criterion
    Existence of a single bound Spring Insight service.

Existence of a Spring Insight service is defined as the VCAP_SERVICES payload containing a service who's name, label or tag has insight as a substring.

    Tags
    <tt>spring-insight=<version></tt>

Tags are printed to standard output by the buildpack detect script

## User-Provided Service
When binding Spring Insight using a user-provided service, it must have name or tag with `insight` in it.  The credential payload must contain the following entries:

| Name | Description
| ---- | -----------
| `dashboard_url` | The URL via which users access the Spring Insight dashboard.

## Configuration
The Spring Insight Framework cannot be configured.

[Spring Insight Service]: http://gopivotal.com/pivotal-products/apps/pivotal-tc-server

repository: cloudfoundry/java-buildpack

gha_language: Ruby

repo_name: cloudfoundry/java-buildpack


text:
## Discord Points
Instantly reward your members with points for posting in specific channels!

### Installation

1. Download Python from [https://www.python.org/downloads/](https://www.python.org/downloads/)
2. Create a bot at [https://discord.com/developers/applications/](https://discord.com/developers/applications/) (Make sure you enable all intents)
3. Clone the repo
   ```sh
   git clone https://github.com/saucesteals/DiscordPoints.git
   ```
4. Install requirements
   ```sh
   pip/pip3 install -r requirements.txt
   ```
5. Fill in the template in `env.example`
6. Rename `env.example` to `.env`
7. Start it!
   ```sh
   python/python3 main.py
   ```

## Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.

1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3.  Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request

## License

Distributed under the MIT License. See `LICENSE` for more information.


text:
## Shopping Cart Layout

### Location
* **Admin Console:** Site Manager > Module Templates > Online Shop Layouts > Individual Catalog > Select Country for the Domain of Purchase
* **SFTP & Develop Mode:** /layouts/onlineshop/shopping_cart- *[country]* .html

### Tags

Tag | Description
-------------- | -------------
`{tag_buybutton,Text or Image,true}` | Link to check out and purchase products in cart (Text or Image allow you to render your own text or to use image instead). True is validation function that checks to make sure that every order has a valid shipping charge before the customer is able to pay and finalize the order.
`{tag_cataloguebreadcrumbs}` | Catalog breadcrumbs help customers easily navigate between related catalogs
`{tag_clearcartbutton}` | Link to clear the cart (customize to use image instead)
`{tag_custom1}` | Custom field #1. Use to display any information about a product
`{tag_custom2}` | Custom field #2. Use to display any information about a product
`{tag_custom3}` | Custom field #3. Use to display any information about a product
`{tag_custom4}` | Custom field #4. Use to display any information about a product
`{tag_discountcode}` | An input box for customers to enter discount code in
`{tag_getquotebutton}` | Link to check out and request a quote (customize to use image instead)
`{tag_giftvoucher}` | An input box for customer to enter gift voucher code in
`{tag_giftvoucheramount}` | Total amount of credit applied to this order as a result of a gift voucher
`{tag_invoicediscountamount}` | Total discount amount based on the discount code entered (shipping price is not discounted)
`{tag_invoicetotal}` | Total cost of the current cart (factoring in all costs and discounts)
`{tag_invoicetotalextaxamount}` | Invoice total amount excluding tax (products ex tax + shipping ex tax)
`{tag_orderid}` | Order ID normally assigned to quotes. Can search on this value via Customer section
`{tag_productcode}` | Product code of the product in the cart
`{tag_productdescription}` | Product description captured from the "Instructions" box or "Product Attributes"
`{tag_producteditorcontent}` | Product description as it appears in the WYSIWYG editor
`{tag_productextaxamount}` | Price of each product excluding tax in the cart
`{tag_productgrandtotal}` | Total price of all products including tax in the cart
`{tag_productimage}` | Small image of the product
`{tag_productinctaxamount}` | Price of each product including tax in the cart
`{tag_productname_nolink}` | Product name already in the cart without a link back to the product
`{tag_productname}` | List of product names in the cart
`{tag_productquantity}` | Number of units of each product in the cart
`{tag_productremovelink}` | Link to remove product from the cart
`{tag_productsubtotal}` | Total price of all products excluding tax in the cart
`{tag_producttaxamount}` | Amount of tax for each product in the cart
`{tag_producttaxpercentage}` | For example, `{tag_producttaxpercentage,percentage}` where customer can supply the percentage in the tag, like 10% for OZ or 12.5% for Europe and the system gets the percentage of the amount and display it.
`{tag_producttaxrate}` | Tax rate associated with each product in the cart
`{tag_producttaxtotal}` | Total tax amount for all products in the cart
`{tag_producttotal}` | Total price of each product in the cart (units x unit price inc tax)
`{tag_producttotalextax}` | Total amount for product excluding tax (Product x Quantity)
`{tag_shippingextaxamount}` | Price of shipping option chosen excluding tax
`{tag_shippingoptions,X,Y,Z}` | List of shipping options. Set X to true to enable state tax. Set Y to true to enable state tax regardless of customer country (otherwise only for customers in your country). Set Z to 2-letter country code to limit shipping country; for example, US for United States.
`{tag_shippingtaxamount}` | Amount of tax associated with the shipping option chosen
`{tag_shippingtaxrate}` | Tax rate associated with the shipping option chosen
`{tag_shippingtotal}` | Total cost of the shipping option chosen (shipping ex tax + shipping tax)
`{tag_totaltaxpercentage,percentage, calculateBeforeShipping,calculateBeforeDiscount}` | where the customer can supply the tax percentage as a tag parameter, such as 10 for 10% in Australia or 12.5 for 12.5% in Europe. The system calculates the percentage of the amount and display it. Enter "true" or "false" for calculateBeforeShipping and calculateBeforeDiscount to set when the tax percentage is calculated.
`{tag_totalunits}` | Total product units in the cart

repository: itbusiness/bc-reference

repo_name: itbusiness/bc-reference


text:
---
title: '[LeetCode 28] Implement strStr()'
published: true
tags: TwoPointers
---

## Problem

Implement `strStr()`.

Return the index of the first occurrence of needle in haystack, or `-1` if `needle` is not part of `haystack`.

### Clarification:

What should we return when `needle` is an empty string? This is a great question to ask during an interview.

For the purpose of this problem, we will return 0 when needle is an empty
string. This is consistent to C's `strstr()` and Java's `indexOf()`.

### Example 1:

```
Input: haystack = "hello", needle = "ll"
Output: 2
```

### Example 2:

```
Input: haystack = "aaaaa", needle = "bba"
Output: -1
```

### Example 3:

```
Input: haystack = "", needle = ""
Output: 0
```

### Constraints:

```
- 0 <= haystack.length, needle.length <= 5 * 104
- haystack and needle consist of only lower-case English characters.
```

## Thoughts

- We can find the first character in haystack that is the same as the first one
  in needle, then checking if the following characters are the same

## Typescript

```typescript
function strStr(haystack: string, needle: string): number {
    if(needle.length === 0) return 0;

    let res = -1;

    for(let i = 0; i < haystack.length; i++){
        if(res !== -1) break;
        // we can check needle here
        if(haystack[i] === needle[0]) {
            let temp = true
            // check next few characters in haystack with needle
            for(let j = i + 1; j < needle.length + i; j++) {
                if(haystack[j] !== needle[j - i]) {
                    temp = false;
                }
            }
            if(temp) {
                res = i;
                return res;
            }
        }
    }

    return res;
};
```

## Reference

- [https://leetcode.com/problems/implement-strstr/](https://leetcode.com/problems/implement-strstr/)


text:
#Solution on C
This is the solution in C (with POSIX Threads) for the problem called Santa Claus.
It is similar to the solution with Python.
Just used C with POSIX Threads and **semaphores**.

To run:

```
gcc SantaClaus.c -o SantaClaus

./SantaClaus
```

path: /C solution using Semaphores/README.md


text:
---
# Display name
name: Pablo Andrés Contreras Kallens

# Username (this should match the folder name)
authors:
- admin

# Is this the primary user of the site?
superuser: true

# Role/position
role: Ph. D. Student

# Organizations/Affiliations
organizations:
- name: Department of Psychology, Cornell University
  url: "https://psychology.cornell.edu/"
- name: Cognitive Neuroscience Lab
  url: "http://cnl.psych.cornell.edu/"
- name: Co-Mind Lab
  url: "https://co-mind.org/"

# Short bio (displayed in user profile at end of posts)
bio: My research interests include distributed language, language evolution and computational modeling.

interests:
- Cognitive Science
- Data Analysis
- Language Evolution
- Language and Cognition
- Science of Science

education:
  courses:
  - course: Ph. D. in Psychology
    institution: Cornell University
    year: Current
  - course: MA in Philosophy
    institution: Universidad de Chile
    year: 2015
  - course: BA in Philosophy
    institution: Universidad de Chile
    year: 2012

# Social/Academic Networking
# For available icons, see: https://sourcethemes.com/academic/docs/page-builder/#icons
#   For an email link, use "fas" icon pack, "envelope" icon, and a link in the
#   form<EMAIL_ADDRESS>or "#contact" for contact widget.
social:
- icon: envelope
  icon_pack: fas
  link<EMAIL_ADDRESS># For a direct email link, use<EMAIL_ADDRESS>- icon: twitter
  icon_pack: fab
  link: https://twitter.com/omfgzell
- icon: google-scholar
  icon_pack: ai
  link: https://scholar.google.com/citations?user=GU6r0m4AAAAJ&hl=en
- icon: github
  icon_pack: fab
  link: https://github.com/contreraskallens
- icon: cv
  icon_pack: ai
  link: files/cv.pdf

# Enter email to display Gravatar (if Gravatar enabled in Config)
email: ""

# Organizational groups that you belong to (for People widget)
#   Set this to `[]` or comment out if you are not using People widget.
# user_groups:
# Researchers
# Visitors
---
Hey! I’m a Ph. D. Student at the Department of Psychology, Cornell University. I’m a member of the Cognitive Neuroscience Lab at Cornell University and the Co-Mind Lab at the University of California, Los Angeles. My main research interests lie in the foundations of modern culturally-transformed human cognition, especially through symbol use, language and categorization. Having a background in Philosophy of Science, I’m also interested in data-driven exploration of scientific activity. I like to tackle these topics through a combination of theory-driven hypothesis formation and computational data analysis.

repository: contreraskallens/academic-kickstart

repo_name: contreraskallens/academic-kickstart


text:
## Checking for coding standards

Make sure that your IDE has support for [stylelint](https://stylelint.io/) or run:
```
npm run lint:style
```

This will ensure that you write styles in a consistent manner.

> NOTE: The stylelint config for this project is based on the Bootstrap v4 config.

## Code snippets

To import helper mixins and variables from the `includes` directory:
```scss
@import "app-styling-utils";
@import "app-styling-variables";

.app-message--success {
  background-color: app-get-color($app-status-colors, "success");
  color: app-get-contrast($app-status-colors, "success");
}

.app-box .app-box__title {
  background-color: app-get-contrast($app-text-colors, "normal");
  color: app-get-color($app-text-colors, "normal");
}
```


text:
# Flip

[![The most recent stable version is 0.2.0][version-image]][semantic versioning]
[![Current build status image][build-image]][current build status]
[![Current coverage status image][coverage-image]][current coverage status]

[build-image]: http://img.shields.io/travis/IcecaveStudios/flip/develop.svg?style=flat-square "Current build status for the develop branch"
[current build status]: https://travis-ci.org/IcecaveStudios/flip
[coverage-image]: https://img.shields.io/codecov/c/github/IcecaveStudios/flip/develop.svg?style=flat-square "Current test coverage for the develop branch"
[current coverage status]: https://coveralls.io/r/IcecaveStudios/flip
[semantic versioning]: http://semver.org/
[version-image]: http://img.shields.io/:semver-0.2.0-yellow.svg?style=flat-square "This project uses semantic versioning"

**Flip** is a tiny PHP library for working with strict sets of boolean flags.

- Install via [Composer] package [icecave/flip]
- Read the [API documentation]

[api documentation]: http://icecavestudios.github.io/flip/artifacts/documentation/api/
[composer]: http://getcomposer.org/
[icecave/flip]: https://packagist.org/packages/icecave/flip

## Defining a flag-set

A flag-set describes the available flags of a given type. Flag-sets are defined
by declaring a class that uses the `FlagSetTrait` trait.

Each property in the class defines a named flag that can be set to `true` or
`false`. All properties must be private and have a default boolean value.

```php
use Icecave\Flip\FlagSetTrait;

final class ExampleFlags
{
    use FlagSetTrait;

    private $foo = true;
    private $bar = false;
    private $baz = false;
}
```

## Creating a flag-set

The flag-set trait provides the following static methods for quickly creating
common sets:

* `defaults()` - creates a flag-set where all flags are set to the default values
* `all()` - creates a flag-set where all flags are set to `true`
* `none()` - creates a flag-set where all flags are set to `false`

Flag-sets can also be created and modified using a fluent interface. The example
below creates a flag-set with only the `bar` and `baz` properties set to `true`.

```php
$flags = ExampleFlags::none()
    ->bar(true)
    ->baz(true);
```

Omitting the initial call to `defaults()`, `all()` or `none()` is short-hand
for using the defaults. This means that the following two examples are equivalent:

```php
$flags = ExampleFlags::defaults()
    ->foo(false)
    ->bar(true);
```

```php
$flags = ExampleFlags
    ::foo(false)
    ->bar(true);
```

Flag-sets are immutable, each call to the fluent interface returns a new
instance with the updated flag value.

Flags can not be named "defaults", "all" or "none".

## Using a flag-set

**Functions that accept flag-sets as parameters can use a type-hint.** Flags are
read using the regular PHP property notation. Flag values are guaranteed to be a
boolean.

```php
function dumpFlags(ExampleFlags $flags)
{
    if ($flags->foo) {
        echo 'Foo is enabled!';
    } else {
        echo 'Foo is disabled!';
    }

    if ($flags->bar) {
        echo 'Bar is enabled!';
    } else {
        echo 'Bar is disabled!';
    }

    if ($flags->baz) {
        echo 'Baz is enabled!';
    } else {
        echo 'Baz is disabled!';
    }
}
```

It is not possible to set flags using the property notation.

## Contact us

- Follow [@IcecaveStudios] on Twitter
- Visit the [Icecave Studios website]

[@icecavestudios]: https://twitter.com/IcecaveStudios
[icecave studios website]: http://icecave.com.au/

repository: IcecaveStudios/flip

branch_name: refs/heads/develop

gha_language: PHP

repo_name: IcecaveStudios/flip


text:
---
# Leave the homepage title empty to use the site title
title:
date: 2023-06-08
type: landing

sections:
  - block: about.biography
    id: about
    content:
      title: Biography
      # Choose a user profile to display (a folder name within `content/authors/`)
      username: admin
  - block: collection
    content:
      title: Recent Publications
      text: |-
        {{% callout note %}}
        Quickly discover relevant content by [filtering publications](./publication/).
        {{% /callout %}}
      filters:
        folders:
          - publication
        exclude_featured: true
    design:
      columns: '2'
      view: citation
  - block: tag_cloud
    content:
      title: Popular Topics
    design:
      columns: '2'
  - block: contact
    id: contact
    content:
      title: Contact
      subtitle:
      text: |-
        Get in touch:
      # Contact (add or remove contact options as necessary)
      email<EMAIL_ADDRESS>      phone:<PHONE_NUMBER>
      appointment_url: 'https://fantastical.app/cwimpy-yBqk/schedule'
      address:
        street: PO Box 1750
        city: State University
        region: AR
        postcode: '72467'
        country: United States
        country_code: US
      office_hours:
        - By appoitnment only
      contact_links:
        - icon: twitter
          icon_pack: fab
          name: Follow Me
          link: 'https://twitter.com/camwimpy'
        - icon: video
          icon_pack: fas
          name: Zoom Me
          link: 'https://astatecall.zoom.us/my/cwimpy'
      # Automatically link email and phone or display as text?
      autolink: true
      # Email form provider
      form:
        provider: netlify
        formspree:
          id:
        netlify:
          # Enable CAPTCHA challenge to reduce spam?
          captcha: true
    design:
      columns: '2'
---

repository: cwimpy/website

repo_name: cwimpy/website


text:
# Kennerton Jimo
See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info.

### Parametric EQs
In case of using parametric equalizer, apply preamp of **-6.7dB** and build filters manually
with these parameters. The first 5 filters can be used independently.
When using independent subset of filters, apply preamp of **-6.7dB**.

| Type    | Fc       |    Q | Gain     |
|:--------|:---------|:-----|:---------|
| Peaking | 38 Hz    | 0.24 | -6.1 dB  |
| Peaking | 171 Hz   | 0.57 | -6.0 dB  |
| Peaking | 440 Hz   | 0.64 | -5.9 dB  |
| Peaking | 3797 Hz  | 0.09 | 7.6 dB   |
| Peaking | 17664 Hz | 0.56 | -26.0 dB |
| Peaking | 654 Hz   | 3.97 | -0.2 dB  |
| Peaking | 4738 Hz  | 2.62 | 1.8 dB   |
| Peaking | 6122 Hz  | 4.21 | -5.4 dB  |
| Peaking | 12870 Hz | 2.61 | 8.8 dB   |
| Peaking | 15356 Hz | 1.42 | -4.6 dB  |

### Fixed Band EQs
In case of using fixed band (also called graphic) equalizer, apply preamp of **-7.3dB**
(if available) and set gains manually with these parameters.

| Type    | Fc       |    Q | Gain     |
|:--------|:---------|:-----|:---------|
| Peaking | 31 Hz    | 1.41 | -6.3 dB  |
| Peaking | 62 Hz    | 1.41 | -5.7 dB  |
| Peaking | 125 Hz   | 1.41 | -7.9 dB  |
| Peaking | 250 Hz   | 1.41 | -6.9 dB  |
| Peaking | 500 Hz   | 1.41 | -2.8 dB  |
| Peaking | 1000 Hz  | 1.41 | 3.8 dB   |
| Peaking | 2000 Hz  | 1.41 | 5.4 dB   |
| Peaking | 4000 Hz  | 1.41 | 5.2 dB   |
| Peaking | 8000 Hz  | 1.41 | 2.7 dB   |
| Peaking | 16000 Hz | 1.41 | -22.0 dB |

### Graphs
![](https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/results/crinacle/harman_in-ear_2017-1/Kennerton%20Jimo/Kennerton%20Jimo.png)


text:
This is a quick utility to find matching [DMC](http://www.dmc-usa.com/)
embroidery floss for a particular colour.

Usage:

    ./find.py <hex-colour>

Example:

    $ ./find.py 96bad5
    Finding close matches for colour 96bad5
    Top 10 recommendations:
            519 ("Sky Blue")
            794 ("Cornflower Blue - LT")
            827 ("Blue - VY LT")
            809 ("Delft Blue")
            3755 ("Baby Blue (?)")
            598 ("Turquoise - LT")
            341 ("Blue Violet - LT")
            3325 ("Baby Blue - LT")
            3840 ("Lavender Blue - LT")
            3761 ("Sky Blue - LT")

All data scraped from [camelia.sk](http://www.camelia.sk) and verified when
possible against DMC's USA website and personal thread supplies to ensure that
the colours in the database match. Corrections welcome!

repository: etherealvisage/find-dmc

repo_name: etherealvisage/find-dmc


text:
## Centos7 base image

This image is a minimally modified Centos7 configured with sensible defaults for hosting a Kubernetes cluster.

## Quickstart

Simply install and configure [packer](https://www.packer.io/) and fork this repo to customize.

> packer build packer.json

## Dependencies

- Packer 0.11+
- Ansible 2.1+ installed ([installation instructions] (http://docs.ansible.com/ansible/intro_installation.html))

repository: Global-localhost/demo

repo_name: Global-localhost/demo


text:
# A Comprehensive Survey of C. elegans Argonaute Proteins Reveals Organism-wide Gene Regulatory Networks and Functions

This repository holds scripts to perform small RNA alignment and counting as described in Seroussi et. al. 2023.

Uri Seroussi, Andrew Lugowski, Lina Wadi, Robert X Lao, Alexandra R Willis, Winnie Zhao, Adam E Sundby, Amanda G Charlesworth, Aaron W Reinke, Julie M Claycomb (2023) A comprehensive survey of C. elegans argonaute proteins reveals organism-wide gene regulatory networks and functions eLife 12:e83853

https://doi.org/10.7554/eLife.83853

## Summary of scripts

### The pipeline

If you wish to follow the exact same process as described in Seroussi et. al. 2023, you can follow the instruction in main_pipline.sh

```
# QA and Counting of reads against the C. elegans genome as in Seroussi et. al. 2023

# Starting point: current working directory should hold fastq.gz files

# Run the commands below in order in terminal

# MD5 Checksum

# Check if any files were corrupted during downloading

ls \*fastq.gz > fastq.txt
$(pwd)/scripts/checkMD5.sh fastq.txt

# Run FastQC - QC analysis tool,reads a set of sequence files and produces from each one a quality control report.

mkdir qc_fastq
fastqc --outdir ./qc_fastq --threads 12 \*fastq.gz

# Cutadapt to remove adapters

# Also discard reads shorter than length=16 (-m), and discard reads longer than 30 (-M)

mkdir cutadapt
adapter3_nebnext=AGATCGGAAGAGCACACGTCTGAACTCCAGTCAC
parallel -j 12 \
cutadapt -a $adapter3_nebnext -f fastq -m 16 -M 30 --discard-untrimmed -o cutadapt/{} {} ::: \*.fastq.gz

# Rerun fastQC post adapter removal

mkdir qc_cutadapt_fastq
fastqc --outdir qc_cutadapt_fastq --threads 12 cutadapt/\*.fastq.gz

# Create a text file with all the samples that need to be processed

find $(pwd)/cutadapt/\*.fastq > fastq.txt

# Generate indexes for your favourite genome reference as in https://github.com/alexdobin/STAR/blob/master/doc/STARmanual.pdf

# Directory of where the STAR indices of your genome are

GENOME=$(pwd)/genome_data/STAR_indices/YOUR_STAR_INDICES_OF_SELECTED_GENOME

# modify this directory for your current working directory

MAIN_DIR=$(pwd)

# Run STAR

while read fastq;
do
base=`basename ${fastq}`
mkdir ${base%.fastq.gz} && cd $\_
STAR \
 --runThreadN 12 \
 --genomeDir ${GENOME} \
 --readFilesIn ${fastq} \
 --readFilesCommand zcat \
 --outSAMtype BAM SortedByCoordinate \
 --quantMode GeneCounts \
 --limitBAMsortRAM<PHONE_NUMBER>0 \
 --outFilterMultimapNmax 50 \
 --outFilterMultimapScoreRange 0 \
 --outFilterMismatchNoverLmax 0.05 \
 --outFilterMatchNmin 16 \
 --outFilterScoreMinOverLread 0 \
 --outFilterMatchNminOverLread 0 \
 --alignIntronMax 1 \
 --genomeLoad LoadAndKeep
cd ${MAIN_DIR}

done < fastq.txt

# Move resulting folders to a new folder called 'STAR'

mkdir STAR;

# Make sure all your samples are in the STAR folder then run the counting script

for bam in `find STAR | grep .bam$`;
do
echo $bam;
Rscript $(pwd)/scripts/counting_script.R ${bam}
done >> output.txt
```

### Counting Script

If you wish to only use the counting script on a given BAM file, run `> Rscript counting_script.R file.bam`.
The reference directory holds genome annotations of genes and their parts.
The WormBase version WS276 PRJNA13758 ce11 canonical geneset annotations were used (excluding miRNAs, repeats and transposons). C. elegans miRNA annotations were obtained from miRBase (release 22.1). For repeats and transposons RepeatMasker + Dfam (ce10 - Oct 2010 - RepeatMasker open-4.0.6 - Dfam 2.0) annotations were used. The UCSC Lift Genome Annotations tool was used to convert ce10 coordinates to ce11 coordinates.


text:
Documentation
=============

The code is documented with [JSDuck](https://github.com/senchalabs/jsduck)
comments.

To generate documentation site, you need to install JSDuck:

    gem install jsduck

And run the command:

    jsduck -o output-directory/ dataflows.js/

Don't mind the warnings (JSDuck isn't aware of Node.js built-ins).

repository: apla/zmok

repo_name: apla/zmok


text:
# 10003 - Cutting Sticks

You have to cut a wood stick into pieces. The most affordable company, The Analog Cutting Machinery,
Inc. (ACM), charges money according to the length of the stick being cut. Their procedure of work
requires that they only make one cut at a time.
It is easy to notice that different selections in the order of cutting can led to different prices. For
example, consider a stick of length 10 meters that has to be cut at 2, 4 and 7 meters from one end.
There are several choices. One can be cutting first at 2, then at 4, then at 7. This leads to a price
of 10 + 8 + 6 = 24 because the first stick was of 10 meters, the resulting of 8 and the last one of 6.
Another choice could be cutting at 4, then at 2, then at 7. This would lead to a price of 10 + 4 + 6 =
20, which is a better price.
Your boss trusts your computer abilities to find out the minimum cost for cutting a given stick.

## Input

The input will consist of several input cases. The first line of each test case will contain a positive
number *l* that represents the length of the stick to be cut. You can assume *l* < 1000. The next line will
contain the number *n* (*n* < 50) of cuts to be made.
The next line consists of *n* positive numbers *ci* (0 < *ci* < *l*) representing the
places where the cuts have to be done, given in strictly increasing order.
An input case with *l* = 0 will represent the end of the input.

## Output

You have to print the cost of the optimal solution of the cutting problem, that is the minimum cost of
cutting the given stick. Format the output as shown below.

## Sample Input

```
100
3
25 50 75
10
4
4 5 7 8
0
```

## Sample Output

```
The minimum cutting is 200.
The minimum cutting is 22.
```

[\[pdf\]](https://uva.onlinejudge.org/external/100/10003.pdf)

path: /10003 - Cutting Sticks/README.md


text:
# Installing Istio using Helm

In this video are going to install Istio using the Helm package manager.

## Prerequesites

You will need a running Kubernetes with enough resources. If you install
Istio locally in Docker Desktop make sure you followed the instructions
under https://istio.io/docs/setup/platform-setup/docker/

## Step 1: Setup and Verify

First, you need to download and setup the latest Istio release.
At the time of writing this is `1.3.4`, upgrade to latest version if desired.
```
$ curl -L https://git.io/getLatestIstio | ISTIO_VERSION=1.3.4 sh -

$ cd istio-1.3.4
$ export PATH=$PWD/bin:$PATH

$ istioctl verify-install
```

## Step 2: Install Helm

In this step we are installing and initializing the Helm package manager
in the Kubernetes cluster

```
# Install Helm
$ curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get | bash

# "Initialize Helm"
# add a service account within a namespace to segregate tiller
kubectl apply -f install/kubernetes/helm/helm-service-account.yaml

helm init --service-account tiller
helm repo update

# verify that helm is installed in the cluster
kubectl get deploy,svc tiller-deploy -n kube-system
```

## Step 3: Install Istio

```
# deploy Istio via Helm
$ helm repo add istio.io https://storage.googleapis.com/istio-release/releases/1.3.4/charts/

# Install the istio-init chart to bootstrap all the Istio CRDs
$ helm install install/kubernetes/helm/istio-init --name istio-init --namespace istio-system
$ kubectl get crds | grep 'istio.io' | wc -l

# install the istio chart using demo profile
$ helm install install/kubernetes/helm/istio --name istio --namespace istio-system --values install/kubernetes/helm/istio/values-istio-demo.yaml

# Verifying the installation
$ kubectl get pods -n istio-system
$ kubectl get svc -n istio-system
```

## (Optional) Step 4: Uninstall Istio

In case you want to uninstall Istio using Helm, issue the following commands:
```
$ helm delete --purge istio
$ helm delete --purge istio-init
$ kubectl label namespace default istio-injection-
```


text:
---
breadcrumbs:
- label: Countries
  url: "../../"
- label: Ethiopia
  url: "../"
layout: featured_site
contentful:
  sys:
    id: 5I6VFY4EX6GOW2mCag08aU
    created_at: !ruby/object:DateTime 2015-11-25 11:54:40.762000000 Z
    updated_at: !ruby/object:DateTime 2015-12-07 20:52:58.329000000 Z
    content_type_id: featured_site
    revision: 5
  title: Shepe, Ethiopia
  slug: shepe
  chapters:
  - sys:
      id: 4ixjUTf8kEQuQk4GMOy4W6
      created_at: !ruby/object:DateTime 2015-11-25 10:41:05.845000000 Z
      updated_at: !ruby/object:DateTime 2017-01-11 11:21:10.230000000 Z
      content_type_id: chapter
      revision: 5
    title_internal: 'Ethiopia: featured site, chapter 1'
    body: The site of Shepe (also known as Chabbé, Šappe or Mancheti) is located in
      the Sidamo Zone of Oromia, about 250 km to the south of Addis Ababa. The region
      is a fertile, forest-mountainous area traditionally dedicated to the cultivation
      of coffee. The site is in a narrow gorge carved by the Shepe River at 1300 m
      above sea level, full of vegetation and therefore difficult to detect. Along
      this gorge there are several notable  engravings depicted in four panels, forming
      one of the most impressive – if secluded —  rock art sites in the Horn of Africa.
      The site was discovered in 1965 by Fitaorari Selechi Defabatchaw, governor of
      the Dilla district where the site is located, and was published by Francis Anfray
      two years later. Since that, the importance of Shepe has been widely recognized
      and some other sites with similar engravings have been documented in the surrounding
      area. This group (known generically as the Shepe-Galma group) constitutes one
      of the main areas of Ethiopian rock art, the other being the Laga Oda-Sourré
      group in the Harar region.
    images_and_captions:
    - sys:
        id: 5EG7K0Z26cUMISeKsAww4s
        created_at: !ruby/object:DateTime 2015-11-25 10:47:14.674000000 Z
        updated_at: !ruby/object:DateTime 2015-11-25 10:47:14.674000000 Z
        content_type_id: image
        revision: 1
      image:
        sys:
          id: pU5IbmTygg4ka2kYisEyc
          created_at: !ruby/object:DateTime 2015-11-25 10:45:07.360000000 Z
          updated_at: !ruby/object:DateTime 2015-11-25 10:45:07.360000000 Z
        title: '2013,2034.16227'
        description:
        url: "//images.ctfassets.net/xt8ne4gbbocd/pU5IbmTygg4ka2kYisEyc/72c98385edd3833e70e9763f66945e98/ETHSID0050002.jpg"
      caption: View of the crease where the Shepe engravings are placed. Shepe, Ethiopia.
        2013,2034.16227.
      col_link: http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=3691737&partId=1&searchText=2013,2034.16227&page=1
  - sys:
      id: 5EG7K0Z26cUMISeKsAww4s
      created_at: !ruby/object:DateTime 2015-11-25 10:47:14.674000000 Z
      updated_at: !ruby/object:DateTime 2015-11-25 10:47:14.674000000 Z
      content_type_id: image
      revision: 1
    image:
      sys:
        id: pU5IbmTygg4ka2kYisEyc
        created_at: !ruby/object:DateTime 2015-11-25 10:45:07.360000000 Z
        updated_at: !ruby/object:DateTime 2015-11-25 10:45:07.360000000 Z
      title: '2013,2034.16227'
      description:
      url: "//images.ctfassets.net/xt8ne4gbbocd/pU5IbmTygg4ka2kYisEyc/72c98385edd3833e70e9763f66945e98/ETHSID0050002.jpg"
    caption: View of the crease where the Shepe engravings are placed. Shepe, Ethiopia.
      2013,2034.16227.
    col_link: http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=3691737&partId=1&searchText=2013,2034.16227&page=1
  - sys:
      id: 1meXvF3KKYugMos2qqyyyA
      created_at: !ruby/object:DateTime 2015-11-25 10:50:09.415000000 Z
      updated_at: !ruby/object:DateTime 2017-01-11 11:21:36.739000000 Z
      content_type_id: chapter
      revision: 2
    title_internal: 'Ethiopia: featured site, chapter 2'
    body: 'The rock art of Shepe consists almost exclusively of engravings of humpless
      cows which follow very strict conventions: profile bodies, small heads with
      long horns seen from above, U-like bellies and udders very clearly depicted.
      Some of the cows have an unidentified, triangular object hanging from their
      left horn. In total, around 50 relatively large cows (40 to 70 cm in length)
      are depicted throughout the gorge walls, distributed in rows and groups to represent
      herds. The most original feature of these engravings is, however, the technique
      used to depict them: rather than carving the outline of the cows, the area around
      them has been lowered to provide a bas-relief effect which has no known parallels
      in the region. The surface of the cows has been polished to obtain a smooth
      appearance.'
    images_and_captions:
    - sys:
        id: 3t1tUJZNRY4kkQAIeKmIea
        created_at: !ruby/object:DateTime 2015-11-25 10:50:00.721000000 Z
        updated_at: !ruby/object:DateTime 2015-11-25 10:50:00.721000000 Z
        content_type_id: image
        revision: 1
      image:
        sys:
          id: 4wQ6Srd7EI0ckCYoA4IaWS
          created_at: !ruby/object:DateTime 2015-11-25 10:45:25.200000000 Z
          updated_at: !ruby/object:DateTime 2015-11-25 10:45:25.200000000 Z
        title: '2013,2034.16236'
        description:
        url: "//images.ctfassets.net/xt8ne4gbbocd/4wQ6Srd7EI0ckCYoA4IaWS/3b87b98a6668f272110f5baf48e65a5b/ETHSID0060007.jpg"
      caption: View of the Shepe main panel. Shepe, Ethiopia. 2013,2034.16236.
      col_link: http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=3691722&partId=1&searchText=2013,2034.16236&page=1
  - sys:
      id: 3t1tUJZNRY4kkQAIeKmIea
      created_at: !ruby/object:DateTime 2015-11-25 10:50:00.721000000 Z
      updated_at: !ruby/object:DateTime 2015-11-25 10:50:00.721000000 Z
      content_type_id: image
      revision: 1
    image:
      sys:
        id: 4wQ6Srd7EI0ckCYoA4IaWS
        created_at: !ruby/object:DateTime 2015-11-25 10:45:25.200000000 Z
        updated_at: !ruby/object:DateTime 2015-11-25 10:45:25.200000000 Z
      title: '2013,2034.16236'
      description:
      url: "//images.ctfassets.net/xt8ne4gbbocd/4wQ6Srd7EI0ckCYoA4IaWS/3b87b98a6668f272110f5baf48e65a5b/ETHSID0060007.jpg"
    caption: View of the Shepe main panel. Shepe, Ethiopia. 2013,2034.16236.
    col_link: http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=3691722&partId=1&searchText=2013,2034.16236&page=1
  - sys:
      id: 2MCiQOzg1WWksmyW4kiCko
      created_at: !ruby/object:DateTime 2015-11-25 10:51:18.446000000 Z
      updated_at: !ruby/object:DateTime 2015-11-25 10:51:18.446000000 Z
      content_type_id: chapter
      revision: 1
    title_internal: 'Ethiopia: featured site, chapter 3'
    body: The chronology of the Shepe cows is difficult to determine, but stylistically
      they have been related to the Laga Oda paintings in the area of Harar and to
      other sites in Eritrea and Djibouti. According to most researchers, the Shepe
      figures have been ascribed to the so-called Ethiopian-Arabian style, with a
      generic chronology from the 3rd to the 1st millennia BC. Shepe engravings can
      be considered relatively naturalistic, and therefore should be among the oldest
      depictions of this style. Other interpretations, however, consider Shepe and
      the nearby sites a completely differentiated school whose chronology is still
      unclear but could be more recent.
    images_and_captions:
    - sys:
        id: 23e0al3lEEaeCEawuaEuei
        created_at: !ruby/object:DateTime 2015-11-25 10:51:09.956000000 Z
        updated_at: !ruby/object:DateTime 2015-11-25 10:51:09.956000000 Z
        content_type_id: image
        revision: 1
      image:
        sys:
          id: 2NxPqNw24UkMkmY0oAeMUW
          created_at: !ruby/object:DateTime 2015-11-25 10:45:40.809000000 Z
          updated_at: !ruby/object:DateTime 2015-11-25 10:45:40.809000000 Z
        title: '2013,2034.16235'
        description:
        url: "//images.ctfassets.net/xt8ne4gbbocd/2NxPqNw24UkMkmY0oAeMUW/2722889dec86c49a3d5c1fa47f5c96ff/ETHSID0060006.jpg"
      caption: Frontal view of one the Shepe panels. Shepe, Ethiopia. 2013,2034.16235.
      col_link: http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=3691723&partId=1&searchText=2013,2034.16235&page=1
  - sys:
      id: 23e0al3lEEaeCEawuaEuei
      created_at: !ruby/object:DateTime 2015-11-25 10:51:09.956000000 Z
      updated_at: !ruby/object:DateTime 2015-11-25 10:51:09.956000000 Z
      content_type_id: image
      revision: 1
    image:
      sys:
        id: 2NxPqNw24UkMkmY0oAeMUW
        created_at: !ruby/object:DateTime 2015-11-25 10:45:40.809000000 Z
        updated_at: !ruby/object:DateTime 2015-11-25 10:45:40.809000000 Z
      title: '2013,2034.16235'
      description:
      url: "//images.ctfassets.net/xt8ne4gbbocd/2NxPqNw24UkMkmY0oAeMUW/2722889dec86c49a3d5c1fa47f5c96ff/ETHSID0060006.jpg"
    caption: Frontal view of one the Shepe panels. Shepe, Ethiopia. 2013,2034.16235.
    col_link: http://www.britishmuseum.org/research/collection_online/collection_object_details.aspx?objectId=3691723&partId=1&searchText=2013,2034.16235&page=1
  - sys:
      id: 5Ts9l53bJ6uU4OKaqYEAMO
      created_at: !ruby/object:DateTime 2015-11-25 10:51:54.888000000 Z
      updated_at: !ruby/object:DateTime 2015-12-11 12:20:03.439000000 Z
      content_type_id: chapter
      revision: 2
    title_internal: 'Ethiopia: featured site, chapter 4'
    body: Regarding their meaning, only conjecture can be made at present, but it
      seems quite likely that they were made by pastoral communities to whom cattle
      were fundamental. The careful depiction of the udders, the repetition of this
      single motif and the effort paid to achieve the bas-relief effect imply a paramount
      importance of cattle in the economy and society of the group that engraved them.
      The fact that some of the cows have what seem to be adornments hanging from
      the horns (a feature documented in other rock art regions as the Libyan Messak)
      also points in that direction. Contemporary groups, such as the Nuer in nearby
      Sudan have similar traditions of horn adornments, and throughout the Omo river
      region different techniques of embellishment (ear cutting, horn shaping, modifications
      of the hump) have been documented, and in all of them cattle are a key cultural
      mark as well as an economic resource.  Of course, direct links cannot be established
      between these contemporary examples and the communities that made the engravings
      of Shepe, but the cattle depictions in the ravine are nevertheless a document
      of the importance and consideration given to cattle, an animal which was undoubtedly
      part of these groups’ identity.
  citations:
  - sys:
      id: 435YtX7CQ08gcuU240ucwc
      created_at: !ruby/object:DateTime 2015-11-25 10:52:31.089000000 Z
      updated_at: !ruby/object:DateTime 2015-12-11 12:20:33.907000000 Z
      content_type_id: citation
      revision: 3
    citation_line: |-
      Anfray, F. (1967): Les sculptures rupestres de Chabbè dans le Sidamo. *Annales d'Ethiopie* 7: 19-32.

      Joussaume, R. (ed.) (1995): *Tiya, l’Ethiopie des mégalithes : du biface à l’art rupestre dans la Corne de l’Afrique*. Association des publications chauvinoises (A.P.C.), Chauvigny.

      Le Quellec, J.-L., & G. Abegaz (2001): New sites of South Ethiopian rock engravings: Godana Kinjo, Ejersa Gara Hallo, and remarks on the Sappe-Galma School. *Annales d’Ethiopie*, 17: 205-224.
  background_images:
  - sys:
      id: 6bqPx8NVF6CsoC6kS4KkQ4
      created_at: !ruby/object:DateTime 2015-12-07 20:36:14.616000000 Z
      updated_at: !ruby/object:DateTime 2015-12-07 20:36:14.616000000 Z
    title: ETHSID0080008
    description:
    url: "//images.ctfassets.net/xt8ne4gbbocd/6bqPx8NVF6CsoC6kS4KkQ4/2b81668d390ad745fc484b83c33c3548/ETHSID0080008.jpg"
  - sys:
      id: 6johOxHojKY4EkOqEco6c6
      created_at: !ruby/object:DateTime 2015-11-25 19:45:27.772000000 Z
      updated_at: !ruby/object:DateTime 2015-11-25 19:45:27.772000000 Z
    title: ETHSOD0030007
    description:
    url: "//images.ctfassets.net/xt8ne4gbbocd/6johOxHojKY4EkOqEco6c6/2640f76a5871320bf2ff03fefd8c37a7/ETHSOD0030007.jpg"
---

repository: kingsdigitallab/african-rock-art

repo_name: kingsdigitallab/african-rock-art


text:
![NoticeBoard](art/noticeboard_banner.png)

NoticeBoard
-------

![GitHub](https://img.shields.io/github/license/furkanakdemir/noticeboard)
![Bintray](https://img.shields.io/bintray/v/furkanakdemir/noticeboard/net.furkanakdemir.noticeboard)
![Codacy](https://img.shields.io/codacy/grade/656e09fc4d2645b4a4966858e539eada)
![CircleCI](https://img.shields.io/circleci/build/github/furkanakdemir/noticeboard/master)
![MinAPI](https://img.shields.io/badge/API-21%2B-blue)
[![Android Arsenal](https://img.shields.io/badge/Android%20Arsenal-NoticeBoard-orange.svg?style=flat)](https://android-arsenal.com/details/1/7938)

NoticeBoard is a changelog library for Android API 21+. It helps developers display the history of changes in their applications.

It shows a list of `Release` or `UnRelease` which contains a list of `Change`.

It receives a source of changes and config.

You can find a sample code of NoticeBoard in this repository.

`NoticeBoardSample` app is now available on Google Play.

Screenshot
-------

|ACTIVITY|DIALOG|
|----------|---------|
|![ACTIVITY](art/noticeboard_activity.png)|![DIALOG](art/noticeboard_dialog.png)|

Download
-------

```
dependencies {
    implementation "net.furkanakdemir:noticeboard:1.1.0"
}

```

Usage
-------

The `pin` function is used to show a change log list. It receives a lambda to make clients config their noticeboards.

Default configs are the following:
TITLE: NoticeBoard
DISPLAY_IN: Activity
SOURCE_TYPE: Dynamic with empty list

```java
NoticeBoard(this).pin {
    // configs
    title(...)
    displayIn(...)
    colorProvider(...)
    source(...)
}
```
`this` can be `Fragment` or `Activity`

### Title

The title of a noticeboard can be set by `title` function.

```java
NoticeBoard(this).pin {
    title("Release Notes")
}
```

### Tag

The tag of a noticeboard can be set by `tag` function.
It can be used to reset the number of noticeboard display after an update.

```java
NoticeBoard(this).pin {
    tag(versionCode)
}
```

### Display Options

NoticeBoard can be displayed in two ways.

Display Options  |
-----------------|
ACTIVITY         |
DIALOG           |

```java
NoticeBoard(this).pin {
    displayIn(ACTIVITY)
}
```

### Show Rules

The show rule of a noticeboard can be set by `showRule` function.

Show Rules |
-----------|
Once       |
Always     |
Limited    |

```java
NoticeBoard(this).pin {
    showRule(Once)
    showRule(Always)
    showRule(Limited(3))
}
```

### Color Provider

A color provider can be passed to provide the change type backgrounds.

Override the default color provider

``` java
class CustomColorProvider(private val context: Context) : NoticeBoardColorProvider(context) {
    override var colorAdded: Int = R.color.colorAccent
    override var colorChanged: Int = R.color.colorAccent
    override var colorDeprecated: Int = R.color.colorPrimary
    override var colorRemoved: Int = R.color.colorPrimary
    override var colorFixed: Int = R.color.colorPrimaryDark
    override var colorSecurity: Int = R.color.colorPrimaryDark
    override var colorDescriptionText = R.color.colorDescriptionCustom
    override var colorBackground: Int = R.color.colorBackgroundCustom
    override var colorTitleDialog: Int = R.color.colorTitleCustom
    override var colorTitleActivity: Int = R.color.colorTitleCustom
}
```

Or Implement `ColorProvider` interface

```java
class CustomColorProvider : ColorProvider {
    override fun getChangeTypeBackgroundColor(changeType: ChangeType): Int {

    }

    override fun getBackgroundColor(): Int {

    }

    override fun getDescriptionColor(): Int {

    }

    override fun getTitleColor(displayOptions: DisplayOptions): Int {

    }
}

```

Finally, a custom color provider can be set by `colorProvider` function.

```java
val customColorProvider = CustomColorProvider(this)

NoticeBoard(this).pin {
    colorProvider(customColorProvider)
}

```

### Unreleased Section

An unreleased section can be added to a noticeboard.

`UnRelease` can be created dynamically

or

`released` field can be set to false in JSON or XML file. (default: true)

The position of the unreleased section can be configured. (default: TOP)

Position  |
----------|
TOP       |
BOTTOM    |
NONE      |

If `TOP` or `BOTTOM` is selected, all of the unreleased items are merged into one list.
If `NONE` is selected, the items remains as it is.

```java
NoticeBoard(this).pin {
    unreleasedPosition(BOTTOM)
}

```

### Change Types

There are currently 6 built-in change types.

Change Type | Enum
------------|------------
ADDED       |0
CHANGED     |1
DEPRECATED  |2
REMOVED     |3
FIXED       |4
SECURITY    |5

### Source Types

There are currently 3 data source types.

Source  |
--------|
Dynamic |
Json    |
Xml     |

#### Dynamic

Save releases by creating dynamically

```java
val changes = listOf(
            Release("30 Sep 2019", "1.0.0",
                listOf(
                    Change("New Login Page", ADDED),
                    Change("Toolbar in Checkout", CHANGED),
                    Change("Old theme will be removed", DEPRECATED),
                    Change("Tutorial page is removed", REMOVED),
                    Change("Crash in Payment", FIXED),
                    Change("HTTPS only requests", SECURITY)
                )
            )
        )

NoticeBoard(this).pin {
    source(Dynamic(changes))
}
```

#### Json

Store releases by creating a json file to the `/assets` folder.

Here is an example of JSON file
```json
[
  {
    "date": "30 Sep 2019",
    "version": "1.0.0",
    "released": true,
    "changes": [
      {
        "type": 0,
        "description": "New Login Page"
      },
      {
        "type": 1,
        "description": "Toolbar in Checkout"
      },
      {
        "type": 2,
        "description": "Old theme will be removed"
      },
      {
        "type": 3,
        "description": "Tutorial page is removed"
      },
      {
        "type": 4,
        "description": "Crash in Payment"
      },
      {
        "type": 5,
        "description": "HTTPS only requests"
      }
    ]
  }
]
```

```java
val filepath = "sample.json"

NoticeBoard(this).pin {
    source(Json(filepath))
}
```

#### Xml

Store releases by creating a xml file to the `/assets` folder.

Here is an example of XML file
```xml
<?xml version="1.0" encoding="UTF-8" ?>
<releases>
    <release>
        <date>30 Sep 2019</date>
        <version>1.0.0</version>
        <released>true</released>
        <change>
            <description>New Login Page</description>
            <type>0</type>
        </change>
        <change>
            <description>Toolbar in Checkout</description>
            <type>1</type>
        </change>
        <change>
            <description>Old theme will be removed</description>
            <type>2</type>
        </change>
        <change>
            <description>Tutorial page is removed</description>
            <type>3</type>
        </change>
        <change>
            <description>Crash in Payment</description>
            <type>4</type>
        </change>
        <change>
            <description>HTTPS only requests</description>
            <type>5</type>
        </change>
    </release>
</releases>

```

```java
val filepath = "sample.xml"

NoticeBoard(this).pin {
    source(Xml(filepath))
}
```

Upcoming
-------
1. Add `Known Issues` section support
2. Add a custom change types
3. Add `MarkdownDataSource` support
4. Add remote data support
5. Add a GOTO button
6. New Date formats

Contribution
-------
If you've found an error in the library or sample, please file an issue.

Patches are encouraged, and may be submitted by forking this project and submitting a pull request.

If you contributed to `noticeboard` but your name is not in the list, please feel free to add yourself to it!

- [Furkan Akdemir](https://github.com/furkanakdemir) - Maintainer
- [Nuh Koca](https://github.com/nuhkoca) - Collaborator, CI Improvements

License
-------

    Copyright 2019 Furkan Akdemir

    Licensed 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.

repository: ladroshan/noticeboard

repo_name: ladroshan/noticeboard


text:
---
# Feel free to add content and custom Front Matter to this file.
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults

permalink: /changelog/
layout: home
title: IBM TRIRIGA Assistant - Changelog
description: New and exciting changes for IBM TRIRIGA Assistant can be found here. Follow our changelog for exciting version update info.

sidebar:
  nav: "docs"
---

## Version 1.0.4

In this update we explore the possibilities of analytics with IBM TRIRIGA
Assistant. With Version 1.0.4 we are introducing a new dashboard for TRIRIGA
Administrators to help understand how the Assistant is being consumed by end users.

This new reporting dashboard helps visualize usage statistics like daily concurrent users, or satisfaction scores over the course of a month. We hope to expand this to even more exciting metrics in updates to come.

### Examples

Monthly View:
![alt]({{ site.url }}{{ site.baseurl }}/assets/post-images/2020-06-16/reports-1.png)

Daily View:
![alt]({{ site.url }}{{ site.baseurl }}/assets/post-images/2020-06-16/reports-2.png)

extension: markdown


text:
+++
title = "azure_data_lake_storage_gen2_filesystems Resource"
platform = "azure"
draft = false
gh_repo = "inspec-azure"

[menu.inspec]
title = "azure_data_lake_storage_gen2_filesystems"
identifier = "inspec/resources/azure/azure_data_lake_storage_gen2_filesystems Resource"
parent = "inspec/resources/azure"
+++

Use the `azure_data_lake_storage_gen2_filesystems` InSpec audit resource to test the properties related to all Azure Data Lake Storage Gen2 Filesystems within a project.

## Azure REST API Version, Endpoint, and HTTP Client Parameters

{{% inspec_azure_common_parameters %}}

## Installation

{{% inspec_azure_install %}}

## Syntax

An `azure_data_lake_storage_gen2_filesystems` resource block returns all Azure Data Lake Storage Gen2 filesystems within a project.

```ruby
describe azure_data_lake_storage_gen2_filesystems(account_name: 'ACCOUNT_NAME') do
  #...
end
```

## Parameters

`account_name` _(required)_

: The Azure Storage account name.

`dns_suffix` _(optional)_

: The DNS suffix for the Azure Data Lake Storage endpoint.

## Properties

`names`
: Unique names for all Azure Storage Account Filesystems.

: **Field**: `name`

`lastModifieds`
: Last modified timestamps of Azure Storage Account Filesystem.

: **Field**: `lastModified`

`eTags`
: A list of eTags for all the Azure Storage Account Filesystems.

: **Field**: `eTag`

`DefaultEncryptionScopes`
: A list of all Encryption scopes of the ADLS Filesystems.

: **Field**: `DefaultEncryptionScope`

`DenyEncryptionScopeOverrides`
: A list of all Deny Encryption Scope Overrides.

: **Field**: `DenyEncryptionScopeOverrides`

{{% inspec_filter_table %}}
Also, refer to [Azure documentation](https://docs.microsoft.com/en-us/rest/api/storageservices/datalakestoragegen2/filesystem/list) for other properties available.

## Examples

### Loop through Data Lake Storage Gen2 Filesystems by their names and verify that each exists

```ruby
azure_data_lake_storage_gen2_filesystems(account_name: 'ACCOUNT_NAME').names.each do |name|
  describe azure_data_lake_storage_gen2_filesystem(account_name: 'ACCOUNT_NAME', name: name) do
    it { should exist }
  end
end
```

### Test To ensure Data Lake Storage Gen2 Filesystems With ‘$account-encryption-key’ encryption scope

```ruby
describe azure_data_lake_storage_gen2_filesystems(account_name: 'ACCOUNT_NAME').where(DefaultEncryptionScope: '$account-encryption-key') do
  it { should exist }
end
```

## Matchers

{{% inspec_matchers_link %}}

### exists

```ruby
# Should not exist if no Data Lake Storage Gen2 filesystems are present in the project and the resource group.

describe azure_data_lake_storage_gen2_filesystems(account_name: 'ACCOUNT_NAME') do
  it { should_not exist }
end
```

### not_exists

```ruby
# Should exist if the filter returns at least one Data Lake Storage Gen2 filesystem in the project and the resource group.

describe azure_data_lake_storage_gen2_filesystems(account_name: 'ACCOUNT_NAME') do
  it { should exist }
end
```

## Azure Permissions

{{% azure_permissions_service_principal role="contributor" %}}

repository: inspec/inspec-azure

gha_license_id: NOASSERTION

repo_name: inspec/inspec-azure


text:
`Rx.DOM.ajax(url | settings)`
[Ⓢ](https://github.com/Reactive-Extensions/RxJS-DOM/blob/master/src/ajax.js "View in source")

Creates a hot observable for an Ajax request with either a settings object with url, headers, etc or a string for a URL.

#### Arguments
- `url` *(String)*: A string of the URL to make the Ajax call.
- `settings` *(Object)*: An object with the following properties

    - `url` *(String)*: URL of the request
      - `method` *(String)*: Method of the request, such as GET, POST, PUT, PATCH, DELETE
      - `async` *(Boolean)*: Whether the request is async
      - `headers` *(Object)*: Optional headers

#### Returns
*(Observable)*: An observable sequence containing the `XMLHttpRequest`.

#### Example

The following example uses a simple URL to retrieve a list of products.
```js
Rx.DOM.Request.ajax('/products')
  .subscribe(
    function (xhr) {

      var products = JSON.parse(xhr.responseText);

      products.forEach(function (product) {
        console.log(product);
      });
    },
    function (error) {
      // Log the error
    }
  );
```

### Location

File:
- [`/src/ajax.js`](https://github.com/Reactive-Extensions/RxJS-DOM/blob/master/src/ajax.js)

Dist:
- [`rx.dom.js`](https://github.com/Reactive-Extensions/RxJS-DOM/blob/master/dist/rx.dom.js) | - [`rx.dom.compat.js`](https://github.com/Reactive-Extensions/RxJS-DOM/blob/master/dist/rx.dom.compat.js)

Prerequisites:
- If using `rx.js`
  - [`rx.js`](https://github.com/Reactive-Extensions/RxJS/blob/master/dist/rx.js) | [`rx.compat.js`](https://github.com/Reactive-Extensions/RxJS/blob/master/dist/rx.compat.js)
  - [`rx.binding.js`](https://github.com/Reactive-Extensions/RxJS/blob/master/dist/rx.binding.js)
- [`rx.lite.js`](https://github.com/Reactive-Extensions/RxJS/blob/master/rx.lite.js) | [`rx.lite.compat.js`](https://github.com/Reactive-Extensions/RxJS/blob/master/rx.lite.compat.js)

NPM Packages:
- [`rx-dom`](https://preview.npmjs.com/package/rx-dom)

NuGet Packages:
- [`RxJS-Bridges-HTML`](http://www.nuget.org/packages/RxJS-Bridges-HTML/)

Unit Tests:
- [`/tests/tests.ajax.js](https://github.com/Reactive-Extensions/RxJS-DOM/blob/master/tests/tests.ajax.js)


text:
# Scenarios {#concept_28403_zh .concept}

Alibaba Cloud Anti-DDoS Basic applies to Internet DDoS attack protection.

Scope: Free DDoS attack protection for ECS, SLB, EIP, NAT and WAF services on Alibaba Cloud.

Limit: Scenarios that require no more than 5 GB DDoS attack protection.

repository: juicechu/ddosbasic

path: /intl.en-US/Anti-DDoS Basic Service/Product Introduction/Scenarios.md

repo_name: juicechu/ddosbasic


text:
# Task Explorer Panel

This VS Code extension provides panel for tasks exploring including their browsing, creation, editing and execution.

## Description

The tasks panel presents the tree of tasks, grouped by intents.
Supported intents are:

- Build
- Deploy
- Miscellenous

### Features

- User can create a new task using `Create` button of the panel.
- Context menu on the tree enables to edit and remove tasks.
- `Run` button on the task's item run's the task.

## Limitations

The tasks panel is hidden if no extension exposes task provider contributing to the Task Explorer.

### Support

You can open [issues](https://github.com/SAP/task-explorer/issues) on GitHub.

### Contributing

See [CONTRIBUTING.md](./CONTRIBUTING.md).

repository: task-explorer-bot/task-explorer

repo_name: task-explorer-bot/task-explorer


text:
# Uberproto

Uberproto is a simple base object that adds some sugar to ECMAScript 5 style object inheritance
in JavaScript.

Here is what it can do in a nutshell:

- Easily extend objects
- Initialization methods
- Super methods
- Mixins
- Method proxies

With a small footprint (about 1Kb minified) and an easy to handle API of just
four methods it also doesn't add a lot of baggage to your JavaScript application.

## Usage

UberProto can be used as a [CommonJS AMD](https://github.com/amdjs/amdjs-api/wiki/AMD) module
(e.g. with [RequireJS](http://requirejs.org/)), [NodeJS](http://nodejs.org) or directly
in the browser. If no module loader is available, the global variable _Proto_
will be defined after you include the script. In the browser you have two options:
The default build that includes EcmaScript 5 shims or, if you only support modern browsers or
provide the shims already, without.

### Using AMD (e.g. RequireJS)

Make sure proto.js is in the right folder and then just define a module like this:

```javascript
define(['proto'], function(Proto) {
	// Source goes here
});
```

### In the browser

[Download proto.min.js](https://raw.github.com/daffl/uberproto/master/dist/proto.min.js) or
the EcmaScript 5 version [proto.es5.min.js](https://raw.github.com/daffl/uberproto/master/dist/proto.es5.min.js).
You can also `bower install uberproto` if you are using [Bower](http://twitter.github.com/bower/)
as your package manager. Then simply include the file as a script:

```html
<script type="text/javascript" src="proto.min.js"></script>
```

Now *Proto* is available as a global vairable.

### With NodeJS

After installing the package using NPM

> npm install uberproto

just require it like any other module:

```javascript
var Proto = require('uberproto');
```

## Creating objects

### Extend

You can extend any UberProto object by using *extend* to create a new object that inherits from the current one.
Internally [Object.create](https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Object/create) is
being used (the library provides a polyfill for browsers that don't support Object.create)
and the prototype is set to the object that you are extending.
If defined, the *init* method will be used as the constructor.
That way you can define a simple Person object (which will be reused throughout the next paragraphs):

```javascript
var Person = Proto.extend({
	init : function(name) {
		this.name = name;
	},

	fullName : function() {
		return this.name;
	}
});
```

You can also define a plain object and pass it to UberProto object methods:

```javascript
var PersonObject = {
	init : function(name) {
		this.name = name;
	},

	fullName : function() {
		return this.name;
	}
};
```

Play around with the examples in [this JSFiddle](http://jsfiddle.net/Daff/2GB8n/1/).

### Initialize

You can create a new instance by calling *create*. This will create a new object and call the *init* method,
if defined:

```javascript
var dave = Person.create('Dave');
console.log(dave.name); // -> 'Dave'
console.log(dave.fullName()); // -> 'Dave'
```

If you are using *init* already for something else you can also set the *__init* property to the method name
of your intialization method:

```javascript
var MyPerson = Proto.extend({
	__init : 'construct',

	construct : function(name) {
		this.name = name;
	}
});
```

For calling the constructor on a plain object, call *create* on an UberProto object:

```javascript
var john = Proto.create.call(PersonObject, 'John');
console.log(john.fullName()); // -> 'John'
```

Overwriting *create* is great if you want to customize the way new objects are being
instantiated.

### Super methods

In each method `this._super` refers to the method being overwritten, if there is one.
For our Person object, for example, it would be a lot better if it also had a last name:

```javascript
var BetterPerson = Person.extend({
	init : function(name, lastname) {
		// If you want to pass all original arguments to the
		// _super method just use apply:
		// this._super.apply(this, arguments);
		this._super(name);
		this.lastname = lastname;
	},

	fullName : function() {
		return this._super() + ' ' + this.lastname;
	}
});

var dave = BetterPerson.create('Dave', 'Doe');
console.log(dave.name); // -> 'Dave'
console.log(dave.lastname); // -> 'Doe'
console.log(dave.fullName()); // -> 'Dave Doe'
```

You can also extend a plain object if you don't want to inherit from an UberProto object:

```javascript
var BetterPersonObject = Proto.extend({
	init : function(name, lastname) {
		this._super(name);
		this.lastname = lastname;
	},

	fullName : function() {
		return this._super() + ' ' + this.lastname;
	}
}, PersonObject); // Pass the plain object as the second parameter
```

### Mixins

Mixins add functionality to an existing object. Mixins can also access their super methods using `this._super`.
This will either refer the overwritten method on the object itself or the one on the prototype:

```javascript
Person.mixin({
	init : function()
	{
		this._super.apply(this, arguments);
		this.can_sing = true;
	},

	sing : function()
	{
		return 'Laaaa';
	}
});

var dude = Person.create('Dude');
console.log(dude.sing()); // -> 'Laaaa'
console.log(dude.can_sing); // -> true
```

Actual instances can be mixed in just the same:

```javascript
var operaSinger = Person.create('Pavarotti');
operaSinger.mixin({
	sing : function()
	{
		return this._super() + ' Laalaaa!';
	}
});

console.log(operaSinger.sing()); // -> 'Laaaa Laalaaa!'
```

And you can also mix into plain objects e.g. overwriting the constructor of PersonObject:

```javascript
Proto.mixin({
	fullName : function() {
		return 'My name is: ' + this._super();
	}
}, PersonObject);

// Create a plain object without calling the constructor
var instance = Object.create(PersonObject);
instance.name = 'Dude';
console.log(instance.fullName()); // 'My name is: Dude'
```

### Method proxy

You can create proxy callbacks, that make sure that _this_ will always
point to the right object:

```javascript
var callback = operaSinger.proxy('fullName');
console.log(callback()); // -> 'Pavarotti'
```

And you can partially apply function arguments:

```javascript
operaSinger.mixin({
	sing : function(text)
	{
		return this._super() + ' ' + text;
	}
});

var singHello = operaSinger.proxy('sing', 'Helloooooo!');

singHello() // Laaaa Laalaaa! Helloooooo!
```

`proxy` only works on objects extended from UberProto.

## Changelog

__1.1.1__

* Updating component and bower ([#6](https://github.com/daffl/uberproto/pull/6))
* Only wrap functions that are actually calling ._super ([#7](https://github.com/daffl/uberproto/pull/7))
* Improved build and tests

__1.1.0__

* Extract ES5 shims (build shim-less version)
* Use Function.bind for proxy
* Switched test suite to [Mocha](http://visionmedia.github.com/mocha/)
* [GruntJS](http://gruntjs.com/) build
* [Bower](http://twitter.github.com/bower/) component: `bower install uberproto`

__1.0.3__

* Added `Object.getPrototypeOf` shim
* Updated documentation
* Added Travis CI

__1.0.2__

* Added `__init` property to allow constructor functions to be named other than *init*. Fixes issue [#1](https://github.com/daffl/uberproto/pull/1)

__1.0.1__

* API now usable with plain objects like `Proto.mixin({}, PlainObject)`

__1.0.0__

* Initial stable release

## License

Copyright (C) 2013 David Luecke<EMAIL_ADDRESS>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

[![Build Status](https://secure.travis-ci.org/daffl/uberproto.png)](http://travis-ci.org/daffl/uberproto)

repository: sarojrout/ReactJS-Gulp-Express

repo_name: sarojrout/ReactJS-Gulp-Express


text:
## CoCaIn BPG: Fast Inertial Algorithm for Non-convex Optimization

## [Convex-Concave Backtracking for Inertial Bregman Proximal Gradient Algorithms in Non-Convex Optimization](https://arxiv.org/abs/1904.03537)
by Mahesh Chandra Mukkamala, Peter Ochs, Thomas Pock and Shoham Sabach.

### Code theme: CoCaIn BPG escapes Spurious Stationary Points

The goal is to minimize the following non-convex objective  (as in Page 18)

![function](function.png)

The objective function visualizations are given below (as in Page 19).
![contour_surface](contour_surface.png)

###
### Dependencies
- numpy, matplotlib

If you have installed above mentioned packages you can skip this step. Otherwise run  (maybe in a virtual environment):

    pip install -r requirements.txt

## Reproduce results

To generate results

    chmod +x generate_results.sh
    ./generate_results.sh

Then to create the plots

    python contour_plot.py

Now you can check **figures** folder for various figures.

## Results

![results](results.png)

## Citation

    @techreport{MOPS19,
    title        = {Convex-Concave Backtracking for Inertial Bregman Proximal Gradient Algorithms in Non-Convex Optimization},
    author       = {M.C. Mukkamala and P. Ochs and T. Pock and S. Sabach},
    year         = {2019},
    journal      = {ArXiv e-prints, arXiv:1904.03537},
    }

## [Related work: CoCaIn BPG for Matrix Factorization](https://github.com/mmahesh/cocain-bpg-matrix-factorization)

## Contact
Mahesh Chandra Mukkamala<EMAIL_ADDRESS>
## References

M. C. Mukkamala, P. Ochs, T. Pock, and S. Sabach: Convex-Concave Backtracking for Inertial Bregman Proximal Gradient Algorithms in Non-Convex Optimization. ArXiv e-prints, arXiv:1904.03537, 2019.

## License

[Check here.](LICENSE)


text:
# Parcel

#### Epicodus exercise to return volume and cost of parcel given the dimensions, 04/24/17

#### By Mohamed Warsame and Marko Ludlow

## Description

Program will return the cost of delivery of parcel with certain volume and weight.

## Specifications

| Behavior | Input | Output |
|----------|-------|--------|
| Program takes input of dimensions and returns volume| 5, 5, 5 | 125 |

## Setup/Installation Requirements

* Clone the parcel folder
* Open the index.erb file and enter the lengths for the three sides

## Known Bugs

No bugs

## Support and contact details

Please feel free to contact us at github profile directly.

## Technologies Used

Ruby

### License

MIT

Copyright (c) 2017 **Mohamed Warsame, Marko Ludlow**

repository: Ludlowm/parcel

repo_name: Ludlowm/parcel


text:
<!--
SPDX-License-Identifier: Apache-2.0
Copyright 2022 Open Networking Foundation
-->
# Developer guide

## Testing local Go dependencies

The `upf-epc` repository relies on some external Go dependencies, which are not mature yet (e.g. pfcpsim or p4runtime-go-client).
It's often needed to extend those dependencies first, before adding a new feature to the PFCP Agent. However, when using Go modules and Dockerized environment,
it's hard to test WIP changes to local dependencies. Therefore, this repository come up with a way to use Go vendoring, instead of Go modules, for development purposes.

To use a local Go dependency add the `replace` directive to `go.mod`. An example:

```
replace github.com/antoninbas/p4runtime-go-client v0.0.0-20211006214122-ea704d54a7d3 => ../p4runtime-go-client
```

Then, to build the Docker image using the local dependency:

```
DOCKER_BUILD_ARGS="--build-arg GOFLAGS=-mod=vendor" make docker-build
```

To run E2E integration tests with the local dependency:

```
DOCKER_BUILD_ARGS="--build-arg GOFLAGS=-mod=vendor" make test-up4-integration
```


text:
---
name: Publish a Release
about: Instructions and checklist for creating a release.
title: 'Release X.Y.Z-rc.N'
labels: kind/release
assignees: ''
---

# Open Match Release Process

Follow these instructions to create an Open Match release. The output of the
release process is new images and new configuration.

## Getting setup

**NOTE: The instructions below are NOT strictly copy-pastable and assume 0.5**
**release. Please update the version number for your commands.**

The Git flow for pushing a new release is similar to the development process
but there are some small differences.

### 1. Clone Repository

```shell
# Clone your fork of the Open Match repository.
git clone git@github.com:afeddersen/open-match.git
# Change directory to the git repository.
cd open-match
# Add a remote, you'll be pushing to this.
git remote add upstream https://github.com/googleforgames/open-match.git
```

### 2. Release Branch

If you're creating the first release of the version, that would be `0.5.0-rc.1`
then you'll need to create the release branch.

```shell
# Create a local release branch.
git checkout -b release-0.5 upstream/master
# Push the branch upstream.
git push upstream release-0.5
```

otherwise there should already be a `release-0.5` branch so run,

```shell
# Checkout the release branch.
git checkout -b release-0.5 upstream/release-0.5
```

**NOTE: The branch name must be in the format, `release-X.Y` otherwise**
**some artifacts will not be pushed.**

## Releases & Versions

Open Match uses Semantic Versioning 2.0.0. If you're not familiar please
see the documentation - [https://semver.org/](https://semver.org/).

Full Release / Stable Release:

* The final software product. Stable, reliable, etc...
* Example: 1.0.0, 1.1.0

Release Candidate (RC):

* A release candidate (RC) is a version with the potential to be the final
  product but it hasn't validated by automated and/or manual tests.
* Example: 1.0.0-rc.1

Hot Fixes:

* Code developed to correct a major software bug or fault
  that's been discovered after the full release.
* Example: 1.0.1

Preview:

* Rare, a one off release cut from the master branch to provide early access
  to APIs or some other major change.
* **NOTE: There's no branch for this release.**
* Example: 0.5-preview.1

**NOTE: Semantic versioning is enforced by `go mod`. A non-compliant version**
**tag will cause `go get` to break for users.**

# Detailed Instructions

## Find and replace

Below this point you will see {version} used as a placeholder for future
releases. Find {version} and replace with the current release (e.g. 0.5.0)

## Create a release branch in the upstream open-match repository

**Note: This step is performed by the person who starts the release.  It is
only required once.**

- [ ] Create the branch in the **upstream** repository. It should be named
  release-X.Y. Example: release-0.5. At this point there's effectively a code
  freeze for this version and all work on master will be included in a future
  version. If you're on the branch that you created in the *getting setup*
  section above you should be able to push upstream.

```shell
git push origin release-0.5
```

- [ ] Announce a PR freeze on release-X.Y branch on [open-match-discuss@](mailing-list-post).
- [ ] Open the [`Makefile`](makefile-version) and change BASE_VERSION entry.
- [ ] Open the [`install/helm/open-match/Chart.yaml`](om-chart-yaml-version) and change the `appVersion` and `version` entries.
- [ ] Open the [`install/helm/open-match/values.yaml`](om-values-yaml-version) and change the `tag` entries.
- [ ] Open the [`cloudbuild.yaml`] and change the `_OM_VERSION` entry.
- [ ] There might be additional references to the old version but be careful not to change it for places that have it for historical purposes.
- [ ] Run `make release`
- [ ] Run `make api/api.md` in open-match repo to update the auto-generated API references in open-match-docs repo.
- [ ] Create a PR with the changes, include the release candidate name, and point it to the release branch.
- [ ] Go to [open-match-build](https://pantheon.corp.google.com/cloud-build/triggers?project=open-match-build) and update all *post submit* triggers' `_GCB_LATEST_VERSION` value to the `X.Y` of the release. This value should only increase as it's used to determine the latest stable version.
- [ ] Merge your changes once the PR is approved.

## Create a release branch in the upstream open-match-docs repository
- [ ] Open [`Makefile`](makefile-version) and change BASE_VERSION entry.
- [ ] Open [`cloudbuild.yaml`] and change the `_OM_VERSION` entry.
- [ ] Open [`site/config.toml`] and change the `release_version` entry.
- [ ] Open [`site/static/swaggerui/config.json`] and change the `api/VERSION/...` entries
- [ ] Create a PR with the changes, include the release candidate name, and point it to the release branch.

## Complete Milestone

**Note: This step is performed by the person who starts the release. It is
only required once.**
- [ ] Create the next [version milestone](https://github.com/googleforgames/open-match/milestones) and use [semantic versioning](https://semver.org/) when naming it to be consistent with the [Go community](https://blog.golang.org/versioning-proposal).
- [ ] Create a *draft* [release](https://github.com/googleforgames/open-match/releases).  Note that github has both "Pre-release" and "draft" as different concepts for a release.  Until the release is finalized, only use "Save draft", and do not use "Publish release".
- [ ] Use the [release template](https://github.com/googleforgames/open-match/blob/master/docs/governance/templates/release.md)
  - [ ] `Tag` = v{version}. Example: v0.5.0. Append -rc.# for release candidates. Example: v0.5.0-rc.1.
  - [ ] `Target` = release-X.Y. Example: release-0.5.
  - [ ] `Release Title` = `Tag`
  - [ ] `Write` section will contain the contents from the [release template](https://github.com/googleforgames/open-match/blob/master/docs/governance/templates/release.md).
- [ ] Add the milestone to all PRs and issues that were merged since the last milestone. Look at the [releases page](https://github.com/googleforgames/open-match/releases) and look for the "X commits to master since this release" for the diff.
- [ ] Review all [milestone-less closed issues](https://github.com/googleforgames/open-match/issues?q=is%3Aissue+is%3Aclosed+no%3Amilestone) and assign the appropriate milestone.
- [ ] Review all [issues in milestone](https://github.com/googleforgames/open-match/milestones) for proper [labels](https://github.com/googleforgames/open-match/labels) (ex: area/build).
- [ ] Review all [milestone-less closed PRs](https://github.com/googleforgames/open-match/pulls?q=is%3Apr+is%3Aclosed+no%3Amilestone) and assign the appropriate milestone.
- [ ] Review all [PRs in milestone](https://github.com/googleforgames/open-match/milestones) for proper [labels](https://github.com/googleforgames/open-match/labels) (ex: area/build).
- [ ] View all open entries in milestone and move them to a future milestone if they aren't getting closed in time. https://github.com/googleforgames/open-match/milestones/v{version}
- [ ] Review all closed PRs against the milestone. Put the user visible changes into the release notes using the suggested format. https://github.com/googleforgames/open-match/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+is%3Amerged+milestone%3Av{version}
- [ ] Review all closed issues against the milestone. Put the user visible changes into the release notes using the suggested format. https://github.com/googleforgames/open-match/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+milestone%3Av{version}
- [ ] Verify the [milestone](https://github.com/googleforgames/open-match/milestones) is effectively 100% at this point with the exception of the release issue itself.

## Build Artifacts

- [ ] Go to the History section and find the "Post Submit" build of the merged commit that's running. Wait for it to go Green. If it's red, fix error repeat this section. Take note of the docker image version tag for next step. Example: 0.5.0-a4706cb.
- [ ] Run `./docs/governance/templates/release.sh {source version tag} {version}` to copy the images to open-match-public-images.
- [ ] If this is a new minor version in the newest major version then run `./docs/governance/templates/release.sh {source version tag} latest`.
- [ ] Once the images have successfully been pushed to the registry, modify the line `open-match.dev/open-match v0.0.0-dev` in all `go.mod` files in the [Tutorials] (https://github.com/googleforgames/open-match/tree/main/tutorials) directory to use the current release version. This includes all solution subdirectories as well
- [ ] Use the files under the `build/release/` directory for the Open Match installation guide. Make sure the artifacts work as expected - these are the artifacts that will be published to the GCS bucket and used in our release assets.
- [ ] Copy the files from `build/release/` generated from `make release` to the release draft you created.  You can drag and drop the files using the Github UI.
- [ ] Update [Slack invitation link](https://slack.com/help/articles/201330256-invite-new-members-to-your-workspace#share-an-invite-link) in [open-match.dev](https://open-match.dev/site/docs/contribute/#get-involved).
- [ ] Test Open Match installation under GKE and Minikube enviroment using YAML files and Helm. Follow the [First Match](https://development.open-match.dev/site/docs/getting-started/first_match/) guide, run `make proxy-demo`, and open `localhost:51507` to make sure everything works.
  - [ ] Minikube: Run `make create-mini-cluster` to create a local cluster with latest Kubernetes API version.
  - [ ] GKE: Run `make create-gke-cluster` to create a GKE cluster.
  - [ ] Helm: Run `helm install open-match -n open-match open-match/open-match`
- [ ] Update usage requirements in the Installation doc - e.g. supported minikube version, kubectl version, golang version, etc.

## Finalize

- [ ] Save the release as a draft.
- [ ] Circulate the draft release to active contributors.  Where reasonable, get everyone's ok on the release notes before continuing.
- [ ] Publish the [Release](om-release) in Github.  This will notify repository watchers.
- [ ] Publish the [Release](om-release) on Open Match [Blog](https://open-match.dev/site/blog/).

## Announce

- [ ] Send an email to the [mailing list](mailing-list-post) with the release details (copy-paste the release blog post)
- [ ] Send a chat on the [Slack channel](om-slack). "Open Match {version} has been released! Check it out at {release url}."

[om-slack]: https://open-match.slack.com/
[mailing-list-post]: https://groups.google.com/forum/#!newtopic/open-match-discuss
[release-template]: https://github.com/googleforgames/open-match/blob/master/docs/governance/templates/release.md
[makefile-version]: https://github.com/googleforgames/open-match/blob/master/Makefile#L53
[om-chart-yaml-version]: https://github.com/googleforgames/open-match/blob/master/install/helm/open-match/Chart.yaml#L16
[om-values-yaml-version]: https://github.com/googleforgames/open-match/blob/master/install/helm/open-match/values.yaml#L16
[om-release]: https://github.com/googleforgames/open-match/releases/new
[readme-deploy]: https://github.com/googleforgames/open-match/blob/master/README.md#deploy-to-kubernetes

repository: googleforgames/open-match

repo_name: googleforgames/open-match