text:
---
title: 3DS MPI - API Reference

language_tabs: # must be one of https://git.io/vQNgJ
  - shell

toc_footers:
  - Sign Up for a Key

includes:
    - eci_codes
    - errors

search: true
---

# Introduction

Welcome to the 3DS-MPI API! You can use our API to access 3DS-MPI API endpoints, which can get you started with 3DS authentication and other resources in the MPI.

We have language bindings in Shell, You can view examples in the dark area to the right.

# Authentication
> To authorize, use this code:

```shell
# With shell, you can just pass the correct header with each request
curl POST "https://3ds-mpi.placetopay.com"
  -H "Authorization: Bearer YourApiKeyHere"
```

3DS-MPI uses API keys to authenticate requests.

3DS-MPI expects for the API key to be included in all API requests to the server in a header that looks like the following:

`Authorization: Bearer YourApiKeyHere`

You must replace YourApiKeyHere with your personal API key.

# Making Requests

The first thing you need to know is what API URL endpoint to use:

- MPI URL: use [https://3ds-mpi.placetopay.com](https://3ds-mpi.placetopay.com)

When you write your own 3DS-MPI client, please keep the following in mind:

- Always set the __Accept__ header to `application/json`.

- Always set the __Content-Type__ header to `application/json`.

- Always set the __Authorization__ header to `Bearer YourApiKeyHere`.

- Client libraries will usually set these headers automatically.

# LookUpRequest

The _LookUpRequest_ is responsible for initiating user authentication.

You must use the _LookUpRequest_ right after you have captured the payment information, which must contain the final amount of the transaction and the credit card information.

The response message returned by the MPI contains information about the enrollment of the card in 3DS.

## LookupRequest Object

> Example of **Basic** LookupRequest Object:

```json
{
    "pan":<PHONE_NUMBER>111111,
    "expiration_year": 2029,
    "expiration_month": 4,
    "amount": 23999.69,
    "currency": "USD",
    "redirect_uri": "https://www.merchanturl.com"
}
```

> Example of **Advanced** LookupRequest Object:

```json
{
    "pan":<PHONE_NUMBER>111111,
    "expiration_year": 2029,
    "expiration_month": 4,
    "amount": 23999.69,
    "currency": "USD",
    "redirect_uri": "https://www.merchanturl.com",
    "installments": 3,
    "recurrence": true,
    "recurrence_frequency": 20,
    "recurrence_expiration": "20201122",
    "locale": "en",
    "disable_redirect": false
}
```

The object contains information about the payment that is being processed, the information is required in order to get information about the credit card in 3DS.

### Arguments

Parameter | Type | Required | Description
--------- | ------- | ----------- | ----------
pan | integer | true | Credit card number
expiration_year | integer | true | Card's expiration year YYYY
expiration_month | integer | true | Card's expiration month MM
amount | number | true | The amount of the transaction
currency | string | true | ISO 4217 alpha code of the currency
redirect_uri | string | true | Return url
installments | number | false | Payment installments
recurrence | boolean | false | Is recurrence enabled?
recurrence_frequency | boolean | false | Days between recurrence
recurrence_expiration | string | false | Expiration date of recurrence
locale | string | false | Localization language
disable_redirect | boolean | false | Disable MPI Redirect Handling

#### Notes

- `redirect_uri` Consumer Url, the user will return to this url once the authentication process is finished.

- `installments` If applicable, the amount of installments selected for payment.

- `recurrence` If applicable, is recurrence enabled for the payment?

- `recurrence_frequency` required if recurrence is enabled, the amount of days between each recurrence.

- `recurrence_expiration` required if recurrence is enabled, format must be YYYYMMDD.

- `locale` Localization language to be used in messages, choose from `es|en`.

- `disable_redirect` if `true`,  the MPI will not handle the automatic redirection to the ACS. The API will return the necessary data for the consumer to make the post form.

## LookupResponse Object

> Example of LookupResponse Object:

```json
{
    "enrolled": "Y",
    "redirect_url": "https://3ds-mpi.placetopay.com/authenticate/veryLargeUrl",
    "transaction_id": 1018
}
```

> Example Response (200), with `disable_redirect` as `true`

```json
{
    "enrolled": "Y",
    "acs_url": "https://www.example-acs-url.com/path/auth",
    "pa_req": "veryLargeCompressedPaReqToBeSent",
    "term_url": "http://www.exmaple-mpi-url.com/authenticate/callback/veryLargeUrl",
    "md": "merchantExtraData",
    "transaction_id": 1242
}
```

### Arguments

Parameter | Type  | Description
--------- | ------- | ----------- | ----------
enrolled | string  | Credit card enrollment status.
redirect_url | string | MPI Url, user must visit to continue with 3DS authentication.
transaction_id | integer | MPI transaction Id.
eci_flag | number | Given ECI flag for the transaction.
acs_url | string  | if if `disable_redirect` was `true`. The original ACS Url to continue with 3DS authentication.
pa_req | string | if `disable_redirect` was `true`. Compressed payer authentication request.
term_url | string | if `disable_redirect` was `true`. Terminal Url, a MPI url.
md | string | if `disable_redirect` was `true`. Merchant data, additional data.

#### Notes

- `enrolled` Enrollment status one of `Y|N|U`. If `Y` the user can be authenticated.

    - `Y` Authentication is available.

    - `N` Authentication is not available.

    - `U` Unable to know if authentication is available.

- `redirect_url` Present if `enrolled` is `Y`, MPI Url that handles the required action for the user to continue with the authentication process.

- `transaction_id` MPI transaction identifier.

- `eci_flag` Present if `enrolled` is `N` or `U`, The *Electronic Commerce Indicator* indicates the level of security and the result of the 3D Secure authorization. See [Eci Codes](#eci-codes)

- `acs_url` Present if `disable_redirect` was `true` & `enrolled` is `Y`. Contains the URL of the card issuer authentication site (bank).

- `pa_req` Present if `disable_redirect` was `true` & `enrolled` is `Y`. Contains information that must be posted with the authentication form.

- `term_url` Present if `disable_redirect` was `true` & `enrolled` is `Y`, Contains information that must be posted with the authentication form.

- `md` Present if `disable_redirect` was `true` & `enrolled` is `Y`, Contains information that must be posted with the authentication form.

## LookupRequest

> Example Request:

```shell
curl "https://3ds-mpi.placetopay.com/api/lookup" \
    -X POST \
    -H "accept: application/json" \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer yourApiKey" \
    -d {"pan":4111111111111111,"expiration_year":2029,"expiration_month":4,"amount":23999.69,"currency":"USD","redirect_uri":"https://www.merchanturl.com","installments":3,"recurrence":true,"recurrence_frequency":20,"recurrence_expiration":"20201122","locale":"en","disable_redirect":false}
```

> Example Response (200):

```json
{
    "enrolled": "Y",
    "redirect_url": "https://3ds-mpi.placetopay.com/authenticate/veryLargeUrl",
    "transaction_id": 1018
}
```

LookUp credit card information in 3DS.

`POST http://example.com/api/lookup`

see [LookupRequest Object](#lookuprequest-object)

## Handle LookupResponse

Verify the `enrolled` parameter in `LookupResponse` and proceed as:

### Authentication not available, `enrolled` is`U`

The enrollment of the card in 3DS could not be verified. It can happen due to some problem in the internal systems of 3DS.

You can proceed without 3DS.

### Authentication not available, `enrolled` is`N`

The card is not enrolled in 3DS.

You can proceed without 3DS.

### Authentication is available, `enrolled` is`Y`

The card is enrolled in 3DS and the cardholder can be authenticated.

The card holder must be redirected to the url given in the `LookupResponse` as `redirect_url`. The MPI will handle the required actions
in order to continue with the authentication process

> Example Post Form when `disable_redirect` is `true`.

```html
    <form method="POST" action="{{ $response['acs_url'] }}">
        <input type="hidden" name="PaReq" value="{{ $response['pa_req'] }}">
        <input type="hidden" name="TermUrl" value="{{ $response['term_url'] }}">
        <input type="hidden" name="MD" value="{{ $response['md'] }}">

        <noscript>
            <div>
                <h2>JavaScript is currently disabled or is not supported by your browser</h2>
                <p>Please continue with the process manually</p>
                <button type="submit" class="button">Continue'</button>
            </div>
        </noscript>
    </form>
```

    If you used disable_redirect parameter as true then you have to handle the post form as follows:

Collect the data given in LookupResponse and send a new web form using the cardholder browser.

An example of the post web form is given here.

The user will go through the authentication process and will be redirected to the url that the consumer sent in `LookupRequest.redirect_uri`.

Once the user visits the merchant Url (`LookupRequest.redirect_uri`), The authentication process can be treated as finished.
The merchant must use `GetTransactionStatus` to get information about the 3DS authentication process.

# TransactionStatus

The *TransactionStatus* object gives information about the results of 3DS authentication in a transaction

You must use the _GetTransactionStatus_ right after the user completed the authentication process and returned to the merchant page.

## TransactionStatus Object

> Example of TransactionStatus Object:

```json
{
    "authentication_status": "Y",
    "validated_signature": true,
    "eci": "05",
    "xid": "3030303030303030303030303030303030303032",
    "cavv": "0000020777351815352670947035181300000000"
}
```

### Arguments

Parameter | Type  | Description
--------- | ------- | ----------- | ----------
authentication_status | string  | Authentication Status on 3DS
validated_signature | boolean | Has the signature of the messages been validated?
eci | integer | Given ECI flag for the transaction.
xid | number | Transaction identifier resulting from the authentication process.
cavv | number  | Cardholder Authentication Verification Value (CAVV)

- `authentication_status`  Authentication Status on 3DS one of `Y|A|N|U`.

    - `Y` Successful Authentication.

    - `A` Successful Attempt.

    - `N` Authentication is not available.

    - `U` Unable to know if authentication is available.

- `validated_signature` When communicating with the ACS, message signatures must be validated, this parameter indicates the result of that validation..

- `eci` The *Electronic Commerce Indicator* indicates the level of security and the result of the 3D Secure authorization. See [Eci Codes](#eci-codes)

## Get Transaction Status

> Example Request:

```shell
curl "https://3ds-mpi.placetopay.com/api/transactions/1039" \
    -X GET \
    -H "accept: application/json" \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer yourApiKey" \
```

> Example Response (200):

```json
{
    "authentication_status": "Y",
    "validated_signature": true,
    "eci": "05",
    "xid": "3030303030303030303030303030303030303032",
    "cavv": "0000020777351815352670947035181300000000"
}
```

Get the status of a transaction in 3DS.

`GET http://example.com/api/transactions/{id}`

### Parameters

Parameter | Type  | Description
--------- | ------- | ----------- | ----------
id | number  | Transaction Id, given in `LookupResponse`

## Handle TransactionStatus

Verify the `authentication_status` parameter in `TransactionStatus` and proceed as:

Authentication Status | Signature  | Description
--------- | ------- | ----------- | ----------
Y | true  | Authentication Successful
A | true  | Merchant attempted to authenticate the cardholder.
N | true  | Failed Authentication
U | true  | Could not be authenticated
Y,A,N,U | false  | Untrusted results


text:
# V1 List Settlements Request Status

## Enumeration

`V1 List Settlements Request Status`

## Fields

| Name |
|  --- |
| `SENT` |
| `FAILED` |

repository: square/square-python-sdk

branch_name: refs/heads/master

extension: md

gha_language: Python

gha_license_id: NOASSERTION

license_type: permissive

repo_name: square/square-python-sdk


text:
# Docker-twisted

## Features

- Minimal, built with latest official Alpine base image.
- Multi-arch, built upon all the architectures that the base image offers.
- SSL support, easy to work with self-signed certificates.

## Installation

```bash
$ docker pull niiiklaus/twisted:latest
```

## Usage

### Parameters

We always recommend you to use Docker containers in normal user for safety reason.

If you use HTTPS, the start script will look for `/certs/app.key` and `/certs/app.crt` by default. You can change the target file names using environment variables, but don't forget to map the volume where your certificate files stored to the container.

|         Parameter          |                           Function                           |
| :------------------------: | :----------------------------------------------------------: |
|   `-u $(id -u):$(id -g)`   |              User mapping (always recommended).              |
|       `-p 6080:6080`       |                          HTTP port.                          |
|       `-p 6443:6443`       | HTTPS port (listened if you map certificate files correctly). |
|   `-v /path/to/app:/app`   |         The directory where the web service starts.          |
| `-v /path/to/certs:/certs` |        The directory where certificate files stored.         |
|  `-e KEY_FILE=custom.key`  | The start script will look for `/certs/custom.key` instead of `/certs/app.key`. |
|  `-e CRT_FILE=custom.crt`  | The start script will look for `/certs/custom.crt` instead of `/certs/app.crt`. |

### Examples

#### One-time basic HTTP service

```bash
docker run -it --rm \
  -u $(id -u):$(id -g) \
  -p 6080:6080 \
  niiiklaus/twisted:latest
```

#### Constant HTTP service with HTTPS

Sometimes SSL raises an error due to time reasons, so read-only mapping `/etc/localtime` and `/etc/timezone` may be necessary.

```bash
docker run -itd \
  -u $(id -u):$(id -g) \
  -p 6080:6080 \
  -p 6443:6443 \
  -v /etc/localtime:/etc/localtime:ro \
  -v /etc/timezone:/etc/timezone:ro \
  -v /path/to/app:/app \
  -v /path/to/certs:/certs:ro \
  -e KEY_FILE="KEY_FILE_NAME.key" \
  -e CRT_FILE="CRT_FILE_NAME.crt" \
  niiiklaus/twisted:latest
```

license: MIT

repository: NiiiKlaus/docker-twisted

repo_name: NiiiKlaus/docker-twisted


text:
---
layout: post
title: Binding to the Window Title in UWP
date: 2017-07-28
comments: true
published: true
categories: ["post"]
tags: [".Net", "UWP", "Binding", "XAML"]
author: Nico Vermeir
---
I was recently in a scenario where I had a UWP app with a timer. The running timer was supposed to be displayed in the title bar of the app (the app is a UWP app that will run only on laptops). To my surprise, this wasn't possible out of the box. We can set a title but we can't bind to it, since the title property cannot be accessed in XAML.

### The default way to set the title

Setting the title is very much the same workflow as setting the title bar's color, or the buttons in the title bar.

```csharp
var window = ApplicationView.GetForCurrentView();
window.Title = "Hello World!";
```

When you run this, you'll notice that the window's title bar says "Hello World - AppName". No matter what you set the title as, the system will always append the appname to it.

Now, how to get this into a binding? The answer is through an attached property.

### Attached Properties

So, what are attached properties? Attached properties are a form of global properties that can be set on a XAML element. An example of attached properties that you have no doubt used are *Grid.Row* and *Grid.Column*. Custom attached properties are often used when you want to expose a property in XAML. Exactly what we want to do here.

### Creating the Attached Property

To create an attached property you'll need a static class and a special form of Dependency Property. Instead of calling *DependencyProperty.Register*, we need to call *DependencyProperty.RegisterAttached*. Another difference is the underlying property. Instead of an actual property we need to write two methods, something that will look familiar to those that know a bit of Java. The naming of those methods are important since Attached Properties are convention based.

Here's the full example

```csharp
public static class PageExtensions
{
    public static readonly DependencyProperty TitleProperty =
        DependencyProperty.RegisterAttached("Title", typeof(string),
            typeof(PageExtensions),
            new PropertyMetadata(string.Empty, OnTitlePropertyChanged));

    public static string GetTitle(DependencyObject d)
    {
        return d.GetValue(TitleProperty).ToString();
    }

    public static void SetTitle(DependencyObject d, string value)
    {
        d.SetValue(TitleProperty, value);
    }

    private static void OnTitlePropertyChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
    {
        string title = e.NewValue.ToString();
        var window= ApplicationView.GetForCurrentView();
        window.Title = title;
    }
}
```

The actual logic of setting the window title happens in the property changed event handler.

### Binding to the property

Final step, time to see if this actually works!

I've added a string property in my MainPage.xaml.cs.

```csharp
public sealed partial class MainPage : Page
{
    public string WindowTitle { get; set; }

    public MainPage()
    {
        InitializeComponent();

        WindowTitle = "Hello World!";
    }
}
```

Very simple example here, but enough to show the gist of it. Next, in MainPage.xaml we can add the binding (extra lines omitted for clarity)

```xml
<Page x:Class="App10.MainPage"
      ...
      xmlns:local="using:App10"
      local:PageExtensions.Title="{x:Bind WindowTitle}"
      mc:Ignorable="d">
```

Run the app, and the value of the string property should be set as the window title! (Note: I used x:Bind here, so no need to set the DataContext, it's always the code-behind)

### Conclusion

In this article I've shown how I tackled a problem that I ran into this week, binding a viewmodel property to the window title in a UWP app. In the real application I've used a TimeSpan to bind to the window title, it goes up every second and the title is refreshed every second as well.

Happy coding!

extension: markdown


text:
# FoundationDB java test application

This is my first attempt at talking to FoundationDB via Java.

It uses gradle as the build system and creates an uber jar by calling the gradle assemble task.

After you have built the project then type
> java -jar fdbtest-1.0-SNAPSHOT-all

to run the program. Of course this does assume that an instance of FoundationDB is running on the host.

If you know Python then you can't go wrong by using Python and interacting with the Python REPL. I don't know Python, hence this project.

The source code has been lifted from the javadocs for the java client for FoundationDB 5.1.7.

This was tested on Windows 10, with JDK 1.8.0_171.

repository: ajazam/FoundationDBTest

repo_name: ajazam/FoundationDBTest


text:
# awesome-thanos
An awesome collection of Thanos inspired algorithms and repositories.
Feel free to contribute.

## Algorithms

* [Thanos Sort](https://gist.github.com/findoslice/4a83d2077fc6e55ed288c592593dbfa9) - A quick implementation of the thanos sort algorithm, removing half of the array's elements at a time until the array is sorted by [Findlay Smith](https://gist.github.com/findoslice).

## Libraries

* [Thanos JS](https://github.com/anandundavia/thanos-js) - Use the Thano's powers to reduce the size of your Project by [Anand Undavia](https://github.com/anandundavia).

## Misc

* [Thanos Dust](https://github.com/lichking24/Thanos_Dust) - As Thanos making a snap with the Infinite Gauntlet, half the heros vanish to dust. As using the time stone, people come back.

## License

[![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0/)

To the extent possible under law, [Alfredo Salzillo](https://www.linkedin.com/in/alfredosalzillo/) has waived all copyright and related or neighboring rights to this work.

repository: alfredosalzillo/awesome-thanos

repo_name: alfredosalzillo/awesome-thanos


text:
---
layout: post
title: Quake Books
tag: misc
---

Coined by [Tyler Cowen](https://marginalrevolution.com/marginalrevolution/2007/11/view-quake-read.html):

> My reading was much different when I was younger. I would more likely intensively engage with some important book totally full of new ideas. Hayek. Parfit. Plato. And so on. There just aren’t books like that left for me anymore. So I read many more, to learn bits, but haven’t in years experienced a "view quake." That is sad, to me at least, but I don’t know how to avoid how that has turned out. So enjoy your best reading years while you can!

When you start reading a new genre, books will take longer to read because you're constantly encountering new ideas and reconciling them with your worldview. But over time, these ideas will become more familiar - so you'll have fewer "quakes" but can skim through books faster and pick out new ideas.


text:
# Common

Shared RabbitMQ server in docker-compose.yaml for E-Commerce Shop micro-services:
- [Wish List](https://github.com/pejovski/wish-list)
- [Catalog](https://github.com/pejovski/catalog)
- [Reviewing - ToDo](https://github.com/pejovski/reviewing)
- [Shopping Cart - ToDo](https://github.com/pejovski/cart)

### Usage

```bash
docker-compose up
```

repository: pejovski/common

repo_name: pejovski/common


text:
## ETL processing pipeline for COVID-19 data using AWS services and Python

This project is for an automatic ETL processing pipeline for Covid-19 data for Greece (or any other selected country) using AWS services and Python code.

The data are downloaded from John Hopkins CSSE's github repository (https://github.com/CSSEGISandData) and specifically the time series data (https://github.com/CSSEGISandData/COVID-19/tree/master/csse_covid_19_data/csse_covid_19_time_series). The data are updated daily around 23:59 (UTC).

The pipeline uses the following:
* an Amazon EventBridge rule (every 24h) to trigger a Amazon Lambda function
* a Amazon Lambda function that load the appropriate libraries, the boto sessions, the sns messaging, the database connection (postgres) and the table creation and update logic
* a Amazon Lambda layers for Pandas, Psycopg2 and data transformaton function.
* a Amazon PostgreSQL RDS database
* a SNS topic for email notfications on the processing pipeline (errors and successful loads)

A Redash connection to the PostgreSQL database and dashboard was created for data presentation and public access to the interested parties.

repository: slimbis/AWS-ETL-REPORTING

branch_name: refs/heads/main

repo_name: slimbis/AWS-ETL-REPORTING


text:
---
layout: default
---

# 1995-11-16 - Re: e$: Come aaaannnndddd Get it!

## Header Data

From: "E. ALLEN SMITH"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: cdef7ca34d7b348b7612f2f17f8b54ae62a024df48d1cfbf2b6034862079545b

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1995-11-16 03:21:46 UTC

Raw Date: Thu, 16 Nov 1995 11:21:46 +0800

## Raw message

```
{% raw  %}From: "E. ALLEN SMITH"<EMAIL_ADDRESS>Date: Thu, 16 Nov 1995 11:21:46 +0800
To<EMAIL_ADDRESS>Subject: Re: e$: Come aaaannnndddd Get it!
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

From<EMAIL_ADDRESS>(Robert Hettinga)

Sameer's done it, I'm going to do it, and I'm hoping that everyone who
*can* do it *will*.

Lumpy though MTB may be, they're taking a risk that no one else in the
financial community would, and they deserve whatever support we can give
'em.

If they do it and it works, there will be others. Come on, people, let's
make it work.

Put your e$ where your mouth is, or at least on a hard drive somewhere...
-------------------
	I will as soon as someone comes up with a _fully_ private digital
cash system and starts using it for something. As I understand it, Chaum's
ecash system is not one (i.e., non-privacy to the sender and of amounts to the
bank). If I'm incorrect, please tell me and I'll set up an account with MTB
immediately (if there's a text-based interface).
	-Allen

{% endraw %}
```

## Thread

+ Return to [November 1995](/archive/1995/11)

+ Return to "["E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>](/authors/e_allen_smith_eallensmith_at_ocelot_rutgers_edu_)"
+ Return to "[sameer <sameer@c2.org>](/authors/sameer_sameer_at_c2_org_)"

+ 1995-11-16 (Thu, 16 Nov 1995 11:21:46 +0800) - Re: e$: Come aaaannnndddd Get it! - _"E. ALLEN SMITH"<EMAIL_ADDRESS>  + 1995-11-17 (Fri, 17 Nov 1995 12:02:42 +0800) - [Re: e$: Come aaaannnndddd Get it!](/archive/1995/11/0d59c615cacaf3004cac9e9750a42bb8f837aeb266655be73fe601bd730ce3e3) - _sameer<EMAIL_ADDRESS>

gha_license_id: MIT


text:
# Groupby_Concat

Link: https://stackoverflow.com/questions/17841149/pandas-groupby-how-to-get-a-union-of-strings?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa

```
>>> d
   A       B
0  1    This
1  2      is
2  3       a
3  4  random
4  1  string
5  2       !

>>> d.groupby('A')['B'].apply(list)
A
1    [This, string]
2           [is, !]
3               [a]
4          [random]
dtype: object
```


text:
# Example: read_all

This Blue Pill board example reads all 16 (or 8 with minor changes) channels on a 4067 (or 4051) series analog multiplexer every 100ms and pretty-prints the results over an ST-LINK debugger via probe-rs (`rprintln!()`).

# Usage

```shell
$ cd examples/bluepill # Make sure you're in the right place
$ cargo run --example read_all
```

# Demonstration

Here's an imaginary example using a 74HC4067 with a Blue Pill (stm32f104) board...

Here's me using it to read a hall effect sensor on channel 15:

![Reading a hall effect sensor on channel 15](https://thumbs.gfycat.com/FlippantAptHadrosaurus-size_restricted.gif)

repository: BinaryBearzz/analog-multiplexer

repo_name: BinaryBearzz/analog-multiplexer


text:
# Install and run RoLaGuard on Linux

This guide provide the steps needed to install and run RoLaGuard in a Linux machine with Ubuntu 18.04 or newer.

## Prerequisites

Open a console and run the following lines to install some dependencies

```bash
sudo apt-get update
sudo apt-get install apt-transport-https ca-certificates software-properties-common curl gcc git dnsmasq openvpn bridge-utils resolvconf
```

### Choose a driver

Minikube can use two drivers to run, virtualbox or kvm2. Choose one and install the needed packages.

#### Virtualbox

```bash
sudo apt-get install virtualbox virtualbox-ext-pack
```

#### KVM

```bash
sudo apt-get install qemu-kvm qemu virt-manager virt-viewer libvirt-bin
```

### Download and install minikubes, docker and kubectl

Download the latest versions of the software and install them.

#### Minikubes

```bash
wget https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
chmod +x minikube-linux-amd64
sudo mv minikube-linux-amd64 /usr/local/bin/minikube
```

#### Kubectl

```bash
curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl
chmod +x ./kubectl
sudo mv ./kubectl /usr/local/bin/kubectl
```

#### Docker

```bash
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install docker-ce
```

### Docker machine

```bash
curl -L https://github.com/docker/machine/releases/download/v0.13.0/docker-machine-`uname -s`-`uname -m` -o ~/docker-machine
chmod +x ~/docker-machine
sudo cp ~/docker-machine /usr/local/bin/
```

## Run RoLaGuard

First, give all the scripts execution permissions

```bash
chmod +x *.sh
```

To run RoLaGuard simply run

```bash
./Run-Rolaguard.sh
```

## Optional: separated steps

The *run_rolaguard.sh* script deletes old files, download and start the K8s cluster, build the docker images of each RoLaGuard component and deploy all these images. If you only want to start the K8s cluster, run the following line:

```bash
./Start-Minikube.sh
```

To only build and deploy the docker images (the cluster must be up!):

```bash
./Configure-Minikube.sh
```

## Optional: build & deploy local Docker images separately

After having created the K8s cluster with minikube (it's important to have the cluster running before building the images!), you can build the local Docker images with the provided scripts.

To build altogether run:

```bash
./Build-DockerImages.sh
```

If you want to build the components separately, comment out the specif line in this file.

After having build all necessary Docker images, deploy the services/deployments with:

```bash
./Deploy-DockerImages.sh
```

If you want to deploy the components separately, comment out the specif line in this file.

## Minikube dashboard

To open the Kubernetes Dashboard run the following line:

```bash
minikube dashboard
```

repository: afroschauer/rolaguard

repo_name: afroschauer/rolaguard


text:
JQuery 3.4 Behavior Patch
=================================

This example enables JQuery 3.4 behavior in the Camunda Webapps 7.14+ . It makes use of the `customScript` property of the webapp configurations.

You can read more about the JQuery 3.5 release in the [JQuery release blog](https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/).

Built and tested against Camunda Platform version `7.15.0`.

Integrate into Camunda Webapp
-----------------------------

We use Tasklist as an example. If you need this fix for Cockpit or Admin, simply adjust the paths.

Copy the `jquery-patch.js` file into the `app/tasklist/scripts/` folder in your Camunda webapp distribution. For the Tomcat distribution, this would be `server/apache-tomcat-X.X.XX/webapps/camunda/app/tasklist/scripts/`.

Add the following content to the `customScripts` object in the `app/tasklist/scripts/config.js` file:

```
  // …
  customScripts: [
    'scripts/jquery-patch'
  ]
  // …
```

License
-------

Use under terms of the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)


text:
## Overview of workflows: syntax and execution

We use workflows written in [WDL](http://www.openwdl.org/), a Workflow Description Language with a human-readable and -writeable syntax. WDL makes it straightforward to define analysis tasks, chain them together in workflows, and parallelize their execution. The language makes common patterns simple to express, while also admitting uncommon or complicated behavior; and strives to achieve portability not only across execution platforms, but also different types of users. WDL is designed to be accessible and understandable to a wide range of users without requiring sophisticated programming knowledge.

The workflow files are recognizable by their '.wdl' extension. They are typically accompanied by one or more '.json' files that contain input file paths and parameters in JSON format.

WDL workflows can be executed using the Cromwell workflow management system, which can be run on a variety of local, HPC and cloud platforms as described [here](https://cromwell.readthedocs.io/en/stable/).

### Execution on Terra

For the purposes of the hackathon, we will run our workflows on [Terra](https://terra.bio/), an open cloud-based platform for genomic analysis operated by the Data Sciences Platform at the Broad Institute. Terra includes a Cromwell server and a user-friendly interface for managing and running WDL workflows.

See the workspace description and link in the main project README doc.

Note that we are using [workspace attributes](workspace_attributes.txt) to facilitate the use of reference files, dockers, etc. by multiple workflows in the same workspace.

## Original prototype workflows

This section lists the WDL workflow files and the corresponding workflow name as used in the original [Tetralogy of Fallot paper reproduction project](https://app.terra.bio/#workspaces/workshop-ashg18/ASHG18-ToF-Reproducible-Paper).

### Synthetic data generation

These are the workflows that we originally used to generate synthetic read data, and which are the main focus of this hackathon project.

#### Collect1000GParticipant | Collect-1000G-participants.wdl
This workflow collects the variants for a single participant from the master 1000 Genomes Projects Phase 3 data stored as separate per-chromosome VCFs in GCS by Google Genomics (as mirror of the EBI site) and consolidates them over all chromosomes.

#### GenerateSyntheticReads | Generate-synthetic-reads.wdl
This workflow uses the NEAT toolkit to generate synthetic paired-end read data based on a file of input variants and a desired mutation rate (can be 0 to not include any random mutation in addition to the input variants). It creates an analysis-ready BAM file and a "ground truth" VCF.

#### MutateReadsWithBAMSurgeon | Mutate-reads-with-BAMSurgeon.wdl
This workflow uses the BAMSurgeon `addsnv.py` tool to introduce specific mutations into an analysis-ready BAM file.

### Data analysis from ToF project

These are the workflows we used to reproduce the Tetralogy of Fallot analysis proper. We include them here in case we want to run some evaluations of how synthetic dataset properties affect analysis results, but we don't expect to make any modifications to these workflows.

#### CallSingleSampleGvcfGATK4 | Call-single-sample-GVCF-GATK4.wdl
This workflow uses GATK4 HaplotypeCaller to call variants per-sample and produce a GVCF file, which is an intermediate in the GATK joint calling workflow for germline short variants. The HaplotypeCaller's execution is scattered over sets of intervals, and followed by a merging step to produce a single file.

#### JointCallAndHardFilterGATK4 | Joint-call-and-hard-filter-GATK4.wdl
This workflow uses several GATK4 tools, including the GenomicsDB tooling for scalable joint calling, to apply joint variant discovery analysis to GVCFs produced by HaplotypeCaller and apply a simple hard filtering threshold. Note that this does not completely follow the official GATK Best Practices recommendations, which use VQSR for multisample datasets and CNN for single WGS or small exome cohorts (N<30).

#### PredictVariantEffectsGEMINI | Predict-variant-effects-GEMINI.wdl
This workflow annotates functional predictions using SnpEff and GEMINI after normalizing the variant representations using vt, a toolkit for manipulating variants that is best known for its normalization capabilities.

## Additional workflows

This section will list any new workflows developed as part of the hackathon.

### In progress

- CollectQualityMetrics (needs documentation)

repository: terra-workflows/synthetic-seq-data

gha_language: Jupyter Notebook

repo_name: terra-workflows/synthetic-seq-data


text:
---
hrs_structure:
  division: '1'
  volume: '3'
  title: '10'
  chapter: 125C
  section: ''
type: chapter
tags:
  - Government
menu:
  hrs:
    identifier: HRS0125C
    parent: title10
    name: 'Chapter 125C Procurement, Control, Distribution and Sale of'
weight: 11000
title: 'Procurement, Control, Distribution and Sale of'
full_title: 'Chapter 125C Procurement, Control, Distribution and Sale of'
---
**CHAPTER 125C**

**PROCUREMENT, CONTROL, DISTRIBUTION AND SALE OF**

**PETROLEUM PRODUCTS**

Part I. General Powers and Procedures

During a Shortage

Section

125C-1 Findings and purpose

125C-2 "Shortage" defined

125C-3 Powers in a shortage

125C-4 Adopting, filing, and taking effect of rules

125C-5 Publication of rules and declarations

125C-6 Petition for adoption, amendment, repeal,

or suspension of rules

125C-7 Repealed

125C-8 Personnel; delegation of powers

125C-9 Investigations and surveys

125C-10 Fraud; misdemeanor

125C-11 Repealed

Part II. Hardship Set-Aside and Allocation of

Petroleum Products During a Shortage

125C-21 Definitions

125C-22 When set-aside required

125C-23 Set-aside system

Part III. Energy Emergency Planning

125C-31 Biennial state energy emergency preparedness plan

125C-32 Biennial county energy emergency preparedness plans

Cross References

Energy industry information reporting, see chapter 486J.

Unfair trade practices by petroleum industry, see chapter 486B.

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
# Change Log

All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.

### [2.0.3](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@2.0.2<EMAIL_ADDRESS>(2021-10-11)

### 📝 Documentation

* Only validate circleCI badge against master ([#1322](https://github.com/coinbase/rest-hooks/issues/1322)) ([04e9642](https://github.com/coinbase/rest-hooks/commit/04e96426a865cbef362947da3a8f74f7347859e9))

### [2.0.2](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@2.0.1<EMAIL_ADDRESS>(2021-09-29)

**Note:** Version bump only for package @rest-hooks/endpoint

### [2.0.1](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@2.0.0<EMAIL_ADDRESS>(2021-09-29)

**Note:** Version bump only for package @rest-hooks/endpoint

## [2.0.0](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@2.0.0-beta.2<EMAIL_ADDRESS>(2021-09-08)

**Note:** Version bump only for package @rest-hooks/endpoint

## [2.0.0-beta.2](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@2.0.0-beta.1<EMAIL_ADDRESS>(2021-09-06)

**Note:** Version bump only for package @rest-hooks/endpoint

## [2.0.0-beta.1](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.2.3<EMAIL_ADDRESS>(2021-07-12)

### ⚠ 💥 BREAKING CHANGES

* * Importing directly from hidden files is no longer supported
* Node>=12
* - Removed: SyntheticError (untriggerable since https://github.com/coinbase/rest-hooks/pull/938)
- @rest-hooks/rest: 500s are 'soft', else 'hard'
- PollingSubscription: any errors are 'soft'
- @rest-hooks/endpoint: no default errorPolicy, therefore all errors are
'hard'
* - fromJS() -> process() to customize init
- normalize results in POJO rather than instances
- FlatEntity, SimpleRecord removed (use @rest-hooks/legacy)
- peerDep @rest-hooks/endpoint > 2

### 🚀 Features

* Add errorPolicy to endpoint options ([#971](https://github.com/coinbase/rest-hooks/issues/971)) ([836f05b](https://github.com/coinbase/rest-hooks/commit/836f05b407b5ac96c8f094e652221aa5a95300b0))
* Use 'exports' package.json member ([#955](https://github.com/coinbase/rest-hooks/issues/955)) ([7e9d39f](https://github.com/coinbase/rest-hooks/commit/7e9d39f15b4b321352ece0caddb93e2c414df8ae))

### 💅 Enhancement

* Different babel targets for cjs and umd builds ([#989](https://github.com/coinbase/rest-hooks/issues/989)) ([f054814](https://github.com/coinbase/rest-hooks/commit/f05481410cf8daa2101d4dbda826e56ad10ec723))
* Entities normalize to POJO ([#940](https://github.com/coinbase/rest-hooks/issues/940)) ([75ebdfe](https://github.com/coinbase/rest-hooks/commit/75ebdfe641ccf57fca35c44a94077e4a314e44d7))
* Give Endpoint.extend() type a name ([#969](https://github.com/coinbase/rest-hooks/issues/969)) ([5afec16](https://github.com/coinbase/rest-hooks/commit/5afec16727f18af6d6acb52b7c0f094555d43e04))
* Remove 'fallback' package.json exports ([#992](https://github.com/coinbase/rest-hooks/issues/992)) ([dc95f9d](https://github.com/coinbase/rest-hooks/commit/dc95f9dbad20d5740218c52c906596b6a3d6eae4))

### 📝 Documentation

* Add doc links to jsdocs ([#966](https://github.com/coinbase/rest-hooks/issues/966)) ([dc7fcfe](https://github.com/coinbase/rest-hooks/commit/dc7fcfec24c30d5f405d24ccc1828620d837ea6b))

## [2.0.0-beta.0](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.2.2<EMAIL_ADDRESS>(2021-06-30)

### ⚠ 💥 BREAKING CHANGES

* * Importing directly from hidden files is no longer supported
* Node>=12
* - Removed: SyntheticError (untriggerable since https://github.com/coinbase/rest-hooks/pull/938)
- @rest-hooks/rest: 500s are 'soft', else 'hard'
- PollingSubscription: any errors are 'soft'
- @rest-hooks/endpoint: no default errorPolicy, therefore all errors are
'hard'
* - fromJS() -> process() to customize init
- normalize results in POJO rather than instances
- FlatEntity, SimpleRecord removed (use @rest-hooks/legacy)
- peerDep @rest-hooks/endpoint > 2

### 🚀 Features

* Add errorPolicy to endpoint options ([#971](https://github.com/coinbase/rest-hooks/issues/971)) ([836f05b](https://github.com/coinbase/rest-hooks/commit/836f05b407b5ac96c8f094e652221aa5a95300b0))
* Use 'exports' package.json member ([#955](https://github.com/coinbase/rest-hooks/issues/955)) ([7e9d39f](https://github.com/coinbase/rest-hooks/commit/7e9d39f15b4b321352ece0caddb93e2c414df8ae))

### 💅 Enhancement

* Different babel targets for cjs and umd builds ([#989](https://github.com/coinbase/rest-hooks/issues/989)) ([f054814](https://github.com/coinbase/rest-hooks/commit/f05481410cf8daa2101d4dbda826e56ad10ec723))
* Entities normalize to POJO ([#940](https://github.com/coinbase/rest-hooks/issues/940)) ([75ebdfe](https://github.com/coinbase/rest-hooks/commit/75ebdfe641ccf57fca35c44a94077e4a314e44d7))
* Give Endpoint.extend() type a name ([#969](https://github.com/coinbase/rest-hooks/issues/969)) ([5afec16](https://github.com/coinbase/rest-hooks/commit/5afec16727f18af6d6acb52b7c0f094555d43e04))
* Remove 'fallback' package.json exports ([#992](https://github.com/coinbase/rest-hooks/issues/992)) ([dc95f9d](https://github.com/coinbase/rest-hooks/commit/dc95f9dbad20d5740218c52c906596b6a3d6eae4))

### 📝 Documentation

* Add doc links to jsdocs ([#966](https://github.com/coinbase/rest-hooks/issues/966)) ([dc7fcfe](https://github.com/coinbase/rest-hooks/commit/dc7fcfec24c30d5f405d24ccc1828620d837ea6b))

### [1.2.3](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.2.2<EMAIL_ADDRESS>(2021-07-06)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.2.2](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.2.1<EMAIL_ADDRESS>(2021-06-19)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.2.1](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.2.0<EMAIL_ADDRESS>(2021-06-16)

**Note:** Version bump only for package @rest-hooks/endpoint

## [1.2.0](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.6<EMAIL_ADDRESS>(2021-06-13)

### 🚀 Features

* Endpoint.name ([#914](https://github.com/coinbase/rest-hooks/issues/914)) ([aa5f80d](https://github.com/coinbase/rest-hooks/commit/aa5f80db6c47ff975b1d257352315a57b87addce))

### [1.1.6](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.5<EMAIL_ADDRESS>(2021-06-09)

### 💅 Enhancement

* 'module' entrypoint targets 2019 browsers ([#905](https://github.com/coinbase/rest-hooks/issues/905)) ([d988abe](https://github.com/coinbase/rest-hooks/commit/d988abe063fc67c74fce12e234c9c3ffdb7cc230))

### [1.1.5](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.3<EMAIL_ADDRESS>(2021-06-02)

### 💅 Enhancement

* Improve autoimport handling in vscode ([#890](https://github.com/coinbase/rest-hooks/issues/890)) ([f8f2bef](https://github.com/coinbase/rest-hooks/commit/f8f2bef411183676009c6a9df24a26d147c6d9f6))

### [1.1.4](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.3<EMAIL_ADDRESS>(2021-05-30)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.1.3](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.2<EMAIL_ADDRESS>(2021-05-24)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.1.2](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.1<EMAIL_ADDRESS>(2021-05-24)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.1.1](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.1.0<EMAIL_ADDRESS>(2021-04-25)

**Note:** Version bump only for package @rest-hooks/endpoint

## [1.1.0](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.12<EMAIL_ADDRESS>(2021-04-24)

### 🚀 Features

* Endpoint parameters can be of any length ([#767](https://github.com/coinbase/rest-hooks/issues/767)) ([552f837](https://github.com/coinbase/rest-hooks/commit/552f83740279376288879a661ff487c5c6f1d469))
* Endpoint.bind() ([#762](https://github.com/coinbase/rest-hooks/issues/762)) ([b5ad3dd](https://github.com/coinbase/rest-hooks/commit/b5ad3dd8478bc8edbdfe752080e72024bc1686da))

### 💅 Enhancement

* Support TypeScript 3.7 ([#752](https://github.com/coinbase/rest-hooks/issues/752)) ([68a10e0](https://github.com/coinbase/rest-hooks/commit/68a10e06dc0718f5e480097e6056a7a7954d1161))

### [1.0.12](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.11<EMAIL_ADDRESS>(2021-04-12)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.0.11](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.10<EMAIL_ADDRESS>(2021-04-12)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.0.10](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.9<EMAIL_ADDRESS>(2021-04-04)

### 🐛 Bug Fix

* Endpoint 'type' in loose typescript mode ([#712](https://github.com/coinbase/rest-hooks/issues/712)) ([9ef9c4f](https://github.com/coinbase/rest-hooks/commit/9ef9c4ffc2813a597f15b571f639ad23fd8d6a03))

### [1.0.9](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.8<EMAIL_ADDRESS>(2021-03-26)

### 🐛 Bug Fix

* Compatibility with TypeScript strict: false ([#683](https://github.com/coinbase/rest-hooks/issues/683)) ([8a6e7ed](https://github.com/coinbase/rest-hooks/commit/8a6e7ed4d179555c4ba5cb8957b1c63697a1ce1a))

### [1.0.8](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.7<EMAIL_ADDRESS>(2021-03-24)

### 💅 Enhancement

* Mark Endpoint's back-compat members as 'deprecated' ([#665](https://github.com/coinbase/rest-hooks/issues/665)) ([6feade0](https://github.com/coinbase/rest-hooks/commit/6feade0ad28eb96c7906793b05d49991294ce858))

### 🐛 Bug Fix

* 'type' inferred from 'sideEffects' correct in union case ([#678](https://github.com/coinbase/rest-hooks/issues/678)) ([2cda690](https://github.com/coinbase/rest-hooks/commit/2cda6900cc3c653637452772ec5439a60354b140))

### [1.0.7](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.6<EMAIL_ADDRESS>(2021-03-14)

### 📝 Documentation

* Update package tags ([#650](https://github.com/coinbase/rest-hooks/issues/650)) ([4ef465a](https://github.com/coinbase/rest-hooks/commit/4ef465a129cd59668cd9c3542bb9ec03c84d2a4d))

### [1.0.6](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.5<EMAIL_ADDRESS>(2021-03-08)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.0.5](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.4<EMAIL_ADDRESS>(2021-03-03)

**Note:** Version bump only for package @rest-hooks/endpoint

### [1.0.4](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.3<EMAIL_ADDRESS>(2021-03-01)

### 💅 Enhancement

* Support 'undefined' as schema ([#583](https://github.com/coinbase/rest-hooks/issues/583)) ([1e81470](https://github.com/coinbase/rest-hooks/commit/7ef172a3d8469b182cc7a19055920a308841b59e))

### 🐛 Bug Fix

* Gracefully handle primitive entity responses ([#584](https://github.com/coinbase/rest-hooks/issues/584)) ([322b4c6](https://github.com/coinbase/rest-hooks/commit/322b4c6615ea02b09baf0bcfc9b214bb8be1ba4f))

### 📝 Documentation

* Typos and minor improvements ([#561](https://github.com/coinbase/rest-hooks/issues/561)) ([aed902a](https://github.com/coinbase/rest-hooks/commit/aed902a7ee8a50f7f08fab261efa528a82c52b19))

### [1.0.3](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.2<EMAIL_ADDRESS>(2021-02-04)

### 📦 Package

* Relax @babel/runtime requirement to ^7.7.2 ([#513](https://github.com/coinbase/rest-hooks/issues/513)) ([cc95b21](https://github.com/coinbase/rest-hooks/commit/cc95b219fbddebfbf334728887ca6d2fa070fce1))

### 📝 Documentation

* Link improvements, flesh out test readme ([#511](https://github.com/coinbase/rest-hooks/issues/511)) ([9cab431](https://github.com/coinbase/rest-hooks/commit/9cab431803a8b7d9c18e02b3e9cb7e336215ccdb))

### [1.0.2](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.1<EMAIL_ADDRESS>(2021-01-30)

### 🐛 Bug Fix

* Ensure Endpoint doesn't trigger CSP ([#505](https://github.com/coinbase/rest-hooks/issues/505)) ([a5a0011](https://github.com/coinbase/rest-hooks/commit/a5a00119c8888ce5c0440d2045febd9985fd2a8e))

### [1.0.1](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@1.0.0<EMAIL_ADDRESS>(2021-01-24)

**Note:** Version bump only for package @rest-hooks/endpoint

## 1.0.0 (2021-01-19)

### ⚠ 💥 BREAKING CHANGES

* Remove `normalize`, `denormalize`; use
`normalizr` package for those
* getFetchOptions() -> getEndpointExtra()

### 🚀 Features

* Add @rest-hooks/endpoint package ([#359](https://github.com/coinbase/rest-hooks/issues/359)) ([642bb1a](https://github.com/coinbase/rest-hooks/commit/642bb1a206ce80bae627574f6b1beacf34be3293))
* Add @rest-hooks/rest package ([#375](https://github.com/coinbase/rest-hooks/issues/375)) ([5e5c125](https://github.com/coinbase/rest-hooks/commit/5e5c125d3396ebbb8514aea6fc80b4dfceb0da27))
* Infer return type from schema ([2dccff4](https://github.com/coinbase/rest-hooks/commit/2dccff44042db4b2869e851156d4363fdd9cc764))
* Simple AbortController integration ([#392](https://github.com/coinbase/rest-hooks/issues/392)) ([899563d](https://github.com/coinbase/rest-hooks/commit/899563deccaccc214c3504b91b96e1460ddfab2f))
* Support extra endpoint members and inheritance ([#387](https://github.com/coinbase/rest-hooks/issues/387)) ([6ad5486](https://github.com/coinbase/rest-hooks/commit/6ad5486b6e333d8721b74fd4fb1b7ed783461435))
* Support helper methods ([c3fb075](https://github.com/coinbase/rest-hooks/commit/c3fb075b390e7c8db28d53962563b92b65d7869d))

### 💅 Enhancement

* `endpoint` package only exports definitions ([#473](https://github.com/coinbase/rest-hooks/issues/473)) ([51dcafe](https://github.com/coinbase/rest-hooks/commit/51dcafe98631998a1db1959f2796d7122d96960b))
* EndpointInstance defaults should match everything ([d7067ba](https://github.com/coinbase/rest-hooks/commit/d7067baf68e03c0b389c4349fee18571e9172062))
* Improve endpoint ([#364](https://github.com/coinbase/rest-hooks/issues/364)) ([503dd29](https://github.com/coinbase/rest-hooks/commit/503dd29f7cb89ecf1659d065932eae33f0855e1d))
* Make Endpoint compatible with FetchShape ([caa967c](https://github.com/coinbase/rest-hooks/commit/caa967ceaa0c1288b15711b0c18b132689b94cc1))
* Resource uses endpoint ([#365](https://github.com/coinbase/rest-hooks/issues/365)) ([4472106](https://github.com/coinbase/rest-hooks/commit/4472106afd05ad060399f0cd3a872ed07e3350ec))

### 🐛 Bug Fix

* Ambient files now typechecked, fixed some types there ([#372](https://github.com/coinbase/rest-hooks/issues/372)) ([223d4a4](https://github.com/coinbase/rest-hooks/commit/223d4a478ae4b6ba7d42f9d1c2b9deca5b228c8d))
* Compile types for endpoint ([a1b4195](https://github.com/coinbase/rest-hooks/commit/a1b4195083420356779deada24290b77092a45d0))
* Export Endpoint through core ([8b60dea](https://github.com/coinbase/rest-hooks/commit/8b60dea6c85518bbd32b088440e591614d3a11f0))
* Export type correctly in endpoint ([#401](https://github.com/coinbase/rest-hooks/issues/401)) ([f2b033a](https://github.com/coinbase/rest-hooks/commit/f2b033a7f7fd6614ad0d7a25093948f26c495db4))
* extend() correctly keeps options for FetchShape compat ([bf522a2](https://github.com/coinbase/rest-hooks/commit/bf522a2d138dc6bc700e9e5b7f9c9bc1dfd9e148))
* Infer useFetcher() has no body when not present in fetch ([#385](https://github.com/coinbase/rest-hooks/issues/385)) ([22dd399](https://github.com/coinbase/rest-hooks/commit/22dd3995c519e1990f2388b6365494cec873d04a))
* Only export AbstractInstanceType in type-world ([#396](https://github.com/coinbase/rest-hooks/issues/396)) ([131fa45](https://github.com/coinbase/rest-hooks/commit/131fa45063be8fe3dc861dc3639d38dc430580dc))
* Publish endpoint ambient typescript declarations ([2e982ca](https://github.com/coinbase/rest-hooks/commit/2e982caf484da6f2970506b803d4eb52ce0c558d))
* Remove broken type ([09e8268](https://github.com/coinbase/rest-hooks/commit/09e826841efc9d3cf1b6432ca2977fb0f8f558bd))
* Remove broken type ([316e5a0](https://github.com/coinbase/rest-hooks/commit/316e5a0945d79ad82748a0e100d3a4a5c788e44c))

### 📦 Package

* Use @babel/runtime @ 7.12 ([e631f6a](https://github.com/coinbase/rest-hooks/commit/e631f6a8c435c5ef74b3809c8950a2caceca8763))

### 📝 Documentation

* Add Endpoint to API section ([73428b0](https://github.com/coinbase/rest-hooks/commit/73428b01a5759c8079ca3b0de5aa51e77f2e2dde))
* Add more to readme ([2fc29e5](https://github.com/coinbase/rest-hooks/commit/2fc29e5f94512a1fa9fb4b2777679a7499e360da))
* Fix tags ([987f0ed](https://github.com/coinbase/rest-hooks/commit/987f0ed7d4980c3276bb8c9701f606364dad93d8))

## [0.8.0](https://github.com/coinbase/rest-hooks/compare/@rest-hooks/endpoint@0.7.4<EMAIL_ADDRESS>(2021-01-19)

### ⚠ 💥 BREAKING CHANGES

* Remove `normalize`, `denormalize`; use
`normalizr` package for those

### 💅 Enhancement

* `endpoint` package only exports definitions ([#473](https://github.com/coinbase/rest-hooks/issues/473)) ([51dcafe](https://github.com/coinbase/rest-hooks/commit/51dcafe98631998a1db1959f2796d7122d96960b))

## 0.7.4 (2021-01-14)

**Note:** Version bump only for package @rest-hooks/endpoint

## 0.7.3 (2021-01-06)

* pkg: Use @babel/runtime @ 7.12 ([e631f6a](https://github.com/coinbase/rest-hooks/commit/e631f6a))

## 0.7.2 (2020-09-08)

* internal: Upgrade build pkgs (#404) ([dc56530](https://github.com/coinbase/rest-hooks/commit/dc56530)), closes [#404](https://github.com/coinbase/rest-hooks/issues/404)
* enhance: EndpointInstance defaults should match everything ([d7067ba](https://github.com/coinbase/rest-hooks/commit/d7067ba))

## 0.7.1 (2020-08-13)

* fix: Export type correctly in endpoint (#401) ([f2b033a](https://github.com/coinbase/rest-hooks/commit/f2b033a)), closes [#401](https://github.com/coinbase/rest-hooks/issues/401)

## 0.7.0 (2020-08-12)

* fix: Only export AbstractInstanceType in type-world (#396) ([131fa45](https://github.com/coinbase/rest-hooks/commit/131fa45)), closes [#396](https://github.com/coinbase/rest-hooks/issues/396)
* feat: Simple AbortController integration (#392) ([899563d](https://github.com/coinbase/rest-hooks/commit/899563d)), closes [#392](https://github.com/coinbase/rest-hooks/issues/392)

## 0.6.1 (2020-08-09)

* fix: extend() correctly keeps options for FetchShape compat ([bf522a2](https://github.com/coinbase/rest-hooks/commit/bf522a2))

## 0.6.0 (2020-08-08)

* internal: Test using endpoints directly (#389) ([bb0e8fd](https://github.com/coinbase/rest-hooks/commit/bb0e8fd)), closes [#389](https://github.com/coinbase/rest-hooks/issues/389)
* feat: Support extra endpoint members and inheritance (#387) ([6ad5486](https://github.com/coinbase/rest-hooks/commit/6ad5486)), closes [#387](https://github.com/coinbase/rest-hooks/issues/387)

## 0.5.3 (2020-08-04)

* fix: Infer useFetcher() has no body when not present in fetch (#385) ([22dd399](https://github.com/coinbase/rest-hooks/commit/22dd399)), closes [#385](https://github.com/coinbase/rest-hooks/issues/385)

## 0.5.2 (2020-07-31)

**Note:** Version bump only for package @rest-hooks/endpoint

## 0.5.1 (2020-07-27)

**Note:** Version bump only for package @rest-hooks/endpoint

## 0.5.0 (2020-07-27)

* feat: Add @rest-hooks/rest package (#375) ([5e5c125](https://github.com/coinbase/rest-hooks/commit/5e5c125)), closes [#375](https://github.com/coinbase/rest-hooks/issues/375)
* feat: Support helper methods ([c3fb075](https://github.com/coinbase/rest-hooks/commit/c3fb075))

## 0.4.3 (2020-07-22)

* fix: Ambient files now typechecked, fixed some types there (#372) ([223d4a4](https://github.com/coinbase/rest-hooks/commit/223d4a4)), closes [#372](https://github.com/coinbase/rest-hooks/issues/372)

## 0.4.2 (2020-07-22)

* fix: Remove broken type ([09e8268](https://github.com/coinbase/rest-hooks/commit/09e8268))
* fix: Remove broken type ([316e5a0](https://github.com/coinbase/rest-hooks/commit/316e5a0))

## 0.4.1 (2020-07-20)

* fix: Export Endpoint through core ([8b60dea](https://github.com/coinbase/rest-hooks/commit/8b60dea))

## 0.4.0 (2020-07-14)

* enhance: Resource uses endpoint (#365) ([4472106](https://github.com/coinbase/rest-hooks/commit/4472106)), closes [#365](https://github.com/coinbase/rest-hooks/issues/365)

### BREAKING CHANGE

* getFetchOptions() -> getEndpointExtra()

## 0.3.2 (2020-07-14)

* fix: Publish endpoint ambient typescript declarations ([2e982ca](https://github.com/coinbase/rest-hooks/commit/2e982ca))

## 0.3.1 (2020-07-13)

* docs: Add Endpoint to API section ([73428b0](https://github.com/coinbase/rest-hooks/commit/73428b0))
* enhance: Improve endpoint (#364) ([503dd29](https://github.com/coinbase/rest-hooks/commit/503dd29)), closes [#364](https://github.com/coinbase/rest-hooks/issues/364)
* enhance: Make Endpoint compatible with FetchShape ([caa967c](https://github.com/coinbase/rest-hooks/commit/caa967c))

## 0.3.0 (2020-07-13)

* feat: Infer return type from schema ([2dccff4](https://github.com/coinbase/rest-hooks/commit/2dccff4))
* docs: Add more to readme ([2fc29e5](https://github.com/coinbase/rest-hooks/commit/2fc29e5))
* docs: Fix tags ([987f0ed](https://github.com/coinbase/rest-hooks/commit/987f0ed))

## 0.2.0 (2020-07-12)

* fix: Compile types for endpoint ([a1b4195](https://github.com/coinbase/rest-hooks/commit/a1b4195))
* internal: Move readme to top level endpoint folder ([36f6194](https://github.com/coinbase/rest-hooks/commit/36f6194))
* feat: Add @rest-hooks/endpoint package (#359) ([642bb1a](https://github.com/coinbase/rest-hooks/commit/642bb1a)), closes [#359](https://github.com/coinbase/rest-hooks/issues/359)

repository: devyboy/rest-hooks

repo_name: devyboy/rest-hooks


text:
# ivs
an intelligent vswitch

Usage:
Inorder to use scons, you should install scons firstly.

1. yum install scons
2. cd ivs
3. scons

then you can find the final executable binary in the project directory.

repository: iaccepted/ivs

repo_name: iaccepted/ivs


text:
# git-codeowners [![Build Status](https://travis-ci.org/softprops/git-codeowners.svg?branch=master)](https://travis-ci.org/softprops/git-codeowners) [![Software License](https://img.shields.io/badge/license-MIT-brightgreen.svg)](LICENSE) [![Crates.io](https://img.shields.io/crates/v/git-codeowners.svg)](https://crates.io/crates/git-codeowners)

> a git extention for Github [CODEOWNERS files](https://help.github.com/articles/about-codeowners/)

Github `CODEOWNERS` files document ownership over paths within git repositories allowing
you to more effectively focus communication with the right people.

## install

### Homebrew

For osx users, you can use `brew` to install or update `git-codeowners`

```bash
$ brew install softprops/tools/git-codeowners
```

To upgrade, just use `brew upgrade` instead

### GH releases

You can download releases for osx and linux directly from github releases

```bash
$ cd $HOME/bin
$ curl -L "https://github.com/softprops/git-codeowners/releases/download/v0.1.2/git-codeowners-$(uname -s)-$(uname -m).tar.gz" \
  | tar -xz
```

### Cargo

If you are a rust user can can just use `cargo`

```bash
$ cargo install git-codeowners
```

## usage

git-codeowners is intended for use as a git extention ( a program whose name starts with git- ) to extend your git workflow.

```bash
$ git codeowners file src/main.rs
@softprops
```

```bash
$ git codeowners log origin/master..
05a4fc chore: do the hokey cokey
 * "Cargo.lock" @ops
 * "Cargo.toml" @ops

e5fe46 feat: Discover current repository
 * "Cargo.lock" @ops
 * "Cargo.toml" @ops
 * "src/main.rs" @softprops

Summary:
 * @softprops: 1 file in 1 commit, including: "src/main.rs" in e5fe46 feat: Discover current repository
 * @ops: 4 files in 2 commits, including: "src/main.rs" in 05a4fc chore: do the hokey cokey
```

```bash
$ git-codeowners --help
git-codeowners 0.1.2
Github CODEOWNERS answer sheet

USAGE:
    git-codeowners [FLAGS] [OPTIONS] <SUBCOMMAND>

FLAGS:
    -e, --emails     Only return emails
    -h, --help       Prints help information
    -t, --teams      Only return teams
    -u, --users      Only return users
    -V, --version    Prints version information

OPTIONS:
    -c, --codeowners <codeowners>    An explicit path for a CODEOWNERS file. program will exit 1 if file can not be
                                     resolved

SUBCOMMANDS:
    help    Prints this message or the help of the given subcommand(s)
    log     annotate log information
    path    Finds information about a specific path or set of paths
```

Doug Tangren (softprops) 2017

repository: syllogy/git-codeowners

repo_name: syllogy/git-codeowners


text:
# Linux canadian cross toolchain generation procedure

## Introduction

If you are here you may be wondering how the linux toolchain is built and or maybe you want to
create a new one. This little helper tool creates a linux toolchain either from scratch or by
providing the sources of all the toolchain components in tar format (you can find them in a
previously built toolchain in /src/...). The expectation is that we're going to switch distributions
every two years or so.

## Prerequisites

The toolchain builder relies on a remote linux machine that can run docker containers, the builder
tool takes care of creating a machine as long as you have a valid GCP credential for the used
project. By default the credentials located in
"$env:AppData\Roaming\gcloud\legacy_credentials\$env:Username\adc.json" will be used, you
can provide another set of credentials using the -gcp-credentials argument, if you alread have a
working Google Cloud SDK installation, you probably already have the credentials.

If you need to get setup and never used GCP, you either create a new instance through the GCP
console by following [this guide](https://cloud.google.com/compute/docs/instances/create-start-instance),
or install the [Google Cloud SDK](go/softwarecenter) and follow
[this guide](https://cloud.google.com/sdk/docs/initializing) to initialize it.

## Using the builder helper

The builder is not distributed in binary format and is rather run through bazel, it relies on some
supporting files to create the toolchain (toolchain definition work file and such) those explicit
dependencies to the executable and are provided through runfiles.
If you have the necessary credentials you can run the following command to generate a toolchain

```powershell
bazel run --config=windows //tools/linux-toolchain-builder --enable_runfiles -- -vm-name=linux-toolchain-builder
```

Otherwise you can provide an already existing ssh host that has apt as a packet manager:

```powershell
bazel run --config=windows //tools/linux-toolchain-builder --enable_runfiles -- -ssh-host=x.x.x.x
```

It happens that the toolchain copy stays stuck, you can relaunch that specific step or a series of steps

```powershell
bazel run --config=windows //tools/linux-toolchain-builder --enable_runfiles -- -vm-name=linux-toolchain-builder -from-step=copytoolchainfromremote -to-step=copytoolchainfromremote
```

Note that when Unzipping the resulting toolchain, you'll have warnings about duplicate files, those
are not really duplicate files. Since Linux is a case sensitive OS, some header files only differ in
casing, windows treats them as the same. Choose Auto-rename to when unzipping so the files are still
there. We haven't encountered an issue with them yet, so if we do we will decide on a patching
strategy when building the toolchain.

When you are done with the toolchain and the machine used to create it, use the clean argument to
delete it

```powershell
bazel run --config=windows //tools/linux-toolchain-builder --enable_runfiles -- -vm-name=linux-toolchain-builder -clean
```

## Manual generation

This section helps you understand better the steps taken to generate a toolchain and are provided as
an extra helper if you need to tweak the toolchain and iterate faster while doing so.

#### In PowerShell:

NOTE: You can run them in Command Prompt, but will need to tweak some environment variables from \$var=x to %VAR%, etc.

### Creating a toolchain from scratch

- Create a VM either through the portal or by using the following command line:

```powershell
gcloud compute --project=$PROJECT instances create $env:USERNAME-linux-toolchain-creation-vm --zone=us-east4-c --machine-type=n1-standard-4 --subnet=default --network-tier=PREMIUM --metadata-from-file ssh-keys="$env:USERPROFILE/.ssh/google_compute_engine.pub" --maintenance-policy=MIGRATE --image-family=ubuntu-1804-lts --image-project=ubuntu-os-cloud --boot-disk-size=50GB --boot-disk-type=pd-standard --boot-disk-device-name=linux-toolchain-creation-vm --reservation-affinity=any
```

- Register the machine ip address in the following variable:

```powershell
$remoteIp=$(gcloud compute instances describe $env:USERNAME-linux-toolchain-creation-vm --format='get(networkInterfaces[0].accessConfigs.natIP)')
```

- Copy the content of this folder to the machine.

NOTE: (Internal Google only): Depending on how you created your ssh key, you may need to append `_google_com` to `$($env:USERNAME)` in all scp and ssh commands.

NOTE: (Internal Google only): You might need to set ssh configurations to make this work internally.
      See internal documentation.

```powershell
scp -i"$env:USERPROFILE/.ssh/google_compute_engine" -r .\docker "$($env:USERNAME)@$($remoteIp):~/xtools-build/"
```

- SSH to the machine

```powershell
ssh "$($env:USERNAME)@$remoteIp" -i"$env:USERPROFILE/.ssh/google_compute_engine"
```

- Add the following linux user that allows the Docker container instance to write a readable shared file

#### In ssh/bash:

```sh
sudo groupadd --gid 1024 buildgroup
sudo useradd --shell /bin/bash --no-create-home --gid buildgroup --uid 1024 builduser
```

- Create an output folder and set it's rights access right to the created user

```sh
cd ~/xtools-build/
mkdir output
sudo chown -R builduser:buildgroup output
```

- Install docker Pre-reqs:

```sh
set -x
set -eu
sudo apt-get update
sudo apt-get -y upgrade
sudo apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
# Verify that you have the key with fingerprint 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
sudo apt-key fingerprint 0EBFCD88
# Should produce:
# pub   rsa4096 2017-02-22 [SCEA]
#      9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
# uid           [ unknown] Docker Release (CE deb<EMAIL_ADDRESS># sub   rsa4096 2017-02-22 [S]
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
```

- Install Docker

```sh
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io
# Optional - test
sudo docker run hello-world
# Downloads new image and prints a "Hello from Docker!" message.
```

- Create the container

```sh
sudo docker build -t xtools .
```

- Run the container

```sh
sudo docker run -v $PWD/output:/xtools-build/output xtools
```

- If the output is valid, push the resulting image our registry. (These instructions are modelled off
[the container registry authentication docs](https://cloud.google.com/container-registry/docs/advanced-authentication)).
First, some setup:

```sh
# add yourself to the docker security group
sudo usermod -a -G ${USER}
# apply changes
sudo reboot
```

- This will obviously end your ssh session while the vm reboots. Give it a few minutes, then reconnect.

#### In PowerShell:

```powershell
ssh "$($env:USERNAME)@$remoteIp" -i"$env:USERPROFILE/.ssh/google_compute_engine"
```

#### In ssh/bash:

```sh
# Set "project" to your GCP project's id.
project=<your-gcp-projectid-here>
sudo docker tag xtools gcr.io/$project/xtools:tag
sudo docker push gcr.io/$project/xtools:tag
exit
```

#### In PowerShell:

- If you'd like to move this to a new machine later, copy back the resulting zip

```powershell
scp -i"$env:USERPROFILE/.ssh/google_compute_engine" "$($env:USERNAME)@$($remoteIp):~/xtools-build/output/toolchain.zip" toolchain.zip
```

### Rebuilding a toolchain from existing packages

To rebuild from an existing state, you'll need the original docker image tag used to generate the
toolchain, and the src packaged used during the generation:

```powershell
scp -i"$env:USERPROFILE/.ssh/google_compute_engine" -r path_to_src "$($env:USERNAME)@$remoteIp:~/xtools-build/src"
```

- SSH to the machine

```powershell
ssh "$($env:USERNAME)@$remoteIp" -i"$env:USERPROFILE/.ssh/google_compute_engine"
```

- Run the the script build script again

```sh
sudo chown -R builduser:buildgroup ~/xtools-build/src
sudo docker run -v $PWD/src:/xtools-build/src -v $PWD/output:/xtools-build/output xtools:tag
```

- Copy the resulting package back

```powershell
scp -i "$env:USERPROFILE/.ssh/google_compute_engine" "$($env:USERNAME)@$remoteIp:~/xtools-build/output/toolchain.zip" toolchain.zip
```

repository: zotrix/sge-monorepo

repo_name: zotrix/sge-monorepo


text:
---
hrs_structure:
  division: '2'
  volume: '8'
  title: '23'
  chapter: '419'
  section: 419-9
type: hrs_section
tags:
  - Business
menu:
  hrs:
    identifier: HRS_0419-0009
    parent: HRS0419
    name: 419-9 Corporations sole heretofore formed; general laws
weight: 34045
title: Corporations sole heretofore formed; general laws
full_title: 419-9 Corporations sole heretofore formed; general laws
---
**§419-9 Corporations sole heretofore formed; general laws.** (a) Any corporation sole heretofore formed and existing under the laws of this State for ecclesiastical purposes may elect to continue its existence under this chapter by filing an application for amendment of its charter in the manner and form provided for an application for an original charter, together with the required certificates as to the incumbency of the corporation. If such amendment is allowed by the director of commerce and consumer affairs, this chapter thereupon shall apply to such corporations sole the same as to corporations formed under this chapter.

(b) Any charter or amended charter granted or corporation created or existing under the authority of this chapter shall be subject to all general laws enacted in regard to corporations. [L Sp 1941, c 58, pt of §1(6769D); RL 1945, §8409; RL 1955, §175-9; am L Sp 1959 2d, c 1, §15; am L 1963, c 114, §3; [HRS §419-9](/title-23/chapter-419/section-419-9/); am L 1982, c 204, §8; am L 1983, c 124, §17; am L 2004, c 121, §23]


text:
hytest
======

Simplify unit testing with Hy

## Getting Started ##

A basic example, adapted from the unittest Documentation:

```lisp
(import [random]
	[unittest])

(require hytest)

(defsuite TestSequenceFunctions
  (deftest test-choice
    (.assertTrue
     self
     (in (random.choice (range 10)) (range 10))
     )
    )

  (deftest test-sample-checks-bounds
    (.assertRaises self ValueError random.sample (range 10) 20)
    )

  (deftest test-sample-in-sequence
    (foreach [member (random.sample (range 10) 5)]
      (.assertTrue
       self
       (in member (range 10))
       )
      )
    )
  )

(if (= --name-- "__main__")
  (hytest-main)
  )
```

`defsuite` is actually a macro for defining a subclass of TestCase,
and `deftest` a test function, so within each test, you can refer to
`self` to invoke the assertions which are members of
`unittest.TestCase`.

## Setup and Teardown ##

You can technically define `setUp` and `tearDown` methods, using
`defsetup` and `defteardown`, like so:

```lisp
(defsuite TestSomething
  (defsetup
	(print "setting up")
	)

  (defteardown
    (print "tearing down")
	)
  )
```

These functions also have access to `self`, but aren't very useful
when testing side-effect free code. A better pattern might be a way to
define input data passed to all the test functions, but I haven't
quite figured out exactly how I'd want to do that.

## Main Function ##

As you can see in the original example, there is a macro named
`hytest-main` which you can use to invoke `unittest.main` on the
current module. Currently this macro takes no arguments, so you cannot
provide additional arguments to `unittest.main`.

The macro is necessary because, as of hy 0.9.10, the mechanism by
which `unittest` discovers test cases in the current module
(`__import__('__main__')`) is broken (the returned module has no
members.

## Nose Plugin ##

A nosetest plugin is also provided, to make it easier to run large
test suites across multiple files.

You can enable the plugin by passing the `--with-hynose` option to
nose, or setting `NOSE_WITH_HYNOSE` to true. It will run all files
named `test_*.hy`.

### Future Work ###

1) The standard options for defining test filename matches should be
honored.

repository: spiralman/hytest

repo_name: spiralman/hytest


text:
# Has Coverage of Online Harassment Grown Since 2014?

In this analysis, I use data from MediaCloud.org to test the hypothesis that coverage of online harassment grew from 1 Jan 2014 to 31 March 2016.

## Data Collection
Data was collected by searching the repository at MediaCloud.org for all sentences matching the following search query:

    “online harassment,”  “cyberbullying,” “online abuse,” “revenge porn,”
    “cyberstalking,” “online hate speech,” and “online racism”

The dataset included 24 US media sources, 95 UK media sources, and 1065 blogs and digital first media sources, for the period from 1 Jan 2014 to March 21, 2016..

![Online Harassment Sentences in US, UK, and Digital Media From 1 Jan 2014 to 31 March 2016](https://raw.githubusercontent.com/natematias/online-harassment-media-2014-2016/master/online_harassment_sentences_over_time.png)

## Analysis
This analysis uses a negative binomial model to test the null hypothesis that there is no relationship between the month since Jan 1 2014 and the number of sentences per region about online harassment in a given week. For more on count models, see:

    Long, J. Scott. 1997. Regression Models for Categorical and Limited Dependent Variables. 1 edition. Thousand Oaks: SAGE Publications, Inc.

## Results
The following R code was executed (see the attached R script).

    nb1 <- glm.nb(Total.Media ~ monthnum, data = weeks)
    nb2 <- glm.nb(UK.Media ~ monthnum, data = weeks)
    nb3 <- glm.nb(US.Media ~ monthnum, data = weeks)
    nb4 <- glm.nb(Digital.Media ~ monthnum, data = weeks)

    stargazer(nb1,nb2,nb3,nb4, type="text")

Model Results:

    =====================================================================================
                                              Dependent variable:
                      -------------------------------------------------------------------
                        Total.Media        UK.Media         US.Media      Digital.Media
                            (1)              (2)              (3)              (4)
    -------------------------------------------------------------------------------------
    monthnum              0.032***         0.039***         0.020***         0.036***
                          (0.006)          (0.007)          (0.006)          (0.007)

    Constant              4.898***         3.389***         3.864***         4.054***
                          (0.090)          (0.111)          (0.096)          (0.106)

    -------------------------------------------------------------------------------------
    Observations            117              117              117              117
    Log Likelihood        -696.264         -549.946         -563.244         -619.492
    theta             4.314*** (0.556) 2.935*** (0.395) 3.919*** (0.527) 3.125*** (0.402)
    Akaike Inf. Crit.    1,396.528        1,103.893        1,130.487        1,242.985
    =====================================================================================
    Note:                                                     *p<0.1; **p<0.05; ***p<0.01

When interpreting these results, remember that the incidence rate ratio is calculated with `exp(beta)`. For example, in the case of UK media, the coefficient of monthnum is 0.039, which means that the incidence rate ratio is 1.039. The final interpretation is that from month to month, the number of sentences about online harassment in UK media increased by a rate of 3.9% on average between 1 Jan 2014 and 31 March 2016, a relationship that is statistically significant.

Note also that this research makes no claims about the number of stories, or whether online harassment is growing. It is also possible that these findings reflect a change in the terms used to describe certain things rather than a change in the incidence of the underlying issues being described. I have attempted to account for this by using terms like cyberbullying and cyberstalking, which have a longer history.


text:
This sample Android app demonstrates
configuring how an input method editor (IME) interacts with an `EditText`.

This app is covered in
[the chapter on the input method framework](https://commonsware.com/Android/previews/the-input-method-framework)
in [*The Busy Coder's Guide to Android Development*](https://commonsware.com/Android/).

gha_language: Java


text:
---
id: gitlab
title: "GitLab CI with APIF-Auto"
sidebar_label: GitLab
keywords:
    - cicd
    - gitlab
    - apif-auto
    - yaml
---

APIF-Auto, a command line tool that supports automated API Fortress test execution is an ideal tool for executing API Fortress tests in a GitLab CI workflow.

The pipeline script below serves as a template for creating a stage in your GitLab Pipeline for testing your APIs with API Fortress. If you’d like to take a look at the documentation for APIF-Auto, click [here](/api-testing/mark2/ci/apif-auto).

> __NOTE__: It’s important to note that this is an **example** of a `.gitlab-ci.yml`.  Experienced GitLab CI users are free to configure their workflow as best suits their needs. Please mind the yaml formatting.

```yaml
image: "python 3.7"
before_script:
  - python --version
  - pip install -r requirements.txt
stages:
  - API Fortress
apif:
  stage: API Fortress
  script:
  - python directory/apif-run.py run-all ci_project -S -o output/directory
```

:::tip call APIs directly
You can configure the `yaml` file to make `curl` calls directly to the API Fortress API to achieve the same behavior.
:::

repository: leftxs/sauce-docs

repo_name: leftxs/sauce-docs


text:
# Javascript testing

Javascript tests use [konacha](https://github.com/jfirebaugh/konacha),
with mostly default settings, stored in `test/javascripts`.

Run the test server with:

```sh
bundle exec rake konacha:serve
```

You can now check out the tests in your browser at
[http://localhost:3500](http://localhost:3500).

repository: lucageo/ProtectedPlanet

repo_name: lucageo/ProtectedPlanet


text:
A non-standard Javadoc block tag was used.

```java
/**
 * @returns two times n
 */
int twoTimes(int n) {
  return 2 * n;
}
```

```java
/**
 * @return two times n
 */
int twoTimes(int n) {
  return 2 * n;
}
```

## Suppression

Suppress by applying `@SuppressWarnings("InvalidBlockTag")` to the element being
documented.

repository: tausiflife/error-prone

repo_name: tausiflife/error-prone


text:
---
title: Introducing Myself
layout: post
---

## Hi. I'm Casey.

It's been a long time since I've written with any expectation of an audience.
That isn't to say that I have expectations of readership even now, but at least I'm publishing again.
A blog may not be the most effective means -- but neither is a book, and people seem to get some traction with those.

The reason for this blog is that I have a deep need to contribute to positive social change, reveal the dark things that we all overlook, and try to get people _feeling and caring_.
If I could see a world I want, every eye would be filled with tears until none of them are.
I was born into this world very confused -- I had thought all through my childhood that, of course, everything would have an answer.

I thought that curiosity would be enough, up until I found the questions _nobody_ has ever answered.
Not the kind that bear out with study, like the color of the sky, but the kind that never do reveal their truths.

Questions of why people are made to suffer by way of other people not caring enough.
Questions of how it is that people will sell out their entire species and the planet just to keep a job.
Questions about inequality, human rights, and what heartlessness has covered this world.

I have very little to tell you about myself. But, I have a lot to say. You can call me Casey, if you must call me.

license: Unlicense

repository: NetizenAbel/lemmegoon

repo_name: NetizenAbel/lemmegoon


text:
---
date: 2020-01-12T09:05:10-04:00
description: "Learn Angular"
tags: [ "typescript", "web-dev" ]
title: "Angular (TypeScript Framework)"
---

# Angular (TypeScript Framework)

[Angular](https://angular.io/) is an application design framework for building [web](web-dev.md), mobile, and desktop applications with [TypeScript](typescript.md). It's most popular use is to develop web applications.

## Angular Resources

* [Angular Official Website](https://angular.io/)
* [Angular Documentation](https://angular.io/docs)
* [ng-conf YouTube Channel](https://www.youtube.com/channel/UCm9iiIfgmVODUJxINecHQkA)

gha_language: TypeScript


text:
# E-Commerce-Back-End [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

### Link to walkthrough video: https://drive.google.com/file/d/13eYgJzJn9Xo2leJcoMcYByYodEdjGPKX/view

# Table of Contents

- [Description](#description)
- [Installation](#installation)
- [Usage](#usage)
- [Contribution](#contribution)
- [Test](#test)
- [Questions](#questions)
- [License](#license)

## Description:
This project uses back end technologies to create and seed database tables and connects them using sequelize. Express is also used to perform RESTful CRUD operations.
## Installation:
express, mysql, and sequelize
## Usage:
This app simulates a real world e-commerce environment by testing routes using an API design platform such as Insomnia to create, read, update or delete a category, product, or tag.
## Contribution:
Refactor code and make pull request.
## Test:
No Tests.
## Questions:
- Visit my GitHub page: https://github.com/Bluekev22
- If you have any question please email me at<EMAIL_ADDRESS>## License:
This project is licensed under MIT: https://opensource.org/licenses/MIT