text:
generator-shields [![NPM version][npm-image]][npm-link]
=================

[![Dependency status][deps-image]][deps-link]
[![peerDependency status][peerdeps-image]][peerdeps-link]

> [Yeoman](http://yeoman.io) generator

Easily add shields to your README file. Available shields:

 * ![NPM version][npm-example] `--npm` current version in npm;
 * ![Build status][build-example] `--travis` current build status from [Travis CI](https://travis-ci.org/repositories);
 * ![Test coverage][coverage-example] `--coverage` test coverage from [Coveralls](https://coveralls.io);
 * ![Code climate][climate-example] `--climate` code climate rate from [Code Climate](https://codeclimate.com/);
 * ![Dependency status][deps-example] `--deps` dependencies from [David DM](https://david-dm.org/);
 * ![devDependency status][devdeps-example] `--devdeps` dev dependencies from [David DM](https://david-dm.org/);
 * ![peerDependency status][peerdeps-example] `--peerdeps` peer devdependencies from [David DM](https://david-dm.org/).

## Usage

```bash
npm install -g yo generator-shields
yo shields
```

## Getting Started

### What is Yeoman?

Trick question. It's not a thing.

Not every new computer comes with a Yeoman pre-installed. He lives in the [npm](https://npmjs.org) package repository. You only have to ask for him once, then he packs up and moves into your hard drive. *Make sure you clean up, he likes new and shiny things.*

```bash
npm install -g yo
```

### Yeoman Generators

Yeoman travels light. He didn't pack any generators when he moved in. You can think of a generator like a plug-in. You get to choose what type of application you wish to create, such as a Backbone application or even a Chrome extension.

To install generator-shields from npm, run:

```bash
npm install -g generator-shields
```

Finally, initiate the generator:

```bash
yo shields
```

### Getting To Know Yeoman

Yeoman has a heart of gold. He's a person with feelings and opinions, but he's very easy to work with. If you think he's too opinionated, he can be easily convinced.

If you'd like to get to know Yeoman better and meet some of his friends, [Grunt](http://gruntjs.com) and [Bower](http://bower.io), check out the complete [Getting Started Guide](https://github.com/yeoman/yeoman/wiki/Getting-Started).

## License

MIT

[npm-example]: https://isqua.github.io/generator-shields/shields/npm.svg
[build-example]: https://isqua.github.io/generator-shields/shields/build.svg
[coverage-example]: https://isqua.github.io/generator-shields/shields/coverage.svg
[climate-example]: https://isqua.github.io/generator-shields/shields/climate.svg
[deps-example]: https://isqua.github.io/generator-shields/shields/deps.svg
[devdeps-example]: https://isqua.github.io/generator-shields/shields/devdeps.svg
[peerdeps-example]: https://isqua.github.io/generator-shields/shields/peerdeps.svg
[npm-image]: https://img.shields.io/npm/v/generator-shields.svg?style=flat
[npm-link]: https://npmjs.org/package/generator-shields
[deps-image]: https://img.shields.io/david/isqua/generator-shields.svg?style=flat
[deps-link]: https://david-dm.org/isqua/generator-shields
[peerdeps-image]: https://img.shields.io/david/peer/isqua/generator-shields.svg?style=flat
[peerdeps-link]: https://david-dm.org/isqua/generator-shields#info=peerDependencies

repository: JohannesMatussek/generator-shields

repo_name: JohannesMatussek/generator-shields


text:
SLTC Core integration/staging repository
=======================================

SLTC Coin Features
- Anonymized transactions using our "Stealth Mode"
- Time Based Masternode Rewards - people who hold MN for a longer time can be rewarded more than others.
- Fast transactions or Flash Send.
- Masternode technology used to secure the network and provide the above features, each Masternode is secured
  with collateral of 6K SLTC

### Coin Specs

Algo	Lyra2z

Block Time	150 Seconds

Difficulty Retargeting	Every Block

Max Coin Supply (PoW Phase)	48,000,000 SLTC

Premine	2,500,000 (minus swap) SLTC

### Reward Distribution

PoW Phase

Block Height	Reward Amount	Notes	Duration (Days)

0-2	2,500,000 SLTC	Initial Premine	0 Days

2-100	1 SLTC	Instamine Protection	0 Days

200-500	3 SLTC	Instamine Protection

501-800	5 SLTC	Instamine Protection

801-2000	7 SLTC	Instamine Protection

2001-25,000	20 SLTC	Open Mining	 Approx 90 Days

PoS Phase

Block Height	Reward Amount

### PoW Rewards Breakdown

Block Height	Miner	Masternodes

2001-25,000	50% (10 SLTC)	50% (10 SLTC)

### PoS Rewards Breakdown

Phase	Block Height	Reward	Stakers	Masternodes

Phase 1	25,000-190,000	24 SLTC	50% (12 SLTC)	50% (12 SLTC)

Phase 2	190,000-380,000	20 SLTC	50% (10 SLTC)	50% (10 SLTC)

Phase 3	380,000-570,000	30 SLTC	50% (15 SLTC)	70% (15 SLTC)

Phase 4	570,000-950,000	24 SLTC	50% (12 SLTC)	50% (12 SLTC)

Phase 5	950,000-1.14M	20 SLTC	50% (10 SLTC)	50% (10 SLTC)

Phase 6	1.14M-1.33M	16 SLTC	50% (8 SLTC)	50% (8 SLTC)

Halves Every 190k blocks after block 1.33M

### MN Payments

- Masternode payments start from block 2001.

license: MIT

repository: SlateTeam/SlatechainCore

branch_name: refs/heads/master

extension: md

gha_license_id: MIT

license_type: permissive

repo_name: SlateTeam/SlatechainCore


text:
# Tick-Tock
## A clock made using P5js

**Try it out here:** [Clock](https://sanskarjaiswal2001.github.io/Tick-Tock/)

**Screenshot:**

<img height = 400 width = 500 src = "https://user-images.githubusercontent.com/63549695/125832441-3f3961c8-60ff-4374-b662-e98e9c5f762c.png">

branch_name: refs/heads/main


text:
redis-service
=============
redis-service

Redis wrapped into windows service

Install:

1) Download x86 or x86_64bit binaries (already precompiled for you) from /bin folder

2) Unpack on your machine or server

3) Execute with admin permissions RedisService.exe /install

4) Start service (from service manager or using "net start Redis" console command)

Enjoy.

# section 1

This is a test section only for testing. Please ignore

repository: selvabrillio/redis-service

repo_name: selvabrillio/redis-service


text:
# zwave2mqtt

This project allows to deploy zwave sensor network on Raspberry Pi 0w with docker and docker-compose. To manage collected data, a local brocker is installed (mosquitto).

## Getting Started

To deploy the service, you need to install raspbian on your Raspberry Pi 0w : [download raspbian](https://www.raspberrypi.org/downloads/raspbian/)

### Prerequisites

Update your platform and install git to clone the project :

```
sudo apt update
sudo apt upgrade
sudo apt install git
```

### Installing

To deploy the service, you don't need to install any source. All installations will be managed by docker. Each configuration wil be managed by docker-compose. To install these two tools, you can run `install.sh`

```
cd ~/zwave2mqtt
sudo bash install.sh
sudo reboot
```

## Running the service

Go to your project and launch docker-compose :

```
cd ~/zwave2mqtt
docker-compose up -d
```

### Tests

After deploying the service, in your browser, you can go to the page : http://`$YOUR_IP`:8091

[HOME_PAGE_PNG](https://hub-creatif.cetic.be/sites/default/files/inline-images/oooo.PNG)

## Configuration

For configuration and more details on ZWave deployement, go to this page and see Step 2 (French link) : http://hub-creatif.ext.cetic.be/node/2

The configuration explains how to:
* Manage your ZWave network
* Configure your MQTT installation
* Customize your gateway service

## Built With

* [Docker](https://www.docker.com/) - Use to deploy the services
* [Docker-Compose](https://docs.docker.com/compose/) - Use to manage the services
* [Mosquitto](https://mosquitto.org/) - MQTT brocker Use to share data
* [ZWavetoMqtt](https://github.com/OpenZWave/Zwave2Mqtt) - Project source

## Authors

* **Benjmain Bernaud** - *Initial work* - [contact](https://github.com/bbenjamin11)

See also the list of [contributors](https://github.com/cetic/zwave2mqtt/graphs/contributors) who participated in this project.

## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details


text:
# image-semantic-segmentation

This project is initiated because of the attendence of Kaggle competetion - [Carvarna](https://www.kaggle.com/c/carvana-image-masking-challenge).

If you are installing tensorflow in virtualenv, please execute pip install --upgrade tensorflow-gpu for GPU support.


text:
#Tutorial xml-xml02 - Handling Sales Orders with XML
COMP4711 - BCIT - Fall 2016

##Planning

Let's plan a few things before we start modifying code.

We have a shopping page, after completing either lab 6 or lab 7, looking somewhat like:

We want to make the menu item icons "live", so that clicking on one adds one
of that item to an in-progress order.

I want to store the order as an XML
document, because it suits the rich structure of an order, with nested items.
The SQL file I provided earlier has Orders and Orderitems tables, which
would be one good way to handle saving orders if we were to use an RDB.
But that needs two tables. The Orderitems table would be an associative
table, because an order could refer to multiple menu items, and a menu item
could appear in multiple orders. So ... XML makes sense for data representation,
in this case.

The second thing I want to plan is how the shopping page should work,
generally. I would like it to display the current ordering page (but "live")
if we are in the process of entering an order, or else a summary of the orders
processed already, if no order is underway. We can tell the state we are in
by testing if the session contains an order object, the same way
we did for menu maintenance last week.

What we want to do should be clear - how we go about it is the fun part :)

##1. State-Driven Shopping Controller

Starting this tutorial, your controllers/Shopping.php should look something like...

    class Shopping extends Application {

	function __construct() {
		parent::__construct();
	}

	public function index() 	{
            $stuff = file_get_contents('../data/receipt.md');
            $this->data['receipt'] = $this->parsedown->parse($stuff);
            $this->data['content'] = '';

            // pictorial menu
            $count = 1;
            foreach ($this->categories->all() as $category) {
                    $chunk = 'category' . $count;
                    $this->data[$chunk] = $this->parser->parse('category-shop',$category,true);
                    foreach($this->menu->all() as $menuitem) {
                            if ($menuitem->category != $category->id) continue;
                            $this->data[$chunk] .= $this->parser->parse('menuitem-shop',$menuitem,true);
                    }
                    $count++;
            }
            $this->render('template-shopping');
	}
    }

To refresh your memory, the default action of the controller is
- to retrieve a "receipt" markdown file, the parsed contents of which are passed as the "receipt" view parameter
- to create an empty "content" view parameter, to prevent the base controller trying to parse a "pagebody"
- create a "chunk" view parameter which combines smaller view fragments for
menu categories and menu items
- and then to render the page sing the shopping template.

We don't want to throw this code away, but we only want to show it if the
user is in the middle of an order. We can tell that by testing if there is an
"order" item in the session. If so, display the menu as above; if not, display a summary
of the orders processed so far.

We can start down this road by replacing the beginning of the index()
with a suitable test and then calling the appropriate method.

	public function index() {
		// What is the user up to?
		if ($this->session->has_userdata('order'))
			$this->keep_shopping();
		else $this->summarize();
	}

	public function summarize() {
		$this->data['content'] = 'we need to flesh this out';
		$this->render('template');  // use the default template
	}

	public function keep_shopping() {
        $stuff = file_get_contents('../data/receipt.md');
        ...

Try this. The result isn't very exciting or informative, but
should be what we expect at this point.

By the way, if you find the page rendering time message annoying, feel
free to remove it from your templates :-/

##2. Order Model

We're not going to get too much further without a model, so let's
start on that. It will encapsulate the state of an order, but
isn't meant to be tied to a relational database table.

Looking at the receipt shown previously, we need to keep track of the
order date & time (when created), and a collection of items that
make up that order. The order total can be calculated from the items.

There should be no mention of XML, as we are not dealing with persistence yet.
This suggests the following starting point, models/Order.php:

    <?php
    class Order extends CI_Model {

            // constructor
            function __construct() {
                parent::__construct();
                $this->number = 0;
                $this->datetime = null;
                $this->items = array();
            }
    }

That's it? Yes, we can set the date/time, and assign an order #, when we save it.
Very minimalist - love it!

Note that is it nowhere near as formal as an entity model in many environments.
There is nothing wrong with planning all the properties ahead of time, making protected variables
for each, and then having getters and setters ... it doesn't add to what we
are trying to do in the tutorial, however.

##3. Start a new order

It is time to provide for an order summary view, although the only thing we know
for sure is that we need to be able to start a new order, which can be done
with a button link.

Not very impressive, but we can add views/summary.php:

Orders Processed So Far

    Start a New Order

We will need a new method in our Shopping controller to deal with this.

    public function neworder() {
        // create a new order if needed
        if (! $this->session->has_userdata('order')) {
            $order = new Order();
            $this->session->set_userdata('order',$order);
        }

        $this->keep_shopping();
    }

Did you remember to autoload the Order model?

Fix the Shopping summarize() so that it loads our
new view fragment instead of a hokey message:

	public function summarize() {
		$this->data['pagebody'] = 'summary';
		$this->render('template');  // use the default template
	}

Reloading the shopping page should show our empty order list, and our button:

Clicking on the button will lead to the original shopping page :)

##4. Changing Our Mind?

What if we want to cancel an order? This would be good for testing too :)

We didn't provide a separate single view fragment for shopping,
opting for a view fragment for each menu category and one for a receipt.

The easiest way to deal with cancelling an order is to add
a button in our views/template-shopping, at the proper spot:

    ...
                            {category3}

                     Cancel This Order

            {receipt}
            ...

We can then add a cancel() method to the Shopping
controller:

	public function cancel() {
		// Drop any order in progress
		if ($this->session->has_userdata('order')) {
			$this->session->unset_userdata('order');
		}

		$this->index();
	}

Try it! You should be able to start and cancel orders at will,
effectively toggling between the order summary and the shopping page :)

##5. Adding an Item to an Order

My "vision" is that each time we click on a menu item
on the shopping menu, one of that item gets added to the order.

We will need to deal with that in our Order model!

My intent is that the array of items in an order would be indexed
by menu item code, and that the value would be the number of that
menu item to go in the order. Simplistic, for sure, but complexity
can be added later if you like.

Our Order will need a new method for this:

	public function addItem($which=null) {
		// ignore empty requests
		if ($which == null) return;

		// add the menu item code to our order if not already there
		if (!isset($this->items[$which]))
			$this->items[$which] = 1;
		else {
			// increment the order quantity
			$this->items[$which]++;
		}
	}

We don't know if this works yet ... time to test it.

##6. Enable Menu Item Buttons

Our menu is shown as the images of each menu item available, organized
into columns by category. This is managed by the views/menuitem-shop view
fragment, and the individual menu items are passed to the view fragment
in Shopping::keep_shopping().

The view fragment right now should look like:

This needs to be made into a link, bound to a suitable method inside our controller.

... and the handling method inside the controller:

	public function add($what) {
		$order = $this->session->userdata('order');
		$order->additem($what);
		$this->keep_shopping();
	}

If we try to add an item to our order, however, our webapp blows up :(

Oh dear! Saving objects in a session is more complicated in PHP than
it is in Java :(

The solution: save the object as an array in the session,
and recreate it from the array state when we get it out of the session.

This will involve changing the Shopping::neworder() method:

    $this->session->set_userdata('order', (array) $order);

and the Shopping::add() methid:

    $order = new Order($this->session->userdata('order'));

and we need to beef up our Order constructor:

	// constructor
	function __construct($state=null) {
		parent::__construct();
		if (is_array($state)) {
			foreach($state as $key => $value)
				$this->$key = $value;
		} else {
			$this->number = 0;
			$this->datetime = null;
			$this->items = array();
		}
	}

Make these changes, cancel your order, and try again.

It no longer blows up, but how do we see what is in an order?

Ah - we didn't save the updated order in the session.
We can add that to Shopping::add():

		$this->session->set_userdata('order',(array)$order);

That may be an improvement, but there is no visible difference after making this change.
Did we actually add anything??

##7. Show Order Receipt

Hmmm - the right column in our shopping page is supposed to show the
in-progress order. It sounds like we need to generate that inside our Order
class now, and modify the Shopping controller to
use the order-generated receipt rather than the fake one we had before.

Our Order can generate a text receipt in markdown format,
loosely modeled after what you have in your fake receipt.

Mine would be something like:

	public function receipt() {
		$total = 0;
		$result = $this->data['pagetitle'] . '  ' . PHP_EOL;
		$result .= date(DATE_ATOM) . PHP_EOL;
		$result .= PHP_EOL . 'Your Order:'. PHP_EOL . PHP_EOL;
		foreach($this->items as $key => $value) {
			$menu = $this->menu->get($key);
			$result .= '- ' . $value . ' ' . $menu->name . PHP_EOL;
			$total += $value * $menu->price;
		}
		$result .= PHP_EOL . 'Total: $' . number_format($total, 2) . PHP_EOL;
		return $result;
	}

Use this in place of the dummy receipt, with a slight change inside
Shopping::keep_shopping():

	public function keep_shopping() {
            $order = new Order($this->session->userdata('order'));
            $stuff = $order->receipt();
            $this->data['receipt'] = $this->parsedown->parse($stuff);
        ...

My shopping page now shows my receipt:

Yours would show your diner name, of course, and would reflect what you have put into
your order :) You can play with different date formatting constants, or
even build your own, inside the receipt generation - up to you.

##8. Initiate Order Checkout

Ok - we are ready to take money from our customers :)

We need to add a "checkout" button on the shopping page.
I suggest the easiest place for that is beside the "Cancel this order"
button that we added earlier.

You are probably feeling that hard-coded buttons inside a template is a
bad practice, and you are correct. Fixing that, with a different view
fragment, for instance, is a task for another day :-/

Inside our views/template-shopping.php,
we need to add another line above the  button link we added in step 4.

             Checkout
             Cancel This Order

Reload the shopping page and ...

Woohoo!

Wait a minute ... have you noticed anything funny?
When we added an item, the browser location field changed to
".../shopping/add/...". Whenever we reload the page, we are adding
another of the last menu item we added to our order.
With my testing, I am up to an order which includes six turkeys!

Oops! At the end of Shopping::add,
we should redirect to the shopping page, rather than simply
rendering the menu.

		redirect('/shopping');

That will fix that problem :-/

##9. Handle Order Checkout

What about actually checking out? We need to see if we are ready to check
out, and then we need to save the order if so.

The boss has dictated that an order has to have at least one menu item
from each menu category in order to be acceptable.

We should add some validation to the Order to test that:

	// test for at least one menu item in each category
	public function validate() {
		// assume no items in each category
		foreach($this->categories->all() as $id => $category)
			$found[$category->id] = false;
		// what do we have?
		foreach($this->items as $code => $item) {
			$menuitem = $this->menu->get($code);
			$found[$menuitem->category] = true;
		}
		// if any categories are empty, the order is not valid
		foreach($found as $cat => $ok)
			if (! $ok) return false;
		// phew - the order is good
		return true;
	}

We can use this inside the Shopping::checkout handling.
Cheesy, in that we ignore invalid orders, but ...

	public function checkout() {
		$order = new Order($this->session->userdata('order'));
		// ignore invalid requests
		if (! $order->validate())
			redirect('/shopping');

		$this->data['content'] = 'Ready for checkout.';
		$this->render();
	}

You were probably wondering when XML would come into play
in the tutorial. Now is the time, as we need to save the order.
We will add an Order::save() method to
create an appropriate XML document and store it :)
This will draw on the XML processing lesson, and on the
example-simplexml repository discussed in class.

	public function save() {
		// figure out the order to use
		while ($this->number == 0) {
			// pick random 3 digit #
			$test = rand(100,999);
			// use this if the file doesn't exist
			if (!file_exists('../data/order'.$test.'.xml'))
					$this->number = $test;
		}
		// and establish the checkout time
		$this->datetime = date(DATE_ATOM);

		// start empty
		$xml = new SimpleXMLElement('<order/>');
		// add the main properties
		$xml->addChild('number',$this->number);
		$xml->addChild('datetime',$this->datetime);
		foreach ($this->items as $key => $value) {
			$lineitem = $xml->addChild('item');
			$lineitem->addChild('code',$key);
			$lineitem->addChild('quantity',$value);
		}

		// save it
		$xml->asXML('../data/order' . $this->number . '.xml');
	}

There are a number of improvements that could be made to this,
but there is only so much time to work on it :-/

With the saving ready, our Shopping::checkout()
can be modified to use it.

	public function checkout() {
		$order = new Order($this->session->userdata('order'));
		// ignore invalid requests
		if (! $order->validate())
			redirect('/shopping');

		$order->save();
		$this->session->unset_userdata('order');
		redirect('/shopping');
	}

Note: you may find that you get a permission error trying to save
the order file inside your data folder, and you
may have to make the folder writeable :-/

##10. Fix the Order Summary

After saving an order, the only way we can find out if it worked is by checking
our data folder :( We need to show a list of the orders
on the shopping page, when we aren't in the middle of creating a new one.

We need to find all the order files in our data file, open each up
as an Order object,
and a one-line summary for it.

First up is enhancing the Order constructor (again), so that it can
retrieve its state from a stored XML document. Do this by passing the name
of the file to the constructor...

	// constructor
	function __construct($state=null) {
		parent::__construct();
		if (is_array($state)) {
			foreach($state as $key => $value)
				$this->$key = $value;
		} elseif ($state != null) {
			$xml = simplexml_load_file($state);
			$this->number = (int) $xml->number;
			$this->datetime = (string) $xml->datetime;
			$this->items = array();
			foreach ($xml->item as $item) {
				$key = (string) $item->code;
				$quantity = (int) $item->quantity;
				$this->items[$key] = $quantity;
			}
		} else {
			$this->number = 0;
			$this->datetime = null;
			$this->items = array();
		}
	}

Before we dive into our controller, we should plan how we are going to
preent the order summary. I suggest changing views/summary.php
to provide for iterating over order lines that we will need to create.

Orders Processed So Far

Order #	Date/time	Amount

    {orders}

                {number}
                {datetime}
                {total}

    {/orders}

    Start a New Order

This is perfect, well except for having any data :-/

Now we can beef up the Shopping::summarize(), to provide
the data to report. From the planned view,
we know we need to build an associative array of arrays.

	public function summarize() {
		// identify all of the order files
		$this->load->helper('directory');
        $candidates = directory_map('../data/');
		$parms = array();
        foreach ($candidates as $filename) {
		   if (substr($filename,0,5) == 'order') {
			   // restore that order object
			   $order = new Order ('../data/' . $filename);
			// setup view parameters
			   $parms[] = array(
				   'number' => $order->number,
				   'datetime' => $order->datetime,
				   'total' => $order->total()
					   );
		    }
	    }
		$this->data['orders'] = $parms;
		$this->data['pagebody'] = 'summary';
		$this->render('template');  // use the default template
	}

Ohoh - I planned to add a total() method to the Order
class, but forgot to do so. That would be...

	public function total() {
		$total = 0;
		foreach($this->items as $key => $value) {
			$menu = $this->menu->get($key);
			$total += $value * $menu->price;
		}
		return $total;
	}

That's more like it!

##11. Examine an Old Order?

It would be nice to see the details of a processed order, for confirmation.
Let's add a link to the line for each order displayed in the summary,
and have that trigger a recreated receipt for that order.

Modify the summary view fragment, embedding the order # in a link...

            {number}
            {datetime}
            {total}

Add an examine method to your shopping controller...

    public function examine($which) {
        $order = new Order ('../data/order' . $which . '.xml');
        $stuff = $order->receipt();
        $this->data['content'] = $this->parsedown->parse($stuff);
        $this->render();
    }

And ...

The change to have the order # show up, like it does, is not in the above;
that is something for you to figure out! :)

##12. Are We Safe?

You should have a functional shopping page by now.
We can only add to an order, and not remove items if we change our mind,
but we are functional, and the orders are stored in and retrieved from
XML documents :)

I was pleasantly surprised at how small a role XML played, but it "feels right".


text:
[![Build Status](https://github.com/Yelp/fuzz-lightyear/actions/workflows/fuzz-lightyear-build.yml/badge.svg)](https://github.com/Yelp/fuzz-lightyear/actions/workflows/fuzz-lightyear-build.yml)

# fuzz-lightyear

fuzz-lightyear is a [pytest-inspired](https://docs.pytest.org/en/latest/),
[DAST](https://en.wikipedia.org/wiki/Dynamic_Application_Security_Testing) framework,
capable of identifying vulnerabilities in a distributed, micro-service ecosystem through
**stateful** [Swagger](https://swagger.io/) fuzzing.

**What's Special About Stateful Fuzzing?**

Traditional fuzzing operates on the assumption that a command invocation failure is
indicative of a vulnerability. This approach does not carry over to web service fuzzing
since failures are **expected** to happen on bad input -- in fact, successful requests
with a purposely malicious payload is so much more dangerous, and should be caught
accordingly.

Stateful fuzzing allows us to do this. By keeping state between requests, we can assemble
a request sequence, and craft it to simulate a malicious attack vector and alert off
unexpected success. Using [hypothesis testing](https://hypothesis.readthedocs.io/en/latest/),
we're able to dynamically generate these test cases so we can continue to discover new
vectors. Finally, when we find an error, this testing framework outputs a list of cURL
commands for easy reproduction.

## Example

```
$ fuzz-lightyear https://petstore.swagger.io/v2/swagger.json -v --ignore-exceptions
```

## Installation

```
pip install fuzz-lightyear
```

## Usage

```
$ fuzz-lightyear -h

usage: fuzz-lightyear [-h] [-v] [--version] [-n [ITERATIONS]] [--schema SCHEMA]
                   [-f FIXTURE] [--seed SEED] [-t TEST] [--ignore-exceptions]
                   [--disable-unicode]
                   url

positional arguments:
  url                   URL of server to fuzz.

optional arguments:
  -h, --help            show this help message and exit
  -v, --verbose         Increase the verbosity of logging.
  --version             Displays version information.
  -n [ITERATIONS], --iterations [ITERATIONS]
                        Maximum request sequence length to fuzz.
  --schema SCHEMA       Path to local swagger schema. If provided, this
                        overrides theswagger file found at the URL.
  -f FIXTURE, --fixture FIXTURE
                        Path to custom specified fixtures.
  --seed SEED           Specify seed for generation of random output.
  -t TEST, --test TEST  Specifies a single test to run.
  --ignore-exceptions   Ignores all exceptions raised during fuzzing (aka.
                        only fails when vulnerabilities are found).
  --disable-unicode     Disable unicode characters in fuzzing, only use ASCII.

```

## Fixtures

Fixtures are a core component of `fuzz-lightyear`, and allow you to customize factories to
supplement fuzzing efforts for various endpoints. This is fundamentally important for
micro-service ecosystems, since services may not be CRUD applications by themselves.
This means the endpoints to create transient resources as part of the request sequence may
not be available in the Swagger specification.

To address this, we allow developers to supply custom commands necessary to populate
certain parts of the fuzzed request parameters.

### Example

Let's say that we have the following Swagger snippet:

```yaml
paths:
  /biz_user/{userID}/invoices:
    get:
      tags:
        - business
      operationId: "get_business_by_id"
      parameters:
        - name: "userID"
          in: "path"
          required: true
          type: integer
      responses:
        200:
          description: "success"
        403:
          description: "forbidden"
        404:
          description: "business not found"
```

We need a valid `userID` to access its invoices. Clearly, it would be a waste of time
for the fuzzer to put random values for the `userID`, because we don't care if an
attacker tries to access a business that doesn't exist. Moreover, this service
doesn't understand how to create a business (to obtain a valid `userID`), so the fuzzer
will not be effective at testing this endpoint.

To address this issue, we define a fixture to tell `fuzz-lightyear` how to handle such
cases.

```python
# fixtures.py
import fuzz_lightyear

@fuzz_lightyear.register_factory('userID')
def create_biz_user_id():
    return 1
```

Now, when `fuzz-lightyear` tries to fuzz `/biz_user/{userID}/invoices`, it will
identify that there's a user-defined factory for `userID`, and use its value in
fuzzing.

```bash
$ fuzz-lightyear -f fixtures.py http://localhost:5000/schema -v
================================== fuzzing session starts ==================================
Hypothesis Seed:<PHONE_NUMBER>48224061420843471695694220247

business E
====================================== Test Failures =======================================
_________________________ business.get_business_by_id [IDORPlugin] _________________________
Request Sequence:
[
  "curl -X GET http://localhost:5000/biz_user/1/invoices"
]
================================== 1 failed in 1.2 seconds =================================
```

We can amend this example by specifying a custom method to create a business in the
`create_business` function.

### Nested Fixtures

In keeping with the example above, let's say that you needed a business first, before you
can create a biz_user. We can accomplish this in the following method:

```python
# fixtures.py
import fuzz_lightyear

@fuzz_lightyear.register_factory('userID')
def create_biz_user_id(businessID):
    return businessID + 1

@fuzz_lightyear.register_factory('businessID')
def create_business():
    return 1
```

Then,

```bash
$ fuzz-lightyear -f fixtures.py http://localhost:5000/schema -v
================================== fuzzing session starts ==================================
Hypothesis Seed:<PHONE_NUMBER>48224061420843471695694220247

business E
====================================== Test Failures =======================================
_________________________ business.get_business_by_id [IDORPlugin] _________________________
Request Sequence:
[
  "curl -X GET http://localhost:5000/biz_user/2/invoices"
]
================================== 1 failed in 1.2 seconds =================================
```

We can also do type-casting of nested fixtures, through the use of **type annotations**.

```python
# fixtures.py
import fuzz_lightyear

@fuzz_lightyear.register_factory('userID')
def create_biz_user_id(businessID: str):
    return businessID + 'a'

@fuzz_lightyear.register_factory('businessID')
def create_business():
    return 1
```

Which will produce:

```bash
$ fuzz-lightyear -f fixtures.py http://localhost:5000/schema -v
================================== fuzzing session starts ==================================
Hypothesis Seed:<PHONE_NUMBER>48224061420843471695694220247

business E
====================================== Test Failures =======================================
_________________________ business.get_business_by_id [IDORPlugin] _________________________
Request Sequence:
[
  "curl -X GET http://localhost:5000/biz_user/1a/invoices"
]
================================== 1 failed in 1.2 seconds =================================
```

### Endpoint Specific Fixtures
Let's say that we have another endpoint , `get_user_by_id`, that requires a different kind of `userID`. We can't use the existing `userID` fixture, since it generates the wrong type of ID. We can solve this by writing an endpoint specific fixture.

```python
# fixtures.py
import fuzz_lightyear

@fuzz_lightyear.register_factory('userID')
def create_biz_user_id(businessID):
    return businessID + 1

@fuzz_lightyear.register_factory('userID', endpoint_ids=['get_user_by_id'])
def create_user_id():
    return 'foo'

@fuzz_lightyear.register_factory('businessID')
def create_business():
    return 1
```

Which will produce:

```bash
...
_________________________ user.get_user_by_id [IDORPlugin] _________________________
Request Sequence:
[
  "curl -X GET http://localhost:5000/user/foo"
]
================================== 1 failed in 1.2 seconds =================================
```

We can combine this with nested fixtures as well, but if we specify an endpoint in a fixture, every fixture that depends on that fixture will also need to specify the endpoint.

```python
# fixtures.py
import fuzz_lightyear

# We have to specify get_business_by_id here!
@fuzz_lightyear.register_factory('userID', endpoint_ids=['get_business_by_id'])
def create_biz_user_id(businessID):
    return businessID + 1

@fuzz_lightyear.register_factory('businessID', endpoint_ids=['get_business_by_id'])
def create_business():
    return 1
```

Which will produce:

```bash
...
_________________________ user.get_user_by_id [IDORPlugin] _________________________
Request Sequence:
[
  "curl -X GET http://localhost:5000/biz_user/2/invoices"
]
================================== 1 failed in 1.2 seconds =================================
```

### Authentication Fixtures

We can use fixtures to specify authentication/authorization methods to the Swagger
specification. This allows developers to customize the use of session cookies, or API
tokens, depending on individual use cases.

These fixtures are required for the `IDORPlugin`. We can include an `operation_id` argument in the fixture so that the operation id is automatically passed in. Other arguments will not be fuzzed.

```python
"""
These values are passed into the configured request method as keyword arguments.
Check out https://bravado.readthedocs.io/en/stable/advanced.html#adding-request-headers
for more info.
"""
import fuzz_lightyear

@fuzz_lightyear.victim_account
def victim_factory():
    return {
        '_request_options': {
            'headers': {
                'session': 'victim_session_id',
            },
        }
    }

@fuzz_lightyear.attacker_account
def attacker_factory():
    return {
        '_request_options': {
            'headers': {
                'session': 'attacker_session_id',
            }
        }
    }
```

### Setup Fixtures

We can use setup fixtures to specify code that we'd like to run _before_ any
tests are run. This allows developers to setup any custom configuration or
external applications the test application relies on.

```python
import fuzz_lightyear

@fuzz_lightyear.setup
def setup_function():
    print("This code will be executed before any tests are run")
```

### Including and excluding Swagger tags and operations

We can use fixtures to control whether fuzz-lightyear fuzzes certain parts of
the Swagger specification. This allows developers to only fuzz the parts
of the specification that can be fuzzed in the test environment.

```python
import fuzz_lightyear

@fuzz_lightyear.include.tags
def get_tags_to_fuzz():
    """fuzz_lightyear will only fuzz operations from
    these tags.
    """
    return ['user', 'transactions']

@fuzz_lightyear.exclude.operations
def get_operations_to_exclude():
    """fuzz_lightyear will not call these Swagger
    operations.
    """
    return [
        'get_user_id',
        'operation_doesnt_work_in_test_environment',
    ]

@fuzz_lightyear.exclude.non_vulnerable_operations
def get_non_vulnerable_operations():
    """fuzz_lightyear will not check these Swagger
    operations for vulnerabilities.

    This is different from `fuzz_lightyear.exclude.operations`
    in that these operations can still be executed by the
    fuzzer to generate request sequences, but the vulnerability
    plugins will not verify that these operations are secure.
    """
    # Accessing a user's public profile shouldn't require
    # authentication.
    return ['get_user_public_profile']
```

### Post-fuzz hooks

Sometimes factory fixtures and random fuzzing are not sufficient to
build a valid request. For example, the API could have an undeclared
required header, and it is unfeasible to add the header to the
Swagger spec. In this case, we can use post-fuzz hooks to transform
fuzzed data to a valid form.

```python
@fuzz_lightyear.hooks.post_fuzz(
    tags='user',
    operations='some_function',
    rerun=True,
)
def apply_nonce(
    operation: bravado.client.CallableOperation,
    fuzzed_data: Dict[str, Any],
) -> None:
    """This hook creates and adds a nonce to any request against
    operations with the 'user' tag, and additionally to the
    'some_function' operation.

    In addition, this nonce cannot be reused by a fuzz-lightyear
    request object, so we mark this hook is needing to be `rerun`.
    """
    nonce = make_nonce()
    fuzzed_data['nonce'] = nonce
```

Note: The order in which these hooks are run is not guaranteed.

repository: Yelp/fuzz-lightyear

gha_language: Python

gha_license_id: NOASSERTION

repo_name: Yelp/fuzz-lightyear


text:
# <img src="images/icon-64.png" width="32" height="32" align="baseline" alt="Add to Things logo"> Add to Things

Adds currently opened page to [Things](http://culturedcode.com/things/) task manager for macOS. Page title goes to task title, URL and selected text both go to notes. Available for [Chrome](https://chrome.google.com/webstore/detail/add-to-things/bfbgliglkhckblibeiojndpncmahbmpo), [Firefox](https://addons.mozilla.org/en-US/firefox/addon/add-2-things/) and [Opera](https://addons.opera.com/en/extensions/details/add-to-things/).

![Add to Things in Chrome](pictures/chrome.png)

![Add to Things in Firefox](pictures/firefox.png)

![Add to Things in Opera](pictures/opera.png)

---
Licensed under MIT License

repository: bowlingmh/add-to-things

repo_name: bowlingmh/add-to-things


text:
#Slug Validator

This validator can be used to ensure that the given value is a valid __slug__. If you don't know what a slug is, kindly read about it [here](https://en.wikipedia.org/wiki/Slug "Slug Background")

[**Back to Validators List**](./reference.md#validators-list)

## Usage
There are two different ways in which all Sparta validators can be used. See below examples for more explanations:

### Example #1:
You can simply instantiate the `Slug` validator and pass to it the data that you want to validate.

```php
<?php
use Sparta\Validators\Slug;

$validator = Slug();

if(!$validator->isValid('This-is-Slug')){
	//handle errors
}
```

### Example #2:
You can build your validation rules and pass it to the __Validation__ object to handle as shown below:

```php
<?php
use Sparta\Validation;

$rules = [
	'articleSlug' => 'slug',
];

//Assuming that your $data has an element with the key "title_slug"

$validation = new Validation($data, $rules);
if(!$validation->isValid()){
	//handle errors
}

```

In case of validation failure, error messages can be retrieved using the `getErrors` method.

[**Back to Validators List**](./reference.md#validators-list)

repository: coderavine/sparta

repo_name: coderavine/sparta


text:
# Overview

The gold standard Stax XML API implementation. Now at Github.

# Fork

Forked from https://github.com/FasterXML/woodstox
Modified to not normalize `\n` in attribute values.

# Get it!

## Maven

The most common way is to use Maven (or Ivy) to access it from Maven Central repository.
Coordinates for this are:

* Group id: `com.scalableminds`
* Artifact id: `woodstox-core`
* Latest published version: 5.2.0-SCM (August 2018)

Note that Maven id has changed since Woodstox 4.x.

## Requirements

Woodstox 5 and above require Java 6 (JDK 1.6); as well as Stax API that is included in JDK.
The only other mandatory dependence is [Stax2 API](../../../stax2-api), extended API implemented by Woodstox
and some other Stax implementations (like [Aalto](../../../aalto-xml).

Optional dependency is [Multi-Schema Validator (MSV)](https://github.com/kohsuke/msv) that is needed if
using XML Schema or RelaxNG validation functionality

## License

Woodstox 5.x is licensed under [Apache 2](http://www.apache.org/licenses/LICENSE-2.0.txt) license.

## Documentation etc

* User mailing list for Qs: [woodstox-user](https://groups.google.com/forum/#!forum/woodstox-user) Google group
* Check out [project Wiki](../../wiki) for javadocs

repository: scalableminds/woodstox

repo_name: scalableminds/woodstox


text:
### Meta-DRN: Meta-Learning for 1-Shot Image Segmentation

[](https://www.arxiv.org/abs/2008.00247)

[](https://www.pytorch.org/) [](https://www.pytorchlightning.ai/) [](https://www.tensorflow.org/tensorboard) [](https://github.com/facebookresearch/higher)

---

### Description

PyTorch implementation of the paper [Meta-DRN: Meta-Learning for 1-Shot Image Segmentation]("https://arxiv.org/abs/2008.00247")

### How to train the model

First install dependencies

```bash
# clone project
git clone https://github.com/RashedDoha/meta-drn-pytorch

# install project dependencies
cd meta-drn-pytorch
pip install -r requirements.txt
```

Next navigate to train.py and run it to train the model

```bash

# training script

cd training

python train.py

```

repository: RehmaRizvi/meta-drn-pytorch

repo_name: RehmaRizvi/meta-drn-pytorch


text:
# _{My Portfolio}_

#### _{Portfolio webpage}, {May 26, 2017}_

#### By _**{Anna Kuznetsova}**_

## Description

_{This is a webpage shows my projects and interest. Click on the image links to look through my work. }_

## Setup/Installation Requirements

* _Click on URL_

## Technologies Used

_{HTML, CSS, Bootstrap.}_

### License

*{This webpage is licensed under the MIT license}*

Copyright (c) 2017 **_{Anna Kuznetsova}_**

repository: codingkuzzi/MyPortfolio

repo_name: codingkuzzi/MyPortfolio


text:
# AppDev-WRL7 Native Build VirtualBox VM

This README file describes the process to use the AppDev-WRL7 Native Build VirtualBox VM and shows how to build a sample application using the Native toolchains bundled in the VM.

# Pre-Built (Ready-to-use) AppDev-WRL7 Native Build Artifacts

Pre-Built (Ready-to-use) Version 1.0 AppDev-WRL7 Native Build Artifacts are available at http://engci-maven-master.cisco.com/artifactory/simple/appdevci-release/AppDev-WRL7/1.0/.

We recommend that you use Version 1.0 artifacts as per instructions provided below.

# Building AppDev-WRL7 Native Build VM box image from WRL7 ISO

Note: Users of AppDev-WRL7 Native Build VM do not need to do this, as they can directly download an existing box. If that is what you want to do, just go to the Section "Using the AppDev-WRL7 Native Build VM, given the box file"

First download the ISO.

```
cd <path-to-iso\
curl -O http://engci-maven-master.cisco.com/artifactory/simple/appdevci-release/AppDev-WRL7/1.0/wrlinux-image-installer-intel-x86-64-20160411171331.iso
```

Now build an AppDev-WRL7 Native Build VM box image, using wrl7vbox tool. Please be patient as wrl7vbox tool will take about 10-15 minutes to generate the vbox image.

The wrl7vbox.sh tool is available at https://github.com/ios-xr/iosxr-appdev-vbox and can be used as shown below.

```
git clone https://github.com/ios-xr/iosxr-appdev-vbox
cd iosxr-appdev-vbox
./wrl7vbox.sh -name AppDev-WRL7 -iso <path-to-iso>/wrlinux-image-installer-intel-x86-64-20160411171331.iso
```

# Using the AppDev-WRL7 Native Build VM, given the box image

Users of AppDev-WRL7 Native Build VM have multiple ways available to them. One can build the box as described in previous section and use that box. Or one can down the box from Cisco artifactory location -  http://engci-maven-master.cisco.com/artifactory/simple/appdevci-release/AppDev-WRL7/1.0/AppDev-WRL7.box. Or one can just use the box available at Atlas - https://atlas.hashicorp.com/ciscoxr/boxes/appdev-xr6.1.1

## Initialize a New Vagrant VM (If using your own box image)

The following will create a brand new Vagrantfile. This approach is recommended if you want to create your own Vagrantfile.

```
vagrant init "AppDev-WRL7"
```

## Create AppDev WRL7 Vagrant Box using the Box image built in Build section

```
vagrant box list             # first list existing boxes
vagrant box add --name "AppDev-WRL7" AppDev-WRL7.box
```

## Alternatively, create AppDev WRL7 Vagrant Box using the Box image hosted at Cisco repository

```
vagrant box list             # first list existing boxes
vagrant box add --name "AppDev-WRL7" http://engci-maven-master.cisco.com/artifactory/simple/appdevci-release/AppDev-WRL7/1.0/AppDev-WRL7.box
```

## Use Atlas AppDev-WRL7 Native Build VM vbox

Users can also use AppDev-WRL7 Native Build VM vbox as available on Atlas. In this case just do the following and the box is automatically downloaded

```
vagrant init ciscoxr/appdev-xr6.1.1
```

## Customize Vagrantfile such as sharing host directory into AppDev WRL7 Vagrant Box VM

A Vagrantfile is packaged as part of the box image. However the packaged Vagrantfile does not allow sharing a host directory as AppDev WRL7 Vagrant Box VM does not support native virtualbox sync folder functionality. Users can , however, share a host directory (e.g., ./share/ into the VM as /home/vagrant/host_share/ directory) by adding the following lines to a Vagrantfile that is created when they execute vagrant init command above. The lines below use an alternative method based on rsync.

```
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.synced_folder "./share/", "/home/vagrant/host_share", type: "rsync",
    rsync__exclude: ".git/",
    rsync__args: ["--verbose", "--rsync-path='sudo rsync'", "--archive", "--delete", "-z"]
```

Make ./share/ directory in current directory before connecting to the VM.

```
mkdir -p ./share
```

## Create and connect to AppDev WRL7 VBox VM

```
vagrant up
vagrant ssh
```

## Destroy AppDev WRL7 VBox VM

```
vagrant destroy
vagrant status
```

## Remove AppDev WRL7 Vagrant Box

User can remove the Box if they created one earlier as follows. You don't need to do this if you are using Atlas box.

```
vagrant box remove "AppDev-WRL7"
vagrant box list
```

## Build an Application inside the VM. As an example we build CollectD

```
# Build CollectD Application in AppDev VM
rm -rf /home/vagrant/collectd
rm -rf /home/vagrant/collectd-wrl7

# Download CollectD Application
git clone -b collectd-5.5 https://github.com/collectd/collectd.git

# Cisco CollectD changes
# E.g., change dependency package lex to flex in build.sh since AppDev VM
# does not contain lex, flex provides equivalent functionality
git clone https://github.com/ios-xr/iosxr-collectd.git

# Apply Cisco changes
cp collectd-wrl7/build.sh collectd/.

# Build CollectD
cd /home/vagrant/collectd
./build.sh
./configure
make
sudo make install

# Build CollectD RPM
cd /home/vagrant/collectd-wrl7/
sudo ./changes.sh
sudo rpmbuild --clean /usr/src//rpm/SPECS/collectd.spec
sudo rpmbuild -ba /usr/src/rpm/SPECS/collectd.spec

# CollectD RPM is at /usr/src/rpm/RPMS/noarch/collectd-5.5.0-211.noarch.rpm

```

repository: ios-xr/iosxr-appdev-vbox

gha_language: Shell

repo_name: ios-xr/iosxr-appdev-vbox


text:
# trace-ip

## screenshot
![ ](https://github.com/ShuBhamg0sain/trace-ip/blob/master/Screenshot_20200922_073517.jpg)

# Find me on

Instagram account
👉[![Instagram  ](https://img.shields.io/badge/INSTAGRAM-FOLLOW-red?style=for-the-badge&logo=instagram)](https://www.instagram.com/shubhamg0sain)👈

### How to install

apt update

apt install git -y

git clone https://github.com/ShuBhamg0sain/trace-ip.git

cd trace-ip

php IP-Tracer.php


text:
# Value Parser Plugin

The "value" data format translates single values into Telegraf metrics. This
is done by assigning a measurement name and setting a single field ("value")
as the parsed metric.

## Configuration

```toml
[[inputs.exec]]
  ## Commands array
  commands = ["cat /proc/sys/kernel/random/entropy_avail"]

  ## override the default metric name of "exec"
  name_override = "entropy_available"

  ## override the field name of "value"
  # value_field_name = "value"

  ## Data format to consume.
  ## Each data format has its own unique set of configuration options, read
  ## more about them here:
  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
  data_format = "value"
  data_type = "integer" # required
```

### Metric name

It is recommended to set `name_override` to a measurement name that makes sense
for your metric, otherwise it will just be set to the name of the plugin.

### Datatype

You **must** tell Telegraf what type of metric to collect by using the
`data_type` configuration option. Available options are:

- `integer`: converts the received data to an integer value. This setting will
             produce an error on non-integer data.
- `float`:   converts the received data to a floating-point value. This setting
             will treat integers as floating-point values and produces an error
             on data that cannot be converted (e.g. strings).
- `string`:  outputs the data as a string.
- `boolean`: converts the received data to a boolean value. This setting will
             produce an error on any data except for `true` and `false` strings.
- `auto_integer`: converts the received data to an integer value if possible and
                  will return the data as string otherwise. This is helpful for
                  mixed-type data.
- `auto_float`: converts the received data to a floating-point value if possible
                and will return the data as string otherwise. This is helpful
                for mixed-type data. Integer data will be treated as
                floating-point values.

**NOTE**: The `auto` conversions might convert data to their prioritized type
by accident, for example if a string data-source provides `"55"` it will be
converted to integer/float. This might break outputs that require the same
datatype within a field or column. It is thus recommended to use *strict* typing
whenever possible.

repository: influxdata/telegraf

gha_language: Go

repo_name: influxdata/telegraf


text:
# gtf - a useful set of Golang Template Functions

This is a fork of Kyoung-chan Lee's [gtf](https://github.com/leekchan/gtf) which
provides `gtft`.  Basically, `gtft` is the same as `gtf`, it just uses
`text/template` instead of `html/template` for compatibility with text templates.

repository: thomasheller/gtf

repo_name: thomasheller/gtf


text:
# Class: WithLocation

URI: [ks:WithLocation](https://w3id.org/linkml/tests/kitchen_sink/WithLocation)

[![img](https://yuml.me/diagram/nofunky;dir:TB/class/[Place]<in%20location%200..1-%20[WithLocation],[MarriageEvent]uses%20-.->[WithLocation],[Place],[MarriageEvent])](https://yuml.me/diagram/nofunky;dir:TB/class/[Place]<in%20location%200..1-%20[WithLocation],[MarriageEvent]uses%20-.->[WithLocation],[Place],[MarriageEvent])

## Trait for

 * [MarriageEvent](MarriageEvent.md) (mixin)

## Referenced by Record

## Attributes

### Own

 * [in location](in_location.md)  0..1
     * Range: [Place](Place.md)

repository: linkml/linkml

repo_name: linkml/linkml


text:
---
layout: default
---

# 1996-11-13 - RE: two bogus messages to this list

## Header Data

From: Jim Wise<EMAIL_ADDRESS>To: _N/A_

Message Hash: bc3689a77a33ed6c5e0a1105302c5f6a9cd740f78c73273eaabd2328a0ed0793

Message ID: \<Pine.NEB.3.94.961113033655.7155A-100000@localhost\>

Reply To<EMAIL_ADDRESS>UTC Datetime: 1996-11-13 08:32:54 UTC

Raw Date: Wed, 13 Nov 1996 00:32:54 -0800 (PST)

## Raw message

```
{% raw  %}From: Jim Wise<EMAIL_ADDRESS>Date: Wed, 13 Nov 1996 00:32:54 -0800 (PST)
Subject: RE: two bogus messages to this list
In-Reply-To<EMAIL_ADDRESS>Message-ID: <Pine.NEB.3.94.961113033655.7155A-100000@localhost>
MIME-Version: 1.0
Content-Type: text/plain

On Tue, 12 Nov 1996, Mark M. Lacey wrote:

>> Even under NT, this DLL can be made to remain resident and trapping
>> Keystrokes, events, and window contents.

> This is (or was?) no problem under X Windows the last time I tried
> it (not recently), too.  In fact, you could monitor the keystrokes
> of any machine that you had access to remotely, as long as X was
> running.  All it took was a short little C program.  So what call
> is it on NT that you're talking about?

  This includes other users on the current machine trying
to trap from your display, BTW.

--
				Jim Wise
				System Administrator
				GSAPP, Columbia University
<EMAIL_ADDRESS>				http://www.arch.columbia.edu/~jim
				* Finger for PGP public key *

{% endraw %}
```

## Thread

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

+ Return to "[Jim Wise <jim@santafe.arch.columbia.edu>](/authors/jim_wise_jim_at_santafe_arch_columbia_edu_)"
+ Return to "["Mark M. Lacey" <mml@halcyon.com>](/authors/mark_m_lacey_mml_at_halcyon_com_)"

+ 1996-11-12 (Tue, 12 Nov 1996 10:12:12 -0800 (PST)) - [RE: two bogus messages to this list](/archive/1996/11/fad3fd9ba9bc2d85c067c6ced974981a6bc96689582f5d159568142481756a35) - _"Mark M. Lacey"<EMAIL_ADDRESS>  + 1996-11-13 (Wed, 13 Nov 1996 00:32:54 -0800 (PST)) - RE: two bogus messages to this list - _Jim Wise<EMAIL_ADDRESS>


text:
---
layout: post
title: Content Management - more linking
published: false
categories: [blogging, web design, web development]
tags: [web design, content management]
---

This post/post series is all about navigation
1) TOC
2) Pagination support
3) intra-page navigation (top/home) - series table helps solve the problem for series posts
    design a custom includes element that can be used to create custom heading elements
    example javadocs.com/se/tutorial
4) digitaldrummerj posts for organising content by category/tag (after framework discussion)

Note: Wary of sidebars - occluding content and mobile nightmare!

TOC

change blog URL to "/blog/post-name"

? add to a series: Content Management

Discuss the different ways of implementing a table of contents
1) Standard kramdown toc attribute
http://stackoverflow.com/questions/9721944/automatic-toc-in-github-flavoured-markdown

2) Step 1 + Custom CSS
http://stackoverflow.com/questions/9602936/how-to-create-a-table-of-contents-to-jekyll-blog-post

3) Adding TOC to layout
http://stackoverflow.com/questions/13481572/jekyll-automatic-table-of-contents

3) Custom element to be included like the series panel in previous post

e.g. wrap basic TOC in a <div> that contains a text title
<div name="custom-toc">Contents
    {:toc}
</div>
<style>
    control div style
    control TOC style
</style>

SO - incidentally, this is how to cross reference a Stack Overflow post.
http://stackoverflow.com/questions/5319754/cross-reference-named-anchor-in-markdown#7335259

Show case code and output (might be hard, given that only ONE toc will show per page (I think)

ensure that TOC (and series panels) autohide when not in use or if series = invalid ( e.g. NULL or empty string )

TOC Rmarkdown ....

https://www.r-bloggers.com/alternate-r-markdown-templates/

http://rmarkdown.rstudio.com/developer_document_templates.html

<!--
Adding TOC title
https://www.w3schools.com/cssref/pr_gen_content.asp

How to move TOC in document:
http://stackoverflow.com/questions/25587773/#25625560

More fun and games with TOC
http://rpubs.com/stevepowell99/floating-css
-->

<style> #TOC:before {
    content: "Table of Contents";
    font-weight: bold;
    font-size: 30px;
}
</style>

4. Jekyll TOC

https://blog.webjeda.com/jekyll-toc/
http://stackoverflow.com/questions/9602936/how-to-create-a-table-of-contents-to-jekyll-blog-post
https://css-tricks.com/css-content/
http://stackoverflow.com/questions/20890654/customize-automatically-generated-toc-on-jekyll-kramdown-site

http://stackoverflow.com/questions/29519469/hide-an-entry-from-the-toc-table-of-contents-in-jekyll

http://stackoverflow.com/questions/20890654/customize-automatically-generated-toc-on-jekyll-kramdown-site

<style>
// Adding 'Contents' headline to the TOC
#markdown-toc:before {
    content: "Contents";
    font-weight: bold;
}

// Using numbers instead of bullets for listing
#markdown-toc ul {
    list-style: decimal;
}

#markdown-toc {
    border: 1px solid #aaa;
    padding: 1.5em;
    list-style: decimal;
    display: inline-block;
}
</style>

* This will become a table of contents (this text will be scraped).
{:toc}


text:
![Logo](../docs/assets/banner_framework.png)

# Lisk Framework

[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](http://www.apache.org/licenses/LICENSE-2.0)

## What is Lisk Framework

Lisk Framework is an application framework to create a blockchain application compatible with the Lisk protocol.
It provides an application where off-chain and on-chain logic can be extended with user defined plugins and modules.

### Architecture Overview

The diagram below provides a high-level overview of the architecture:

![Logo](./docs/assets/diagram_framework.png)

The framework consists of 3 main parts, an application, a controller and a node.

The application is an entry point and manages the controller and the node. The node is responsible for blockchain protocol logic using user defined modules, while the controller is responsible for maintaining plugins and managing the interaction between plugins and the application.

## Installation

```sh
$ npm install --save lisk-framework
```

## Tests

```
npm run test:<testType>
```

`testType` can be `unit`|`integration`|`functional`

##### Executing the tests per file:

```
npm run test:<testType> -- [testPathPattern] [jestCliOptions]
```

## Contribution

To test the changes in framework you can run example application under `examples`,

`./bin/run start`

If you want to test the changes in `lisk-sdk/elements` to reflect in `lisk-sdk/framework`, please make sure you run `npm run build` at `lisk-sdk` after making any changes in elements library and run the example app above.

## Get Involved

| Reason                          | How                                                                                |
| ------------------------------- | ----------------------------------------------------------------------------------------------- |
| Want to chat with our community | [Reach them on Discord](https://discord.gg/lisk)                                                |
| Found a bug                     | [Open a new issue](https://github.com/LiskHQ/lisk/issues/new)                                   |
| Found a security issue          | [See our bounty program](https://blog.lisk.com/announcing-lisk-bug-bounty-program-5895bdd46ed4) |
| Want to share your research     | [Propose your research](https://research.lisk.com)                                              |
| Want to develop with us         | [Create a fork](https://github.com/LiskHQ/lisk/fork)                                            |

## License

Copyright 2016-2020 Lisk Foundation

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: LiskHQ/lisk-sdk

branch_name: refs/heads/development

gha_language: TypeScript

repo_name: LiskHQ/lisk-sdk


text:
#### [home](README.md)

# Web and Data Monitoring End-to-End Example

## Architecture
Application architecture without monitoring.
![Architecture](/PNG/todoapp-webapp_data_1.png)

## Application [Criticality](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/considerations/criticality) and Monitoring Requirements
Define application criticality and monitoring requirements.
### [Business Commitment](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/considerations/commitment)

* [Criticality:](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/considerations/criticality) Mission Critical
* [Time/Value Impact:](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/considerations/impact) $1m
* [Commitment Level:](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/considerations/commitment) High Availability Commitment

### [Monitoring Requirements](http://aka.ms/monitoring-reqs)

#### Requirements for health monitoring
* An operator should be alerted within seconds if any part of the system is unhealthy.
* An operator should be able to ascertain which parts of the system are functioning normally and experiencing problems.
* System health should be highlighted through a traffic-light system:
  * Red for unhealthy.
  * Yellow for partially healthy.
  * Green for healthy.

#### Requirements for availability monitoring
* An Operator should be able to view historical availability of each system and subsystem, and use this information to spot any trends.
* A monitoring solution should provide an immediate and historical view of the availability or unavailability of each subsystem.
* An Operator should be able to examine user actions if these actions fail when they attempt to communicate with a service.

#### Requirements for performance monitoring
* An Operator should have access to:
  * The response rates for user requests.
  * The number of concurrent user requests.
  * The volume of network traffic.
  * The rates at which business transactions are being completed.
  * The average processing time for requests.
  * The number of concurrent users versus request latency times (how long it takes to start processing a request after the user has sent it).
  * The number of concurrent users versus the average response time (how long it takes to complete a request after it has started processing).
  * The volume of requests versus the number of processing errors.
  * Memory utilization.
  * Number of threads.
  * CPU processing time.
*	All visualizations should allow an operator to specify a time period. The displayed data might be a snapshot of the current situation and/or a historical view of the performance.
*	An operator should be able to raise an alert based on any performance measure for any specified value during any specified time interval.

#### Requirements for SLA monitoring
*	An operator should be able to determine at a glance whether the system is meeting the agreed SLAs or not.
*	The following indicators should be available:
  * The percentage of service uptime
  * The application throughput (measured in terms of successful transactions and/or operations per second).
  * The number of successful/failing application requests.
  * The number of application and system faults, exceptions, and warnings.
All of these indicators should be capable of being filtered by a specified period of time up to 2 years.
*	System uptime needs to be defined carefully. In a system that uses redundancy to ensure maximum availability, individual instances of elements might fail, but the system can remain functional.
*	System uptime as presented by health monitoring should indicate the aggregate uptime of each element and not necessarily whether the system has actually halted. Additionally, failures might be isolated. So even if a specific system is unavailable, the remainder of the system might remain available, although with decreased functionality.
*	For alerting purposes, the system should be able to raise an event if any of the high-level indicators exceed a specified threshold. The lower-level details of the various factors that compose the high-level indicator should be available as contextual data to the alerting system.

#### Requirements for auditing
*	An analyst must be able to trace the sequence of relevant control plane change operations.
* Data must be available and searchable for a period of 2 years.

#### Requirements for usage monitoring
*	To examine system usage, an operator will need access to the following information:
  * The number of requests that are processed by each subsystem and directed to each resource.
  * Where users are located.
  * What devices are being used to access the system.
  * What percentage of users are returning to the system over time.
  * How system performance affect user behavior.
  * The performance of individual web pages and its effect on user progression through the web site.

## Monitoring
Application architecture with monitoring to meet requirements.
![Monitoring](/PNG/todoapp-webapp_data_monitoring_3.png)

## Inventory
Inventory of application components using Azure Resource Graph Explorer.
* [Azure Resource Graph Explorer](https://docs.microsoft.com/en-us/azure/governance/resource-graph/overview)
![Inventory](/PNG/todoapp-webapp_data_monitoring_Inventory_10.png)

## Web App Monitoring
Web App monitoring extract.
![Web1](/PNG/todoapp-webapp_monitoring_4.png)
Web App monitoring extract.
![Web2](/PNG/todoapp-webapp_monitoring_2_5.png)

## Data Monitoring
Data monitoring extract.
![Data1](/PNG/todoapp-data_monitoring_6.png)
Data monitoring extract.
![Data2](/PNG/todoapp_data_monitoring_7.png)

## Service and Resource Health Monitoring
Service and Resource health monitoring extract.
![SHRH](/PNG/todoapp-webapp_data_monitoring_SHRH_8.png)

## Cost Monitoring
Cost monitoring extract.
* [Cost Management and Billing](https://docs.microsoft.com/en-us/azure/cost-management-billing/cost-management-billing-overview)
Note: Cost management is covered in the FTA Governance Live session.
![Cost](/PNG/todoapp-webapp_data_monitoring_Cost_9.png)

## Dashboard
Sample Azure portal dashboard.
![Dashboard](/PNG/todoapp_dashboard.png)

#### [home](README.md)


text:
---
title: >-
  Proportion  of  members  and  voting  rights  of  developing  countries  in  international  organizations
permalink: /10-6-1/
sdg_goal: 10
layout: indicator
indicator: 10.6.1
indicator_variable: null
graph: null
graph_type_description: null
graph_status_notes: null
variable_description: null
variable_notes: null
un_designated_tier: '1'
un_custodial_agency: DESA/FFDO
target_id: '10.6'
has_metadata: true
rationale_interpretation: >-
  The  UN  is  based  on  a  principle  of  sovereign  equality  of  all  its  Member  States  (Article  2,  UN  Charter).  Voting  rights  in  international  organizations,  particularly  those  under  the  auspices  of  the  UN  system,  should  respect  this  principle.  This  indicator  aims  to  measure  the  degree  to  which  States  enjoy  equal  representation  in  international  organizations.
goal_meta_link: 'http://unstats.un.org/sdgs/files/metadata-compilation/Metadata-Goal-10.pdf'
goal_meta_link_page: 8
indicator_name: >-
  Proportion  of  members  and  voting  rights  of  developing  countries  in  international  organizations
target: >-
  Ensure  enhanced  representation  and  voice  for  developing  countries  in  decision-making  in  global  international  economic  and  financial  institutions  in  order  to  deliver  more  effective,  credible,  accountable  and  legitimate  institutions.
source_title: null
source_notes: null
published: true
comments_and_limitations: Under  review.

indicator_definition: >-
  The  indicator  is  computed  as  the  number  of  voting  rights  allocated  to  developing  countries,  divided  by  the  total  number  of  voting  rights  in  international  organizations,  multiplied  by  100.
---


text:
<!--remark setext-->

<!--lint disable no-multiple-toplevel-headings -->

2.1.0 / 2016-07-30
==================

*   Add support for passing any error ([`3712dc4`](https://github.com/wooorm/vfile-reporter/commit/3712dc4))

2.0.1 / 2016-07-20
==================

*   Fix superfluous lines from showing up ([`e3dd9b2`](https://github.com/wooorm/vfile-reporter/commit/e3dd9b2))
*   Fix a bug where the `color` setting wasn’t honoured ([`7904055`](https://github.com/wooorm/vfile-reporter/commit/7904055))

2.0.0 / 2016-06-23
==================

*   Add support for `defaultName` ([`fb461cf`](https://github.com/wooorm/vfile-reporter/commit/fb461cf))
*   Add support for passing an error ([`a4c95be`](https://github.com/wooorm/vfile-reporter/commit/a4c95be))
*   Fix mutation of files ([`ea22861`](https://github.com/wooorm/vfile-reporter/commit/ea22861))
*   Fix ranges on files with file-paths added later ([`6359168`](https://github.com/wooorm/vfile-reporter/commit/6359168))

1.5.0 / 2015-11-21
==================

*   Remove initial newline before report ([ac6a778](https://github.com/wooorm/vfile-reporter/commit/ac6a778))

1.4.1 / 2015-10-23
==================

*   Fix for changes in vfile ([32c2460](https://github.com/wooorm/vfile-reporter/commit/32c2460))

1.4.0 / 2015-09-12
==================

*   Add support for `note` properties in `verbose` mode ([41a4910](https://github.com/wooorm/vfile-reporter/commit/41a4910))

1.3.0 / 2015-08-21
==================

*   Add output location when applicable to report ([a5b6369](https://github.com/wooorm/vfile-reporter/commit/a5b6369))

1.2.0 / 2015-08-20
==================

*   Refactor summary to only expose non-zero types ([1148621](https://github.com/wooorm/vfile-reporter/commit/1148621))

1.1.0 / 2015-08-19
==================

*   Remove error count, warning count when `0` ([7927078](https://github.com/wooorm/vfile-reporter/commit/7927078))
*   Rename `screen-shot.png` > `screenshot.png` ([f1bb7de](https://github.com/wooorm/vfile-reporter/commit/f1bb7de))

1.0.0 / 2015-08-17
==================

repository: psbrandt/clinFHIR

repo_name: psbrandt/clinFHIR


text:
http://luajit.org/

FFI (foreign function interface)
The FFI library allows calling external C functions and using C data structures from pure Lua code.

repository: SC-CS-KS/KS-Language

repo_name: SC-CS-KS/KS-Language


text:
# **Traffic Sign Recognition**

## Writeup
---

**Build a Traffic Sign Recognition Project**

The goals / steps of this project are the following:
* Load the data set (see below for links to the project data set)
* Explore, summarize and visualize the data set
* Design, train and test a model architecture
* Use the model to make predictions on new images
* Analyze the softmax probabilities of the new images
* Summarize the results with a written report

[//]: # (Image References)

[image1]: ./report_images/01_eda.png "eda"
[image2]: ./report_images/02_class_distribution.png     "class_distribution"
[image3]: ./report_images/03_undistorted.png "undistorted"
[image4]: ./report_images/04_distorted.png "distorted"
[image5]: ./report_images/05_random_noise.png "random_noise"
[image6]: ./report_images/06_invert_color.png "invert_color"
[image7]: ./report_images/07_horizontal_flip.png "horizontal_flip"
[image8]: ./report_images/08_blurred_image.png "blurred_image"
[image9]: ./report_images/09_model_architecture.jpg "model_architecture"
[image10]: ./report_images/10_lenet.jpeg "model architecture diagram"

[image11]: ./new_test_images/end-of-all-speed-limits.jpg
[image12]: ./new_test_images/no-passing-2.jpg
[image13]: ./new_test_images/road-work.jpg
[image14]: ./new_test_images/turn-right-ahead.jpg "model architecture diagram"
[image15]: ./new_test_images/dangerous-turn-to-the-left.jpg
[image16]: ./report_images/11_5images_prediction.png

[image17]: ./report_images/12_prediction_1.JPG
[image18]: ./report_images/13_prediction_2.JPG
[image19]: ./report_images/14_prediction_3.JPG
[image20]: ./report_images/15_prediction_4.JPG
[image21]: ./report_images/16_prediction_5.JPG
[image22]: ./report_images/17_cnn1.png
[image23]: ./report_images/18_cnn2.png
[image24]: ./report_images/19_cnn3.png

## Rubric Points
### Here I will consider the [rubric points](https://review.udacity.com/#!/rubrics/481/view) individually and describe how I addressed each point in my implementation.

---
### Writeup / README

#### 1. Provide a Writeup / README that includes all the rubric points and how you addressed each one. You can submit your writeup as markdown or pdf. You can use this template as a guide for writing the report. The submission includes the project code.

### Data Set Summary & Exploration

#### 1. Provide a basic summary of the data set. In the code, the analysis should be done using python, numpy and/or pandas methods rather than hardcoding results manually.

I used the pandas library to calculate summary statistics of the traffic
The code for this step is contained in the third code cell of the IPython notebook.

I used the numpy library to calculate summary statistics of the traffic signs data set:

* The size of the training set is 34799
* The size of the validation set is 4410
* The size of the test set is 12630
* The shape of a traffic sign image is (32, 32, 3)
* The number of unique classes/labels in the data set is 43

#### 2. Include an exploratory visualization of the dataset.

Here is an exploratory visualization of the data set.
The code for this step is contained in the fourth code cell of the IPython notebook.

![alt text][image1]

It is a bar chart showing how the data. See code cell 6....

![alt text][image2]

### Design and Test a Model Architecture

#### 1. Describe how you preprocessed the image data. What techniques were chosen and why did you choose these techniques? Consider including images showing the output of each preprocessing technique. Pre-processing refers to techniques such as converting to grayscale, normalization, etc. (OPTIONAL: As described in the "Stand Out Suggestions" part of the rubric, if you generated additional data for training, describe why you decided to generate additional data, how you generated the data, and provide example images of the additional data. Then describe the characteristics of the augmented training set like number of images in the set, number of images for each class, etc.)

The code for this step is contained in the 7th and 8th cells of the IPython notebook.

My preprocessing pipeline consists of the following steps:

1. Conversion to grayscale: It didn't significantly change the accuracy, but it made it easier to do the normalization.
2. Saturating the intensity values at 1 and 99 percentile.
3. Min/max normalization to the [0, 1] range.
4. Subtraction of its mean from the image, making the values centered around 0 and in the [-1, 1] range.
5. Apply random noise.
6. Invert the color of the images.
7. Horizontal flipping of images
8. Blurring of images.

The undistorted image as below,

![alt text][image3]

After applying steps 1 to 4 above, the distorted image as below,

![alt text][image4]

Random noise:

![alt text][image5]

Invert color:

![alt text][image6]

Horizontal flip:

![alt text][image7]

Blurred image:

![alt text][image8]

With a simple min/max normalization I had (approx.) 1% better validation-accuracies than without it. The percentile-based method gave an additional (approx.) 1% improvement over simple min/max normalization (this method was mentioned in [3]).

#### 2. Describe what your final model architecture looks like including model type, layers, layer sizes, connectivity, etc.) Consider including a diagram and/or table describing the final model.

The code for my final model is located in the 14th cell of the ipython notebook.

My architecture is a deep convolutional neural network inspired by two existing architectures: one is LeNet[1], and the other is the one in Ciresan's paper[3]. Its number and types of layers come from LeNet, but the relatively huge number of filters in convolutional layers came for Ciresan. Another important property of Ciresan's network is that it is multi-column, but my network contains only a single column. It makes it a little less accurate, but the training and predition is much faster.

The model architecture diagram as below,

![alt text][image10]

The final model consisted of the following layers:

![alt text][image9]

#### 3. Describe how you trained your model. The discussion can include the type of optimizer, the batch size, number of epochs and any hyperparameters such as learning rate.

The code for training the model is located in the 15th to 19th cell of the ipython notebook.

To train the model, I used AdamOptimizer, a batch size of 128, at most 30 epochs, a learn rate of 0.001. Another hyperparameter was the dropout rate which was 0.7 at every place where I used it. I have tried changing these parameters but it didn't really increase the accuracy. I saved the model which had the best validation accuracy.

#### 4. Describe the approach taken for finding a solution and getting the validation set accuracy to be at least 0.93. Include in the discussion the results on the training, validation and test sets and where in the code these were calculated. Your approach may have been an iterative process, in which case, outline the steps you took to get to the final solution and why you chose those steps. Perhaps your solution involved an already well known implementation or architecture. In this case, discuss why you think the architecture is suitable for the current problem.

The code for calculating the accuracy of the model is located in the twelfth cell of the Ipython notebook.

My final model results were:

training set accuracy of 0.991
validation set accuracy of 0.980
test set accuracy of 0.961

I started out by creating an architecture which could clearly overfit the training data. (It converged to 1.0 training-accuracy in a couple of epochs, but the validation accuracy was much lower. Then I have added regulators until the overfitting was more-or-less eliminated. I added dropout operations between the fully connected layers. I also tried L2 regularization for the weights (in addition to the dropout), but it made the accuracy worse by a tiny amount. Then I have kept removing filters up to the point when the accuracy started decreasing.

### Test a Model on New Images

#### 1. Choose five German traffic signs found on the web and provide them in the report. For each image, discuss what quality or qualities might be difficult to classify.

Here are five German traffic signs that I found on the web:

![alt text][image11]

![alt text][image12]

This picture is interesting because the perspective and rotation makes the car figures almost form a diagonal similar to the one in End of all speed limits sign.

![alt text][image13]

![alt text][image14]

This picture might be hard to classify because it is from a strange perspective and another sign is hanging in to the picture.

![alt text][image15]

This is a very blurry image, at first even I didn't know which sign is it. It might be a photo or an artistic painting, of most likely the "Dangerous turn to the left" sign.

#### 2. Discuss the model's predictions on these new traffic signs and compare the results to predicting on the test set. At a minimum, discuss what the predictions were, the accuracy on these new predictions, and compare the accuracy to the accuracy on the test set (OPTIONAL: Discuss the results in more detail as described in the "Stand Out Suggestions" part of the rubric).

Here are the results of the prediction:

![alt text][image16]

The model was able to correctly guess 3 of the 5 traffic signs, which gives an accuracy of 60%.
This is lower than the test accuracy of 96.1%, however I would not draw conclusions from this very small (5 images) dataset.

#### 3. Describe how certain the model is when predicting on each of the five new images by looking at the softmax probabilities for each prediction. Provide the top 5 softmax probabilities for each image along with the sign type of each probability. (OPTIONAL: as described in the "Stand Out Suggestions" part of the rubric, visualizations can also be provided such as bar charts)

The code for making predictions on my final model is located in the 23rd cell of the Ipython notebook.

For the first image, the model is very confident (99.2%), and correct. The top five soft max probabilities were:

![alt text][image17]

For the second image, the model is relatively sure (27%) that we are looking at a "Dangerous curve to the right " sign , but the correct answer is No passing which was not even in the top five guesses. Maybe the image was too skewed.

![alt text][image18]

For the third image, the model is completely confident (100%), and correct.

![alt text][image19]

For the fourth image, the model is relatively sure (18%), and correct.

![alt text][image20]

For the fifth image, the model is very sure (95.16%) that it is a Bumpy road sign, but the correct answer is Dangerous curve to the left, which was not even in the top five guesses.

![alt text][image21]

### (Optional) Visualizing the Neural Network (See Step 4 of the Ipython notebook for more details)
#### 1. Discuss the visual output of your trained network's feature maps. What characteristics did the neural network use to make classifications?

In the visualization of the activations of the first convolutional layer, I have seen that different feature maps look for different edges, for example the 7th feature map is activated by diagonal edges, and the 8th feature map is activated by horizontal edges.

![alt text][image22]

![alt text][image23]

![alt text][image24]

Reference

[1] Lecun(1998): Gradient-Based Learning Applied to Document Recognition

[2] Sermanet(2011): Traffic Sign Recognition with Multi-Scale Convolutional Networks

[3] Ciresan (2012): Multi-Column Deep Neural Network for Traffic Sign Classification

[4] https://www.kaggle.com/tomahim/image-manipulation-augmentation-with-skimage


text:
---
layout: post
title: "Terminal Shortcut in OS X"
date: 2013-02-08 09:59
---

One of my favorite defaults in some Linux distros is the ability to use CTRL+ALT+T to open a new terminal window. I wanted to enable this same functionality in OS X using [Quicksilver](http://qsapp.com/). I did this using [iTerm 2](http://www.iterm2.com/) but you can do it with the default Terminal if that's what you want.

1. Enable the `Terminal` and `iTerm2` Quicksilver plugins.
![Quicksilver plugins](/images/qs-terminal/qs-plugins.png)

2. Create a new custom hotkey trigger. Using the `Home` directory with the action `Open Directory in Terminal`
![Quicksilver trigger](/images/qs-terminal/qs-triggers.png)

3. Set it's hotkey using the drawer to whatever you want.
![Quicksilver hotkey](/images/qs-terminal/qs-hotkey.png)

4. Set your default `Command Line Interface` `Trigger` to `iTerm` (if that's what you want)
![Quicksilver CLI](/images/qs-terminal/qs-cli.png)

You're done! Now you can easily press your hotkey and pull up a new iTerm/Terminal window whenever and wherever.

gha_language: CSS


text:
# Drum Machine

![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)

## Description

This is a website that gives the gift of music to ANYONE! By signing in, the user can click on the buttons to hear different aspects of musical instruments! And by playing different sounds the user can make music right in their browser!

## Installation

To install necessary dependencies, run the following command:

```
npm i
```

```
npm start
```

## Usage

Run "node server.js" to start the server localhost:3000

## Demo

Visit to see my work: https://-----.herokuapp.com/

## License

This project is licensed under the MIT license.

## Contributing

https://github.com/ccastillo356/Drum-Machine-App


text:
# Overview

This is a starter template for a data analysis exercise, containing data, a codebook and an RMarkdown file.

It is set up as a small website.

This is a Github template repository. The best way to get it and start using it is [by following these steps.](https://help.github.com/en/articles/creating-a-repository-from-a-template)


text:
# _Hello World_

#### _Hello in different languages, 4/22/2019_

#### By _**Jordan King**_

## Description

_Hello in multiple different languages_

## Setup/Installation Requirements

* _This is a great place_
* _to list setup instructions_
* _in a simple_
* _easy-to-understand_
* _format_

_{Leave nothing to chance! You want it to be easy for potential users, employers and collaborators to run your app. Do I need to run a server? How should I set up my databases? Is there other code this app depends on?}_

## Known Bugs

_{Are there issues that have not yet been resolved that you want to let users know you know?  Outline any issues that would impact use of your application.  Share any workarounds that are in place. }_

## Support and contact details

_{Let people know what to do if they run into any issues or have questions, ideas or concerns.  Encourage them to contact you or make a contribution to the code.}_

## Technologies Used

_HTML_

### License

*This software is licensed under the MIT license.*

Copyright (c) 2015 **_Jordan King_**


text:
General Info and Prerequisites
==============================

The following script will use `.cql` schema file and `.csv` data file as inputs to create an index in Elasticsearch (ES) and insert the data.

- The ES index name will be created based on the `.csv` file name
- The index `_id` field (index partition key) is based on the `PRIMARY KEY` taken from `.cql` schema (simple/composite/compound).
- The index `_type` field will represent the partition key (PK), in case of a compund key it will use `-` to concatenate the column names.
- The script will print progress for every 1000 rows processed and total rows processed in its output.

**Prerequisites**
- [python installed](https://www.python.org/download/releases/2.7/)
- [pip installed](https://packaging.python.org/guides/installing-using-linux-tools/)
- [Java 8 installed](http://openjdk.java.net/install/)
- An instance for Elasticsearch installation and python scripts (can be separate instances)
- `.cql` schema file that contains the table schema
- `.csv` data file in the following name format: `<keyspace>.<table>.csv`
- The data file contains a header line with the column names

Instructions
============

**Procedure**

1. Install the python drivers on the node to be used for the script
```
$ sudo pip install cassandra-driver
$ sudo pip install elasticsearch
```

2. Install [Elasticsearch](https://www.elastic.co/guide/en/beats/libbeat/current/elasticsearch-installation.html)
```
$ sudo apt-get update
$ curl -L -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.2.3.deb
$ sudo dpkg -i elasticsearch-6.2.3.deb
```

3. Start Elasticsearch, verify status and health state
```
$ sudo /etc/init.d/elasticsearch start
[ ok ] Starting elasticsearch (via systemctl): elasticsearch.service.
```
```
curl http://<IP_ADDRESS>:9200/_cluster/health?pretty
{
  "cluster_name" : "elasticsearch",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 0,
  "active_shards" : 0,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0

}
```

4. Copy the python file to the location from which you will run it, and make it executable. Place your `.csv` and `.cql` files in an accessible location (can be same dir as the python script)

5. Run the script (see below usage, important details and examples)

- **Usage**
```
$ python ES_insert_data_per_schema.py -h
usage: ES_insert_data_per_schema.py [-h] [-e ES_IP] [-c CSV_FILE_NAME]
                                    [-s CQL_SCHEMA_FILE_NAME]
                                    [-i IGNORE_CQL_SCHEMA]

optional arguments:
  -h, --help            show this help message and exit
  -e ES_IP
  -c CSV_FILE_NAME
  -s CQL_SCHEMA_FILE_NAME
  -i IGNORE_CQL_SCHEMA
```

- **Important Details**
	- Use `-e` flag to insert a comma-separated list of IPs for Elasticsearch (ES) nodes. If ES is running locally, no need for this flag, default `<IP_ADDRESS>` will be used
	- `-i` ignore_cql_schema -> default: `True`. Meaning it will use the 1st column from the `.csv` for the index `_id` field. If you have a compound PK use `-i no` so not to ignore the `.cql` schema
	- `-c` csv_file_name -> requires full path to file. Needs to be in the format as described in the prerequisites
	- `-s` cql_schema_file name -> requires full path to file. Checking schema for compound PK, if did not find it checking for simple PK
	- If `.cql` not provided (but `.csv` was provided), will fall back to ignoring cql schema and use the 1st column from the `.csv` for the index `_id` field
	- If both `.cql` + `.csv` files are not provided, error is printed and script exists.

- **Output Example Using Compound PK**
```
ubuntu@ip-172-16-0-124:~/scylla_elastic$ python ES_insert_data_per_schema.py -c ./cp_prod.product_all.csv -s ./cp_prod_product_all.cql -i no

## Check schema (./cp_prod_product_all.cql) for compound primary key to be used as index id

## Did not find a compound primary key, checking for regular primary key to be used as index id

## Connecting to ES -> Creating 'cp_prod.product_all' index, if not exist

## Write csv file (./cp_prod.product_all.csv) content into Elasticsearch

## Update every 1000 rows proccesed ##
Rows processed: 1000
Rows processed: 2000
Rows processed: 3000
Rows processed: 4000
Rows processed: 5000
Rows processed: 6000
Rows processed: 7000
Rows processed: 8000
Rows processed: 9000

## After all inserts, refresh index (just in case)

### Total Rows Processed: 9715 ###

```

- **Print 1 doc from Index**
	- Note the `_index`, `_type` and `_id` fields.

```
$ curl -XGET 'http://<IP_ADDRESS>:9200/move.inventory_by_sku/_search?size=1&pretty'
{
  "took" : 1,
  "timed_out" : false,
  "_shards" : {
    "total" : 5,
    "successful" : 5,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : 160,
    "max_score" : 1.0,
    "hits" : [
      {
        "_index" : "move.inventory_by_sku",
        "_type" : "by_sku-bin_case_id",
        "_id" : "gm-shr-uv-gy-s-m-gm",
        "_score" : 1.0,
        "_source" : {
          "promise_qty" : "15",
          "non_locate_reserved_qty" : "19",
          "lock_qty" : "21",
          "ecomm_ringfence_qty" : "24",
          "dropship_status" : "order",
          "intransit_qty" : "23",
          "receipt_qty" : "13",
          "pre_sell_qty" : "16",
          "crossdock_qty" : "26",
          "location_id" : "shr",
          "picking_qty" : "17",
          "sku" : "gm-shr-uv-gy-s-m",
          "ecomm_rf_restricted" : "yes",
          "expected_date" : "2018-11-09",
          "backorder_qty" : "29",
          "ringfence_qty" : "11",
          "inv_adj_qty" : "22",
          "available_qty" : "30",
          "bin_case_id" : "gm",
          "broker_qty" : "28",
          "newstore_qty" : "20",
          "checkdigit" : "digit9",
          "dropship_qty" : "25",
          "reserved_qty" : "12",
          "caselot_qty" : "27",
          "physical_qty" : "18",
          "rdq_qty" : "14",
          "suspend_qty" : "10",
          "to_be_picked_qty" : "9"
        }
      }
    ]
  }
}
```

6. To delete Elasticsearch index run the following commands
	- `$ curl -X DELETE "<IP_ADDRESS>:9200/<index_name>"`

repository: scylladb/scylla-code-samples

repo_name: scylladb/scylla-code-samples


text:
# Cerberus Gradle Plugin

Konrad Biernacki, 2018

[![CircleCI](https://circleci.com/gh/outware/gradle-plugin-cerberus.svg?style=svg)](https://circleci.com/gh/outware/gradle-plugin-cerberus)

## About

Cerberus is a gradle plugin for extracting Jira issues from commit messages and sharing information on its respective Jenkins job and HockeyApp upload.

Using all of Cerberus' features, you can use your commit history -
```
 * HEAD -> Develop
 | \
 *   \
 | \ |
 | | * [CER-12] Address PR Feedback
 | | * [CER-12] Fix bug
 | | |
 | * | [CER-7] Add feature
 | / |
```

to generate release notes using data from Jira and your build -
```
### Changelog
- [CER-12] UI Bug
- [CER-7] Minor Feature

Built by [Jenkins](https://jenkins.url/build/451)
```

and comment on your Jira tickets with build and artefact information
```
Jenkins: [Build #451|https://jenkins.url/build/451]
HockeyApp: [Version 2.0-RC|https://hockey.url/app/d3adcaf3]
```

## Installation

### As a buildSrc Plugin

1. If you don't have one already, create a `buildSrc` folder in your target project's root directory
2. Copy this project into the `buildSrc` directory (so the plugin `build.gradle` file would be found in `target_project/buildSrc/build.gradle`)

### As a JAR Plugin

1. Compile the plugin as a `.jar` file
2. Add the `.jar` to your target project (eg. `target_project/libs/cerberus.jar`)
3. Add the following to your target project's `build.gradle` file:
    ```groovy
    buildscript {
        dependencies {
            classpath files('libs/cerberus.jar')
        }
    }
    ```

## Usage

1. Add the plugin to your target project's `build.gradle`
    ```groovy
    apply plugin: 'au.com.outware.cerberus'
    ```
2. Specify any configuration parameters in the Gradle DSL plugin configuration block. A typical implementation could be as follows:
    ```groovy
    cerberus {
        shouldUpdateTicketAfter = ['pushToHockeyApp']

        jiraDomain = 'https://jira.mydomain.com'
        jiraUsername = 'cerberus'
        jiraPassword = 'password'
    }
    ```
3. Use Cerberus' tasks in your target build flow

    ```groovy
    task runCi {
        configure {
            group = 'Continuous Integration'
            description = "Main CI Task"
        }

        dependsOn('assemble',
                  'cerberus_makeReleaseNotes',
                  'pushToHockeyApp',
                  'cerberus_updateTicket')
    }
    ```

## Gradle Tasks

Cerberus adds the following tasks to your project classpath:

`cerberus_makeReleaseNotes`
- Generate release notes from all changes between the HEAD and a specified SHA-1 (`cerberus.lastSuccessfulCommit`)
- Load those changes into the plugin extension at `cerberus.releaseNotes` as a markdown formatted string

`cerberus_updateTicket`
- Comment on any identified Jira tickets with:
    - Build information
        - `cerberus.buildNumber`
        - `cerberus.buildUrl`
    - HockeyApp upload information
        - `cerberus.hockeyAppUploadUrl`
        - `cerberus.hockeyAppShortVersion`

## Configuration

The plugin extension available through the Gradle DSL is documented at `CerberusPluginExtension.kt`

### Environment Variables

Some configuration parameters are populated from environment variables

| Parameter            | Environment Variable             | Description                                                |
|----------------------|----------------------------------|------------------------------------------------------------|
| jiraDomain           | `CER_JIRA_URL`                   | URL to Jira instance                                       |
| jiraUsername         | `CER_JIRA_CREDENTIALS_USR`       | Username for Jira instance                                 |
| jiraPassword         | `CER_JIRA_CREDENTIALS_PWD`       | Password for Jira instance                                 |
| lastSuccessfulCommit | `GIT_PREVIOUS_SUCCESSFUL_COMMIT` | The SHA-1 to use as the root commit when comparing to HEAD |
| buildUrl             | `BUILD_URL`                      | The URL to the current build information                   |
| buildNumber          | `BUILD_NUMBER`                   | The current build number                                   |

If additional (or alternate) environment variables need to be used, then configure them in the plugin DSL block like so:

```groovy
cerberus {
    jiraDomain = System.env.OTHER_JIRA_DOMAIN
    ...
}
```

### Default Values

Some configuration parameters have default values

| Parameter               | Default Value   | Description                                                                                |
|-------------------------|-----------------|------------------------------------------------------------------------------------------------------------|
| ticketExtractionPattern | `"[A-Z]+-\\d+"` | Regex pattern to match tickets against. Default matches `ABC-123`                                          |
| gitLogPrettyFormat      | `"%s"`          | Commit information to match against, and include in release notes if it matches `commitPassthroughPattern` |
| disableJiraSSLVerify    | `false`         | Verify an SSL connection attempt is valid before connecting                                                |

repository: outware/gradle-plugin-cerberus

branch_name: refs/heads/develop

gha_language: Kotlin

repo_name: outware/gradle-plugin-cerberus