text:
A quick way to get a Laravel app spun up in a docker stack.

1. Remove the README from the ./src directory.
2. Install your Laravel app into the ./src directory.
3. In the Laravel .env file update mysql variables to match the docker-compose.yml mysql variables.
4. In your terminal run, "docker-compose build"
5. After the build completes run, "docker-compose up -d"
6. Once the stack is up run, "docker-compose exec php composer install"
7. If you need to install NPM packages you can run, "docker-compose exec php npm install"
8. Migrate with, "docker-compose exec php php artisan migrate"

repository: TheBanditDave/laravel-docker-dev-stack

repo_name: TheBanditDave/laravel-docker-dev-stack


text:
# may_http

[![Travis Build Status](https://travis-ci.org/rust-may/may_http.svg?branch=master)](https://travis-ci.org/rust-may/may_http)
<!-- refs
[![crates.io](http://meritbadge.herokuapp.com/may_http)](https://crates.io/crates/may_http)
-->

Coroutine based HTTP library for Rust.

<!-- refs

### Documentation

- [Docs](http://rust-may.github.io/may_http)
-->

## Overview

may_http is a fast, coroutine based HTTP implementation that can be used as lower level layer for http servers and clients.

Some of the implementation logic comes from [hyper](https://github.com/hyperium/hyper) 0.10.x branch

But most of the logic are re-written for ergonomical usage and performance consideration.

Thanks to the [httparse](https://github.com/seanmonstar/httparse) and [http](https://github.com/hyperium/http) crates, they make may_http only focus on the transportation logic.

## Example

### Hello World Server:

```rust
use http::header::*;
use may_http::server::*;

fn hello(_req: Request, rsp: &mut Response) {
    rsp.headers_mut()
        .append(CONTENT_TYPE, "text/plain; charset=utf-8".parse().unwrap());
    rsp.send(b"Hello World!").unwrap();
}

fn main() {
    let server = HttpServer::new(hello).start("<IP_ADDRESS>:8080").unwrap();
    server.wait();
}
```

### Simple Client
for a more complicated client example, you can ref [wrk-rs](https://github.com/Xudong-Huang/wrk-rs)
```rust
use http::Uri;
use std::io::{self, Read};
use may_http::client::*;

fn client_get(uri: Uri) -> io::Result<()> {
    let mut client = {
        let host = uri.host().unwrap_or("<IP_ADDRESS>");
        let port = uri.port().unwrap_or(80);
        HttpClient::connect((host, port))?
    };

    let mut s = String::new();
    for _ in 0..100 {
        let uri = uri.clone();
        let mut rsp = client.get(uri)?;
        rsp.read_to_string(&mut s)?;
        println!("get rsp={}", s);
        s.clear();
    }
    Ok(())
}

fn main() {
    let uri: Uri = "http://<IP_ADDRESS>:8080/".parse().unwrap();
    client_get(uri).unwrap();
}
```

## Performance

The data only benched on one thread hello server, compared with hyper master branch which is power by tokio and future.
### hyper
```sh
$ wrk http://<IP_ADDRESS>:3000 -d 10 -t 1 -c 200
Running 10s test @ http://<IP_ADDRESS>:3000
  1 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.95ms  272.35us   8.49ms   94.67%
    Req/Sec    68.13k     1.99k   70.36k    87.00%
  677836 requests in 10.05s, 83.39MB read
Requests/sec:  67466.95
Transfer/sec:      8.30MB
wrk http://<IP_ADDRESS>:3000 -d 10 -t 1 -c 200  2.79s user 5.97s system 87% cpu 10.051 total
```

### may_http
```sh
$ wrk http://<IP_ADDRESS>:8080 -d 10 -t 1 -c 200
Running 10s test @ http://<IP_ADDRESS>:8080
  1 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.45ms  330.62us  10.91ms   96.82%
    Req/Sec    81.79k     2.83k   84.95k    81.00%
  814731 requests in 10.03s, 111.11MB read
Requests/sec:  81253.47
Transfer/sec:     11.08MB
wrk http://<IP_ADDRESS>:8080 -d 10 -t 1 -c 200  2.75s user 6.89s system 96% cpu 10.030 total
```

# License

This project is licensed under either of

 * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or
   http://www.apache.org/licenses/LICENSE-2.0)
 * MIT license ([LICENSE-MIT](LICENSE-MIT) or
   http://opensource.org/licenses/MIT)

at your option.

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
# NSWG
Navigable Small World Graphs For Approximate Nearest Neighbors In Rust.

Implements k-nearest neighbor search on navigable small graphs.
Provides a reader for the [UCR time series collection](https://www.cs.ucr.edu/~eamonn/time_series_data_2018/).
Supports querys with euclidean distance and dtw distance.

license: MIT

repository: dkohlsdorf/NSWG

repo_name: dkohlsdorf/NSWG


text:
# BrewMap
BreweryDB and Google Maps mashup

http://www.brewerydb.com/developers/docs

https://developers.google.com/maps/documentation/javascript/

Author: Greg Wajda

Displays an interactive map using the Google Maps API. Using the BreweryDB API, I have marked the locations of the breweries in Illinois. When you click on the map marker, a display will pop up giving you the info on that specific brewery. The idea is to have a visual display where people can look at nearby breweries and check information such as ratings, beer they serve, time they are open, etc. It is meant to make the search easier and less of a hassle for the user.

Have only tested on Chrome. Needs "Allow-Control-Allow-Origin" extension enabled to work.

repository: gjwajda/BrewMap

repo_name: gjwajda/BrewMap


text:
## A package will help you to split your data frame into training, validation and testing subsets

## Working:
Splits arrays or matrices into random train, validation and test subsets
"train_val_test_split" function accepts independent features(X), dependent
feature (y), validation size (default size = 0.15),test size (default size = 0.15) and shuffle (default = True) as input parameters and returns X_train,X_val,X_test,y_train,y_val,y_test

Note: If shuffle parameter is True, after shuffling index of all records will be reset in ascending order

## How to use it:

from vinzy_splitter import train_val_test_split

X_train,X_val,X_test,y_train,y_val,y_test = train_val_test_split(X,y,val_size=0.15,test_size=0.15,shuffle=True)

after executing the function your data frame will be splitted into training,validation and testting subsets based on validation and testing size you have provided, deafult value will be 15% for both and suffling will be True.

branch_name: refs/heads/main


text:
# Contacts List

Contacts List displays a number contacts, including their name, email, age, and profile image.
The [Random User Generator](https://randomuser.me/) API is used for generating random user data.

## Table of Contents

- [Screenshots](https://github.com/jasonranney/contacts-list#screenshots)
- [Technologies](https://github.com/jasonranney/contacts-list#technologies)
- [Installation](https://github.com/jasonranney/contacts-list#installation)
- [Usage](https://github.com/jasonranney/contacts-list#usage)
- [Sources](https://github.com/jasonranney/contacts-list#sources)
- [License](https://github.com/jasonranney/contacts-list#license)

## Screenshots

![Image of Contacts List](https://github.com/jasonranney/contacts-list/blob/master/docs/screenshots/contacts-list.png)

## Technologies

Project is created with:

- react - 16.13.1
- react-dom - 16.13.1
- react-scripts - 3.4.1

## Installation

In the project directory, you can run:

### `npm install`

Installs all dependencies in the local `node_modules` folder.

## Usage

In the project directory, you can run:

#### Development

### `npm start`

Runs the app in the development mode.
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

#### Production

### `npm run build`

Builds the app for production to the `dist` folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

## Sources

This app is inspired by freeCodeCamp guide [How to Get Started with React — A Modern Project-based Guide for Beginners (Including Hooks)](https://www.freecodecamp.org/news/getting-started-with-react-a-modern-project-based-guide-for-beginners-including-hooks-2/) by Chris Blakely.

## License

MIT

repository: jasonranney/contacts-list

repo_name: jasonranney/contacts-list


text:
# pihole-docker

This docker image is based on the official PiHole docker image.  The difference
is that this image starts a second dnsmasq instance and sets pihole's upstream
servers to the second dnsmasq instance.  This allows more fine-grained control
over locally served DNS records.

The original motivation for this image was the need to be able to set a
local-ttl higher than 2 (the PiHole default).  With the configuration in this
image, PiHole maintains its TTL of 2 (for blacklisted records) and forwards all
requests to the upstream dnsmasq server.  That dnsmasq server is configured
however you like.

### Usage

In order to use this image, dnsmasq configs must be provided using a bind mount
to /etc/upstream.d.  Here is an example:

```shell
docker run --rm --volume=$(pwd)/upstream.d:/etc/upstream.d abates314/pihole
```

### Upstream DNS

All of the PiHole docker environment variables are supported.  Do not change the
DNS settings in the PiHole admin console.  This setting is overwritten every time
the docker image boots.  To set upstream DNS servers either use the DNS1 and DNS2
environment variables, or use the PIHOLE_DNS_ environment variable:

```
docker run --rm -e DNS1=<IP_ADDRESS> -e DNS2=<IP_ADDRESS> abates314/pihole
```

or

```
docker run --rm -e "PIHOLE_DNS_=<IP_ADDRESS>;<IP_ADDRESS>" abates314/pihole
```

repository: abates/pihole-docker

repo_name: abates/pihole-docker


text:
# Yutani

[![Gem Version](https://badge.fury.io/rb/yutani.svg)](https://badge.fury.io/rb/yutani)
[![Build Status](https://travis-ci.org/leg100/yutani.svg?branch=master)](https://travis-ci.org/leg100/yutani)

## About

Yutani - A ruby DSL for generating [Terraform](https://github.com/hashicorp/terraform/) configurations:

* Eschews Terraform variables in favour of querying [Hiera](https://github.com/puppetlabs/hiera)
* No Terraform modules; everything is in a single 'root' module
* Generates multiple configurations or 'stacks'
* Generates JSON rather than HCL

## Installation

Ensure you have at least version 2.3.1 of ruby installed.

Install the gem:

```sh
gem install yutani
```

Initialise a directory structure and configuration file with defaults:

```sh
yutani init
```

## Examples

The DSL bears a strong similarity to the Terraform HCL syntax:

```ruby
stack {
	resource(:aws_instance, :nginx) {
		ami           "ami-123123"
		instance_type "t2.micro"
		key_name      "my-ssh-key"
	}
}
```

Yutani integrates with [Hiera](https://github.com/puppetlabs/hiera). Variables can be looked up by key:

```ruby
stack {
	resource(:aws_instance, :nginx) {
		ami           hiera(:ami)
		instance_type "t2.micro"
		key_name      "my-ssh-key"
	}
}
```

You can create multiple stacks, each with a different Hiera scope:

```ruby
%w[dev staging prod].each do |env|
	stack(env: env) {
		resource(:aws_instance, :nginx) {
			ami           hiera(:ami)
			instance_type hiera(:instance_type)
			key_name      "my-ssh-key"
		}
	}
end
```

Depending on your Hiera hierarchy each stack can have different ami and instance_type, optionally falling back on a default.

## Objects

### Stack

A stack object creates a directory containing Terraform configuration. This is the same directory from which you'd run commands like `terraform plan` and `terraform apply`. It takes the following parameters:

* _namespace_ - optional symbols
* _hiera scope_ - a single level hash

For example:

```ruby
stack(:mystack, env: 'dev', region: 'eu-west-1')
```

Has the namespace `:mystack`, and a hiera scope `{env: 'dev', region: 'eu-west-1'}`.

The hiera scope determines which variables are looked up in the Hiera hierarchy.

The namespace is joined together with the hiera scope _values_ to form the resulting stack directory. In this case the directory would be:

```
./terraform/mystack_dev_eu_west_1
```

### Resource

A resource maps to a Terraform resource. It takes the following parameters:

* _resource type_ - mandatory, symbol, i.e. `:aws_instance`
* _resource names_ - mandatory, symbols, i.e. `:app, :frontend`

The _resource names_ are joined together with an underscore to form the resulting Terraform resource name, i.e.:

```ruby
resource(:aws_instance, :app, :backend, :v2)
```

would result in a Terraform resource named `app_backend_v2`.

### References

Use the `ref()` function to make references to other resources and their attributes. It takes the form:

`ref(resource_type, *resource_names, attr)`

Alternatively, you can use the syntax `ref_X()` to refer to a particular attribute, e.g. referencing the `id` attribute of a resource:

`ref_id(resource_type, *resource_names)`

### Includes

You can include DSL code from other files:

```ruby
stack {
	inc { './nginx.rb' }
}
```

## Style

I've opted for using `{}` instead of `do; end` for the blocks in the examples. Either can of course be used, but I wanted to convey the similarity to HCL.

## Notes

* Either blocks and hashes can be used for sub-resources (i.e. `tags` in `aws_instance`, or `listener` in `aws_elb`)
* `{}` and `({})` for property values, represent blocks and hashes respectively
* Makes heavy use of ruby's `method_missing`. Basically, Yutani knows nothing of which providers and resources are possible, it just converts the resource property names to methods, and passes the property values as parameters. While this means Yutani doesn't have to keep track of the continual changes to Terraform's resources, it does make it more brittle than I'd like. For instance, the resource `aws_security_group_rule` has a property called `self`, which is of course also a ruby keyword, and if it is defined in this way it will trigger an error. To get around this, pass a parameter to your resource block like so:

```ruby
resource(:aws_security_group_rule, :bastion) {|r|
    type              "ingress"
    from_port         22
    to_port           22
    protocol          "tcp"
    r.self            true
    security_group_id "sg-123456"
}
```

Not so pretty, but you'll be alright.

## Roadmap

* Rewrite in golang, evaluating the ruby DSL via mruby
* Investiate supporting Ansible, Packer, and any other tools that rely on a serialization format for configuration
* Support for setting remote config via DSL
* Support for files and templates. Consider whether this can be done at evaluation stage and placed inline into generated JSON

## Issues that this will overcome

* Unable to selectively enable SSL on an ELB
* Add more as I think of em!


text:
## Hacktoberfest 2020 and Tekton!

### What's this about?

We'd love to encourage folks to contribute to Tekton - and over at the [Continuous Delivery Foundation](https://cd.foundation/) we've decided something like this could come in handy.

### Guidance for project maintainers

When creating a new issue for Hacktoberfest, please assign it the Hacktoberfest-2020 label and make sure you provide at least:

- A perceived difficulty level
- Awesome contacts/mentors willing to help out
- An idea of what we'd like to achieve
- Any useful pointers for getting started

### Guidance for contributors

The below links all contain the label selector for hacktoberfest-2020 and there you can find all of the issues that the maintainers think would be good ones to get involved in.

We enourage all of the following:
- Sharing ideas and progress
- Mentoring others
- Challenging yourself
- Bringing others in to contribute
- Asking for help and making new contacts

If there's any doubt please don't hesitate to contact the issue creator or the project maintainers - we'd love to help out!

If you start addressing an issue please assign yourself to it by posting the `/assign` message in the issue; this will help maintainers know exactly who is working on it and let others know that the issue has already been picked up by someone.

### Project ideas with Hacktoberfest queries

- [Catalog](https://github.com/tektoncd/catalog/labels/hacktoberfest-2020)
- [Chains](https://github.com/tektoncd/chains/labels/hacktoberfest-2020)
- [CLI](https://github.com/tektoncd/cli/labels/hacktoberfest-2020)
- [Dashboard](https://github.com/tektoncd/dashboard/labels/hacktoberfest-2020)
- Demos! Building and putting cool ideas together
- [Experimental](https://github.com/tektoncd/experimental/labels/hacktoberfest-2020)
- [Pipeline](https://github.com/tektoncd/pipeline/labels/hacktoberfest-2020)
- Testing! Including using Tekton projects on different clouds and Kubernetes platforms
- [Triggers](https://github.com/tektoncd/triggers/labels/hacktoberfest-2020)
- [Website](https://github.com/tektoncd/website/labels/hacktoberfest-2020)

### More information on Hacktoberfest, recognition and our FAQ!

Check out our [CDF Hacktoberfest page!](https://cd.foundation/hacktoberfest/) If anything's unclear please reach out to the CDF on [our CDF Slack](https://cdeliveryfdn.slack.com).

You can also refer to the [official guidelines](https://hacktoberfest.digitalocean.com/hacktoberfest-update) (including the label to use and the topics for each repo we should have).

repository: tektoncd/community

gha_language: Python

repo_name: tektoncd/community


text:
---
order: 100
title: Change Log
type: Other
---

NG-ALAIN strictly follows [Semantic Versioning 2.0.0](http://semver.org/lang/zh-CN/).

#### Release Schedule

* Weekly release: patch version at the end of every week for routine bugfix (anytime for urgent bugfix).
* Monthly release: minor version at the end of every month for new features.
* Major version release is not included in this schedule for breaking change and new features.

---

# [7.5.0](https://github.com/ng-alain/delon/compare/7.4.0...7.5.0) (2019-05-25)

### Scaffold

* refactor `color-less.js` ([#1100](https://github.com/ng-alain/ng-alain/pull/1100))

### Bug Fixes

* **abc:se:** fix losing optional icon ([#577](https://github.com/ng-alain/delon/issues/577)) ([d9033dd](https://github.com/ng-alain/delon/commit/d9033dd))
* **form:** fix ingore trigger `formChange` event when call `refreshSchema` ([#579](https://github.com/ng-alain/delon/issues/579)) ([4f4c4f9](https://github.com/ng-alain/delon/commit/4f4c4f9))
* **form:autocomplete:** fix verify form in typing ([#580](https://github.com/ng-alain/delon/issues/580)) ([3371168](https://github.com/ng-alain/delon/commit/3371168))

### Features

* **abc:st:** add `expandAccordion` property ([#576](https://github.com/ng-alain/delon/issues/576)) ([d3dd0e4](https://github.com/ng-alain/delon/commit/d3dd0e4))
* **abc:sv:** add `optional` `optionalHelp` properittes ([#578](https://github.com/ng-alain/delon/issues/578)) ([8968ae4](https://github.com/ng-alain/delon/commit/8968ae4))
* **form:** add `acl` property ([#574](https://github.com/ng-alain/delon/issues/574)) ([54ddae9](https://github.com/ng-alain/delon/commit/54ddae9))

# [7.4.0](https://github.com/ng-alain/delon/compare/7.3.2...7.4.0) (2019-05-16)

### Bug Fixes

* **abc:sidebar:** fix invalid iconfont icon ([#568](https://github.com/ng-alain/delon/issues/568)) ([9a8ebae](https://github.com/ng-alain/delon/commit/9a8ebae))
* **abc:st:** fix ingore pi event trigger when change size in last page ([#564](https://github.com/ng-alain/delon/issues/564)) ([375d605](https://github.com/ng-alain/delon/commit/375d605))
* **abc:st:** fix responsive styles pollution `nz-table` ([#563](https://github.com/ng-alain/delon/issues/563)) ([4a78ef2](https://github.com/ng-alain/delon/commit/4a78ef2))
* **cli:** fix invalid translate in `ng add` ([#561](https://github.com/ng-alain/delon/issues/561)) ([add2ec0](https://github.com/ng-alain/delon/commit/add2ec0))
* **cli:** fix repeat variable suffix in `ng g ng-alain` ([#560](https://github.com/ng-alain/delon/issues/560)) ([7b8d9eb](https://github.com/ng-alain/delon/commit/7b8d9eb))
* **form:select:** fix invlaid tag count ([#571](https://github.com/ng-alain/delon/issues/571)) ([56abb18](https://github.com/ng-alain/delon/commit/56abb18))

### Features

* **abc:st:** ingore sort procees when `compare` is `null` ([#570](https://github.com/ng-alain/delon/issues/570)) ([0b625b4](https://github.com/ng-alain/delon/commit/0b625b4))
* **acl:** add `except` property in `ACLType` ([#566](https://github.com/ng-alain/delon/issues/566)) ([3787128](https://github.com/ng-alain/delon/commit/3787128))

## [7.3.2](https://github.com/ng-alain/delon/compare/7.3.1...7.3.2) (2019-05-04)

### Scaffold

* style: update html config of prettier ([c0338ef](https://github.com/ng-alain/ng-alain/commit/c0338ef))
* perf: performance demo ([#1062](https://github.com/ng-alain/ng-alain/pull/1062))

### Bug Fixes

* **abc:se:** fix ingore label width when layout is inline ([#553](https://github.com/ng-alain/delon/issues/553)) ([70322fa](https://github.com/ng-alain/delon/commit/70322fa))
* **abc:st:** add `rawData` parameter of `res.process` ([#549](https://github.com/ng-alain/delon/issues/549)) ([102f53f](https://github.com/ng-alain/delon/commit/102f53f))
* **abc:st:** fix auto hide dropdown in buttons ([#556](https://github.com/ng-alain/delon/issues/556)) ([5eb00eb](https://github.com/ng-alain/delon/commit/5eb00eb))
* **theme:http:** fix losing generic in `get` ([#551](https://github.com/ng-alain/delon/issues/551)) ([b2e1482](https://github.com/ng-alain/delon/commit/b2e1482))
* **util:deepMergeKey:** fix override array when  ingoreArray is true ([#555](https://github.com/ng-alain/delon/issues/555)) ([6d4c1cc](https://github.com/ng-alain/delon/commit/6d4c1cc))

### Performance Improvements

* use secondary entry modules in ng-zorro ([#548](https://github.com/ng-alain/delon/issues/548)) ([5d8bac1](https://github.com/ng-alain/delon/commit/5d8bac1))

## [7.3.1](https://github.com/ng-alain/delon/compare/7.3.0...7.3.1) (2019-04-30)

### Scaffold

* style: update stylelint config ([#1054](https://github.com/ng-alain/ng-alain/pull/1054))

### Bug Fixes

* **abc:sv:** fix detail misalignment when content include block ([#545](https://github.com/ng-alain/delon/issues/545)) ([a3191a3](https://github.com/ng-alain/delon/commit/a3191a3))
* **cli:** fix `lint:style` invalid script ([#541](https://github.com/ng-alain/delon/issues/541)) ([1d41e82](https://github.com/ng-alain/delon/commit/1d41e82))
* **form:*:** fix `ViewDestroyedError` error ([#542](https://github.com/ng-alain/delon/issues/542)) ([5d8ffa4](https://github.com/ng-alain/delon/commit/5d8ffa4))
* **theme:http:** fix losing retrun a generic type in `get` ([#546](https://github.com/ng-alain/delon/issues/546)) ([359159c](https://github.com/ng-alain/delon/commit/359159c))

# [7.3.0](https://github.com/ng-alain/delon/compare/7.2.0...7.3.0) (2019-04-26)

### Scaffold

* 401 no need to prompt for request error ([#1023](https://github.com/ng-alain/ng-alain/pull/1023))
* Upgrade `screenfull` to `4.2.0` ([#1031](https://github.com/ng-alain/ng-alain/pull/1031))
* Update `prettier` settings ([#1034](https://github.com/ng-alain/ng-alain/pull/1034))

### Bug Fixes

* **abc:st:** fix ingore load data when page size changed ([#539](https://github.com/ng-alain/delon/issues/539)) ([12ad96f](https://github.com/ng-alain/delon/commit/12ad96f))
* **form:*:** fix can't render when async data ([#525](https://github.com/ng-alain/delon/issues/525)) ([d4d4428](https://github.com/ng-alain/delon/commit/d4d4428))
* **form:date:** fix throw error when not include end property ([#527](https://github.com/ng-alain/delon/issues/527)) ([f06757c](https://github.com/ng-alain/delon/commit/f06757c))
* **form:select:** fix i18n of notFoundContent ([#524](https://github.com/ng-alain/delon/issues/524)) ([1df658c](https://github.com/ng-alain/delon/commit/1df658c))
* **form:upload:** fix clean value when remove file list ([#526](https://github.com/ng-alain/delon/issues/526)) ([0f4e1c5](https://github.com/ng-alain/delon/commit/0f4e1c5))
* **theme:drawer:** fix deep merge object ([#535](https://github.com/ng-alain/delon/issues/535)) ([9c588eb](https://github.com/ng-alain/delon/commit/9c588eb))
* **theme:modal:** fix losing `nzWrapClassName` when has `size` exists ([#537](https://github.com/ng-alain/delon/issues/537)) ([c64834a](https://github.com/ng-alain/delon/commit/c64834a))

### Features

* **abc:st:** add `showExpand` property ([#520](https://github.com/ng-alain/delon/issues/520)) ([d87d56f](https://github.com/ng-alain/delon/commit/d87d56f))
* **abc:st:** add `widthMode` property ([#518](https://github.com/ng-alain/delon/issues/518)) ([715d5de](https://github.com/ng-alain/delon/commit/715d5de))
* **abc:st:** support controlled `loading` property ([#533](https://github.com/ng-alain/delon/issues/533)) ([317b88c](https://github.com/ng-alain/delon/commit/317b88c))
* **acl:** add `*aclIf` structural directive ([#529](https://github.com/ng-alain/delon/issues/529)) ([cf49779](https://github.com/ng-alain/delon/commit/cf49779))
* **form:** add icon in `button` proprety ([#538](https://github.com/ng-alain/delon/issues/538)) ([0ef4281](https://github.com/ng-alain/delon/commit/0ef4281))
* **form:** add `loading` property ([#517](https://github.com/ng-alain/delon/issues/517)) ([1e9df24](https://github.com/ng-alain/delon/commit/1e9df24))
* **theme:yn:** add `mode` property ([#534](https://github.com/ng-alain/delon/issues/534)) ([ebd42be](https://github.com/ng-alain/delon/commit/ebd42be))
* **theme:drawer:** add `exact` property ([#535](https://github.com/ng-alain/delon/issues/535)) ([9c588eb](https://github.com/ng-alain/delon/commit/9c588eb))

### Special Thanks

Amit0043, its404

# [7.2.0](https://github.com/ng-alain/delon/compare/7.1.0...7.2.0) (2019-04-09)

### Bug Fixes

* **abc:_src:** fix invalid `size` property ([#503](https://github.com/ng-alain/delon/issues/503)) ([76fc61b](https://github.com/ng-alain/delon/commit/76fc61b))
* **abc:reuse-tab:** fix actived select tab when close right or other ([#500](https://github.com/ng-alain/delon/issues/500)) ([ed3eef7](https://github.com/ng-alain/delon/commit/ed3eef7))
* **abc:st:** fix missing trigger `expand` event when click expand icon ([#501](https://github.com/ng-alain/delon/issues/501)) ([a0a9c53](https://github.com/ng-alain/delon/commit/a0a9c53))
* **cli:** fix removed `header-i18n` when no-include i18n ([#505](https://github.com/ng-alain/delon/issues/505)) ([9839f69](https://github.com/ng-alain/delon/commit/9839f69))
* **sf:** fix layout misplacement in inline mode ([#514](https://github.com/ng-alain/delon/issues/514)) ([9a7901a](https://github.com/ng-alain/delon/commit/9a7901a))
* **sf:radio:** fix async data invlid render ([#504](https://github.com/ng-alain/delon/issues/504)) ([18c6af5](https://github.com/ng-alain/delon/commit/18c6af5))

### Features

* **abc:reuse-tab:** add `tabBarExtraContent` `tabBarStyle` `tabBarGutter` properites ([#510](https://github.com/ng-alain/delon/issues/510)) ([5d48933](https://github.com/ng-alain/delon/commit/5d48933))
* **acl:** add `preCan` property in global config ([#511](https://github.com/ng-alain/delon/issues/511)) ([1bdbd8c](https://github.com/ng-alain/delon/commit/1bdbd8c))

# [7.1.0](https://github.com/ng-alain/delon/compare/7.0.3...7.1.0) (2019-03-29)

### Bug Fixes

* **sf:checkbox:** fix invalid trigger check-all when click input ([#493](https://github.com/ng-alain/delon/issues/493)) ([4ee3ca5](https://github.com/ng-alain/delon/commit/4ee3ca5))
* **sf:select:** fix invalid clear value ([#496](https://github.com/ng-alain/delon/issues/496)) ([28e3915](https://github.com/ng-alain/delon/commit/28e3915))

### Features

* **abc:qr:** add support unicode value ([#495](https://github.com/ng-alain/delon/issues/495)) ([9082319](https://github.com/ng-alain/delon/commit/9082319))
* **abc:sv:** add `unit` property ([#497](https://github.com/ng-alain/delon/issues/497)) ([5a84e1b](https://github.com/ng-alain/delon/commit/5a84e1b))
* **cli:plugin:sts:** add [sts](https://github.com/ng-alain/sts) plugin ([#494](https://github.com/ng-alain/delon/issues/494)) ([5f735db](https://github.com/ng-alain/delon/commit/5f735db))
* **module:theme:** adding Korean locale ([#486](https://github.com/ng-alain/delon/issues/486)) ([5e3ad9c](https://github.com/ng-alain/delon/commit/5e3ad9c))

### BREAKING CHANGES

* **refactor(abc:st):** `currenty` rename to `currency` ([#492](https://github.com/ng-alain/delon/issues/492)) ([f42861a](https://github.com/ng-alain/delon/commit/f42861a))

## [7.0.3](https://github.com/ng-alain/delon/compare/7.0.2...7.0.3) (2019-03-20)

### Bug Fixes

* **abc:result:** use `nzType` instead of class anticon ([#483](https://github.com/ng-alain/delon/issues/483)) ([7553860](https://github.com/ng-alain/delon/commit/7553860))
* **abc:se:** should be keeping placeholder when content is empty ([#480](https://github.com/ng-alain/delon/issues/480)) ([e35c2e0](https://github.com/ng-alain/delon/commit/e35c2e0))
* **abc:st:** fix invalid number type of width ([#481](https://github.com/ng-alain/delon/issues/481)) ([7cdbe6e](https://github.com/ng-alain/delon/commit/7cdbe6e))
* **abc:st:** fix losing global config in modal or drawer ([#482](https://github.com/ng-alain/delon/issues/482)) ([ab34a44](https://github.com/ng-alain/delon/commit/ab34a44))
* **abc:st:** fix styles of filter button ([#474](https://github.com/ng-alain/delon/issues/474)) ([f491b4d](https://github.com/ng-alain/delon/commit/f491b4d))
* **sf:number:** fix show undefined or null when use prefix or unit an… ([#473](https://github.com/ng-alain/delon/issues/473)) ([4d2cede](https://github.com/ng-alain/delon/commit/4d2cede))
* **util:deepGet:** fix losing 0 value ([#479](https://github.com/ng-alain/delon/issues/479)) ([bf37459](https://github.com/ng-alain/delon/commit/bf37459))

### Features

* **abc:st:** add raw data in custom  type of statistical ([#478](https://github.com/ng-alain/delon/issues/478)) ([431c461](https://github.com/ng-alain/delon/commit/431c461))

## [7.0.2](https://github.com/ng-alain/delon/compare/7.0.1...7.0.2) (2019-03-05)

### Bug Fixes

* **abc:sidebar-nav:** fix warnning 'Navigation triggered outside Angu… ([#466](https://github.com/ng-alain/delon/issues/466)) ([b565b3f](https://github.com/ng-alain/delon/commit/b565b3f))
* **abc:st:** fix losing req config ([#467](https://github.com/ng-alain/delon/issues/467)) ([697f33e](https://github.com/ng-alain/delon/commit/697f33e))
* **theme:drawer:** fix body scroll when placement is top or bottom ([#469](https://github.com/ng-alain/delon/issues/469)) ([873d0de](https://github.com/ng-alain/delon/commit/873d0de))

### Features

* **sf:upload:** add urlReName property ([#464](https://github.com/ng-alain/delon/issues/464)) ([5540631](https://github.com/ng-alain/delon/commit/5540631))

## [7.0.1](https://github.com/ng-alain/delon/compare/7.0.0...7.0.1) (2019-03-01)

### Bug Fixes

* **cli:** fix ignores files and folders named "core" by default ([#461](https://github.com/ng-alain/delon/issues/461)) ([bd5696a](https://github.com/ng-alain/delon/commit/bd5696a))

# [7.0.0](https://github.com/ng-alain/delon/compare/7.0.0-rc.10...7.0.0) (2019-02-28)

**All is well, has been waiting for NG-ZORRO 7.0.0, it's the basic component of ng-alain, so this update just keeps the synchronization of the major version number**

### Features

* sync NG-ZORRO 7.0.0
* add el_GR locale ([#423](https://github.com/ng-alain/delon/issues/423)) ([17a03d6](https://github.com/ng-alain/delon/commit/17a03d6))

## Old Version

All releases notes can be found [here](https://github.com/ng-alain/ng-alain/releases)

repository: xiaruqin/delon

gha_license_id: MIT

repo_name: xiaruqin/delon


text:
# 1. Create the badge text.

- Be careful about the differences between equality (`==`) and identity (`===`) operators.
- [Strings][strings] in JavaScript have several methods to change between upper and lower cases.

[strings]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String#Instance_methods

repository: lbain/javascript

repo_name: lbain/javascript


text:
---
title: API
---

# API

## applyMiddlewareBuffered

Creates a store enhancer that applies middleware to the dispatch method
of the Redux store, and buffers actions until all middlewares are finished processing
the action. This should be the first store enhancer in the composition chain.

**Parameters**

-   `buffer`   (optional, default `[]`)
-   `middlewares` **...[function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function)** The chain of middlewares to be applied. (optional, default `[]`)

Returns **[function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function)** A store enhancer applying the middleware.

## index

The entry point to the whole system.

**Parameters**

-   `config` **[object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object)** The Vester configuration. (optional, default `{}`)

## createBrokerBacktest

Creates a broker middleware to be used when running backtests.
In contrast to the realtime broker middleware, this middleware both places and fills an order
in one cycle. This makes it possible to simulate what would happen if we always were able to
perform our transactions at the historical date and time.

**Parameters**

-   `commission` **([number](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number) \| [function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function))** Calculate the commission based on price and quantity (optional, default `0`)

Returns **[function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function)** Middleware

## createBrokerRealtime

Creates a broker middleware to be used running backtests.
In contrast to the backtest broker middleware, this middleware builds an order, then dispatches
the built order for the next round-trip. When the built order arrives back at this middleware,
it is executed synchronously.

**Parameters**

-   `createClient` **[function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function)** Factory function for building the client to be used when sending
                                    requests to an _actual_ broker.

Returns **[function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function)** Middleware

## createRiskManager

The risk manager middleware has the capability to alter orders or even prevent them from being
requested in the first place. It should also warn the user when some risk metric is out of bounds.

**Parameters**

-   `settings` **[object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object)** A settings object.
-   `getMetrics`

Returns **[function](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function)** Middleware

repository: ben-haim/vester

repo_name: ben-haim/vester


text:
Description [ ![Codeship Status for TheSerapher/chef-awstats](https://www.codeship.io/projects/434832e0-6884-0130-7230-22000a8c4a68/status?branch=master)](https://www.codeship.io/projects/1790)
===========

Installs and configures awstats for Apache.

Requirements
============

## Platform:

* Ubuntu
* Debian
* CentOS
* RHEL

## Cookbooks:

* apache2
* yum

Attributes
==========

    Attribute
    Description
    Default

    node['awstats']['reload_apache']
    Reload apache if the apache configuration changes
    true

Recipes
=======

## awstats::default

Installs/configures awstats

Testing
=======

The cookbook comes with some testing facilities allowing you to iterate quickly
on cookbook changes.

## Rake

You can execute the tests with [Rake](http://rake.rubyforge.org). The `Rakefile`
provides the following tasks:

    $ rake -T
    rake chefspec    # Run ChefSpec examples
    rake foodcritic  # Run Foodcritic lint checks
    rake knife       # Run knife cookbook test
    rake test        # Run all tests

## Bundler

If you prefer to let [Bundler](http://gembundler.com) install all required gems
(you should), run the tests this way:

    $ bundle install
    $ bundle exec rake test

## Berkshelf

[Berkshelf](http://berkshelf.com) is used to set up the cookbook and its
dependencies (as defined in `Berksfile`) prior to testing with Rake and Vagrant.

This command will boot and provision the VM as specified in the
`Vagrantfile`:

    $ bundle exec vagrant up <name>

Name refers to any box setup by `test-kitchen`, see below.

(Berkshelf's Vagrant plugin will make your cookbook and its dependencies
automatically available to Vagrant when creating or provisioning a VM.)

## Kitchen

This cookbook is using [test-kitchen](https://github.com/opscode/test-kitchen)  to propagate
the `Vagrantfile`. You can review the boxes by using:

    $ bundle exec kitchen list

Each item in this list is a regular vagrant box that can be started as
usual.

To run the full kitchen suite included in this cookbook simply execute:

    $ bundle exec kitchen test

License and Author
==================

Author:: Sebastian Grewe<EMAIL_ADDRESS>

Copyright:: 2013, Sebastian Grewe

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: TheSerapher/chef-awstats

branch_name: refs/heads/next

gha_language: Ruby

repo_name: TheSerapher/chef-awstats


text:
# FX Rates Right

[![Build Status](https://travis-ci.org/successkrisz/fx-rates-right.svg?branch=master)](https://travis-ci.org/successkrisz/fx-rates-right?branch=master)
[![dependencies](https://david-dm.org/successkrisz/fx-rates-right.svg)](https://david-dm.org/successkrisz/fx-rates-right)
[![devDependency Status](https://david-dm.org/successkrisz/fx-rates-right/dev-status.svg)](https://david-dm.org/successkrisz/fx-rates-right#info=devDependencies)
[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg)](http://standardjs.com/)

### Description

App to retrieve FX rates on any given weekday (since 04/01/1999).
Written for an interview coding challenge.

### Features

 * React
 * Redux
 * React Router
 * Recharts
 * davezuko's development setup (Webpack, ES6+, ...)

### Install from source

First, clone the project:

```bash
$ git clone https://github.com/successkrisz/fx-rates-right.git <my-project-name>
$ cd <my-project-name>
```

Then install dependencies and check to see it works. It is recommended that you use [Yarn](https://yarnpkg.com/) for deterministic installs, but `npm install` will work just as well.

```bash
$ yarn install    # Install project dependencies
$ yarn start      # Compile and launch (same as `npm start`)
```
If everything works, you should see the following:

<img src="http://i.imgur.com/Kk2qTHC.png" />

While developing, you will probably rely mostly on `yarn start`; however, there are additional scripts at your disposal:

|`yarn run <script>`|Description|
|------------------|-----------|
|`start`|Serves your app at `localhost:3000`. HMR will be enabled in development.|
|`compile`|Compiles the application to disk (`~/dist` by default).|
|`dev`|Same as `yarn start`, but enables nodemon for the server as well.|
|`test`|Runs unit tests with Karma and generates a coverage report.|
|`test:dev`|Runs Karma and watches for changes to re-run tests; does not generate coverage reports.|
|`deploy`|Runs linter, tests, and then, on success, compiles your application to disk.|
|`deploy:dev`|Same as `deploy` but overrides `NODE_ENV` to "development".|
|`deploy:prod`|Same as `deploy` but overrides `NODE_ENV` to "production".|
|`lint`|Lint all `.js` files.|
|`lint:fix`|Lint and fix all `.js` files. [Read more on this](http://eslint.org/docs/user-guide/command-line-interface.html#fix).|

### Thank you

[David Zukowski](https://github.com/davezuko) - For creating an amazing development `boilerplate`

repository: successkrisz/fx-rates-right

repo_name: successkrisz/fx-rates-right


text:
# react-infinite-ticker

React component that scrolls children infinitely.

## Demo

[See here](https://g12i.github.io/react-infinite-ticker/).

## Quick start

```bash
npm install react-infinite-ticker
```

```jsx
import React from "react";
import { VerticalTicker, HorizontalTicker } from "react-infinite-ticker";

function App() {
  const [ref, scroll] = useScrollTo();

  return (
    <div>
      <VerticalTicker>
        <div>Put anything you want</div>
        <img src="/images/as/well.png" />
        <h1>All good</h1>
      </VerticalTicker>
      <HorizontalTicker speed={1.5}>
        <div>Put anything you want</div>
        <img src="/images/as/well.png" />
        <h1>All good</h1>
      </HorizontalTicker>
    </div>
  );
}
```

## Configuration

### `speed` _(optional)_

Both `VerticalTicker` and `HorizontalTicker` take `speed` props, which is a
**number** of pixels by which elements are scrolled on each animation frame.

license: ISC

repository: inkinkz/react-infinite-ticker

repo_name: inkinkz/react-infinite-ticker


text:
# Javascript-like C++ promise library

This library provides a `Promise` class that aims to mimic the behavior of the typical
JavaScript promise object. It does not implement any particular Javascript standard promise
API (Promises/A, native promise, etc), but follows the main principles. This document assumes that
the reader has a basic understanding of how typical Javascript promises work.

IMPORTANT NOTE: there is one major difference, though. Most modern Javascript promises (including JS Native promises) resolve asynchronously, i.e. their `resolve()` method does not directly call the `then()` handlers,
but schedules the calls on the next message loop iteration. The same happens when a `then()/catch()` handler
is attached to an already resolved/rejected promise. This may be a bit less efficient, but makes the behavior symmetric and more predictable. This library resolves synchronously, because it is unaware of the
message loop that is used in the application.

## Installation
You need to clone this repository with the `--recursive` switch if you want to run the tests. This is because the test framework - `async-test`, is included as a submodule.

## Usage
This is a header-only library, consisting of just one header - promise.hpp. You only need to include that header in your code. There are no dependencies on other files from this repository, so you can copy promise.hpp to your project tree and use it from there.

## Compatibility
This library should be compatible with gcc >= 4.9, clang >= 3.3 and Visual Studio >= 2015

## Tests
A test suite is included, together with a submodule for the `async-test` framework that is used for the test suite. See the Readme.md in the `tests` subdirectory for details how to run and build the tests.

# API
A brief overview of the API follows. For practical usage examples and details on the behavior,
please see the included tests in `tests/promise-test.cpp`

## The Promise<T, L> class
Intuitively, the `T` class is the type of the value, held by the promise object. It can be `void` as well.

As for what `L` is - some explanation is needed. When `.then()` and `.fail()` handlers
are attached to a promise, they are added to internal lists. For performance reasons,
these lists are implemented as static arrays. The `L` constant is the size of
these arrays, and its default value is 4. This avoids some dynamic memory allocation and deallocation
when promise objects are created and destroyed. This comes at the cost of having a fixed limit of
`.then` and `.fail` handlers that can be attached to a _single_ promise object.
Note that this does not affect the promise chain length, but only the number of chains a promise can
"fork". Also, when a `.then()` or `.fail()` callback is executed, the actual promise that it returns
is "merged" with the "placeholder" promise that was returned by the `.then()` / `.fail()` method
at the time the promise chain was set up (usually before anything has yet executed).
This "merge" operation moves all handlers, that may be attached to the returned promise,
to the "placeholder", i.e. chain linking promise.
Therefore, there need to be enough slots in that chain linking promise. This is usually not an issue,
because the promises returned by handlers don't have any handlers attached. Handlers are usually
attached when chaining promises. This, however, may not be the case, if the handler itself contains
a promise chain, and returns a promise that is not at its end. This is a very exotic case, and is still
perfectly fine with a reasonable number of handlers attached to each of the two promises. In any case,
checks are performed in both debug and release mode and an exception is thrown if callback slots are
exhausted. The exception is of type `std::runtime_error` and has an informative message. Please let me know
if the fixed maximum of handlers is a problem for you. If it turns our to be cumbersome for many users,
I will consider switching to dynamic lists.
You can increase the default globally by defining `PROMISE_MAX_HANDLE_COUNT` before including `promise.hpp`. However, this define-before-include order has to be taken care of for each compilation unit.
This may be cumbersome, if done at the source code level. A better option could be to add the define to the
build system of your application, so that all compilation units will have it specified, and it will always be defined before any code is preprocessed/compiled.
You can also define it per object by overriding the template parameter. This can be done in specific
use cases where it is known that a lot of handlers will be attached to that promise object. However, this is
currently not well supported, since L is not passed to the promise types returned by `.then()`, `.fail()`, etc.
This may lead to compile errors.

### Lifetime of Promise objects
The Promise object is internally reference counted, so copying it is very lightweight and its lifetime is
automatically managed. Normally you don't need to create Promise objects on the heap with `operator new`, and
pass them by pointers. They are designed to be allocated on the stack or as a member.
You can regard the Promise<T> class as a fancy shared pointer.

### Error class
Error is a special class that carries information about an error. It has a type code, error code and an
optional message string. It is reference-counted, so it's very lightweight to copy around and
its lifetime is automatically managed.
If a particular Error object is not passed to a `fail()` handler during its lifetime,
an "unhandled promise error" warning will be printed to `stderr`. The user can configure the library
to call a function instead, by defining the macro `PROMISE_ON_UNHANDLED_ERROR` to the name of the function
to be called. The function has the following prototype: `myHandler(const std::string& msg, int type, int code)`.
In this case, `PROMISE_ON_UNHANDLED_ERROR` has to be defined as:

`#define PROMISE_ON_UNHANDLED_ERROR myHandler`

The handler function doesn't need to be aware of the Promise library - this is the reason its prototype is specified to not take the Error object directly.

### `Promise::resolve(T val)`
### `Promise::resolve()`
Resolves the promise and causes `.then()` handlers to be executed down the promise chain.

### `Promise::reject(Error err)`
Rejects the promise and causes `.fail()` handlers to be executed down the promise chain.

### `Promise::then(F&& func)`
The provided functor is called with the value of the promise, when the promise is
resolved. The return value of `then()` is a `Promise` object of the type, returned
by the functor. If the functor returns a promise, the return type of the type of that promise.

### `Promise::fail(F&& func)`
The provided functor is called with an Error object. The return value is a promise of the same type as the
one on which `fail()` is called. If the functor returns a promise that is eventually rejected, further error handlers down the chain will be called, if any. If there are none, a warning will be printed on stdout (see above). If the returned promise is eventually resolved, further `.then()` handlers down the chain will be executed.

### `Promise::done()`
Returns the state of the promise, as one of the three values of the `ResolvedState` enum - pending, succeeded or
failed. The pending state `kNotResolved` has the value of zero, so the value can be conveniently used in boolean
expressions to signify whether the promise is is pending or resolved/failed, i.e. "done".

### `Promise::succeeded(), Promise::failed()`
Convenience methods to check the state of the promise.

### `Promise::error()`
Returns the Error object with which the promise was rejected. If the promise is not in `kRejected` state, an assertion is triggered. Therefore, this method should only be called after a check if the promise is actually
in rejected state.

### `static Promise<void> Promise::when(...)`
### `static Promise<void> Promise::when(std::vector<Promise<P>>)`
Returns a Promise<void> that is:
 - Resolved when all the provided promises are resolved.
 - Rejected if at least one of the provided promises is rejected.
The difference between the two methods is that the one that takes multiple arguments can take promises of different
types, where as the one that takes a vector operates on promises of the same type.


text:
# Metaparticle/Package for Go
Metaparticle/Package is a collection of libraries intended to
make building and deploying containers a seamless and idiomatic
experience for developers.

This is the implementation for Go.

## Introduction
Metaparticle/Package simplifies and centralizes the task of
building and deploying a container image.

Here is a quick example.

Consider this simple Go application:

```go
package main

import "fmt"

func main() {
    fmt.Println("Hello World")
}
```

To containerize this application, you need to replace the contents of your main on the main.go file (the entrypoint is still hardcoded)
function with the `Containerize` wrapper, passing the `Runtime` and `Package` structs, and wrapping your old main on a `func()`, like this:

```go
package main

import(
    "fmt"
    "github.com/metaparticle-io/package/go/metaparticle"
)

func main() {
    metaparticle.Containerize(
        &metaparticle.Runtime{
            Executor:        "docker"},
        &metaparticle.Package{Repository: "xfernando",
            Builder: "docker"},
        func() {
            fmt.Println("Hello World")
        })
}
```

Then you only have to do `go run main.go`, and a container will be built and deployed to your docker instance.

repository: pemmasanikrishna/package

gha_language: Go

repo_name: pemmasanikrishna/package


text:
---
# Documentation: https://sourcethemes.com/academic/docs/managing-content/

title: "Relationship Between Party Control of State Government and Key Well-Being Metrics"
summary: "Interactive dashboard exploring the relationship between party control of state government and a variety of well-being metrics at the state level. This is part 1 of a multi-part series of visualizations and analyses exploring this topic."
authors: []
tags: []
categories: []
date: 2020-01-13T10:57:56-05:00

# Optional external URL for project (replaces project detail page).
external_link: ""

# Featured image
# To use, add an image named `featured.jpg/png` to your page's folder.
# Focal points: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight.
image:
  caption: ""
  focal_point: ""
  preview_only: true

# Custom links (optional).
#   Uncomment and edit lines below to show custom links.
# links:
# - name: Follow
#   url: https://twitter.com
#   icon_pack: fab
#   icon: twitter

url_code: ""
url_pdf: ""
url_slides: ""
url_video: ""

# Slides (optional).
#   Associate this project with Markdown slides.
#   Simply enter your slide deck's filename without extension.
#   E.g. `slides = "example-slides"` references `content/slides/example-slides.md`.
#   Otherwise, set `slides = ""`.
slides: ""
---
The following is an interactive dashboard exploring the relationship between party control of state government and a variety of well-being metrics at the state level. This is part 1 of a multi-part series of visualizations and analyses exploring this topic.

The dashboard, along with a short accompanying piece, was published by the Georgetown Public Policy Review in January 2020. The link to that publication can be found [here](http://gppreview.com/2020/01/09/relationships-party-control-state-government-key-well-metrics/).

The data and code used in this analysis can be found [here](https://github.com/andygreen-1/PartyControlStateGov).
***


text:
# Giter8 Template for TMT

This is a Giter8 template for a TMT component developer which creates a sample `sbt` project for CSW Components.
The created project contains three subprojects:

- An Assembly
- An HCD
- A Deploy module, containing code to run the components

## Getting Started

### Install Coursier
Please follow the [coursier installation](https://get-coursier.io/docs/cli-installation)

### Install Giter8

`cs install giter8`

### Create new project using giter8 template

`g8 tmtsoftware/csw.g8`

This template will prompt for the following parameters. Press Enter to accept the default values, shown in brackets:

- `name [sample]`: The name of the project.
- `assemblyComponentName [sample]` : The Component Name of the Assembly
- `hcdComponentName [sampleHcd]` : The Component Name of the HCD
- `organization [org.tmt]`: Specifies the organization for this project.
- `subsystem [CSW]`: Specifies the subsystem name.
- `version [0.0.1]`: Specifies the component version for this project.
- `package [org.tmt.csw]`: Top level package which dynamically gets created based on provided organization and subsystem in all subprojects.
- `deploy_module [sample-deploy]`: Subproject name which holds HostConfig and ContainerCmd applications.
- `assembly_module [sample]`: Subproject name which holds the Assembly code.
- `hcd_module [samplehcd]`: Subproject name which holds the HCD code.
- `scala_version [2.13.3]`: Specifies the Scala version for this project.

---
**NOTE**
Following section is intended only for testing purpose and can be skipped by the consumers of template.

#### Testing the template

For people interested in testing the template with the latest commit on the dev branch (active development branch), refer [TESTING.md](TESTING.md)

gha_language: Scala


text:
Pattern: Calling uncallable object

Issue: -

## Description

This issue is usually a result of name collision between class/method or module/function. Because of this a `TypeError` is raised at runtime. Fully qualify the called function or use more specific `import` statements to resolve this issue.

Example of **incorrect** code:

```python
import random

print(random()) # [not-callable]
```

Examples of **correct** code:

```python
from random import random # more specific import statement

print(random())
print(random.random()) # fully qualified function
```

repository: Adroiti/docs-for-code-review-tools

repo_name: Adroiti/docs-for-code-review-tools


text:
# Backbone::View::Enhanced::Events::Declaration::Rails

A Rails 3 asset pipeline gem for [Backbone.View.EnhancedEventsDeclaration](http://github.com/simsalabim/backbone.view.enhanced_events_declaration) mixin.

## Installation

Add this line to your application's Gemfile:

    gem 'backbone-view-enhanced-events-declaration-rails', '~> 0.0.3'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install backbone-view-enhanced-events-declaration-rails

## Usage

Add the mixin script to your `application.coffee` after backbone.js

```coffeescript
#= require backbone
#= require backbone/backbone.view.enhanced_events_declaration
```

There's also a minified version available by `backbone/backbone.view.enhanced_events_declaration.min`

That's it! Now you can inherit your classes from `Backbone.View` and use all the convenience of enhanced events declaration.

```coffeescript
class ContentView extends Backbone.View

  events:
    'click .decorate'     : 'decorate'
    'click .reorder'      : 'reorder'
    'click .mix-it'       : 'decorate reorder'
    'click .mix-it-again' : [ 'decorate', 'reorder' ]
    'click .mix-it-quick' : [ 'decorate', =>( console.log('reordering method') ) ]

  decorate: (e) ->
  # ...

  reorder: (e) ->
  #  ...
```

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request

Author: Alexander Kaupanin


text:
# View the node performance diagnostics report {#concept_ibb_qyr_2gb .concept}

The diagnostics report lists the details and levels of the issues on a node and provides optimization suggestions. It allows you to fully understand the issues and optimize the node accordingly to improve the node performance. The diagnostics report includes the basic information, comprehensive performance score, status and issues of the core metrics, and Structured Query Language \(SQL\) statement analysis of the node. The core metrics include the central processing unit \(CPU\) usage, memory usage, storage usage, input/output operations per second \(IOPS\), and connections. This topic describes how to create and view the performance diagnostics report for a node.

## Procedure {#section_f4b_sb3_mfb .section}

1.  Log on to the [ApsaraDB for POLARDB console](https://polardb.console.aliyun.com/).
2.  Select a region.
3.  Find the target cluster and click the **cluster ID** in the Cluster Name column.
4.  In the left-side navigation pane, choose **Diagnostics and Optimization** \> **Diagnosis**.
5.  Click the Diagnostics Report tab, and click **Create Diagnostics Report**.

    ![](images/34849_en-US.png)

6.  Set the start time and end time of the diagnostics report, and click **Create Report**.
7.  After the report is generated, click **View Report** in the **Actions** column. Click **View** in the dialog box that appears.

url: https://raw.githubusercontent.com/15205080581/polardb/217a5d73551e5f5fd780e425946fcaa047332afc/intl.en-US/User Guide for MySQL/Diagnostics and optimization/Diagnosis/View the node performance diagnostics report.md


text:
<img src="https://raw.githubusercontent.com/soumya92/barista/gh-pages/logo/128.png" height="128" width="128" alt="Logo" />

# Barista

[![Build Status](https://travis-ci.org/soumya92/barista.svg?branch=master)](https://travis-ci.org/soumya92/barista)
[![GoDoc](https://godoc.org/github.com/soumya92/barista?status.svg)](https://godoc.org/github.com/soumya92/barista)
[![Go Report Card](https://goreportcard.com/badge/github.com/soumya92/barista)](https://goreportcard.com/report/github.com/soumya92/barista)
[![codecov](https://codecov.io/gh/soumya92/barista/branch/master/graph/badge.svg)](https://codecov.io/gh/soumya92/barista)

Barista is an i3 status bar written in golang.

**This is not an official Google product**

*This project is in progress. The core API is stable, but user bars may still
break on updates. See the [Release (v1) Project](https://github.com/soumya92/barista/projects/3)
for progress towards a stable release.*

Also look at the [stable-api sample](https://github.com/soumya92/barista/tree/master/samples/stable-api)
to see what APIs are considered stable. As a general rule, any code in the
stable-api sample will continue to work across updates.

## Features

- Based on push rather than fixed interval polling. Currently only media and
  volume benefit from this, but this opens the door to async updates from
  shell scripts, irc, &c.

- Produces a single binary via go build. This makes it easy to set up the bar
  executable, since no import paths, environment variables, et al. need to be
  configured.

- Good click handlers (especially media and volume), since we can wait for a
  command and update the bar immediately rather than waiting for the next 'tick'.

- Configuration is code, providing oodles of customization options without
  needing myriad configuration options in a file somewhere. If/then/else, loops,
  functions, variables, and even other go packages can all be used seamlessly.

## Usage

See samples/sample-bar.go for a sample bar.

To build your own bar, simply create a `package main` go file,
import and configure the modules you wish to use, and call `barista.Run()`.

To show your bar in i3, set the `status_command` of a `bar { ... }` section
to be the newly built bar binary, e.g.

```
bar {
  position top
  status_command exec ~/bin/mybar
  font pango:DejaVu Sans Mono 10
}
```

See the [wiki](https://github.com/soumya92/barista/wiki) for more details

repository: Happy-Ferret/barista

repo_name: Happy-Ferret/barista


text:
---
title: Flashing LOLin V3 NodeMCU firmware
date: 2016-08-23
tags:
  - iot
---
A few months ago, i did bought a chinese version of NodeMCU named LOLin V3, it's not version of 3 of NodeMCU, it's using CH340G chip which is the TTL to USB converter made by a chinese manufacture instead of the FTDI. After using for few times, it's stopped working.

![LOLin V3](/assets/posts/lolin/board.jpg)

## Install the esptool
We need to download and install the ```esptool``` that will help us the new flash the new firmware

```sh
$ git clone https://github.com/themadinventor/esptool.git
$ cd esptool
$ python setup.py install
```

## Downloading the firmware
You can grab the latest .bin version of the firmware from the [github][0] repo, or use [nodemcu-build][1] to build a custom firmware.

## Flashing the firmware
First, you need to know is the USB port where the board is plugged, open the commandline, then use the esptool to flash the new firmware :

```sh
$ python esptool.py --port /dev/ttyUSB0 --baud 9600 write_flash --flash_mode qio --flash_size 32m --flash_freq 40m 0x00000 nodemcu_float_0.9.6-dev_20150704.bin
esptool.py v1.0.2-dev
Connecting...
Running Cesanta flasher stub...
Flash params set to 0x0040
Writing 450560 @ 0x0... 450560 (100 %)
Wrote 450560 bytes at 0x0 in 19.5 seconds (184.5 kbit/s)...
Leaving...
```

Once the flashing is done, just open ```ESPlorer```, set the USB port and the baud speed then hit ```Open``` :

![ESPlorer](/assets/posts/lolin/esplorer.jpg)

[0]: https://github.com/nodemcu/nodemcu-firmware/releases
[1]: https://nodemcu-build.com


text:
This may include information that identifies you.

00.sec=Once your information is shared with {_Program}, it may no longer be protected by patient privacy rules (like HIPAA). However, it will still be protected by other privacy rules. These include the rules that researchers must follow to access the {_Program} scientific database.

=[G/Z/paras/s2]

repository: CommonAccord/Cmacc-Org

gha_language: CSS

repo_name: CommonAccord/Cmacc-Org


text:
---
layout: default
---

# 1994-12-19 - (fwd) Re: Content-Type of application/pgp

## Header Data

From<EMAIL_ADDRESS>(James A. Donald)

To<EMAIL_ADDRESS>Message Hash: ff63d6aefc234a6b7901bca966217a8f9e9c42dc0db34579ecae315b2598be6d

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1994-12-19 19:15:02 UTC

Raw Date: Mon, 19 Dec 94 11:15:02 PST

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(James A. Donald)
Date: Mon, 19 Dec 94 11:15:02 PST
To<EMAIL_ADDRESS>Subject: (fwd) Re: Content-Type of application/pgp
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

Xref: netcom.com comp.mail.mime:5131
Path: netcom.com!ix.netcom.com!howland.reston.ans.net!agate!library.ucla.edu!csulb.edu!paris.ics.uci.edu!ucivax!gateway
From<EMAIL_ADDRESS>(Nathaniel Borenstein)
Subject: Re: Content-Type of application/pgp
Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>Newsgroups: comp.mail.mime
Lines: 17
References<EMAIL_ADDRESS>Date: 12 Dec 94 15:01:06 GMT

After several discussions over the last few weeks -- with Phil
Zimmerman, Jim Galvin, Ned Freed, and others at Email World and IETF --
I have reached the conclusion that the application/pgp type should be
ABANDONED in favor of an approach based on multipart/security.   My
application/pgp Internet Draft is expiring shortly & will not be
renewed.  By using multipart/security, we can work towards a greater
level of harmony between the PEM and PGP communities.  It also now
appears that there's a chance that PEM and PGP keys can be made
interoperable, which would be a huge win.

I don't want anyone to think I'm standing in the way of this
convergence, so I wanted to publicly state that I have abandoned my
application/pgp Internet Draft.

What we need now is for someone to work up a new draft on how to use PGP
inside of multipart/security.  I'm swamped.  Any volunteers?  --
Nathaniel

--
 ---------------------------------------------------------------------
We have the right to defend ourselves and our
property, because of the kind of animals that we        James A. Donald
are.  True law derives from this right, not from
the arbitrary power of the omnipotent state<EMAIL_ADDRESS>

{% endraw %}
```

## Thread

+ Return to [December 1994](/archive/1994/12)

+ Return to<EMAIL_ADDRESS>(James A. Donald)](/authors/jamesd_at_netcom_com_james_a_donald_)"

+ 1994-12-19 (Mon, 19 Dec 94 11:15:02 PST) - (fwd) Re: Content-Type of application/pgp -<EMAIL_ADDRESS>(James A. Donald)_


text:
# Design
This app will mostly center around scrolling through quiz cards.

## Components

### Introduction Page
We'll need a page to give instructions and trigger starting the quiz.

### Quiz Card
Each quiz card will be a stateful representation of the quote, with an option to select the answer

#### Quote
A stylized quotation.

#### Answer Select
An answer select with the nine names listed.

#### Submit button
A button to commit to the answer. This should trigger

* Displaying the correct answer.
* Update your score.
* Display the image for the answer.

#### Answer
A display that shows the correct answer.

### Quiz Navigation
Click next if the current question is complete and loads the next question if it exists.

### Score
Potentially colored by percentage (0-33% red, 34-75% yellow, 76%-100% green).

### Ending Screen
Congratulations. Display EndingScore, and picture of orc.

repository: mshenfield/know-your-nine

gha_language: TypeScript

repo_name: mshenfield/know-your-nine


text:
# Kettle CKAN Writer
Kettle CKAN DataStore Writer (forked from https://github.com/OpenGov-OpenData/CKAN-DataStore-Writer-for-Pentaho-Data-Integration)

## Installation
Remove old versions of the plugin from your <KETTLE_DIR>/plugins.

run 'mvn clean install'

copy target/knowbi-kettle-ckan-step to the plugins folder in your Kettle install dir

OR

run 'mvn clean install -Dkettle.dir=<KETTLE_DIR>/plugins' to install directly.

## Options
To create an new Datastore resource provide a valid Package ID and omit the Resource ID

| Option         | Description                                                                                |
| -------------- | ------------------------------------------------------------------------------------------------------- |
| Step name	     |Name of the step. This name should be unique in a single transformation.                                 |
| Domain         |The domain of the CKAN data portal to which data will be uploaded. (eg: http://demo.ckan.org)            |
| API Key        |Users can find their API key in their user profile on the CKAN data portal.                              |
| Package ID     |The ID of an existing package where data will be uploaded in a DataStore resource. (eg: test-dataset)    |
| Resource Title |The title of the resource.                                                                               |
| Description    |A short description about the resource. (optional)                                                       |
| Resource ID    |The ID of an existing DataStore resource to update. If left empty a new DataStore resource will be made. |
| Batch Size     |The writer will upload rows of data in batches of this amount. (default: 5000)                           |
| Primary Key    |If a Primary Key is specified then data will be upserted instead of inserted. Multiple fields can be specified as the Primary Key, use double semicolons to delineate the fields (eg: field1;;field2) |

### PDI Sample Transformation
Caio Moreno's blog post http://blog.professorcoruja.com/2017/06/unlock-your-data-using-pdi-and-ckan-pdi.html

example transformation: src/test/resources/tr_ckan_kettle_plugin_example.ktr

repository: knowbi/knowbi-kettle-ckan-step

repo_name: knowbi/knowbi-kettle-ckan-step


text:
# Store

## Overview

Store is a simple Node.js CLI for working with data in the form of key-value pairs. It provides basic Create / Update / Delete functionality, and will persist your data to a local file automatically.

## Objectives

Allow the user to:

- Add a key-value pair.

- Update a key-value pair.

- List all key-value pairs.

- Get a value by entering its corresponding key.

- Remove a key-value pair.

## Getting Started

### Installation
These instructions assume that you already have Node installed globally on your system, and are familiar with using the command line.

#### Git
Clone the repo using `$ git clone https://github.com/nfurfaro/node-cli-datastore.git`

or

#### Zip Archive

Download  the zip archive from https://github.com/nfurfaro/node-cli-datastore

From inside the `node-cli-datastore` directory, run `$ npm install` to install project dependencies, followed by `$ npm link` to set up the executable command "store".

### Usage
`$ store help `
View the store documentation.

`$ store add <myKey> <myValue>`
Add a key-value pair.
example: `$ store add goesTo 11`

`$ store list `
View all key-value pairs

`$ store get <myKey> `
Get a value by its key.
example:`$ store get goesTo` returns `$ 11`

`$ store remove <myKey>`
Remove a key-value pair by its key.
example:`$ store remove goesTo` removes both the key and its value.

license: Unlicense

repository: nfurfaro/node-cli-datastore

repo_name: nfurfaro/node-cli-datastore


text:
---
layout: kanji
v4: 975
v6: 1049
kanji: 側
keyword: side
elements: side, person, rule, shellfish, clam, oyster, eye, animal legs, eight, sword, sabre, saber
strokes: 11
image: E581B4
on-yomi: ソク
kun-yomi: かわ、がわ、そば
permalink: /rtk/側/
prev: 健
next: 侍
---

1) [nilfisq] 12-9-2007(185): Mr. T rulezzz! I am on his side!

2) [amthomas] 21-3-2007(38): Chuck Norris's rules are easy to live by, just be on his side.

3) [CharleyGarrett] 17-12-2006(29): "Mr. T got one rule!" says Mr. T. "I'm on the side of those picked on by the bullies. I pity da foo who tries to bully those smaller than he is!".

4) [somukeru] 6-3-2008(23): There is the dark side and the Jedi side. Those on the Jedi side follows the rules.

5) [cescoz] 24-7-2009(15): A PERSON that follow your RULES is at your side.


text:
# EOS Payment Terminal

## Synopsis

Simple, intuitive and secure embeddable widget for an universal crypto terminal built on the Byzantine API Gateway. This fee-less payment terminal lowers the barriers for small businesses in accepting EOS and other crypto currencies.

### Terminal Interface
![Terminal Iterface](./image/terminal.png)

## Install and run dev mode

```sh
git clone https://github.com/Byzantine-Works/EOS-Community.git
cd eos-payment-terminal
npm install
npm start
```

## Build

```sh
//Codes
git clone https://github.com/Byzantine-Works/EOS-Community.git
cd eos-payment-terminal
npm install
npm run build
```

## Embed

```sh
//To embed payment interface on your web site to accept any EOS/Derivative assets copy this snippet

<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">
<div id="wallet" style="transform: translateY(150px); margin: 0 auto; width:700px"></div>
<script type="text/javascript" src="https://api.byzanti.ne/main.js"></script>

```

repository: Byzantine-Works/EOS-Community

gha_language: JavaScript

repo_name: Byzantine-Works/EOS-Community


text:
# Harvester

### Asynchronous Proxy/Address test and automation tool

### How to Install

```bash
npm install -d proxy_harvester
```

### How to use

* put your proxy list file into proxy directory
* put your address list file into address directory
* specify items in settings.js file for your needs
* run application below
* enjoy the colorful results

```bash
node app.js
```

### Author

**Erhan Gundogan**

+ http://twitter.com/erhangundogan
+ http://github.com/erhangundogan

License
---------------------

Copyright 2013 Erhan Gundogan

Licensed under the MIT License.

repository: erhangundogan/harvester

repo_name: erhangundogan/harvester


text:
## Random Forest :

Random forests or random decision forests are an ensemble learning method for classification, regression and other tasks that operates by constructing a multitude of decision trees at training time. For classification tasks, the output of the random forest is the class selected by most trees. For regression tasks, the mean or average prediction of the individual trees is returned.

#### Implementation :

```python
import numpy as np
from collections import Counter
from sklearn.model_selection import train_test_split
from sklearn.datasets import make_blobs
from DecisionTree import DecisionTree

class RandomForest:

    def __init__(self , nbr_trees ,min_Samples_to_Split = 2 , maximum_Depth = 100 , nbr_features = None):
        self.nbr_trees = nbr_trees
        self.min_Samples_to_Split = min_Samples_to_Split
        self.maximum_Depth = maximum_Depth
        self.nbr_features = nbr_features

    def fit(self , x, y):
        self.trees = []
        for i in range(self.nbr_trees):
            tree = DecisionTree(min_Samples_to_Split=self.min_Samples_to_Split , maximum_Depth=self.maximum_Depth , nbr_features=self.nbr_features)
            x_i , y_i = self.randomSubSet(x, y)
            tree.fit(x_i , y_i)
            self.trees.append(tree)

    def randomSubSet(self , x, y):
        nbr_samples = x.shape[0]
        indexes = np.random.choice(nbr_samples , nbr_samples , replace = True)
        return x[indexes] , y[indexes]

    def predict(self , x):
        trees_Predictions = np.array([t.predict(x) for t in self.trees])
        trees_Predictions = np.swapaxes(trees_Predictions, 0, 1)
        y_hat = np.array([Counter(t_Predictions).most_common(1)[0][0] for t_Predictions in trees_Predictions])
        return y_hat
```

#### Testing The Model :
```python
def accuracy(y_true , y_pred):
    return np.sum(y_true == y_pred ) / len(y_true)

x , y = make_blobs(n_samples=100 , n_features=10 , centers=10 , random_state=0)
x_train , x_test , y_train , y_test = train_test_split(x,y,test_size=0.1)

R_Forest = RandomForest(nbr_trees=10)
R_Forest.fit(x_train, y_train)
y_hat = R_Forest.predict(x_test)
print("Model Accuracy : ",accuracy(y_test, y_hat))
```


text:
# Furry Text
A monstrocity made by a human furry

## How to run it
Either run it as a python script/run the valac compiler or get the runnable .bin files from releases or from the next two links. [Python](https://github.com/SafyreLyons/F--ing-Furries/releases/download/1/main.bin) / [Vala](https://github.com/SafyreLyons/F--ing-Furries/releases/download/1.0/furries-python.bin) and write/paste a string in the test box and click the button. It ain't hard.

Sample output:

`some cool awesome text` to `sawme cawawll awesawme text (*꧆▽꧆*)`

----
Made by [Safyre Lyons](https://github.com/SafyreLyons)

repository: KaiLyons/Furry-Text

repo_name: KaiLyons/Furry-Text


text:
# react-postprocessing

![npm](https://img.shields.io/npm/v/react-postprocessing?label=npm%20package&style=flat-square) ![npm](https://img.shields.io/npm/dt/react-postprocessing?style=flat-square)

This is a [postprocessing](https://vanruesc.github.io/postprocessing) wrapper for [react-three-fiber](https://github.com/react-spring/react-three-fiber). This is not (yet) meant for complex orchestration of effects, but can save you [hundreds of LOC](https://twitter.com/0xca0a/status/1289501594698960897) for a straight forward effects-chain.

```bash
npm install postprocessing react-postprocessing
```

#### Why postprocessing and not three/examples/jsm/postprocessing?

From [https://vanruesc.github.io/postprocessing](https://vanruesc.github.io/postprocessing/#performance)

> This library provides an EffectPass which automatically organizes and merges any given combination of effects. This minimizes the amount of render operations and makes it possible to combine many effects without the performance penalties of traditional pass chaining. Additionally, every effect can choose its own blend function.
>
> All fullscreen render operations also use a single triangle that fills the screen. Compared to using a quad, this approach harmonizes with modern GPU rasterization patterns and eliminates unnecessary fragment calculations along the screen diagonal. This is especially beneficial for GPGPU passes and effects that use complex fragment shaders.

Postprocessing also supports srgb-encoding out of the box, as well as WebGL2 MSAA (multi sample anti aliasing), which is react-postprocessing's default, you get high performance crisp results w/o jagged edges.

#### What does it look like?

Well, you can do pretty much anything, but here's an example combining a couple of effects ([live demo](https://codesandbox.io/s/vigorous-currying-3r6l2)).

```jsx
import React from 'react'
import { EffectComposer, DepthOfField, Bloom, Noise, Vignette } from 'react-postprocessing'
import { Canvas } from 'react-three-fiber'

function App() {
  return (
    <Canvas>
      {/* Your regular scene contents go here, like always ... */}
      <EffectComposer>
        <DepthOfField focusDistance={0} focalLength={0.02} bokehScale={2} height={480} />
        <Bloom luminanceThreshold={0} luminanceSmoothing={0.9} height={300} />
        <Noise opacity={0.02} />
        <Vignette eskil={false} offset={0.1} darkness={1.1} />
      </EffectComposer>
    </Canvas>
  )
}
```

#### Documentation

[react-postprocessing exports](https://github.com/react-spring/react-postprocessing/blob/master/api.md)

[postprocessing docs](https://vanruesc.github.io/postprocessing/public/docs/)

repository: emmelleppi/react-postprocessing

repo_name: emmelleppi/react-postprocessing


text:
# Available Backends

In theory [all the restic backends](https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html) are supported.

Those tested are the following:

> ℹ You can also [specify the `env` variables in a config file](/backend/env) to separate them from the config file.

## Local

```yaml
backends:
  name-of-backend:
    type: local
    path: /data/my/backups
```

## Backblaze

```yaml
backends:
  name-of-backend:
    type: b2
    path: 'bucket_name'
    # Or With a path
    # path: 'bucket_name:/some/path'
    env:
      B2_ACCOUNT_ID: 'backblaze_keyID'
      B2_ACCOUNT_KEY: 'backblaze_applicationKey'
```

#### API Keys gotcha

If you use a _File name prefix_ when making the application key, do not include a leading slash. Make sure to include this prefix in the path (e.g. `path: 'bucket_name:my/path'`).

## S3 / Minio

```yaml
backends:
  name-of-backend:
    type: s3
    path: s3.amazonaws.com/bucket_name
    # Minio
    # path: http://localhost:9000/bucket_name
    env:
      AWS_ACCESS_KEY_ID: my_key
      AWS_SECRET_ACCESS_KEY: my_secret
```

## SFTP

For SFTP to work you need to use configure your host inside of ~/.ssh/config as password prompt is not supported. For more information on this topic please see the [official docs](https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#sftp) on the matter.

```yaml
backends:
  name-of-backend:
    type: sftp
    path: my-host:/remote/path/on/the/server
```

## Rest Server

See [here](https://github.com/restic/rest-server) for how to install a rest server backend and [here](https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#rest-server) for further documentation.

```yaml
backends:
  name-of-backend:
    type: rest
    path: http://localhost:8000/repo_name
    # Or authenticated
    path: https://user:pass@host:6969/path
```

Optionally you can set user and password separately

```yaml
backends:
  rest:
    type: rest
    path: http://localhost:6969/path
    key: ...
    rest:
      user: user
      password: pass
```

> :ToCPrevNext

repository: cupcakearmy/autorestic

repo_name: cupcakearmy/autorestic


text:
# Task
Submit a Pull Request to this file, checking off your name, and adding your GitHub username. Feel free to add some :rocket: emoji as well :smiley: !

## Formatting
This is a Markdown document (note the .md file name), so you'll need to use [proper Markdown formatting](https://help.github.com/articles/basic-writing-and-formatting-syntax/#task-lists).

In the code, you'll see `- [ ]` you'll need to add an X like so `- [X]` to check off your name.

## Pull Request etiquette
Make the Pull Request from your own GitHub account. Make sure you're changing the file in _my repo_ (not your fork). I suggest you @mention me (@joewadcan) in the Pull Request, so we can chat and fix any issues that come up.

repository: joewadcan/FirstPullRequest

repo_name: joewadcan/FirstPullRequest


text:
# ini_config

#### Table of Contents

1. [Description](#description)
1. [Setup - The basics of getting started with ini_config](#setup)
    * [What ini_config affects](#what-ini_config-affects)
    * [Setup requirements](#setup-requirements)
    * [Beginning with ini_config](#beginning-with-ini_config)
1. [Usage - Configuration options and additional functionality](#usage)
1. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
1. [Limitations - OS compatibility, etc.](#limitations)
1. [Development - Guide for contributing to the module](#development)

## Description

Ever wanted a way to manage an entire INI configuration file and didn't want to
subclass `puppetlabs/inifile` to let you force purge? Well, now you're in luck!
This rather simple utility module is just what you need.

## Setup

`puppet module tykeal-ini_config`

## Usage

`ini_config` consists of a single define. At the most basic you're going to pass
in a hash of the ini file that you want built up. For instance, the following
will get you an almost empty configuration file. The only thing in it will be a
header comment of `; MANAGED BY PUPPET` and a few empty lines

```puppet
ini_config { '/etc/my_config.ini':
}
```
That's not all that interesting though, here's a much more interesting example:

```puppet
ini_config { /etc/my_config.in':
  config              => {
		'testsection'     => {
			'testvar1'      => 'testvar1',
      'testvar2'      => [ 'testvar2.1', 'testvar2.2' ],
		},
		'testsection.sub' => {
      'testvar3'      => 'testvar3',
		},
	},
}
```

Which will produce the following ini file

```ini
; MANAGED BY PUPPET

[testsection]
	testvar1 = testvar1
	testvar2 = testvar2.1
	testvar2 = testvar2.2

[testsection "sub"]
	testvar3 = testvar3
```

## Reference

  * `ensure`
		Ensure if the file is present or absent

		**Type**: Enum - `present`, `absent`

		**Default**: `present`

	* `config_file`
		Absolute path to the file to manage.

		NOTE: If not set then the resource title will be used for the file to
		manage. If this is set it takes precedence over the resource title.

		**Type**: String

		**Default**: Empty

	* `config`
		A hash detailing the ini configuration that needs to be managed.

		The hash schema is as follows:

		```puppet
		$config         => {
			<OPTIONTITLE> => {
				<OPTIONKEY> => <OPTIONVALUE>
			}
		}
		```

		```
		OPTIONTITLE ::= <STRING> | <STRING>"."<STRING>
		OPTIONKEY   ::= <STRING>
		OPTIONVALUE ::= <STRING> | [ <STRING>, <STRING>, ... ]
		```

		The `OPTIONTITLE` may containg a single "subsection" which is separated by a
		`.`

		**Type**: Hash

		**Default**: `{}`

	* `mode`
		The file mode octal to set

		**Type**: String matching pattern `^[0-7]{4}$`

		**Default**: `0440`

	* `owner`
		The owner of the file

		**Type**: String

		**Default**: `root`

	* `group`
		The group of the file

		**Type**: String

		**Default**: `root`

	* `quotesubsection`
		Boolean to determine if the the subsection title should be place inside `"`
		or not. Some ini-like systems cannot handle this and others require it.

		**Type**: Boolean

		**Default**: `true`

	* `indentoptions`
		Boolean to determine if the options of a section should be tab indented or
		not. Some ini-like systems cannot handle starting white space on their
		configuration lines

		**Type**: Boolean

		**Default**: `true`

	* `show_diff`
		Boolean to determine if the diff should be reported on a puppet
        run that changes the file contents

		**Type**: Boolean

		**Default**: `true`

## Limitations

While this module is flagged as only operating on RedHat and CentOS systems it
should work on any system as it is extremely basic

## Development

Do you want to contribute? Please fork on github and send a PR!


text:
#An answer to the most material objections made by the Linnen-Drapers, against the bill which restrains the wearing East-India wrought silks, &c. in England; humbly submitted to the consideration of the most honourable House of Lords.#
An answer to the most material objections made by the Linnen-Drapers, against the bill which restrains the wearing East-India wrought silks, &c. in England; humbly submitted to the consideration of the most honourable House of Lords.

##General Summary##

**Links**

[TCP catalogue](http://www.ota.ox.ac.uk/tcp/)  •
[HTML](http://tei.it.ox.ac.uk/tcp/Texts-HTML/free/B17/B17161.html)  •
[EPUB](http://tei.it.ox.ac.uk/tcp/Texts-EPUB/free/B17/B17161.epub) •
[Page images (Historical Texts)](https://historicaltexts.jisc.ac.uk/eebo-99885970e)

**Availability**

This keyboarded and encoded edition of the work described above is co-owned by the
    institutions providing financial support to the Early English Books Online Text Creation
    Partnership. This text is available for reuse, according to the terms of  Creative Commons 0 1.0 Universal
    licence. The text can be copied, modified, distributed and performed, even for commercial
    purposes, all without asking permission.

**Major revisions**

1. __2014-02 __ __SPi Global__ *Keyed and coded from ProQuest page images *
1. __2014-04 __ __Kate Allen __ *Sampled and proofread *
1. __2014-04 __ __Kate Allen__ *Text and markup reviewed and edited *
1. __2015-03 __ __pfs__ *Batch review (QC) and XML conversion *
1. __2021-05 __ __lb__ *TEI P5 conversion *

##Content Summary##

#####Body#####

1. AN ANSWER TO THE Most Material Objections Made by the LINNEN-DRAPERS, Against the Bill which restrains the Wearing East-India wrought Silks, &c. in England; Humbly Submitted to the Consideration of the Most Honourable House of Lords.

#####Back#####
An ANSWE•… TO THE Most Material Objecti•… Made by the Linnen-Dra•… against the Bill which〈…〉strains
**Types of content**

  * Oh, Mr. Jourdain, there is **prose** in there!

There are 6 **omitted** fragments!
 @__reason__ (6) : illegible: right margin cropped or obscured (6)  •  @__resp__ (6) : #murp (6)  •  @__extent__ (6) : 1+ letters (5), 1 span (1)

**Character listing**

|Text|string(s)|codepoint(s)|
|---|---|---|
|General Punctuation|•…|8226 8230|
|CJKSymbolsandPunctuation|〈〉|12296 12297|

##Tag Usage Summary##

###Header Tag Usage###

|No|element name|occ|attributes|
|---|---|---|---|
|1.|__availability__|1||
|2.|__biblFull__|1||
|3.|__change__|5||
|4.|__date__|7| @__when__ (1) : 2016-02 (1)|
|5.|__editorialDecl__|1||
|6.|__encodingDesc__|1||
|7.|__extent__|2||
|8.|__fileDesc__|1||
|9.|__idno__|8| @__type__ (8) : DLPS (1), EEBO-CITATION (1), VID (1), EEBO-PROQUEST (1), STC (3), PROQUEST (1)|
|10.|__keywords__|1| @__scheme__ (1) : http://authorities.loc.gov/ (1)|
|11.|__label__|5||
|12.|__langUsage__|1||
|13.|__language__|1| @__ident__ (1) : eng (1)|
|14.|__listPrefixDef__|1||
|15.|__note__|6||
|16.|__notesStmt__|2||
|17.|__p__|11||
|18.|__prefixDef__|2| @__ident__ (2) : tcp (1), char (1)  •  @__matchPattern__ (2) : ([0-9\-]+):([0-9IVX]+) (1), (.+) (1)  •  @__replacementPattern__ (2) : http://eebo.chadwyck.com/downloadtiff?vid=$1&page=$2 (1), https://raw.githubusercontent.com/textcreationpartnership/Texts/master/tcpchars.xml#$1 (1)|
|19.|__profileDesc__|1||
|20.|__projectDesc__|1||
|21.|__pubPlace__|2||
|22.|__publicationStmt__|2||
|23.|__publisher__|2||
|24.|__ref__|4| @__target__ (4) : https://creativecommons.org/publicdomain/zero/1.0/ (1), http://www.textcreationpartnership.org/docs/. (1), https://textcreationpartnership.org/faq/#faq05 (1), https://github.com/textcreationpartnership (1)|
|25.|__relatedItem__|1| @__type__ (1) : facs (1)  •  @__target__ (1) : https://data.historicaltexts.jisc.ac.uk/view?pubId=eebo-99885970e (1)|
|26.|__revisionDesc__|1||
|27.|__seriesStmt__|1||
|28.|__sourceDesc__|1||
|29.|__term__|4| @__type__ (4) : corporate_name (1), topical_term (2), geographic_name (1)|
|30.|__textClass__|1||
|31.|__title__|3||
|32.|__titleStmt__|2||

###Text Tag Usage###

|No|element name|occ|attributes|
|---|---|---|---|
|1.|__back__|1||
|2.|__body__|1||
|3.|__desc__|6||
|4.|__div__|2| @__type__ (2) : response (1), docket_title (1)|
|5.|__g__|14| @__ref__ (14) : char:EOLhyphen (14)|
|6.|__gap__|6| @__reason__ (6) : illegible: right margin cropped or obscured (6)  •  @__resp__ (6) : #murp (6)  •  @__extent__ (6) : 1+ letters (5), 1 span (1)|
|7.|__head__|1||
|8.|__hi__|83||
|9.|__p__|10||
|10.|__pb__|4| @__facs__ (4) : tcp:186337:1 (2), tcp:186337:2 (2)|


text:
# Matrix Video Chat

Testbed for full mesh video chat.

## Getting Started

You must first run a local Synapse server on port 8008

Then install the dependencies:

```
cd matrix-video-chat
npm install
```

Locally checkout the [robertlong/full-mesh-voip](https://github.com/matrix-org/matrix-js-sdk/tree/robertlong/full-mesh-voip) branch of the matrix-js-sdk.

```
cd matrix-js-sdk
git checkout robertlong/full-mesh-voip
yarn
yarn build
npm link
```

Link the matrix-js-sdk into the matrix-video-chat project:

```
cd matrix-video-chat
npm link matrix-js-sdk
```

Finally run the development server

```
npm run dev
```


text:
# BlockFetchingListener

`BlockFetchingListener` is an [extension](#contract) of the `EventListener` ([Java]({{ java.api }}/java/util/EventListener.html)) abstraction that want to be notified about [block fetch success](#onBlockFetchSuccess) and [failures](#onBlockFetchFailure).

`BlockFetchingListener` is used to create a [OneForOneBlockFetcher](../storage/OneForOneBlockFetcher.md), `OneForOneBlockPusher` and [RetryingBlockFetcher](RetryingBlockFetcher.md).

## Contract

###  onBlockFetchFailure

```java
void onBlockFetchFailure(
  String blockId,
  Throwable exception)
```

###  onBlockFetchSuccess

```java
void onBlockFetchSuccess(
  String blockId,
  ManagedBuffer data)
```

## Implementations

* "Unnamed" in [ShuffleBlockFetcherIterator](../storage/ShuffleBlockFetcherIterator.md#sendRequest)
* "Unnamed" in [BlockTransferService](../storage/BlockTransferService.md#fetchBlockSync)
* [RetryingBlockFetchListener](RetryingBlockFetcher.md#RetryingBlockFetchListener)

repository: japila-books/apache-spark-internals

repo_name: japila-books/apache-spark-internals


text:
# Cloud Foundry Node.js Buildpack v2

[![CF Slack](https://www.google.com/s2/favicons?domain=www.slack.com) Join us on Slack](https://cloudfoundry.slack.com/messages/buildpacks/)

A Cloud Foundry [buildpack](http://docs.cloudfoundry.org/buildpacks/) for Node based apps, composed of [Cloud Native Buildpacks](https://buildpacks.io/).

### Buildpack User Documentation

Official buildpack documentation can be found at [node buildpack docs](http://docs.cloudfoundry.org/buildpacks/node/index.html).

### Building the Buildpack for Use in Cloud Foundry

To build this buildpack, run the following commands from the buildpack's directory:

1. Source the .envrc file in the buildpack directory.

   ```bash
   $ source .envrc
   ```
   To simplify the process in the future, install [direnv](https://direnv.net/) which will automatically source .envrc when you change directories.

1. Install Go, if it is not already installed

    ```bash
    $ ./scripts/install_go.sh
    ```

1. Install the packaging tools

    ```bash
    $ ./scripts/install_shim_tools.sh
    ```

1. Build the buildpack, using [cnb2cf](https://github.com/cloudfoundry/cnb2cf#usage)

    ```bash
   $ cnb2cf package -stack <stack> [-cached] [-version <version>] [-cachedir <path to cachedir>]
    ```

1. Use in Cloud Foundry

   Upload the buildpack to your Cloud Foundry and optionally specify it by name

    ```bash
    $ cf create-buildpack [BUILDPACK_NAME] [BUILDPACK_ZIP_FILE_PATH] 1
    $ cf push my_app [-b BUILDPACK_NAME]
    ```

### Testing

Buildpacks use the [Cutlass](https://github.com/cloudfoundry/libbuildpack/tree/master/cutlass) framework for running integration tests.

To test this buildpack, run the following command from the buildpack's directory:

1. Source the .envrc file in the buildpack directory.

   ```bash
   $ source .envrc
   ```
   To simplify the process in the future, install [direnv](https://direnv.net/) which will automatically source .envrc when you change directories.

1. Install Go, if it is not already installed

    ```bash
    $ ./scripts/install_go.sh
    ```

1. Run integration tests

   Buildpacks use the [Cutlass](https://github.com/cloudfoundry/libbuildpack/tree/master/cutlass) framework for running integration tests against Cloud Foundry. Before running the integration tests, you need to login to your Cloud Foundry using the [cf cli](https://github.com/cloudfoundry/cli):

    ```bash
    $ cf login -a https://api.your-cf.com -u<EMAIL_ADDRESS>-p pa55woRD
    ```

   Note that your user requires permissions to run `cf create-buildpack` and `cf update-buildpack`.

   To run the integration tests, run the following command from the buildpack's directory:

    ```bash
    $ ./scripts/integration.sh
    ```
### Contributing

Find our guidelines [here](./CONTRIBUTING.md).

### Help and Support

Join the #buildpacks channel in our [Slack community](http://slack.cloudfoundry.org/).

### Reporting Issues

[Open an issue](https://github.com/cloudfoundry/nodejs-cnb/issues/new) on this project.

### Active Development

The project backlog is on [Pivotal Tracker](https://www.pivotaltracker.com/projects/1042066).


text:
# Formspree React

The React component library for [Formspree](https://formspree.io).

## Help and Support

For help and support please see [the Formspree React docs](https://help.formspree.io/hc/en-us/articles/360055613373).

repository: gazpachu/formspree-react

repo_name: gazpachu/formspree-react


text:
## Paying Taxes
https://www.baylor.edu/globalengagement/index.php?id=962296

## Form 1098-T
https://www.baylor.edu/sfs/index.php?id=936966

With a 1098-T, the business — your college — reports how much qualified tuition and expenses you (or your parents) paid it
during the tax year. The IRS uses these forms to match data from information returns to income, deductions and credits
reported on individual income tax returns.Dec 4, 2019

No, you don't have to report your 1098-T, not unless you want to claim an education credit. However if your
grant/scholarship amount (box 5) is more than your tuition (box 1/box 2) you may want to report it because
excess scholarship money may be treated as taxable income on your return.

## Form 8843
https://www.baylor.edu/globalengagement/index.php?id=962297

All individuals in F-1, F-2, J-1, or J-2 nonimmigrant status must file Form 8843 also called the “Statement for
Exempt Individuals and Individuals with a Medical Condition" even if they received NO income during the past
year and regardless of their age. You may have to file Form 8843 and an Income Tax Return as well.
Form 8843 must be filed if an individual is:

present in the U.S. during the previous year,
a non-resident alien, and
present in the U.S. under F-1, F-2, J-1, or J-2 status.

## Form W-2
The IRS requires employers, like Baylor, to report wage and salary information for employees on Form W-2.
Your W-2 also reports the amount of federal, state and other taxes withheld from your paycheck.
Baylor is required to make the W-2 available no later than January 31st of each year. You may download
it from Bearweb or you may go to the Payroll Office to pick-up a copy. If you worked for Baylor and did
not receive a W-2, you should contact the Baylor Payroll Office at<PHONE_NUMBER>. If you worked for any
other company and it has not been mailed to you, you should contact that company's payroll office. Some
indiviudals who receive a W-2 may also receive a Form 1042-S (see below)

## Form 1042-S
Form 1042-S is a special tax form for non-residents such as international students and scholars who are reporting
income from a United States-based source, such as Baylor University. Baylor will mail you this form at the end of
February or you may go to the Payroll Office to pick it up. You may receive a 1042-S Form if you are a graduate
student who can claim a tax treaty and you worked for a department and received a stipend. You also might
receive this form if you are an athlete who received a Baylor scholarship. Some individuals who receive a 1042-S
may also receive a W-2.

Please note – If you are from a treaty country and your earnings did not go over the treaty limit,
you will only have a 1042-S form, and no W-2 form.  If your earnings did go over the treaty limit,
you will have both a W-2 form and a 1042-S form.

Baylor University has arranged free access to Sprintax Tax Preparation for you. Sprintax will guide you through the tax preparation process, arrange the necessary documents and check if you are due a tax refund.  Sprintax will include Form 8843 as part of your tax returns.

If you are filing as a non-resident (meaning you have been in the U.S. less than 5 years), DO NOT use other services such as Turbo Tax or H&R Block.
Sprintax was used by over 165,000 international students and scholars last year, and the average Federal refund received by eligible students was over $1,087.
All you need to do is using this link

https://www.sprintax.com/?utm_ref=baylor&utm_cprmc

Register and follow the simple instructions
Complete the online questionnaire
Enter your unique code "" in the box on the ‘Review your order’ page
Sprintax will prepare your tax return

repository: minweny/programmingNotes

repo_name: minweny/programmingNotes