text:
# Gridlock

A responsive CSS grid system. Part of the Formstone Library.

- [Demo](http://formstone.it/components/Gridlock/demo/index.html)
- [Documentation](http://formstone.it/gridlock/)

#### Bower Support
`bower install Gridlock`

---

## Usage

Gridlock works by nesting 'cells' within 'rows'. Cells are defined by classes that set widths at specific breakpoints. The breakpoints  correspond to general screen sizes. By default, Gridlock renders 3 columns on mobile, 6 columns on tablet and 12 columns on desktop.

### Markup

A basic example may look something like:

```
<body class="gridlock">
	<div class="row">
		<div class="mobile-3 tablet-2 desktop-4">...</div>
		<div class="mobile-3 tablet-2 desktop-4">...</div>
		<div class="mobile-3 tablet-2 desktop-4">...</div>
	</div>
</body>
```

This will create 3 cells that each span 3 columns on mobile, 2 columns on tablet and 4 columns on desktop screen sizes. You can think of the nested structure like a directory tree:

```
gridlock
├─ row
|  ├─ cell
|  |─ cell
|  |  └─ row
|  |     ├─ cell
|  |     └─ cell
|  └─ cell
└─ row
   ├─ cell
   └─ cell
```

### Box-Sizing

Gridlock relies on border-box and includes a global box-sizing reset:

```
*, *:before, *:after {
	-webkit-box-sizing: border-box;
	   -moz-box-sizing: border-box;
	        box-sizing: border-box;
}
```

This will effect every element on the page and can have unexpected results. In the long run it will help speed development by modifying how padding and borders effect the box model calculations. [Learn more about border-box](http://www.paulirish.com/2012/box-sizing-border-box-ftw/).

### Row Widths and Columns Counts

| Name | Screen Size | Row Width | Column Count |
| --- | --- | --- | --- |
| min | smaller than 500px | 300px | 3 |
| mobile | smaller than 740px | 480px | 3 |
| tablet | 740px to 960px | 720px | 6 |
| desktop | 960px to 1220px | 960px | 12 |
| max | larger than 1220px | 1200px | 12 |

### Defining Cells

| Class | Description |
| --- | --- |
| `min-X` | only min size |
| `mobile-X` | both mobile and min sizes |
| `tablet-X` | tablet size |
| `desktop-X` | both desktop and max sizes |
| `max-X` | only max size |
| `all-X` | all sizes |

Cells are defined by the target screen size and column count, relative to it's screen size. For example `mobile-2` will produce a cell spanning 2 of the 3 available columns in the mobile screen size range. Cell classes should be stacked to specify column spans across all screen sizes:

```
<div class="mobile-3 tablet-6 desktop-12">...</div>
```

The `max-X` and `min-X` classes give you an added level of control when targeting the desktop and mobile sizes. For example, you may need a cell to span 2 columns at the larger mobile size, but span the full width at the smallest mobile size:

```
<div class="min-3 mobile-2 ...">...</div>
```

The `all-X` classes give you the ability to create a cell that spans the specified width on all screen sizes (only works with fraction cells):

```
<div class="all-full ...">...</div>
```

### Fraction Cells

You can also use the fraction classes in place of specific column counts:

| Class | Description |
| --- | --- |
| `X-full` | entire row width |
| `X-half` | 1/2 row width |
| `X-third` | 1/3 row width |
| `X-fourth` | 1/4 row width |

### Helper Classes

Helper classes can be added to cells to modify their default behavior in predictable ways.

| Class | Description |
| --- | --- |
| `padded` | Swaps cell margin for padding. Allows backgrounds to touch while maintaining gutters. |
| `contained` | Removes cell margin. Allows backgrounds to touch by removing gutters. |
| `centered` | Centers cell. Useful for centering odd column counts cells. |

### LESS Configuration

Gridlock can also be configured and rebuilt using Grunt. Simply edit the variables found in `/src/fs.gridlock-config.less` before running the default `grunt` process.

| Variable | Default | Description |
| --- | --- | --- |
| **Structure** | | |
| `@class-container` | `gridlock` | Container class |
| `@class-row` | `row` | Row class |
| `@class-contained` | `contained` | Contained helper class |
| `@class-padded` | `padded` | Padded helper class |
| `@class-centered` | `centered` | Centered helper class |
| **Cells** | | |
| `@class-all` | `all` | All cell class |
| `@class-min` | `min` | Min cell class |
| `@class-mobile` | `mobile` | Mobile cell class |
| `@class-tablet` | `tablet` | Tablet cell class |
| `@class-desktop` | `desktop` | Desktop cell class |
| `@class-max` | `max` | Max cell class |
| **Columns** | | |
| `@columns-mobile` | `3` | Mobile column count |
| `@columns-tablet` | `6` | Tablet column count |
| `@columns-desktop` | `12` | Desktop column count |
| **Widths** | | |
| `@width-min` | `300px` | Min row width |
| `@width-mobile` | `480px` | Mobile row width |
| `@width-tablet` | `720px` | Tablet row width |
| `@width-desktop` | `960px` | Desktop row width |
| `@width-max` | `1200px` | Max row width |
| **Breakpoints** | | |
| `@width-break-min` | `320px` | Min break width |
| `@width-break-mobile` | `500px` | Mobile break width |
| `@width-break-tablet` | `740px` | Tablet break width |
| `@width-break-desktop` | `980px` | Desktop break width |
| `@width-break-max` | `1220px` | Max break width |
| **Gutters** | | |
| `@gutter` | `1.0416666666666667%;` | Gutter width |


text:
django-hug
==========================
[![Build Status](https://api.cirrus-ci.com/github/jounderwood/django-hug.svg?branch=master)](https://cirrus-ci.com/github/jounderwood/django-hug)
[![Coverage Status](https://coveralls.io/repos/github/jounderwood/django-hug/badge.svg?branch=master)](https://coveralls.io/github/jounderwood/django-hug?branch=master)

Package for working with Django urls/views and request/response validation in more convenient way.

Inspired by beautiful [hug](https://github.com/timothycrosley/hug).

Powered by awesome [pydantic](https://github.com/samuelcolvin/pydantic).

Getting Started
===================
Simple API building example with django-hug.

In your views module create routes and couple API endpoints.
```python
# views.py
import djhug
from pydantic import PositiveInt

routes = djhug.Routes()

@routes.get('new/<int:year>/')
def simple(request, year, month: int):
    return {"year": year, "month": month}

@routes.get('happy/<int:year>/')
def pydantic_field(request, year, month: PositiveInt = 1):
    return [year, month]
```

In your urls.py specify new endpoints
```python
from .views import routes

urlpatterns = routes.get_urlpatterns()
```

Thats all, now you can make requests to new API endpoints with convenient data validation
```bash
curl http://<IP_ADDRESS>:8000/new/2019/?month=133

>> {"year": 2019, "month": 133}
```

Usage
=====
## Regexp path
You can also use regexp path
```python
@routes.get("(?P<year>[0-9]{4})/", re=True)
def index3(request, year, name: str):
    return {"year": year, "name": name}
```

## Request POST data model
Use `Body` base model to validate whole POST data using whole pydantic Model power

```python
# views.py
import djhug
from pydantic import BaseModel

routes = djhug.Routes(prefix="api")

class RespModel(djhug.Body):
    id: int
    quantity: int

@routes.post("test/")
def view(request, body: RespModel):
    assert isinstance(body, RespModel)
    assert isinstance(body, BaseModel)

    return {"id": body.id}
```

## Camelcase response data and response renderers
You can enable response data camelcase formatting

```python
# views.py
import djhug
from djhug.content_negotiation import json_renderer

routes = djhug.Routes()

@djhug.response.camelcased
@djhug.response.renderer(json_renderer)
@routes.get("api/(?P<year>[0-9]{4})/", re=True)
def api(request, year, name: int, date: datetime):
    loc = locals()
    del loc["request"]
    return {"some_data": 1, **loc}
```
```bash
curl http://<IP_ADDRESS>:8000/api/2000/?name=2&date=2020-10-12T12:00

Content-Type: application/json

{
    "someData": 1,
    "date": "2020-10-12T12:00:00",
    "name": 2,
    "year": "2000"
}
```

## Routes prefix
Specify prefix in Routes object to add prefix to all urls
```python
# views.py
import djhug

routes = djhug.Routes(prefix="api")

@routes.get('<int:year>/')
def api_method(request, year, month: int = 1):
    return {"year": year, "month": month}
```
```bash
curl http://<IP_ADDRESS>:8000/api/2019/

>> {"year": 2019, "month": 1}
```

## Settings
```python
DJHUG_RESPONSE_ADDITIONAL_HEADERS = {"Access-Control-Allow-Origin": "*"}
DJHUG_REQUEST_PARSERS_MODULES = ("dotted.path.to.request_parsers",)
DJHUG_RESPONSE_RENDERERS_MODULES = ("dotted.path.to.response_renderers",)
DJHUG_CAMELCASED_RESPONSE_DATA = False
DJHUG_UNDERSCORED_REQUEST_DATA = False
```

## To start example app
```bash
make venv
source activate
cd example
./manage.py runserver
```

## TODO
* Docs and examples
* Coverage
* Openapi, swagger
* Add exception handler

license: MIT

repository: jounderwood/django-hug

branch_name: refs/heads/master

extension: md

gha_language: Python

gha_license_id: MIT

license_type: permissive

repo_name: jounderwood/django-hug


text:
  Template React Web

    :sparkles: Trying to create a scalable template for React Web applications.

    :building_construction: Under construction.

# :muscle: The project

This repository contains a boilerplate for React web apps started with CRA, to practice and apply what i'm learning.

It is being built based on my studies in frontend, architecture and React, looking for a clean and scalable architecture.

A generic structure that can supply most scenarios.

PS.: Using this repository to apply techniques, tricks and best practices that I'm learning too.

## ⚗ Technologies involved

- Typescript
- Styled Components
- Axios
- Redux
- Redux Saga
- Immer
- Eslint
- Husky
- React Toastify

## :jigsaw: Patterns adopted

- Ducks Modular Redux - https://github.com/erikras/ducks-modular-redux
- Conventional Commits - https://www.conventionalcommits.org/en/v1.0.0/
- Adapter (for third party libraries, to isolate components) - https://refactoring.guru/design-patterns/adapter

## :bicyclist: Road Map

A road map to be incremented everyday.

- [x] Create a common module.
- [x] Absolute paths.
- [ ] Create a identity to use in examples for project (E.g. a cat for NestJS, FooBar for concepts).
- [x] Write a good readme.
- [ ] Create one example of test for each type of content.
- [x] Study a better structure to declare routes.
- [x] Add eslint import helpers.
- [ ] Semantic Versioning.
- [ ] Add commitizen.

## :books: My studies fonts

- Kent C. Dodds Blog - https://kentcdodds.com/blog/
- Book Tao of React - https://alexkondov.com/tao-of-react/
- React documentation - https://reactjs.org/

## :pencil: Contribute

Feel free to open a pull request and suggest anything ☺.

---

	Made with :purple_heart: by me.

repository: luanfonsecap/react-web-template

gha_language: TypeScript

repo_name: luanfonsecap/react-web-template


text:
---
layout: default
---

# 1994-03-04 - Re: Standard for Stenography?

## Header Data

From: Sergey Goldgaber<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: ae94ba90b278dfec6f50f778f3e48c0c58a4db9bbfaa424d1a81b513781b04ea

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1994-03-04 03:01:22 UTC

Raw Date: Thu, 3 Mar 94 19:01:22 PST

## Raw message

```
{% raw  %}From: Sergey Goldgaber<EMAIL_ADDRESS>Date: Thu, 3 Mar 94 19:01:22 PST
To<EMAIL_ADDRESS>Subject: Re: Standard for Stenography?
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

On Thu, 3 Mar 1994<EMAIL_ADDRESS>wrote:

> Sergey writes:
> > I have often heard it said that one should always assume that one's
> > opponent knows everything except one's secret key.  To me, this makes no
> > sense!  If your opponent is good enough and determined enough to get by
> > all the layers of obscurity you may have put up, than its just one more
> > step to getting your secret key.
>
> If your cryptography methods are good enough to withstand an
> opponent who has full documentation of your algorithms and methods,
> lots of funds, and everything except your keys, then you don't
> need to waste your time with all the other stuff.  And if you can't
> protect a couple of keys, it doesn't really matter how much other
> security you have.

I have never heard a serious, reputable claim about the unbreakablity of
an algorithm.  Any newbie that dares to pretend otherwise is promptly
referred to the example of the NSA.  The biggest single purchaser of
computer hardware, and employer of mathematicians.  Dozens of years ahead
of public research and all classified.

The point is, that in the real world, we'll never know if our algorithms
are "good enough to withstand an opponent who has full documentation of
your algorithms and methods lots of funds, and everything except your keys."
This opponent need not be the NSA, per se, BTW.  With "lots of funds"
they may have access to at least some of the NSA's findings.  And, who
knows, the NSA may regularly hire its services out to the highest bidder.

You may trust your encryption alone, but if it ever comes to that, I'll
hide any sensitive information I may have every way I can.

> security-by-obscurity is a naive waste of time,

I still don't see why.

> obscurity-by-obscurity is hard to argue against real clearly :-)
> On the other hand, if your cyphertext looks like random bits anyway,
> it doesn't take a lot to make them invisible.

It certainly lookss like it takes a lot!  The Mimic function seems, to me,
to be the only effective practical steganography application.  Most of the
rest of the informed members of this group seem to be debating the
relative visibility/invisibility of their respective systems.

> The real need is to make your data look like Somebody Else's Problem....

Here's to somebody elese's problems!

> 			Bill
>

Sergey

{% endraw %}
```

## Thread

+ Return to [March 1994](/archive/1994/03)

+ Return to "[Eli Brandt <ebrandt@jarthur.cs.hmc.edu>](/authors/eli_brandt_ebrandt_at_jarthur_cs_hmc_edu_)"
+ Return to<EMAIL_ADDRESS>(Mike McNally)](/authors/m5_at_vail_tivoli_com_mike_mcnally_)"
+ Return to "[Sergey Goldgaber <sergey@delbruck.pharm.sunysb.edu>](/authors/sergey_goldgaber_sergey_at_delbruck_pharm_sunysb_edu_)"
+ Return to "[SINCLAIR  DOUGLAS N <sinclai@ecf.toronto.edu>](/authors/sinclair_douglas_n_sinclai_at_ecf_toronto_edu_)"
+ Return to<EMAIL_ADDRESS><EMAIL_ADDRESS>+1-510-484-6204)](/authors/wcs_at_anchor_ho_att_com_bill_stewart_at_pleasantonca_ncr_com_15104846204_)"

+ 1994-03-04 (Thu, 3 Mar 94 17:34:46 PST) - [Re: Standard for Stenography?](/archive/1994/03/61dc6e1cc08417abe5c7249d0a91a76ac1821b3231e172d501e86d672fddc9f1) -<EMAIL_ADDRESS><EMAIL_ADDRESS>+1-510-484-6204)_
  + 1994-03-04 (Thu, 3 Mar 94 19:01:22 PST) - Re: Standard for Stenography? - _Sergey Goldgaber<EMAIL_ADDRESS>  + 1994-03-04 (Fri, 4 Mar 94 06:57:08 PST) - [Re: Standard for Stenography?](/archive/1994/03/79ce33c3b8c97caf67fb0e312684b9abbd87b0f1bdf4bdc8d6692a333e840211) -<EMAIL_ADDRESS>(Mike McNally)_
    + 1994-03-05 (Fri, 4 Mar 94 22:22:00 PST) - [Re: Standard for Stenography?](/archive/1994/03/3bf82cb846b6e36c3438f651e3c36fe3812a0ea2782da61466d0a0572369b72e) - _Sergey Goldgaber<EMAIL_ADDRESS>      + 1994-03-05 (Fri, 4 Mar 94 23:51:28 PST) - [Re: Standard for SteGAnography](/archive/1994/03/b09c1a852a1e117a545f3e5612b9bb28e6a18ddf52c9a8e8fa4c3731af271cf1) - _Eli Brandt<EMAIL_ADDRESS>        + 1994-03-05 (Sat, 5 Mar 94 00:22:13 PST) - [Re: Standard for SteGAnography](/archive/1994/03/3bdb217c4050708798b6d5f3bb9b5fe7db5b1e7984d30d84075575e76d44d1f8) - _Sergey Goldgaber<EMAIL_ADDRESS>          + 1994-03-05 (Sat, 5 Mar 94 00:59:38 PST) - [Re: Standard for SteGAnography](/archive/1994/03/418366f6b8223a28a4fa906999f22c1679bb8c6bc0a761eb3177741bf758cfd5) - _Eli Brandt<EMAIL_ADDRESS>            + 1994-03-07 (Mon, 7 Mar 94 00:41:15 PST) - [Re: Standard for SteGAnography](/archive/1994/03/2a5ca3fdf09cef53184d19e6eda14afa266c8f62a7dad1ad94a172b63173b786) - _Sergey Goldgaber<EMAIL_ADDRESS>              + 1994-03-07 (Mon, 7 Mar 94 01:03:20 PST) - [Re: Standard for SteGAnography](/archive/1994/03/7a888b9bd3d43ba61b35651fc798c45dbe9ba2e3e736758ab91fe1a8f028fc79) - _Eli Brandt<EMAIL_ADDRESS>        + 1994-03-06 (Sun, 6 Mar 94 07:18:13 PST) - [Re: Standard for SteGAnography](/archive/1994/03/5894b5bb5f3c2743da1e49c03aec0bec61f5ae96ca1807e3a0e5ab4e1b989ffb) - _SINCLAIR  DOUGLAS N<EMAIL_ADDRESS>


text:
# README Project
    [licenses](undefined)
        ## Generate a README file

        ## Table of Content
        - [description](#description)
        - [installation](#installation)
        - [usage](#usage)
        - [licenses](#licenses)
        - [contribution](#contribution)
        - [test](#test)
        - [questions](#questions)
        - [username](#username)

        This project allows people to input their information and it generates a README file with headers and all.
        ## *description*

        undefined
        ## *username*

        Answer all prompted questions
        ## *installation*

        Class assignment
        ## *usage*

        MIT
        ## *licenses*

        Robert Ortiz
        ## *contribution*

        N/A
        ## *test*

        undefined
        ## *email*

        undefined
        ## *screenshot*

repository: RobOrtiz/readme

branch_name: refs/heads/main

repo_name: RobOrtiz/readme


text:
---
layout: default
---

# 1994-05-04 - Re: PC-Expo

## Header Data

From<EMAIL_ADDRESS>(Arsen Ray Arachelian)

To<EMAIL_ADDRESS>(Greg Broiles)

Message Hash: e7a749ca25667416173a7b5f2111d19fda8528d3511ccc5da3503bfbd5039d13

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1994-05-04 02:43:23 UTC

Raw Date: Tue, 3 May 94 19:43:23 PDT

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Arsen Ray Arachelian)
Date: Tue, 3 May 94 19:43:23 PDT
To<EMAIL_ADDRESS>(Greg Broiles)
Subject: Re: PC-Expo
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text

> If it looks like you're really going to do this, I'll send you some $ or
> some disks if you promise to use them for this project.

I've had enough folks volunteer for this in NYC that there's no way I'd
back out.  If you want to send me something I'd rather you send me disks
because I don't have any time to buy them.  Just as many 3.5" HD's as you
can... I'll accept money if you'd rather do it that way, but I want to make
sure it gets used up 100% for the disks.  (I'll be taking a $20 loss in disks
and about $100 in taking the day off, if my boss decides not to pay me
for the day off...)

> Sandy Sanfort (I think) said a few weeks ago that he's writing an article
> for Soldier of Fortune about PGP and privacy; perhaps he'd give you
> permission to use that.

That would be most cool.  Sandy, is you reading this?

> I wrote up a short (~ 2 pages, I think) article a few months ago for
> someone who wanted to hand out something printed; I'll poke around and
> see if I can dig it up. It wasn't anything special, or anything that anyone
> else who's been on the list > 3 months couldn't have written.

Please, anything you can scrounge together or revise.  Also I'd reccomend that
you quote from current magazine articles and mention them.  This way they can
seem more offical media-looking...

> You might see if there are pieces you could steal from the PGP docs; they
> did a fair job of explaining lots of the issues, as I remember it.

I won't include any extra docs or source code.  No room on one disk :-(

> Like someone on the list suggested, you might think about handing out
> Mac disks, too - I'm not familiar enough with PC Expo to know if they
> mean "IBM PC" when they say "PC". If that's the case, there may not
> be much demand for Mac stuff. :)

I may do this if I have the time.  I have a Mac, but not much time on my
hands anymore... Maybe I'll bring a few Mac disks just incase....

> With respect to copyright, remember that everything* created is born
> copyrighted; net-news postings, E-mail, newspaper articles, and everything
> else. An author must take affirmative steps to make it public domain.
> You're probably safest if you stick to articles explicitly written
> for this project, or ones where you have permission to reprint. I
> wouldn't be surprised if sympathetic folks/organizations (Wired, John
> Perry Barlow, Whole Earth Review) will grant permission if you ask.
>
> (* where "everything" == original works of authorship fixed in a
> tangible medium of expression)

The Wired JackBoots article is freely distributable, so that will go on there. :-)

{% endraw %}
```

## Thread

+ Return to [May 1994](/archive/1994/05)

+ Return to "["Alan (Miburi-san) Wexelblat" <wex@media.mit.edu>](/authors/alan_miburisan_wexelblat_wex_at_media_mit_edu_)"
+ Return to<EMAIL_ADDRESS>(Arsen Ray Arachelian)](/authors/rarachel_at_prism_poly_edu_arsen_ray_arachelian_)"

+ _Unknown thread root_
  + 1994-05-04 (Tue, 3 May 94 19:43:23 PDT) - Re: PC-Expo -<EMAIL_ADDRESS>(Arsen Ray Arachelian)_
    + 1994-05-06 (Thu, 5 May 94 18:36:04 PDT) - [PC-Expo](/archive/1994/05/f6d82d064267bd4fd50b3208cb7b1df5882a047f1bb1f8a0bc6668e1460a28b9) - _"Alan (Miburi-san) Wexelblat"<EMAIL_ADDRESS>


text:
# Array-Leader
Array Leader Assessment

Integers K, M and a non-empty array A consisting of N integers, not bigger than M, are given.

The leader of the array is a value that occurs in more than half of the elements of the array, and the segment of the array is a sequence of consecutive elements of the array.

You can modify A by choosing exactly one segment of length K and increasing by 1 every element within that segment.

The goal is to find all of the numbers that may become a leader after performing exactly one array modification as described above.

Write a function:

class Solution { public int[] solution(int K, int M, int[] A); }

that, given integers K and M and an array A consisting of N integers, returns an array of all numbers that can become a leader, after increasing by 1 every element of exactly one segment of A of length K. The returned array should be sorted in ascending order, and if there is no number that can become a leader, you should return an empty array. Moreover, if there are multiple ways of choosing a segment to turn some number into a leader, then this particular number should appear in an output array only once.

For example, given integers K = 3, M = 5 and the following array A:

  A[0] = 2
  A[1] = 1
  A[2] = 3
  A[3] = 1
  A[4] = 2
  A[5] = 2
  A[6] = 3
the function should return [2, 3]. If we choose segment A[1], A[2], A[3] then we get the following array A:

  A[0] = 2
  A[1] = 2
  A[2] = 4
  A[3] = 2
  A[4] = 2
  A[5] = 2
  A[6] = 3
and 2 is the leader of this array. If we choose A[3], A[4], A[5] then A will appear as follows:

  A[0] = 2
  A[1] = 1
  A[2] = 3
  A[3] = 2
  A[4] = 3
  A[5] = 3
  A[6] = 3
and 3 will be the leader.

And, for example, given integers K = 4, M = 2 and the following array:

  A[0] = 1
  A[1] = 2
  A[2] = 2
  A[3] = 1
  A[4] = 2
the function should return [2, 3], because choosing a segment A[0], A[1], A[2], A[3] and A[1], A[2], A[3], A[4] turns 2 and 3 into the leaders, respectively.

Write an efficient algorithm for the following assumptions:

N and M are integers within the range [1..100,000];
K is an integer within the range [1..N];
each element of array A is an integer within the range [1..M].


text:
# BsodSimulator 蓝屏模拟器
A UWP program to customize your bug check experience.

一个自定义蓝屏的UWP程序

Build for fun and some extents of exercising on XAML layout.

一方面为了好玩，另一方面作为XAML布局的练习

Support for GSOD(green screen of death) which is available in build 15002 is included.

支持预览版15002的绿屏

Have fun 😋

玩得愉快 😋

### Changelog 更新记录

 1.2.0 [2017.9.23]

Fix a issue cause customization not showing on BSOD page after enting BSOD page multiple times.

修复多次进入蓝屏页面后自定义文本不显示的问题。

QRCode use selected color as foreground and  contains the link in URL field. Use a QRCode reader see for yourself.

生成的二维码使用选中的颜色作为前景色，并且用URL文本框中的链接作为内容。你可以扫码试一试

[![StoreLink](BsodSimulator/Assets/Store.png)](https://www.microsoft.com/store/apps/9nm26dl0v2b6)

---

![Custom](BsodSimulator/Assets/Custom.PNG)
===
![GSOD](BsodSimulator/Assets/GSOD.PNG)

repository: Berrysoft/BsodSimulator

repo_name: Berrysoft/BsodSimulator


text:
# Numpy
 Numpy Tutorials
 Link to official documentation : https://numpy.org/doc/stable/reference/

   **NumPy** (short for Numerical Python) provides an efficient interface to store and operate on dense data buffers. In some ways, NumPy arrays are like Python's built-in list type, but NumPy arrays provide much more efficient storage and data operations as the arrays grow larger in size.
   NumPy arrays form the core of nearly the entire ecosystem of data science tools in Python, so time spent learning to use NumPy effectively will be valuable no matter what aspect of data science interests you.

   Here are the top four benefits that NumPy can bring to your code:

**More speed:** NumPy uses algorithms written in C that complete in nanoseconds rather than seconds.
**Fewer loops:** NumPy helps you to reduce loops and keep from getting tangled up in iteration indices.
**Clearer code:** Without loops, your code will look more like the equations you’re trying to calculate.
**Better quality:** There are thousands of contributors working to keep NumPy fast, friendly, and bug free.

Because of these benefits, NumPy is the de facto standard for multidimensional arrays in Python data science, and many of the most popular libraries are built on top of it. Learning NumPy is a great way to set down a solid foundation as you expand your knowledge into more specific areas of data science.

## Useful References

https://numpy.org/doc/

https://numpy.org/doc/stable/user/theory.broadcasting.html#array-broadcasting-in-numpy

https://realpython.com/how-to-use-numpy-arange/

https://www.youtube.com/watch?v=dEzyaIh-7hs - Video tutorial

https://www.youtube.com/watch?v=vN5dAZrS58E - Video tutorial

https://numpy.org/

repository: anushka-DS/NUMPY

repo_name: anushka-DS/NUMPY


text:
# Galvanize Group Project Proposal

## Team Name
SHOOK

## Group Members
Justin Hart, Izabela Louw, Tom Jones, Tristan Gilford

## Project/Application Name
SHOOK

## Project Description
Keeping people honest since 2017. A web app designed to document the terms of bets/challenges to ensure neither party disagrees upon completion.

## Who uses it?
Anyone that enjoys challenges and has a poor or "convenient" memory (especially drunk people).

## What outputs do they need?
A documented challenge with specific terms.
STRETCH: automate the calculation of who actually won/lost

## What inputs are needed to generate those outputs?
* Sign up (new users) || sign in (registered users)

[There are two different ways to create a new challenge]:

1. Create challenge on the website
    * Define a registered opponent (optional)
    * Completed form with challenge/bet details
        * Start/end dates
        * Challenge type
        * Terms
        * Comments

2. Create challenge via Twitter Bot API
    * Tweet the challenge to opponent using #SHOOK
    * Opponent accepts by responding with message using #SHOOK

## What technologies do you plan to use?
* Express
* Knex.js
* node.js
* Postgresql
* Psql
* HTML
* CSS
* JavaScript
* jQuery
* Handlebars
* Heroku
* AWS
* AJAX
* wireframe.cc
* draw.io
* Twitter API

## Feature list
* App Info
* Sign up
* Sing in
* Create Profile
* Edit Profile
* Place bet
* Bets by category
* Generate new challenge via Twitter using #SHOOK
* Set date of Bet
* Define who you are betting
* Set odds/line of sports bets
* Able to list other details of bet
* Win/Loss evaluation
* Accumulate points
* Confirmation message
* Ability to challenge yourself
* Active bets tracker
* Bet history
* Generate random challenge

repository: sixgun-bridal/shook

repo_name: sixgun-bridal/shook


text:
# InfluxDB

1,000,000 6.1M WAL, data folder is empty

````
⇒  xkb --limit points --target influxdb
log:
  level: info
  color: true
  source: false
mode: local
loader:
  target: influxdb
  reporter: basic
  limitBy: points
  points: 1000000
  series: 100
  time: 10
  workerNum: 10
  workerTimeout: 30
generator:
  timeInterval: 1
  timeNoise: false
  pointsPerSeries: 100
  numSeries: 10
targets:
  influxdb:
    host: localhost
    port: 8086
    url: write?db=xb
    timeout: 30
  xephonk:
    host: localhost
    port: 2333
    url: write
    timeout: 30
  kairosdb:
    host: localhost
    port: 8080
    url: api/v1/datapoints
    timeout: 30
Do you want to proceed? [Y/N]y
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0011] worker started pkg=k.bench.worker
INFO[0029] generator stopped after 1000000 points pkg=k.bench
INFO[0029] close data channel pkg=k.bench
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] worker finished by input channel pkg=k.bench.worker
INFO[0029] basic report finished by channel pkg=k.bench.reporter
Total: 10000
0.0058959335000000005
0.009159969666666668
0.011229679
0.013282145
0.015270097005449566 	 ..............
0.016677509277120688 	 ...........................................................
0.018215746064766215 	 ...............................................................................
0.019876091
0.02079301199631902 	 ................................
0.023975321691131493 	 ......
0.02617547595833334 	 .
0.027930318166666666
0.030007455722222225
0.0320365560506329 	 .
0.033529532788235276 	 .
0.035604549571428584
0.037761762250000004
0.03995495111764706
0.04229246
0.055023617
INFO[0030] run time 18.733643 s pkg=k.bench.reporter
INFO[0030] total request 10000 pkg=k.bench.reporter
INFO[0030] fastest 5892809 pkg=k.bench.reporter
INFO[0030] slowest 55023617 pkg=k.bench.reporter
INFO[0030] total request size 47000000 pkg=k.bench.reporter
INFO[0030] toatl response size 0 pkg=k.bench.reporter
INFO[0030] 204: 10000 pkg=k.bench.reporter
INFO[0030] bench finished pkg=k.cmd.bench
````

10,000,000  1.8 M

````
root@329e05187d49:/var/lib/influxdb/data/xb/autogen/2# du -sh *
1.5M	000000004-000000003.tsm
332K	000000005-000000001.tsm
````

````
⇒  xkb --limit points --target influxdb
log:
  level: info
  color: true
  source: false
mode: local
loader:
  target: influxdb
  reporter: basic
  limitBy: points
  points: 10000000
  series: 100
  time: 10
  workerNum: 10
  workerTimeout: 30
generator:
  timeInterval: 1
  timeNoise: false
  pointsPerSeries: 1000
  numSeries: 10
targets:
  influxdb:
    host: localhost
    port: 8086
    url: write?db=xb
    timeout: 30
  xephonk:
    host: localhost
    port: 2333
    url: write
    timeout: 30
  kairosdb:
    host: localhost
    port: 8080
    url: api/v1/datapoints
    timeout: 30
Do you want to proceed? [Y/N]y
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0003] worker started pkg=k.bench.worker
INFO[0023] generator stopped after 10000000 points pkg=k.bench
INFO[0023] close data channel pkg=k.bench
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] worker finished by input channel pkg=k.bench.worker
INFO[0023] basic report finished by channel pkg=k.bench.reporter
Total: 10000
0.006332456714285712
0.011334941534883722
0.0152038685
0.01617709979157388 	 ..................................................................................................
0.019085289336168654 	 ......................................................
0.021819765044131394 	 .....................
0.025140076313765188 	 .........
0.028374251141078836 	 ....
0.031259074407035146 	 ...
0.03442091589719627 	 ..
0.03699015820895522 	 .
0.0399347663125
0.04243660850000001
0.045809186999999994
0.050121871307692314
0.05558600208333333
0.061915671000000005
0.06706112425
0.076331226
0.0790071195
INFO[0024] run time 19.655630 s pkg=k.bench.reporter
INFO[0024] total request 10000 pkg=k.bench.reporter
INFO[0024] fastest 4459598 pkg=k.bench.reporter
INFO[0024] slowest 79678882 pkg=k.bench.reporter
INFO[0024] total request size 470000000 pkg=k.bench.reporter
INFO[0024] toatl response size 0 pkg=k.bench.reporter
INFO[0024] 204: 10000 pkg=k.bench.reporter
INFO[0024] bench finished pkg=k.cmd.bench
````

100,000,000 19M

- tar -czf a.tar.gz *.tsm

````
root@816048fc9f7e:/var/lib/influxdb/data/xb/autogen/2# du -sh *
15M	000000032-000000005.tsm
2.2M	000000036-000000003.tsm
1.1M	000000038-000000002.tsm
488K	000000039-000000001.tsm
2.2M	a.tar.gz
````

````
⇒  xkb --limit points --target influxdb
log:
  level: info
  color: true
  source: false
mode: local
loader:
  target: influxdb
  reporter: basic
  limitBy: points
  points: 100000000
  series: 100
  time: 10
  workerNum: 10
  workerTimeout: 30
generator:
  timeInterval: 1
  timeNoise: false
  pointsPerSeries: 10000
  numSeries: 10
targets:
  influxdb:
    host: localhost
    port: 8086
    url: write?db=xb
    timeout: 30
  xephonk:
    host: localhost
    port: 2333
    url: write
    timeout: 30
  kairosdb:
    host: localhost
    port: 8080
    url: api/v1/datapoints
    timeout: 30
Do you want to proceed? [Y/N]y
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0008] worker started pkg=k.bench.worker
INFO[0072] generator stopped after 100000000 points pkg=k.bench
INFO[0072] close data channel pkg=k.bench
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] worker finished by input channel pkg=k.bench.worker
INFO[0072] basic report finished by channel pkg=k.bench.reporter
Total: 10000
0.02547461117073171
0.031097282741052626 	 .........
0.03665486298137381 	 .................
0.042203592756335215 	 ....................
0.04817877791572606 	 ..........................
0.05572437511756023 	 ........................................
0.06319053637218329 	 .........................
0.06934404148698481 	 ..................
0.07529120360185178 	 ...............
0.08208258025285177 	 ..........
0.08906499071720102 	 ......
0.09612240634000006 	 ....
0.10460719207407412 	 ..
0.11306831372000001 	 .
0.12126799583333335
0.12983624591666668
0.140761655
0.15038328033333334
0.17062228799999998
0.179243064
INFO[0073] run time 63.458617 s pkg=k.bench.reporter
INFO[0073] total request 10000 pkg=k.bench.reporter
INFO[0073] fastest 20303930 pkg=k.bench.reporter
INFO[0073] slowest 179243064 pkg=k.bench.reporter
INFO[0073] total request size<PHONE_NUMBER> pkg=k.bench.reporter
INFO[0073] toatl response size 0 pkg=k.bench.reporter
INFO[0073] 204: 10000 pkg=k.bench.reporter
INFO[0073] bench finished pkg=k.cmd.bench
````

repository: xephonhq/xephon-k

gha_language: Go

repo_name: xephonhq/xephon-k


text:
# bpmotd -- BPM of the day

Are you building a user interface and struggling to find just the right time interval for a flashing light, a repeated beep, a vibration pattern, or anything else with periodic behaviour?

Not only that, but you also love music?

Let this little library choose the right tempo for you!

Every day (at UTC midnight), it generates a pseudorandom tempo between 80 and 159 BPM inclusive.

If enough people use this, everything around you will flash, beep, or vibrate at the same tempo, which will be extremely beautiful.

Example usage:

```
const { getBPMForDay, getBPMForToday } = require('./bpmotd');

console.log(getBPMForDay('2021-08-26'));
console.log(getBPMForToday());
```

repository: mglch/bpmotd

repo_name: mglch/bpmotd


text:
---
title: Streaming Video with Sia (Live Demo)
comments: true
hide_description: true
layout: post
description: A preview of some neat things you can do with the streaming feature of
  Sia 1.3.3
tags:
- sia
- docker
image: "/images/2018-05-08-sia-streaming-preview/streaming-preview.png"
---

File streaming is the headline feature of Sia's next release. Users will be able to stream files over HTTP, whereas previously they had to fully download their files to disk in order to access them.

The key limitation is that streaming only works within the local system. Sia can't, for instance, serve videos to a web page.

Or rather, Sia can't do this *natively*. Using Docker and the Sia 1.3.3 release candidate, I created a server that streams my files from Sia to any place I want.

Below, you'll find embedded videos that I'm serving directly from my Sia node.

# Setting up remote streaming

## Requirements

The only software you'll need to follow my examples is Docker.

[Docker Community Edition](https://store.docker.com/search?offering=community&type=edition) is available for free on all major OSes.

## Files

You'll need to download just two files, which I'll explain in turn:

### docker-compose.yml

{% include files.html title="docker-compose.yml" language="yml" %}

This file tells Docker to set up a network of three containers to support my streaming solution.

Obviously, there's a container for Sia, which runs the 1.3.3 release candidate.

The next container is for [nginx](https://nginx.org/en/), which I use as a reverse proxy to connect external HTTP requests to Sia.

Finally, there's the Sia metrics collector. That one is optional and just captures metrics about Sia that you can visualize by following [these instructions](https://github.com/mtlynch/sia_metrics_collector).

### nginx.conf

{% include files.html title="nginx.conf" language="text" %}

This is the configuration file for nginx. It listens on port 80, the default port for HTTP traffic. When it receives an HTTP request for a path like `/foo/bar.mp4`, it forwards the request to the Sia node and rewrites the path to `http://sia:9980/renter/stream/foo/bar.mp4`, which is Sia's [streaming download endpoint](https://github.com/NebulousLabs/Sia/blob/master/doc/API.md#renterstreamsiapath-get).

It's worth noting that Sia runs many endpoints on port 9980, many of which are sensitive APIs that you shouldn't expose publicly. The APIs for sending funds or displaying your wallet seed run on the same port, for example. The configuration above protects the Sia node by only exposing the `/renter/stream` API and keeping every other sensitive endpoint inaccessible externally.

## Starting your node

Starting your streaming Sia node requires just five shell commands:

```bash
# Create directories for Sia.
mkdir sia-streaming && cd sia-streaming
mkdir sia-data uploads metrics

# Download the necessary files.
wget https://blog.spaceduck.io/files/sia-streaming-preview/docker-compose.yml
wget https://blog.spaceduck.io/files/sia-streaming-preview/nginx.conf

# Start the Docker containers
docker-compose up --detach
```

## Interacting with Sia

You can interact with Sia through the `siac` command-line client within the container to perform any standard actions:

```bash
$ docker exec -it sia ./siac version
Sia Client
        Version 1.3.2
        Git Revision 6cf56381
        Build Time   Thu May  3 15:49:46 UTC 2018
Sia Daemon
        Version 1.3.2
        Git Revision 6cf56381
        Build Time   Thu May  3 15:49:46 UTC 2018
```

To start streaming, you need to create a Sia wallet and fund it with at least 500 SC (this is left as an exercise to the reader).

You then need to create renter contracts. I created contracts through the command below. It's a bit unusual because I'm choosing very short contracts to match my VPS's one-month lifetime.

```bash
docker exec -it sia ./siac renter setallowance 5KS 30d 50 288b
```

Next, you'll need to upload files. Any file you place in the `./uploads` directory on your host will appear within your Sia container under the `/sia-uploads` path. Here are the commands I used to upload a few video files:

```bash
docker exec -it sia ./siac renter upload \
  /sia-uploads/big_buck_bunny_480p_surround-fix.mp4 \
  /big_buck_bunny_480p_surround-fix.mp4

docker exec -it sia ./siac renter upload \
  /sia-uploads/bbb_sunflower_1080p_60fps_normal.mp4 \
  /bbb_sunflower_1080p_60fps_normal.mp4

docker exec -it sia ./siac renter upload \
  /sia-uploads/bbb_sunflower_2160p_60fps_normal.mp4 \
  /bbb_sunflower_2160p_60fps_normal.mp4
```

I'm keeping the files on the Sia network, so it wouldn't be very exciting if I had to keep all the files locally as well. Once `siac renter -v` showed that my files were 100% uploaded to Sia, I deleted the local copies from my host:

```bash
rm uploads/*
```

# Live demo

I set up a demo below where you can stream the short film *Big Buck Bunny*  **directly from my Sia node**.

Click one of the "Play" buttons and a video player will pop up below:

| Filename | Resolution | File size | Watch |
|------------|------------|---------------|---|
| [big_buck_bunny_480p_surround-fix.mp4](http://streamingdemo.spaceduck.io/big_buck_bunny_480p_surround-fix.mp4) | 480p | 151 MB | <input type="submit" value="Play" id="load480p"> |
| [bbb_sunflower_1080p_60fps_normal.mp4](http://streamingdemo.spaceduck.io/bbb_sunflower_1080p_60fps_normal.mp4) | 1080p | 356 MB | <input type="submit" value="Play" id="load1080p"> |
| [bbb_sunflower_2160p_60fps_normal.mp4](http://streamingdemo.spaceduck.io/bbb_sunflower_2160p_60fps_normal.mp4) | 2160p | 673 MB | <input type="submit" value="Play" id="load2160p"> |

Click one of the "Play" buttons above to watch.

***Note**: The streaming feature is not meant to support streaming to multiple clients at once. Expect to see very long load times and timeouts.*

The server is an [Afterburst Mini KVM](https://afterburst.com/unmetered-kvm-vps) with 2 CPU cores, 2 GB of RAM, and 1 Gbps network. I rented the server for one month and loaded my Sia wallet with 5000 SC, so I’ll let it run until people download enough to exhaust my renter contracts or until my VPS month ends. I'm [collecting metrics](https://github.com/mtlynch/sia_metrics_collector) on Sia's spending, so I'll update if anything neat emerges from that.

# Stream whatever you want

Video and audio are the most useful types of files to stream because they allow you to skip around the file, but Sia can stream files of any type.

I copied the PDF of my [Sia Load Test](/load-test-wrapup/) plan to my Sia node as well, so you can download that via the URL below:

* [http://streamingdemo.spaceduck.io/load-test-plan-2018-02-14.pdf](http://streamingdemo.spaceduck.io/load-test-plan-2018-02-14.pdf)

# Don't get too excited yet

When people hear that Sia will offer video streaming, they think that it's going to be some sort of decentralized, censorship-free YouTube. That's not what this is.

The server is still the single-point of failure. When I shut off the VPS at the end of the month, the video demos above will stop playing. If I streamed something illegal, authorities could track down the server and seize it just like any other site.

Sia does indeed stream videos, but if all you wanted to do was stream a few videos from a web server, there are far easier ways to do it.

What's interesting about Sia's streaming feature is how it allows you to trade resource constraints. There are four main resources that a video streaming provider typically cares about (in descending order of importance):

1. Network bandwidth
1. Compute power
1. Memory
1. Storage

Sia's streaming feature increases network bandwidth because it has to download data from hosts, then send data to the user's browser. It increases compute and memory consumption because it also needs to rejoin and decrypt each data shard.

The advantage Sia offers is its low storage footprint. You could theoretically set up Sia to serve ~5 TB of files on a server that has only 50 GB of local storage. An example use-case might be a site that has a very large catalog of videos which users don't access very frequently (e.g., [The Internet Archive](https://archive.org/)).

# Okay, you can get a little excited

Sia is advertising the video streaming aspect of this feature because that's the most tangible use-case. If you're thinking ahead, the *really* exciting part is how it facilitates software integrations with Sia.

Prior to 1.3.3, applications could only download files from Sia if they ran on the same system. That's a crippling limitation, as most apps expect to integrate with storage backends over the network, not through the filesystem.

Download streaming brings Sia closer to the point where applications can communicate with Sia entirely over the network. It's not quite there yet because Sia doesn't yet support upload streaming, but downloads get it halfway there.

# Acknowledgments

Thanks to Christoph Schaefer, who created [the first tutorial](https://medium.com/@chrsch79/stream-video-from-sia-network-bc9e2d5d9daa) for Sia's video streaming feature. His post showed me how to use the feature and inspired me to extend it in this post.

repository: mtlynch/spaceduck

gha_language: HTML

repo_name: mtlynch/spaceduck


text:
# Starbucks Customer Type Clusters

Exploratory data analysis of Starbucks customers and grouping them into clusters.

You can see my blog post for this project here: https://blog.saucloud.com/starbucks-customer-types-a-data-scientist-overview-cjy7qd76i001qras1dmaj93sa

# Project Overview
The Starbucks customer types is my capstone project for the Udacity Data Scientist Nanodegree. This data was provided by Starbucks to simulate their customers and transactions to see if there are better approaches to sending customers specific promotional deals.

My motivation for this project is that I really enjoy analysis and predicting projects and I had never done any type of clustering project with scenario data before, so I really wanted to get out of my comfort zone for this one. I also enjoy finding information about businesses that would typically not be viewed as important and taking more of a statistical approach to solving a problem that wouldn't use traditional statistics. I love problem solving, and not having any definitive end result gave me the freedom to solve a problem any way that I could find out.

The different files that were used to create this project are located in the Profile Portfolio and Transcript Data.zip file. Here is a quick overview of each file:
1. Profile - Dimensional data about each person, including their age, salary, and gender. There is one unique customer for each record.
2. Portfolio - Information about the promotional offers that are possible to receive, and basic information about each one including the promotional type, duration of promotion, reward, and how the promotion was distributed to customers
3. Transcript - Records show the different steps of promotional offers that a customer received. The different values of receiving a promotion are receiving, viewing, and completing. You also see the different transactions that a person made in the time since he became a customer. With all records, you see the day that they intereacted with Starbucks and the amount that it is worth.

One important segment of any business is to look for areas that can be improved to save money or create more revenue. I was determined to look to see how well certain promotions were being used by all customers and to try and see what was a more effective method to offering promotions. Once I could see how people normally reacted, the problem then became to find a better way to make sure that the right people were receiving the right promotions.

I used exploratory analysis to see what type of customers existed in the Starbucks universe, their transaction / promotional engagement habits, and created a customer matrix dataframe that gae the whole view of what type of customer they were. The best machine learning approach was then to use a clustering method that could break up customers into different segments that would respond differently to different promotional deals.

By doing this, Starbucks can allocate their promotional deals in a more effective manner. People who come back on a regular basis dont need buy one get one free deals, but should receive discount deals. People who might not be able to afford coming into Starbucks stores at a constant basis or don't go regularly for their own reasons should be given BOGO deals to reengage their interests in Starbucks and make them a more reliable customer.

My results showed that Starbucks customers fall into 4 different categories based on mostly their income and the number of times they interact with Starbucks. There are 2 clusters that come consistantly to Starbucks that don't need to receive buy one get one free offers and should only receive discounted promotions. That way those customers still feel rewarded for being a customer, while Starbucks saves some money that they were giving away to them when they didn't have to. The other 2 clusters are groups of people who should be offered more buy one get one free promotions.  These customers might not be able to afford coming into Starbucks stores at a constant basis or don't go regularly for their own reasons should be given BOGO deals to reengage their interests in Starbucks and make them a more reliable customer.

# Profile Portfolio and Transcript Data folder contain

Three JSON files that show profiles of customers, promotional deals that are offered, and the transaction history of customers.

portfolio.json

- id (string) - offer id
- offer_type (string) - type of offer ie BOGO, discount, informational
- difficulty (int) - minimum required spend to complete an offer
- reward (int) - reward given for completing an offer
- duration (int) - UNKNOWN
- channels (list of strings)

profile.json

- age (int) - age of the customer
- became_member_on (int) - date when customer created an app account
- gender (str) - gender of the customer (note some entries contain 'O' for other rather than M or F)
- id (str) - customer id
- income (float) - customer's income

transcript.json

- event (str) - record description (ie transaction, offer received, offer viewed, etc.)
- person (str) - customer id
- time (int) - time in hours. The data begins at time t=0
- value - (dict of strings) - either an offer id or transaction amount depending on the record

# Starbucks Capstone Project.ipynb
Jupyter Notebook that shows the start to finish of the this project. This starts with data cleanup and exploration, top level statsitics of customers and their transactions, and cluster analysis for better approaches of sending customers promotions.

# Requirments :

- python 3.6 or above.
- Pandas 0.23.2 or above.
- seaborn.
- numpy.
- matplotlib.
- sklearn.

License:

BSD 3-clause


text:
 Ah yes, another TODO program (but in Haskell!)

That's about it. A to-do program written in Haskell. I know my code is weird, and you're welcome to
crack your head through it (otherwise I'll do it myself eventually).

# Installation

After pulling this repository,
```
$ cabal install
```

# Usage

## Commands

Todo can be run just with
```
todo
```
This will launch the interactive mode of the program.

Todo also supports CLI parameters. Here they are:
```
todo [add/remove/view] [filename] [parameter for first argument]
```

WARNING: Currently, TODO only supports filenames ending with `.txt`, otherwise your filename will be treated as a TODO and be added
to the default list!

Todo uses the file `~/.config/todo.txt` as default. The main commands are:

```
todo add         #Adds TODOs to your list.
todo view        #Prints out your todo list.
todo remove      #Removes TODOs from your list.
todo version     #Prints out version.
todo help        #Prints out help message.
```

These commands are self-explanatory.

## Subcommands

### Add
The parameters for add are just the filename and things you want to add to your TODO list.

For example
```
todo add "Say hello to the world"
```
Will add "Say hello to the world" to your default TODO list.

To add your TODO to a different file (you guessed it):

```
todo add helloworld.txt "Say hello to the world"
```

This will create a helloworld.txt file in the current directory if it doesn't exist, otherwise add the string to your list.

You can also add multiple TODOs with a single command like this:
```
todo add "Foo" "Bar" "Baz"
```

### Remove
The parameters for remove are the filename, and the number at which the to-be-removed TODO is at,
and/or a simple phrase that the to-be-removed TODO contains.

An example with indexes as the parameter:

An example with keywords as the parameter:

You can also combine both types of parameters:
```
todo remove "Foo" 1
```

### View

View only takes filenames as the parameter.

# Contributing

Feel free to contribute anything at all, if you feel like cracking your head over
a trivial project is what you want.

repository: Axarva/todo

gha_language: Haskell

repo_name: Axarva/todo


text:
### What should you be prepared for in Project Review?

During your project review, be prepared to:

1.  Explain your code from execution point to exit point. Use the best technical vocabulary you can.

2.  Live code. This could be refactoring, adding a new feature, or both.

3.  Answer questions about your knowledge of JavaScript Fundamentals.

In particular, the JavaScript Fundamentals concepts your reviewer may ask about include:
* variables
* data structures
* functions
* hoisting
* scope
* context
* this
* closures
* ES6 syntax
* let, const
* arrow functions
___

### Learning Goals

These are the skills and knowledge that you should aim to demonstrate through the project review.

* Explain how Rails routes a request to a controller and method based on the URL and HTTP verb

* Use render json: to render serialized JSON

* Select, Create, and Modify DOM nodes

* Attach listeners to DOM nodes to respond to user interaction

* Use preventDefault to control form submit behavior

* Use fetch with 'GET', 'POST', 'PATCH' & 'DELETE' HTTP methods

* Create a JavaScript object with ES6 class syntax

* Instantiate JavaScript objects and call methods on them.


text:
# PALMIRA

## A Deep Deformable Network for Instance Segmentation of Dense and Uneven Layouts in Handwritten Manuscripts

**_To appear at [ICDAR 2021](https://icdar2021.org/)_**

| **[ [```Paper```](<>) ]** | **[ [```Website```](<https://ihdia.iiit.ac.in/Palmira/>) ]** |
|:-------------------:|:-------------------:|

---

# Dependencies and Installation
The PALMIRA code is tested with
- Python 3.7
- PyTorch 1.7.1
- Detectron2
- CUDA 10.0
- CudNN/7.3-CUDA-10.0

For setup of detectron2, please follow the [official documentation](https://detectron2.readthedocs.io/en/latest/tutorials/install.html)

# Usage
## Training

## Evaluation (w GT)
### Quantitative
### Qualitative - Parsing .json and overlays images

## Inference (wo GT)
### Qualitative

# Visual Results
![visual results](assets/Qualitative.png)

# Citation
```bibtex
@inproceedings{sharan2021palmira,
    title = {PALMIRA: A Deep Deformable Network for Instance Segmentation of Dense and Uneven Layouts in Handwritten Manuscripts},
    author = {Sharan, S P and Aitha, Sowmya and Amandeep, Kumar and Trivedi, Abhishek and Augustine, Aaron and Sarvadevabhatla, Ravi Kiran},
    booktitle = {International Conference on Document Analysis Recognition, {ICDAR} 2021},
    year = {2021},
}
```

# Contact
If you have any question, please contact [Dr. Ravi Kiran<EMAIL_ADDRESS>
# License
This project is open sourced under MIT license.

repository: SowmyaAitha/Palmira

repo_name: SowmyaAitha/Palmira


text:
# dashing.wunderlist

## Preview
![](https://raw.githubusercontent.com/sbaerlocher/dashing.wunderlist/master/wunderlist.png)

## Description

Widget for [Dashing](http://dashing.io/) that shows [Wunderlist](https://wunderlist.com) tasks.

## Usage

Add this to your Gemfile and run `bundle install`:
```bash
gem 'rest-client'
```

To use this widget, copy `wunderlist.html`, `wunderlist.coffee`, and `wunderlist.scss` into a `/widgets/wunderlist` directory, and copy the `wunderlist.rb` file into your `/jobs` folder.

To include the widget in a dashboard, add the following snippet to the dashboard layout file:

```html
<li data-row="1" data-col="1" data-sizex="1" data-sizey="1">
    <div data-id="wunderlist" data-view="Wunderlist"></div>
</li>
```

## Changelog

### 1.2

* add function show all tasks
* add function to a specific list Select

### 1.1

* fix bug in wunderlist.rb

### 1.0

* Initial release

## Contributor

* [Simon Bärlocher](https://sbaerlocher.ch)

## License

This project is under the MIT License. See the [LICENSE](https://sbaerlo.ch/licence) file for the full license text.

## Copyright

(c) 2015, Simon Bärlocher


text:
---
layout: post
rel_link:  "7_2_0_pre7"
title:  "CMSSW_7_2_0_pre7"
date:   2014-10-02 06:44:44
categories: cmssw
relmajor: 7
relminor: 2
relsubminor: 0
relpre: _pre7
---

# CMSSW_7_2_0_pre7
#### Changes since CMSSW_7_2_0_pre6:

[compare to previous](https://github.com/cms-sw/cmssw/compare/CMSSW_7_2_0_pre6...CMSSW_7_2_0_pre7)

1. [5643](http://github.com/cms-sw/cmssw/pull/5643){:target="_blank"}  from **@davidlange6**: Fix sim g4 core generators created: 2014-10-01 19:40:27 merged: 2014-10-01 19:41:35

2. [5273](http://github.com/cms-sw/cmssw/pull/5273){:target="_blank"}  from **@igv4321**: deriving ts5 correction from ts4 `alca`  `db`  created: 2014-09-11 21:31:20 merged: 2014-09-30 19:22:38

3. [5586](http://github.com/cms-sw/cmssw/pull/5586){:target="_blank"}  from **@franzoni**: re-store for GEN relvals the EnableHarvesting in reqmgr  `operations`  created: 2014-09-26 16:28:36 merged: 2014-09-30 19:20:15

4. [5625](http://github.com/cms-sw/cmssw/pull/5625){:target="_blank"}  from **@batinkov**: A script that manages a FU/BU appliance is added. `dqm`  created: 2014-09-30 13:26:47 merged: 2014-09-30 19:19:50

5. [5604](http://github.com/cms-sw/cmssw/pull/5604){:target="_blank"}  from **@mmarionncern**: add JECpayload protection in PhysicsTools/PatUtils/interface/ShiftedJetProducerT.h `analysis`  created: 2014-09-29 07:24:14 merged: 2014-09-29 18:38:39

6. [5610](http://github.com/cms-sw/cmssw/pull/5610){:target="_blank"}  from **@arizzi**: MiniAOD: set track_ as transient in PackedPFCandidate `analysis`  created: 2014-09-29 14:15:22 merged: 2014-09-29 16:16:45

7. [5605](http://github.com/cms-sw/cmssw/pull/5605){:target="_blank"}  from **@Martin-Grunewald**: Fix IB addOn tests `core`  `fastsim`  created: 2014-09-29 07:59:43 merged: 2014-09-29 16:15:53

8. [5530](http://github.com/cms-sw/cmssw/pull/5530){:target="_blank"}  from **@Martin-Grunewald**: HLT update with new menu AND L1 update - 72X `alca`  `core`  `hlt`  `l1`  `operations`  `simulation`  created: 2014-09-24 11:57:11 merged: 2014-09-28 19:11:36

9. [5463](http://github.com/cms-sw/cmssw/pull/5463){:target="_blank"}  from **@franzoni**: Beamspot nominal collision2015 `operations`  `simulation`  created: 2014-09-22 09:09:48 merged: 2014-09-28 10:36:28

10. [5596](http://github.com/cms-sw/cmssw/pull/5596){:target="_blank"}  from **@danduggan**: updates to online dqm configurations needed for global running `dqm`  created: 2014-09-27 05:06:37 merged: 2014-09-28 10:31:19

11. [5581](http://github.com/cms-sw/cmssw/pull/5581){:target="_blank"}  from **@nickmccoll**: Revert new cpe `reconstruction`  created: 2014-09-26 11:42:18 merged: 2014-09-28 10:30:55

12. [5592](http://github.com/cms-sw/cmssw/pull/5592){:target="_blank"}  from **@gartung**: fix for insidious bug that skips function declarations in an extern C  `core`  created: 2014-09-26 18:21:50 merged: 2014-09-27 10:35:17

13. [5446](http://github.com/cms-sw/cmssw/pull/5446){:target="_blank"}  from **@cms-btv-pog**: Added combinedMVABJetTags and removed  combinedSecondaryVertexMVABJetTags from reco sequence, added bugfix for pfTagInfos, updated PAT/miniAOD configs `analysis`  `dqm`  `reconstruction`  created: 2014-09-19 17:39:16 merged: 2014-09-26 15:14:53

14. [5526](http://github.com/cms-sw/cmssw/pull/5526){:target="_blank"}  from **@arizzi**: Same as #5525 (#4914 #4833 #4862 #5037 #5230 plus #5425 and other fixes) MiniAOD related `analysis`  `reconstruction`  created: 2014-09-24 10:02:41 merged: 2014-09-26 11:26:01

15. [5540](http://github.com/cms-sw/cmssw/pull/5540){:target="_blank"}  from **@cms-l1t-offline**: Removed tau bit from non-isolated taus and changed some tau parameters. created: 2014-09-24 14:49:37 merged: 2014-09-26 11:24:03

16. [5572](http://github.com/cms-sw/cmssw/pull/5572){:target="_blank"}  from **@franzoni**: swap over two samples from extendedgen to generator `operations`  created: 2014-09-25 20:30:42 merged: 2014-09-26 06:03:57

17. [5423](http://github.com/cms-sw/cmssw/pull/5423){:target="_blank"}  from **@Sam-Harper**: Ecal regression refactor `analysis`  `reconstruction`  created: 2014-09-18 20:13:03 merged: 2014-09-25 20:03:06

18. [5421](http://github.com/cms-sw/cmssw/pull/5421){:target="_blank"}  from **@dmitrijus**: Forward port for Online DQM from 71X `daq`  `dqm`  created: 2014-09-18 15:56:24 merged: 2014-09-25 18:57:57

19. [5528](http://github.com/cms-sw/cmssw/pull/5528){:target="_blank"}  from **@fruboes**: New HLT jet ptave filter allowing to specify eta ranges for tagging/probeing jet `hlt`  created: 2014-09-24 10:08:40 merged: 2014-09-25 18:57:33

20. [5536](http://github.com/cms-sw/cmssw/pull/5536){:target="_blank"}  from **@apfeiffer1**: make condDBv2 default `alca`  `operations`  created: 2014-09-24 13:05:57 merged: 2014-09-25 18:56:45

21. [5518](http://github.com/cms-sw/cmssw/pull/5518){:target="_blank"}  from **@ebouvier**: cleaning old obsolete DQMOffline top or egamma related files `dqm`  created: 2014-09-24 06:38:14 merged: 2014-09-25 18:55:48

22. [5517](http://github.com/cms-sw/cmssw/pull/5517){:target="_blank"}  from **@ebouvier**: changing iso lepton path names `dqm`  created: 2014-09-24 06:29:08 merged: 2014-09-25 15:31:27

23. [5548](http://github.com/cms-sw/cmssw/pull/5548){:target="_blank"}  from **@jpavel**: Default python values for new parameters introduced with PR 5255 `reconstruction`  created: 2014-09-24 16:28:28 merged: 2014-09-25 12:50:07

24. [5535](http://github.com/cms-sw/cmssw/pull/5535){:target="_blank"}  from **@vadler**: 72X - Fix PAT Egamma ClassVersions for 70X compatibility `analysis`  created: 2014-09-24 13:01:30 merged: 2014-09-25 12:48:56

25. [5481](http://github.com/cms-sw/cmssw/pull/5481){:target="_blank"}  from **@vadler**: 72X-updateRelValInput `analysis`  created: 2014-09-22 18:00:43 merged: 2014-09-25 12:41:19

26. [5529](http://github.com/cms-sw/cmssw/pull/5529){:target="_blank"}  from **@vasile-ghete**: Added L1Menu_Collisions2015_25ns_v1_L1T_Scales_20101224_Imp0_0x102f.xml `l1`  created: 2014-09-24 11:54:24 merged: 2014-09-25 12:40:58

27. [5425](http://github.com/cms-sw/cmssw/pull/5425){:target="_blank"}  from **@rappoccio**: MiniAOD JME changes `analysis`  `reconstruction`  created: 2014-09-18 21:02:23 merged: 2014-09-25 12:38:58

28. [5491](http://github.com/cms-sw/cmssw/pull/5491){:target="_blank"}  from **@franzoni**: RequestType RequestPriority for relval submission `operations`  created: 2014-09-23 08:03:22 merged: 2014-09-25 12:38:03

29. [5550](http://github.com/cms-sw/cmssw/pull/5550){:target="_blank"}  from **@gartung**: ClangSA : Fix for FunctionDumper not reporting function calls inside Root global function declarations `core`  created: 2014-09-24 17:41:35 merged: 2014-09-25 09:52:25

30. [5513](http://github.com/cms-sw/cmssw/pull/5513){:target="_blank"}  from **@davidlange6**: replace import lib with python 2.6 compatible command `analysis`  created: 2014-09-23 19:10:25 merged: 2014-09-24 09:09:38

31. [5524](http://github.com/cms-sw/cmssw/pull/5524){:target="_blank"}  from **@ktf**: Support for clang 3.5 created: 2014-09-24 07:35:00 merged: 2014-09-24 07:35:11

32. [5452](http://github.com/cms-sw/cmssw/pull/5452){:target="_blank"}  from **@Martin-Grunewald**: Big HLT update for 72x `hlt`  `reconstruction`  created: 2014-09-20 13:48:31 merged: 2014-09-23 18:45:48

33. [5407](http://github.com/cms-sw/cmssw/pull/5407){:target="_blank"}  from **@lveldere**: fix out of bound array index in HCalResponse `fastsim`  created: 2014-09-18 11:40:30 merged: 2014-09-23 17:37:15

34. [5401](http://github.com/cms-sw/cmssw/pull/5401){:target="_blank"}  from **@alja**: 72x Merge SLHC TGeo changes `visualization`  created: 2014-09-17 20:56:11 merged: 2014-09-23 17:36:59

35. [5400](http://github.com/cms-sw/cmssw/pull/5400){:target="_blank"}  from **@ggovi**: Fix for L1KeyList migration tools `db`  created: 2014-09-17 20:34:17 merged: 2014-09-23 17:36:47

36. [5440](http://github.com/cms-sw/cmssw/pull/5440){:target="_blank"}  from **@mmarionncern**: 72X TMatrix and TVector replacement with SMatrix and SVector in default MET code `reconstruction`  created: 2014-09-19 12:55:44 merged: 2014-09-23 17:15:48

37. [5447](http://github.com/cms-sw/cmssw/pull/5447){:target="_blank"}  from **@UAEDF-tomc**: Update QGLikelihoodDBWriter to read bins from file `analysis`  created: 2014-09-19 19:41:31 merged: 2014-09-23 17:15:35

38. [5319](http://github.com/cms-sw/cmssw/pull/5319){:target="_blank"}  from **@ianna**: Fix Rotation for RPC Chambers in Ring 4 `geometry`  created: 2014-09-16 16:22:26 merged: 2014-09-23 17:15:04

39. [5284](http://github.com/cms-sw/cmssw/pull/5284){:target="_blank"}  from **@threus**: added validation plots for Strip ALCA `dqm`  created: 2014-09-12 22:03:42 merged: 2014-09-23 17:14:49

40. [5335](http://github.com/cms-sw/cmssw/pull/5335){:target="_blank"}  from **@deguio**: Clean couts validation seq `analysis`  `dqm`  `l1`  created: 2014-09-17 14:29:03 merged: 2014-09-23 17:14:40

41. [5353](http://github.com/cms-sw/cmssw/pull/5353){:target="_blank"}  from **@rappoccio**: Fixing comment for JetDeltaRValueMapProducer `reconstruction`  created: 2014-09-17 19:06:22 merged: 2014-09-23 17:14:15

42. [5412](http://github.com/cms-sw/cmssw/pull/5412){:target="_blank"}  from **@ianna**: Fix Runtime Crashing Issues `geometry`  created: 2014-09-18 13:52:14 merged: 2014-09-23 17:13:54

43. [5437](http://github.com/cms-sw/cmssw/pull/5437){:target="_blank"}  from **@ggovi**: Enabling import of HCAL OOT related types `db`  created: 2014-09-19 10:35:50 merged: 2014-09-23 17:13:36

44. [5469](http://github.com/cms-sw/cmssw/pull/5469){:target="_blank"}  from **@fabozzi**: increase splitting for PU samples; using GEN-SIM from 720_pre6 `operations`  created: 2014-09-22 10:44:18 merged: 2014-09-23 17:13:05

45. [5424](http://github.com/cms-sw/cmssw/pull/5424){:target="_blank"}  from **@davidlt**: Resolve undefined behavior with VLAs length `reconstruction`  created: 2014-09-18 20:25:27 merged: 2014-09-23 17:12:27

46. [5405](http://github.com/cms-sw/cmssw/pull/5405){:target="_blank"}  from **@apfeiffer1**: fix uninitialised var timetype to avoid error from checker `alca`  `db`  created: 2014-09-18 10:08:04 merged: 2014-09-23 17:12:15

47. [5321](http://github.com/cms-sw/cmssw/pull/5321){:target="_blank"}  from **@bendavid**: Ecal multifit optimized `reconstruction`  created: 2014-09-16 18:55:58 merged: 2014-09-23 17:11:47

48. [5337](http://github.com/cms-sw/cmssw/pull/5337){:target="_blank"}  from **@vadler**: 72X - fix division by zero `analysis`  created: 2014-09-17 14:34:04 merged: 2014-09-23 17:11:36

49. [5415](http://github.com/cms-sw/cmssw/pull/5415){:target="_blank"}  from **@cms-btv-pog**: Fix for division by zero in RecoBTag/PerformanceDB `reconstruction`  created: 2014-09-18 14:12:11 merged: 2014-09-23 17:11:07

50. [5427](http://github.com/cms-sw/cmssw/pull/5427){:target="_blank"}  from **@quertenmont**: fix getByLabel `analysis`  created: 2014-09-19 07:45:31 merged: 2014-09-23 17:10:57

51. [5451](http://github.com/cms-sw/cmssw/pull/5451){:target="_blank"}  from **@davidlt**: Remove unused seedsRefs from DuplicateListMerger.cc `reconstruction`  created: 2014-09-20 11:24:48 merged: 2014-09-23 17:10:43

52. [5455](http://github.com/cms-sw/cmssw/pull/5455){:target="_blank"}  from **@davidlt**: DQM/SiStripMonitorDigi: remove unsued subdetswitchtotdigiproflson `dqm`  created: 2014-09-21 09:03:38 merged: 2014-09-23 17:10:28

53. [5458](http://github.com/cms-sw/cmssw/pull/5458){:target="_blank"}  from **@davidlt**: Change Word64 type from long long to unsigned long long `reconstruction`  created: 2014-09-21 10:54:04 merged: 2014-09-23 17:10:06

54. [5459](http://github.com/cms-sw/cmssw/pull/5459){:target="_blank"}  from **@davidlt**: Remove undefined behavior from PixelTrackCleanerBySharedHits.cc `reconstruction`  created: 2014-09-21 11:42:18 merged: 2014-09-23 17:09:43

55. [5304](http://github.com/cms-sw/cmssw/pull/5304){:target="_blank"}  from **@Dr15Jones**: Clang fix problems in L1Trigger/CSCTrackFinder `l1`  created: 2014-09-15 22:01:29 merged: 2014-09-22 13:57:57

56. [5403](http://github.com/cms-sw/cmssw/pull/5403){:target="_blank"}  from **@gartung**: Changes needed because of changes in the API for clang v3.5 `core`  created: 2014-09-18 02:31:44 merged: 2014-09-22 09:35:12

57. [5445](http://github.com/cms-sw/cmssw/pull/5445){:target="_blank"}  from **@gartung**: Use the dabloom package routines to write out a bloom filter from a clas... `core`  created: 2014-09-19 17:20:55 merged: 2014-09-22 07:26:53

58. [5315](http://github.com/cms-sw/cmssw/pull/5315){:target="_blank"}  from **@ktf**: Avoid division by zero report by static analyzer. `core`  created: 2014-09-16 13:21:36 merged: 2014-09-20 08:19:12

59. [5329](http://github.com/cms-sw/cmssw/pull/5329){:target="_blank"}  from **@davidlt**: FWCore: add support for Address Sanitizer IBs `core`  created: 2014-09-17 08:38:33 merged: 2014-09-18 12:56:56

60. [5309](http://github.com/cms-sw/cmssw/pull/5309){:target="_blank"}  from **@fwyzard**: chrono: improvements to IFUNC and native timers `hlt`  created: 2014-09-16 08:00:12 merged: 2014-09-17 19:43:35

61. [5330](http://github.com/cms-sw/cmssw/pull/5330){:target="_blank"}  from **@ianna**: DD Tests Cleanup `geometry`  created: 2014-09-17 10:35:59 merged: 2014-09-17 19:42:01

62. [5302](http://github.com/cms-sw/cmssw/pull/5302){:target="_blank"}  from **@Dr15Jones**: Fixed clang compiler warnings and errors created: 2014-09-15 21:36:11 merged: 2014-09-17 19:41:01

63. [5305](http://github.com/cms-sw/cmssw/pull/5305){:target="_blank"}  from **@fwyzard**: FastTimerServiceClient: update plots after every lumisection `hlt`  created: 2014-09-15 22:40:30 merged: 2014-09-17 19:39:52

64. [5300](http://github.com/cms-sw/cmssw/pull/5300){:target="_blank"}  from **@Dr15Jones**: Clang fixes for PhysicsTools/SelectorUtils `analysis`  created: 2014-09-15 20:38:21 merged: 2014-09-17 19:38:38

65. [5301](http://github.com/cms-sw/cmssw/pull/5301){:target="_blank"}  from **@Dr15Jones**: Clang fixes for RecoEgamma/ElectronIdentification `reconstruction`  created: 2014-09-15 20:39:20 merged: 2014-09-17 19:38:10

66. [5317](http://github.com/cms-sw/cmssw/pull/5317){:target="_blank"}  from **@Dr15Jones**: Silence static analyzer warning for BXVector `l1`  created: 2014-09-16 14:48:40 merged: 2014-09-17 19:37:33

67. [5325](http://github.com/cms-sw/cmssw/pull/5325){:target="_blank"}  from **@alja**: 72x Fix gcc491 warning. `visualization`  created: 2014-09-16 21:53:06 merged: 2014-09-17 19:37:03

68. [5328](http://github.com/cms-sw/cmssw/pull/5328){:target="_blank"}  from **@davidlt**: Clean up undefined behavior in PixelChannelIdentifier.h `simulation`  created: 2014-09-17 07:04:17 merged: 2014-09-17 19:36:37

69. [5331](http://github.com/cms-sw/cmssw/pull/5331){:target="_blank"}  from **@deguio**: fix uninitialized variable `dqm`  created: 2014-09-17 12:07:44 merged: 2014-09-17 19:34:53

70. [5356](http://github.com/cms-sw/cmssw/pull/5356){:target="_blank"}  from **@alja**: 72x changes related to cmsShow standalone version `visualization`  created: 2014-09-17 19:11:24 merged: 2014-09-17 19:34:07

71. [5278](http://github.com/cms-sw/cmssw/pull/5278){:target="_blank"}  from **@mtosi**: DQM: fix tracking summary map `dqm`  created: 2014-09-12 14:46:01 merged: 2014-09-17 19:32:47

72. [5236](http://github.com/cms-sw/cmssw/pull/5236){:target="_blank"}  from **@smorovic**: output adler32 checksumming propagated to JSON file `daq`  `dqm`  created: 2014-09-09 10:33:03 merged: 2014-09-17 19:32:16

73. [5316](http://github.com/cms-sw/cmssw/pull/5316){:target="_blank"}  from **@ianna**: DDValue Cleanup `geometry`  created: 2014-09-16 14:16:30 merged: 2014-09-17 15:30:38

74. [5308](http://github.com/cms-sw/cmssw/pull/5308){:target="_blank"}  from **@franzoni**: restore assert ValidationEventGenerator 4tau decays `generators`  created: 2014-09-16 07:41:23 merged: 2014-09-17 15:29:16

75. [5318](http://github.com/cms-sw/cmssw/pull/5318){:target="_blank"}  from **@Dr15Jones**: Provide only const access to ME0EtaPartitions `geometry`  created: 2014-09-16 15:00:31 merged: 2014-09-17 15:28:58

76. [5324](http://github.com/cms-sw/cmssw/pull/5324){:target="_blank"}  from **@Dr15Jones**: Converted MultiTrackSelector from global to stream `reconstruction`  created: 2014-09-16 20:57:20 merged: 2014-09-17 15:28:21

77. [5297](http://github.com/cms-sw/cmssw/pull/5297){:target="_blank"}  from **@VinInn**: Fix bug on demand offline `reconstruction`  created: 2014-09-15 17:02:37 merged: 2014-09-17 08:13:26

78. [5295](http://github.com/cms-sw/cmssw/pull/5295){:target="_blank"}  from **@gartung**: ClangSA : add checker cms.ThrUnsafeFCallChecker  `core`  created: 2014-09-15 16:00:58 merged: 2014-09-16 13:17:59

79. [5298](http://github.com/cms-sw/cmssw/pull/5298){:target="_blank"}  from **@gartung**: clangSA: change edmChecker to flag classes inheriting from edm::EDProduc... `core`  created: 2014-09-15 17:30:18 merged: 2014-09-16 04:53:16

#### CMSDIST Changes between Tags REL/CMSSW_7_2_0_pre6/slc6_amd64_gcc481 and REL/CMSSW_7_2_0_pre7/slc6_amd64_gcc481:

[compare to previous](https://github.com/cms-sw/cmsdist/compare/REL/CMSSW_7_2_0_pre6/slc6_amd64_gcc481...REL/CMSSW_7_2_0_pre7/slc6_amd64_gcc481)

1. [1067](http://github.com/cms-sw/cmsdist/pull/1067){:target="_blank"}  from **@degano**: Update root to use fix for fIsAMethod thread safe. created: 2014-09-29 10:05:56 merged: 2014-09-29 10:05:59

2. [1059](http://github.com/cms-sw/cmsdist/pull/1059){:target="_blank"}  from **@mkirsano**: Fix directory structure for lhapdf6 and some improvements created: 2014-09-26 07:58:24 merged: 2014-09-26 13:53:46

3. [1055](http://github.com/cms-sw/cmsdist/pull/1055){:target="_blank"}  from **@degano**: Include fix to make TFormula thread safe. created: 2014-09-25 10:40:39 merged: 2014-09-25 10:40:42

4. [1044](http://github.com/cms-sw/cmsdist/pull/1044){:target="_blank"}  from **@degano**: Update llvm and clang to 3.5. created: 2014-09-22 09:34:56 merged: 2014-09-22 09:35:07

5. [1036](http://github.com/cms-sw/cmsdist/pull/1036){:target="_blank"}  from **@davidlt**: cmssw-ib: fetch int-build sources from GitHub created: 2014-09-19 10:09:02 merged: 2014-09-19 10:09:41

6. [1015](http://github.com/cms-sw/cmsdist/pull/1015){:target="_blank"}  from **@ktf**: Fix multithreading issue in TFormula exposed by Vincenzo. created: 2014-09-15 19:21:31 merged: 2014-09-15 19:22:10

repository: cms-sw/ReleaseNotes

repo_name: cms-sw/ReleaseNotes


text:
## 1. devopsubuntu1804
`devopsubuntu1804` is a Vagrant VM box with Base image of Ubuntu 18.04 LTS (Bionic) that has DevOps tools, programming/scripting languages and environments pre-installed and pre-configured to be ready to be used instantly after boot up.

`devopsubuntu1804 Releases`: [Vagrant Cloud URL](https://app.vagrantup.com/darkwizard242/boxes/devopsubuntu1804)

Supported Provider: **VirtualBox**

#### Audience
IT professionals, organizations, enthusiasts or learners with a focus or interest towards CI/CD/CM/Containerization/DevOps.

#### Disclaimer:
It is expected that you have Vagrant and Virtualbox installed on your host machine (whether the host is Windows, Linux or OSX). If not, then please download/install [Vagrant](https://www.vagrantup.com/downloads.html) and [Virtualbox](https://www.virtualbox.org/wiki/Downloads).

## 2. List of Tools and Languages:
 * _Docker_
    * `Docker version 18.06.1-ce, build e68fc7a`
 * _Ansible_
    * `ansible 2.7.1`
 * _Jenkins_
    * `Jenkins ver. 2.138.2`
 * _Git_
    * `git version 2.17.1`
 * _Python_
    * `Python 2.7.15rc1`
 * _Java_
    * `openjdk version "1.8.0_181"`
 * _etc.._

All of the tools have been preset to run at boot time using the `init` system, so you don't have to worry about doing that and can instantly get on to working with these awesome tools!

## 3. Virtualizing `devopsubuntu1804` on Vagrant
This section covers easy to use steps to get started with downloading and virtualizing `devopsubuntu1804` virtual environment.

### 3.1. Single Machine Mode:
Single Machine mode is a mode where you will only be initializing a fresh vagrant virtual envrionment to use`devopsubuntu1804`. Open CMD (for **Windows** host) or Terminal (for **Linux/OSX** host), then change to a directory of your liking on the Command Prompt or Terminal and run the following command:

```shell
vagrant init darkwizard242/devopsubuntu1804
```

Now that `Vagrantfile` has been created for `devopsubuntu1804`, you can initialize/boot up the box (it will download the box if not already downloaded) using the following command:

```shell
vagrant up
```

Once the box is up, do `vagrant ssh` and you will be within the virtualized box.

### 3.2. Multi Machine Mode:
As per Vagrant's website, "Vagrant is able to define and control multiple guest machines per Vagrantfile. This is known as a 'multi-machine' environment." So if you are running in a **multi-machine mode**, you can simple add the following chunk within the existing Vagrantfile:

```shell
config.vm.define "mydevopsbox" do |mydevopsbox|
   mydevopsbox.vm.box = "darkwizard242/devopsubuntu1804"
   mydevopsbox.vm.hostname = 'mydevopsbox'
end
```

Now run the following command so that the box can be downloaded (if not already) and be booted up:
```shell
vagrant up mydevopsbox
```

Once the box is up, do `vagrant ssh mydevopsbox` and you will be within the virtualized box.

## 4. Users - for `devopsubuntu1804` Vagrant box
Docker, Ansible and Jenkins each have their own respective system users i.e. `docker` , `ansible` & `jenkins`.

Like any other vagrant box, you can easily ssh into devopsubuntu1804 using the default `vagrant ssh` command and make use of any of the other system level users or application level ones as you like.

### 4.1. Type and list of users and passwords:

Below is table listing the type of users as well as their usernames and passwords:

|          User Type           |                  Username                |              Password              |
|        -------------       |                  -------------           |               -------------       |
|           System User        |                    vagrant               |                 password           |
|           System User        |                    root                  |                 password           |
|           System User        |                    docker                |                 password           |
|           System User        |                    ansible               |                 password           |
|           System User        |                    jenkins               |                 password           |
|Jenkins Web-Application Console|                    admin                |                 admin              |

**NOTE:** _Though, the passwords for all of the users have been set by default by me so that anyone can use them easily. I would highly recommend to change the passwords of system level users via `root` user using the following commands:_

 * `passwd vagrant`
 * `passwd root`
 * `passwd docker`
 * `passwd ansible`
 * `passwd jenkins`

### 4.2.  Users and home directories:

Following table consists the system **users** and their `$HOME` directories.

|          User                |            Home Directory                |
|        :-------------       |                  :-------------         |
|           root               |                    /root                 |
|           vagrant            |                    /home/vagrant         |
|           ansible            |                    /home/ansible         |
|           docker             |                    /home/docker          |
|           jenkins            |                    /var/lib/jenkins      |

## 5. Acknowledgements:
 * [Vagrant](https://www.vagrantup.com/)
 * [Ubuntu](https://www.ubuntu.com/)

## 6. Authors:
 * [Ali Muhammad](https://www.linkedin.com/in/ali-muhammad-759791130/)


text:
# ApiV2010ShortCode

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**AccountSid** | Pointer to **string** | The SID of the Account that created this resource |
**ApiVersion** | Pointer to **string** | The API version used to start a new TwiML session |
**DateCreated** | Pointer to **string** | The RFC 2822 date and time in GMT that this resource was created |
**DateUpdated** | Pointer to **string** | The RFC 2822 date and time in GMT that this resource was last updated |
**FriendlyName** | Pointer to **string** | A string that you assigned to describe this resource |
**ShortCode** | Pointer to **string** | The short code. e.g., 894546. |
**Sid** | Pointer to **string** | The unique string that identifies this resource |
**SmsFallbackMethod** | Pointer to **string** | HTTP method we use to call the sms_fallback_url |
**SmsFallbackUrl** | Pointer to **string** | URL Twilio will request if an error occurs in executing TwiML |
**SmsMethod** | Pointer to **string** | HTTP method to use when requesting the sms url |
**SmsUrl** | Pointer to **string** | URL we call when receiving an incoming SMS message to this short code |
**Uri** | Pointer to **string** | The URI of this resource, relative to `https://api.twilio.com` |

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

repository: shwetha-manvinkurke/twilio-go

repo_name: shwetha-manvinkurke/twilio-go


text:
# Storage

Available Drivers
- Azure Blob Storage
- Azure File Storage

## Azure Blob Storage

In order to make it work please add the following configuration to the ``config/filesystems.php`` config file:

```php

'disks' => [

    ...

    'azure' => [

        // Mandatory fields
        'driver' => 'azure.blob', // The driver
        'container' => env('AZURE_STORAGE_BLOB_CONTAINER') // Your default container,

        // Optional fields
        'auto_create_container' => true, // Will automatically create containers if don't exist

        // Override fields
        'portocol' => 'https', // Connection protocol, recommended to leave it as it is
        'account_name' => env('AZURE_ACCOUNT_NAME'), // Your Storage account name
        'key' => env('AZURE_ACCOUNT_KEY'), // Your Storage Account key
    ]

]

```

## Azure File Storage

To use the file storage driver please add these lines into the ``config/filesystems.php`` config file:

```php

'disks' => [

    ...

    'azure' => [

        // Mandatory fields
        'driver' => 'azure.file', // The driver
        'container' => env('AZURE_STORAGE_FILE_SHARE') // Your default container,

        // Optional fields
        'auto_create_share' => true, // Will automatically create shares if don't exist

        // Override fields
        'portocol' => 'https', // Connection protocol, recommended to leave it as it is
        'account_name' => env('AZURE_ACCOUNT_NAME'), // Your Storage account name
        'key' => env('AZURE_ACCOUNT_KEY'), // Your Storage Account key
    ]

]

```

## Known issues
_File storage driver does not support recursive item listing yet._

## Note on configuration overrides

The following driver specific configurations will be inherited by the package config file by default:
- protocol
- account_name
- key

So if you decide to use only one Storage Account you can specify these values only once and you don't have to repeat adding these credentials.

[See how to export package configuration.](../README.md#configuration)

repository: SzuniSOFT/azure-laravel

gha_language: PHP

repo_name: SzuniSOFT/azure-laravel


text:
# Freshdesk API Client

[![Build Status][travis_badge]][travis]
[![Gem Version][rubygems_badge]][rubygems]
[![Code Climate][codeclimate_badge]][codeclimate]

A Ruby API client that interfaces with freshdesk.com web service. This client supports regular CRUD operation.

Please see [API documentation](https://developers.freshdesk.com/api/) for more information.

As of now,it supports the following:

* Solution Category
* Solution Folder
* Solution Article

To experiment with that code, run `bin/console` for an interactive prompt.

## Installation

The Freshdesk API client can be installd using Bundler or Rubygems.

### Bundler

Add this line to your application's Gemfile:

```ruby
gem 'freshdesk_api'
```

And then execute:

```
$ bundle
```

### Rubygems

Or install it yourself as:

```
$ gem install freshdesk_api
```

## Configuration

Configuration is done through a block returning an instance of `FreshdeskAPI::Client`. The block is mandatory and if not passed, an `ArgumentError` will be thrown.

```ruby
require 'freshdesk_api'

client = FreshdeskAPI::Client.new do |config|
  config.base_url = '<- your-freshdesk-url ->' # e.g. 'https://mydesk.freshdesk.com'
  config.username =<EMAIL_ADDRESS>  config.password = 'your freshdesk password'

  require 'logger'
  config.logger = Logger.new(STDOUT)
end
```

Note: This FreshdeskAPI API client only supports basic authentication at the moment.

## Usage

The result of configuration is an instance of `FreshdeskAPI::Client` which can then be used in two different methods.

One way to use the client is to pass it in as an argument to individual classes.

```ruby
FreshdeskAPI::SolutionCategory.create!(client, name: 'API', description: 'API related documents')
FreshdeskAPI::SolutionArticle.find!(client, id: 1, 1: category_id, folder_id: 1)
FreshdeskAPI::SolutionFolder.update!(client, id: 1, category_id: 1, name: 'Folder API')
FreshdeskAPI::SolutionArticle.destroy!(client, id: 1, category_id: 1, folder_id: 1)
```
Another way is to use the instance methods under client.

```ruby
categories = client.solution_categories
category = categories.create!(name: 'API', description: 'API related documents')
category.update!(name: 'API v2', description: 'API related documents v2')
category = categories.find!(id: 1)
category.destroy!
```

The methods under `FreshdeskAPI::Client` (such as `.solution_categories`) return an instance of `FreshdeskAPI::Collection` a lazy-loaded list of that resource.

Actual requests may not be sent until an explicit `FreshdeskAPI::Collection#all!`.

## Development

After checking out the repo, run `bin/setup` to install dependencies. Then, run `bin/console` for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release` to create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).

## Contributing

1. Fork it ( https://github.com/mamantoha/freshdesk_api_client_rb/fork )
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create a new Pull Request

## License and Author

The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

Copyright (c) 2015-2018 by Anton Maminov

[travis_badge]: http://img.shields.io/travis/mamantoha/freshdesk_api_client_rb.svg?style=flat
[travis]: https://travis-ci.org/mamantoha/freshdesk_api_client_rb

[rubygems_badge]: http://img.shields.io/gem/v/freshdesk_api.svg?style=flat
[rubygems]: https://rubygems.org/gems/freshdesk_api

[codeclimate_badge]: http://img.shields.io/codeclimate/github/mamantoha/freshdesk_api_client_rb.svg?style=flat
[codeclimate]: https://codeclimate.com/github/mamantoha/freshdesk_api_client_rb

gha_language: Ruby


text:
# Providers in Veewee

Initially veewee started as provider for virtualbox. From v0.3 Vmware fusion and KVM support are introduced.

## Virtualbox

To interact with virtualbox, veewee executes shell-commands through the 'VboxManage' command. The virtualbox gem library proved to be less stable.

To simulate the typing, veewee uses the 'VBoxManage controlvm 'myubuntu' keyboardputscancode <keycode>'.
Scancode are injected directly the keyboard buffer with this. And as this buffer is small, we can't type fast.
This is why you have the delay while veewee types the commands. Speeding it up, will make the keyboard buffer loose keystrokes.

## Vmware fusion

To interact with Vmware fusion, we leverage (a currently patched) version of [Fission gem](https://github.com/thbishop/fission). This takes care of the heavy lifting.

To interact with the screen , veewee enables VNC on the created vmware fusion machines and use the [Ruby-VNC gem](http://code.google.com/p/ruby-vnc/) to send the keystrokes. Here too , sending keystrokes too fast is a problem.

## KVM

To interact  with KVM veewee, uses [libvirt support](http://libvirt.org/ruby/) provided through [Fog gem](http://fog.io).

To interact with the screen , veewee enables VNC on the created kvm machines and use the [Ruby-VNC gem](http://code.google.com/p/ruby-vnc/) to send the keystrokes. Here too , sending keystrokes too fast is a problem.

repository: bruienne/veewee

repo_name: bruienne/veewee