text:
---
id: 176
title: 'Download The Boss Baby (2017) Dual Audio {Hindi-English} 480p [300MB] || 720p [1GB] || 1080p [2.8GB]'
date: 2020-10-15T14:16:44+00:00
author: admin
layout: post
guid: https://themoviesflix.co/?p=13617
permalink: /2020/10/15/download-the-boss-baby-2017-dual-audio-hindi-english-480p-300mb-720p-1gb-1080p-2-8gb/
tdc_dirty_content:
  - "1"
tdc_icon_fonts:
  - 'a:0:{}'
cyberseo_rss_source:
  - https://themoviesflix.co/feed/?paged=15
cyberseo_post_link:
  - https://themoviesflix.co/download-the-boss-baby-2017-hindi-english-480p-720p-1080p/
categories:
  - Uncategorized
---
✅ Download The Boss Baby Movie 2017 Dual Audio (Hindi-English) 720p & 480p & 1080p. This is a dual audio movie and available in 720p & 480p qualities. This movie is based on  **Animation, Action**, **Adventure**. This movie is available in Hindi Dual Audio. Click on the Download button below to download this movie.

**TheMoviesFlix.co** is The Best Website/Platform For Hollywood HD Movies. We Provide Direct Google Drive Download Links For Fast And Secure Downloading. Just Click On Download Button _And Follow Steps To Download And Watch Movies Online For Free_.

    <img class="imdbwp__img"<EMAIL_ADDRESS>/>

      The Boss Baby (2017)

      6.3Rating: 6.3 / 10 from 106,421 users

      A suit-wearing, briefcase-carrying baby pairs up with his 7-year old brother to stop the dastardly plot of the CEO of Puppy Co.

### Download The Boss Baby Hindi Dubbed 720p & 480p & 1080p~ **TheMoviesFlix.co** {.has-text-align-center.has-text-color}

###  Movie Info:  {.has-text-color}

  * **Full Name: **The Boss Baby
  * **Language:** Dual Audio (Hindi-English)
  * **Released Year: **2017
  * **Size:** 300MB & 1GB & 2.8GB
  * **Quality:** 480p & 720p & 1080p Bluray
  * **Format:** Mkv

### Storyline: {.has-text-color}

Seven year old Tim Templeton has the best life ever. With his kind parents all to himself and his big imagination Tim has a hard time thinking about anything better! But when his new little brother comes along, he is getting less and less attention. Then, one night Tim hears a voice coming from inside his brother’s bedroom and discovers something incredibly creepy… his newborn brother can TALK! The two go through a lot together and start to find brotherly love that definitely wasn’t there when they met! After fights and fun, hurtful words and kind actions, the two become the best of friends and they fight side by side to solve a big puppy problem and save their trapped parents.

### ScreenShots: {.has-text-color}

  Download The Boss Baby (2017) Dual Audio (Hindi-English) 480p [300MB]

Download Links

  Download The Boss Baby (2017) Dual Audio (Hindi-English) 720p [1GB]

Download Links

  Download The Boss Baby (2017) Dual Audio {Hindi-English} 1080p [2.8GB]

Download Links

  <button class="button button5">Join Our Telegram</button> <button class="button button5">Announcements</button> <button class="button button5">How To Download?</button> <button class="button button5">Report Broken Links</button>

  Please Do Not Use VPN for Downloading Movies From Our Site.

  Click On The Above Download Button Download File.

  If You Find Any Broken Link Then Report To Us.

  Comment Your Queries And Requests Below In The Comment Box.


text:
The data of the content to be created or updated.

Please note that each field is an object with one entry per language.
If the field is not localizable you must use `iv` (invariant language) as a key.

Read more about it at: https://docs.squidex.io/04-guides/02-api.html

license: MIT

repository: oguzhankahyaoglu/squidex

branch_name: refs/heads/master

extension: md

gha_language: C#

gha_license_id: MIT

license_type: permissive

repo_name: oguzhankahyaoglu/squidex


text:
# Enable

[Enable](https://www.enable.credit) is a “Kiva for Dai” that allows lenders to make peer-to-peer stablecoin microloans to emerging market borrowers. Our first product is a [peer-to-peer crowdloan kit](https://github.com/enabledao/enable/blob/master/product/specs/2019-07-14-v0.1-specs-(ines)/v0.1-specs.md).

We are an open source volunteer project that grew out of the [open finance hackathon](https://www.buildandship.it/) in May 2019. We are currently funded by a [3-month grant](https://twitter.com/onggunhao/status/1148140687327555584) from [Binance Labs](https://labs.binance.com/).

This repo is mainly for project management and product-related discussions. See our workstreams for development work.

**Mailing List**: https://www.enable.credit

### Team

* Thomas Spofford, [@tspoff](https://github.com/tspoff) (USA)
* Anthony Adegbemi, [@adibas03](https://github.com/adibas03) (Nigeria)
* Faisal Amir, [@urmauur](https://github.com/urmauur) (Indonesia)
* Daniel Onggunhao, [@onggunhao](https://github.com/onggunhao) (Singapore)

## Workstreams

In line with the open source ethos of decentralized finance, we are committed to building in public. See the contributor instructions in the individual repos.

| Workstream                 | Github                                                    | Contributor Instructions                                          |
| -------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------- |
| Enable Crowdloan Contracts | [repo](https://www.github.com/enabledao/enable-contracts) | [instructions](https://www.github.com/enabledao/enable-contracts) |
| Enable Crowdloan UI        | [repo](https://www.github.com/enabledao/enable-ui)        | [instructions](https://www.github.com/enabledao/enable-ui)        |
| Proof-of-concept fundraise | [Ines Fund](https://www.ines.fund)                        |                                                                   |

## Roadmap

### Phase 1 (June - Aug 2019)
* [Single-loan peer-to-peer crowdloan kit](https://github.com/enabledao/enable/blob/master/product/specs/2019-07-14-v0.1-specs-(ines)/v0.1-specs.md)
* [Proof-of-concept fundraise](https://www.ines.fund): raising 60,000 Dai for Ines (Indonesia) to attend Cornell University

### Phase 2

* Open to ideas - debt tokens, collateralized loans, interest rate auctions, social credit

# About Enable

[![image](https://user-images.githubusercontent.com/518024/56973331-35e9d600-6b9f-11e9-8e41-b88185cfdea7.png)](https://youtu.be/Xqu4cmHzTis?t=3289)

## Value add

Enable makes use of [smart contracts](https://blockgeeks.com/guides/smart-contracts/) and [stablecoins](https://en.wikipedia.org/wiki/Stablecoin) to automate the operations required to do a cross-border peer-to-peer loan.

|                    | Status Quo                                                                                | Enable Loan Contracts                              |
| ------------------ | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Cross-border Costs | Incurs forex, transfer and bank fees as it goes through the cross-border banking system                        | **$0**, uses stablecoins                           |
| Accounting Effort  | Team of diligent accountants required to manage fractional loan ownership and allocation of repayments streams | **0 headcount**, automated through smart contracts |
| Transparency       | Loan repayment data is usually opaque or subject to time delays                                                | **Fully transparent ledger**                       |
| Composability      | Investment bankers, auditors, legal contracts required to package it into derivatives (e.g. bonds, CLOs)       | **Fully programmable smart contract**              |

## Future Directions

* Debt Tokens
* Marketplace
* Collateralized loans: identity-collateralized loans
* Sophisticated loan types: PMT
* Sophisticated payment tracking
* interest rate auctions
* Derivative products (e.g. collateralized loan obligations) to try to create investment-grade products

repository: PreciousTosin/enable

repo_name: PreciousTosin/enable


text:
[![CircleCI](https://circleci.com/gh/versioneye/versioneye.svg?style=svg)](https://circleci.com/gh/versioneye/versioneye)
[![Dependency Status](https://www.versioneye.com/user/projects/596388a7368b08005360289c/badge.svg?style=flat-square)](https://www.versioneye.com/user/projects/596388a7368b08005360289c)

# VersionEye

This is the source code for the web application [VersionEye](https://www.versioneye.com).

## Start the backend services for VersionEye

This project contains a [docker-compose.yml](docker-compose.yml) file which describes the backend services
of VersionEye. You can start the backend services like this:

```
docker-compose up -d
```

That will start:

 - MongoDB
 - RabbitMQ
 - ElasticSearch
 - Memcached

For persistence you should comment in and adjust the mount volumes in [docker-compose.yml](docker-compose.yml)
for MongoDB and ElasticSearch. If you are not interested in persisting the data on your host you can
let it untouched.

Shutting down the backend services works like this:

```
docker-compose down
```

## Configuration

All important configuration values are read from environment variable. Before you start
VersioneyeCore.new you should adjust the values in [script/set_vars_for_dev.sh](script/set_vars_for_dev.sh)
and load them like this:

```
source ./script/set_vars_for_dev.sh
```

The most important env. variables are the ones for the backend services, which point to MongoDB, ElasticSearch,
RabbitMQ and Memcached.

## Install dependencies

If the backend services are all up and running and the environment variables are set correctly
you can install the dependencies with `bundler`. If `bundler` is not installed on your machine
run this command to install it:

```
gem install bundler
```

Then you can install the dependencies like this:

```
bundle install
```

## Rails Server

If the dependencies are installed correctly you can start the Rails server like this:

```
rails s
```

Now the application should be available at `http://localhost:3000`.

## Amazon S3

You can use the fake-s3 GEM to simulate S3 offline: <https://github.com/jubos/fake-s3>.
You can start the fake-s3 service like this:

```
fakes3 -r /tmp -p 4567
```

## React.JS

Some parts of VersionEye are implemented in ReactJS.
For autocompiling the JSX files in ReactJS use the `jsx` node package.

```
jsx --watch src/ build/
```

`jsx` can be installed via NPM with this command:

```
sudo npm install -g react-tools
```

## Tests

The tests for this project are running after each `git push` on [CircleCI](https://circleci.com/gh/versioneye/versioneye)!
For more details take a look to the [circle.yml](circle.yml) file in the root directory!

If the Docker containers for the backend services are running locally, the tests can be executed locally
with this command:

```
./script/runtests_local.sh
```

Make sure that you followed the steps in the configuration section, before you run the tests!

## Support

For commercial support send a message to<EMAIL_ADDRESS>
## License

VersionEye-Core is licensed under the MIT license!

Copyright (c) 2016 VersionEye GmbH

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

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

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

repository: versioneye/versioneye

branch_name: refs/heads/develop

gha_language: JavaScript

repo_name: versioneye/versioneye


text:
---
title: A Clockwork Orange
playwright: Anthony Burgess
season: In House
season_sort: 240
period: Spring
venue: New Theatre
date_start: 2013-03-19
date_end: 2013-03-22

cast:
  - role: Alex
    name: Richard Hill
  - role: Georgie
    name: Nick Slater
  - role: Dim
    name: Phil Damms
  - role: Pete
    name: Sam Peake
  - role: F.
    name: Tom Selves
  - role: Dr. Brodsky
    name: Tom Sheldon
  - role: Chaplain
    name: Eoin Buckley
  - role: Deltoid
    name: Andrew Sambell
  - role: The
    name: Josh Blake
  - role: Dr. Branom
    name: Lucy Dollman

crew:
  - role: Director
    name: Nadia Amico
  - role: Director
    name: Alex Mawby
  - role: Producer
    name: Laura Gallop
  - role: Lighting Designer
    name: Lydia Scott
  - role: Technical Director
    name: Joseph Heil
  - role: Technical Operator
    name: Page Phillips Harrington
  - role: Set Designer
    name: Natasha Mortimer
  - role: Stage Manager
    name: Liz Cornwell
  - role: Video Technician
    name: Will Pimblett
  - role: Graphic Designer
    name: Harry Bradley

assets:
  - type: poster
    image: rCCdDhq
  - type: programme
    title: Cast and Crew List
    filename: clockwork-cast-crew-list.pdf

links:
  - type: Review
    href: https://impactnottingham.com/2013/03/clockwork-orange-nottingham-new-theatre/
    snapshot: b0tWe
    publisher: Impact Nottingham
    author: Hyeran Kim
    title: "Clockwork Orange @ Nottingham New Theatre"
    date: 2013-03-21
    quote: "If you are a fan of the original novel or film, do not expect a dramatic retelling, instead imagine it with a shot of youth and screwball animation."

prod_shots: LXKVTq

---

Fifteen-year-old Alex doesn’t just like ultra-violence – he also enjoys drugs and Beethoven. He and his gang rampage through a dystopian future, hunting for terrible thrills. But when Alex finds himself at the mercy of the state and subjected to the ministries of Dr Brodsky, he discovers that fun is no longer the order of the day…

repository: newtheatre/history-project

gha_language: HTML

repo_name: newtheatre/history-project


text:
# HungarianBPMex: Pairwise Matching through Max-Weight Bipartite Belief Propagation

### Introduction

This repository contains the source code of the algorithm described in a [CVPR 2016](http://www.pamitc.org/cvpr16/) paper [Pairwise Matching through Max-Weight Bipartite Belief Propagation](http://zzhang.org/ZhangEtal2016Cvpr.pdf). Note that this project only contains the relaxation solver. For the whole framework, please go to [HungarianBP](https://github.com/zzhang1987/HungarianBP).

### Citing HungarianBPMex:
If you find HungarianBPMex useful in your research, please consider citing:

    @inproceedings{Zhang:2016:CVPR,
        author = {Zhang, Zhen and Shi, Qinfeng and McAuley, Julian and Wei, Wei and Zhang, Yanning and Hengel, Anton},
        booktitle = {CVPR},
        title = {Pairwise Matching through {Max-Weight} Bipartite Belief Propagation},
        year = {2016},
    }

### Usage
0. **Prerequisites**
 0. [Boost] (http://www.boost.org/): Install the boost library via apt-get, yum, or compiling from scratch.

### Feedback

If you have any issues (question, feedback) or find bugs in the code, please contact<EMAIL_ADDRESS>

repository: antonmil/m-best

repo_name: antonmil/m-best


text:
# Struct vs class

## Struct and class

```
// Small passive objects that carry public date and have no or few basic member functions
// Data container
struct Person_t
{
	std::string name; // public
	unsigned age;
}

// Bigger active objects that carry private data, interfacced through public member functions
// Complex data structure
class Person
{
	std::string name_; // private
	unsigned age_; // m_age, _age
}
```

## Object-oriented programming

```
class Person
{
	std::string name_; // private
	unsigned age_;
public:
	unsigned age() const { return age_; }      // getter or accessor
	void set_age(unsigned age) { age_ = age; } // settor or mutator
};
```

## Too many setter or getter functions indicate problems in design


text:
# jumpgate
[![Build Status](https://drone.element-43.com/api/badges/EVE-Tools/jumpgate/status.svg)](https://drone.element-43.com/EVE-Tools/jumpgate) [![Go Report Card](https://goreportcard.com/badge/github.com/EVE-Tools/jumpgate)](https://goreportcard.com/report/github.com/EVE-Tools/jumpgate) [![Docker Image](https://images.microbadger.com/badges/image/evetools/jumpgate.svg)](https://microbadger.com/images/evetools/jumpgate)

This service for [Element43](https://element-43.com) is based on [grpc-gateway](https://github.com/grpc-ecosystem/grpc-gateway) and translates requests between HTTP and gRPC.

Issues can be filed [here](https://github.com/EVE-Tools/element43). Pull requests can be made in this repo.

## Installation
Either use the prebuilt Docker images and pass the appropriate env vars (see below), or:

* Install Go, clone this repo into your gopath
* Run `go get ./...` to fetch the service's dependencies
* Run `bash generateProto.sh` to generate the necessary gRPC-related code
* Run `go build` to build the service
* Run `./jumpgate` to start the service

## Deployment Info
Builds and releases are handled by Drone.

Environment Variable | Default | Description
--- | --- | ---
LOG_LEVEL | info | The service's log level
LISTEN_HOST | :8000 | The host/port jumpgate will listen on
ESI_MARKETS_HOST | esi-markets.element43.svc.cluster.local:43000 | Location of the ESI markets service
MARKET_STATS_HOST | market-stats.element43.svc.cluster.local:43000 | Location of the market statistics service
STATIC_DATA_HOST | static-data.element43.svc.cluster.local:43000 | Location of the static data service
TOP_STATIONS_HOST | top-stations.element43.svc.cluster.local:43000 | Location of the top stations service

repository: AdlinFisherAbellBall/jumpgate

repo_name: AdlinFisherAbellBall/jumpgate


text:
classes
=> CLI - interact with user (input & user)

=> Scraper - class will scrap information from (dogtime.com) dog breed website to pull informartion/necessary data required

=>DogBreed : class to hold info on dog breeds and assign attributes/ properties to all the dogs that get instantiated .

All classes will have relationship, collaborate and interact with each other .

repository: olagoroye/CLI-PROJECT

repo_name: olagoroye/CLI-PROJECT


text:
# how [![stability][0]][1]
[![build status][4]][5] [![test coverage][6]][7]

`how(1)` - learn how to do anything. [Unix is not discoverable][8], so we need
to fix that.
```txt
Last login: Wed Nov 4 19:05:55 on ttys000
Type 'how start' to get started.
❯
```

## Installation
```sh
$ git clone https://github.com/yoshuawuyts/how
```

## Usage
```txt
how(1) - learn how to do anything

Usage: how [options] <keyword>

Options:
  -h, --help        Output usage information
  -v, --version     Output version number

Examples:
  $ how start          # learn how to get started
  $ how unix           # get an explanation of how unix works
  $ how programming    # learn how to program

Docs: https://github.com/yoshuawuyts/how
Bugs: https://github.com/yoshuawuyts/how/issues
```

## License
[MIT](https://tldrlegal.com/license/mit-license)

[0]: https://img.shields.io/badge/stability-experimental-orange.svg?style=flat-square
[1]: https://nodejs.org/api/documentation.html#documentation_stability_index
[4]: https://img.shields.io/travis/yoshuawuyts/how/master.svg?style=flat-square
[5]: https://travis-ci.org/yoshuawuyts/how
[6]: https://img.shields.io/codecov/c/github/yoshuawuyts/how/master.svg?style=flat-square
[7]: https://codecov.io/github/yoshuawuyts/how
[8]: https://medium.com/@yoshuawuyts/unix-is-not-discoverable-8b64c02a33ef

repository: yoshuawuyts/how

repo_name: yoshuawuyts/how


text:
# Depression-Analysis

## System designs

![proposed model](https://github.com/Thehunk1206/Depression-Analysis/blob/master/Sytem%20Designs/BEproject_proposed.png)

![module 1](https://github.com/Thehunk1206/Depression-Analysis/blob/master/Sytem%20Designs/Module%201.png)

![module 2 and 3](https://github.com/Thehunk1206/Depression-Analysis/blob/master/Sytem%20Designs/moduel2%20and%203.png)

* The log file is in csv format. It is then uploaded to our [webapp](https://depression-analyser.herokuapp.com/) to visualize the collected data. The webapp is developed using [streamlit](https://www.streamlit.io/)

## screenshot of WebApp

![screenshot1](https://github.com/Thehunk1206/Depression-Analysis/blob/master/Sytem%20Designs/webapp2.png)
![screenshot2](https://github.com/Thehunk1206/Depression-Analysis/blob/master/Sytem%20Designs/webapp3.png)


text:
# scoop-science

A "science" bucket for [Scoop](http://scoop.sh), containing software commonly used for scientific analysis that doesn't fit the [criteria](https://github.com/lukesampson/scoop/wiki/Criteria-for-including-apps-in-the-main-bucket) for inclusion in Scoop's [main bucket](https://github.com/ScoopInstaller/Main).

To make it easier to install apps from this bucket, run:

    scoop bucket add science https://github.com/mhowison/scoop-science.git

license: Unlicense

repository: mhowison/scoop-science

branch_name: refs/heads/main

repo_name: mhowison/scoop-science


text:
# <%= appName %>

**@TODO: Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.**

### Motivation

**@TODO: A short description of the motivation behind the creation and maintenance of the project. This should explain why the project exists.**

### Installation

**@TODO: Provide code examples and explanations of how to get the project.**

### Usage

**@TODO: Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.**

### Contributing

See [CONTRIBUTING.md](../master/CONTRIBUTING.md)

### History

**@TODO: Write history**

### Common Tasks

* **gulp help**: get an overview of what tasks are available
* **gulp test**: run the tests
* **gulp doc**: generate the docs. They will be placed in the `docs/` folder
* **gulp todo**: display all todos and fixmes in the project. It also writes them to TODO.md and todo.json

**@TODO: List the other tasks specific to this module**

repository: luma/generator-tok

repo_name: luma/generator-tok


text:
---
layout: post
title: Breaking Games for Balance 2
---

Welcome back to this multi-part series on breaking games to balance them! In our last post, we discussed some of the symptoms of a broken game, and now we're going to begin trying to discover those problems in the free print-and-play game [Forsaken Gods](https://docs.google.com/document/d/1--_soZprsUVg0Ruc9d_Q3tjEz4k5XSdHwVawHCcgVAY/edit). I will take you through my process for finding broken games, one that is by no assurances the best one, but the one that makes the most sense to me.

## Mechanics
The first thing to look for is any mechanics that *feel* broken to me. This isn't to say that they are broken, but these are the first things I want to test out to find out if they *are* broken. I'll go through the evergreen mechanics listed in the rules book below and give my thoughts on each of them.

|Mechanic|Thoughts|
|---|---|
|Bow|Effectively just tapping. This seems so basic that it would be impossible to break. If something allows you to un-bow followers, then this might be worth looking into, but for now it seems to be just a part of the game functioning.|
|Arrival|An enter the battlefield trigger. These can be useful, but don't jump out as broken. They happen once and would require synergy to break.|
|Devotion|An interesting mechanic that would make some cards become more useful in a long game. This one has some promise to be broken.|
|Onslaught|This one is more difficult to evaluate. At a cursory glance, it seems like the best strategy would be to focus all of your efforts on two lanes and abandon the third, but we will see if this is the case. If it isn't, then onslaught could be very powerful.|
|Solitary|Probably bad. This effect would need to be quite powerful, or be in a spells matter deck for me to actually place any real value in this.|
|Masochist|Now this one is intriguing. With the power to heal a follower every turn, this one might be able to be relatively easily abused with a small setup. This is definitely something to look at carefully.|
|Urgency|Haste. Could be broken, probably not though. Also not exciting.|
|Breach|This is by far the mechanic I like the most so far. It rewards you for doing what you want to do anyways. This seems like an easily abusable mechanic.|
|Opposing Lane|A definition. Nothing to see here.|
|Vengeance|An interesting catch up mechanic. It might enable some all in strategies where you focus on two lanes and hope to lose the third. Definitely worth messing around with.|
|God Costs|Being able to summon these gods seems to be very costly. If they have powerful effects it might be worth it, but we'll see.|
|Swarm|I have no idea how to value this. It is costly to set up, but has the power to help you get further ahead in that lane. Again, a mechanic we need to see specific cards to evaluate.|
|Dreamcatcher|A defensive ability. May or may not be necessary depending on how good Ethereal is.|
|Gatecrash|Here it is! Another mechanic that feels like it could be absolutely busted!|
|Ethereal|Evasion, always a solid mechanic.|
|Teleport|This is an interesting mechanic, but I don't forsee it being super powerful.|
|Switch|Better teleport?|
|Abandon|This one has promise. With such a downside, they would need to be somewhat powerful to compensate, so they could be useful, especially paired with Onslaught.|
|Bounce|Good with Arrival and Urgency.|
|Drain|Good, solid value. If drain is too powerful it will run away with the meta.|
|Toxic|Deathtouch, Poison, etc. If this has strong toughness, this will be powerful, but otherwise it seems meh|
|Dying Breath|Similar to Arrival, just happens when things change zones, not super broken on the surface.|
|The Void|As we discussed previoulsy, if there are ways to interact with this discard zone, it will be very powerful.|
|Provoke|I like this as a defensive ability that still allows for aggressive play. It could be broken.|
|Shield|Ehh? Like okay? It enables two-for-ones, which are value. I'll be interested if there are other things that interact with it outside of it being simply a combat ability.|
|Sacrifice|A definition|
|Damage|A definition|
|Destroy|A definition|
|+1/+1 Counter|A definition|
|Leader|Here's another good mechanic! This one seems like it could easily slot in with some of the other mechanics we've been excited about. It seems to reward you for doing what you want to do anyways.|
|Honorbound|A defensive ability that seems to be limited. It might disrupt your opponents plans, but I don't hold my breath with this one.|
|Heal|A definition|
|Defend|Now here's another exciting one. This allows you to ignore the lanes within the game. Another mechanic that might be able to be easily exploited. We shall see.|
|Collective|STORM!!!!!!!!!!!!!!!!|
|Gain Control|A definition, but it makes an interesting not. If you would gain control of a creature, but don't have space, it simply dies. This might mean that instead of removal you only need to try to gain control of followers. This might be genuinely broken.|
|Possession Card|Static effects can always be interesting to look at, so this could run away quickly if there is no way to interact with them.|
|Follower|A definition|
|Forbid|I think this is a counter spell, but the game says nothing about playing cards on your opponents turn. This might be confusing.|
|God|Having to pay this cost three times if you have all your lines but only once if you only have one lane makes this feel like an interesting catch up mechanic.|
|God Power|These are cool! Basically hearthstone's hero powers, and we're gonna review these next.|
|Shrine|The basic resource of the game. I really like the way they're set up, and I don't immediately see a way to break them.|
|Temple|Transform shrines into wild cards, now these feel like they allow you to run a couple out of color cards that could be broken. I'm more apprehensive about temples.|

Phew, that was a whole lot of mechanics! But at the end of it, we have nine mechanics that I think have the ability to be easily broken, so we'll focus our early testing on them! They are:
* Gatecrash
* Breach
* Abandon
* Vengeance
* Onslaught
* Provoke
* Leader
* Defend
* Collective

## God Powers
These god powers, in addition to the shrine system, are my two favorite parts of this game, so let's look at them next. These god powers allow you to take repeated actions every turn with only a two shrine commitment.

Strife: Deal 1 damage to any target in this lane - *Unlike the drain ability of Contagion, this allows you to burn down lanes. It can give you some inevitability in the late game, but seems like it may be too little to affect the game state in that way. In regards to removing followers, Contagion's ability is simply better at that.*

Infestation: Create a 1/1 Insect in this lane - *The value of tokens in this game will depend largely on how easy it is to get followers into lanes, if there are useful anthem effects, or if there are benefits to having large numbers of tokens/followers.*

Grandeur: Heal any target in this lane for 2 - *This seems quite good, and I really like it thematically. However, life gain strategies are often unviable in card games. If it is too easy to gain life, then everyone does it and you get into a virtual arms race of life points. If it is too difficult, those resources would be better spent in simply removing the other play/the sources of damage. The power of this ability will depend on the synergies available with life gain.*

Contagion: Drain any follower in this lane for 1 - *This is my second favorite god power of all. It combines affecting the board state with gaining life, and doing damage. All of this combines to make it my favorite ability for use in lane.*

Occult: Draw a card and then discard a card - *Yeah this is busted. Looting effects are so good, and I anticipate this being the best by far. In addition, since you have only one hand, this mechanically affects the entire game instead of just a single lane, making it even better on face examination. I anticipate that one of the first things you will do in any game  is build a lane where you have two blue shrines on turn two.*

So if you can't tell, I think one of these abilities is far and above better than the others. Card advantage is everything in card games, and a looting effect is one of the strongest things that you can do.

**Footnote: This is called a looting effect because it comes from the MtG card, Faithless Looting. It lets you draw two cards and then discard two, and it is very powerful. Since Magic is such a dominant game in the trading card game market, I use the term since many players will already have this as a base framework for their evaluation of cards.**

## Cards
Now, time for the bread and butter of any card game! The cards themselves. Now, there's 40 pages of creatures, each page with like 8 creatures spoiled, so I'll link to the full spoiler [here](https://docs.google.com/document/d/1--_soZprsUVg0Ruc9d_Q3tjEz4k5XSdHwVawHCcgVAY/edit) and just talk about the highlights in this part of the article. Additionally, unless there is something truly unique about the card, I'll only name them in the buckets where they are most valuable. So here goes, organized by God (color):

### Strife

Thoughts: Strife seems to be decent in its ability to deal damage to opposing followers, and it could be a very good splash color or closing color in order to keep your opponent at bay. It doesn't feel too fast despite the multiple urgency cards.

|Bucket|Cards|
|---|---|
|Value|Temple Runner; Vengeful Barbarian; Combat Reveler; War Celebrant|
|Closers|Disciple of Strife; Flame Rider; Strife, Lord of War; War Incarnate|
|Removal|Incinerate; Ignite; Scald|
|Card Advantage|Flaming Arrows; Blinding Blaze|

### Infestation

Thoughts: Infestation seems to go ultra hard on the ramp, and so unless there is some aggressive deck in the format, I don't see why every deck wouldn't run an Infestation Ramp package. Especially with cards like Acolyte of Faith just giving you shrines in the early game.

|Bucket|Cards|
|---|---|
|Value|Acolyte of Faith; Shrine Architect; Druid of Devotion; Call to Arms|
|Closers|Astral Crusher; Growth Incarnate; Infestation, God of Growth; Forest of Infestation; Insectile Invasion|
|Removal|Showdown|
|Card Advantage|Prayer for Intervention; Bolster Devotion|

### Occult

Thoughts: Occult doesn't have much in terms of removal other than bounce spells.  This seems to be an OP color, and it seems likely with all the card draw you could grind through most of your deck to set up a consistent win in just this color.

|Bucket|Cards|
|---|---|
|Value|Admirer of Revelation; Harbinger of Epiphany; Shaman of Marvel; Spiritual Enforcer; Mysticism Incarnate|
|Closers|Insight Seeker; Occult, God of Mysticism; Occult's Tome; Occult's Reckoning|
|Removal|Soul Cage?; Avenging Conscription?|
|Card Advantage|Acolyte of Inquiry; Professor of Truths; Shrine Investigator; Disciple of Occult; Divine Omen|

### Contagion

Thoughts: Contagion seems to have a ton of ways for you to put things into the Void, Sacrifice followers, and similar effects; however, the payoffs for those seem to be much weaker. I would want to see a card or two that has payoffs for filling the void before I really thought about a master contagion decklist.

|Bucket|Cards|
|---|---|
|Value|Acolyte of Consumption; Unstable Horror; Reckless Abomination; Disciple of Contagion; The Void's Embrace|
|Closers|Void Warrior; Thrashing Horror; Monk of Unknown Horrors; Contagion, God of Decay|
|Removal|Toxic Abomination; Putrefy|
|Card Advantage|Return from the Void; Drain Intellect; Rip from the Void|

### Grandeur

Thoughts: I love how Grandeur feels like there are two distinct decks that come out of it. There's the defensive deck with defender, shield, and healing effects that relies on a big finisher to close out the game, and there's a tempo deck that cares about counters and the leader effect. This god feels like it might have the best identity of all of them. That being said, it seems like Grandeur is lacking big closers and would look to win through more tempo gameplay and war of attrition style games.

|Bucket|Cards|
|---|---|
|Value|Acolyte of Honor; Kingdom Enforcer; Grizzled Veteran; Restore Faith|
|Closers|Grandeur, God of Glory; Armor Upgrade?; Grandeur's Reckoning?|
|Removal|Dematerialize; Place in the Pillory; Vanquish|
|Card Advantage|Prepare for Battle?|

## Final Thoughts
So at this point, I've examined every part of this game and it's time to start building decks and throwing them at each other to try to crack the meta-game wide open on day 0. Unfortunately, this blog post is already the longest one I've ever written, so we're going to go ahead and split the deck building into the next post! After that, I'll play a bunch of games and report back with my findings and tuned lists in a further post, and finally give a final verdict on my views of the meta-game of this unreleased, in design game, as well a discuss how I would go about changing the design to account for those systems.

Until next time.
-Andey


text:
---
layout: default
---

# 1994-12-14 - Re: pgp library

## Header Data

From<EMAIL_ADDRESS>(Jim McCoy)

To<EMAIL_ADDRESS>Message Hash: f5e643b6548f129fa618f45f92daa6ef8a7fd5a7a82bcec07b2fd33c1205f2b3

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1994-12-14 23:42:48 UTC

Raw Date: Wed, 14 Dec 94 15:42:48 PST

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Jim McCoy)
Date: Wed, 14 Dec 94 15:42:48 PST
To<EMAIL_ADDRESS>Subject: Re: pgp library
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

<EMAIL_ADDRESS>(Anonymous) writes:
> Jim McCoy responds:
> >  [...]  I do know of some people who are interested in working on
> >  a PGP compatible library of crypto code, but I am not quite sure
> >  what the status of that project is at this time...
>
> This is really a shame, because at the current time one of the most
> lacking aspects of most crypto software is the key management
> interface.

A key-management module is planned for this library.  Something that takes
the key management stuff out of the various places in the code it is
scattered and into it's own is one of the goals of the project.

> [...]  But you are doubly screwed because the PGP development
> team has made it clear that the keyring file format will change in
> 3.0.
[...]
> Who wants to spend time writing a key management API (which, I admit,
> is NOT trivial...) which is guaranteed not to work in the next version
> of PGP?

It is not necessarily guaranteed to not work.  We have been in contact with
members of the PGP development team, and may be able to emulate much of
thier API as things develop.  Either way, this is not just a project to
develop an updated PGPTools; we hope to have a general purpose crypto
library including better math routines, generalized key management, support
for multiple public-key and symmetrical ciphers, and hooks for various APIs
at different levels.

> PGP front-ends aren't the only application type whose progress is
> being slowed by this situation.  IMHO, any app that uses PK-crypto
> should support PGPformat keys, even if it's output isn't designed to
> be fed into PGP.

Either that, or PGP should learn to use a key standard that might not
necessarly be it's own.  Key management issues are one of the primary goals
for Eclipse and hopefully some of the IETF work in this arena in recent
months will help us in determining a direction to work in.  Either way,
while we want to support as much PGP functionality as possible I doubt we
will shackle ourselves with the liabilities of blindly following only the
PGP developers when deciding what to do.

jim

{% endraw %}
```

## Thread

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

+ Return to<EMAIL_ADDRESS>(Jim McCoy)](/authors/mccoy_at_io_com_jim_mccoy_)"
+ Return to<EMAIL_ADDRESS>(Anonymous)](/authors/nobody_at_jpunix_com_anonymous_)"

+ 1994-12-14 (Wed, 14 Dec 94 14:29:58 PST) - [Re: pgp library](/archive/1994/12/01ad65cfc2199190ea9530fef7b96367a7180428d2dcc9be08b59a113f0e8821) -<EMAIL_ADDRESS>(Anonymous)_
  + 1994-12-14 (Wed, 14 Dec 94 15:42:48 PST) - Re: pgp library -<EMAIL_ADDRESS>(Jim McCoy)_


text:
# Jewlz-TheBoyz-EmailCategorizationBot-P2

# Introduction
For our P2, we have decided to make an automation in UI Path Studio based off of one of the suggestions in the RevaturePro Slides. We will be making a Email Categorization Bot.

# Automation
This bot will automatically sort and categorize the users emails by a certain set of rules. We plan on adding facial recogniztion, the ability to login to different email services, and anything else we have time for.

# Flow Chart

# Tech Stack
Phase 1:
-Gmail
-UI Path Studio

Phase 2:
-Python/Flask
-OpenCV
-MS Outlook

# Phase 1
Implement Robot to take in user credentials, users preferred organization rules, and navigate to gmail on a web browser. The bot will then sign in that user, navigate the UI elements on gmail and organize emails based on a users rules.

# Phase 2
Implement Phase 1 as defined previously but instead of asking for credentials, the bot will have a “scan” step which makes a call to a python flask site which returns credential information related to that user.

# Audience
Our audience will include:
-Anyone with a gmail account
-Anyone who wants to categorize their emails


text:
# Terraform-aws-iam-role
Terraform module to create custom iam role with option to pass in custom policy or aws policy please see example for more details

# Usage

```hcl
module "iam_assume_role" {
  source                        = "anonymint/iam-role/aws"
  role_name                     = "ec2-container-instance-profile"
  policy_arns_count             = "1"
  policy_arns                   = ["arn:aws:iam::aws:policy/service-role/AmazonEC2ContainerServiceforEC2Role"]
  create_instance_role          = true
  iam_role_policy_document_json = "${data.aws_iam_policy_document.ec2_role_policy.json}"
}

# ROLE Policy
data "aws_iam_policy_document" "ec2_role_policy" {
  statement {
    actions = ["sts:AssumeRole"]

    principals {
      type = "Service"

      identifiers = [
        "ec2.amazonaws.com",
      ]
    }

    effect = "Allow"
  }
}

```

repository: h-nago/terraform-aws-iam-role

repo_name: h-nago/terraform-aws-iam-role


text:
---
layout: default
title: "DistributedLog Team"
permalink: /community/team/
redirect_from: /team/
---

# Apache DistributedLog Team

A successful project requires many people to play many roles. Some members write code or documentation, while others are valuable as testers, submitting patches and suggestions.

The team is comprised of Members and Contributors. Members have direct access to the source of a project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated.

{% for team in site.distributedlog_team %}

{{ team.group }}

{{ team.description }}

        Name
        Apache ID
        Email
        Organization
        Roles
        Time Zone

      {% for member in team.members %}

          {{ member.name }}
          {{ member.apache_id }}
          {{ member.email }}
          {{ member.organization }}
          {{ member.roles }}
          {{ member.time_zone }}

      {% endfor %}

{% endfor %}

{% for mentors in site.mentors %}

{{ mentors.group }}

{{ mentors.description }}

        Name
        Apache ID
        Email
        Organization
        Roles
        Time Zone

      {% for member in mentors.members %}

          {{ member.name }}
          {{ member.apache_id }}
          {{ member.email }}
          {{ member.organization }}
          {{ member.roles }}
          {{ member.time_zone }}

      {% endfor %}

{% endfor %}

repository: altusnets/distributedlog

repo_name: altusnets/distributedlog


text:
# CoreTextSwift

Swifty CoreText API.

CoreText is C API. This library is a set of wrappers and extensions that makes it convenient to work with Swift.

## Example

Draw line in currect graphics context

```swift
guard let ctx = UIGraphicsGetCurrentContext() else {
  return
}

let attributedString = NSAttributedString(string: "abcdefgh")
ctx.draw(attributedString.line())
```

Use Glyph Run

```swift
let attributedString = NSAttributedString(string: "abcdefgh")

for run in attributedString.line().glyphRuns() {
  let font = run.font
  for glyph in run.glyphs() {
    let glyphPath = font.path(for: glyph)
  }
}
```

Draw Glyph Run to CGContext

```swift
guard let ctx = UIGraphicsGetCurrentContext() else {
  return
}

for run in attributedString.line().glyphRuns() {
  run.draw(in: ctx)
}
```

repository: vrkkarthi/CoreTextSwift

repo_name: vrkkarthi/CoreTextSwift


text:
---
layout: post
title: NASA released its 2017-2018 software catalog
keywords: 'NASA, open source, software, programs'
published: true
comments: true
---

[NASA just released its software catalog](https://www.nasa.gov/press-release/nasa-releases-software-catalog-granting-the-public-free-access-to-technologies-for) for the 2017-2018 period.

{% include youtube.html id="JIpyc8AfMZY" %}

If you've ever wanted to know what programs does NASA use, now you can. The entire catalog is [visible at this page](https://software.nasa.gov/), and I particularly recommend looking at the [Data Servers Processing & Handling section](https://software.nasa.gov/data_servers_processing_and_handling) because it has a few tools that might be interesting.


text:
---
layout: post
title:  "28 Backspaces"
date:   2015-12-18 9:15:27
tags:
- linux
- security
---
Via [SC Magazine][sc-article], researchers from the [Cybersecurity Group at Polytechnic University of Valencia][upv-site]
found an exploit in [GRUB2][grub-manual] where pressing backspace 28 times at the login prompt
causes an integer underflow that runs GRUB2's rescue shell.

For all the gory details, you can check out [the full writeup][bug-breakdown].  I'm always amazed by the amount of damage
that can be caused/fixed with something as simple as changing
{% highlight js %}
if(key == '\b')
{% endhighlight %}
to
{% highlight js %}
if(key == '\b' && cur_len)
{% endhighlight %}

[sc-article]: http://www.scmagazine.com/how-to-bypass-lynixs-grub2-bootloader-with-one-key/article/460521/
[upv-site]: http://cybersecurity.upv.es/
[grub-manual]: http://www.gnu.org/software/grub/manual/grub.html
[bug-breakdown]: http://hmarco.org/bugs/CVE-2015-8370-Grub2-authentication-bypass.html

extension: markdown


text:
# DescribeInstanceVncUrl {#doc_api_Ecs_DescribeInstanceVncUrl .reference}

You can call this operation to query the Web management terminal URL of an ECS instance.

## Description {#description .section}

When you call this operation, note that:

-   A management terminal URL is only valid for 15 seconds. If a connection is not established within 15 seconds after a successful query, the URL expires and you must query it again.
-   The **KeepAlive** time of a management terminal connection is 60 seconds. If you do not interact with the management terminal within 60 seconds, the management terminal will be automatically disconnected.
-   When the management terminal is disconnected, you can only reconnect to the management terminal up to 30 times a minute.
-   At the end of [https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.5/index.html?](https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.5/index.html?), add `vncUrl=xxxx`, `instanceId=xxx`, `isWindows=True`, `isWindows=False`, and `password=XXXXXX`. Connect these parameters with `&`. Where:
    -   `vncUrl`: The value of `VncUrl` is returned after a successful query.
    -   `instanceId`: the ID of instance to be queried.
    -   `isWindows`: specifies whether the operating system of the instance is Windows. The value of `true` indicates the Windows system. The value of `false` indicates that the Windows system is not used.
    -   `password`: Optional. The password to establish a remote connection from the instance. It must be six characters in length and can contain digits and uppercase and lowercase letters. This parameter eliminates the need to enter a password on the management terminal when a connection is being established.

        Example:

        ```

               https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.5/index.html?vncUrl=ws%3A%2F%xxx&instanceId=i-wz9hhwq5a6tmxxxxxxx&isWindows=true

        ```

        or

        ```

               https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.5/index.html?vncUrl=ws%3A%2F%xxx&instanceId=i-wz9hhwq5a6tmxxxxxxx&isWindows=true&password=111111

        ```

## Debugging {#apiExplorer .section}

Alibaba Cloud provides [OpenAPI Explorer](https://api.aliyun.com/#product=Ecs&api=DescribeInstanceVncUrl) to simplify API usage. You can use OpenAPI Explorer to search for APIs, call APIs, and dynamically generate SDK example code.

## Request parameters {#parameters .section}

|Parameter|Type|Required|Example|Description|
|---------|----|--------|-------|-----------|
|InstanceId|String|Yes|i-AY121018033933eaxxxxxxx|The ID of the instance to be queried.

 |
|RegionId|String|Yes|cn-hangzhou|The region ID of the instance. You can call the [DescribeRegions](~~25609~~) operation to query the latest region list.

 |
|Action|String|No|DescribeInstanceVncUrl|The operation that you want to perform. Set the value to DescribeInstanceVncUrl.

 |

## Response parameters {#resultMapping .section}

|Parameter|Type|Example|Description|
|---------|----|-------|-----------|
|RequestId|String|473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E|The ID of the request.

 |
|VncUrl|String|ws%3A%2F%2Fhz01-vncproxy.aliyun.com%2Fwebsockify%2F%3Fs%3DDvh%252FIA%252BYc73gWO48cBx2gBxUDVzaAnSKr74pq30mzqUYgeUMcB%252FbkNixDxdEA996|The management terminal URL.

 |

## Examples {#demo .section}

Sample requests

``` {#request_demo}
https://ecs.aliyuncs.com/?Action=DescribeInstanceVncUrl
&InstanceId=i-AY121018033933eaxxxxxxx
&RegionId=cn-hangzhou
&<Common request parameters>
```

Sample success responses

`XML` format

``` {#xml_return_success_demo}
<DescribeInstanceVncUrlResponse>
  <RequestId>1450F2D7-5435-4420-BBC9-49C5xxxxxxxx</RequestId>
  <VncUrl>ws%3A%2F%2Fhz01-vncproxy.aliyun.com%2Fwebsockify%2F%3Fs%3DDvh%252FIA%252BYc73gWO48cBx2gBxUDVzaAnSKr74pq30mzqUYgeUMcB%252FbkNixDxdEA996</VncUrl>
</DescribeInstanceVncUrlResponse>

```

`JSON` format

``` {#json_return_success_demo}
{
	"VncUrl":"ws%3A%2F%2Fhz01-vncproxy.aliyun.com%2Fwebsockify%2F%3Fs%3DDvh%252FIA%252BYc73gWO48cBx2gBxUDVzaAnSKr74pq30mzqUYgeUMcB%252FbkNixDxdEA996",
	"RequestId":"1450F2D7-5435-4420-BBC9-49C5xxxxxxxx"
}
```

## Error codes { .section}

|HTTP status code|Error code|Error message|Description|
|----------------|----------|-------------|-----------|
|404|InvalidRegionId.NotFound|The specified RegionId does not exist.|The error message returned because the specified RegionId parameter does not exist.|
|404|InvalidInstanceId.NotFound|The specified InstanceId does not exist.|The error message returned because the specified InstanceId parameter does not exist.|
|403|IncorrectInstanceStatus|The current status of the resource does not support this operation.|The error message returned because the operation is not supported while the resource is in the current state.|
|500|InternalError|The request processing has failed due to some unknown error.|The error message returned because an internal error has occurred. Try again later. If the problem persists, submit a ticket.|
|403|InstanceNotReady|The specified instance is not ready for use|The error message returned because the operation is not supported while the resource is in the current state. Retry the operation after a few minutes.|

[View error codes](https://error-center.aliyun.com/status/product/Ecs)

repository: WensonYang/ecs

repo_name: WensonYang/ecs


text:
# docker-base

Minimal container images built on Alpine.

- Docker Hub [aeonproject/base](https://hub.docker.com/r/aeonproject/base/) is 5.949 MB

[![Docker Repository on Quay](https://quay.io/repository/aeonproject/base/status "Docker Repository on Quay")](https://quay.io/repository/aeonproject/base)

repository: aeon-io/docker-base

repo_name: aeon-io/docker-base


text:
KuroTwi
=============

This application is a twitter client. It works on Google Chrome.

Installation
=============
[Chrome Webstore](https://chrome.google.com/webstore/detail/kurotwi/kcijnjkpackkklmkicldmkbhpdeilbgf)

Usage
=============

Click the KuroTwi icon from the application list of Google Chrome.


text:
# Change Log

## [1.2.3](https://github.com/grisp/rebar3_grisp/tree/1.2.3) (2018-08-07)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.2.2...1.2.3)

**Implemented enhancements:**

- Print a proper error for missing template keys [\#37](https://github.com/grisp/rebar3_grisp/issues/37)

**Fixed bugs:**

- Default GRiSP sources overwrite custom sources [\#38](https://github.com/grisp/rebar3_grisp/issues/38)

## [1.2.2](https://github.com/grisp/rebar3_grisp/tree/1.2.2) (2018-08-01)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.2.1...1.2.2)

**Fixed bugs:**

- Templates do not work when deploying [\#36](https://github.com/grisp/rebar3_grisp/issues/36)

## [1.2.1](https://github.com/grisp/rebar3_grisp/tree/1.2.1) (2018-08-01)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.2.0...1.2.1)

**Fixed bugs:**

- Templates do not work when building [\#35](https://github.com/grisp/rebar3_grisp/issues/35)

## [1.2.0](https://github.com/grisp/rebar3_grisp/tree/1.2.0) (2018-07-31)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.1.5...1.2.0)

**Implemented enhancements:**

- Re-introduce GRISP\_TOOLCHAIN environment variable [\#34](https://github.com/grisp/rebar3_grisp/pull/34) ([eproxus](https://github.com/eproxus))
- Add version task that prints version number [\#33](https://github.com/grisp/rebar3_grisp/pull/33) ([eproxus](https://github.com/eproxus))
- Include environment variables in templates [\#32](https://github.com/grisp/rebar3_grisp/pull/32) ([eproxus](https://github.com/eproxus))

## [1.1.5](https://github.com/grisp/rebar3_grisp/tree/1.1.5) (2018-06-25)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.1.4...1.1.5)

**Fixed bugs:**

- Weird directory with name " created during deploy [\#30](https://github.com/grisp/rebar3_grisp/issues/30)

## [1.1.4](https://github.com/grisp/rebar3_grisp/tree/1.1.4) (2018-06-21)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.1.3...1.1.4)

## [1.1.3](https://github.com/grisp/rebar3_grisp/tree/1.1.3) (2018-06-21)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.1.2...1.1.3)

## [1.1.2](https://github.com/grisp/rebar3_grisp/tree/1.1.2) (2018-06-06)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.1.1...1.1.2)

**Merged pull requests:**

- deploy: added support for whitespaces in source and deployment directories [\#28](https://github.com/grisp/rebar3_grisp/pull/28) ([lwehmeier](https://github.com/lwehmeier))
- Remove references to old versions [\#27](https://github.com/grisp/rebar3_grisp/pull/27) ([nextl00p](https://github.com/nextl00p))
- consistency of the instructions for release name [\#26](https://github.com/grisp/rebar3_grisp/pull/26) ([CrowdHailer](https://github.com/CrowdHailer))
- Add support for OTP 21.0-rc1 [\#25](https://github.com/grisp/rebar3_grisp/pull/25) ([sylane](https://github.com/sylane))

## [1.1.1](https://github.com/grisp/rebar3_grisp/tree/1.1.1) (2018-05-25)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.1.0...1.1.1)

**Fixed bugs:**

- Freshly generated grispapp fails to deploy the first time its run [\#23](https://github.com/grisp/rebar3_grisp/issues/23)

## [1.1.0](https://github.com/grisp/rebar3_grisp/tree/1.1.0) (2018-05-24)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.0.1...1.1.0)

**Closed issues:**

- Start Erlang runtime when source dependencies are included [\#21](https://github.com/grisp/rebar3_grisp/issues/21)
- Wrong warning about Erlang version mismatch [\#14](https://github.com/grisp/rebar3_grisp/issues/14)
- Make deploy destination available via command-line flag [\#5](https://github.com/grisp/rebar3_grisp/issues/5)
- Confusing error message, when no toolchain root is set [\#4](https://github.com/grisp/rebar3_grisp/issues/4)

**Merged pull requests:**

- Prebuilt toolchain [\#20](https://github.com/grisp/rebar3_grisp/pull/20) ([nextl00p](https://github.com/nextl00p))
- Add version to OTP xcomp files [\#18](https://github.com/grisp/rebar3_grisp/pull/18) ([sylane](https://github.com/sylane))
- Allow deploy without grisp runtime and fix version warning [\#17](https://github.com/grisp/rebar3_grisp/pull/17) ([sylane](https://github.com/sylane))
- Refactor build configuration [\#16](https://github.com/grisp/rebar3_grisp/pull/16) ([sylane](https://github.com/sylane))

## [1.0.1](https://github.com/grisp/rebar3_grisp/tree/1.0.1) (2017-12-20)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/1.0.0...1.0.1)

## [1.0.0](https://github.com/grisp/rebar3_grisp/tree/1.0.0) (2017-12-19)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/0.1.1...1.0.0)

**Fixed bugs:**

- With default profile section ERTS does not get included [\#8](https://github.com/grisp/rebar3_grisp/issues/8)

**Closed issues:**

- Document rebar3 grisp build [\#3](https://github.com/grisp/rebar3_grisp/issues/3)

**Merged pull requests:**

- Make SMP the default and add support for OTP 20.2 [\#13](https://github.com/grisp/rebar3_grisp/pull/13) ([sylane](https://github.com/sylane))
- Make OTP version branch customizable [\#12](https://github.com/grisp/rebar3_grisp/pull/12) ([eproxus](https://github.com/eproxus))

## [0.1.1](https://github.com/grisp/rebar3_grisp/tree/0.1.1) (2017-12-05)
[Full Changelog](https://github.com/grisp/rebar3_grisp/compare/0.1.0...0.1.1)

## [0.1.0](https://github.com/grisp/rebar3_grisp/tree/0.1.0) (2017-10-20)

\* *This Change Log was automatically generated by [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator)*


text:
---
layout: spec
title: "[DEMO] Images"
---

# Images
{: .primer-spec-toc-ignore }

# Basic syntax

Primer Spec automatically adds a subtle `1px` border to images. In my opinion, the border helps with readability, especially for images whose background colors match the background of the page.

For instance, try viewing this image in the "default" theme in "light" mode:

![This image shows a screenshot of Primer Spec in the 'Bella' theme.](https://drive.google.com/uc?export=view&id=1_QPsSGlXKjfqY-3TUbsXej5isOZypK7U)

You can use either Markdown syntax or HTML syntax to define images.

Source code for basic image syntax

Markdown syntax:
![This image shows a screenshot of Primer Spec in the 'Bella' theme.](./screenshot.png)

Equivalent HTML syntax:
<img
  src="./screenshot.png"
  alt="This image shows a screenshot of Primer Spec in the 'Bella' theme." />

Don't forget the 'alt' text! It's the only way fot visually-impaired users to understand the context provided by the image.

# Opt-out of image borders

Simply add the `no-border` class to the image. For instance:

![This image shows a screenshot of Primer Spec in the 'Bella' theme.](https://drive.google.com/uc?export=view&id=1_QPsSGlXKjfqY-3TUbsXej5isOZypK7U){: .no-border }

Source code for borderless images

Markdown syntax:
![This image shows a screenshot of Primer Spec in the 'Bella' theme.](./screenshot.png){: .no-border }

Equivalent HTML syntax:
<img
  src="./screenshot.png"
  alt="This image shows a screenshot of Primer Spec in the 'Bella' theme."
  class="no-border" />

# Supporting dark mode

Primer Spec supports built-in dark mode themes, which invert the background and foreground colors on the page. Primer Spec is able to invert most colors automatically, but *cannot* automatically handle images on your pages.

You'll need to opt-in to these optimizations to better support your dark mode users. Primer Spec offers you two easy options to add dark mode support for your images:

- [**Option 1 *(recommended)***](#option-1-recommended-auto-invert-image-colors-in-dark-mode): Ask Primer Spec to auto-invert your image!
- [**Option 2**](#option-2-show-images-only-in-certain-theme-mode): Create two separate images (one optimized for light mode, the other for dark mode)

## Option 1 (recommended): Auto-invert image colors in dark mode

If you add the `invert-colors-in-dark-mode` class to an image, Primer Spec will automatically invert the colors of the image when users view the page in a dark theme!

For instance, the following image changes colors in light mode and dark mode:

![This image shows a screenshot of Primer Spec in the 'Bella' theme.](https://drive.google.com/uc?export=view&id=1_QPsSGlXKjfqY-3TUbsXej5isOZypK7U){: .invert-colors-in-dark-mode }

Source code for auto-inverted images

Markdown syntax:
![This image shows a screenshot of Primer Spec in the 'Bella' theme.](./screenshot.png){: .invert-colors-in-dark-mode }

Equivalent HTML syntax:
<img
  src="./screenshot.png"
  alt="This image shows a screenshot of Primer Spec in the 'Bella' theme."
  class="invert-colors-in-dark-mode" />

## Option 2: Show images only in certain theme mode

You can specify that an image is only shown in light mode or dark mode by appending `#gh-dark-mode-only` or `#gh-light-mode-only` to the end of an image URL.

Context	URL

  Light mode
  ![Light mode image](./image.png#gh-light-mode-only)

  Dark mode
  ![Dark mode image](./image.png#gh-dark-mode-only)

For instance, I created two different versions of the Primer Spec logo:

Light mode	Dark mode

However, I only want to show the correct version of the image depending on the theme mode. The following image dynamically displays the correct version of the logo when you change the theme between light and dark modes!

Source code for auto-switching logo

Markdown syntax:
![Light mode version of Primer Spec logo](./logo-light.svg#gh-light-mode-only)
![Dark mode version of Primer Spec logo](./logo-dark.svg#gh-dark-mode-only)

Equivalent HTML syntax:
<img
  src="./logo-light.svg#gh-light-mode-only"
  alt="Light mode version of Primer Spec logo" />
<img
  src="./logo-dark.svg#gh-dark-mode-only"
  alt="Dark mode version of Primer Spec logo" />

# Diagrams

If you wish to upload images that represent flow charts or other diagrams, consider using Excalidraw or Mermaid instead. Check out the [Diagrams demo](./diagrams.html) for more information.

gha_language: TypeScript


text:
The aim of this project is to provide a very simple web form for users
to be able to change their SSH key stored in LDAP or Active Directory
(Samba 4 AD). It’s built with [Bottle](http://bottlepy.org), a WSGI
micro web-framework for Python.

Installation
============

Manually
--------

Clone this repository and install dependencies:

    git clone git@github.com:jceloria/adkey.git
    cd adkey
    pip install -r requirements.txt

Read the next sections to learn how to run it.

Requirements
------------

-   Python 3.x

-   [bottle](https://pypi.python.org/pypi/bottle/)

-   [ldap3](https://pypi.python.org/pypi/ldap3) 2.x

Configuration
=============

Configuration is read from the file
[settings.ini](settings.ini.example). You may change location of the
settings file using the environment variable `CONF_FILE`.

Run it
======

There are multiple ways how to run it:

-   with the built-in default WSGI server based on
    [wsgiref](https://docs.python.org/3/library/wsgiref.html#module-wsgiref.simple_server),

-   under a
    [WSGI](https://en.wikipedia.org/wiki/Web_Server_Gateway_Interface)
    server like [uWSGI](https://uwsgi-docs.readthedocs.org),
    [Waitress](https://docs.pylonsproject.org/projects/waitress),
    [Gunicorn](http://gunicorn.org), … (recommended)

-   as a [CGI](https://en.wikipedia.org/wiki/Common_Gateway_Interface)
    script.

Run with the built-in server
----------------------------

Simply execute the `adkey.py`:

    python3 adkey.py

Then you can access the app on <http://localhost:8080>. The port and
host may be changed in [settings.ini](settings.ini.example).

Run with Waitress
-----------------

    cd adkey
    waitress-serve --listen=*:8080 app:application

Run with uWSGI and nginx
------------------------

If you have many micro-apps like this, it’s IMO kinda overkill to run
each in a separate uWSGI process, isn’t it? It’s not so well known, but
uWSGI allows to “mount” multiple application in a single uWSGI process
and with a single socket.

**Sample uWSGI configuration:.**

    [uwsgi]
    plugins = python3
    socket = /run/uwsgi/main.sock
    chdir = /var/www/scripts
    logger = file:/var/log/uwsgi/main.log
    processes = 1
    threads = 2
    # map URI paths to applications
    mount = /admin/adkey=adkey/adkey.py
    #mount = /admin/change-world=change-world/adkey.py
    manage-script-name = true

**Sample nginx configuration as a reverse proxy in front of uWSGI:.**

    server {
        listen 443 ssl;
        server_name example.org;

        ssl_certificate     /etc/ssl/nginx/nginx.crt;
        ssl_certificate_key /etc/ssl/nginx/nginx.key;

        # uWSGI scripts
        location /admin/ {
            uwsgi_pass  unix:/run/uwsgi/main.sock;
            include     uwsgi_params;
        }
    }

Screenshot
==========

![](doc/screenshot.png)

License
=======

This project is licensed under [MIT
License](http://opensource.org/licenses/MIT/). For the full text of the
license, see the [LICENSE](LICENSE) file.

repository: jceloria/adkey

repo_name: jceloria/adkey


text:
# Getting started

- [Installation](#installation)
- [Basic usage](#basic-usage)
- [Using multiple storages to improve readability](#using-multiple-storages-to-improve-readability)
- [Using memory storage in tests](#using-memory-storage-in-tests)

## Installation

flysystem-bundle requires PHP 7.1+ and Symfony 4.2+.

You can install the bundle using Symfony Flex:

```
composer require league/flysystem-bundle
```

## Basic usage

The default configuration file created by Symfony Flex provides enough configuration to
use Flysystem in your application as soon as you install the bundle:

```yaml
# config/packages/flysystem.yaml

flysystem:
    storages:
        default.storage:
            adapter: 'local'
            options:
                directory: '%kernel.project_dir%/var/storage/default'
```

This configuration defines a single storage service (`default.storage`) based on the local adapter
and configured to use the `%kernel.project_dir%/var/storage/default` directory.

For each storage defined under `flysystem.storages`, an associated service is created using the
name you provide (in this case, a service `default.storage` will be created). The bundle also
creates a named alias for each of these services.

This means you have two way of using the defined storages:

* either using autowiring, by typehinting against the `FilesystemOperator` and using the
  variable name matching one of your storages:

    ```php
    use League\Flysystem\FilesystemOperator;

    class MyService
    {
        private $storage;

        // The variable name $defaultStorage matters: it needs to be the camelized version
        // of the name of your storage.
        public function __construct(FilesystemOperator $defaultStorage)
        {
            $this->storage = $defaultStorage;
        }

        // ...
    }
    ```

  The same goes for controllers:

    ```php
    use League\Flysystem\FilesystemOperator;

    class MyController
    {
        // The variable name $defaultStorage matters: it needs to be the camelized version
        // of the name of your storage.
        public function index(FilesystemOperator $defaultStorage)
        {
            // ...
        }
    }
    ```

* or using manual injection, by injecting the service named `default.storage` inside
  your services.

Once you have a FilesystemOperator, you can call methods from the
[Filesystem API](https://flysystem.thephpleague.com/v2/docs/usage/filesystem-api/)
to interact with your storage.

## Using multiple storages to improve readability

While using the default storage can be enough, it is usually recommended to create multiple
storages, even if behind the scene you may rely on the same adapter.

The reason for this is the added readability this provides to your project code: by naming
your storages using their **intents**, you will naturally increase the readability of your
autowired arguments. For example:

```yaml
# config/packages/flysystem.yaml

flysystem:
    storages:
        users.storage:
            adapter: 'local'
            options:
                directory: '%kernel.project_dir%/storage/users'

        projects.storage:
            adapter: 'local'
            options:
                directory: '%kernel.project_dir%/storage/projects'
```

```php
use League\Flysystem\FilesystemOperator;

class MyService
{
    private $usersStorage;
    private $projectsStorage;

    public function __construct(FilesystemOperator $usersStorage, FilesystemOperator $projectsStorage)
    {
        $this->usersStorage = $usersStorage;
        $this->projectsStorage = $projectsStorage;
    }

    // ...
}
```

## Using memory storage in tests

One of the best reason to use a filesystem abstraction in your project is the ability
it gives you to swap the actual implementation during tests.

More specifically, it can be useful to swap from a persisted storage to a memory one during
tests, both to ensure the state is reset between tests and to increase tests speed.

To achieve this, you can overwrite your storages in the test environment:

```yaml
# config/packages/flysystem.yaml

flysystem:
    storages:
        users.storage:
            adapter: 'local'
            options:
                directory: '%kernel.project_dir%/storage/users'
```

```yaml
# config/packages/test/flysystem.yaml

flysystem:
    storages:
        users.storage:
            adapter: 'memory'
```

This configuration will swap every reference to the `users.storage` service (or to the
`FilesystemOperator $usersStorage` typehint) from a local adapter to a memory one during tests.

## Next

[Cloud storage providers](https://github.com/thephpleague/flysystem-bundle/blob/master/docs/2-cloud-storage-providers.md)

repository: thephpleague/flysystem-bundle

gha_language: PHP

repo_name: thephpleague/flysystem-bundle


text:
# pull-file

This is a simple module which uses raw file reading methods available in
the node `fs` module to read files on-demand.  It's a work in progress
and feedback is welcome :)

[![NPM](https://nodei.co/npm/pull-file.png)](https://nodei.co/npm/pull-file/)

[![Build Status](https://img.shields.io/travis/DamonOehlman/pull-file.svg?branch=master)](https://travis-ci.org/DamonOehlman/pull-file) [![experimental](https://img.shields.io/badge/stability-experimental-red.svg)](https://github.com/badges/stability-badges) [![Dependency Status](https://david-dm.org/DamonOehlman/pull-file.svg)](https://david-dm.org/DamonOehlman/pull-file)

## Example Usage

```js
var file = require('pull-file');
var pull = require('pull-stream');
var path = require('path');
var inputFile = path.resolve(__dirname, '../test/assets/ipsum.txt');

pull(
  file(inputFile, { bufferSize: 40 }),
  pull.take(4),
  pull.drain(function(buffer) {
    console.log(buffer.toString());
  })
);
```

## License(s)

### MIT

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

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

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

repository: ATMatrix/demo

repo_name: ATMatrix/demo


text:
## Note

Note that not all algorithms are well tested so bugs are quite possible.

## About

This repository contains different famous Computer Science algorithms implemented in JavaScript

In order to run the tests use:

```Bash
jasmine-node test/
```

and all `*.spec.js` files will be executed.

## Contributions

Fork the repo and make requred changes. After that push your changes in branch, which is named according to the changes you did.
Initiate the PR.

## Contributors

[![mgechev](https://avatars.githubusercontent.com/u/455023?v=3&s=117)](https://github.com/mgechev)[![Microfed](https://avatars.githubusercontent.com/u/613179?v=3&s=117)](https://github.com/Microfed)[![contra](https://avatars.githubusercontent.com/u/425716?v=3&s=117)](https://github.com/contra)

## License

The code in this repository is distributed under the terms of the MIT license.

repository: shankscript/javascript-algorithms

repo_name: shankscript/javascript-algorithms


text:
---
layout: main.njk
title: FicusJS documentation - Going build-less
---
# Going build-less

Browsers have improved a lot over the past years. It's now possible to do web development without requiring any build tools, using the native module loader of the browser. We think this is a great fit for FicusJS, and we recommend this as a general starting point.

Build tools can quickly add a lot of complexity to your code, and make your code reliant on a specific build setup. We think it's best to avoid them during development, or only add them for light transformations if you know what you're doing.

[Read this article](https://dev.to/open-wc/developing-without-a-build-1-introduction-26ao) to learn more about this approach.

If your project is using an existing build tool, FicusJS is fully compatible and can work alongside other libraries and frameworks.

repository: ficusjs/ficusjs-docs

repo_name: ficusjs/ficusjs-docs


text:
---
layout:     post
title:      "It Always Starts With a Blank Canvas"
subtitle:   ""
date:       2016-09-17 00:45:00
author:     "Nicholas Rees"
header-img: "img/newfivesmall.jpg"
---

Where to Begin

Beginning a new project can be tough, so I’ve decided - hopefully to benefit both myself and anyone reading - to record the process of building a small, reusable and modular infographic library utilising D3.js.

The idea is to build a library that can work like a puzzle, where pieces seamlessly fit on top of one another in such a way that the visuals are neither boring nor repetitive, but will still carry the desired visual identity.

From the outset, It’s important not to be blinded by any seemingly unsurmountable obstacles, which means approaching this in one step at a time.


text:
# ring-apigw-lambda-proxy

Ring middleware for handling AWS API Gateway Lamdbda proxy Requests and responses

Note! Currently only GET requests are supported.

## Installation

Add the following to your `project.clj` `:dependencies`:

```clojure
[ring-apigw-lambda-proxy "0.0.1"]
```

## Usage

AWS Lambda JSON Rest API example.

Add `ring/ring-core`, `ring/ring-json`,`compojure`,`lambdada` and `cheshire` dependencies.

```clojure
(ns example
  (:require [uswitch.lambada.core :refer [deflambdafn]]
            [cheshire.core :refer [parse-stream generate-stream]]
            [clojure.java.io :as io]
            [ring.middleware.apigw :refer [wrap-apigw-lambda-proxy]]
            [ring.middleware.params :refer [wrap-params]]
            [ring.middleware.keyword-params :refer [wrap-keyword-params]]
            [ring.middleware.json :refer [wrap-json-params
                                          wrap-json-response]]
            [ring.util.response :as r]
            [compojure.core :refer :all]))

(defroutes app
  (GET "/v1/hello" {params :params}
    (let [name (get params :name "World")]
      (-> (r/response {:message (format "Hello, %s" name)})))))

(def handler (wrap-apigw-lambda-proxy
               (wrap-json-response
                 (wrap-json-params
                   (wrap-params
                     (wrap-keyword-params
                       app))))))

(deflambdafn example.LambdaFn [is os ctx]
  (with-open [writer (io/writer os)]
    (let [request (parse-stream (io/reader is :encoding "UTF-8") true)]
      (generate-stream (handler request) writer))))

```

repository: mnylen/ring-apigw-lambda-proxy

repo_name: mnylen/ring-apigw-lambda-proxy


text:
-   [Using types to unit-test in Haskell](https://lexi-lambda.github.io/blog/2016/10/03/using-types-to-unit-test-in-haskell/)

    > By taking advantage of Haskell's expressive type system, it's possible to not only achieve parity with object-oriented testing techniques, but also to provide stronger static guarantees as well. Furthermore, it's all possible without resorting to extra-linguistic hacks that static object-oriented languages sometimes use for mocking.

-   [Docker demons: PID-1, orphans, zombies, and signals](https://www.fpcomplete.com/blog/2016/10/docker-demons-pid1-orphans-zombies-signals)

    > There are a number of corner cases to consider when dealing with Docker, multiple processes, and signals. Probably the most famous post on this matter is from the Phusion blog. Here, we'll see some examples of how to see these problems first hand, and one way to work around it: fpco/pid1.

-   [Patat and Myanmar travels](https://jaspervdj.be/posts/2016-10-02-patat-myanmar.html)

    > At work, I frequently need to give (internal) presentations and demos using video conferencing. I prefer to do these quick-and-dirty presentations in the terminal. To this end, I wrote patat (Presentations And The ANSI Terminal) because I was not entirely happy with the available solutions.

-   [wrecker](https://github.com/skedgeme/wrecker/blob/0aacc038931b5c7c45419cc314692ea3334b5bf3/README.md)

    > wrecker is an HTTP benchmarking library and executable for profiling several API actions. wrecker is designed from the ground-up for scripting complex API sequences sublimely. Benchmarks can utilize a wreq-like interface, perhaps the easiest-to-use Haskell library for HTTP interaction, and quickly create wonderful, typed API clients.

-   [Qtah](http://khumba.net/projects/qtah/)

    > Qtah is a set of Qt bindings for Haskell, providing a traditional imperative interface to a mature GUI toolkit.

-   [Hackage reliability via mirroring](https://www.well-typed.com/blog/2016/09/hackage-reliability-via-mirroring/)

    > Hackage now has multiple secure mirrors which can be used fully automatically by clients such as cabal.

-   [ICFP 2016 Haskell videos](https://www.youtube.com/playlist?list=PLnqUlCo055hX8RkgLEjBYnETx6NuiL756)

    > ICFP 2016 is the 21st ACM SIGPLAN International Conference on Functional Programming. ICFP provides a forum for researchers and developers to hear about the latest work on the design, implementations, principles, and uses of functional programming. The conference covers the entire spectrum of work, from practice to theory, including its peripheries.

-   [Full-time Haskell jobs in London, at Barclays](https://neilmitchell.blogspot.co.uk/2016/09/full-time-haskell-jobs-in-london-at.html)

    > I work for Barclays, in London, working on a brand new Haskell project. We're looking for nine additional Haskell programmers to come and join the team.

-   [Haskell Internship (Paid. Remote acceptable.)](https://www.vacationlabs.com/haskell-internship/)

    > Before we dive into Haskell head-first, we're planning to first build a proof-of-concept (POC) webapp. We believe that a lot of questions need to be answered about building a large-scale webapp in Haskell.

Did you like this issue?
Let us know [on Twitter](https://twitter.com/haskellweekly)!
Think it could be better?
Send us [an<EMAIL_ADDRESS>or open [an issue](https://github.com/haskellweekly/haskellweekly.github.io/issues/new).
Thanks for reading!

repository: haskellweekly/haskellweekly

branch_name: refs/heads/haskellweekly

gha_language: Haskell

repo_name: haskellweekly/haskellweekly


text:
<!--    CHANGELOG FORMAT                                                -->
<!--                                                                    -->
<!--    Completed Entry template:                                       -->
<!--                                                                    -->
<!--    ## Date in DD MMM YYYY format                                   -->
<!--    ### ATT&CK Workbench version ##.##.##                           -->
<!--    #### New Features                                               -->
<!--    #### Improvements                                               -->
<!--    #### Fixes                                                      -->
<!--                                                                    -->
<!--    Entries for pull request template:                              -->
<!--                                                                    -->
<!--    ## Changes staged on develop                                    -->
<!--    #### New Features                                               -->
<!--    #### Improvements                                               -->
<!--    #### Fixes                                                      -->
<!--                                                                    -->
<!--                                                                    -->
<!--    VERSION NUMBERING                                               -->
<!--                                                                    -->
<!--    app versions are set up in a major.minor.patch format:          -->
<!--    MAJOR updates are when we release major new features or         -->
<!--          pages                                                     -->
<!--    MINOR updates are when we improve a small number of             -->
<!--          existing features                                         -->
<!--    PATCH updates are when a bugfix is made without the             -->
<!--          addition of notable features. When PATCH is 0 it can      -->
<!--          be omitted                                                -->
<!--                                                                    -->
<!--    Versions must match across repos, and must be reflected in      -->
<!--    each repo's package.json file's version marking.                -->

# Changelog

## 21 October 2021

### ATT&CK Workbench version 1.1.0

ATT&CK Workbench v1.1.0 includes support for ATT&CK Spec v2.1.0 and coincides with the ATT&CK v10.0 release. Users who do not upgrade to Workbench v1.1.0 may encounter issues with the new ATT&CK data:

-   If the user added the ATT&CK collection index prior to the ATT&CK v10.0 release, it may lose track of imported Enterprise collections. These collections can still be found in the "imported collections" tab of the collection manager, but won't be reflected in the collection manager. Collection subscriptions for Enterprise may also be lost. Upgrading to ATT&CK Workbench v1.1.0 will fix this issue and restore prior collection subscriptions.
-   If the user imports ATT&CK v10.0 using ATT&CK Workbench 1.0.X, data sources and data components will not be imported into their local knowledge base. You can re-import the collection after upgrading Workbench to v1.1.0 to acquire the data sources and data components even if you had already imported it when running a prior version of Workbench.

ATT&CK Workbench version 1.1.0 includes improvements to how data is imported which should circumvent the above issues for future releases of ATT&CK.

#### Improvements in 1.1.0

-   Added object type documentation on list pages. See [frontend#221](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/221).
-   Added support for ATT&CK Spec v2.1.0:
    -   Added support for data sources and data components, and viewing/editing interfaces for these object types and their relationships with techniques. See [frontend#67](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/67), [frontend#66](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/66).
    -   Added support for `x_mitre_attack_spec_version` on all object types.
-   Improved the flexibility and robustness of collection imports:
    -   Workbench will now check the ATT&CK Spec version of imported data and warn the user if the ATT&CK Spec version is unsupported (ex. if the Workbench instance is too outdated to support the data it is trying to import). The user can choose to bypass this warning.
    -   Workbench can now import the same collection multiple times in case objects in the initial import could not be imported due to an error.
    -   The user will now be provided with a downloadable list of objects that could not be saved (and the reason why) in the event of import errors.
    -   REST API will now log import errors for individual objects to the console when the log level is set to `verbose`.
    -   Frontend will now log import errors to the console when the application environment is not set to production.
-   Added validation for missing ATT&CK IDs on objects that support them. The user will now be warned if they neglect to assign an ATT&CK ID to an object which supports it. When exporting a collection, the user will similarly be warned if any contained objects are missing ATT&CK IDs. See [frontend#231](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/231).
-   REST API now supports setting the log level through an environment variable. See [rest-api#108](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/108).
-   REST API no longer sets the `upgrade-insecure-requests` directive of the `Content-Security-Policy` header in responses. This will facilitate the deployment of ATT&CK Workbench in an internal environment without requiring the system to be configured to support HTTPS. See [rest-api#96](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/96).

#### Fixes in 1.1.0

-   Fixed an issue where the navigation header could be inaccessible when navigating within the application or when the page resized due to user input.
-   Frontend will no longer claim objects were imported when they were actually discarded due to import errors such as spec violations.
-   Imported STIX bundles will no longer require (but still allow) the `spec_version` field on the bundle itself. This was causing issues importing collections created by the Workbench. Objects within the bundle still require the `spec_version` field per the STIX 2.1 spec. See [rest-api#103](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/103).
-   Fixed an issue where the REST API would save references when importing a collection bundle even though the `previewOnly` flag had been set. See [rest-api#120](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/120).

## 20 August 2021

### ATT&CK Workbench version 1.0.2

#### Fixes in 1.0.2

-   Error snackbars will now show appropriate messages instead of `[object ProgressEvent]` when communication with the REST API is interrupted or cannot be established. See [frontend#227](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/227).
-   Fixed a bug where tactic shortnames were computed incorrectly for tactics with more than one space in the name (E.g `"Command and Control"`). See [frontend#239](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/239).
    -   If you have edited a technique under a tactic with more than one space in the name, remove and re-add the tactic under the technique edit interface to ensure that the tactic reference is formatted properly.
    -   If you have created a tactic with more than one space in the name, save a new version of the tactic and the proper shortname should be saved. You do not need to make any edits when saving the tactic page for the shortname to be fixed.

## 8 July 2021

### ATT&CK Workbench version 1.0.1

#### Improvements in 1.0.1

-   Added a system for configuring the Collection Manager with self-signed certs when using the docker setup. Documentation for this configuration will be improved in a subsequent release.

#### Fixes in 1.0.1

-   Fixed an error encountered when using the `attack-objects` API with large datasets. This error was preventing users from loading the "create a collection" page when Enterprise ATT&CK collections were imported. See [rest-api#87](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/87).

## 21 June 2021

### ATT&CK Workbench version 1.0.0

#### Improvements in 1.0.0

-   Performance improvements when adding, editing, and validating relationships.
-   Improved error messages when importing collections that are too large or malformed. See [frontend#198](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/198).
-   Improved page titles and breadcrumb on "object not found" pages.
-   User can now import collections from file. See [frontend#207](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/207).
-   Collection index update interval is now set in the REST API configuration instead of hardcoded in the frontend. See [frontend#200](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/200).

#### Fixes in 1.0.0

-   Fixed vertically misaligned timestamps across several UIs.
-   Fixed missing timestamp on collection version lists within collection indexes.
-   Fixed object status popover showing the wrong status if opened too soon after the page loads. Also improved performance of the status popover code.
-   Collection import UI no longer gets stuck if it runs into a problem fetching/importing/previewing the collection. See [frontend#198](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/198)
-   Object status popover now closes properly when the user starts editing the object. See [frontend#199](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/199).

## 7 May 2021

### ATT&CK Workbench version 0.4.0

#### Improvements in 0.4.0

-   Added a favicon. See [frontend#137](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/137).
-   Added dynamic page title to make it easier to distinguish multiple Workbench tabs in the browser. See [frontend#130](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/130).
-   Added a list of recommended indexes available when adding a collection index. See [frontend#194](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/194).
-   Added ability to set workflow state when objects are saved. See [frontend#184](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/184).
-   Updated occurrences of "aliases" to "associated groups" or "associated software" for consistency across the application. See [frontend#176](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/176).
-   Improved logging and added log level to environment configuration to suppress unnecessary logs from production deployments. See [frontend#209](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/209).
-   Updated the reference editor to enforce correct formatting when creating a new reference. See [frontend#177](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/177).

## 21 April 2021

### ATT&CK Workbench version 0.3.0

#### New Features in 0.3.0

-   Added attribution of edits and tracking of organization identity. See [frontend#61](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/124) and [frontend#182](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/61).
-   Added ability to revoke and deprecate objects. See [frontend#164](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/164).
-   Added tracking of workflow state. See [frontend#3](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/3).
-   Added ability to create and edit collections. See [frontend#4](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/4), [frontend#5](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/5), and [frontend#112](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/112).
-   Added support and documentation for [ATT&CK Navigator](https://github.com/mitre-attack/attack-navigator) integration. See [frontend#153](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/153).
-   Added support and documentation for [ATT&CK Website](https://github.com/mitre-attack/attack-website/) integration. See [frontend#152](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/152).

#### Improvements in 0.3.0

-   Improved display of object domains. See [frontend#166](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/166).

## 19 March 2021

### ATT&CK Workbench version 0.2.0

#### New Features in 0.2.0

-   Added support for MTC and CAPEC IDs. See [frontend#124](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/124).
-   Added ability to create and edit objects. See [frontend#44](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/44) and [frontend#145](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/145).
    -   Added ability to edit group/software aliases. See [frontend#118](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/118).
    -   Added ability to edit various list properties such as platforms, tactics, and domains. See [frontend#31](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/31).
    -   Added rich-text description editor. See [frontend#32](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/32).
    -   Added ability to convert techniques to sub-techniques, and vice versa.
    -   Added ability to edit ATT&CK IDs. See [frontend#55](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/55).
    -   Added validation system to warn user of malformed data.
    -   Added ability to reorder tactics on matrices. See [frontend#116](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/116).
    -   Added ability to edit object version numbers, and a UI for incrementing versions when objects are saved. See [frontend#56](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/56).
-   Added ability to create and edit notes (annotations) on objects. See [frontend#59](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/59).
-   Added citations/references support.
    -   Added automatic detection of citations on descriptions and aliases. See [frontend#115](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/115).
    -   Added references manager tool. See [frontend#115](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/115) and [frontend#133](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/133).

#### Improvements in 0.2.0

-   Lists of objects can now be searched and filtered. See [frontend#128](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/128) and [frontend#127](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/127).
-   Lists of objects now display ATT&CK IDs when relevant. See [frontend#119](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/119).
-   When viewing an object, fields which have no value(s) will now be hidden. See [frontend#120](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/120).
-   Improved display of sub-techniques. See [frontend#125](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/125).
-   Layout and formatting improvements to [USAGE](/docs/usage.md) document

#### Fixes in 0.2.0

-   Fixed broken pagination on relationship tables. See [frontend#126](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/126).

## 16 February 2021

### ATT&CK Workbench version 0.1.1

#### New Features in 0.1.1

-   Added Dockerfiles, docker-compose, [and documentation on how to use them](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/tree/master/docs/docker-compose.md). See [frontend#108](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/108), [frontend#109](https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/109) [rest-api#14](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/14), and [collection-manager#13](https://github.com/center-for-threat-informed-defense/attack-workbench-collection-manager/issues/13).

#### Fixes in 0.1.1

-   Fixed a crash that could occur with specific queries on the REST API. See [rest-api#28](https://github.com/center-for-threat-informed-defense/attack-workbench-rest-api/issues/28).

## 19 January 2021

### ATT&CK Workbench version 0.1.0

#### New Features in 0.1.0

-   Created object view pages for matrix, technique, tactic, mitigation, group, and software objects.
-   Added the ability to browse and import collection indexes.
    -   Collection indexes can be imported via URL.
    -   A preview of the collection index is shown before confirming the import.
-   Added the ability to import, view, and subscribe to collections.
    -   Collections listed within an index can be subscribed to, which will pull new versions when they are published.
    -   Collections can also be manually imported via URL. When importing, a preview of the collection and its contents is shown before confirming the import. At this step, users can preview the objects in the collection and select which ones they want to import. Changes in the import are displayed relative to the state of the knowledge base similar to the update pages on the [ATT&CK Website](https://attack.mitre.org/resources/updates/).
    -   An interface provides the ability to review prior imports, which provides a list of changes at the time of the import identical to that shown during the import of the collection.

repository: euschang/attack-workbench-frontend

repo_name: euschang/attack-workbench-frontend