text:
## Discard all local commits on branch, update to upstream of branch
`git reset --hard @{u}`

## Determine What Has Been Merged

`git checkout master`

`git branch --merged`

## Prune Remote Branches

`git remote prune origin`

Deletes all stale remote-tracking branches under <name>. These stale branches have already been removed from the remote repository referenced by <name>, but are still locally available in "remotes/<name>".

## Branches w/ Deleted Upstream/Remote Counterparts
https://railsware.com/blog/2014/08/11/git-housekeeping-tutorial-clean-up-outdated-branches-in-local-and-remote-repositories/

`git branch -vv | grep 'origin/.*: gone]' | awk '{print $1}'`

## One-liner to Delete Branches w/ Deleted Upstream/Remote Counterparts

`git branch -vv | grep 'origin/.*: gone]' | awk '{print $1}' | xargs git branch -d`

### Powershell + Posh Git

`git branch -vv | grep 'origin/.*: gone]' | awk '{print $1}' | %{git branch -d $_}`

The command above replaces `xargs` with PowerShell syntax for a Foreach loop. I run posh-git behind PowerShell and was having some issues getting `xargs` to work right. First had to using `-I` flag and wrap the input in quotes to get proper line replacement: `xargs -I% git branch -d '%'`. But then it was still not executing right.

## Select parts of diff to stage for a commit

`git add -p <file>`

https://git-scm.com/docs/git-add#git-add--p

## Selectively stash changes

stash file1.js and file2.js

`git stash push -m "Description" ./file1.js ./file2.js`

select parts of diff to stage from all files

`git stash push -p -m "Description"`

select parts of diff to stage from file1.js and file2.js

`git stash push -p -m "Description" ./file1.js ./file2.js`

(q can quit at any point keeping all changes already chosen for stash)

## Update branch w/o switching to it

`git fetch origin <branch>:<branch>`

For example:

`git fetch origin dev:dev`

## Check out branch from another fork/repo

(Stolen from GitHub manual merge of PR instructions)

```
git checkout -b <new branch name> main
git pull git@github.com:<external repo>.git <existing branch>
```

repository: michaelgoin/knowledge-share

repo_name: michaelgoin/knowledge-share


text:
# Agents

Agents are specialized services that run a single process on each cluster instance.

## Configuration

You can define any given Service as an Agent by setting its `agent` attribute to `true`

    services:
      telemetry:
        agent: true

### Communicating with an Agent

Often it is useful for other Services to communicate with an agent running on its instance.

You can declare ports that will be available to communicate with an agent using the `ports` attribute:

    services:
      telemetry:
        agent: true
        ports:
          - 8125/udp
          - 8126

> Agents will listen on the IP address of the underlying instance. This means that you can not deploy
> two agents on the same Rack that listen on the same port.

Each Service will have the IP of its instance available in the `INSTANCE_IP` environment variable.

In the example above, other Services can communicate with the `telemetry` agent running on its instance
using the following endpoints:

* `udp://$INSTANCE_IP:8125`
* `tcp://$INSTANCE_IP:8126`

repository: AstmDesign/convox

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: AstmDesign/convox


text:
# Fake News Classifier [![Open in Streamlit](https://static.streamlit.io/badges/streamlit_badge_black_white.svg)](https://share.streamlit.io/mlsquad/fake_news/main.py)
An application for detecting fake news using a LSTM model

##  ⚡ Demo
![Demo](Demo/FinalFake.gif)

Live Demo available `https://share.streamlit.io/mlsquad/fake_news/main.py`

## Platform
The LSTM model was generated using [Tensorflow](https://www.tensorflow.org/)
Frontend was developed and hosted on [Streamlit](https://www.streamlit.io/)

## 👨🏻💻 Local Development
Clone the repo:
```
git clone https://github.com/MLSquad/fake_news.git
```
cd to `fake_news` directory
Install Python packages:
```
pip install -r requirements.txt
```

Run application:
```
streamlit run main.py
```

## 💻 Contributors

- [Angelina Gasharova](https://github.com/angelinag)
- [Nkosilathi Tauro](https://github.com/nkosi-tauro)
- [Egor Tarasov](https://github.com/Jorres)

## 🔑 LICENSE

- MIT

license: MIT

gha_language: Python

gha_license_id: MIT


text:
Thawani For WooCommerce

    Enables Credit/Debit card payments through Thawani on your WooCommerce shop.

    Report a bug

  Download latest release

>

>
> **⚠ INFORMATION & REQUIREMENTS**
>
> - Thawani For WooCommerce is currently only available in Oman.
> - Only OMR is currently supported.
>

The Thawani Plugin for WooCommerce allows merchants to accept Credit & Debit card transactions.

This plugin will only work with WooCommerce and is built to extend it.

## Motivation

The need for this project came from the shortage in the Omani market when it comes to payment gateways that allows online transactions to be in OMR. Most payment gateways do not support this and require some kind of currency conversion as part of the transaction process.

[Thawani Pay](https://thawani.om/about/) is a Payment Gateway that solves this problem. The [Thawani Checkout](https://thawani.om/checkout/) API, allows for transactions to be made using OMR.

This project makes Thawani's API accessible to the public. Making it easy for anyone to setup Credit & Debit Payment on their online store.

## Contribution

The Thawani for Woocommerce plugin is a community project launched by [PhazeRo](https://phaze.ro/) where we would like to give everyone the opportunity to take part in its development. If you wish to contribute and be part of this project look at the [Contribution](./CONTRIBUTING.md) file.

## Features

- Credit & Debit card payment.
- Payments are in OMR no conversion currency needed.
- Easy to switch from sandbox and live environment.
- Checks for payment confirmation.
- Track Session History
- Logging to make debugging easy.
- Sharable payment link

## Requirements

- WooCommerce 5.6+

For live account, please create a [merchant account](https://thawani.om/merchants/) with Thawani then follow the instructions on their [documentation](https://developer.thawani.om/).

## Installation

1. **Download** the .zip file from this repository.

![download zip file](./static/download_zip.PNG)

2. **Go to: WordPress Admin > Plugins > Add New** to upload the .zip file you downloaded with Choose File.

![install the plugin](./static/thawani_install.gif)

3. **Activate** the extension. (If you haven't already in the previous step)

![activate the plugin](./static/activate_plugin_blur.PNG)

More information at: [Managing Plugins](https://wordpress.org/support/article/managing-plugins/).

For the plugin to work properly, please make sure that your permalink settings are set to _post name_. To do that **Go to: Settings > Permalinks > Common Settings** and make sure that _post name_ is selected.

![permalink settings](./static/permalink.png)

## Thawani For WooCommerce Set up

1. **Go to: WooCommerce > Settings > Payments**.

![payment settings](./static/woocommerce_setting.PNG)

2. Select **Thawani Gateway**. You are taken to the configuration screen.

![Thawani Payment Gateway](./static/thawani_payment_gateway_setting.PNG)

3. **Enable/Disable** – Enabled by default. Disable to turn off Thawani Pay.

![enable/disable plugin](./static/enable_disable.gif)

## Configuration

1. Select the Environment:

- Development Environment

In development environment you will be able to make mock payments to simulate the payment processing flow of a live account.

When you are in development mode you will need to use the User Acceptable Test ("UAT") secret and publishable keys and **not** your own secret and publishable keys. These two keys can be found on the [Thawani documentation](https://developer.thawani.om/).

- Production Environment

Production environment is to be used when the website is live

To setup a live account you need the following:

- An SSL certificate.
- A Thawani merchant account. You can apply by visiting [Thawani's website](https://thawani.om/merchants/).
- Access to the Thawani merchant dashboard. This is where you can get your live secret and publishable keys. Learn more by reading [Thawani's documentation](https://developer.thawani.om/).
- Add the following URL: `https//<YOUR-SITE-URL>/wc-api/thawani-payment-status` to the webhook URL section on the Thawani dashboard. Learn more by reading [Thawani's documentation](https://developer.thawani.om/).
- Set the secret and publishable keys in the payment settings page to the secret and publishable keys provided by Thawani

![live keys](./static/keys.png)

2. Enable logging

Thawani For WooCommerce comes with a troubleshooting tool. This is in the form of logs. The logs are added each time a user orders an item, even if the payment fails.

To enable logging make sure that the _Enable Logging_ checkbox is checked.

![enable logging](./static/logging_enable.png)

To view the logs **Go to: WooCommerce > Status > Logs**

![thawani logs](./static/logs.png)

The logs messages for this plugin follow the following format `thawani-<DATE-OF-ORDER-PLACEMENT>`.

## View Session History

The Thawani Gateway plugin keeps a record of all the sessions created to process payments and displays them for the admin.

The plugin keeps a record of:

- Timestamp of when the session was created
- Client refrence / Order ID
- Customer Information
- Payment Status
- Total Amount

To access the session history:
**Go to: WordPress Admin > Thawani Gateway**

![session history](./static/session_history.png)

## Customer Checkout Flow

![customer workflow](./static/customer_workflow.gif)

Nothing will be change from WooCommerce's default customer checkout flow. Customers will see an option on their checkout page to select payment via Thawani as shown in the image below:

![checkout with thawani](./static/checkout_page.png)

## Admin Order Fulfillment Flow

To view all orders **Go to: WooCommerce > Orders**

![go to order page](./static/order_page.png)

Note that this plugin automatically updates the order status as follows:

- **Processing:** Payment received (paid); order is awaiting fulfillment from merchant.
- **On hold:** Awaiting payment
- **Failed:** Payment failed or was declined (unpaid)
- **Canceled:** Canceled by an admin or the customer

For more information about WooCommerce Orders, Go to: [Managing Orders](https://docs.woocommerce.com/document/managing-orders/).

## Frequently Asked Questions

We welcome input from the community please let us know how we can improve this plugin. Do not hesitate to ask us questions on the [issues](https://github.com/PhazeRoOman/thawani_gw/issues) page.

## License

Distributed under the MIT License. See [License] (https://github.com/PhazeRoOman/thawani-for-woocommerce/blob/changes/LICENSE.md) for more information.

## Maintained By:

- [PhazeRo](https://phaze.ro/)


text:
# SCons
Hacking with SCons

## What's SCons?

> SCons is an Open Source software construction tool—that is, a next-generation build tool. Think of SCons as an improved, cross-platform substitute for the classic Make utility with integrated functionality similar to autoconf/automake and compiler caches such as ccache. In short, SCons is an easier, more reliable and faster way to build software.

## Setting up SCons

### Building from source - Ubuntu.

At the time of this writing the latest version of SCons is 3.0.1

Ensure Python is installed locally

```bash
sudo mkdir /opt/src
cd /opt/src/
sudo wget http://prdownloads.sourceforge.net/scons/scons-3.0.1.tar.gz
sudo tar -xvzf scons-3.0.1.tar.gz
cd scons-3.0.1/
sudo python setup.py install
```

Other installation options can be found from [this link](http://scons.org/doc/HTML/scons-user.html#chap-build-install)

```bash
scons -v
# SCons by Steven Knight et al.:
#        script: v<IP_ADDRESS>b2c53bc42290e911b334a6b44f187da698a668, 2017/11/14 13:16:53, by bdbaddog on hpmicrodog
#       engine: v<IP_ADDRESS>b2c53bc42290e911b334a6b44f187da698a668, 2017/11/14 13:16:53, by bdbaddog on hpmicrodog
#        engine path: ['/usr/local/lib/scons-3.0.1/SCons']
# Copyright (c) 2001 - 2017 The SCons Foundation
```

### Up and Running

```bash
cd /myproject && sudo mkdir helloscons && cd helloscons
echo '#include <stdio.h> int main(){ printf("Hello SCons\n");}' > app.c
echo "Program('app.c')" > SConstruct
scons
# scons: Reading SConscript files ...
# scons: done reading SConscript files.
# scons: Building targets ...
# gcc -o app.o -c app.c
# gcc -o app app.o
# scons: done building targets.
./app
# Hello SCons

```

### Deep dives

Learn more from the user guide from [this link](http://scons.org/doc/HTML/scons-user.html)

repository: Kalpavrikshika/scons

repo_name: Kalpavrikshika/scons


text:
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [4.0.0] - 2021-01-17
### Changed
 - Updated support libraries to android X
 - Translated to Kotlin
 - `StickyHeaderDecoration` now tracks the actual header position
 - Added the ability to get the child index to header adapters with `getChildIndex(adapterPosition)`

## [3.0.1] - 2018-05-10
### Fixed
 - Fixed `HeaderListAdapter` incorrect item size

## [3.0.0] - 2018-05-10
### Changed
 - Updated the `minSdk` to `14` (was `9`)
 - Updated support library to `27.1.1`
 - Sticky Headers are now clickable
 - Sticky Header transitions are now smooth
 - Sticky Headers now use ViewHolders

### Fixed
 - `FastScroll` animations are now consistent

### Removed
 - `CursorAdapter`s have been removed

## [2.1.1] - 2017-04-01
### Changed
 - Updated support library to `25.3.1`

### Fixed
 - `FastScroll` now correctly stays hidden on load

## [2.1.0] - 2017-01-25
### Added
 - Reorder support added to the `CursorAdapter`
 - `ItemStatefulTouchHelper`

### Changed
 - Updated dependencies

### Deprecated
 - `CursorAdapter` deprecated due to inherent issues with long-lived cursors

## [2.0.1] - 2016-10-31
### Fixed
 - `FastScroll` track clicking now works as expected

## [2.0.0] - 2016-10-24
## Added
 - `FastScroll` can now be hidden on short lists

### Changed
 - Updated the `minSdk` version to `9` (was `7`)
 - Updated support library to `24.2.1`
 - Added a callback with `sectionId` to the `FastScroll` for improved popup change determination
 - `FastScroll` now uses the finger position for the scroll instead of the center
 - Optimized header calculations
 - `FastScrollPopupCallbacks` renamed to `PopupCallbacks`

### Fixed
 - Fixed inconsistent positioning in the `FastScroll` between dragging and normal scrolling

## [1.3.1] - 2016-08-17
### Changed
 - `FastScroll` smoothed out, particularly with short lists

### Fixed
 - Vector drawables now work correctly on pre-Lollipop devices
 - `FastScroll` drag handle now stays visible during a drag

## [1.3.0] - 2016-08-11
### Changed
 - Added drag handle animations to `FastScroll`
 - Added popup alignment options to `FastScroll`
 - Track clicks can now be disabled in `FastScroll`

### Fixed
 - Smooth scrolling now works as expected

## [1.2.0] - 2016-08-02
### Updated
 - Adapter position can now be determined from a child position

### Changed
 - Updated support library to `24.1.1`

### Deprecated
 - `determineChildPosition()` deprecated in favor or `getChildPosition()`

## [1.1.2] - 2016-06-24
### Changed
 - Updated support library to `24.0.0`

## [1.1.1] - 2016-04-20
### Fixed
 - `StickyHeaderDecoration` now works correctly with the `RecyclerHeaderListAdapter`

## [1.1.0] - 2016-04-13
### Added
 - `RecyclerHeaderListAdapter`

### Updated
 - Added `set()` to `RecyclerListAdapter`

### Changed
 - Support library updated to `23.3.0`

## [1.0.2] - 2016-03-23
### Fixed
 - `FastScroll` now properly shows text bubble when dynamically enabling/disabling

## [1.0.1] - 2016-03-22
### Fixed
 - `AutoColumnGridLayoutManager` sizing and spacing

## [1.0.0] - 2016-03-13
### Changed
 - Updated support library versions

## [0.18.0] - 2016-03-10
### Fixed
 - `AutoColumnGridLayoutManager` spacing issues caused by support `23.2.0`

## [0.18.0] - 2016-03-02
### Fixed
 - `AutoColumnGridLayoutManager` sizing issues caused by support `23.2.0`

### Removed
 - `WrapLinearLayoutManager` due to the support library `23.2.0` adding native support

## [0.17.1] - 2016-01-29
### Fixed
 - `FastScroll` resource issue

## [0.17.0] - 2016-01-27
### Added
 - `FastScroll` widget

## [0.16.0] - 2016-01-19
### Added
 - Item touch helper callback to support elevation changes

## [0.15.0] - 2016-01-07
### Added
 - `SpacerDecoration`

### Changed
 - `AutoColumGridLayoutManager` now supports specifying the max column count, edge separators, and separator sizes

## [0.14.0] - 2015-12-12
### Added
 - Sticky headers can now be made from individual views instead of the entire holder
 - Items can now be treated as a header (see Lollipop & Marshmallow contacts)

### Changed
 - Removed code duplication in the header adapters

## [0.13.0] - 2015-12-11
### Added
 - `ViewTypes` are now available in the header adapters

## [0.12.4] - 2015-12-10
### Fixed
 - `WrapLinearLayoutManager` now abides by `RecyclerView` padding
 - `WrapLinearLayoutManager` now properly wraps in vertical and horizontal lists

## [0.12.3] - 2015-10-22
### Added
 - Created view holders to support clicks and menus

### Fixed
 - methods are now properly available

## [0.12.1] - 2015-10-21
### Changed
 - Added ability to specify a min amount of spacing between cards in the `GridLayoutManager`
 - Added child count to the `HeaderAdapter`s

## [0.12.0] - 2015-10-19
### Changed
 - Added `swap` and `move` methods to the `RecyclerListAdapter`
 - Updated support library versions

### Fixed
 - General issues with `StickyHeaderDecoration`

## [0.11.1] - 2015-10-15
### Changed
 - `ListAdapter` now notifies of data range changes to support animations

### Fixed
 - `GridLayoutManager` now correctly abides by padding

## [0.11.0] - 2015-10-12
### Added
 - `GridLayoutManager` that auto-determines column count based on item size

### Changed
 - Rewrote `StickyHeaderDecoration` to properly handle data changes

## [0.10.4] - 2015-09-17
### Changed
 - `RecyclerHeaderCursorAdapter` and `RecyclerHeaderAdapter` updated to standardized methods and parameters

## [0.10.0] - 2015-08-11
### Added
 - `ListAdapter`

### Changed
 - Minor updates to the `CursorAdapter`

## [0.8.0] - 2015-07-02
### Changed
 - `ReorderDecoration` now has smooth reorder animations

## [0.7.0] - 2015-04-12
### Added
 - `CursorAdapter`
 - `ReorderDecoration`

repository: brianwernick/RecyclerExt

gha_language: Kotlin

repo_name: brianwernick/RecyclerExt


text:
# sphinx-problem-matcher

This action adds a problem matcher that catches Sphinx warnings to show them
neatly inside your pull request like this:

![Example Screenshot](https://i.imgur.com/xkUMS1a.png)

The common usage of this will be like so:

```yaml
    - uses: ammaraskar/sphinx-problem-matcher@master
    - name: "Build docs"
      run: |
        cd docs
        make html
```

That is, simply run this action before building your docs.

**Note: this does not handle actually building your docs.**

repository: emacsway/sphinx-problem-matcher

repo_name: emacsway/sphinx-problem-matcher


text:
This is a list of domains associated with top websites. It was compiled with comprehensiveness in mind and thus errs on the side of blocking too much instead of too little.

## Credits

This list was compiled from personal query tracing and from multiple sources. Credit is given to:

https://github.com/jmdugan/blocklists/tree/master/corporations

https://github.com/speeddemon574/YouTube-Blacklist/blob/master/domainList.txt

https://github.com/JamieFarrelly/Popular-Site-Subdomains

### Tools used to source these lists:

Using https://crt.sh to run a wildcard "%.domain.com" search for certificates which yielded some subdomains

Running a VirusTotal search like https://www.virustotal.com/#/domain/youtube.com which yields observed subdomains

https://www.bugcrowd.com/discovering-subdomains/

### Some helpful tools used to produce these lists:

http://tools.dynamicdrive.com/listscrubber/

https://delim.co/

http://www.convertcsv.com/csv-to-csv.htm

http://www.objgen.com/json

repository: chandulaushan/domainlists

repo_name: chandulaushan/domainlists


text:
# ![logo](https://github.com/AbFarid/daegmael/blob/master/public/img/icons/icon.png?raw=true) Daegmael
> **Dæg-Mæl** - Anglo-Saxon for "day measure".

## Introduction

Unofficial companion app for game __Kingdom: Two Crowns__.
https://abfarid.github.io/daegmael/

#### Features:
* __convert Roman numerals__ (into Arabic numerals, with which you don't have to do a bunch of math)
* __show current season__
* __show amount of days left till winter comes__ (and crushes you)
* __shows time till sunset/sunrise__ (slightly more precisely than Sun and Moon)
* __always-on display that keeps your info at a glance__ (even has burn-in protection for OLED screens)
* __offline installation for compatible devices__ (as a PWA app, it can be installed into your app drawer)

# Usage

### Season tracker
Enter your current in-game campaign day (shown in the pause menu) using the in app buttons (or keyboard; only valid Roman numerals):
* ___-i___ / ___+i___ jumps a day backwards/forwards
* ___-xvi___ / ___+xvi___ jumps a season backwards/forwards

You can now see your season related information:
* Current day in Arabic numerals
* Current season
* Days left till winter starts/ends

### Day tracker
If you'd like to use automatic day progression and/or see daytime countdown to know precise time, use the countdown timer.

Timer buttons:
* __START__ - Starts or resumes the countdown
* __PAUSE__ - Pauses the countdown
* __STOP__ - Stops and resets the countdown
* __RESET__ - Resets and starts countdown immediately (useful for readjusting timer)

Optionally, if you're on a mobile device (Android/iOS) you'll see a button with an LED (![LED](https://github.com/AbFarid/daegmael/blob/master/src/assets/img/led_mini_dark.png?raw=true)) icon, that will enable the _always-on display_ (AOD). This will remove the unnecessary UI element and keep your screen awake untill you press the button again. There's a basic OLED screen burn-in protection enabled, where the content will move around once a minute.

## Installation as native(ish) app for offline use
The web app can be installed onto your compatible device (Windows/Android/iOS) as a Progressive Web App (PWA). Doing so enables offline usage of the app.

repository: AbFarid/daegmael

gha_language: Vue

repo_name: AbFarid/daegmael


text:
---
page_type: sample
languages:
- csharp
products:
- azure
extensions:
  services: virtual-network,network-watcher
  platforms: dotnet
---

# Use network watcher to check connectivity between virtual machines in peered networks #

 Azure Network sample for enabling and updating network peering between two virtual networks
 Summary ...
 - This sample uses Azure Network Watcher's connectivity check to verify connectivity between
   two peered virtual networks.
 Details ...
 1. Define two virtual networks network "A" and network "B" with one subnet each
 2. Create two virtual machines, each within a separate network
   - The virtual machines currently must use a special extension to support Network Watcher
 3. Peer the networks...
   - the peering will initially have default settings:
   - each network's IP address spaces will be accessible from the other network
   - no traffic forwarding will be enabled between the networks
   - no gateway transit between one network and the other will be enabled
 4. Use Network Watcher to check connectivity between the virtual machines in different peering scenarios:
   - both virtual machines accessible to each other (bi-directional)
   - virtual machine A accessible to virtual machine B, but not the other way

## Running this Sample ##

To run this sample:

Set the environment variable `AZURE_AUTH_LOCATION` with the full path for an auth file. See [how to create an auth file](https://github.com/Azure/azure-libraries-for-net/blob/master/AUTH.md).

    git clone https://github.com/Azure-Samples/network-dotnet-use-network-watcher-to-check-connectivity.git

    cd network-dotnet-use-network-watcher-to-check-connectivity

    dotnet build

    bin\Debug\net452\VerifyNetworkPeeringWithNetworkWatcher.exe

## More information ##

[Azure Management Libraries for C#](https://github.com/Azure/azure-sdk-for-net/tree/Fluent)
[Azure .Net Developer Center](https://azure.microsoft.com/en-us/develop/net/)
If you don't have a Microsoft Azure subscription you can get a FREE trial account [here](http://go.microsoft.com/fwlink/?LinkId=330212)

---

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode<EMAIL_ADDRESS>with any additional questions or comments.


text:
# Portland Synth

> Control Sonic Pi using Python and some potentiometers connected to a Raspberry Pi

These are a collection of Sonic Pi loops and Python scripts that work together to generate music either with Python alone or Sonic Pi on a headless Raspberry Pi. You'll need a set of 10k potentiometers (8 is great, 4 is enough), a MCP3008 ADC chip, a mini solderless breadboard, some jumper wires, and any Raspberry Pi with populated GPIO pins (I'm using a Pi Zero W but Sonic Pi is not officially supported on it so beware).

The idea is that you can generate music one of two ways:

1. Play Sonic Pi music through Python scripts and manipulate the sound in real time with the values read from some potentiometers.
2. Run a Python script that generates a waveform and play it through `aplay`

## Contents

- [Wiring it up](#wiring-it-up)
- [Installation](#installation)
- [Usage](#usage)
	- [Starting sonic Pi Headless](#To-start-Sonic-Pi-on-a-headless-Raspberry-Pi)

## Wiring it up

I had limited materials to work with. You can wire it up however you like but this is how it is currently working with 8 potentiometers and 2 rotary encoders.

![Breadboard Image](https://github.com/billpatrianakos/portlandsynth/raw/master/docs/portland_synth_bb.png)

TODO: In depth explanation of wiring and which GPIO controls what part.

## Installation

1. Install Sonic Pi however you want. Use the package manager or build from source. Doesn't matter. *If you are running a headless Pi* then be sure to install `xvfb` otherwise Sonic Pi won't start.
2. Copy this entire project to your Pi
3. Install the dependencies with `pip install -r requirements.txt` (Only Python 3 is supported. Python 2.7 may or may not work with these scripts)

## Usage

### To start Sonic Pi on a headless Raspberry Pi

Run the script in the system folder: `./sonic-pi-headless.sh`

### To play some music

Just run any of the Python music files like `python3 pysounds/sine.py` or `python3 sonic_python/track2.py`

*Remember:* If you don't have at least 4 potentiometers connected to your Pi then there will be no signals to read and the scripts will probably crash.

TODO:

- how to run sonic pi headless
- what to do if you run on a pi zero with no audio out
- python OSC to sonic pi explanation
- pure python instructions

## Why is it called "Portland Synth"?

Because I've been naming my Raspberry Pi's after places and landmarks in the Pacific Northwest recently and I built this project on my Pi Zero W with the hostname `portland`.

repository: billpatrianakos/portlandsynth

repo_name: billpatrianakos/portlandsynth


text:
# initDockerImage
used for digitalocean vps.

I write this script is not obey the docker's princeple which one container one funciton, but I just want when I run a new image of digitalocan, I can quickly have these functions works:

+ apache
+ shadowsocks
+ aria2
+ aria2-webui

so...

## install & build

    git clone https://github.com/walkerwzy/initDockerImage.git mydocker
    cd mydocker/
    sudo docker build -t walker/do .
    bash run.sh

repository: walkerwzy/initDockerImage

repo_name: walkerwzy/initDockerImage


text:
The contents of this directory have been moved to https://storage.googleapis.com/gresearch/value_dice/datasets/

To copy:

```
gsutil cp -r gs://gresearch/value_dice/datasets/ .
```


text:
# DevRadar

DevRadar is a complete app to register and search Devs near you.

This is the backend installation.

## Installation

##### Use the package manager of your preference. I've used yarn, so the examples will be with yarn.

### Database Setup

To use this backend, you will need a MongoDB account. I've created one on MongoDB Atlas.

### Dependencies

To install the dependencies just open the backend folder within a command line and type:

```bash
yarn install
```

## Usage

Again on your command line type:

```bash
yarn start
```

After that, your server will be running on http://localhost:3333/

## License

[MIT](https://choosealicense.com/licenses/mit/)

repository: Wolffsmith/DevRadar

repo_name: Wolffsmith/DevRadar


text:
# pinger

Quickly see what's on your network by pinging all the machines

## Getting started

- ./pinger -i IPAddr -m AddMask (-offline)
- Not providing any params will provide online assets with current ip address and defaulting to a /24 address mask


text:
hazelcast-kubernetes
====================

Hazelcast clustering for Kubernetes made easy.

Lean (188MB) Hazelcast with  Kubernetes discovery support container image, based on `alpine`.

## Software

* JRE 8u60
* Hazelcast 3.5.2

## Pre-requisites

* Docker 1.7.1+
* Kubernetes 1.0 or newer cluster

## Kubernetes cluster

You can test with a local cluster. Check [this other repository from yours truly](https://github.com/pires/kubernetes-vagrant-coreos-cluster).

## Docker image

The image is already available at [quay.io/pires](https://quay.io/repository/pires/hazelcast-kubernetes)

## Cloud Native Deployments of Hazelcast using Kubernetes

The following document describes the development of a _cloud native_ [Hazelcast](http://hazelcast.org/) deployment on Kubernetes.  When we say _cloud native_ we mean an application which understands that it is running within a cluster manager, and uses this cluster management infrastructure to help implement the application. In particular, in this instance, a custom Hazelcast ```bootstrapper``` is used to enable Hazelcast to dynamically discover Hazelcast nodes that have already joined the cluster.

Any topology changes are communicated and handled by Hazelcast nodes themselves.

This document also attempts to describe the core components of Kubernetes, _Pods_, _Services_ and _Replication Controllers_.

### Prerequisites
This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the `kubectl` command line tool somewhere in your path.  Please see the [getting started](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides) for installation instructions for your platform.

### A note for the impatient
This is a somewhat long tutorial.  If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end.

### Sources

Source is freely available at:
* Hazelcast Discovery - https://github.com/pires/hazelcast-kubernetes-bootstrapper
* Dockerfile - https://github.com/pires/hazelcast-kubernetes
* Docker Trusted Build - https://registry.hub.docker.com/u/pires/hazelcast-k8s

### Simple Single Pod Hazelcast Node
In Kubernetes, the atomic unit of an application is a [_Pod_](http://docs.k8s.io/pods.md).  A Pod is one or more containers that _must_ be scheduled onto the same host.  All containers in a pod share a network namespace, and may optionally share mounted volumes.

In this case, we shall not run a single Hazelcast pod, because the discovery mechanism now relies on a service definition.

### Adding a Hazelcast Service
In Kubernetes a _Service_ describes a set of Pods that perform the same task.  For example, the set of nodes in a Hazelcast cluster.  An important use for a Service is to create a load balancer which distributes traffic across members of the set.  But a _Service_ can also be used as a standing query which makes a dynamically changing set of Pods available via the Kubernetes API.  This is actually how our discovery mechanism works, by relying on the service to discover other Hazelcast pods.

Here is the service description:
```yaml
apiVersion: v1
kind: Service
metadata:
  labels:
    name: hazelcast
  name: hazelcast
spec:
  ports:
    - port: 5701
  selector:
    name: hazelcast
```

The important thing to note here is the `selector`. It is a query over labels, that identifies the set of _Pods_ contained by the _Service_.  In this case the selector is `name: hazelcast`.  If you look at the Replication Controller specification below, you'll see that the pod has the corresponding label, so it will be selected for membership in this Service.

Create this service as follows:
```sh
$ kubectl create -f hazelcast-service.yaml
```

### Adding replicated nodes
The real power of Kubernetes and Hazelcast lies in easily building a replicated, resizable Hazelcast cluster.

In Kubernetes a _Replication Controller_ is responsible for replicating sets of identical pods.  Like a _Service_ it has a selector query which identifies the members of it's set.  Unlike a _Service_ it also has a desired number of replicas, and it will create or delete _Pods_ to ensure that the number of _Pods_ matches up with it's desired state.

Replication Controllers will "adopt" existing pods that match their selector query, so let's create a Replication Controller with a single replica to adopt our existing Hazelcast Pod.

```yaml
apiVersion: v1
kind: ReplicationController
metadata:
  labels:
    name: hazelcast
  name: hazelcast
spec:
  replicas: 1
  selector:
    name: hazelcast
  template:
    metadata:
      labels:
        name: hazelcast
    spec:
      containers:
          image: quay.io/pires/hazelcast-kubernetes:0.5.1
          name: hazelcast
          env:
          - name: "DNS_DOMAIN"
            value: "cluster.local"
          ports:
            - containerPort: 5701
              name: hazelcast
```

You may note that we tell Kubernetes that the container exposes the `hazelcast` port.  Finally, we tell the cluster manager that we need 1 cpu core.

The bulk of the replication controller config is actually identical to the Hazelcast pod declaration above, it simply gives the controller a recipe to use when creating new pods.  The other parts are the `selector` which contains the controller's selector query, and the `replicas` parameter which specifies the desired number of replicas, in this case 1.

Last but not least, we set `DNS_DOMAIN` environment variable according to your Kubernetes clusters DNS configuration.

Create this controller:

```sh
$ kubectl create -f hazelcast-controller.yaml
```

After the controller provisions successfully the pod, you can query the service endpoints:
```sh
$ kubectl get endpoints hazelcast -o yaml
{
    "kind": "Endpoints",
    "apiVersion": "v1",
    "metadata": {
        "name": "hazelcast",
        "namespace": "default",
        "selfLink": "/api/v1/namespaces/default/endpoints/hazelcast",
        "uid": "094e507a-2700-11e5-abbc-080027eae546",
        "resourceVersion": "4094",
        "creationTimestamp": "2015-07-10T12:34:41Z",
        "labels": {
            "name": "hazelcast"
        }
    },
    "subsets": [
        {
            "addresses": [
                {
                    "ip": "<IP_ADDRESS>",
                    "targetRef": {
                        "kind": "Pod",
                        "namespace": "default",
                        "name": "hazelcast-nsyzn",
                        "uid": "f57eb6b0-2706-11e5-abbc-080027eae546",
                        "resourceVersion": "4093"
                    }
                }
            ],
            "ports": [
                {
                    "port": 5701,
                    "protocol": "TCP"
                }
            ]
        }
    ]
}
```

You can see that the _Service_ has found the pod created by the replication controller.

Now it gets even more interesting.

Let's scale our cluster to 2 pods:
```sh
$ kubectl scale rc hazelcast --replicas=2
```

Now if you list the pods in your cluster, you should see two hazelcast pods:

```sh
$ kubectl get pods
NAME              READY     STATUS    RESTARTS   AGE
hazelcast-nanfb   1/1       Running   0          40s
hazelcast-nsyzn   1/1       Running   0          2m
kube-dns-xudrp    3/3       Running   0          1h
```

To prove that this all works, you can use the `log` command to examine the logs of one pod, for example:

```sh
$ kubectl log hazelcast-nanfb hazelcast
2015-07-10 13:26:34.443  INFO 5 --- [           main] com.github.pires.hazelcast.Application   : Starting Application on hazelcast-nanfb with PID 5 (/bootstrapper.jar started by root in /)
2015-07-10 13:26:34.535  INFO 5 --- [           main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@42cfcf1: startup date [Fri Jul 10 13:26:34 GMT 2015]; root of context hierarchy
2015-07-10 13:26:35.888  INFO 5 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2015-07-10 13:26:35.924  INFO 5 --- [           main] c.g.p.h.HazelcastDiscoveryController     : Asking k8s registry at https://kubernetes.default.svc.cluster.local..
2015-07-10 13:26:37.259  INFO 5 --- [           main] c.g.p.h.HazelcastDiscoveryController     : Found 2 pods running Hazelcast.
2015-07-10 13:26:37.404  INFO 5 --- [           main] c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.5.2] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [<IP_ADDRESS>, <IP_ADDRESS>]
2015-07-10 13:26:37.405  INFO 5 --- [           main] c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.5.2] Prefer IPv4 stack is true.
2015-07-10 13:26:37.415  INFO 5 --- [           main] c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.5.2] Picked Address[<IP_ADDRESS>]:5701, using socket ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true
2015-07-10 13:26:37.852  INFO 5 --- [           main] com.hazelcast.spi.OperationService       : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Backpressure is disabled
2015-07-10 13:26:37.879  INFO 5 --- [           main] c.h.s.i.o.c.ClassicOperationExecutor     : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Starting with 2 generic operation threads and 2 partition operation threads.
2015-07-10 13:26:38.531  INFO 5 --- [           main] com.hazelcast.system                     : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Hazelcast 3.5 (20150617 - 4270dc6) starting at Address[<IP_ADDRESS>]:5701
2015-07-10 13:26:38.532  INFO 5 --- [           main] com.hazelcast.system                     : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Copyright (c) 2008-2015, Hazelcast, Inc. All Rights Reserved.
2015-07-10 13:26:38.533  INFO 5 --- [           main] com.hazelcast.instance.Node              : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Creating TcpIpJoiner
2015-07-10 13:26:38.534  INFO 5 --- [           main] com.hazelcast.core.LifecycleService      : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Address[<IP_ADDRESS>]:5701 is STARTING
2015-07-10 13:26:38.672  INFO 5 --- [        cached1] com.hazelcast.nio.tcp.SocketConnector    : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Connecting to /<IP_ADDRESS>:5701, timeout: 0, bind-any: true
2015-07-10 13:26:38.683  INFO 5 --- [        cached1] c.h.nio.tcp.TcpIpConnectionManager       : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Established socket connection between /<IP_ADDRESS>:59951
2015-07-10 13:26:45.699  INFO 5 --- [ration.thread-1] com.hazelcast.cluster.ClusterService     : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2]

Members [2] {
	Member [<IP_ADDRESS>]:5701
	Member [<IP_ADDRESS>]:5701 this
}

2015-07-10 13:26:47.722  INFO 5 --- [           main] com.hazelcast.core.LifecycleService      : [<IP_ADDRESS>]:5701 [someGroup] [3.5.2] Address[<IP_ADDRESS>]:5701 is STARTED
2015-07-10 13:26:47.723  INFO 5 --- [           main] com.github.pires.hazelcast.Application   : Started Application in 13.792 seconds (JVM running for 14.542)
```

Now let's scale our cluster to 4 nodes:
```sh
$ kubectl scale rc hazelcast --replicas=4
```

Examine the status again by checking a node’s log and you should see the 4 members connected.

### tl; dr;
For those of you who are impatient, here is the summary of the commands we ran in this tutorial.

```sh
# create a service to track all hazelcast nodes
kubectl create -f hazelcast-service.yaml

# create a replication controller to replicate hazelcast nodes
kubectl create -f hazelcast-controller.yaml

# scale up to 2 nodes
kubectl scale rc hazelcast --replicas=2

# scale up to 4 nodes
kubectl scale rc hazelcast --replicas=4
```

### Hazelcast Discovery Source

```java
package com.github.pires.hazelcast;

import com.fasterxml.jackson.annotation.JsonIgnoreProperties;
import com.fasterxml.jackson.databind.ObjectMapper;
import com.hazelcast.config.Config;
import com.hazelcast.config.GroupConfig;
import com.hazelcast.config.JoinConfig;
import com.hazelcast.config.MulticastConfig;
import com.hazelcast.config.NetworkConfig;
import com.hazelcast.config.SSLConfig;
import com.hazelcast.config.TcpIpConfig;
import com.hazelcast.core.Hazelcast;
import java.io.IOException;
import java.net.URL;
import java.nio.file.Files;
import java.nio.file.Paths;
import java.security.KeyManagementException;
import java.security.NoSuchAlgorithmException;
import java.security.SecureRandom;
import java.security.cert.X509Certificate;
import java.util.List;
import java.util.UUID;
import java.util.concurrent.CopyOnWriteArrayList;
import javax.net.ssl.HostnameVerifier;
import javax.net.ssl.HttpsURLConnection;
import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLSession;
import javax.net.ssl.TrustManager;
import javax.net.ssl.X509TrustManager;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.CommandLineRunner;
import org.springframework.stereotype.Controller;

/**
 * Read from Kubernetes API all Hazelcast service bound pods, get their IP and connect to them.
 */
@Controller
public class HazelcastDiscoveryController implements CommandLineRunner {

  private static final Logger log = LoggerFactory.getLogger(
      HazelcastDiscoveryController.class);

  @JsonIgnoreProperties(ignoreUnknown = true)
  static class Address {
    public String ip;
  }

  @JsonIgnoreProperties(ignoreUnknown = true)
  static class Subset {
    public List<Address> addresses;
  }

  @JsonIgnoreProperties(ignoreUnknown = true)
  static class Endpoints {
    public List<Subset> subsets;
  }

  private static String getServiceAccountToken() throws IOException {
    String file = "/var/run/secrets/kubernetes.io/serviceaccount/token";
    return new String(Files.readAllBytes(Paths.get(file)));
  }

  private static String getEnvOrDefault(String var, String def) {
    final String val = System.getenv(var);
    return (val == null || val.isEmpty())
        ? def
        : val;
  }

  // TODO: Load the CA cert when it is available on all platforms.
  private static TrustManager[] trustAll = new TrustManager[] {
    new X509TrustManager() {
      public void checkServerTrusted(X509Certificate[] certs, String authType) {}
      public void checkClientTrusted(X509Certificate[] certs, String authType) {}
      public X509Certificate[] getAcceptedIssuers() { return null; }
    }
  };
  private static HostnameVerifier trustAllHosts = new HostnameVerifier() {
    public boolean verify(String hostname, SSLSession session) {
      return true;
    }
  };

  @Override
  public void run(String... args) {
    final String serviceName = getEnvOrDefault("HAZELCAST_SERVICE", "hazelcast");
    final String path = "/api/v1/namespaces/default/endpoints/";
    final String domain = getEnvOrDefault("DNS_DOMAIN", "cluster.local");
    final String host = getEnvOrDefault("KUBERNETES_MASTER", "https://kubernetes.default.svc.".concat(domain));
    log.info("Asking k8s registry at {}..", host);

    final List<String> hazelcastEndpoints = new CopyOnWriteArrayList<>();

    try {
      String token = getServiceAccountToken();

      SSLContext ctx = SSLContext.getInstance("SSL");
      ctx.init(null, trustAll, new SecureRandom());

      URL url = new URL(host + path + serviceName);
      HttpsURLConnection conn = (HttpsURLConnection)url.openConnection();
      // TODO: remove this when and replace with CA cert loading, when the CA is propogated
      // to all nodes on all platforms.
      conn.setSSLSocketFactory(ctx.getSocketFactory());
      conn.setHostnameVerifier(trustAllHosts);
      conn.addRequestProperty("Authorization", "Bearer " + token);

      ObjectMapper mapper = new ObjectMapper();
      Endpoints endpoints = mapper.readValue(conn.getInputStream(), Endpoints.class);
      if (endpoints != null) {
        if (endpoints.subsets != null && !endpoints.subsets.isEmpty()) {
          endpoints.subsets.parallelStream().forEach(subset -> {
            subset.addresses.parallelStream().forEach(
                addr -> hazelcastEndpoints.add(addr.ip));
          });
        }
      }
    } catch (IOException | NoSuchAlgorithmException | KeyManagementException ex) {
      log.warn("Request to Kubernetes API failed", ex);
    }

    log.info("Found {} pods running Hazelcast.", hazelcastEndpoints.size());

    runHazelcast(hazelcastEndpoints);
  }

  private void runHazelcast(final List<String> nodes) {
    // configure Hazelcast instance
    final Config cfg = new Config();
    cfg.setInstanceName(UUID.randomUUID().toString());
    // group configuration
    final String HC_GROUP_NAME = getEnvOrDefault("HC_GROUP_NAME", "someGroup");
    final String HC_GROUP_PASSWORD = getEnvOrDefault("HC_GROUP_PASSWORD",
        "someSecret");
    final int HC_PORT = Integer.parseInt(getEnvOrDefault("HC_PORT", "5701"));
    cfg.setGroupConfig(new GroupConfig(HC_GROUP_NAME, HC_GROUP_PASSWORD));
    // network configuration initialization
    final NetworkConfig netCfg = new NetworkConfig();
    netCfg.setPortAutoIncrement(false);
    netCfg.setPort(HC_PORT);
    // multicast
    final MulticastConfig mcCfg = new MulticastConfig();
    mcCfg.setEnabled(false);
    // tcp
    final TcpIpConfig tcpCfg = new TcpIpConfig();
    nodes.parallelStream().forEach(tcpCfg::addMember);
    tcpCfg.setEnabled(true);
    // network join configuration
    final JoinConfig joinCfg = new JoinConfig();
    joinCfg.setMulticastConfig(mcCfg);
    joinCfg.setTcpIpConfig(tcpCfg);
    netCfg.setJoin(joinCfg);
    // ssl
    netCfg.setSSLConfig(new SSLConfig().setEnabled(false));
    // set it all
    cfg.setNetworkConfig(netCfg);
    // run
    Hazelcast.newHazelcastInstance(cfg);
  }

}

```

repository: donray/hazelcast-kubernetes

repo_name: donray/hazelcast-kubernetes


text:
# Bridge Client

Written by Jeff Rose and James Zinger of Axon Interactive

## Description

This browser library is the client-side portion of Bridge, Axon's own API development framework for database-backed browser applications. It provides a direction function call interface to each of the default Bridge API routes as well as some convenience functions for higher-order operations that are common to client-side webapps.

This version of bridge-client (v0.2.12) in intended to be compatible with v0.2.12 of bridge-server (the counterpart server-side module).

## Usage

This module is available from the Bower package registry. Install it with the following command:

```bash
bower install axon-bridge-client
```

Once installed, simply point your build process to

`<bower_components>/axon-bridge-client/lib/axon-bridge-client.js`

Once it is being included in your website, you will be able to access Bridge globally (as window.Bridge).

## Dependencies

### CryptoJS

Internal security computations are done using hash functions provided by CryptoJS.

### Q

In order to maintain consistency with the server-side API framework and to handle asynchrony better and more intuitively, this client-side library comes packaged with the Q.js promise library. All Bridge API call functions return promises that adhere to the Promise A+ spec.

repository: AxonInteractive/bridge-client

repo_name: AxonInteractive/bridge-client


text:
Date: 2017/05/29
Authors: [Stefan Endres](http://www.stefanendres.com)
Keywords: Website, Responsive

---
---

# stefanendres.com/dev/superfamerelaxation

![](stefanendres-com-dev-superfamerelaxation.png)

Website, Responsive, Highest Level User Experience Website

[stefanendres.com/dev/superfamerelaxation](http://stefanendres.com/dev/superfamerelaxation)

---

![](heimspiel_10_stefan.png)

Heimspiel. Bi-weekly public solo exhibitions at New Media Kassel.

Every second week a student of New Media exhibits works in our 15 sqm
dedicated gallery space. The 'Home Game' series helps the students to
test run ideas and to gain experience in planning and setting up works.
In a public critique process the class and visitors then discuss the show.

gha_language: PHP


text:
# The IEEE Student Branch Program

---

IEEE was founded in 1884 with Alexander Graham Bell and Thomas Edison among its charter members. Today, IEEE serves over 400,000 members worldwide. Over 100,000 Student and Graduate Student members worldwide make up 25% of the membership of IEEE and are essential to its continued growth and vitality. Not only is IEEE the world’s largest technical and professional society, it also publishes a significant amount of the electrical engineering and computer-science literature in the world.

IEEE worldwide membership is geographically divided into ten Regions. These Regions are further divided into Sections that serve as the centers of activity for professional engineers at the local level. Your Student Branch falls under your local Section. You can locate your Section by visiting [myIEEE](https://www.ieee.org/membership_services/membership/my_ieee.html) and selecting Communities.

Student Branches provide an opportunity for IEEE Student members to begin networking in their areas of interest and future profession. There are over 3,000 Student Branches in over 100 countries, globally.

## Starting an IEEE Student Branch

To start a Student Branch, here are the steps to be followed.

Basic necessities :

1. Three faculty members
2. Min. 20 student members needed to start a Student Branch
3. Bank Account Details

**(Note: Faculty and Students have to take up the IEEE Membership)**

With the above, one has to file the petition.

The petition can be found [here.](https://www.ieee.org/societies_communities/geo_activities/forms_petitions/forms_petitions_index.html) Fill up the petition form especially pages 3 to 9 and then scan the same and make a pdf of it sequentially and mail it to<EMAIL_ADDRESS>and mark a cc to us.

or any further queries on the same, kindly feel free to communicate with us.

**SAC Chair:** Mrs. Dr. G. Sree Lakshmi<EMAIL_ADDRESS>

## IEEE Hyderabad Section Student Branches

|S .No	|	School Name											|	Count of Members	|
| ----- | ----------------------------------------------------- | --------------------- |
| **Total** | **Hyderabad Section**                                    | **4045**                  |
|	1	|	G Pulla Reddy Engrg College							|	191					|
|	2	|	GITAM University									|	155					|
|	3	|	Univ College of Eng - Osmania Univ-HYDERABAD		|	123					|
|	4	|	MVSR Engineering College							|	122					|
|	5	|	Sasi Institute of Technology & Engineering			|	118					|
|	6	|	Gokaraju Ranga Raju Inst of Eng & Tech-HYDERABAD	|	108					|
|7|Keshav Memorial Institute of Technology-KMIT|103|
|8|Balaji Institute of Technology & Science|96|
|9|Dadi Inst of Eng and Tech|94|
|10|Muffakhamjah College of Engineering & Technology|94|
|11|Geethanjali College of Engineering & Technology|90|
|12|Vardhaman College of Engrg-Shamshabad|87|
|13|Nalla Malla Reddy Engineering College|86|
|14|Sreyas Institute of Engineering & Technology|86|
|15|Vaagdevi College Of Engineering|84|
|16|CMR College of Engineering & Technology|80|
|17|Gayatri Vidya Parishad College Of Engrg|77|
|18|Koneru Lakshmaiah College of Engineering|77|
|19|GVP College of Engineering For Women|70|
|20|Mvgr College Of Engineering|70|
|21|Raghu Institute of Technology|70|
|22|VNR Vignana Jyothi Inst Of Eng & Tech|63|
|23|Sreenidhi Inst of Science & Tech|62|
|24|Vaagdevi Engineering College|55|
|25|Chaitanya Bharathi Institute of Tech - HYDERABAD|54|
|26|Jayamukhi Inst Of Technological Sciences|51|
|27|Jawaharlal Nehru Tech Univ-Hyderabad|49|
|28|Indian Institute of Technology-Hyderabad|48|
|29|International Institute of Info Tech - Hyderabad|46|
|30|National Institute of Technology-Warangal|42|
|31|BVRIT Hyderabad|38|
|32|Hyderabad Instiute of Technology & Management|38|
|33|Shri Vishnu Engineering College For Women|38|
|34|Vignana Bharathi Institute Of Technology|37|
|35|Birla Inst of Tech & Sci Pilani - Hyderabad|36|
|36|Raghu Engineering College - Visakhapatnam|36|
|37|G Narayanamma Inst Of Tech & Sci (Women)|35|
|38|Institute of Aeronautical Engineering|34|
|39|Vignan's Foundation for Sci, Tech & Research|34|
|40|Vasavi College of Engineering - HYDERABAD|33|
|41|Stanley Coll of Eng & Tech for Women|32|
|42|JNTUK Univ College of Engineering Narasaropet|31|
|43|LAKIREDDY BALI REDDY COLLEGE OF ENGINEERING|31|
|44|National Institute of Technology-Andhra Pradesh|31|
|45|Vignan's Institute of Information Technology|31|
|46|Audisankara College of Engineering & Tech|30|
|47|Jawaharlal Nehru Technological Univ-Anantapur|30|
|48|Rajeev Gandhi Memorial College of Eng and Tech|28|
|49|Prasad V Potluri Siddhartha Ins of Tech Vijayawada|26|
|50|S R Engineering College - Warangal|26|
|51|Velagapudi Ramakrishna Siddhartha Eng College|26|
|52|Vignan's Inst. of Management and Tech for Women|26|
|53|Aditya College of Engineering and Technology|25|
|54|Chadalawada Ramanamma Engineering College|24|
|55|Satya Inst of Tech and Management SITAM|24|
|56|Sir C.R.Reddy College Of Eng|24|
|57|St. Ann's College of Engineering & Tech-Chirala|23|
|58|SV Engineering College|22|
|59|Vidya Jyothi Institute of Technology|22|
|60|Andhra Univ College Of Engineering|21|
|61|Anil Neerukonda Inst Of Tech & Sciences|21|
|62|Matrusri Engineering College|21|
|63|Sri Venkateswara College of Engineering|21|
|64|Srinivasa Ramanujam Institute of Technology|21|
|65|Vardhaman College of Engineering|21|
|66|SRM University, AP - Amaravati|20|
|67|Vignan Institute of Technology & Science|20|
|68|Madanapalle Inst of Tech & Science, MADANAPALLE|19|
|69|ANURAG GROUP OF INSTITUTIONS|18|
|70|Joginpally B.R. Engineering College|17|
|71|Mahindra Ecole Centrale|17|
|72|Santhiram Engineering College|17|
|73|Vellore Institute of Technology University, AP|17|
|74|Annamacharya Institute of Technology, Rajempet|16|
|75|CMR Technical Campus|16|
|76|Malla Reddy College of Eng.(CM Eng. College)|16|
|77|Sree Vidyanikethan Engineering College-TIRUPATI|16|
|78|KG Reddy College of Engineering and Technology|15|
|79|CMR Institute of Technology-Hyderabad|14|
|80|Kakatiya Institute of Tech & Science - Warangal|14|
|81|Narasaraopeta Engineering College|13|
|82|Chaitanya Bharathi Institute of Tech - Proddatur|12|
|83|Geethanjali Institute of Science & Technology|12|
|84|Hyderabad Univ Of - School Of Maths & Comp Sci|12|
|85|Jawaharlal Nehru Technological Univ-Viziangaram|12|
|86|Kommuri Pratap Reddy Institute of Technology|12|
|87|Padmasri Dr B V Raju Inst of Tech|12|
|88|Sridevi Women'S Engineering College|12|
|89|Govt College Of Engrg-Ananthapur/Jntu Univ|11|
|90|Sphoorthy Engineering College|11|
|91|Tirumala Engineering College|11|
|92|Vasireddy Venkatadri Institute of Technology|11|
|93|Mahatma Gandhi Inst Of Tech|8|
|94|Malla Reddy Institute of Technology & Science|8|
|95|Osmania Univ|8|
|96|Jawaharlal Nehru Technological Univ-Kakinada|7|
|97|Centurion Univ of Technology & Management, AP|6|
|98|CVR College of Engineering|6|
|99|Malla Reddy Institute of Enging and Tech.|5|
|100|Methodist College of Engineering & Technology|5|
|101|RVR &JCOP College Of Engrg|5|
|102|Acharya Nagarjuna University|4|
|103|Bapatla Engineering College Mahatmajipuram|3|
|104|Vishnu Institute Of Technology|3|
|105|Bharath Inst Of Engineering & Tech|2|
|106|Gudlavalleru Engineering College|2|
|107|Kakatia Inst Of Tech & Science Kaktia Univ|2|
|108|Konneru L College Of Engrg-Guntur/Nagarjuna U|2|
|109|LENDI INSTITUTE OF ENGINEERING & TECHNOLOGY|2|
|110|NBKR Inst Of Tech-Vidyanagar/Sri Venkateswar|2|
|111|Rajeev Gandhi Memorial College of Eng & Tech|2|
|112|Vignan University - GUNTUR|2|
|113|Aditya Institute Of Tech & Management - Tekkali|1|
|114|CMR Engineering College|1|
|115|Dravidian University|1|
|116|Godavari Inst Of Eng & Tech|1|
|117|Guru Nanak Institutions Technical Campus-HYDERABAD|1|
|118|Jawaharlal Nehru Technical Univ - Andhra Pradesh|1|
|119|Jawaharlal Nehru Technological Univ-Pulivendula|1|
|120|Kakatia Univ|1|
|121|KKR & KSR Institute of Tech & Sciences|1|
|122|Loyola Inst Of Tech & Mgmt|1|
|123|Malla Reddy Eng College|1|
|124|Nagarjanasagar College Of Engrg-Hyderabad/Jnt|1|
|125|PSCMR College of Engineering and Technology|1|
|126|Rajiv Gandhi Memorial College Of Engr|1|
|127|Rajiv Gandhi University of Knowledge Technologies|1|
|128|Rayalaseema University|1|
|129|Scient Inst Of Tech|1|
|130|Shadan College Of Engg & Tech|1|
|131|Sri Sathya Sai Inst Of Higher Learning|1|
|132|TKR College of Engineering and Tech|1|

## IEEE organization

---

To provide services for members, IEEE depends not only on a well-trained staff but also on thousands of dedicated volunteers, including Student Branch officers, faculty counselors, Section officers, and Regional volunteers. The Student Activities Committee, Student Services Headquarters staff, Student Branch Chapters, Student Branch affinity groups, and faculty counselors are all committed to the success of the student program. To review the formal guidelines for the student program, please refer to the [Member and Geographic Activities Operations Manual](https://www.ieee.org/documents/section_09_june_2016.pdf) (PDF, 361 KB).

## Branch administration

---

The responsibility for administering Branch operations lies within your Student Branch Executive Committee. The Executive Committee should consist of all of the Branch Officers, sub-committee Chairs, and the Branch Counselor. The key to an efficient and fun Executive Committee lies in regular meetings and good communication. Please see the [Branch Calendar](https://www.ieee.org/membership_services/membership/students/st_calendar-student_branch_development.pdf) (PDF, 286 KB).

## SB Executive Committee

---

The key to running a successful Student Branch is in the administration. There are several key positions: the Branch Officers (Chair, Vice-Chair, Treasurer, and Secretary), the Branch Counselor (or Faculty Advisor), and the subcommittee Chairs. While each has somewhat different duties, it is important to work together as a team. All officers should be aware of the benefits of IEEE membership. [Find more information.](https://www.ieee.org/membership_services/membership/benefits/benefits.html)

## Student Branch operations

---

Effective Student Branch operations comes from knowing how to develop a varied and interesting program of activities for members. The intent of this section is to provide you with some ideas on how to keep your Student Branch vibrant and how to provide new services to your members.

## Student Branch program

---

In planning your Branch programs for the year, it is important to keep in mind that events where students are highly engaged are critical to your Branch’s success. Ask your members what their interests are and invite them to participate in a subcommittee that interests them. When choosing an event, you should ask several questions to evaluate the potential of that event:

 1. Will this event attract new members?

 2. Do we have the resources to carry it through (e.g., time, people, funding)?

 3. How will it satisfy the needs of existing members?

 4. Does it meet a specific need for your Branch?

 5. Will you need to undertake a fundraising effort to hold this event?

Once you have decided on Branch programs for the year, you need to organize the subcommittees and ensure the commitment is there. 7. These committees will gain valuable leadership experience. Be sure to involve as many members (and non-members) as possible in order to ensure the growth of your Branch.

The following is a list of some activities that Student Branches have undertaken in the recent years:

* Host an annual “Welcome Back” or “End of School” event to welcome and farewell your members
* Collaborate with other IEEEE Student Branches, Young Professionals, IEEE-Eta Kappa Nu (IEEE-HKN), and Women in Engineering groups
* Schedule speakers on technical or professional subjects. See SPAx for more information
* Enter design competitions
* Design a Student Branch website and enter the Global Student Website and Social Media Competition
* Organize field trips to industry
* Give tutorials to non-members
* Raise funds for charity or Student Branch projects
* Participate in IEEE conferences
* Publish a Student Branch newsletter
* Participate in engineering awareness programs

## Student Branch planning

---

To ensure success of any Branch program, careful planning is crucial: assess the state of your Branch; identify major goals and objectives for the year; identify activities that will allow you to meet these goals and objectives. For each activity, develop an action plan.

## SB Reporting requirements

---

To help you keep track of your yearly activities, your Student Branch is required to [submit the Student Branch Activity Report.](https://sbr.vtools.ieee.org/) It also serves as a valuable historical document to aid future executives in their planning and records financial statements so it is important that the Student Branch Treasurer is involved in the preparation of the report. To encourage you to submit this plan and to meet IEEE Bylaw requirements, an incentive allotment of US$100 is given if your Branch has 50 or more members or US$50 if your Student Branch has fewer than 50 members. The due date for filing this report is on or before 1 November annually. In addition, IEEE provides an incentive rebate of US$2 per Student or Graduate Student member at your Branch (based on membership statistics as of 31 December of the previous year).

Completing the Student Branch Activity Report should help you evaluate the success of your program and to provide some continuity for future years. IEEE requires that Student Branches report their activities and maintain a minimum of 10 Student or Graduate Student members.

## SB Elections

---

You can hold elections at any time. All active IEEE Student and Graduate Student members should participate in your elections. Be sure to provide incoming officers the Branch records and transferring any accounts to the new leadership. Assist the new leadership by developing the Branch program for the upcoming academic year and arranging for new committees to meet and begin planning. [Be sure to record the newly elected Chair and Counselor information.](https://officers.vtools.ieee.org/)

## SB Membership

---

Attracting and retaining new Student and Graduate Student members is an opportunity and a challenge for most Student Branches. Student Branches have natural attrition, through graduation and to members letting their membership lapse.

It is important for Student members to see the value of their membership at the Student Branch level and the value of becoming an IEEE Young Professional. [Find more information about IEEE Young Professionals.](http://yp.ieee.org/) These experiences as a higher IEEE Grade member will allow opportunities for professional development, mentorship, and personal growth.

When recruiting new members, it is important to consider students who may not necessarily be in your immediate academic department. Students in the IEEE designated fields of interest can also benefit from membership. The professional, technical, and social activities that a Student Branch can offer are beyond just the campus and local experience. Be sure to direct prospective members to [join IEEE.](https://www.ieee.org/membership_services/membership/join/join_DB.html)


text:
# Config persistent component test cases

## Contents##
- [Test cases to verify Config Persistence daemon](#test-cases-to-verify-config-persistence-daemon)
    - [Test to verify no configdb detection](#test-to-verify-no-configdb-detection)
    - [Test to verify configdb detection and connection](#test-to-verify-configdb-detection-and-connection)
    - [Test to verify configdb detect startup row](#test-to-verify-configdb-detect-startup-row)
    - [Test to verify configdb mark completion](#test-to-verify-configdb-mark-completion)
    - [Test to verify startup config push during boot](#test-to-verify-startup-config-push-during-boot)
- [Test cases to verify Config Persistence utility](#test-cases-to-verify-config-persistence-utility)
    - [Test to verify show startup configuration](#test-to-verify-show-startup-configuration)
    - [Test to verify delete startup configuration](#test-to-verify-delete-startup-configuration)
    - [Test to verify running configuration to startup configuration](#test-to-verify-running-configuration-to-startup-configuration)
    - [Test to verify startup configuration to running configuration](#test-to-verify-startup-configuration-to-running-configuration)

##Test cases to verify the config persistence daemon ##
### Objective ###
Test cases to verify that the configdb and the cfgd daemon work.
### Requirements ###
The requirements for this test case are:

 - AS5712 switch

### Setup ###
#### Topology diagram ####
```ditaa
              +------------------+
              |                  |
              |  AS5712 switch   |
              |                  |
              +------------------+
```

### Test to verify no configdb detection  ###
#### Description ####
Test to verify that the config persistence daemon detects that configdb is not present and logs the correct error.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the "No rows found in the config table" error message is received.
#### Test fail criteria ####
Test case result is a fail if the "No rows found in the config table" error message is not received.

### Test to verify configdb detection and connection  ###
#### Description ####
Test to verify that the config persistence daemon detects configdb and connects to db.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the cfgd is able to detect an empty configdb with no row present.
#### Test fail criteria ####
Test case result is a fail if the cfgd is not able connect to the configdb.

### Test to verify configdb detect startup row  ###
#### Description ####
Test to verify that the config persistence daemon detects a startup row in the configdb.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the "Config data found" message is received.
#### Test fail criteria ####
Test case result is a fail if  the "Config data found" message is not received.

### Test to verify configdb mark completion  ###
#### Description ####
Test to verify that the config persistence daemon marks completion in the configdb after pushing a startup config to a running config.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the cur_cfg and next_cfg in the System table is greater than 1.
#### Test fail criteria ####
Test case result is a fail if the cur_cfg and next_cfg in the System table is zero or empty.

### Test to verify startup config push during boot ###
#### Description ####
Test to verify that the config persistence daemon copies the startup config saved in the configdb to the running db during boot up time, then saves a startup config with hostname configured to "CT-TEST" and the system is rebooted.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the hostname in the System table is "CT-TEST"
#### Test fail criteria ####
Test case result is a fail if the hostname in the System table is not "CT-TEST".

## Test cases to verify Config Persistence utility ##
### Objective ###
Test cases to verify that the cfgdbutil performs a copy configuration and shows the configuration correctly.
### Requirements ###
The requirements for this test case are:

 - AS5712 switch

### Setup ###
#### Topology diagram ####
```ditaa
              +------------------+
              |                  |
              |  AS5712 switch   |
              |                  |
              +------------------+
```

#### Test setup ####
### Test to verify show startup configuration  ###
#### Description ####
Test to verify that the config persistence utility fetches the startup configuration in JSON format from the startup row in the configdb. Saves a dummy JSON string in the startup row, executes the show command and then compares the output of the show command and the configured dummy JSON string to verify they are the same.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the show command output matches with the JSON string configured during setup.
#### Test fail criteria ####
Test case result is a fail if the show command output doesn't match with the JSON string configured during setup.

### Test to verify delete startup configuration ###
#### Description ###
Test to verify that the config persistence utility fetches a startup row in the configdb and deletes it. Inserts a dummy row with type = startup and executes the delete command.
### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the show command output matches with the JSON string configured during setup.

#### Test fail criteria ####
Test case result is a fail if the show command output doesn't match with the JSON string configured during setup.

### Test to verify running configuration to startup configuration ###
#### Description ###
Test to verify that the config persistence utility copies the current system running configuration and saves it in JSON format in the startup row of the configdb. Configure hostname as "CT-TEST" in the running configuration and execute a copy running the configuration to startup configuration.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the saved JSON string in the startup row contains hostname key value as "CT-TEST" in the System table.
#### Test fail criteria ####
Test case result is a fail if the saved JSON string in the startup row does not contain the hostname key value as "CT-TEST" in the System table.

### Test to verify startup configuration to running configuration###
#### Description ###
Test to verify that the config persistence utility copies the saved JSON format configuration in the startup row of the configdb to the current system running configuration. Save a startup JSON string in the startup row with the hostname configured to "CT-TEST" and execute a copy of the startup config to the running config.

### Test result criteria ###
#### Test pass criteria ####
Test case result is a success if the `show running-config` command has hostname configured as "CT-TEST".

#### Test fail criteria ####
Test case result is fail if the `show running-config` command has a hostname not configured as "CT-TEST".


text:
# Angles CSGO Graphics

![Full HUD](./media/FullHUD.jpg)

## Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

### Prerequisites

* [NodeCG](https://www.nodecg.dev/)
* [NodeCG CSGO Manager](https://github.com/EwanLyon/nodecg-csgo-manager)

For killfeed and player firing indicators on the mini map:

* [HLAE](https://www.advancedfx.org/download/) I recommed understanding what this program does if you haven't used it before

### Installing

A GitHub action is planned to be made. Currently you have to manually build

1. Clone the repo into the NodeCG bundles folder

   ```sh
   cd nodecg/bundles
   git clone https://github.com/EwanLyon/angles-csgo-hud.git
   ```

2. Install NPM packages

   ```sh
   npm install
   ```

3. Run build

   ```sh
   npm run build
   ```

4. Start NodeCG

   ```sh
   npm run start
   ```

   or

   ```sh
   cd ../..
   node .
   ```

5. (Optional) If running HLAE type into the CSGO console

    ```sh
    mirv_pgl events whitelist add "player_death"
    mirv_pgl events whitelist add "other_death"
    mirv_pgl events whitelist add "weapon_fire"
    mirv_pgl url "ws://localhost:31337/mirv"
    mirv_pgl start
    ```

<!-- ROADMAP -->
## Roadmap

Currently a lot of code cleanup needs to occur. Expect changes to occur rapidly and break bundles using this.

See the [open issues](https://github.com/EwanLyon/clubwho-csgo-graphics/issues) for a list of proposed features (and known issues).

## Built With

* [NodeCG](https://www.nodecg.dev/)
* [NodeCG CSGO Manager](https://github.com/EwanLyon/nodecg-csgo-manager)
* [TypeScript](https://www.typescriptlang.org/)
* [React](https://reactjs.org/)
* [Redux](https://redux.js.org/)
* [Styled Components](https://styled-components.com/)

<!-- CONTRIBUTING -->
## Contributing

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

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

## License

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

repository: EwanLyon/angles-csgo-hud

branch_name: refs/heads/main

repo_name: EwanLyon/angles-csgo-hud


text:
# Adding plug-ins and features to category.xml

This document is a quick tutorial on how to get a working category.xml file working.
You will find yourself editing it in one of the following circumstances:

- DDS4CCM is upgrade to a new Eclipse base version
- A new dependency is added to DDS4CCM

In other case, you will likely encounter problems when trying to install DDS4CCM in a clean RSA
environment. The Eclipse Install New Software wizard may report a failure such as the following:

> Cannot complete the install because one or more required items could not be found.
>>  Software being installed: CX Base Components <IP_ADDRESS>903081520 (com.zeligsoft.base.feature.group <IP_ADDRESS>903081520)

>> Missing requirement: Zeligsoft Domain Language Core <IP_ADDRESS>903081520 (com.zeligsoft.base.zdl <IP_ADDRESS>903081520) requires 'bundle org.eclipse.xtend.shared.ui [1.0.1,2.1.0)' but it could not be found

>> Cannot satisfy dependency:
>>>    From: CX Base Components <IP_ADDRESS>903081520 (com.zeligsoft.base.feature.group <IP_ADDRESS>903081520)

>>>   To: com.zeligsoft.base.zdl [<IP_ADDRESS>903081520]
In the case, the error is telling you that the bundle `org.eclipse.xtend.shared.ui` is not part
of the p2 repository created by our build.

To fix this, your goals are:

1. Identify a p2 repository that contains the required bundle.
2. Identify an appropriate feature that includes the bundle.
3. Update the category.xml file to include that feature.

## Identifying an appropriate p2 repository as the source of a missing bundle

DDS4CCM already assembles plug-ins from the following p2 repositories:

- Eclipse Luna (4.4) release: `http://download.eclipse.org/releases/luna/`
- Eclipse CDT 8.6 release: `http://download.eclipse.org/tools/cdt/releases/8.6`

The repositories are encoded in `releng/com.zelgisoft.dds4ccm.configuration/pom.xml`.
If you need to change or add repositories, you do it in that POM file.

For the most part, you will find the missing bundle in the Luna repository.
If you are adding a completely new feature, you may have to add another repository.

If adding a new repository, be aware of its durability. Release repositories from Eclipse
a generally published forever. If you doubt the repository you are using will last that
long, consider copying it to the `deps` folder, and using a `file:` protocol in the POM file.
This is the case for the RSA 9.5 repository.

## Finding a feature contining the missing bundle

This requires some p2 wizard work. Much of what is found below is a summary of this
[Paul Webster StackOverflow article](https://stackoverflow.com/questions/10025599/how-to-find-out-which-feature-contains-a-needed-plug-in-on-an-eclipse-download-s).

Steps:

- Start RSA, or any modern Eclipse IDE.
- Open the Console view.
- From the Open Console tool button, choose 'Host OSGi Console'
- Type the following text to find the bundle number of the 'P2 Console':

	> ss p2.console

- You will receive an response such as:

	 id	State	Bundle

	 858	ACTIVE	org.eclipse.equinox.p2.console_1.0.300.v20131113-1212
- Start the bundle with the following command:

	> start 858
- Query the p2 repository for your missing bundle with the following command:

	> provlquery http://download.eclipse.org/releases/luna "select(parent | parent.properties['org.eclipse.equinox.p2.type.group'] == true && parent.requirements.exists(rc | everything.exists(iu | iu.id == 'org.eclipse.xtend.shared.ui' && iu ~= rc)))" true
- (Note you have to use your p2 repo URL (near the start) and your missing bundle id (near the end).
- The search can take several minutes. Get yourself a coffee. Eventually, the output will look like:

	org.eclipse.xpand.ui.feature.group 2.0.0.v201406030414
	org.eclipse.xtend.typesystem.emf.feature.group 2.0.0.v201406030414
	org.eclipse.xtend.typesystem.uml2.feature.group 2.0.0.v201406030414
	org.eclipse.xtend.typesystem.xsd.feature.group 2.0.0.v201406030414
	org.eclipse.xtend.ui.feature.group 2.0.0.v201406030414

- Use the dds4ccm.aggr file (with CBI Aggregator Editor and Engine installed) to browse your
source repository for the listed features. (They will not include the `.feature.group` suffix.)
- As you find a feature, expand its 'Requirements' subfolder, and ensure your bundle appears with
a full version number. If not, this feature will not aggregate your bundle.
- Choose the feature that aggregates your bundle version. Record it's id (again, without the `.feature.group` suffix), and its version.
- Edit category.xml to include new set of lines like the following:

	<feature
		url="features/org.eclipse.xtend.ui_2.0.0.v201406030414.jar"
		id="org.eclipse.xtend.ui"
		version="2.0.0.v201406030414">
		<category name="com.zelgisoft.dds4ccm.deps.category" />
	</feature>

- If you cannot find an acceptable feature (either, there is not, or the one you found is 'too big'), you can add a bundle definition to category.xml, instead:

	<bundle id="com.google.guava" version="15.0.0.v201403281430">
		<category name="com.zelgisoft.dds4ccm.deps.category"/>
	</bundle>

- Include the feature in the correct category (or categories), as specified by the `category-def` elements.
- Build dds4ccm again.
- Attempt to install it, again. Rinse and repeat until all your dependencies are resolved.

gha_language: Java


text:
# Automate AWS Lightsail Backups

Automate lightsail instance and database backups using these AWS Lambda functions:

- [backup_instance.js](https://github.com/Amit-A/automate-lightsail-backups/blob/master/backup_instance.js) for instance backups
- [backup_database.js](https://github.com/Amit-A/automate-lightsail-backups/blob/master/backup_database.js) for relational database backups

Make sure that you set the required environment variables:

- `INSTANCE_NAME` or `RELATIONAL_DATABASE_NAME`
- `BACKUP_DAYS_MAX`: keep the last `BACKUP_DAYS_MAX` daily backups
- `BACKUP_WEEKS_MAX`: keep at least `BACKUP_WEEKS_MAX` weekly backups
- `BACKUP_MONTHS_MAX`: keep at least `BACKUP_MONTHS_MAX` monthly backups
- `LIGHTSAIL_REGION`: the region where your lightsail resource is located (e.g. us-east-1)

## Setup

These are beginner-friendly instructions; if you know what you're doing feel free to skim :)

### Create new IAM policy: lightsail-snapshots

- Head over to the AWS [IAM console](https://console.aws.amazon.com/iam/)
- Find **Policies** in the sidebar and click on **Create Policy**
- Click on the **JSON** tab and paste this:

```json
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "lightsail:GetInstanceSnapshot",
                "lightsail:CreateRelationalDatabaseSnapshot",
                "lightsail:GetRelationalDatabaseSnapshot",
                "lightsail:DeleteInstanceSnapshot",
                "lightsail:GetRelationalDatabaseSnapshots",
                "lightsail:GetInstanceSnapshots",
                "lightsail:DeleteRelationalDatabaseSnapshot",
                "lightsail:CreateInstanceSnapshot"
            ],
            "Resource": "*"
        }
    ]
}
```

- Click **Review Policy**, and use the name **lightsail-snapshots**, and click **Create Policy**.

### Create IAM role: lightsail-snapshots-role

- In the [IAM console](https://console.aws.amazon.com/iam/), find **Roles** in the sidebar and click on **Create Role**
- Select **Lambda** in the services list and click **Next: Permissions**
- Use the search field to find and add **AWSLambdaBasicExecutionRole** and **lightsail-snapshots**
- Click **Next: Review**, use the name **lightsail-snapshots-role**, and click **Create Role**

### Create Lambda functions

We need to create a lambda function **for each instance and database** that we want to backup automatically:

- Head over to the [Lambda console](https://console.aws.amazon.com/lambda) and click **Create Function**
- Use the **Author from Scratch** option, give the function whatever name you want, use the Node.js 10.x runtime, select **Choose an existing role** > **lightsail-snapshots-role**, and click **Create Function**.
- In the designer section, click **Add trigger**, select **CloudWatch Events**, select **Create a new rule**, give the rule whatever name you want, enter **rate(1 day)** for the Schedule Expression, make sure Enable Trigger is selected, and click **Add**.
- In the function code section, open the index.js file, remove any existing code from this file, and paste the contents of [backup_instance.js](https://raw.githubusercontent.com/Amit-A/automate-lightsail-backups/master/backup_instance.js) to use this function for **instance backups** or [backup_database.js](https://raw.githubusercontent.com/Amit-A/automate-lightsail-backups/master/backup_database.js) for **database backups**.
- Add the required environment variables (see the comment at the top of backup_instance.js or backup_database.js)
- **Set the timeout** to 5 minutes, set reserve concurrency = 1, and click **Save**.

Tada! It's setup. Make sure that you test it.

## License

[Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0)

Copyright 2019 Amit-A

repository: Amit-A/automate-lightsail-backups

gha_language: JavaScript

repo_name: Amit-A/automate-lightsail-backups


text:
---
template: SinglePost
title: Driving under the Influence … of your meds!
status: Published
date: 2017-11-30
featuredImage: /images/animals.jpg
excerpt: It turns out many folks have no idea that their prescription
  medications make driving dangerous and put them at risk for a DUI arrest.
categories:
  - category: Safety
meta:
  title: Driving under the Influence … of your meds!
  description: It turns out many folks have no idea that their prescription
    medications make driving dangerous and put them at risk for a DUI arrest.
---
<!--StartFragment-->

It turns out many folks have no idea that their prescription medications make driving dangerous and put them at risk for a DUI arrest.

![](/images/pills.png)

A recent 2017 study looked at data from the 2013-2014 National Roadside Survey, in which drivers across America were asked about drug use, including prescription drugs. Almost 20 percent said they had recently taken a prescription medication and yet were unaware the mediation could affect their driving. Yet another 2015 study found that the prevalence of [drivers with prescription opioids in their systems at the time of death](/practice-areas/drunk-driving-accident-lawyer/) from a car accident surged from 1 percent in 1995 to 7.2 percent in 2015.

Opioids are a big risk when you are driving (around 35 percent of adult Americans were given a pain killer prescription by medical providers last year). So are other legitimately prescribed meds like antidepressants sedative hypnotics (including diazepam/ Valium and others), antihistamines (Benadryl), decongestants, sleeping pills and medical marijuana. They can compromise your reaction time.

So, read the warnings on medications and ask your doc about driving risks associated with medications and combination of medications so that you are not in a danger to yourself and others.

<!--EndFragment-->

repository: emmadigital/austinlaw

repo_name: emmadigital/austinlaw


text:
# Buffer Components

[![Build Status](https://travis-ci.org/bufferapp/buffer-components.svg?branch=master)](https://travis-ci.org/bufferapp/buffer-components)

A shared set of UI Components using React and CSS Modules.

Demo: https://bufferapp.github.io/buffer-components/

To use this in your project start at the [usage](#usage) section. If you'd like to add to this
library skip to [component development](#component-development).

## Usage

Install the package and save the exact version:

```sh
npm install @bufferapp/components -SE
```

Now in your code you can import a specific component:

```js
import Button from '@bufferapp/components/Button';
```

### Requirements

For the component library you're required to use a few plugins and a valid Webpack config.

First, you'll need React installed (0.14 or newer):

```sh
npm i react react-dom -SE
```

In addition to your Babel configuration (not documented), you'll need the style-loader Webpack plugin:

```sh
npm i style-loader -SDE
```

Your Webpack config should use the proper config, here is an example:

```js
module.exports = {
  module: {
    loaders: [
      {
        test: /\.css$/,
        loaders: [
          'style-loader',
        ],
      },
    ],
  },
};
```

## Component Development

- [Quick Start](#quick-start)
- [Test](#test)
- [Component Anatomy](#component-anatomy)
- [FAQ](#faq)

## Quick Start

Install Node Modules

```sh
npm i
```

Start React Storybook

```sh
npm start
```

Open http://localhost:9001

## Test

Run Linter And Test

```sh
npm run test
```

Run Test and watch for changes

```sh
npm run test-watch
```

Update Test Snapshots

```sh
npm run test-update
```

Note: only commit these if you have manually inspected them with a story

## Component Anatomy

```
src/ # root
+-- MyComponent/ # component root
  `-- index.js # component display logic
  `-- story.js # storybook entry
```

## Versioning

```
major.minor.patch
```

### Considered patch release

Can upgrade without changes to the codebase

- Add a component
- Add a new prop to a component

### Considered minor release

An upgrade would require a code change to work

- Remove a component
- Remove a prop

### Considered major release

- Major milestone achieved (i.e a complete set of components)
- Complete re-skinning of components
- Up for debate

## FAQ

**What is a component**

In the current implementation components are all [functional and stateless](https://medium.com/@housecor/react-stateless-functional-components-nine-wins-you-might-have-overlooked-997b0d933dbc#.ukhlhrqlw).

This means that UI is a function of state since we're using pure functions to build our views.

```
UI = f(state)
```

**How do I determine the scope of a component**

This is a tough question, it really depends. But as a general rule, a component should be simple enough to be reusable across multiple applications and be not much longer than 150 lines of code. This is a good one to seek advice if you're not sure.

**What's the development workflow look like?**

Note: this is *a way* to do this, but not necessarily *the way* to build components. For this workflow let's create a component called `NewComponent`.

1. Create a branch with the name of the new component

Note: also make sure you're up to date

```
git checkout master
git pull -r
git checkout -b task/add-newcomponent
```

2. Install dependencies and start the storybook

```
npm i && npm start
```

open http://localhost:9001 in your browser

3. Create a `NewComponent` folder under `src` (see [Component Anatomy](#component-anatomy))
```
src/
+-- NewComponent/
```

4. Create a story for the `NewComponent`

```
src/
+-- NewComponent/
 `-- story.js
```

populate **story.js** with a default story

```js
// story.js
import React from 'react';
import { storiesOf } from '@storybook/react';
import NewComponent from './index';

storiesOf('Card', module)
  .add('Default', () => (
    <NewComponent />
  ));
```

Now when you look at Storybook you should see a broken story (red screen)

5. Implement your component

```
src/
+-- NewComponent/
 `-- story.js
 `-- index.js
```

populate **index.js** with the new component

```js
import React from 'react';
import { calculateStyles } from '../lib/utils';

const NewComponent = ({ hovered }) =>
  <div
    style={calculateStyles({
      default:{
        background: 'green',
      },
      hovered: {
        background: 'red',
      }
    },{
      hovered, // key matches above style key and is activated when value is true
    })}
  >
    NewComponent
  </div>;

export default NewComponent;
```

6. Run the test for the first time

It's important to note that this creates a snapshot of the component. All tests ran in the future will be tested against this snapshot to ensure they haven't changed.

```sh
npm t
```

7. Commit it!

```sh
git add .
git commit -m "Add NewComponent"
git push -u origin task/add-newcomponent
```

At this point it's a good idea to generate a PR on github :)

**How do I write tests for a component?**

This automatically happens when you write stories. They are tested with jest snapshots under the hood.

Since components are [functional and<EMAIL_ADDRESS>we can use snapshot testing to get complete coverage.

You're verifying that each property change has the expected outcome in HTML.

The first time the test is run it generates a new snapshot. The **second** time it's checked against the snapshot.

There's a pattern you can follow

1. Look at the Component.propTypes section
  - This is essentially the API of the component
2. Look at the render function
3. Look at any helper functions
4. Ask one of the contributors :)

repository: bufferapp/buffer-components

repo_name: bufferapp/buffer-components


text:
## URL Service Application

**Application Description:**
  - This application uses a service that includes notifications using a broadcast receiver and asynchronously deletes saved files when requested by the user.
  - The user enters urls (in the main layout), selects a "Notify" checkbox (optional) and then selects the "Fetch Web Pages" button (which will launch the second activity). Only if the "Notify" checkbox is selected, a notification will be sent through the broadcast receiver.
  - The second activity will display the url pages in a webview. The urls will be displayed in a spinner and when the user selects one url, it will display the website in the webview.
  - If the user selects the "Clear" button within the second activity, it will asynchronously delete all the urls and clear the webview.
  -	**Technologies:** Android Studio, Java.

[Link to Repository](https://github.com/ryanhuber65/android-URLservice)


text:
# V1NUMA

## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**guest_mapping_passthrough** | [**V1NUMAGuestMappingPassthrough**](V1NUMAGuestMappingPassthrough.md) | GuestMappingPassthrough will create an efficient guest topology based on host CPUs exclusively assigned to a pod. The created topology ensures that memory and CPUs on the virtual numa nodes never cross boundaries of host numa nodes. | [optional]

[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

repository: kubevirt/client-python

repo_name: kubevirt/client-python


text:
# locust-scripts

This repository is intended as a dumping ground for Locust test plans. Each
test plan subdirectory should contain a ```README.md``` explaining the test
plan and how it works.

### Setup

Each test plan will need to have [locustio] installed.

[locustio]:http://docs.locust.io/en/latest/installation.html

repository: lbragstad/locust-scripts

repo_name: lbragstad/locust-scripts


text:
# OpenStack Heat for SDC
Uses: sdcadmin (https://github.com/icclab/sdcadmin) package

## Step 1 - Create KVM-VM for OpenStack Services
Create a KVM-VM with the following Parameters:

* Owner: admin (the owner of the admin network)
* 4GB Ram, 2 CPU, 2000 LWPs, 40 GB Disk (create a Package if necessary)
* centos-7 Image (20141202, b1df4936-7a5c-11e4-98ed-dfe1fa3a813a)
* Primary NIC to network with internet-access (Public)
* Secondary NIC to admin network

## Step 2 - Installing Packstack
SSH as root into the machine once provisioned. Make sure networking is working (in my setup the default gateway was missing), then run:

```
yum update -y
yum install -y https://repos.fedorapeople.org/repos/openstack/openstack-kilo/rdo-release-kilo-1.noarch.rpm
yum install -y openstack-packstack
```

## Step 3 - Install OpenStack Components
Generate a new answer file:

```
packstack --gen-answer-file=/root/packstack-answers
```

Modify the following lines:

```
CONFIG_GLANCE_INSTALL=n
CONFIG_CINDER_INSTALL=n
CONFIG_NOVA_INSTALL=n
CONFIG_NEUTRON_INSTALL=n
CONFIG_HORIZON_INSTALL=n
CONFIG_SWIFT_INSTALL=n
CONFIG_CEILOMETER_INSTALL=n
CONFIG_HEAT_INSTALL=y
CONFIG_NAGIOS_INSTALL=n
CONFIG_CINDER_VOLUMES_CREATE=n
CONFIG_PROVISION_DEMO=n
```

Run packstack with the modified file:

```
packstack --answer-file=/root/packstack-answers

```
This may take a while, consider having a coffee ;-)

## Step 4 - Verify OpenStack Components
Source the Creds file at ```/root/keystonerc_admin``` and run a couple of keystone and heat commands:

```
$ keystone user-list
$ heat stack-list
```

## Step 5 - Install sdcadmin library & Heat plugin
Install sdcadmin package:

```
pip install sdcadmin
```

Copy the heat plugin to /usr/lib/heat

```
mkdir -p /usr/lib/heat
cp PATH/TO/sdc_plugin.py /usr/lib/heat/sdc_plugin.py
```

Let Heat know where to look for plugins by uncommenting the ```plugin_dirs``` line in ```/etc/heat/heat.conf```

Then restart the heat engine service:

```
service openstack-heat-engine restart
```

Run ```heat resource-type-list```, verify that ```SDC::Compute::KVM``` and ```SDC::Compute::SmartMachine``` show up.

## Step 6
Setup is complete, you now can start stacks with those resources. Example heat-templates are included in this repo.

# Licence

```
# Copyright 2015 Zuercher Hochschule fuer Angewandte Wissenschaften
# All Rights Reserved.
#
#    Licensed under the Apache License, Version 2.0 (the "License"); you may
#    not use this file except in compliance with the License. You may obtain
#    a copy of the License at
#
#         http://www.apache.org/licenses/LICENSE-2.0
#
#    Unless required by applicable law or agreed to in writing, software
#    distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
#    WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
#    License for the specific language governing permissions and limitations
#    under the License.
```

repository: icclab/sdc-heat

repo_name: icclab/sdc-heat


text:
# AdapterBase

## Background

Adapters are short sequences that are attached to cDNA templates during preparation of next generation sequencing (NGS) libraries. Depending on the preparation of the NGS library and how it is sequenced, the raw NGS data may be contaminated with the adapter sequences. See [Didion et al. 2017](https://peerj.com/preprints/2452/) for more details.

Adapter trimming is a critical component of NGS data preprocessing. To trim adapters appropriately, it is necessary to know the sequences of the adapters that were used. However, adapter sequences are poorly documented and often are not included in the metadata of public database submissions ([SRA](http://www.ncbi.nlm.nih.gov/sra), [ENA](http://www.ebi.ac.uk/ena), and [DDBJ](http://www.ddbj.nig.ac.jp)).

### Target Users

**fill in here**

## System Design

AdapterBase is implemented in SQLite3 and Django with the primary API implemented in REST. Lists of kits and adapter sequences have been extracted from [Illumina's documentation](https://support.illumina.com/content/dam/illumina-support/documents/documentation/chemistry_documentation/experiment-design/illumina-adapter-sequences_1000000002694-01.pdf). An initial list of runs is being populated by automatic detection of adapters using [Atropos](https://github.com/jdidion/atropos). (**Do we need more here??**)

![AdapterBase schema](assets/SystemDesign.png)

## Usage

Currently, AdapterBase can be accessed from the Hackathon AWS instance by mapping port 80 back to the local host. A permanent, publically facing home will be determined later.  **COMPLETE THIS SECTION**

### Local installation

If you want to spin up a local copy of AdapterBase: (**Replace with code/vignette!**)
1. Make sure python3 is installed
2. Clone or download this git repository
3. Create and enter a virtual environemnt
4. Run buildoadb.sh
5. Create a superuser for the database
6. Start the server by runnin startoadb.sha

### Web interface vignettes

#### Get adapter sequences used by a run from the accession number

#### Deposit adapter information for a run

#### Adding new kits and/or adapter sequences

### Using the Commandline API

### Using Python bindings

## Remaining Goals

1. Complete implementation of website/API
2. Pre-populate Run database from SRA using Atropos
3. Find a home for web implementation and build Docker image
4. User group implementation and security features

### Stretch goals/post-hackathon

5. Continue building out run database with manual curation of SRA datasets
6. Integrate the AdpaterBase API into Atropos

## Project Team

AdapterBase was intitially developed as part of an NCBI-sponsored hackathon at the National Library of Medicine, August 14-16th, 2017.
- John P Didion (project lead), NHGRI/NIH<EMAIL_ADDRESS>- Dan Davis, Systems/Applications Architect, OCCS/AB, NLM, NIH<EMAIL_ADDRESS>- Scott Lewis, Pulmonary Critical Care Medicine, Washington University in St. Louis<EMAIL_ADDRESS>- Chaim A Schramm, Vaccine Research Center, NIAID, NIH<EMAIL_ADDRESS>- Vamsi Vungutur OCCS/AB NLM, NIH<EMAIL_ADDRESS>

repository: alexeyrakov/OnlineAdapterDatabase

repo_name: alexeyrakov/OnlineAdapterDatabase