text:
[![Build Status](https://travis-ci.org/andela/matterhorn-cfh.svg?branch=staging)](https://travis-ci.org/andela/matterhorn-cfh)
[![Coverage Status](https://coveralls.io/repos/github/andela/matterhorn-cfh/badge.svg?branch=staging)](https://coveralls.io/github/andela/matterhorn-cfh?branch=staging)
Cards for Humanity - [http://cfh.io](http://cfh.io)
===========
Cards for Humanity is a fast-paced online version of the popular card game, Cards Against Humanity, that gives you the opportunity to donate to children in need - all while remaining as despicable and awkward as you naturally are.

Our Team
--------
Cards for Humanity was created at [Hack Reactor](http://www.hackreactor.com) by:
* [Matt Silverstein](http://www.mattsilverstein.com/)
* [Will Ngo](https://mrngoitall.net)
* [Tyler McGinnis](http://www.tylermcginnis.com)
* [David Gonzalez](http://www.truthyfalsy.com)

About the Game
-------------
The game is simple - each player is given 10 answer cards which are used to fill in the question card. For each round, one player is the "Card Czar". Their sole job is to select a submitted answer card that they think best fits the question. Whoever's card is selected wins a point for the round.

Cards Against Humanity is open-source and licensed under Creative Commons. The idea for Cards for Humanity was to create a web version of the game we love so much, while still doing something good for humanity. To achieve this we integrated the option to donate to the Make a Wish Foundation.

The app is completely functional across all devices - from iPhone to full-sized desktop. We used Socket.io to create rooms which hold up 6 players at a time, and also included the functionality to create private rooms once logged in. Passport handles authentication with Local, Twitter, Facebook, Google and Github strategies implemented.

![alt-text](https://dl.dropboxusercontent.com/u/7390609/CFHforGit.png "Cards for Humanity views")

![alt-text](http://www.tylermcginnis.com/images/cfh3.png "Desktop with Cards")

Our Tech Stack
--------------
Cards for Humanity uses AngularJS and Sass on the front-end, with Node.js/Express.js, MongoDB and Socket.io on the back-end. It's currently deployed to Amazon EC2.

![alt-text](https://dl.dropboxusercontent.com/u/7390609/tech.png "Tech Stack Overview")

## Installation
- Clone the Repository `git clone git@github.com:andela/matterhorn-cfh.git`
- cd into Project directory and install all dependencies
- Create a **.env** file in the root of the project
- Enter in `PORT=27017` and `HOST=<IP_ADDRESS>` in the **.env** file
- Install **dotenv** to save config information in project environment
- Add this line to start of **server.js** file located in the root of the project
  - `require ('dotenv').config();`
- Install mongodb locally https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/#install-mongodb-community-edition
- Start up mongodb server locally on computer
- in Project directory run `npm start` at terminal to boot up project

## License

(The MIT License)

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

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

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

repository: andela/matterhorn-cfh

branch_name: refs/heads/staging

repo_name: andela/matterhorn-cfh


text:
# syntax-flow-game
Try to keep the flow going without causing a syntax error. The syntax gets harder and the speed gets faster the longer you go.

Planning to build this as a ios and android app.

Basic idea:
Its sort of like tetris...
You are given an 'n' (1<n<6 depending on difficulty) number of options.
Each option is a simple code block. As simple as a single character ('{', ';', '(') or as complex as ('/n this()', '/n const newFunct = (param) => {').
You have a short amount of time to pick your option.
When you pick your option it will be placed at the end of your code block (at the beginning the code block will be blank)
and then the code block will be quickly checked for syntax errors.
score will be based on how many option choices you get through with multipliers for choosing more complex options ('/n this()' worth more points than ';' for example).

license: MIT

repository: Sheldonfrith/syntax-flow-game

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: Sheldonfrith/syntax-flow-game


text:
# Peer-graded-Assignment-Course-Project-Shiny-Application-and-Reproducible-Pitch

This repository has the ui.R and server.R files for the first part of the Developing
Data Products Course Project. The peer assessed assignment has two parts.
First, we need to create a Shiny application and deploy it on Rstudio's
servers. Second, we should use Slidify or Rstudio Presenter to prepare a
reproducible pitch presentation about the application.

The app developed for the first part of the assignment is avalilable at: https://1matyusi.shinyapps.io/appproject/

The presentation is available at: http://rpubs.com/MatyusI/286750

Files for the presentation are avalilable on the GitHub: https://github.com/sambathcs/datasciencecoursera/tree/master/9_Developing_Data_Products/Peer-graded-Assignment-Course-Project-Shiny-Application-and-Reproducible-Pitch

url: https://raw.githubusercontent.com/MnNikhil/Johns-Hopkins-University-Data-Science-Specialization/97be0f7b3f131a206df1c9e309f9a666f14c2c07/9.Developing Data Products/Course Project: Shiny Application and Reproducible Pitch/README.md


text:
# LittleNews

A news app via electron

### features

- app is based on Electron.app(v1.4.3)
- set pattern and get your customized news
- support RSS/Crawler/API

### for developer

- you need Electron.app(v1.4.3), see [releases](https://github.com/electron/electron/releases)
- you need electron-packager installed in global
- `git clone git@github.com:excaliburhan/LittleNews.git yourProjectName`
- `npm install`
- dev: `npm run dev`
- build: `npm run dev`

repository: excaliburhan/LittleNews

repo_name: excaliburhan/LittleNews


text:
# EasyBle
Multi device process Ble library for Android

中文文档 [README_CN.md](https://github.com/nziyouren/EasyBle/blob/master/README_CN.md)

# Why I develop this library?
## Current Ble difficulties

* When app interacts with multiple devices, App UI may tightly coupled with bluetooth interact logic. It's difficult to maintain
* BLE command must executed one by one. If not, many strange issues may happen such as packet drop, gatt 133
* Devices made by different manufacturers have differences in detailed Ble stack implementations. We need to deal with these situations specially. Such as on Samsung device, characteristic write operations must be executed on Android main thread.
* Some peripheral devices can't consume lots of data in a very short time, so we need to control send speed in producer side.

So I develop this library to solve above issues.

## EasyBle advantages

* Decouple App UI and bluetooth interact logic totally
* Simple API. App just need to register one listener to listen all bluetooth events
* Based on Powerful [RXAndroidBle](https://github.com/Polidea/RxAndroidBle) (https://github.com/Polidea/RxAndroidBle). Improve stablities a lot, easy thread switch, clean code.

## Architecture

Architecture of this library

# Download
## Gradle

    compile 'com.happysoftware.easyble:easyble:0.3.3'

# Sample

## Bluetooth init

	BleCenterManager bleCenterManager = BleCenterManager.getInstance();//APP keep singleton
	BleConfig config = new BleConfig.BleConfigBuilder()
        .setStopScanAfterConnected(true)
        .setStartScanAfterDisconncted(true)
        .createBleConfig();//create config
	bleCenterManager.init(this,config);//init config

## Open Bluetooth
	try {
        bleCenterManager.openBluetooth(this, requestCode);
	} catch (EasyBleException e) {
        e.printStackTrace();
	}

## Disconnect device and close Bluetooth
```
	if (bleCenterManager.isBluetoothOpen()){
    try {
         bleCenterManager.prepareClose();//disconnect device
 		   bleCenterManager.closeBluetooth();//close Bluetooth
 		 } catch (EasyBleException e) {
        e.printStackTrace();
 		}
	}
```

## Scan Device
	bleCenterManager.startScan();

## Stop scan
	bleCenterManager.stopScan();

## Set listener and listen all Bluetooth events

```
bleCenterManager.setBleDeviceListener(new BleDeviceListener() {
    @Override
 public void onDeviceStateChange(BleDevice device, BleDeviceState state) {
        //Device state change callback. BLE_DEVICE_STATE_CONNECTED(1),
 		// BLE_DEVICE_STATE_CONNECTING(2),
 		// BLE_DEVICE_STATE_DISCONNECTED(0),
 		// BLE_DEVICE_STATE_DISCONNECTING(3);
 		if (state == BleDeviceState.BLE_DEVICE_STATE_CONNECTED){

        }
        if (state == BleDeviceState.BLE_DEVICE_STATE_DISCONNECTED){

        }
    }

    @Override
 public void onDataComing(BleDevice device, BleDataType type, Object data) {
        //data coming callback
		 Log.e(TAG,"onDataComing "+type+ "rawData: "+data.toString());
 		if (type == BleDataType.BLE_DATA_TPYE_CONTINUOUS){
            //data type is BleDataType.BLE_DATA_TPYE_CONTINUOUS
 		}else (type == BleDataType.BLE_DATA_TPYE_SINGLE){
            //data type is BleDataType.BLE_DATA_TPYE_SINGLE
 		}
    }

    @Override
 public void onInteractComplete(BleDevice device, Object finalResult) {
        //interact complete callback
 		Log.e(TAG,"onInteractComplete "+device.getDeviceName()+ "state: "+finalResult);
 }

    @Override
 public void onInteractUpdate(BleDevice device, BleStep step) {
        //interact update callback
 		Log.e(TAG,"onInteractUpdate "+device.getDeviceName()+ " step: "+step.action);
 }

    @Override
 public void onInteractError(BleDevice device, Throwable throwable, BleStep step) {
        //interact error callback
 }

 @Override
 public void onScanStart(){
 	 	//scan start callback
  }

@Override
public void onScanStop(){
		//scan stop callback
}

    @Override
 public void onScanUpdate(BleScanResult scanResult) {
        //scan device callback

 }

    @Override
 public void onScanError(Throwable throwable) {
        //scan error callback
}
});

```

## Write data to characteristic
	public void writeCharacteristic(UUID uuid, byte[] data);

## Write lots of data to characteristic and chunkify data automatically
	public void writeCharacteristic(UUID uuid, byte[] longData, int maxLengthPerPacket);

## Read data from characteristic
	public void readCharacteristic(UUID uuid);

## How to integrate new device
#### You just need 3 steps to integrate new device:

1. Create custom AdapterFactory and implement buildDeviceAdapter method

	```
	public class BloodPressureFactory extends DeviceAdapter.Factory{

	 //static create Factory method
    public static BloodPressureFactory create(BleCenterManager bleCenterManager){
	        return new BloodPressureFactory(bleCenterManager);
	 }

    public BloodPressureFactory(BleCenterManager bleCenterManager) {
	        super(bleCenterManager);
    }

	 //Create deviceAdapter
    @Override
    public DeviceAdapter<T> buildDeviceAdapter() {
        return new BloodPressureDeviceAdapter(mBleCenterManager);
	}
	}
	```
2.  Create your custom deviceAdapter inherited from DeviceAdatper and implements some methods

    ##### public String[] supportedNames()

	EasyBle find appropriate deviceAdapter to process your device by name. So your deviceAdapter need to tell EasyBle framework the device name you can process. If your deviceAdapter supports more than one device, return all names. If you'r not sure about the name, you can use supportedNameRegExps() instead. supportedNameRegExps() support regular expressions.

	```
	@Override
	public String[] supportedNames() {
	    return new String[]{"Model-name-old","Model-name-new"};//return device advertised names
	}
	```

    ##### public UUID[] notificationUUIDs()

	If you want to set UUID notifications, just return UUID[]

	```
	@Override
	public UUID[] notificationUUIDs() {
    	return new UUID[]{UUID.fromString("UUID-1"),UUID.fromString("UUID-2")};// return UUIDs which need to enable notification
	}
	```

    ##### public UUID[] indicatorUUIDs()

	If you want to set UUID indications, just return UUID[]

	```
	@Override
	public UUID[] indicatorUUIDs() {
    return new UUID[]{UUID.fromString("UUID-1"),UUID.fromString("UUID-2")};//return UUIDs which need to enable indication
	}
	```
    ##### public void processData(UUID uuid, byte[] data)

	Put your peripherals and device protocol logic here. The second parameter data is the data you received from peripherals. You can parse, process and send some other data to peripherals.

	```
	@Override
	public void processData(UUID uuid, byte[] data) {

		//Process data you received from peripherals.
		byte cmd = data[0];
        if (cmd == 1){
            //Notify APP UI, we've reached step1. NotifyInteractUpdate is wrapper of BleDeviceListener.onInteractUpdate.
            notifyInteractUpdate(mBleDevice,new BleStep("Interact update on step1",data));
        }else if (cmd == 2){
            //Notify APP UI, we've reached step2
            notifyInteractUpdate(mBleDevice,new BleStep("Interact update on step2",data));
        }else if (cmd == 3){
            //Notify APP UI, we've reached step3
            notifyInteractUpdate(mBleDevice,new BleStep("Interact update on step3",data));
            notifyDataComing(mBleDevice,BleDataType.BLE_DATA_TPYE_CONTINUOUS,data);
        }else if (cmd == 4){
            //Notify APP UI, we've finished protocol, and pass data to APP UI through callback method. So APP UI can parse data and update UI
            notifyInteractComplete(mBleDevice,data);
        }

	}
	```
    #### What we need to do in processData(UUID uuid, byte[] data) method?

	**Because different peripheral equipment has different protocols, so in every key step of protocols interaction, we need to invoke according BleDeviceListener method manually. As a result the APP UI(Activity) can receive BLE event callback and process received data.**

3. 	Register custom device factory to BLECenterManager.

	```
    bleCenterManager.addDeviceAdapterFactory(BloodPressureFactory.create(bleCenterManager));
	```

	Wow! Now EasyBle can process and interact with your new peripheral equipment.

# Contact
You can reach me by email<EMAIL_ADDRESS>
# License:
Apache License, Version 2.0

repository: nziyouren/EasyBle

repo_name: nziyouren/EasyBle


text:
[LeetCode: 724. Find Pivot Index](https://leetcode.com/problems/find-pivot-index/description/)

### 724. Find Pivot Index
### 题目描述

Given an array of integers nums, write a method that returns the "pivot" index of this array.

We define the pivot index as the index where the sum of the numbers to the left of the index is equal to the sum of the numbers to the right of the index.

If no such index exists, we should return -1. If there are multiple pivot indexes, you should return the left-most pivot index.

Example 1:

Input:
nums = [1, 7, 3, 6, 5, 6]

Output: 3

Explanation:

The sum of the numbers to the left of index 3 (nums[3] = 6) is equal to the sum of numbers to the right of index 3.
Also, 3 is the first index where this occurs.

Example 2:

Input:
nums = [1, 2, 3]

Output: -1

Explanation:
There is no index that satisfies the conditions in the problem statement.

Note:

The length of nums will be in the range [0, 10000].

Each element nums[i] will be an integer in the range [-1000, 1000].

更像是个数学问题，总和为 sum，左边的和为 left，右边的和为 right，若满足题意，则 left + right = sum - nums[i]，且 left = right，然后就求出来了。

```java
class Solution {
    public int pivotIndex(int[] nums) {

        int len = nums.length;
        int left = 0;
        int sum = 0;

        for (int i = 0; i < len; i++) sum += nums[i];

        for (int i = 0; i < len; i++) {
            if (2 * left == sum - nums[i]) return i;
            left += nums[i];
        }
        return -1;
    }
}
```

repository: shelbylee/My-Notes

path: /leetcode（Java）/Array/724. Find Pivot Index.md

filename: 724. Find Pivot Index.md

repo_name: shelbylee/My-Notes


text:
#Change Log

### [0.5.6](https://github.com/rzimmerman/kal/compare/r0.5.6...r0.5.5)
* Added support for block and multiline strings
* Add the `from ... to .. as` feature
* Added the `delete` statement
* Fixes to implicit parentheses
* Conditionals in comprehensions are supported
* Added support for generators to `for` loops (like Python)
* Added object unpacking support

### [0.5.5](https://github.com/rzimmerman/kal/compare/r0.5.5...r0.5.4)
* For loops support the `at` index syntax (`for x at index in y`)
* `is not` now works like `isnt` rather than `is (not`
* Fixed command-line execution of scripts
* Late bound methods no longer cause the class to be defined in scope (bug)

### [0.5.4](https://github.com/rzimmerman/kal/compare/r0.5.4...r0.5.3)
* Fixed support for using the `arguments` structure in list comprehensions.
* Fixed a bug where Kal would allow compilation of class definitions with bad class names
* Converted source to Literate Kal.

### [0.5.3](https://github.com/rzimmerman/kal/compare/r0.5.2...r0.5.3)
* Bug fixes to Literate Kal support

### [0.5.2](https://github.com/rzimmerman/kal/compare/r0.5.1...r0.5.2)
* Added Literate Kal support

### [0.5.1](https://github.com/rzimmerman/kal/compare/r0.5.0...r0.5.1)
* Fixed bugs in `run in parallel` blocks
* `none` and `nothing` keywords now working as aliases for `null`
* Added `bitwise left` (`<<`) and `bitwise right` (`>>`) shift operators.
* Added support for late binding of methods to classes.
* Fixed issues with Unicode support for international characters

### [0.5.0](https://github.com/rzimmerman/kal/compare/r0.4.9...r0.5.0)
* Some cleanup to internal variable names and spacing in generated JavaScript.
* Compile-time checks for JavaScript/Kal keywords being used as identifiers.
* Async callbacks after `wait for`s are now consistent about running on the next process tick. The initial call runs synchronously.

### [0.4.9](https://github.com/rzimmerman/kal/compare/r0.4.8...r0.4.9)
* `this`/`me` is now preserved between `wait for` calls
* Added `until` loops (equivalent to `while not`)
* Using anything other than a literal for an object key is now a compile time error (it used to just produce bad JavaScript).
* The command line utility now accepts hyphenated file names (bug fix).
* Added the `run in parallel` block feature for kicking off parallel tasks.
* You can now define a function in an object definition.
* CoffeeScript-style functions can now be the first argument to a function call without extra parentheses.
* Fixed issues with the `^` operator.

### [0.4.8](https://github.com/rzimmerman/kal/compare/r0.4.7...r0.4.8)
* Added support for default arguments in functions, methods, and tasks.
* A compound assignment (like `+=`) no longer causes a variable to be declared. `a += 1` with no other definition of a will now throw an error, not return `NaN`.
* Fixed bugs with `pause for` statements
* Tasks now work as class members.

### [0.4.7](https://github.com/rzimmerman/kal/compare/r0.4.6...r0.4.7)
* Added the `mod` (modulo) keyword
* Removed all dependencies including uglify-js. `kal --minify` replaces `kal -f minify` and requires that you already have uglify installed.
* Comments that start with `##` no longer get cut off
* Output is beautified by default. The `concise` option no longer exists.
* Added the `pause for` syntax
* Bug fixes for consecutive `try` blocks with `wait for`s.
* `wait for`s no longer need to have return values (e.g. `wait for task()` is now valid)
* Fixed multi-line mode (Ctrl-V) in the REPL

### [0.4.6](https://github.com/rzimmerman/kal/compare/r0.4.5...r0.4.6)
* Fixes to the `but` operator. It was failing to compile in certain cases, such as when combined with `not`.
* Added support for bitwise operators (see the README for a full list).
* Fixed an issue where you could not have an `if` statement directly after a multiline object definition.
* Multiple return values from `wait for`s now actually work.
* Fixed a (cosmetic) issue with JavaScript output for standard `return` statements.

### [0.4.5](https://github.com/rzimmerman/kal/compare/r0.4.4...r0.4.5)
* Cleaned up the npm configuration for users building the repo manually (does not affect npm repository packages)
* Fixed a bug with the command line tool where things like list comprehensions were not working when running a script directly with `kal`

### [0.4.4](https://github.com/rzimmerman/kal/compare/r0.4.3...r0.4.4)
* Fixed a bug with `try` blocks containing `wait for` statements that could throw unexpected errors when nested in certain ways
* Improvements to the command-line tool
* Added the ability to compile a whole directory and recursive directories to the command-line tool
* Fixed some issues with the `in` and `instanceof` operators in the REPL

### [0.4.3](https://github.com/rzimmerman/kal/compare/r0.4.2...r0.4.3)
* Fixed a bug with `for parallel` blocks that could cause them to return multiple times
* Better syntax error reporting in `catch` blocks
* Added support for `catch` blocks with no error variable
* `wait for` statements now work in the main file body instead of just in functions
* Added support for `safe wait for` for functions that don't call back with an error argument
* `wait for` statements now work in the REPL and bare files
* Added the `pass` keyword for blank statements (like Python)
* Added the `print` keyword as an alias for `console.log`

### [0.4.2](https://github.com/rzimmerman/kal/compare/r0.4.1...r0.4.2)
* Added support for no-brace multiline CoffeeScript style object assignments
* Fixed a bug with double quoted strings as the first argument to function calls
* Better error messages for when `wait for` statements get included in `catch` blocks

### [0.4.1](https://github.com/rzimmerman/kal/compare/r0.4.0...r0.4.1)
* Fixed the REPL and executable to actually work correctly

### [0.4.0](https://github.com/rzimmerman/kal/compare/r0.3.2...r0.4.0)
* Added support for `wait for` statements which simplify callback use
* `wait for` statements are supported inside conditionals and loops
* `for` loops have a `parallel` or `series` specifier available for when they contain `wait for` statements
* `try` blocks also support `wait for` statements
* Fixed some bugs with tail conditionals
* Fixed a bug where parentheses were not optional if the last line of a file was a function call
* Output files are now beautified by default using uglify-js. They can also be minified or "compact" which is just standard output without most of the whitespace.
* Known issues: the REPL is not really complete (scope is reset between each line) and running a script directly from the command line using `kal script.kal` doesn't always work right. Compiling a script using `kal -o out_dir/ script.kal` works fine.

### [0.3.2](https://github.com/rzimmerman/kal/compare/r0.3.1...r0.3.2)
* Better error reporting from the compiler
* List comprehension over objects is supported using the syntaxes:

    [expr(p) for property p of y]
    [expr(v) for property value v of y]
    [expr(p,v) for property p with value v of y]

* Fixed a bug where you couldn't call a function with a list argument and implicit parens like `myfunc [1,2,3]`
* Multi-line lists with optional commas (like CoffeeScript) are now supported. Multiline objects are not supported yet.
* Some fixes to the command line tool to get it to work with node.js 0.6.x. No promises, though.

### [0.3.1](https://github.com/rzimmerman/kal/compare/r0.3.0...r0.3.1)
* Support for list comprehensions using the `[expr(x) for x in y]` syntax

### [0.3.0](https://github.com/rzimmerman/kal/compare/r0.2.9...r0.3.0)
* Indentation on blank lines is now ignored
* The `Kal.eval` options argument is now optional
* Better Javascript output for comments

### [0.2.9](https://github.com/rzimmerman/kal/compare/r0.2.8...r0.2.9)
* Significant performance improvements for compile time
* Fixed the command line options to the `kal` executable
* Much better error reporting for syntax errors
* Fixed a bug to allow no-parentheses function calls in for and while loop headers

### [0.2.8](https://github.com/rzimmerman/kal/compare/r0.2.7...r0.2.8)
* Fixed some issues with escape sequences in strings
* Fixed some issues with conditional return statements
* Included an interactive shell which now runs be default if you run `kal` with no arguments.

### [0.2.7](https://github.com/rzimmerman/kal/compare/r0.2.6...r0.2.7)
* Added a proper npmignore file to reduce the package size
* Added this change log
* Added support for reserved words as properties and function calls to reserved word properties

### [0.2.6](https://github.com/rzimmerman/kal/compare/r0.2.5...r0.2.6)
* Now correctly parses and compiles expressions inside of double-quoted strings. Previous versions just
  treated these as Javascript
* Added support for the `super` keyword

### [0.2.5](https://github.com/rzimmerman/kal/tree/8d994cca210638b2ac2518a2f7bbe598e067a418) - Nov 25 2012
* Fixes reported version (was reporting 0.2.3 for version 0.2.4)

### [0.2.4](https://github.com/rzimmerman/kal/tree/c6a34fc132f15a10b787e5814d89648e27061aee) - Nov 25 2012
* Added a `kal` command line tool
* Still reports version 0.2.3 in some places (bug)

### [0.2.3](https://github.com/rzimmerman/kal/tree/f5a8cac5bace0a3d96b92f4d125a09026a4b9ae2) - Nov 25 2012
* Fixes to trailing conditionals on function calls with implicit parentheses

### [0.2.2](https://github.com/rzimmerman/kal/tree/4798522fef3e41fc40f2b7819cd41c75a1b1f16a) - Nov 25 2012
* Fixed the npm package.json file (was causing failed installs)

### [0.2.1](https://github.com/rzimmerman/kal/tree/914db52fa3a158c36b22bbde3480d9d8ba5bec3f) - Nov 25 2012
* Added support for negative unary expressions (`-3`)
* Added support for `!=` and `==`
* Full support for function calls without parentheses
* Added support for `not in` and `not of` operators
* Removed CoffeeScript source files

### [0.2.0](https://github.com/rzimmerman/kal/tree/63075434b0343520d0c4f9c7a0460742108d96b9) - Nov 24 2012
* Removed dependency on CoffeeScript, thought the .coffee files are still included for reference

### [0.1.0](https://github.com/rzimmerman/kal/tree/021497d75468bd648bf36944d5ab528f7185b8c9) - Nov 24 2012
* Initial release

repository: KoreanFoodComics/kal

repo_name: KoreanFoodComics/kal


text:
# Adventure512

![Image of Adventure512](adventure512.png)

Extremely simple adventure game in 512 bytes

## Instructions for compiling

Compile with FASM or other assembler. Run on VirtualBox(tested), QEMU, etc. THIS HAS NOT BEEN TESTED ON **REAL HARDWARE**! BEWARE! It might be buggy or crash.

## How to play

You can type `north`,`south`,`east`,`west`,`take`,`drop`,`pack`,and `plugh`

### Cardinal directions

For now, since this is 1-room, these just say "Ow!" because you bonk into a wall.

### Object interaction

For now, there is only one object, a key. You can type `take key` and `drop key`. The description changes from

`Entrance`

`A key is here`

to just

`Entrance`

Taking and dropping the key sets a byte to 1 and 0.

### Pack (inventory)

The command `pack` shows you your inventory.

Normal output with key:
`Inventory: key`

### Plugh (easter egg)

The command `plugh` references Colossal Cave Adventures. It displays `No cave here`, as a joke.

## Limitations
 - Since the code only looks at the command and not what follows it, `plughlol` will be interpreted as `plugh`.
 - This takes all 512 bytes, with no extra space, so not much room for improvement.
 - Since it all has to fit into 512 bytes, the strings are very short and don't give much information.


text:
---
layout: default
---

# 1997-12-03 - Delete if you do NOT have or plan to have a webpage.

## Header Data

From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: 46dd67da3baed2aa8bff6683b5c0c475b2d56de07015b6bdae0ff51148d820a3

Message ID: \<\>

Reply To: _N/A_

UTC Datetime: 1997-12-03 16:02:31 UTC

Raw Date: Wed, 3 Dec 1997 08:02:31 -0800 (PST)

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>Date: Wed, 3 Dec 1997 08:02:31 -0800 (PST)
To<EMAIL_ADDRESS>Subject: Delete if you do NOT have or plan to have a webpage.
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain

Online Sales & Marketing (OSM) would like your assistance
With an Internet marketing survey. Your assistance would be greatly appreciated.
Please go to:

	http://www.osmweb.net/survey2.htm

------------------------------------------------------------------------------------------------
We believe in free speech and responsible online
Mass marketing. To be removed from all future mailings
correctly, please send remove request to:

<EMAIL_ADDRESS>

{% endraw %}
```

## Thread

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

+ Return to "[93704355@08177.com](/authors/93704355_at_08177_com)"

+ 1997-12-03 (Wed, 3 Dec 1997 08:02:31 -0800 (PST)) - Delete if you do NOT have or plan to have a webpage. -<EMAIL_ADDRESS>

gha_license_id: MIT


text:
# Exhale
[![Build Status](https://travis-ci.org/Michanne/exhale.svg?branch=master)](https://travis-ci.org/Michanne/exhale)

Originally a fork of the [vita port][3] of [Moonlight Embedded][1], Exhale is a streaming frontend/manager for Vita.
It supports Steam and various PC emulators natively

## Documentation

More information can find [moonlight-docs][1], [moonlight-embedded][2], and [vita-moonlight][3].
If you need more help, join the #vita-help channel in [discord][4].

[1]: https://github.com/moonlight-stream/moonlight-docs/wiki
[2]: https://github.com/irtimmer/moonlight-embedded/wiki
[3]: https://github.com/xyzz/vita-moonlight/wiki
[4]: https://discord.gg/atkmxxT

# Build deps

You can install build dependencies with [ddpm](https://github.com/dolcesdk/ddpm).

# Build Exhale

```
# if you do git pull, make sure submodules are updated first
git submodule update --init
mkdir build && cd build
cmake ..
make
```

# Assets

- Icon - [moonlight-stream][moonlight] project logo
- Livearea background - [Moonlight Reflection][reflection] Public domain

[moonlight]: https://github.com/moonlight-stream
[reflection]: http://www.publicdomainpictures.net/view-image.php?image=130014&picture=moonlight-reflection

repository: Michanne/exhale

repo_name: Michanne/exhale


text:
![https://github.com/nobe4/SansBullshitSans.vim/blob/master/head.jpg](https://github.com/nobe4/SansBullshitSans.vim/blob/master/head.jpg)

# Huh?

Do you know [SansBullshitSans](http://www.sansbullshitsans.com/)?
It changed my life, seriously.

One problem though, this font is not really developer friendly.

Demo!](https://media.giphy.com/media/uoNSJpsqWPs1a/giphy.gif)

# How does it work ?

Vim `:h conceal` allows to hide/replace pattern of texts as part of the syntax definition. This is massively used for enhancing the coding experience on verbose languages:

- [calebsmith/vim-lambdify](https://github.com/calebsmith/vim-lambdify)
- [enomsg/vim-haskellConcealPlus](https://github.com/enomsg/vim-haskellConcealPlus)
- [plasticboy/vim-markdown](https://github.com/plasticboy/vim-markdown#syntax-concealing)

Here I use it to replace some words by others.

Bare in mind this is not what conceal is used for!

 s .

And the following syntax will roughly be applied:

    syntax match GroupName1 contained 'a' conceal cchar=b
    ...
    syntax match GroupName4 contained 'le' conceal cchar=.

    syn match /agile/ contains=GroupName1,GroupName2,GroupName3,GroupName4

And now when you type 'agile' anywhere, a beautiful 'b.s.' will appear instead.

# Help!

If it doesn't work, if it crashes, if emacs launches, ...

This is not what conceal are used for, don't take it too seriously.

# Contributing

... Serioulsy? Don't you have anything interesting to do?

(I accept issues and pull requests)

# License

- [Picture Credits](https://unsplash.com/search/bull?photo=9uOasewOoXc)
- [SansBullshitSans Inspiration](http://www.sansbullshitsans.com/)
- [MIT License for this project](https://github.com/nobe4/SansBullshitSans.vim/blob/master/LICENSE)


text:
---
id: aws_ecs
title: ECS
sidebar_label: ECS
description: AWS ECS Queries
hide_title: true
---

## Sample AWS ECS RQL Queries

:::note
The following guide will walk you through AWS ECS RQL Query Examples
:::

### PublicIPs associated with ECS

```bash
config from cloud.resource where api.name = 'aws-ecs-service' as X; config from cloud.resource where api.name = 'aws-ec2-describe-network-interfaces' as Y; filter " $.Y.tagSet[?(@.key=='aws:ecs:serviceName')].value contains $.X.serviceName and $.X.networkConfiguration.awsvpcConfiguration.assignPublicIp equals ENABLED"; show X;
```


text:
# EasyBluetooth

[![CI Status](http://img.shields.io/travis/mysevenmi2013<EMAIL_ADDRESS>[![Version](https://img.shields.io/cocoapods/v/EasyBluetooth.svg?style=flat)](http://cocoapods.org/pods/EasyBluetooth)
[![License](https://img.shields.io/cocoapods/l/EasyBluetooth.svg?style=flat)](http://cocoapods.org/pods/EasyBluetooth)
[![Platform](https://img.shields.io/cocoapods/p/EasyBluetooth.svg?style=flat)](http://cocoapods.org/pods/EasyBluetooth)

## Example

To run the example project, clone the repo, and run `pod install` from the Example directory first.

## Requirements

## Installation

EasyBluetooth is available through [CocoaPods](http://cocoapods.org). To install
it, simply add the following line to your Podfile:

```ruby
pod 'EasyBluetooth'
```

## Author

<EMAIL_ADDRESS><EMAIL_ADDRESS>
## License

EasyBluetooth is available under the MIT license. See the LICENSE file for more info.

repository: myseven/EasyBluetooth

repo_name: myseven/EasyBluetooth


text:
---
hrs_structure:
  division: '1'
  volume: '3'
  title: '11'
  chapter: '161'
  section: 161-11
type: hrs_section
tags:
  - Government
menu:
  hrs:
    identifier: HRS_0161-0011
    parent: HRS0161
    name: 161-11 Certificate of sanitation
weight: 56035
title: Certificate of sanitation
full_title: 161-11 Certificate of sanitation
---
**PART III. LICENSING**

**§161-11 Certificate of sanitation.** The board may issue certificates of sanitation to poultry slaughterhouses and poultry processors which are subject to this chapter and which meet minimum sanitary specifications required for (1) the slaughtering of poultry for use of the poultry or poultry products in intrastate commerce, and (2) for the processing, transporting, storing, and handling of poultry or poultry products in intrastate commerce. The board may adopt rules subject to chapter 91 governing the minimum sanitary specifications and prescribing forms, requiring reports, and providing for periodic renewals of certificates of sanitation.

Notwithstanding any requirement under this chapter or the rules adopted under this chapter which require the renovation or upgrading of the physical facilities of poultry slaughterhouses or poultry processors in order to obtain a certificate of sanitation, the board, as of July 1, 1970, shall continue to issue certificates of sanitation to poultry slaughterhouses and poultry processors now licensed by the State, and shall allow them to continue their operations; provided that the facilities of the poultry slaughterhouses and poultry processors shall be sanitary and that the products which emerge from their respective operations are wholesome, not adulterated, and fit for human consumption; and provided further that upon the sale or transfer of any of the foregoing businesses, the person to whom the business is transferred shall be required to meet all of the requirements of this chapter and the rules adopted under this chapter. [L 1969, c 212, §7; am L 1993, c 92, §3]

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
| [![](https://images.microbadger.com/badges/version/scbd/drupal-code-base:dev.svg)](https://microbadger.com/images/scbd/drupal-code-base:devÂ "Get your own version badge on microbadger.com")     | [![](https://images.microbadger.com/badges/version/scbd/drupal-code-base:stg.svg)](https://microbadger.com/images/scbd/drupal-code-base:stg "Get your own version badge on microbadger.com")               |
| --------------- | ------------------------ |
|  [![CircleCI](https://circleci.com/gh/scbd/drupal-code-base/tree/dev.svg?style=shield&circle-token=a58506c78edadf94d5268ee9eb5975f720d48580)](https://circleci.com/gh/scbd/drupal-code-base/tree/dev)     | [![CircleCI](https://circleci.com/gh/scbd/drupal-code-base/tree/stg.svg?style=shield&circle-token=a58506c78edadf94d5268ee9eb5975f720d48580)](https://circleci.com/gh/scbd/drupal-code-base/tree/stg) |
|[![](https://images.microbadger.com/badges/image/scbd/drupal-code-base:dev.svg)](https://microbadger.com/images/scbd/drupal-code-base:dev "Get your own image badge on microbadger.com")| [![](https://images.microbadger.com/badges/image/scbd/drupal-code-base:stg.svg)](https://microbadger.com/images/scbd/drupal-code-base:stg "Get your own image badge on microbadger.com")|
| [![Maintainability](https://api.codeclimate.com/v1/badges/96c7ed474e6495c1cf66/maintainability)](https://codeclimate.com/github/scbd/drupal-code-base/maintainability)| [![Maintainability](https://api.codeclimate.com/v1/badges/96c7ed474e6495c1cf66/maintainability)](https://codeclimate.com/github/scbd/drupal-code-base/maintainability) |

TODO:

- auto import db local and server env
- bug in encrypted config - Could not open input file: security-checker.phar
- auto sync 'files' from canonical site (one way) possible s3 module
- cli export

- test theme
<<<<<<< HEAD

=======
- cron container
>>>>>>> badges

- test module

- install search/solr
- instal seo module

- circle ci - simple tests

repository: scbd/drupal-code-base

gha_language: PHP

repo_name: scbd/drupal-code-base


text:
# ZLXibTool

[![CI Status](https://img.shields.io/travis/ZLDamo<EMAIL_ADDRESS>[![Version](https://img.shields.io/cocoapods/v/ZLXibTool.svg?style=flat)](https://cocoapods.org/pods/ZLXibTool)
[![License](https://img.shields.io/cocoapods/l/ZLXibTool.svg?style=flat)](https://cocoapods.org/pods/ZLXibTool)
[![Platform](https://img.shields.io/cocoapods/p/ZLXibTool.svg?style=flat)](https://cocoapods.org/pods/ZLXibTool)

## Example

To run the example project, clone the repo, and run `pod install` from the Example directory first.The constraints in xib are automatically adapted to fit in a wide scale
```
self.tool = [ZLXibTool tool];
[self.tool setSubViewsConstraint:self.view];
```

## Requirements

## Installation

ZLXibTool is available through [CocoaPods](https://cocoapods.org). To install
it, simply add the following line to your Podfile:

```ruby
pod 'ZLXibTool'
```

## Author

<EMAIL_ADDRESS><EMAIL_ADDRESS>
## License

ZLXibTool is available under the MIT license. See the LICENSE file for more info.

repository: ZLDamo/ZLXibTool

repo_name: ZLDamo/ZLXibTool


text:
# Lembosia quercicola Katum. SPECIES

#### Status
ACCEPTED

#### According to
Index Fungorum

#### Published in
Bulletin of the Faculty of Agriculture, Yamaguchi University 26: 85 (1975)

#### Original name
Lembosia quercicola Katum.

### Remarks
null

repository: mdoering/backbone

repo_name: mdoering/backbone


text:
---
title: About
subtitle: This is a meta post!
episode: meta
description: Meta posts are awesome!
---
By creating a post and making it's episode property in the header `meta` instead of a number, you can create a *meta post*, which will automatically appear as a link in the sidebar.

Meta posts can be used to create About pages or similar things outside the normal episode structure of a serious story.

repository: ChapelR/serious-npm

gha_language: JavaScript

repo_name: ChapelR/serious-npm


text:
### Disclaimer

Please note that this code example is more suited for people that have at least beginners experience using C#.

### Prerequisites

To run this code you will need a C# compiler:

* [Visual Studio with Visual Basic](https://docs.microsoft.com/en-us/visualstudio/ide/quickstart-visual-basic-console?view=vs-2019)

### Installation

The following example is built with Visual Studio, you can run it using these steps:

1. Create a new Console Application.
2. Using a terminal of your choice navigate to the projects directory.
3. Run the cURL command to download the code or copy it directly from [here](https://raw.githubusercontent.com/Proxyverse/Proxyverse/master/csharp/csharp.cs):

`curl https://raw.githubusercontent.com/Proxyverse/Proxyverse/main/csharp/csharp.cs > csharp.cs`

4. You should see a new file named csharp.cs in your project folder.

### Usage

To run this C# example, setup your username, password and endpoint you would like to use, change the according lines in within punctuation marks ('').

If you did everything correctly, you should see an IP appearing form our proxy server in the console window.

## Need help?
Email -<EMAIL_ADDRESS>

repository: Proxyverse/Proxyverse

branch_name: refs/heads/main

repo_name: Proxyverse/Proxyverse


text:
# Change Log

* 5.5.0
  * Add ability to specify the node_modules relative dir ([#689][] @ypxing)
  * Fix the spawn E2BIG error when zipping ([#813][] @j0k3r)
  * Extends the --no-build option to serverless offline start ([#770][] @nponeccop)
  * Add Serverless Container Support ([#723][] @rogersgt)
  * Add support for Yarn network-concurrency option ([#550][] @cfroese )

[#689]: https://github.com/serverless-heaven/serverless-webpack/pull/689
[#813]: https://github.com/serverless-heaven/serverless-webpack/pull/813
[#770]: https://github.com/serverless-heaven/serverless-webpack/pull/770
[#723]: https://github.com/serverless-heaven/serverless-webpack/pull/723
[#550]: https://github.com/serverless-heaven/serverless-webpack/pull/550

* 5.4.2
  * Regression Fix: Empty lines while stats: 'errors-only' ([#773][] @Enase)
  * Add type to CLI options ([#774][] @j0k3r)
  * Add Serverless v2 compatibility ([#775][] @nponeccop)
  * Support local errors with NPM 7 workspaces ([#782][] @mikejpeters)
  * Fix `excludeRegex` option and allow dotfiles to be packaged ([#780][] @l1b3r)
  * Correctly handle packaging for function during `deploy -f` ([#794][] @pgrzesik)

[#773]: https://github.com/serverless-heaven/serverless-webpack/pull/773
[#774]: https://github.com/serverless-heaven/serverless-webpack/pull/774
[#775]: https://github.com/serverless-heaven/serverless-webpack/pull/775
[#782]: https://github.com/serverless-heaven/serverless-webpack/pull/782
[#780]: https://github.com/serverless-heaven/serverless-webpack/pull/780
[#794]: https://github.com/serverless-heaven/serverless-webpack/pull/794

* 5.4.1
  * Display the zip method used ([#735][] @j0k3r)
  * Dependabot should now updates package.json too ([#742][] @j0k3r)
  * Fix configuration check for `keepOutputDirectory` in cleanup ([#748][] @daryl-c)
  * Prevent ts-node being registered twice ([#766][] @apancutt)
  * Fix external modules with webpack 5 ([#746][] @janicduplessis)
  * Allow custom webpack config files to export as an ES6 module (interop default) ([#767][] @apancutt)

[#735]: https://github.com/serverless-heaven/serverless-webpack/pull/735
[#742]: https://github.com/serverless-heaven/serverless-webpack/pull/742
[#748]: https://github.com/serverless-heaven/serverless-webpack/pull/748
[#766]: https://github.com/serverless-heaven/serverless-webpack/pull/766
[#746]: https://github.com/serverless-heaven/serverless-webpack/pull/746
[#767]: https://github.com/serverless-heaven/serverless-webpack/pull/767

* 5.4.0
  * Skip compile & packaging if `--no-build` is set [#560](https://github.com/serverless-heaven/serverless-webpack/pull/560)
  * Serialized compile to address [#299](https://github.com/serverless-heaven/serverless-webpack/pull/299) [#517](https://github.com/serverless-heaven/serverless-webpack/pull/517)
  * Add concurrency support for more than one thread [#681](https://github.com/serverless-heaven/serverless-webpack/pull/681)
  * Option to exclude files using regular expression [#612](https://github.com/serverless-heaven/serverless-webpack/pull/612)
  * Speed up cleanup process [#462](https://github.com/serverless-heaven/serverless-webpack/pull/462)
  * Allow custom runtime if Nodejs based [#675](https://github.com/serverless-heaven/serverless-webpack/pull/675)
  * Convert packageModules to use bestzip instead of archiver [#596](https://github.com/serverless-heaven/serverless-webpack/pull/596)
  * Fix external modules version for transitive dependencies [#541](https://github.com/serverless-heaven/serverless-webpack/pull/541) (see [#507](https://github.com/serverless-heaven/serverless-webpack/pull/507))
  * Support noFrozenLockfile options [#687](https://github.com/serverless-heaven/serverless-webpack/pull/687)
  * Don't package non-node functions (fix for [#644](https://github.com/serverless-heaven/serverless-webpack/issues/644)) [#663](https://github.com/serverless-heaven/serverless-webpack/pull/663)
  * Testing with Node.js 14.x [#688](https://github.com/serverless-heaven/serverless-webpack/pull/688)
  * Replace `babel-eslint` by `@babel/eslint-parser` [#713](https://github.com/serverless-heaven/serverless-webpack/pull/713)

* 5.3.5
  * Improve runtime validation [#629](https://github.com/serverless-heaven/serverless-webpack/pull/629)
  * Move `ts-node` as optional dependency [#636](https://github.com/serverless-heaven/serverless-webpack/pull/636)
  * Upgrade deps [#637](https://github.com/serverless-heaven/serverless-webpack/pull/637)

* 5.3.4
  * Bump lodash from 4.17.15 to 4.17.19 [#597](https://github.com/serverless-heaven/serverless-webpack/pull/597)
  * Bump lodash from 4.17.15 to 4.17.19 in /examples/typescript [#598](https://github.com/serverless-heaven/serverless-webpack/pull/598)
  * Bump lodash from 4.17.4 to 4.17.19 in /examples/multiple-statically-entries [#599](https://github.com/serverless-heaven/serverless-webpack/pull/599)
  * Bump lodash from 4.17.4 to 4.17.19 in /examples/include-external-npm-packages [#600](https://github.com/serverless-heaven/serverless-webpack/pull/600)
  * Bump lodash from 4.17.4 to 4.17.19 in /examples/babel-multiple-statically-entries [#601](https://github.com/serverless-heaven/serverless-webpack/pull/601)
  * Bump lodash from 4.17.4 to 4.17.19 in /examples/babel [#603](https://github.com/serverless-heaven/serverless-webpack/pull/603)
  * Ignore more files from NPM [#609](https://github.com/serverless-heaven/serverless-webpack/pull/609)
  * Update all examples [#626](https://github.com/serverless-heaven/serverless-webpack/pull/626)

* 5.3.3
  * default webpackConfig.node should be false [#502](https://github.com/serverless-heaven/serverless-webpack/pull/502)
  * Fix yarn list --json stdOut parsing [#516](https://github.com/serverless-heaven/serverless-webpack/pull/516)
  * Updated release notes [#585](https://github.com/serverless-heaven/serverless-webpack/pull/585)
  * Updated Node versions in CI [#587](https://github.com/serverless-heaven/serverless-webpack/pull/587)
  * Remove optional peer dependencies [#542](https://github.com/serverless-heaven/serverless-webpack/pull/542)
  * Check for node runtimes first [#579](https://github.com/serverless-heaven/serverless-webpack/pull/579)
  * Bumps lodash from 4.17.15 to 4.17.19 [#602](https://github.com/serverless-heaven/serverless-webpack/pull/602)

* 5.3.2
  * Fix eslint prettier [#518](https://github.com/serverless-heaven/serverless-webpack/pull/518)
  * Add TypeScript definition [#520](https://github.com/serverless-heaven/serverless-webpack/pull/520)
  * Project dependencies updated [#524](https://github.com/serverless-heaven/serverless-webpack/pull/524)
  * fix typescript example lockfile [#526](https://github.com/serverless-heaven/serverless-webpack/pull/526)
  * Typescript example babel loader [#527](https://github.com/serverless-heaven/serverless-webpack/pull/527)
  * Bump tar from 2.2.1 to 2.2.2 in /examples/babel [#544](https://github.com/serverless-heaven/serverless-webpack/pull/544)
  * Bump acorn from 6.3.0 to 6.4.1 in /examples/typescript [#562](https://github.com/serverless-heaven/serverless-webpack/pull/562)
  * Bump eslint-utils from 1.4.0 to 1.4.3 [#567](https://github.com/serverless-heaven/serverless-webpack/pull/567)
  * Bump handlebars from 4.1.2 to 4.7.6 [#568](https://github.com/serverless-heaven/serverless-webpack/pull/568)
  * Addressed npm security vulnerabilities [#569](https://github.com/serverless-heaven/serverless-webpack/pull/569)
  * Bump https-proxy-agent from 2.2.2 to 2.2.4 [#572](https://github.com/serverless-heaven/serverless-webpack/pull/572)
  * Bump https-proxy-agent from 2.2.2 to 2.2.4 in /examples/typescript [#573](https://github.com/serverless-heaven/serverless-webpack/pull/573)
  * Bump extend from 3.0.1 to 3.0.2 in /examples/babel [#574](https://github.com/serverless-heaven/serverless-webpack/pull/574)
  * Bump stringstream from 0.0.5 to 0.0.6 in /examples/babel [#575](https://github.com/serverless-heaven/serverless-webpack/pull/575)
  * Bump tough-cookie from 2.3.2 to 2.3.4 in /examples/babel [#576](https://github.com/serverless-heaven/serverless-webpack/pull/576)
  * Bump sshpk from 1.13.1 to 1.16.1 in /examples/babel [#577](https://github.com/serverless-heaven/serverless-webpack/pull/577)
  * Bump debug from 2.6.8 to 2.6.9 in /examples/babel [#578](https://github.com/serverless-heaven/serverless-webpack/pull/578)

* 5.3.1
  * Fixed bug that prevented to use handlers using import [#505][link-505]
  * Do not print empty lines in webpack stats [#499][link-499]
  * Added git hooks to improved code quality and developer experience [#496][link-496]

* 5.3.0
  * Restore compatibility with TypeScript [#449][link-449] [#465][link-465]
  * Allow glob for excludeFiles [#471][link-471]
  * Support Webpack 5 [#472][link-472]
  * Use colored output depending on tty [#480][link-480]
  * Allow to keep webpack folder [#453][link-453] [#467][link-467]
  * Add ability to exclude files from handler lookup [#433][link-433]
  * Documentation fixes [#429][link-429]

* 5.2.0
  * Show info message in verbose mode if aws-sdk has been excluded automatically [#393][link-393]
  * Added support for asynchronous webpack configuration [#412][link-412]
  * Better error message if handlers are not found [#418][link-418]

* 5.1.5
  * Re-publish of 5.1.4 without yarn.lock

* 5.1.4
  * Fix support for Yarn resolutions definitions [#379][link-379]
  * Better debugging for "Unable to import module ..." errors: Detect runtime dependencies that are only declared as devDependencies [#384][link-384]
  * Documentation updates [#382][link-382]

* 5.1.3
  * Fixed issue with Yarn and file references as dependencies [#370][link-370]

* 5.1.2
  * Fixed issue that leads to `Unexpected end of JSON` in projects with lots of dependencies [#309][link-309][#373][link-373]
  * Update webpack-4 example with VSCode debugging configuration [#365][link-365]

* 5.1.1
  * Fixed local invoke watch mode not executing changed files [#349][link-349]
  * Added Webpack 4 example [#355][link-355]
  * Documentation updates [#354][link-354]

* 5.1.0
  * Support Yarn [#286][link-286]
  * Allow local invoke to use existing compiled output [#341][link-341] [#275][link-275]
  * Support custom packager scripts [#343][link-343] [#342][link-342]

* 5.0.0
  * Support Webpack 4 [#331][link-331] [#328][link-328]
  * BREAKING: Drop support for Webpack 2
  * Allow to check for local invocation in the webpack configuration [#232][link-232]
  * New centralized configuration with fallback to the old one [#336][link-336]
  * Improved unit tests and actual coverage calculation [#337][link-337]

* 4.4.0
  * Support serverless-step-functions-offline [#313][link-313]
  * Fixed webpack documentation links [#326][link-326]
  * Abstracted packager interface [#329][link-329]

* 4.3.0
  * Add new `webpack:compile:watch:compile` event [#315][link-315]
  * Added note to README about using yarn [#316][link-316]
  * Made babel dynamic example the default babel example [#253][link-253]
  * Documentation fixes [#317][link-317] [#321][link-321]

* 4.2.0
  * Support local file references in package.json [#263][link-263]
  * Updated used tools (dev dependencies)

* 4.1.0
  * Prohibit manual entry configuration with individual packaging [#272][link-272]
  * Fixed bug with stats in webpack config for individual packaging [#278][link-278]
  * Fixed bug with startup order in combination with serverless-offline [#279][link-279]
  * Default target to "node" if not set [#276][link-276]
  * Support `serverless run` including watch mode [#269][link-269]

* 4.0.0
  * BREAKING: Expose lifecycle events for plugin authors [#254][link-254]
  * Fixed deprecated hook warning [#126][link-126]
  * Support forceExclude option for external modules [#247][link-247]
  * Support stats output configuration in webpack config [#260][link-260]
  * Google: Only integrate package.json but not node modules into artifact [#264][link-264]
  * Documentation fixes and updates [#265][link-265]
  * Updated examples [#250][link-250]

* 3.1.2
  * Fix issue where dependencies with dots in their names would not be installed [#251][link-251]

* 3.1.1
  * Fix issue where locked dependencies (package-lock.json) were ignored [#245][link-245]

* 3.1.0
  * Allow filesystem polling in watch mode (`--webpack-use-polling`) [#215][link-215]
  * Allow forced include of not referenced modules [#217][link-217]
  * Automatically include peer dependencies of used modules [#223][link-223]
  * Show explicit message if the provided webpack config can not be loaded [#234][link-234]
  * Improve examples [#227][link-227]
  * Update 3rd party provider compatibility table [#221][link-221]
  * Added automatic Travis and Coveralls builds to increase stability

* 3.0.0
  * Integrate with `serverless invoke local` [#151][link-151]
  * Support watch mode with `serverless invoke local --watch`
  * Stabilized and improved the bundling of node modules [#116][link-116], [#117][link-117]
  * Improved interoperability with Serverless and 3rd party plugins [#173][link-173]
  * Support individual packaging of the functions in a service [#120][link-120]
  * Allow setting stdio max buffers for NPM operations [#185][link-185]
  * Support bundling of node modules via node-externals whitelist [#186][link-186]
  * Removed the `webpack serve` command in favor of [`serverless-offline`](https://www.npmjs.com/package/serverless-offline) [#152][link-152]
  * Updated examples [#179][link-179]
  * Added missing unit tests to improve code stability
  * Fixed unit tests to run on Windows [#145][link-145]

* 2.2.2
  * Reverted breaking change introduced in default output config [#202][link-202]

* 2.2.1
  * Restore functionality for Google provider [#193][link-193]

* 2.2.0
  * Allow full dynamic configurations [#158][link-158]
  * Fix a bug that prevented the entries lib export to work with TypeScript [#165][link-165]

* 2.1.0
  * Added support for webpack configuration in TypeScript format [#129][link-129]
  * Fixed bug with serverless-offline exec [#154][link-154]
  * Added unit tests for cleanup. Updated test framework [#11][link-11]
  * Support single function deploy and packaging [#107][link-107]
  * Fixed path exception bug with individual packaging and SLS 1.18 [#159][link-159]

* 2.0.0
  * Support arbitrary Webpack versions as peer dependency [#83][link-83]
  * Support `serverless offline start` invocation [#131][link-131]
  * Documentation updates [#88][link-88], [#132][link-132], [#140][link-140], [#141][link-141], [#144][link-144]
  * Print Webpack stats on recompile [#127][link-127]

[comment]: # (Referenced issues)

[link-135]: https://github.com/serverless-heaven/serverless-webpack/issues/135

[link-83]: https://github.com/serverless-heaven/serverless-webpack/pull/83
[link-88]: https://github.com/serverless-heaven/serverless-webpack/pull/88
[link-127]: https://github.com/serverless-heaven/serverless-webpack/pull/127
[link-131]: https://github.com/serverless-heaven/serverless-webpack/pull/131
[link-132]: https://github.com/serverless-heaven/serverless-webpack/pull/132
[link-140]: https://github.com/serverless-heaven/serverless-webpack/pull/140
[link-141]: https://github.com/serverless-heaven/serverless-webpack/issues/141
[link-144]: https://github.com/serverless-heaven/serverless-webpack/issues/144

[link-11]: https://github.com/serverless-heaven/serverless-webpack/issues/11
[link-107]: https://github.com/serverless-heaven/serverless-webpack/issues/107
[link-129]: https://github.com/serverless-heaven/serverless-webpack/pull/129
[link-154]: https://github.com/serverless-heaven/serverless-webpack/issues/154
[link-159]: https://github.com/serverless-heaven/serverless-webpack/issues/159

[link-158]: https://github.com/serverless-heaven/serverless-webpack/issues/158
[link-165]: https://github.com/serverless-heaven/serverless-webpack/issues/165

[link-193]: https://github.com/serverless-heaven/serverless-webpack/issues/193

[link-116]: https://github.com/serverless-heaven/serverless-webpack/issues/116
[link-117]: https://github.com/serverless-heaven/serverless-webpack/issues/117
[link-120]: https://github.com/serverless-heaven/serverless-webpack/issues/120
[link-145]: https://github.com/serverless-heaven/serverless-webpack/issues/145
[link-151]: https://github.com/serverless-heaven/serverless-webpack/issues/151
[link-152]: https://github.com/serverless-heaven/serverless-webpack/issues/152
[link-173]: https://github.com/serverless-heaven/serverless-webpack/issues/173
[link-179]: https://github.com/serverless-heaven/serverless-webpack/pull/179
[link-185]: https://github.com/serverless-heaven/serverless-webpack/pull/185
[link-186]: https://github.com/serverless-heaven/serverless-webpack/pull/186

[link-202]: https://github.com/serverless-heaven/serverless-webpack/issues/202

[link-215]: https://github.com/serverless-heaven/serverless-webpack/issues/215
[link-217]: https://github.com/serverless-heaven/serverless-webpack/issues/217
[link-221]: https://github.com/serverless-heaven/serverless-webpack/pull/221
[link-223]: https://github.com/serverless-heaven/serverless-webpack/issues/223
[link-227]: https://github.com/serverless-heaven/serverless-webpack/pull/227
[link-234]: https://github.com/serverless-heaven/serverless-webpack/pull/234

[link-245]: https://github.com/serverless-heaven/serverless-webpack/issues/245

[link-251]: https://github.com/serverless-heaven/serverless-webpack/issues/251

[link-126]: https://github.com/serverless-heaven/serverless-webpack/issues/126
[link-247]: https://github.com/serverless-heaven/serverless-webpack/issues/247
[link-250]: https://github.com/serverless-heaven/serverless-webpack/issues/250
[link-254]: https://github.com/serverless-heaven/serverless-webpack/pull/254
[link-260]: https://github.com/serverless-heaven/serverless-webpack/issues/260
[link-264]: https://github.com/serverless-heaven/serverless-webpack/pull/264
[link-265]: https://github.com/serverless-heaven/serverless-webpack/pull/265

[link-272]: https://github.com/serverless-heaven/serverless-webpack/issues/272
[link-278]: https://github.com/serverless-heaven/serverless-webpack/pull/278
[link-279]: https://github.com/serverless-heaven/serverless-webpack/issues/279
[link-276]: https://github.com/serverless-heaven/serverless-webpack/issues/276
[link-269]: https://github.com/serverless-heaven/serverless-webpack/issues/269

[link-263]: https://github.com/serverless-heaven/serverless-webpack/issues/263

[link-286]: https://github.com/serverless-heaven/serverless-webpack/issues/286

[link-315]: https://github.com/serverless-heaven/serverless-webpack/issues/315
[link-316]: https://github.com/serverless-heaven/serverless-webpack/issues/316
[link-253]: https://github.com/serverless-heaven/serverless-webpack/issues/253
[link-317]: https://github.com/serverless-heaven/serverless-webpack/pull/317
[link-321]: https://github.com/serverless-heaven/serverless-webpack/pull/321

[link-313]: https://github.com/serverless-heaven/serverless-webpack/pull/313
[link-326]: https://github.com/serverless-heaven/serverless-webpack/pull/326
[link-329]: https://github.com/serverless-heaven/serverless-webpack/issues/329

[link-232]: https://github.com/serverless-heaven/serverless-webpack/issues/232
[link-331]: https://github.com/serverless-heaven/serverless-webpack/issues/331
[link-328]: https://github.com/serverless-heaven/serverless-webpack/pull/328
[link-336]: https://github.com/serverless-heaven/serverless-webpack/pull/336
[link-337]: https://github.com/serverless-heaven/serverless-webpack/pull/337

[link-275]: https://github.com/serverless-heaven/serverless-webpack/issues/275
[link-286]: https://github.com/serverless-heaven/serverless-webpack/issues/286
[link-341]: https://github.com/serverless-heaven/serverless-webpack/issues/341
[link-342]: https://github.com/serverless-heaven/serverless-webpack/issues/342
[link-343]: https://github.com/serverless-heaven/serverless-webpack/issues/343

[link-349]: https://github.com/serverless-heaven/serverless-webpack/issues/349
[link-354]: https://github.com/serverless-heaven/serverless-webpack/pull/354
[link-355]: https://github.com/serverless-heaven/serverless-webpack/pull/355

[link-309]: https://github.com/serverless-heaven/serverless-webpack/issues/309
[link-365]: https://github.com/serverless-heaven/serverless-webpack/pull/365
[link-373]: https://github.com/serverless-heaven/serverless-webpack/pull/373

[link-370]: https://github.com/serverless-heaven/serverless-webpack/issues/370

[link-379]: https://github.com/serverless-heaven/serverless-webpack/issues/379
[link-382]: https://github.com/serverless-heaven/serverless-webpack/pull/382
[link-384]: https://github.com/serverless-heaven/serverless-webpack/pull/384

[link-393]: https://github.com/serverless-heaven/serverless-webpack/issues/393
[link-412]: https://github.com/serverless-heaven/serverless-webpack/issues/412
[link-418]: https://github.com/serverless-heaven/serverless-webpack/issues/418

[link-453]: https://github.com/serverless-heaven/serverless-webpack/issues/453
[link-467]: https://github.com/serverless-heaven/serverless-webpack/issues/467
[link-449]: https://github.com/serverless-heaven/serverless-webpack/issues/449
[link-465]: https://github.com/serverless-heaven/serverless-webpack/issues/465
[link-480]: https://github.com/serverless-heaven/serverless-webpack/issues/480
[link-429]: https://github.com/serverless-heaven/serverless-webpack/pull/429
[link-433]: https://github.com/serverless-heaven/serverless-webpack/issues/433
[link-471]: https://github.com/serverless-heaven/serverless-webpack/issues/471
[link-472]: https://github.com/serverless-heaven/serverless-webpack/pull/472

[link-505]: https://github.com/serverless-heaven/serverless-webpack/issues/505
[link-499]: https://github.com/serverless-heaven/serverless-webpack/issues/499
[link-496]: https://github.com/serverless-heaven/serverless-webpack/pull/496

repository: RichSlaton/UserForm

repo_name: RichSlaton/UserForm


text:
---
type: introduction
page: conclusion
locale: en-US
---

You know how you sometimes start tweaking a few lines of code here and there, then realize a couple functions could use some refactoring, and then one things leading to another you find yourself a few days later in the process of setting up a brand new stack complete with a database and GraphQL API?

This is what happened to us this year. And while it resulted in quite a few stressful evenings as we tried to wrap this up and release the State of JavaScript 2019 results in, well, 2019; it also means we now have a much more powerful and flexible stack to collect and analyze data going forward.

This will come in handy to analyze the evolution of all the new tools starting to make waves such as Svelte, Stencil, Sporky, Nest, or Flutter. And yes, I did just make up one of those five, but admit it: you had a moment of doubt didn’t you?

But don’t worry. No matter how many weirdly-named libraries the community keeps throwing at you, we’ll be there to help make sense of all this chaos… that is, if we’re not too busy going through yet another refactoring to get our code just perfect!

– Sacha & Raphaël

gha_license_id: NOASSERTION


text:
Synaptics touchpad driver for X.Org
===================================

This project is forked from: [https://github.com/dieghen89/xserver-xorg-input-synaptics](https://github.com/dieghen89/xserver-xorg-input-synaptics)

which is alredy based on: [https://github.com/felipejfc/xserver-xorg-input-synaptics](https://github.com/felipejfc/xserver-xorg-input-synaptics)

And fixes this issue [https://github.com/felipejfc/xserver-xorg-input-synaptics/issues/1](https://github.com/felipejfc/xserver-xorg-input-synaptics/issues/1)

This driver has been tested on Ubuntu 15.04 with a Dell Inspiron 15 5000 series.

Below is the original README from [felipejfc](https://github.com/felipejfc)

ABOUT
-----

In this fork I've put back SynapticsSHM into the driver to be able to use synclient monitor mode, so that the user can use xSwipe again for example.
This also add support to 4 and 5 finger click on some more trackpads, It worked on my XPS14.

HOW TO COMPILE AND INSTALL
--------------------------

**First run**

```
./autogen.sh
```

And the script will tell you all the dependencies you'll have to install in order to make.
Run the command again and again until you've resolved all the dependencies and can run ./autogen.sh without errors.

**Uninstall current installed synaptics driver from the system**

```
sudo apt-get remove xserver-xorg-input-synaptics
```

**The compile and install**

```
./configure --exec_prefix=/usr
make
sudo make install
```

Reboot and you're done!

repository: Chosko/xserver-xorg-input-synaptics

repo_name: Chosko/xserver-xorg-input-synaptics


text:
# eslint-plugin-dfsx
eslint plugin customized for d.f.s.x company

# rules

* dfsx-camelcase: flag non-camelcased identifiers except assignment statement

repository: dfsxdev/eslint-plugin-dfsx

repo_name: dfsxdev/eslint-plugin-dfsx


text:
# PoseNet Face Detection

### About
Quickly detect multiple faces within a group photo. This **browser-side utility** takes an image ([Image Data URL](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs)) with multiple people, such as group photo / selfie / portrait / etc. and outputs an array of faces (Image Data URLs). Additional controls include ability to control the accuracy of the image and maximum number of faces to be detected from the orignal image.

#### Privacy
Images or image data is not saved or uploaded to any cloud service. All detections happen on the browser side without leaving the device. Utility does not require an active internet connection at runtime.

### Usage
Because **PoseNet Face Detection** leverages TensorflowJS and PoseNet model to identify body landmarks, these packages must be first imported.

```
<script<EMAIL_ADDRESS></script>
<script src="https://cdn.jsdelivr.net/npm/@tensorflow-models/posenet"></script>

<!-- Finally, also include`face-detection.js` -->
<script src="https://cdn.jsdelivr.net/gh/mppise/posenet-face-detection/src/index.js"></script>
```

Once the packages are imported,

Assuming you have an input control to upload an image,

```
<input type="file" name="imagePicker" id="imagePicker"
    onChange="loadImageFromDevice(event)"
    accept="image/png, image/jpeg">
```

1. upload an image using FileReader object

```
 function loadImageFromDevice(event) {
    const file = event.target.files[0];
    const reader = new FileReader();
    reader.readAsDataURL(file);
    reader.onload = () => {
        let imageDataURL = reader.result;
        /*
        ..
        .. [to step 2]
        ..
        */
    };
 }
```

2. Call`detectFaces(imageDataURL)`, which returns a promise.

An optional `options` object  can be passed containing following parameters. Note: All parameters are optional.

```
let options = {
    accuracy: 0.4,  // default: 0.2, i.e. 20%
    maxFaces: 5,    // default: 10
};

detectFaces(imageDataURL, options)
    .then((faces) => {
        console.log(faces); // Array of faces as Image Data URL's.
          /*
        ..
        .. [display images within 'img' tags]
        .. [e.g. document.getElementById('face1').setAttribute('src') = faces[0]]
        ..
        */
    }).catch((err) => console.log(err));
```

  ![Face Detection in action](facedetectioninaction.gif)

### Demo
Clone this repository and run `index.html` within the `demo/` directory.

### References:
- [Pose Detection in the Browser: PoseNet Model](https://github.com/tensorflow/tfjs-models/tree/master/posenet)
- [Real-time Human Pose Estimation in the Browser with TensorFlow.js](https://medium.com/tensorflow/real-time-human-pose-estimation-in-the-browser-with-tensorflow-js-7dd0bc881cd5)

repository: mppise/posenet-face-detection

repo_name: mppise/posenet-face-detection


text:
# Adding new ensembles

One of the powerful tools in OpenPathSampling is its flexible way of defining
path ensembles. To add a specialized ensemble, create a file (module) with your
new ensemble, and import any public classes/functions in the
`ensembles/__init__.py` file.

repository: dwhswenson/openpathsampling

gha_language: Python

repo_name: dwhswenson/openpathsampling


text:
Backstab
===============================================================================

>

Development Instructions
-------------------------------------------------------------------------------

The following `npm` scripts are available to you, performing the tasks as
described below.

```sh
npm start     # Launch a development server. Same as `gulp dev`.
npm run dist  # Prepare the game release for distribution. Also `gulp dist`.
npm run clean # Delete temporary and distribution build files.
```

<small>Also, you may want to install Gulp and Bower globally, but you are not
required to do so.</small>

Should you consider distributing your game as an open source project, please
[include a LICENSE file][lcnc] in your project root.

Congrats and happy coding!

<!-- ---------------------------------------------------------------------- -->

[lcnc]: http://choosealicense.com

repository: begedin/backstab

branch_name: refs/heads/development

repo_name: begedin/backstab


text:
# HPOBench

HPOBench is a library for hyperparameter optimization and black-box optimization benchmark with a focus on reproducibility.

**Note:** HPOBench is under active construction. Stay tuned for more benchmarks. Information on how to contribute a new benchmark will follow shortly.

**Note:** "If you are looking for a different or older version of our benchmarking library, you might be looking for
 [HPOlib1.5](https://github.com/automl/HPOlib1.5)

## In 4 lines of code

Run a random configuration within a singularity container
```python
from hpobench.container.benchmarks.ml.xgboost_benchmark import XGBoostBenchmark
b = XGBoostBenchmark(task_id=167149, container_source='library://phmueller/automl', rng=1)
config = b.get_configuration_space(seed=1).sample_configuration()
result_dict = b.objective_function(configuration=config, fidelity={"n_estimators": 128, "subsample": 0.5}, rng=1)
```

All benchmarks can also be queried with fewer or no fidelities:

```python
from hpobench.container.benchmarks.ml.xgboost_benchmark import XGBoostBenchmark
b = XGBoostBenchmark(task_id=167149, container_source='library://phmueller/automl', rng=1)
config = b.get_configuration_space(seed=1).sample_configuration()
result_dict = b.objective_function(configuration=config, fidelity={"n_estimators": 128,}, rng=1)
result_dict = b.objective_function(configuration=config, rng=1)
```

Containerized benchmarks do not rely on external dependencies and thus do not change. To do so, we rely on [Singularity (version 3.5)](https://sylabs.io/guides/3.5/user-guide/).

Further requirements are: [ConfigSpace](https://github.com/automl/ConfigSpace), *scipy* and *numpy*

**Note:** Each benchmark can also be run locally, but the dependencies must be installed manually and might conflict with other benchmarks.
 This can be arbitrarily complex and further information can be found in the docstring of the benchmark.

A simple example is the XGBoost benchmark which can be installed with `pip install .[xgboost]`
```python
from hpobench.benchmarks.ml.xgboost_benchmark import XGBoostBenchmark
b = XGBoostBenchmark(task_id=167149)
config = b.get_configuration_space(seed=1).sample_configuration()
result_dict = b.objective_function(configuration=config, fidelity={"n_estimators": 128, "subsample": 0.5}, rng=1)

```

## Installation

Before we start, we recommend using a virtual environment. To run any benchmark using its singularity container,
run the following:
```
git clone https://github.com/automl/HPOBench.git
cd HPOBench
pip install .
```

**Note:** This does not install *singularity (version 3.5)*. Please follow the steps described here: [user-guide](https://sylabs.io/guides/3.5/user-guide/quick_start.html#quick-installation-steps).

## Available Containerized Benchmarks

| Benchmark Name                    | Container Name     | Container Source                     | Hosted at | Additional Info                      |
| :-------------------------------- | ------------------ | ------------------------------------ | ----------|-------------------------------------- |
| XGBoostBenchmark                  | xgboost_benchmark  | library://phmueller/automl/xgboost_benchmark | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f610eae86dd3232deb5a5) | Works with OpenML task ids |
| CartpoleFull                      | cartpole           | library://phmueller/automl/cartpole  | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f310084a01836e4395601) | Not deterministic                    |
| CartpoleReduced                   | cartpole           | library://phmueller/automl/cartpole  | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f310084a01836e4395601) | Not deterministic                    |
| Learna                            | learna_benchmark   | library://phmueller/automl/learna_benchmark | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f31c3b1793638c1134e58) | Not deterministic                    |
| MetaLearna                        | learna_benchmark   | library://phmueller/automl/learna_benchmark | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f31c3b1793638c1134e58) | Not deterministic                    |
| SliceLocalizationBenchmark        | tabular_benchmarks | library://phmueller/automl/tabular_benchmarks | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f630cb1793638c1134e5d) | Loading may take several minutes     |
| ProteinStructureBenchmark         | tabular_benchmarks | library://phmueller/automl/tabular_benchmarks | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f630cb1793638c1134e5d) | Loading may take several minutes     |
| NavalPropulsionBenchmark          | tabular_benchmarks | library://phmueller/automl/tabular_benchmarks | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f630cb1793638c1134e5d) | Loading may take several minutes     |
| ParkinsonsTelemonitoringBenchmark | tabular_benchmarks | library://phmueller/automl/tabular_benchmarks | [Sylabs](https://cloud.sylabs.io/library/_container/5f0f630cb1793638c1134e5d) | Loading may take several minutes     |
| NASCifar10ABenchmark              | nasbench_101       | library://phmueller/automl/nasbench_101 | [Sylabs](https://cloud.sylabs.io/library/_container/5f227263b1793638c1135c37) |                                     |
| NASCifar10BBenchmark              | nasbench_101       | library://phmueller/automl/nasbench_101 | [Sylabs](https://cloud.sylabs.io/library/_container/5f227263b1793638c1135c37) |                                     |
| NASCifar10CBenchmark              | nasbench_101       | library://phmueller/automl/nasbench_101 | [Sylabs](https://cloud.sylabs.io/library/_container/5f227263b1793638c1135c37) |                                     |

## Further Notes

### How to build a container locally

With singularity installed run the following to built the xgboost container

```bash
cd hpobench/container/recipes/ml
sudo singularity build xgboost_benchmark Singularity.XGBoostBenchmark
```

You can use this local image with:

```python
from hpobench.container.benchmarks.ml.xgboost_benchmark import XGBoostBenchmark
b = XGBoostBenchmark(task_id=167149, container_name="xgboost_benchmark",
                     container_source='./') # path to hpobench/container/recipes/ml
config = b.get_configuration_space(seed=1).sample_configuration()
result_dict = b.objective_function(config, fidelity={"n_estimators": 128, "subsample": 0.5})
```

### Remove all caches

#### HPOBench data
HPOBench stores downloaded containers and datasets at the following locations:

```bash
$XDG_CONFIG_HOME # ~/.config/hpobench
$XDG_CACHE_HOME # ~/.cache/hpobench
$XDG_DATA_HOME # ~/.local/share/hpobench
```

For crashes or when not properly shutting down containers, there might be socket files left under `/tmp/`.

#### OpenML data

OpenML data additionally maintains it's own cache with is found at `~/.openml/`

#### Singularity container

Singularity additionally maintains it's own cache which can be removed with `singularity cache clean`

### Troubleshooting

  - **Singularity throws an 'Invalid Image format' exception**
  Use a singularity version > 3. For users of the Meta-Cluster in Freiburg, you have to set the following path:
  ```export PATH=/usr/local/kislurm/singularity-3.5/bin/:$PATH```

  - **A Benchmark fails with `SystemError: Could not start a instance of the benchmark. Retried 5 times` but the container
can be started locally with `singularity instance start <pathtocontainer> test`**
See whether in `~/.singularity/instances/sing/$HOSTNAME/*/` there is a file that does not end with '}'. If yes delete this file and retry.

## Status

Status for Master Branch:

[![Build Status](https://travis-ci.org/automl/HPOBench.svg?branch=master)](https://travis-ci.org/automl/HPOBench)
[![codecov](https://codecov.io/gh/automl/HPOBench/branch/master/graph/badge.svg)](https://codecov.io/gh/automl/HPOBench)

Status for Development Branch:

[![Build Status](https://travis-ci.org/automl/HPOBench.svg?branch=development)](https://travis-ci.org/automl/HPOBench)
[![codecov](https://codecov.io/gh/automl/HPOBench/branch/development/graph/badge.svg)](https://codecov.io/gh/automl/HPOBench)

repository: jtitusj/HPOBench

repo_name: jtitusj/HPOBench


text:
# Router

- Joins two or more networks
- Passes packets from one network to another
- Can do the following:
  - Connect dissimilar networks (LANs and WANs)
  - Interpret layer 3 ([[network layer]]) and layer 4 ([[transport layer]]) addressing
  - Determine the best path for data to follow from point A to point B
  - Reroute traffic if the path of first choice is down but another path is available
- May perform any of the following:
  - Filter broadcast transmissions
  - Prevent certain types of traffic from getting to a network
  - Support local/remote connectivity simultaneously
  - Provide high network fault tolerance through redundant components
    - Such as power supplies
  - Monitor network traffic and report stats
  - Diagnose internal connectivity problems and trigger alarms
- Act as a broadcast boundary
  - Don't forward broadcast traffic

## Routing Table

![Routers and routing tables](/assets/second-brain/2020-09-29-18-09-09.png)

- Database maintaining information about where hosts are located and the most efficient way to reach them
  - Routers rely on them to identify which router is the next hop to reach a particular destination host
- Contain [[IP address]]es and network masks that identify a network that a host or another router belongs to

## Routing Path Types

- Static routing
  - Network admins configure a routing table to direct messages along specific paths
- Dynamic routing
  - Automatically calculated paths between two networks
  - Maintains information in a routing table
  - Router can detect problems with failed/congested routes and reroutes messages through a different path

## Optimal Paths

- Routing protocols
  - Used by routers to communicate with each other to determine the best path
- Routers rate reliability and priority of a routing protocol's data based on:
  - Administrative distance (AD)
    - Number indicating protocol's reliability
  - Convergence time
    - Time it takes to recognize a best path in event of a change or outage
  - Overhead
    - Burden places on underlying network to support the protocol

[[Networking]] [[Computer Science]]

gha_language: TypeScript


text:
---
title: Historic building a haven for developing talent
feature_image:
  description: Former WHS student, Te Paerata Tichbon is back in town with Bad Hagrid.
  credit: Supplied
  image: https://res.cloudinary.com/whanganuihigh/image/upload/v1593640903/News/Te_Paerata_Tichbon._Midweek_1.7.20.jpg
news_author:
  date: 2020-06-30T22:00:42.996Z
  publication: Whanganui Midweek
  name: Ken Chernoff
show_in_slider: false
date: 2020-07-01T22:00:43.017Z
---
The Whanganui Musicians Club was created to promote and support local musicians, and it continues to provide a haven for developing talent. The club is now taking what was Whanganui's first public museum, built in the 1890s, into the 21st century.

For anyone who has yet to visit the historic building at 65 Drews Ave, the first Friday of the month is the best time to do it. The doors open at 7pm and you will be greeted by dedicated members of the club's committee. The evening is designed to allow locals of all ages to gather together and celebrate making music. The atmosphere is warm and informal, with tables arranged for members bringing their own food and drink. It is a place to meet old friends, and make new ones.

Since rescuing the remarkable building from the Savage Club, who itself had rescued it from demolition in the 1930s (when the museum relocated, making it redundant), the Musicians Club is looking to the future. The main performance hall boasts an iconic stage, with lighting and sound equipment that allow for performances of all types of music to resonate within the natural aesthetic that has been evolving for well over 100 years.

The club invites old members to come out this Friday night. Let's get together and do what we are meant to do – celebrate being part of a vibrant community enjoying each others' company and making music. To those who have yet to experience club night, come and check it out. You are sure to be made welcome.

And to Whanganui musicians and bands, young and old – there is a place on the stage for you. If you play, you earn the price of admission!

Enquiries to<EMAIL_ADDRESS>Friday, July 3, 65 Drews Ave. Music from 7.30pm.
Annual memberships at the door $30. Admission $10. Non members $15.

gha_language: Blade


text:
# Motivation

It was the year 1982 when
[Peter Henderson](https://www.ecs.soton.ac.uk/people/peter), publishes a paper
called _Functional Geometry_. In it he describes an algebra of pictures that
allowed him to recreate [Escher's](https://en.wikipedia.org/wiki/M._C._Escher)
_Square Limit_.

![Square Limit, Escher 1964](https://uploads3.wikiart.org/images/m-c-escher/square-limit.jpg!Large.jpg)

The 2002 reprint of [the article](https://eprints.soton.ac.uk/257577/1/funcgeo2.pdf)
inspired [Einar Host](https://einarwh.wordpress.com/) to give a
[talk](https://einarwh.wordpress.com/2017/07/22/picture-combinators-and-recursive-fish/)
and a [workshop](https://github.com/einarwh/escher-workshop).

I was lucky enough to attend that workshop at
[Booster Conf](https://2018.boosterconf.no/). I had such a good time that I
translated the workshop to Rust.

I hope that you enjoy it as much as I did, when I first learned how to recreate
Escher's Square Limit in code.


text:
# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog],
and this project adheres to [Semantic Versioning].

## [Unreleased]

- /

## [2.0.0] - 2023-08-04

- Change namespace to `Easy`
- Rename composer package to `iziphp/menv`
-

<!-- Links -->

[keep a changelog]: https://keepachangelog.com/en/1.0.0/
[semantic versioning]: https://semver.org/spec/v2.0.0.html

<!-- Versions -->

[unreleased]: https://github.com/iziphp/menv/compare/v2.0.0...HEAD
[2.0.0]: https://github.com/iziphp/menv/releases/tag/v2.0.0

repository: iziphp/menv

repo_name: iziphp/menv


text:
452\. Minimum Number of Arrows to Burst Balloons

Medium

There are some spherical balloons taped onto a flat wall that represents the XY-plane. The balloons are represented as a 2D integer array `points` where points[i] = [xstart, xend] denotes a balloon whose **horizontal diameter** stretches between xstart and xend. You do not know the exact y-coordinates of the balloons.

Arrows can be shot up **directly vertically** (in the positive y-direction) from different points along the x-axis. A balloon with xstart and xend is **burst** by an arrow shot at `x` if xstart <= x <= xend. There is **no limit** to the number of arrows that can be shot. A shot arrow keeps traveling up infinitely, bursting any balloons in its path.

Given the array `points`, return _the **minimum** number of arrows that must be shot to burst all balloons_.

**Example 1:**

**Input:** points = [[10,16],[2,8],[1,6],[7,12]]

**Output:** 2

**Explanation:** The balloons can be burst by 2 arrows:

- Shoot an arrow at x = 6, bursting the balloons [2,8] and [1,6].

- Shoot an arrow at x = 11, bursting the balloons [10,16] and [7,12].

**Example 2:**

**Input:** points = [[1,2],[3,4],[5,6],[7,8]]

**Output:** 4

**Explanation:** One arrow needs to be shot for each balloon for a total of 4 arrows.

**Example 3:**

**Input:** points = [[1,2],[2,3],[3,4],[4,5]]

**Output:** 2

**Explanation:** The balloons can be burst by 2 arrows:

- Shoot an arrow at x = 2, bursting the balloons [1,2] and [2,3].

- Shoot an arrow at x = 4, bursting the balloons [3,4] and [4,5].

**Constraints:**

*   1 <= points.length <= 105
*   `points[i].length == 2`
*   -231 <= xstart < xend <= 231 - 1

repository: javadev/LeetCode-in-Java

gha_language: Java

repo_name: javadev/LeetCode-in-Java


text:
---
layout: post
title: Using MySQL Workbench with a remote OpenIndiana/OpenSolaris host.
date: 2011-08-06
tags:
  - OpenIndiana
  - MySQL
---
# Using MySQL Workbench with a remote OpenIndiana/OpenSolaris host.

For anyone having issues connecting the MySQL Workbench via SSH Tunnel to an OpenIndian/OpenSolaris host with error messages like:

	"Error connecting SSH tunnel: Incompatible ssh server (no acceptable ciphers)".

This is actually and easy fix. Checking the /var/adm/messages file you will see something like:

	Aug 6 07:06:21 db01 sshd[7090]: [ID 800047 auth.crit] fatal: Client and server could not agree on a common cipher: client "aes128-cbc,blowfish-cbc,aes256-cbc,3des-cbc", server "aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour". The server cipher list can be controlled using the "Ciphers" option, see sshd_config(4) for more information.

Here is the easy fix.

**/etc/ssh/sshd_conf**

	Ciphers aes128-cbc,blowfish-cbc,aes256-cbc,3des-cbc

**svcadm restart ssh** and thats it!


text:
---
layout: post
title: Mongodb set dbpath and debugging
---

From the node project directory use the following command to launch mongodb with the path to the data directory:

mongod --dbpath /path/to/data

ie) mongod --dbpath ~/Desktop/nodeCIHL/data

If there is an error about the address being in use check that mongod is not already active with

sudo service mongodb stop
mongod --dbpath /path/to/data

Finally, if there is an error about not enough space to make the directories use:

mongod --dbpath /path/to/data --smallfiles


text:
# Examples for the Second Edition of the Scala Cookbook

Hi, this is Alvin Alexander, and this repository contains the
source code examples for the [Second Edition of the Scala
Cookbook](https://www.amazon.com/Scala-Cookbook-Object-Oriented-Functional-Programming-dp-1492051543/dp/1492051543), which was released in August, 2021.

All the best,
Al
https://alvinalexander.com


text:
---
layout: page
title: "The Aesthetic Bullseye"
permalink: /aesthetic-bullseye
published: true
last_updated: 2019-10-30
---

When I’m cooking a meal, writing a paragraph, or programming a piece of software, I usually have a personal standard of quality that guides my decisions. After watching [this vlogbrothers video](https://www.youtube.com/watch?v=1LAhHDEtTD0), I started referring to this standard as my ‘aesthetic target’. At its center is my ‘aesthetic bullseye’, which represents my concept of perfection.

![](/assets/img/aesthetic_bullseye/one_target.png)

It’s tempting to remain unsatisfied until I hit my aesthetic bullseye. However, if I’m making something for others to enjoy, I need to consider their tastes as well as my own. And while this might seem to make my job harder, it actually makes it much easier. The reason is that not everyone’s tastes are exactly the same. If I superimpose other people’s aesthetic targets onto my own, my aesthetic bullseye disappears.

![](/assets/img/aesthetic_bullseye/multiple_targets.png)

Even if I hit my own bullseye, I will miss the bullseyes of others. Realizing this has helped me to relax more when I’m struggling to achieve my own standard of perfection. Better to take more shots in the right general direction than to get caught in the perfectionist’s eternal refrain of “ready, aim, aim, aim, aaaaaaim…”

repository: ybalkind/ideas-and-notes

repo_name: ybalkind/ideas-and-notes


text:
# Kershaw BP5 and BPS5

## Performance Results (E/GPU=8000)

### NVIDIA V100
```
BPS5
solve time: 0.292781s
  preconditioner 0.219345s
    smoother 0.160926s
    coarse grid 0.0339261s
iterations: 28
throughput: 2.62421e+08 (DOF x iter)/s/rank
throughput: 9.37219e+06 DOF/s/rank
flops/rank: 5.66996e+11

BP5
throughput: 2.39e+09 (DOF x iter)/s/rank
flops/rank: 4.53206e+11
```

### NVIDIA A100
```
BPS5
solve time: 0.196772s
  preconditioner 0.147807s
    smoother 0.0987781s
    coarse grid 0.0321823s
iterations: 28
throughput: 3.90e+08 (DOF x iter)/s/rank
throughput: 1.39451e+07 DOF/s/rank
flops/rank: 8.43646e+11

BP5
throughput: 3.87e+09 (DOF x iter)/s/rank
flops/rank: 7.34419e+11
```

### AMD MI250X/1
```
BPS5
solve time: 0.279318s
  preconditioner 0.212514s
    smoother 0.156591s
    coarse grid 0.0339095s
iterations: 28
throughput: 2.7507e+08 (DOF x iter)/s/rank
throughput: 9.82393e+06 DOF/s/rank
flops/rank: 5.87756e+11

BP5
throughput: 3.07e+09 (DOF x iter)/s/rank
flops/rank: 5.83144e+11
```

### Summit 85 nodes
```
BPS5
solve time: 1.43221s
  preconditioner 1.23929s
    smoother 0.712053s
    coarse grid 0.396102s
iterations: 59
throughput: 1.13e+08 (DOF x iter)/s/rank
throughput: 1.92343e+06 DOF/s/rank
flops/rank: 2.43445e+11
tbd

BP5
throughput: 1.85983e+09 (DOF x iter)/s/rank
flops/rank: 3.5324e+11
```

### Perlmutter 128 nodes
```
BPS5
solve time: 0.965085s
  preconditioner 0.842747s
    smoother 0.447103s
    coarse grid 0.321199s
iterations: 59
throughput: 1.68e+08 (DOF x iter)/s/rank
throughput: 2.84328e+06 DOF/s/rank
flops/rank: 3.6387e+11

BP5
throughput: 3.37e+09 (DOF x iter)/s/rank
flops/rank: 6.3896+11
```

### Crusher 64 nodes
```
BPS5
solve time: 1.17859s
  preconditioner 1.00887s
    smoother 0.533104s
    coarse grid 0.398124s
iterations: 59
throughput: 1.37e+08 (DOF x iter)/s/rank
throughput: 2.32820e+06 DOF/s/rank
flops/rank: 2.9795e+11

BP5
throughput: 2.27e+09 (DOF x iter)/s/rank
flops/rank: 4.3017e+11
```

repository: thilinarmtb/nekRS

branch_name: refs/heads/next

repo_name: thilinarmtb/nekRS


text:
# Gmail Bridge

Script starts up a web-server connected to your gmail inbox via IMAP. As soon as you request `activation-link` resource e.g.
```
http://<IP_ADDRESS>:3500/api/v1/activation-link/joe@gmail.com?secret=secret
```
the server looks for unseen recent messages and performs `parseActivationLink` function on the body of each.
If the activation link successfully extracted the server returns it as `{ value: "link" }`

## Installation

- If you exported the project into this directory for the first time, please run `npm install` to install dependencies.
- Setup env variables:
```bash
<EMAIL_ADDRESS>EID_PASSWORD=gmail password
EID_SECRET=secret
EID_NODE_SERVER_PORT=3500
EID_NODE_SERVER_HOST=<IP_ADDRESS>

```
- start the server `npm start`

## NOTE
To make it really work with Gmail, please, [enable 2-step verification](https://www.google.com/landing/2step/) and
generate an [App password](https://security.google.com/settings/security/apppasswords). This password you shall use
for `EID_PASSWORD`

repository: dsheiko/puppetry

repo_name: dsheiko/puppetry


text:
Since I couldn't sleep until I fixed, I figured I'd blog it. (It's finishing up fixing itself now.)

Symptom:

Running Leopard, all normal updates. On 12/25/2007 I get a popup window with some macbook upgrades, a quicktime patch, and another innocuous looking update. However, after authorizing it to reboot the computer, I get the message "Reboot failed because application 'Software Update' failed to quit." This, I think, is a bad sign. I quit every other application and tried running software update again. Same thing happens.  It won't. Power button's not even working to bring up the "shutdown" menu. Only thing I can do is hold down the power button and power it back up.

Here's the thing -- on next boot, I'm looking at the OS X Setup Assistant. Yeah. As if I'd just installed Leopard. Great.

Fix:

Thankfully, the fix was easy, after I got my heart rate back down from 210 BPM. I searched in the KB a bit and found: [Setup Assistant Appears after Every Restart](http://docs.info.apple.com/article.html?artnum=306998)

And that worked. Start it in safe mode, (hold shift right after power-on 'Bong!') when it gets to the login screen don't login, but hit back arrow, then restart, and viola -- upgrades continued like they should have, and on next reboot I was normal.

All's well that ends well, but this DID make me want to get my backups back in shape one way or another; no more waiting around for SuperDuper to get Leopard-ready. (Even though his latest update suggests I could be good to go within a week... it's rsync time, at least.)

Edit: Turns out the rsync was is easy. [Just listen to jwz.](http://jwz.livejournal.com/801607.html)

extension: markdown


text:
# Revision history for `cryptol-remote-api` and `cryptol-eval-server`

## 2.11.1 -- 2021-06-23

* HTTPS/TLS support added. Enable by running server in `http` mode with `--tls`
  flag or by setting an environment variable (command line `--help` contains details).

## 2.11.0

* First "released" version of `cryptol-remote-api`.

repository: mbenelli/cryptol

repo_name: mbenelli/cryptol


text:
# json-syntax-error
![David](https://img.shields.io/david/dev-inately/json-syntax-error) ![npm bundle size](https://img.shields.io/bundlephobia/min/json-syntax-error) ![NPM](https://img.shields.io/npm/l/json-syntax-error)
>  Middleware to help you to catch syntax errors in JSON sent to your express server and give you a much cleaner error

Ever tried sending an invalid JSON syntax to your express server when you use it with body-parser
or `express.json()` and you get an ugly error at your client side?

Tired of seeing your server throwing Syntax error when an invalid JSON data is forced
down it's throat?

```html

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>SyntaxError: Unexpected string in JSON at position 53<br> at JSON.parse (<anonymous>)<br>
   at parse (/home/pc/Desktop/TC/tc-sample/node_modules/body-parser/lib/types/json.js:89:19)<br>
   at /home/pc/Desktop/TC/tc-sample/node_modules/body-parser/lib/read.js:121:18<br>
   at invokeCallback (/home/pc/Desktop/TC/tc-sample/node_modules/raw-body/index.js:224:16)<br>
   at done (/home/pc/Desktop/TC/tc-sample/node_modules/raw-body/index.js:213:7)<br>
   at IncomingMessage.onEnd (/home/pc/Desktop/TC/tc-sample/node_modules/raw-body/index.js:273:7)<br>
   at IncomingMessage.emit (events.js:327:22)<br>
   at endReadableNT (_stream_readable.js:1220:12)<br>
   at processTicksAndRejections (internal/process/task_queues.js:84:21)</pre>
</body>
</html>
```

 This small middleware will help you to resolve syntax errors in your express server by
 allowing you to catch the error early and returning a cleaner error

 ```json
 {
    "status": "fail",
    "message": "Invalid JSON: The server is unable to process your request as it is badly malformed!
 }

 ```

## Installing / Getting started

Install via npm

```shell
npm install json-syntax-error --save
```

Configuration is easy, as a, b, c. Just `require('json-syntax-error')` anywhere below your json parser (`express.json()` or `bodyParser.json()`)

```js

const JSONSyntaxErr =  require('json-syntax-error')
...
const app = express();
...
app.use(express.json());
app.use(JSONSyntaxErr()); // That's all, really!

...
```

You can also pass in your custom response. It can be JSON, HTML, text or any format allowed by express `.send()`

```js
app.use(JSONSyntaxErr({ error: 'Why are you sending a bad json?' })); // Torture their conscience!

```
or

```js
app.use(JSONSyntaxErr('<p>Really? A bad JSON? Really?</p>')); // Wasn't hard, was it?!

```

## Tests

```shell
npm test
```

repository: dev-inately/json-syntax-error

repo_name: dev-inately/json-syntax-error


text:
---
layout: post
title: "SSL and Web Security"
modified:
categories: blog
excerpt:
tags: ['security']
image:
  feature:
date: 2014-07-14T15:39:55-04:00
---

It is worth noting that SSL is only one piece of your web security. It offers a great way to protect your data as it flows between the client and the server as well as providing a check to ensure the server is who you think it is but it is only a piece of the security puzzle. Often people will think just by having SSL enabled their site is now secure but this is just not the case.
<!--more-->
You still have to worry about

* Url tampering
* Sql injection
* Social Engineering
* Incorrectly implemented authentication

to name just a few.

The Open Web Application Security project lists out the [top 10 security flaws](https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Main) on most websites are for the year.

Here is a good video on [how SSL works](https://www.youtube.com/watch?v=iQsKdtjwtYI).

repository: johndehavilland/myblog

repo_name: johndehavilland/myblog