text:
# knwldg/template

## Overview

### Contents

#### Directories

- `data` - Where generated data sits
- `input` - Where input data sits
- `log` - Where logs from running code sits
- `scripts` - Bash (or other non-python) scripts
- `package-name` - Where source code sits

#### Files

Top-level files are package manager or config files, e.g.

- `Pipfile`
- `Pipfile.lock`
- `scrapy.cfg`

## Create new package

To create a new package within the knwldg repo:

1. Copy and rename the `template` folder (and the source code folder too)
2. Display the new folder in the VS Code workspace by adding it `folders` settings in `knwldg/knwldg.code-workspace`

   ```json
   {
     "folders": [
       {
         "path": "my-new-package"
       },
       {
         "path": "common"
       },
       {
         "name": "knwldg",
         "path": "."
       }
     ],
     "settings": {}
   }
   ```

3. Do not display the new folder within the `knwldg` folder by adding it to `files.exclude` settings in `knwldg/.vscode/settings.json`

   ```json
   {
     "files.exclude": {
       "my-new-package": true
     }
   }
   ```

4. Initialize virtual envrionment in the top-level of the new folder.

   ```bash
   pipenv --python 3.7
   ```

5. Run

   ```bash
   pipenv --venv
   ```

   and update the `python.pythonPath` settings in `knwldg/my-new-package/.vscode/settings.json` to point to the venv's python exec.

6. Update the namespaces in `knwldg/my-new-package/scrapy.cfg`

   ```cfg
   # my-new-package/scrapy.cfg

   [settings]
   default = my_new_package.settings

   [deploy]
   project = my_new_package
   ```

7. Configure the Pipfile at `knwldg/my-new-package/Pipfile` if necessary.

8. Update `README.md`

9. Now you should be good to go! Just don't forget to write new spiders and components in `knwldg/my-new-package/my_new_package`

license: MIT

repository: JuroOravec/knwldg

branch_name: refs/heads/master

extension: md

gha_language: Python

gha_license_id: MIT

license_type: permissive

repo_name: JuroOravec/knwldg


text:
# Throttler - intelligent WaitGroups

[![GoDoc](https://godoc.org/github.com/nozzle/throttler?status.svg)](http://godoc.org/github.com/nozzle/throttler) [![Coverage Status](https://coveralls.io/repos/nozzle/throttler/badge.svg?branch=master)](https://coveralls.io/r/nozzle/throttler?branch=master)

 Throttler fills the gap between sync.WaitGroup and manually monitoring your goroutines with channels. The API is almost identical to Wait Groups, but it allows you to set a max number of workers that can be running simultaneously. It uses channels internally to block until a job completes by calling Done() or until all jobs have been completed. It also provides a built in error channel that captures your goroutine errors and provides access to them as `[]error` after you exit the loop.

See a fully functional example on the playground at http://bit.ly/throttler-v3

Compare the Throttler example to the sync.WaitGroup example from http://golang.org/pkg/sync/#example_WaitGroup

### How to use Throttler

```
// This example fetches several URLs concurrently,
// using a Throttler to block until all the fetches are complete.
// Compare to http://golang.org/pkg/sync/#example_WaitGroup
func ExampleThrottler() {
	var urls = []string{
		"http://www.golang.org/",
		"http://www.google.com/",
		"http://www.somestupidname.com/",
	}
	// Create a new Throttler that will get 2 urls at a time
	t := throttler.New(2, len(urls))
	for _, url := range urls {
		// Launch a goroutine to fetch the URL.
		go func(url string) {
			// Fetch the URL.
			err := http.Get(url)
			// Let Throttler know when the goroutine completes
			// so it can dispatch another worker
			t.Done(err)
		}(url)
		// Pauses until a worker is available or all jobs have been completed
		// Returning the total number of goroutines that have errored
		// lets you choose to break out of the loop without starting any more
		errorCount := t.Throttle()
	}
}
```

### vs How to use a sync.WaitGroup

```
// This example fetches several URLs concurrently,
// using a WaitGroup to block until all the fetches are complete.
func ExampleWaitGroup() {
	var wg sync.WaitGroup
	var urls = []string{
		"http://www.golang.org/",
		"http://www.google.com/",
		"http://www.somestupidname.com/",
	}
	for _, url := range urls {
		// Increment the WaitGroup counter.
		wg.Add(1)
		// Launch a goroutine to fetch the URL.
		go func(url string) {
			// Decrement the counter when the goroutine completes.
			defer wg.Done()
			// Fetch the URL.
			http.Get(url)
		}(url)
	}
	// Wait for all HTTP fetches to complete.
	wg.Wait()
}
```

repository: tektoncd/cli

branch_name: refs/heads/main

gha_language: Go

repo_name: tektoncd/cli


text:
![starbackjs](https://user-images.githubusercontent.com/45036724/130007266-83c720b8-ce3f-47e8-a854-ac0b640ce36f.gif)

## Getting Started

You can use starback.js directly with `<script>` tag or import syntax.

- With `<script>` tag

  ```html
  # Using CDN
  <script<EMAIL_ADDRESS>
  # Using downloaded files
  <script src="PATH_TO_YOUR_DIST_FOLDER/starback.js"></script>
  ```

- With import

  Install via NPM first:

  ```bash
  npm install starback
  ```

  and then

  ```js
  import Starback from 'starback'
  ```

## Example Usage

```html
<canvas id="canvas"></canvas>

<script src="PATH_TO_DIST_FOLDER/starback.js"></script>
<script>
  const canvas = document.getElementById('canvas')
  const starback = new Starback(canvas, {
    width: 1000,
    height: 500,
    speed: 5,
    spread: 0.2,
    // ...and the other options
  })
  starback.generateStar(20)
</script>
```

You can check the more options in [Options section](#options)

## Options

| Key             | Type              | Description                                                                                | Required | Default Value           |
| --------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------- |
| width           | Number            | Canvas width to set                                                                                | no       | 800                     |
| height          | Number            | Canvas height to set                                                                                | no       | 600                     |
| backgroundColor | String|Array | Color of the background, use string for solid color, or array of colors for linear gradient                                                                         | no       | #ccc                    |
| directionY      | Number            | The direction the star to move vertically (1 = to bottom, 0 = to top)                                                                                | no       | 1                       |
| directionX      | Number            | The direction the star to move vertically (1 = to right, 0 = to left)                                                                                | no       | 1                       |
| distanceX       | Number            | Distance horizontally the star should reaching at                                                                                | no       | 0.1                     |
| frequency       | Number            | The frequency of star will be rotated                                                                                | no       | 10                      |
| randomOpacity   | Boolean           | If `true`, random star will get random opacity                                                                                | no       | false                   |
| slope           | Object            | The quadraticCurve coordinate that will be applied to stars. Read [MDN](https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/quadraticCurveTo) | no       | {x: 1, y: 1}            |
| starColor       | String|Array | Color of the stars, use string for solid color, or array of colors for linear gradient                                                                              | no       | hsla(299, 100%, 50%, 1) |
| speed           | Number            | Star speed                                                                                | no       | 0.5                     |
| spread          | Number            | The spread level of the stars                                                                                | no       | 1                       |
| starSize        | Number            | Star height                                                                                | no       | 100                     |
| showFps         | Boolean           | Show FPS on the top left screen                                                                                | no       | false                   |

## Methods

| Name                         | Parameter                               | Description                                       |
| ---------------------------- | --------------------------------------- | ------------------------------------------------- |
| `generateStar(amount)`       | amount                                  | The quantity of stars that will be shown          |
| `addToFront(callback(ctx))`  | function(ctx: CanvasRenderingContext2D) | Add to front of the falling star by given context |
| `addToBehind(callback(ctx))` | function(ctx: CanvasRenderingContext2D) | Add to back of the falling star by given context  |

Example method usage: adding image to front

```js
let starback = new Starback(canvas, options)

let mountainImage = new Image()
mountainImage.src = 'images/mountain.png'

mountainImage.onload = () => {
  starback.addToFront((ctx) => {
    ctx.drawImage(
      mountain,
      0,
      0,
      mountain.width,
      mountain.height,
      0,
      canvas.height - mountain.height,
      canvas.width,
      mountain.height
    )
  })
}
```

## Contributing

You can contribute to this repository. See [CONTRIBUTING.md](https://github.com/zuramai/starback.js/blob/main/CONTRIBUTING.md)

## Donate

If you have used this library and it's useful for you, please consider to donate:

[Ko-fi](https://ko-fi.com/saugi) | [Trakteer](https://trakteer.id/saugi)

## License

This library is under MIT license.


text:
---
hrs_structure:
  division: '4'
  volume: '13'
  title: '32'
  chapter: '603'
  section: 603-37
type: hrs_section
tags:
  - Court
  - Judicial Proceeding
menu:
  hrs:
    identifier: HRS_0603-0037
    parent: HRS0603
    name: 603-37 Change of venue
weight: 16135
title: Change of venue
full_title: 603-37 Change of venue
---
**§603-37 Change of venue.** After the parties shall have had an opportunity to be heard, any circuit court may, upon satisfactory proof that a fair and impartial trial cannot be had in any civil case pending in the court, or, in its discretion, upon satisfactory proof that it would be more fair and equitable to the parties thereto if any civil case pending in the court were heard in another jurisdiction, change the venue to some other circuit and order the record to be transferred thereto; provided that any circuit court may, in its discretion, upon the consent of all the parties to any civil case pending in the court, change the venue to some other circuit court and order the record to be transferred thereto. [L 1892, c 57, pt of §36; am L 1903, c 32, pt of §10; am L 1921, c 157, pt of §1; RL 1925, pt of §2247; RL 1935, pt of §3643; RL 1945, pt of §9647; RL 1955, pt of §215-17; am L 1957, c 195, §1; [HRS §603-37](/title-32/chapter-603/section-603-37/); am L 1972, c 88, §3(p)]

Rules of Court

Hawaii Rules of Civil Procedure do not extend or limit jurisdiction or venue, see HRCP rule 82.

Case Notes

Change of venue and discretion therein. 9 H. 360 (1894); 11 H. 314, 317 (1898); 20 H. 7, 11 (1910); in ejectment, 19 H. 334 (1909); 31 H. 65 (1929).

Where action is brought in wrong circuit, this section cannot be used as a remedy to transfer case to proper circuit. 47 H. 271, 386 P.2d 880 (1963).

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
# expand-ebs-root-volume
Expands an EC2 instance's root volume. Requires instance downtime.

This script started life as Eric Hammond's excellent [blog post](https://alestic.com/2010/02/ec2-resize-running-ebs-root/) on the topic. It's been turned into a script suitable for a variety of different use cases, including iterative resizing for a fleet.

## Usage

```
root-volume-expand.sh $instance-id
```

repository: QuinnyPig/expand-ebs-root-volume

repo_name: QuinnyPig/expand-ebs-root-volume


text:
PEP: 515 Title: Underscores in Numeric Literals Version: $Revision$
Last-Modified: $Date$ Author: Georg Brandl, Serhiy Storchaka Status:
Final Type: Standards Track Content-Type: text/x-rst Created:
10-Feb-2016 Python-Version: 3.6 Post-History: 10-Feb-2016, 11-Feb-2016

Abstract and Rationale
======================

This PEP proposes to extend Python's syntax and number-from-string
constructors so that underscores can be used as visual separators for
digit grouping purposes in integral, floating-point and complex number
literals.

This is a common feature of other modern languages, and can aid
readability of long literals, or literals whose value should clearly
separate into parts, such as bytes or words in hexadecimal notation.

Examples::

    # grouping decimal numbers by thousands
    amount = 10_000_000.0

    # grouping hexadecimal addresses by words
    addr = 0xCAFE_F00D

    # grouping bits into nibbles in a binary literal
    flags = 0b_0011_1111_0100_1110

    # same, for string conversions
    flags = int('0b_1111_0000', 2)

Specification
=============

The current proposal is to allow one underscore between digits, and
after base specifiers in numeric literals. The underscores have no
semantic meaning, and literals are parsed as if the underscores were
absent.

Literal Grammar
---------------

The production list for integer literals would therefore look like
this::

integer: decinteger \| bininteger \| octinteger \| hexinteger
decinteger: nonzerodigit (\[\"\_\"\] digit)\* \| "0" (\[\"\_\"\] "0")\*
bininteger: "0" ("b" \| "B") (\[\"\_\"\] bindigit)+ octinteger: "0" ("o"
\| "O") (\[\"\_\"\] octdigit)+ hexinteger: "0" ("x" \| "X") (\[\"\_\"\]
hexdigit)+ nonzerodigit: "1"..."9" digit: "0"..."9" bindigit: "0" \| "1"
octdigit: "0"..."7" hexdigit: digit \| "a"..."f" \| "A"..."F"

For floating-point and complex literals::

floatnumber: pointfloat \| exponentfloat pointfloat: \[digitpart\]
fraction \| digitpart "." exponentfloat: (digitpart \| pointfloat)
exponent digitpart: digit (\[\"\_\"\] digit)\* fraction: "." digitpart
exponent: ("e" \| "E") \["+" \| "-"\] digitpart imagnumber: (floatnumber
\| digitpart) ("j" \| "J")

Constructors
------------

Following the same rules for placement, underscores will be allowed in
the following constructors:

-   `int()` (with any base)
-   `float()`
-   `complex()`
-   `Decimal()`

Further changes
---------------

The new-style number-to-string formatting language will be extended to
allow `_` as a thousands separator, where currently only `,` is
supported. This can be used to easily generate code with more readable
literals. \[11\]\_

The syntax would be the same as for the comma, e.g. `{:10_}` for a width
of 10 with `_` separator.

For the `b`, `x` and `o` format specifiers, `_` will be allowed and
group by 4 digits.

Prior Art
=========

Those languages that do allow underscore grouping implement a large
variety of rules for allowed placement of underscores. In cases where
the language spec contradicts the actual behavior, the actual behavior
is listed. ("single" or "multiple" refer to allowing runs of consecutive
underscores.)

-   Ada: single, only between digits \[8\]\_
-   C\# (open proposal for 7.0): multiple, only between digits \[6\]\_
-   C++14: single, between digits (different separator chosen) \[1\]\_
-   D: multiple, anywhere, including trailing \[2\]\_
-   Java: multiple, only between digits \[7\]\_
-   Julia: single, only between digits (but not in float exponent parts)
    \[9\]\_
-   Perl 5: multiple, basically anywhere, although docs say it's
    restricted to one underscore between digits \[3\]\_
-   Ruby: single, only between digits (although docs say "anywhere")
    \[10\]\_
-   Rust: multiple, anywhere, except for between exponent "e" and digits
    \[4\]\_
-   Swift: multiple, between digits and trailing (although textual
    description says only "between digits") \[5\]\_

Alternative Syntax
==================

Underscore Placement Rules
--------------------------

Instead of the relatively strict rule specified above, the use of
underscores could be less limited. As seen in other languages, common
rules include:

-   Only one consecutive underscore allowed, and only between digits.
-   Multiple consecutive underscores allowed, but only between digits.
-   Multiple consecutive underscores allowed, in most positions except
    for the start of the literal, or special positions like after a
    decimal point.

The syntax in this PEP has ultimately been selected because it covers
the common use cases, and does not allow for syntax that would have to
be discouraged in style guides anyway.

A less common rule would be to allow underscores only every N digits
(where N could be 3 for decimal literals, or 4 for hexadecimal ones).
This is unnecessarily restrictive, especially considering the separator
placement is different in different cultures.

Different Separators
--------------------

A proposed alternate syntax was to use whitespace for grouping. Although
strings are a precedent for combining adjoining literals, the behavior
can lead to unexpected effects which are not possible with underscores.
Also, no other language is known to use this rule, except for languages
that generally disregard any whitespace.

C++14 introduces apostrophes for grouping (because underscores introduce
ambiguity with user-defined literals), which is not considered because
of the use in Python's string literals. \[1\]\_

Implementation
==============

A preliminary patch that implements the specification given above has
been posted to the issue tracker. \[12\]\_

References
==========

.. \[1\]
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3499.html

.. \[2\] http://dlang.org/spec/lex.html\#integerliteral

.. \[3\]
http://perldoc.perl.org/perldata.html\#Scalar-value-constructors

.. \[4\] http://doc.rust-lang.org/reference.html\#number-literals

.. \[5\]
https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift\_Programming\_Language/LexicalStructure.html

.. \[6\] https://github.com/dotnet/roslyn/issues/216

.. \[7\]
https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores-literals.html

.. \[8\]
http://archive.adaic.com/standards/83lrm/html/lrm-02-04.html\#2.4

.. \[9\]
http://docs.julialang.org/en/release-0.4/manual/integers-and-floating-point-numbers/

.. \[10\]
http://ruby-doc.org/core-2.3.0/doc/syntax/literals\_rdoc.html\#label-Numbers

.. \[11\]
https://mail.python.org/pipermail/python-dev/2016-February/143283.html

.. \[12\] http://bugs.python.org/issue26331

Copyright
=========

This document has been placed in the public domain.

 .. Local Variables: mode: indented-text indent-tabs-mode: nil
sentence-end-double-space: t fill-column: 70 coding: utf-8 End:

repository: erdal-pb/opep

repo_name: erdal-pb/opep


text:
**Summary**
**Summary**
*html book*
How the web works
when you connect to the web you do so via an ISP or Internet service provider.
your computer contacts a network of servers called domain name system servers
the unique number that the dns server returns to your computer allows your browser to contact the web server that hosts the website you requested
the web server then sends the page you requested back to your browser
**Structure**
Elements are usually made up of two tags and opening and closing tag
The characters in the brackets indicate the tags purpose
the body, head, and title are part of structure
tags are often referred to as elements
**Extra Markup**
You can add comments to your code between the <!-- and -->
The div and span elements allow you to group block-level and inline elements together
**html5 layout**
The article element acts as a container for any section of a page that could stand alone and potentially be syndicated
the new elements provide clearer code
**process and design**
A wireframe is a simple sketch of the key information that needs to go on each page of the site
visual hierarchy refers to the order in which your eyes perceive what they see.
*Site maps allow you to plan the structure of a site.
*JS Book*
a script is a series of instructions that a computer can follow to achieve a goal.
vocabulary- the words that computers understand
syntax - how you put those words together to create instructions computers can follow
in computer programming each physical thing in the world can be represented as an object.
an event is the computer's way of saying hey this just happened
methods represent things people need to do with objects.


text:
# Testing

## Jest for unit testing

### Supporting server-only tests

We support server and client testing based on the following naming convention:

- A test named `myTest.test.ts` will be executed in a JSDOM environment (~ like a browser). Use as a default for React components and generic utility code.
- A test named `myTest.test.server.ts`, or any test located within a `server` folder, will be executed only in the Node server environment. Use to test your Graphql resolvers for instance.

### React Testing library

We have preinstalled [React Testing Library](https://testing-library.com/docs/react-testing-library/intro) and [React Testing Hooks](https://github.com/testing-library/react-hooks-testing-library).

### Tests for Vulcan Next (for contributors only)

We have a unit tests for some key features and scripts of VN, through the `tests/vn` folder.

This folder is ignored when running `yarn run test:unit`, to avoid bloating your own tests.

### MDX parsing, magic imports with ~

[jest-transformer-mdx](https://github.com/bitttttten/jest-transformer-mdx) allow importing .mdx also in Jest

### .env support

Load `.env` config automatically in Jest,
see [Jest globalSetup](https://github.dev/VulcanJS/vulcan-next/blob/main/.vn/tests/globalSetup.js).

## Unified testing patterns

We strive to unify testing patterns between Cypress and Jest where it makes sense.

First, add [React Testing queries into Cypress](https://github.com/testing-library/cypress-testing-library), so you can fetch elements with similar patterns. Check [React Testing docs for example of the reverse approach](https://testing-library.com/docs/react-testing-library/setup#add-custom-queries) (data-cy in React Testing).

### Unified test coverage

We followed awesome [recommandations from Bahmutov](https://github.com/bahmutov/cypress-and-jest) to unify Cypress and Jest coverage. This is crucial to have a clearer vision of what is correctly tested in your application, whatever the test method is. For instance, e2e tests provides a huge coverage for React components, while unit tests are more efficient for helpers, hooks and functions.

`yarn run coverage` will run tests and compute the unified report in `coverage`.

`yarn run reports:combined` will compute the combined report without running tests.

[More insights with Cypress](https://glebbahmutov.com/blog/combined-end-to-end-and-unit-test-coverage/)

## Cypress for e2e testing

### Run Next in test mode

Run `yarn start:test` or `yarn dev:test` to run your Next server in Test mode. This will in particular load `.env.test` environment config and set `NODE_ENV` to "test".

### TypeScript and vanilla JS (+ESLint)

### Custom commands, with TypeScript

[Relevant doc](https://docs.cypress.io/guides/tooling/typescript-support.html#Types-for-custom-commands)

You can write JavaScript tests and still enjoy auto-completion of custom commands, thanks to TS [triple slash directives](https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html).

### Reuse app Webpack config

You may want your Cypress code to be as powerful as your app code. For this, we are enhancing the Cypress webpack config with the same features as in the app.

[Example from Cypress with TS + Webpack](https://github.com/cypress-io/cypress-webpack-preprocessor/tree/master/examples/use-ts-loader)

### Code coverage

See [Cypress Code Coverage example for TS](https://github.com/cypress-io/code-coverage/tree/master/examples/ts-example), [Cypress Next example](https://github.com/bahmutov/next-and-cypress-example), [Cypress TS example](https://github.com/lluia/cypress-typescript-coverage-example)...

Note: [doc of NYC for TS](https://www.npmjs.com/package/@istanbuljs/nyc-config-typescript) has to be followed carefully (computing sourceMaps for TS code, installing all sibling packages...). The difficult part is instrumentation.

Code coverage is totally disabled client-side when simply running tests, using ["CYPRESS_coverage" variable](https://github.com/cypress-io/code-coverage#disable-plugin) (thanks [@bahmutov](https://github.com/bahmutov)).

### No screenshot/videos as a default

For some reason, Cypress:run will automatically store videos of test run. We disabled this behavior in the config as it may bloat CI/CD.

### Import from your code

We use [Cypress Webpack Preprocessor](https://github.com/cypress-io/cypress-webpack-preprocessor), to enhance Cypress build with similar options as the actual app.

We use `ts-loader`, with [`transpileOnly`](https://github.com/TypeStrong/ts-loader#transpileonly) option to fasten build. We expect your e2e tests typing to be correct at run time.

### Pure SSR testing

The `cy.visitAsHtml()` command allow to check the pure HTML render of a page. It will disable JS in the the page automatically.

Note: at the time of writing (2020/06) [there is an open issue when needing this command in multiple tests](https://github.com/VulcanJS/vulcan-next/issues/40)

### Loads .env.development the same way next does

We use a plugin that will in turn rely on Next.js dotenv loading capabilities.
Used for instance to load the default admin user credentials in tests.
As a default, it will use development values from `.env.development`.

### Intercept emails

Vulcan Next embeds the setup described in the [following official tutorial on how to test mail workflows in Cypress](https://www.cypress.io/blog/2021/05/11/testing-html-emails-using-cypress/).
Cypress will automatically run a test mail server on `http://localhost:7777` and can intercept mails via the "getMail" task.

See e2e tests for the authentication workflow to get some usage examples.

## Storybook

### Webpack 5 and TypeScript config

You can write your Storybook config as normal TypeScript files and even import your local code.

NOTE: installing `ts-node` may break Storybook, see [this Stack Overflow ticket](https://stackoverflow.com/questions/69808808/storybook-main-ts-cannot-use-import-statement-outside-a-module)

### Same import as in Next

We reuse our Webpack config extension function, so you can enjoy magic imports and isomorphic imports in Storybook too.

### Styling with Styled JSX and CSS Modules

Note: CSS modules are currently not appearing correctly in Storybook, see [vulcan-next/issues/20](https://github.com/VulcanJS/vulcan-next/issues/20)

### Public folder

Storybook is aware of the `public` folder, so it will display images accordingly.

### I18n

We reuse the same i18n config as in the app, so your stories will be internationalized automatically.

### Webpack bundle analyzer for storybook

There is nothing worse than a slow Storybook build, you can debug your Webpack bundle using `yarn run analyze-bundle:storybook`

### Mock packages

See `.storybook/mocks/packages` and `.storybook/main.js`, we use Webpack alias to load them. Thus, you can use components that rely on `next/config` for instance.

We use [Storybook Addon Next Router](https://storybook.js.org/addons/storybook-addon-next-router) for mocking the router.

### Chromatic configuration

We don't usually recommend third party services, but [Chromatic](https://www.chromatic.com/) is really an excellent addition to any developer
workflow.

Set the [`CHROMATIC_PROJECT_TOKEN` environment variable](https://www.chromatic.com/docs/cli#required-options) in `.env.development.local`
and then run `yarn run chromatic`.

repository: VulcanJS/vulcan-npm

gha_language: TypeScript

repo_name: VulcanJS/vulcan-npm


text:
# version-control
Get familiar with version control basics

Log

9/4/2020
Updated math_lib.py for potential divide-by-zero error.

9/4/2020
Added an add function to math_lib.py.

9/4/2020
Created a new file, calculate.py, for adding and dividing together.

9/4/2020
Fixed calculate.py to match the assignment better.

9/4/2020
Made a run.sh file to run the calculate.py file. No idea if it's the right way to do it but this looks like it'll work so.

9/8/2020
Updated calculate.py and run.sh after class. Actually ran them in the terminal to see errors that came up, and then debugged to fix those errors.


text:
### Dinghy Ping

[![Build Status](https://travis-ci.org/silvermullet/dinghy-ping.svg?branch=master)](https://travis-ci.org/silvermullet/dinghy-ping)

![dinghy](https://user-images.githubusercontent.com/538171/47242041-7d96d600-d3a2-11e8-8c55-a04e1249bc46.jpeg)

Dinghy Ping is a simple network debugging interface meant to be deployed into your compute infrastructure (ie, Kubernetes). Used for debugging network connectivity to other services local to Dinghy Ping or external to the compute infrastructure (egress). Meant to answer simple connectivity questions developers might have when deploying their applications to a container orchestration setup where routing and accessibility may be different from their local development environments.

#### Display for response headers

#### Formated display for response body

#### Pod logs, per namespace

#### Dinghy ping single endpoint

```bash
curl "http://<IP_ADDRESS>/dinghy/ping/https/google.com"
```

#### Dinghy ping single endpoint with params

```bash
curl "http://<IP_ADDRESS>/dinghy/ping/https/www.google.com/search?source=hp&ei=aIHTW9mLNuOJ0gK8g624Ag&q=dinghy&btnK=Google+Search&oq=dinghy&gs_l=psy-ab.3..35i39l2j0i131j0i20i264j0j0i20i264j0l4.4754.5606..6143...1.0..0.585.957.6j5-1......0....1..gws-wiz.....6..0i67j0i131i20i264.oe0qJ9brs-8"
```

#### Dinghy ping multiple sites

```bash
# dinghy-ping multiple sites
curl -vX POST "http://<IP_ADDRESS>/dinghy/ping/domains" \
  -d @tests/multiple_domains.json \
  --header "Content-Type: application/json"
```

#### Deployment pod logs API
```bash
# 1000 line truncated response
curl "https://<IP_ADDRESS>/deployment-logs/kube-addons/dinghy-ping?json=true?preview=true"
```

```bash
# Full logs
curl "https://<IP_ADDRESS>/deployment-logs/kube-addons/dinghy-ping?json=true"
```

#### Local development on Mac with Docker controlled K8s

##### Install Docker for MacOS and enable Kubernetes

* requires Docker for Mac 2.x or greater
* Enable Kubernetes on Docker for Mac under preferences

```
# Install ingress-nginx
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud-generic.yaml
```

##### Update your /etc/hosts
```
<IP_ADDRESS> localhost dinghy-ping.localhost
```

##### Install dinghy-ping helm chart, modify to docker image tag of your branch, pr, or release tag
```
# Init helm if your local k8s doesn't have it yet
helm init
helm upgrade --install dinghy-ping ./helm/dinghy-ping/ --set image.tag=v0.2.0 --set ingress.subdomain="localhost"
```

##### Navigate to Dinghy-Ping in browser
http://dinghy-ping.localhost

![dinghy copy](https://user-images.githubusercontent.com/538171/50532052-77228a00-0ac8-11e9-8ffd-12f53f55724e.png)

repository: tatianajiselle/dinghy-ping

repo_name: tatianajiselle/dinghy-ping


text:
# 372. Delete Node in a Linked List

**Description**

Implement an algorithm to delete a node in the middle of a singly linked list, given only access to that node.

**Example**

Example 1:

```
Input:
1->2->3->4->null
3
Output:
1->2->4->null
```

Example 2:

```
Input:
1->3->5->null
3
Output:
1->5->null
```

```python
"""
Definition of ListNode
class ListNode(object):

    def __init__(self, val, next=None):
        self.val = val
        self.next = next
"""

class Solution:
    """
    @param: node: the node in the list should be deleted
    @return: nothing
    """
    def deleteNode(self, node):
        # write your code here
        if not node or not node.next:
            node = None
            return

        node.val = node.next.val
        node.next = node.next.next
```

url: https://raw.githubusercontent.com/jxhangithub/lintcode/afd79d790d0a7495d75e6650f80adaa99bd0ff07/Linked_List/372.Delete Node in a Linked List/README.md

repository: jxhangithub/lintcode

repo_name: jxhangithub/lintcode


text:
# Congratulations, you've successfully authenticated

Welcome to **Advocado**, more content will be displayed here when ready

## Why are you seeing this page?

This page is a markdown file loaded from the backend when a request is sent with an authentication header, its here simply to demonstrate that the route works properly.

Currently the home routes looks like this:

```clojure
(defn home-routes
  "These routes are when user is authenticated using auth-token middleware, the
  only exception is the root route, which returns our SPA so that shouldn't be
  wrapped in auth-token"
  []
  [""
   {:middleware [middleware/wrap-csrf
                 middleware/wrap-formats]}
   ["/" {:get home-page}]
   ["/docs" {:middleware [middleware/wrap-auth-token]
             :get (fn [_]
                    (-> (response/ok (-> "docs/home.md" io/resource slurp))
                        (response/header "Content-Type" "text/plain; charset=utf-8")))}]])
```

Where `wrap-auth-token ensures` that for any request to the `/docs` route, a request header must be included. It is handled in frontend by the namespace `advocado.ajax`:

```clojure
(defn default-headers [request]
  (let [token (<sub [:auth/current-token])]
    (if (local-uri? request)
      (-> request
          (update :headers #(merge {"x-csrf-token" js/csrfToken
                                    "x-token" token} %)))
      request)))
```

And is loaded as an interceptor here:

```clojure
(defn load-interceptors! []
  (swap! ajax/default-interceptors
         conj
         (ajax/to-interceptor {:name "default headers"
                               :request default-headers})))
```

repository: roosta/advocado

repo_name: roosta/advocado


text:
## https://anna-podhajska.github.io/api-interaction/

### As a user I want:
 -  view random proverbs in Maori language and their translation
 -  refresh the page to see a new proverb

### Learning goals:
 - pair programming
 - task prioritising
 - consuming external API
 - ajax
 - JavaScript
 - HTML
 - CSS

repository: anna-podhajska/api-interaction

gha_language: HTML

repo_name: anna-podhajska/api-interaction


text:
# easy-click

## Installation
 * NodeJS could be download at: [link](https://nodejs.org/)

## Run Auto Tests:
```
npm run test
```

## Generate Html Report
```
npm run report
```

repository: SET-SKYNET/easy-click

repo_name: SET-SKYNET/easy-click


text:
rabbitmq-zabbix
=======================

Template and checks to monitor rabbitmq queues and server via Zabbix.

## Source:
https://github.com/Travix-International/rabbitmq-zabbix
Modified from original: https://github.com/jasonmcintosh/rabbitmq-zabbix

## What:
Set of python scripts, zabbix template, and associated data to do autodiscovery

## How:
1. Install the `rabbitmq_zabbix` python script in your agent extensions
   directory
2. Configure zabbix agent UserParameters (see below)
3. Import the template to your zabbix server
4. Make sure zabbix_sender is available on the agent server
5. Restart the zabbix agent

## Configuration:
You may optionally create a `.rab.auth` file in the `scripts/rabbitmq` directory.
This file allows you to change default parameters. The format is
`VARIABLE=value`, one per line. The default values are as follows:

    USERNAME=guest
    PASSWORD=guest
    CONF=/etc/zabbix/zabbix_agent.conf

You can also add a filter in this file to restrict which queues are monitored.
This item is a JSON-encoded string. The format provides some flexibility for
its use. You can either provide a single object or a list of objects to filter.
The available keys are: status, node, name, consumers, vhost, durable,
exclusive_consumer_tag, auto_delete, memory, policy

For example, the following filter could find all the durable queues:
`FILTER='{"durable": true}'`

To only use the durable queues for a given vhost, the filter would be:
`FILTER='{"durable": true, "vhost": "mine"}'`

To supply a list of queue names, the filter would be:
`FILTER='[{"name": "mytestqueuename"}, {"name": "queue2"}]'`

## Low level discovery of queues, including global regular expressions:
`https://www.zabbix.com/documentation/3.0/manual/regular_expressions`
The low level discovery, which is what determines what queues to be monitored,
requires with the existing template that a filter be defined as a global regular
expression. You can modify the template to do it in other ways, e.g. with a host
level macro (not tested), override it per host, or any number of methods. But
without a filter, *no* queues will be discovered, *just* server level items will
show up, and your checks will fail.

At some point the filters may be improved to include regular expressions or
"ignore these queues"

## CHANGES
* Changed template to work with Zabbix 2.2
* Changed file structure
* Added more checks and metrics to be exposed
* Updated to use zabbix_sender to push data on request to an item request.  This is similar to how the FromDual MySQL Zabbix stuff works and the concept was pulled from their templates.
* Updated the filters to handle a list of objects

## Ideas for the future?
Add a local cache of the results (may be overkill for RabbitMQ).
Feel free to submit changes or ideas -<EMAIL_ADDRESS>
## Definite kudos to some of the other developers around the web.  In particular,
* Python Scripts: https://github.com/kmcminn/rabbit-nagios
* Base idea for the Rabbit template:  https://github.com/alfss/zabbix-rabbitmq
* Also need to thank Lewis Franklin https://github.com/brolewis for his contributions!
* Base of this fork: https://github.com/jasonmcintosh/rabbitmq-zabbix

repository: Travix-International/rabbitmq-zabbix

repo_name: Travix-International/rabbitmq-zabbix


text:
# AWS DevOps ToolBox

## Tools that make my AWS Cloud Developer / DevOps Engineer job easier

The tools developed in this project are intended to make your cloud developer / devops / sysops job easier. The tools are meant to be used interactively & modified to your current needs.

[Unused resources finder](unusedresources/unused-resources-finder.md)

[Metrics gathering](metrics/metrics-gatherer.md)


text:
### Scrumwala
Your very own Scrum/Agile web app built with Laravel

### Features
* Create and manage projects with plan and work views
* Group issues in a project into sprints
* Set deadlines for issues, active sprints and projects
* Get reminders via email listing issues nearing deadline
* Responsive UI, *thanks to Bootstrap*

### Screenshots

*Project: Plan View*
![alt tag](https://raw.githubusercontent.com/modestkdr/Scrumwala/master/screenshots/project-plan-view.png)

*Project: Work View*
![alt tag](https://raw.githubusercontent.com/modestkdr/Scrumwala/master/screenshots/project-show-view.png)

### Install Instructions
To install Scrumwala you can clone the repository:

```
$ git clone https://github.com/modestkdr/scrumwala.git.
```

Next, enter the project's root directory and install the project dependencies:

```
$ composer install
```

Next, configure your .env file (root directory) and database (config/database.php). Subsequently, create the database and then run the migrations:

```
$ php artisan migrate
```

### License
Scrumwala is licensed under the MIT license. If you find something wrong with the code or think it could be improved, I welcome you to create an issue or submit a pull request!

repository: craigweiser/Scrumwala

gha_language: CSS

repo_name: craigweiser/Scrumwala


text:
# SwiftLog
Yet Another Logger

[![GitHub issues](https://img.shields.io/github/issues/upbra/swiftlog.svg)](https://github.com/upbra/swiftlog/issues)
[![GitHub release](https://img.shields.io/github/release/upbra/swiftlog.svg)](https://github.com/upbra/swiftlog/)

repository: UpBra/SwiftLog

gha_language: Swift

repo_name: UpBra/SwiftLog


text:
Android Save Object to file and Load Object from file
===================

This is utils class to save java object to file and load Object from file

----------
Feature
-------------
```
1. Encryption disable model

1)the java object will toJson using Jackson ObjectMapper,and save the json string in the file
2)load Object:read the string from the file and transfer the string(json format) to Object

2.Encryption enable model

In order to protect the file, encryption the file is need.
```

----------
Usage

```
1.Save a object without encryption

boolean isSucc = FileUtils.getInstance().saveObject(car,filePath, false);

if the isSucc is true,the the object 'car' save on the file.
```
```
2.Load a object without encryption

Car car = (Car) FileUtils.getInstance().loadObject(filePath, Car.class, false);

```
```
3.Save a object with encryption

boolean isSucc = FileUtils.getInstance().saveObject(car,filePath, true);

if the isSucc is true,the the object 'car' save on the file.
```
```
4.Load a object with encryption

Car car = (Car) FileUtils.getInstance().loadObject(filePath, Car.class, true);

```
```
5.Conclusion

you can open the file(filePath) with a text tools to compare the encryption and without it.

```

License
-------------

Copyright 2014  [Zheng Haibo](https://github.com/nuptboyzhb/)

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.


text:
Frontend API
================
## Introduction
REST API provides a powerful and simple Web services API for interacting with Intel(R) *IoT Services Orchestration Layer*.
The API consist of two groups:

- **DevFrontEnd**
- **UserFrontEnd**

Currently, all of API using the standard **POST** HTTP method.

| API | URL |
|---------|-----|
|`DevFrontEnd`|`http://<host>:8080/apis/dev`|
|`UserFrontEnd`|`http://<host>:3000/apis/user`|

### Example
Fetch the list of apps.

#### Request
Request URL:

`http://localhost:8080/apis/dev`

Requst body:
```json
{"api":"app.list","params":[]}
```

#### Response
```json
[{
  "name":"A4","id":"HOPE_APP_184c1560","description":"A4 XXX",
  "graphs":[{
    "id":"GRAPH_0014b930","name":"G1","description":""
    },{
    "id":"GRAPH_4058fec0","name":"ox","description":""
  }],
  "uis":[{
    "id":"UI_1bb298f0","name":"U1","description":""
  }],
},{
  "name":"A1","id":"HOPE_APP_27598be0","description":"",
  "graphs":[],"uis":[]
}]
```

## Category
### App
#### app.list
**Description**

    Get the list of app.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{"api":"app.list","params":[]}
```
**Response**
```json
[ Array of app_info ]
```

#### app.get
**Description**

    Get a list of app that given in array of app_id.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{"api":"app.get","params":[ Array of app_id ]}
```
**Response**
```json
[ Array of app_info ]
```

#### app.get_widget_data
**Description**

    Get widget data cached in server.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{
  "api":"app.get_widget_data",
  "params":[{
    "app":    app_id,
    "widget": widget_id,
 }]
}
```
**Response**
```json
[ Array of widget data ]
```

#### app.send_widget_data
**Description**

    Post the data to server, this data will be consumed by workflow engine.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{
  "api":"app.send_widget_data",
  "params":[{
    "app":    app_id,
    "widget": widget_id,
    "data": data
 }]
}
```
**Response**

N/A

#### app.create
**Description**

    Create and return an app.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"app.create",
  "params":[{
     "name": app_name,
     "description": app_desc
 }]
```
**Response**
```json
{ app_info }
```

#### app.update
**Description**

    Update the app information.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"app.update",
  "params":[{
     "app": app_id,
     "props": {...}
 }]
```
**Response**
```json
{command log}
```

#### app.remove
**Description**

    Delete one app on the server, this operation will also automatically delete all
    workflows and UI belong it.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"app.remove",
  "params":[{ "app": app_id }]
```
**Response**
```json
{command log}
```

#### app.create_graph
**Description**

    Create a new workflow.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"app.create_graph",
  "params":[{
     "app": app_id,
     "graph": graph_info
 }]
```
**Response**
```json
{command log}
```

#### app.create_ui
**Description**

    Create a new UI.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"app.create_ui",
  "params":[{
     "app": app_id,
     "ui": ui_info
 }]
```
**Response**
```json
{command log}
```

### Graph

**Applicability**

- *DevFrontEnd*

#### graph.get
**Description**

    Get a list of workflow that given in array of graph_id.

**Request**
```json
{"api":"graph.get","params":[ Array of graph_id ]}
```
**Response**
```json
[ Array of graph_info ]
```

#### graph.update
**Description**

    Update one graph.

**Request**
```json
{
  "api":"graph.update",
  "params":[ graph_info ]
```
**Response**
```json
{command log}
```

#### graph.remove
**Description**

    Delete workflows on the server.

**Request**
```json
{
  "api":"graph.remove",
  "params":[ Array of graph_id ]
```
**Response**
```json
{command log}
```

#### graph.start
**Description**

    Start workflows on the server.

**Request**
```json
{
  "api":"graph.start",
  "params":[ Array of graph_id ]
```
**Response**
```json
{}
```

#### graph.stop
**Description**

    Stop workflows on the server.

**Request**
```json
{
  "api":"graph.stop",
  "params":[ Array of graph_id ]
```
**Response**
```json
{}
```

#### graph.status
**Description**

    Get the status of workflows, valid status is "Non-exist", "Working", "Paused", "Stopped"
    or "Idle".

**Request**
```json
{
  "api":"graph.status",
  "params":[ Array of graph_id ]
```
**Response**
```json
[ Array of {
  "graph": graph_id,
  "status": status
}]
```

#### graph.trace
**Description**

    Get the tracing data of workflows.

**Request**
```json
{
  "api":"graph.trace",
  "params":[ Array of graph_id ]
```
**Response**
```json
[ Array of {
  "id": graph_id,
  "trace": [ Array of records ]
}]
```

### UI
#### ui.get
**Description**

    Get a list of UI that given in array of ui_id.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{"api":"ui.get","params":[ Array of ui_id ]}
```
**Response**
```json
[ Array of ui_info ]
```

#### ui.update
**Description**

    Update one UI.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"ui.update",
  "params":[ ui_info ]
```
**Response**
```json
{command log}
```

#### ui.remove
**Description**

    Delete workflows on the server.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"ui.remove",
  "params":[ Array of ui_id ]
```
**Response**
```json
{command log}
```

### Spec

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

#### spec_bundle.list
**Description**

    Get the list of all available spec bundle.

**Request**
```json
{"api":"spec_bundle.list","params":[]}
```
**Response**
```json
[ Array of spec_bundle_info ]
```

#### spec_bundle.get
**Description**

    Get the list of spec bundle that given in array of spec_bundle_id.

**Request**
```json
{"api":"spec_bundle.get","params":[ Array of spec_bundle_id ]}
```
**Response**
```json
[ Array of spec_bundle_info ]
```

#### spec_bundle.get_for_specs
**Description**

    Get the list of spec bundle that includes spec in array of spec_id.

**Request**
```json
{"api":"spec_bundle.get_for_specs","params":[ Array of spec_id ]}
```
**Response**
```json
[ Array of spec_bundle_info ]
```

### Hub
#### hub.list
**Description**

    Get the brief list of all available Hub.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{"api":"hub.list","params":[]}
```
**Response**
```json
[ Array of {
  "id": hub_id,
  "name": hub_name,
  "description": hub_desc
}]
```

#### hub.get
**Description**

    Get a list of Hub given in array of hub_id.

**Applicability**

- *DevFrontEnd*
- *UserFrontEnd*

**Request**
```json
{"api":"hub.get","params":[ Array of hub_id ]}
```
**Response**
```json
[ Array of hub_info]
```

#### hub.create_thing
**Description**

    Create a new thing on the Hub.

**Applicability**

- *DevFrontEnd*

**Request**
```json
{
  "api":"hub.create_thing",
  "params":[{
    "hub": hub_id,
    "thing": {
       "type": "hope_thing",
       "name": thing_name,
       "description": thing_desc
    }
   }]
}
```
**Response**
```json
{
  "id": thing_id,
  "name": thing_name,
  "type": "hope_thing"
}
```

### Thing
**Applicability**

- *DevFrontEnd*

#### thing.update
**Description**

    Update the thing information.

**Request**
```json
{
  "api":"thing.update",
  "params":[{
     "id": thing_id,
     ...
 }]
```
**Response**
```json
{}
```

#### thing.remove
**Description**

    Delete things on the server, this operation will also automatically delete all
    services belong it.

**Request**
```json
{
  "api":"thing.remove",
  "params":[[ thing_id ]]
```
**Response**

N/A

#### thing.create_service
**Description**

    Create a new service on the Thing.

**Request**
```json
{
  "api":"thing.create_service",
  "params":[{
    "thing": thing_id,
    "service": {
       "type": "hope_service",
       "spec": spec_id or spec,
       "name": service_name,
       "description": service_desc
    }
   }]
}
```
**Response**
```json
{
  "id": service_id,
  "name": service_name,
  "type": "hope_service"
}
```

### Service
**Applicability**

- *DevFrontEnd*

#### service.update
**Description**

    Update the service information.

**Request**
```json
{
  "api":"service.update",
  "params":[{
     "id": service_id,
     ...
 }]
```
**Response**
```json
{}
```

#### service.remove
**Description**

    Delete services on the server, this operation will also automatically delete all codes
    for it.

**Request**
```json
{
  "api":"service.remove",
  "params":[[ service_id ]]
```
**Response**

N/A

#### service.list_files
**Description**

    Get a list of file that service had and/or expected for.

**Request**
```json
{
  "api":"service.list_files",
  "params":[ service_id ]
```
**Response**
```json
{
  "expected": [ Array of filename ],
  "existing": [ Array of filename ]
}
```

#### service.read_file
**Description**

    Read a service file.

**Request**
```json
{
  "api":"service.read_file",
  "params":[{
    "service_id": service_id,
    "file_path": file_path
  }]
```
**Response**
```json
{
  "content": String of file content
}
```

#### service.write_file
**Description**

    Write a service file.

**Request**
```json
{
  "api":"service.write_file",
  "params":[{
    "service_id": service_id,
    "file_path": file_path,
    "content": String of file content
  }]
```
**Response**
```json
{
  service_brief_object
}
```

#### service.remove_file
**Description**

    Delete a service file.

**Request**
```json
{
  "api":"service.remove_file",
  "params":[{
    "service_id": service_id,
    "file_path": file_path
  }]
```
**Response**
```json
{
  service_brief_object
}
```

repository: mrbian/Other-intel-iot

repo_name: mrbian/Other-intel-iot


text:
# Consequences Schema

```txt
#/properties/dataDisclosed/items/anyOf/0/properties/nonDisclosure/properties/consequences#/properties/dataDisclosed/items/anyOf/0/properties/nonDisclosure/properties/consequences
```

Description of the consequences in the case of non-disclosure.

| Abstract            | Extensible | Status         | Identifiable            | Custom Properties | Additional Properties | Access Restrictions | Defined In                                                           |
| :------------------ | ---------- | -------------- | ----------------------- | :---------------- | --------------------- | ------------------- | -------------------------------------------------------------------- |
| Can be instantiated | No         | Unknown status | Unknown identifiability | Forbidden         | Allowed               | none                | [tilt-schema.json\*](../out/tilt-schema.json "open original schema") |

## consequences Type

`string` ([Consequences](tilt-schema-properties-datadisclosed-items-anyof-anyof-schema-properties-nondisclosure-properties-consequences.md))

## consequences Examples

```json
"If the data is not disclosed, the shipment cannot be delivered."
```


text:
### [CVE-2014-2448](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-2448)
![](https://img.shields.io/static/v1?label=Product&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

Unspecified vulnerability in the PeopleSoft Enterprise PT PeopleTools component in Oracle PeopleSoft Products 8.52 and 8.53 allows remote attackers to affect confidentiality via unknown vectors related to Install and Packaging.

### POC

#### Reference
- http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html

#### Github
No PoCs found on GitHub currently.

repository: trickest/cve

repo_name: trickest/cve


text:
![safeDelivr](http://i.imgur.com/ZGzd6kW.png)
-----------------------------------------------------------------------------------------------------------------

## Architecture
![Basic Architecture](http://i.imgur.com/YPTyw1X.png)

Safedelivr has the following core components
- User  : A github oAuth user
- Batch : An Email Batch
- Logs  : A status Log of each recipient
- Stats : A stats counter
- Worker: A queue consumer

## User
User is a basic entity of the safedelivr system. It has the following key properties.

|   User_Id     |      Email       |    Auth_Token     |     Api_Key       |
----------------|------------------|-------------------|-------------------|
|   Time UUID   |    varchar       |   Github Token    |    Unique Api_Key |

There isn't much to explain about the User entity as it is self explanatory.

## Batch
A Batch is a fundamental entity defining an email task, whenever the API is been hit, system generates a Batch_Id corresponding to the email delivery job.

A Batch has the following key parameters.

|   Batch_Id     |      User_Id               |    Subject              |     Options                                     |
-----------------|----------------------------|-------------------------|-------------------------------------------------|
|   Time UUID    |    The owner of this batch |   Subject Line of Email |    A map of options associated to this job      |

The _Options_ property of the Batch is a map which has the following keys

|     Key         |       Value                                     |
|-----------------|-------------------------------------------------|
|      _to_       |   A comma separated list of recipients         |
|     _from_      | Standard SMTP _from_ email address field       |
|     _body_      | HTML string                                     |
|    _reply_to_   |  Standard SMPTY _reply_to_ email address field  |

Whenever a client sends a batch creation task, system will acknowledge the request after performing necessary checks and will than save the job in the cassandra DB and publish a ```batch.batch-uuid``` key on the AMQP server.

A typical flow of batch creation is depicted below.
![Batch Creation](http://i.imgur.com/z11050c.png)
## Logs

A log is a bidirectional entity, it corresponds to an individual event/log for a given email address which has been dispatched by the provider. The logs are generated whenever the system receives an event corresponding to an email address via webhooks from the email provider. There are different types of events that are sent by the providers, the generic ones are the following.

|     Event Name     |         Meaning                                        |
|--------------------|--------------------------------------------------------|
|     processed      | Provider has dispatched the email.                     |
|     sent/delivered | Email has been successfully delivered                  |
|     dropped        | Mail has been dropped/bounced/hardfailed               |
|     delayed        | Mail service provider will retry sending the mail later|

From the above list, our system narrows down the events to ```success```, ```failure``` and ```queued```.

An email/log is said to be in __queued__ state if:
- Dispatched from our end, not yet received any status update.
- Failed by one/many providers and has been put back in queue for retrial with another provider.

An email/log is said to be in ___failed___ state if:
- Provider sends hardbounce/dropped/bounced event for that email.
- While retrying we exhausted out of the providers and don't have any options to retry with.

__Success__ state is self explanatory.
The main parameters of a Log doc are:

|     Log_Id          |           Batch_Id          |            User_Id          |        Email           |      State            |           Status                               |
----------------------|-----------------------------|-----------------------------|------------------------|-----------------------|------------------------------------------------|
|  Time UUID          |     Associated Batch_Id     |    Associated User_Id       |      Recipient Email   | queued/failed/success |      A map<> that holds the status of retrials |

The __status__ field is a boolean map which looks like this, it tells the system which provider we have retried with
```json
{
  "sendgrid": true,
  "mailgun":  false
}
```
## Stats

This is a meta doc which keeps track of counts for daily failures, success and queued emails in the system. Doc structure is pretty basic.

|    User_Id       |     Date        |      success        |      failure        |     queued         |
|------------------|-----------------|---------------------|---------------------|--------------------|
|   User Id        | Date of the stat|      counter        |       counter       |     counter        |

Overall Doc structure of complete system is shown below for reference.
![Doc Structure](http://i.imgur.com/getX1Mn.png)

## Consumers

Consumers are rabbitmq consumers listening on different queues, queues used by the system are categorized as:
- Generic Batch Processing consumer
- Individual Exclusive service provider based consumers
- Individual Exclusive Log retry consumers

### Generic Consumers

Generic consumers are associated to the batch processing part, they keeps on processing new enqueued batch that needs to be dispensed off.

Generic consumers listens for batches on the routing key ```batch.#```, where # corresponds to the batch's UUID.

Whenever a generic consumer fails to dispatch the mail batch request, it enqueues the packet into the exclusive consumer queue of a provider other than itself with an appended ```.retry._int_retry_count_``` routing key.
The appended ```retry``` field in routing key helps the exclusive queues in taking decision as to when to stop trying.

### Individual Exclusive Batch Consumers

These are service provider specific consumers, they will try to dispatch an email through the provider they are associated to e.g. Sendgrid, MailGun. They too follow the same method of retrial in case of failure i.e. Push into another service provider's queue.

### Individual Exclusive Log Consumer

These are also similar to individual batch consumers and consumes packets of ```log.provider_namespace.log-uuid``` signature. Whenever our system receives a delayed/failure response via webhooks by a service provider and we know we can retry sending mail to that particular recipient with another mail provider, the system will push that logid to another service provider's namespaced consumers.

Currently the signature of routing keys in the system are the following:

|      Routing Key                               |         Associated consumer          |
|------------------------------------------------|--------------------------------------|
|   _batch.00000000-0000-0000-0000-000000000000_   | Round Robin based (sendgrid/mailgun)  |
|   _mg.00000000-0000-0000-0000-000000000000_      |     __Mailgun__                          |
|   _sg.00000000-0000-0000-0000-000000000000_      |     __Sendgrid__                         |
|   _mg.00000000-0000-0000-0000-000000000000_.__retry.#num__|   __Mailgun__                       |
|   _sg.00000000-0000-0000-0000-000000000000_.__retry.#num__|   __Sendgrid__                      |
|   _log.mg.00000000-0000-0000-0000-000000000000_       |   __Mailgun__                       |
|   _log.sg.00000000-0000-0000-0000-000000000000_       |   __Sendgrid__                      |
|   _log.sg.00000000-0000-0000-0000-000000000000_.__retry.#num__|  __Sendgrid__                   |
|   _log.mg.00000000-0000-0000-0000-000000000000_.__retry.#num__|  __Mailgun__                    |

## Fail safe mechanism

Whenever the system encounters a failure, it is bound to retry until any one of the following condition is met:
- Successfully dispatched through one of the provider
- Ran out of service providers
- Ran out of number of retries

### Batch Lifecycle

A lifecycle of a Batch in fail safe mode is shown below
![Batch Lifecycle](http://i.imgur.com/vyGGuDe.png)

### Log Lifecycle
Lifecycle for a log in fail safe mode.
![Log Lifecycle](http://i.imgur.com/iWyhp6c.png)

## Adding Email Provider

Addition of a new Email provider is quite easy as long as the provider has webhook feedback mechanism, to add a new email provider you will need to add the following things:
- Add a Channel and append it to the [rabbit.EmailProvideres](https://github.com/DronRathore/safedelivr/blob/master/src/rabbit/setup.go#L47)
- Implement a consumer. Consumers are generically executed, have a look at the [sendgrid one](https://github.com/DronRathore/safedelivr/blob/master/src/worker/sendgrid.go#L26) to get an idea.
- Add a [webhook controller](https://github.com/DronRathore/safedelivr/blob/master/src/controller/webhook.go#L23-L203) for the same.
## Architecture flaws
- Current architecture doesn't keep state of consumer based failures, we can have a consumer based failure states so that they can be taken offline if any of them is failing rigorously
- Instead of immediately pushing for retry in case of a provider failure we can use [Dead Letter Exchange](http://yuserinterface.com/dev/2013/01/08/how-to-schedule-delay-messages-with-rabbitmq-using-a-dead-letter-exchange/) mechanism and add a delay in our retries, optionally we can make use of go context timeouts.
## Future Scope
 - An addition of a cron like consumer for delayed or unacknowledged entity will enhance the whole system's robustness.
 - Allow user defined webhooks to make it a completely service driven framework

MIT LICENSED

repository: DronRathore/safedelivr

repo_name: DronRathore/safedelivr


text:
![Railsbridge 100%](img/railsbridge-cape-town-logo-large.png)

^ intros
name, what you do. alumni?
work through course
ask us Qs

---

## Your development set up
# Text editor, Browser, Terminal

![Sublime Text inline](img/set-up-text-editor.png) ![Browser inline](img/set-up-browser.png) ![Terminal inline](img/set-up-terminal.png)

^ Write Code
See the Results
Issue Commands

---

### Why are we here?

## Diversity in Cape Town tech
## Programming skills: useful, empowering, fun

^ People making the software should reflect the people using it
Especially on the web

---

# Code of Conduct: [rbcpt.org/code](http://rbcpt.org/code/)

---

### Open source workshop

## Community project
## Editable by anyone

^ site, docs, activities
not the animal stickers

---

### More betterer

## Make notes as you go along
## Survey: [rbcpt.org/exitsurvey](http://rbcpt.org/exitsurvey)

^ We've added: breaks; overview; glossary; lightning talk
Survey is anonymous

---

### Goal of the day
## build a web page about yourself
## build a job board (in Rails)

^ In our case, a voting system

---

### After today?

## [rbcpt.org/resources](http://rbcpt.org/resources/)
## More coding, Ruby, or Rails
## Do another RailsBridge

^ Intro to Rails course?
Become a developer?

---

## Help us improve the docs: stickies!
## @RailsBridgeCPT #railsbridge

---

## Our awesome sponsors

---

## Warm-up activity

---

# [rbcpt.org/frontend](http://rbcpt.org/frontend/)
# [rbcpt.org/job](http://rbcpt.org/job/)

repository: RailsBridge-CapeTown/presentations

repo_name: RailsBridge-CapeTown/presentations


text:
# Content Types

Any payload supplied in a web request is normally parsed using the content type on the request's headers. However, it's possible to override - or *force* - a specific content type on routes when parsing the payload. This can be achieved by either using the `-ContentType` parameter on the  [`Add-PodeRoute`](../../../../Functions/Routes/Add-PodeRoute) function, or using the [`server.psd1`](../../Configuration) configuration file.

When a specific content type is supplied then any payload will be parsed as that content type only - even if the content type is supplied on the web request's header. This way, you can force a route to only accept a certain content type.

## Routes

You can specify a content type to use per route by using the `-ContentType` parameter.

For example, if you have two routes you can force one to only parse JSON and the other XML as follows:

```powershell
Start-PodeServer {
    Add-PodeEndpoint -Address * -Port 8080 -Protocol Http

    Add-PodeRoute -Method Get -Path '/api/json' -ContentType 'application/json' -ScriptBlock {
        Write-PodeJsonResponse -Value @{}
    }

    Add-PodeRoute -Method Get -Path '/api/xml' -ContentType 'text/xml' -ScriptBlock {
        Write-PodeXmlResponse -Value @{}
    }
}
```

If the `/api/json` endpoint is supplied an XML payload then the parsing will fail.

## Configuration

Using the `server.psd1` configuration file, you can define a default content type to use for every route, or you can define patterns to match multiple route paths to set content types on mass.

### Default

To define a default content type for everything, you can use the following configuration:

```powershell
@{
    Web = @{
        ContentType = @{
            Default = "text/plain"
        }
    }
}
```

### Route Patterns

You can define patterns to match multiple route paths, and any route that matches (when created) will have the appropriate content type set.

For example, the following configuration in your `server.psd1` would bind all `/api` routes to `application/json`, and then all `/status` routes to `text/xml`:

```powershell
@{
    Web = @{
        ContentType = @{
            Routes = @{
                "/api/*" = "application/json"
                "/status/*" = "text/xml"
            }
        }
    }
}
```

## Precedence

The content type that will be used is determined by the following order:

1. Being defined on the Route.
2. The Route matches a pattern defined in the configuration file.
3. A default content type is defined in the configuration file.
4. The content type supplied on the web request.

repository: Jaykul/Pode

repo_name: Jaykul/Pode


text:
# A Concept for V-Sekai

I've been contemplating an unconventional concept for V-Sekai. The idea revolves around the creation of not just one or two, but a hundred interactive worlds from me!

Drawing inspiration from VRChat, which boasts millions of such interactive environments, I believe it's feasible to create a hundred of my own.

The challenge lies not in the quantity but in the quality and interactivity of these worlds. However, with the right amount of dedication and creativity, I am confident that this ambitious project can be realized.

repository: V-Sekai/manuals

repo_name: V-Sekai/manuals


text:
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

---

**advancedfx specific?**

Please check that the bug is specific to the advancedfx modded version and not present in the original https://github.com/namazso/nSkinz and otherwise report it there in stead please.

**Describe the bug**

repository: advancedfx/nSkinz

branch_name: refs/heads/advancedfx

repo_name: advancedfx/nSkinz


text:
# NBA Data

> Project folder for all my Jupyter Notebooks and NBA data workings.

## Coding conventions

- [black](https://github.com/psf/black) for formatting
- [google docstrings](https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings)
- [flake8](https://flake8.pycqa.org/en/latest/index.html#quickstart) for linting
- [mypy](http://mypy-lang.org/) for static typing analysis
- [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) for commit style.
- [isort](https://github.com/timothycrosley/isort/) for import organization.

## Overview

Currently working on some analysis with Power BI. To get the NBA data I created some Python scripts that run through NBA stats pages and storing the data into a PostgreSQL database. I've model the data in form of a star schema to work well with Power BI and it's data modeling.

## Todo Checklist

A helpful checklist to gauge how your README is coming on what I would like to finish:

- [ ] Lots of items! :)

## 🤝 Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

1. Fork this repository;
2. Create your branch: `git checkout -b my-new-feature`;
3.  Push to the branch: `git push origin my-new-feature`.

**After your pull request is merged**, you can safely delete your branch.

## 📝 License

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

repository: JovaniPink/nba-data

repo_name: JovaniPink/nba-data


text:
# vstatus [![](https://img.shields.io/crates/v/vstatus.svg)](https://crates.io/crates/vstatus) [![License](https://img.shields.io/badge/license-ISC-blue.svg)](/LICENSE) [![Build status](https://travis-ci.org/Arkanosis/vstatus.svg?branch=master)](https://travis-ci.org/Arkanosis/vstatus)

**vstatus** is a lightning-fast version control status string generator that you can use wherever you want (eg. in your shell prompt: bash, zsh, fish…).

## Current Status

vstatus is still under active design and not yet ready for mainstream usage.

## Design goals

vstatus aims at the following objectives:
* be extremely lightweight, self-contained and easy to deploy;
* be lightning-fast, to avoid slowing down a terminal if used to draw an informative prompt;
* be extensible enough to support multiple VCS (git, mercurial, subversion, fossil, veracity…)
* be customizable enough to support arbitrary formatting options.

## Compilation

Run `cargo build --release` in your working copy.

## Installation

Copy the `vstatus` binary wherever you want.

## Usage

```
Usage: vstatus <format>
       vstatus -h | --help
       vstatus --version

Arguments:
    format      Version control status string format

Options:
    -h, --help  Show this screen.
    --version   Show version.
```

## Contributing and reporting bugs

Contributions are welcome through [GitHub pull requests](https://github.com/Arkanosis/vstatus/pulls).

Please report bugs and feature requests on [GitHub issues](https://github.com/Arkanosis/vstatus/issues).

## License

vstatus is copyright (C) 2018 Jérémie Roquet<EMAIL_ADDRESS>and licensed under the ISC license.

license: ISC

repository: Arkanosis/vstatus

repo_name: Arkanosis/vstatus


text:
# Changelog

## Unreleased - 2019-05-05  - updated from Minimo master

### Changed

- Forked from [Minimo project][minimo-github] and branded.

[minimo-github]: https://github.com/MunifTanjim/minimo/


text:
# How to claim test token

## Create new account

If you already have an account, you can skip this step.

If you don't have an account, you can use `nchcli` to create a new account as follows:

```bash
nchcli keys add <key_name>
```

Enter the wallet password as prompted, and get the following example output:

```bash
- name: lucy
  type: local
  address: nch1p3fuppcxud5rjsaywuyuguh6achmj5p0r6z6ve
  pubkey: nchpub1addwnpepqg8mfc6t9eaw9lal0c4tzma5vgmqzkgszwcgljcz3sy8rd2rukgxz9dtmph
  mnemonic: ""
  threshold: 0
  pubkeys: []

**Important** write this mnemonic phrase in a safe place.
It is the only way to recover your account if you ever forget your password.
# The following is Mnemonic
connect plug cigar purchase inflict enroll ten limb quantum never supply grid home case process claw truly grape federal liberty tree remove side quantum
```

The mnemonic can be used to restore the account. The command to restore the account is:

```bash
nchcli keys add <key_name> --recover
```

## Claim test token

Faucet address: ```https://docs.netcloth.org/nch/get_token?<address>```

Replace `` `<address>` '' with your wallet address to get the test token

## How to check your balance

**Method A:** Query via blockchain explorer

**Method B:** Query via nchcli

You can execute the following command to check your balance.

```bash
nchcli query account [address]
```

repository: netcloth/docs

repo_name: netcloth/docs


text:
# Set Security Center Contact Details

## Display Name

Automatically set the security contact email address and phone number should they be blank on the subscription

## Mode

`All`

## Description

Enters an email address and phone number to receive notifications when Azure Security Center detects compromised resources

## Built-In Reference

Modified from: [Built-In: ASC_Security_contact_email.json](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Security%20Center/ASC_Security_contact_email.json)

Modified from: [Built-In: ASC_Security_contact_phone_number.json](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Security%20Center/ASC_Security_contact_phone_number.json)

- [Microsoft Documentation](https://docs.microsoft.com/en-us/azure/security-center/)
- [API Reference](https://docs.microsoft.com/en-us/azure/templates/microsoft.security/securitycontacts)


text:
# :PROJECT_NAME

:PROJECT_DESCRIPTION

# Usage
```
        /\
       /  \
      / _o \
     / <(\  \
    /   />`A \
   '----------`
  Under Construction
```

# Testing

Run all unit tests and generate code coverage reports.
```
composer run test
```

repository: xiian/composer-generator

repo_name: xiian/composer-generator


text:
# Cocoon

A simple php view renderer.

# Requirements

* Composer
* PHP 7.1 or greater

# Installation

To install Cocoon via composer, run the following command:

    composer require james-draper/cocoon

# Getting started

Here is a simple example of how to render a view, for a more detailed explanation consult the [documentation](docs/contents.md).

    <?php

    $factory = new \Cocoon\Factory([__DIR__ . '/views'])
    return $factory
        ->create('path/to/template')
        ->setVar('some_var', 123)
        ->setVarRaw('some_other_var', 456)
        ->render();

The above code snippet first creates a factory, uses the factory to creates a view, assigns variables to that view, and then renders the view.
Below is what the template file might contain.

var1: <?php echo $this->some_var; ?>

var2: <?php echo $this->some_other_var; ?>

repository: JamesDraper/cocoon

repo_name: JamesDraper/cocoon


text:
# Authentication - I01 IdentityBasics

## Demonstrates

 * Async Main
 * Dependency Scope Access in Main
 * Newer AspNetCore 3.x Routing/Endpoint setup
 * How to setup Razor for RuntimeCompilation in AspNetCore 3.x (in Debug) to view edits on the fly.
 * EntityFramework Core
   * EntityFramework Core InMemory
   * AppDbContext
 * AspNetCore Identity
   * AspNetCore Identity with EntityFramework
   * IdentityDbContext replaces DbContext
   * Using UserManager<T>
   * Using SignInManager<T>
   * Configuring the Cookie properties used by Identity
 * Authorization and Authentication middleware usage.
 * Creating a login.
 * Creating a user.
 * Creating a logout.
 * Various tag helpers.
 * Specific Controller/Action httpmethod and routing.

## Sources

Microsoft Docs - Tag Helpers
https://docs.microsoft.com/en-us/aspnet/core/mvc/views/working-with-forms?view=aspnetcore-3.1

Microsoft Docs - DI
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-3.1

Microsoft Docs - Controller Methods and Views
https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/controller-methods-views?view=aspnetcore-3.1

Identity Tutorial - Raw Coding Youtube Guide (This just done really well)
https://www.youtube.com/watch?v=IjbtWPXVJGw

repository: houseofcat/Authentication

gha_language: C#

repo_name: houseofcat/Authentication


text:
# redux-mock-store [![Circle CI](https://circleci.com/gh/arnaudbenard/redux-mock-store/tree/master.svg?style=svg)](https://circleci.com/gh/arnaudbenard/redux-mock-store/tree/master)

![npm](https://nodei.co/npm/redux-mock-store.png?downloads=true&downloadRank=true&stars=true)

A mock store for testing your redux async action creators and middleware. The mock store will create an array of dispatched actions which serve as an action log for tests.

Please note that this library is designed to test the action-related logic, not the reducer-related one. In other words, it does not update Redux store. If you want a complex test combining action and reducer together, take a look at other libraries (e.g., [redux-actions-assertions](https://github.com/redux-things/redux-actions-assertions)). Refer issue [#71](https://github.com/arnaudbenard/redux-mock-store/issues/71) for more detail.

## Install

```
npm install redux-mock-store --save-dev
```
## Documentation

You can see the latest documentation [here](http://arnaudbenard.com/redux-mock-store/).

### Old version (`< 1.x.x`)

https://github.com/arnaudbenard/redux-mock-store/blob/v0.0.6/README.md

## License

The MIT License

repository: ohtangza/redux-mock-store

repo_name: ohtangza/redux-mock-store