text:
# Aperture JS bootstrap

The Aperture JS bootstrap project is a simple full-stack starting point for creating single-page applications using [Aperture JS](https://github.com/oculusinfo/aperturejs). It separates development of the html/js/css client (using client development best practices) from that of the Java server (with Java best practices). This client-server code separation was inspired by [Making Maven Grunt](http://addyosmani.com/blog/making-maven-grunt/) by [Addy Osmani](http://addyosmani.com/) and the [JHipster yeoman generator](http://jhipster.github.io/).

## Design

The client-side development environment uses [bower](http://bower.io/) for client package management, [gulp](http://gulpjs.com/) for build scripting, [stylus](http://learnboost.github.io/stylus/) (+ [nib](https://github.com/visionmedia/nib)) as a css preprocessor, and other common development tools such as [jshint](http://www.jshint.com/), [gulp-useref](https://github.com/jonkemp/gulp-useref), [uglifyjs](https://github.com/mishoo/UglifyJS2), [connect](http://www.senchalabs.org/connect/) and [livereload](https://github.com/intesso/connect-livereload). It is meant to be a good starting point but not prescriptive. It is entirely feasible to change any or all parts to fit your development preferences.

The server-side development environment uses Maven and the Jetty webapp container. The server code itself uses [Restlet](http://restlet.com/) and Google [Guice](https://code.google.com/p/google-guice/) which are both heavily used by the Aperture JS server components. A different server architecture can easily be used provided that any Aperture JS services you require are still exposed.

## Setup

Ensure that the following development tools are installed:

 1. [JDK (v7+)](http://www.oracle.com/technetwork/java/javase/downloads/index.html)
 1. [Apache Maven](http://maven.apache.org/)
 1. [node.js & npm](http://nodejs.org/download/) - `npm` will automatically be installed as part of most node.js packages

A minimal setup is sufficient for an automated build or CI machine and you'll be able to do everything you need to do, but some commands may be a little clunky. For the best possible development experience, also install:

 1. [bower](http://bower.io/) - `npm install -g bower`
 1. [gulp](http://gulpjs.com/) - `npm install -g gulp`

Next, clone this repo locally:

```
git clone https://github.com/oculusinfo/aperturejs-bootstrap.git my-aperture-app
```

## Usage

### Development

#### Client

First install all dependencies. From the `my-aperture-app/client` directory run:
```
npm install
bower install
```
*Note: if you didn't install bower globally you'll need to run `./node_modules/.bin/bower` instead of `bower`

During development the client code is managed and served out by a local node.js express server running on port `9000` (the port is configurable in `gulpfile.js`. The development server will compile (stylus) then livewatch and update the browser on any changes. It proxies all requests to `/aperture` and `/rest` paths to the Java server running on port `8080` which you must run as a seperate process. Any additional paths that need to be opened up to the back end should be added to the proxy configuration settings near the top of `gulpfile.js`.

To run the client-side development build, server, and auto-compile/reload on change use the following command from the `my-aperture-app/client` directory:
```
gulp serve
```

#### Server

Before building and running the server for the first time, ensure you have cloned the [Aperture JS repo](https://github.com/oculusinfo/aperturejs), built, and installed the artifacts into your local Maven repository. This only needs to be done once:

```
cd {/somewhere appropriate on your filesystem/}
git clone https://github.com/oculusinfo/aperturejs.git
cd aperturejs/aperture
mvn install
```

During development the Java servlet only handles "API" requests. html, js, css and other "front-end" files are all handled by the gulp client development server.

To run the development API server on port `8080` use the following command from the `my-aperture-app/server` directory:
```
mvn jetty:run
```

Point your favorite browser at `http://localhost:9000` and start developing.

### Production

To build the production WAR file, run the following from the `my-aperture-app/server` directory:

```
mvn clean install -Denvironment=deployment
```

This will include a stage that does `npm install`, `bower install` and builds the production client distribution. The generated WAR file will contain the entire server and client package. This WAR can be found in `my-aperture-app/server/target`.

To run and test the built production server:

```
mvn jetty:run -Denvironment=deployment
```

Generally the server build process will handle making the production client for a final release. However, the production client build can be executed and tested independently of the back end. To build the front-end, run from the `my-aperture-app/client` directory:
```
gulp build
```

## Troubleshooting

#### npm won't install packages globally, requests sudo
If you'd rather not install global npm packages with `sudo` take a look at https://gist.github.com/isaacs/579814 or run:
```
npm config set prefix ~/npm
```
And add the following line to your `.bashrc`:
```
export PATH=$HOME/npm/bin:$PATH
```
*Courtesy of http://stackoverflow.com/a/18277225/1204216*

#### Unable to connect to github.com via git:// protocol
A local or network firewall may be blocking the port that the `git://` protocol is trying to use. Instruct git to fallback to `https`
```
git config --global url.https://github.com/.insteadOf git://github.com/
```

#### The server build fails, cannot find artifact `oculus.aperture.*`
At this time the Aperture JS JAR files are not available in a public Maven repository. Until they are you must clone the Aperture JS source (https://github.com/oculusinfo/aperturejs) and follow the instructions to build and install the artifacts into your local maven repository.

repository: drzo/aperturejs-bootstrap

branch_name: refs/heads/develop

repo_name: drzo/aperturejs-bootstrap


text:
# In-memory Cache ![Continous Integration](https://github.com/KTH/in-memory-cache/actions/workflows/main.yml/badge.svg)

Npm: `@kth/in-memory-cache`

This is how you use the in-memory cache. It is a very basic iplementation.

```javascript

const cache = require("@kth/in-memory-cache");

const user = { firstName: "John", lastname: "Doe" }

cache.add('user-id', user);

if (cache.isValid('user-id')) {
    console.log('Users lastname is ' + cache.get('user-id').lastname);
}

cache.remove('user-id');
```

## TTL - Set the time an item is valid

If a cache item should live for a long time you can set a time to live (TTL) on it in milliseconds on the item.

```javascript
const cache = require('@kth/in-memory-cache');

const aDay = 1000 * 60 * 60 * 24;
const user = { firstName: 'John', lastname: 'Doe' }

cache.add('long-caching-object', user, aDay);
```

## Limit the number of items in the store

Sometimes you whould like to limit the number of items that are stored in the cache.
This is not a FIFO, if there is space, the item will be added. Otherwise silently ignored.

```javascript
const cache = require('@kth/in-memory-cache');

cache.setMaxSlots(2)

cache.add('key-1', 'value 1');
cache.add('key-2', 'value 2');
cache.add('key-3', 'value 3'); // not added, with logger.info(str) message

cache.length(); // 2
```

## Use your own logger

Your project probably already have a logging framework, you can pass it to the cache.
The default logger is console.

```javascript
const cache = require('@kth/in-memory-cache');
const log = require('someLogger')

// The logger needs to implement the function info(string)
cache.setLogger(log);

```

## Run tests

To run the tests, do npm magic or run `./build.sh`. You can also view the tests at https://travis-ci.org/KTH/in-memory-cache

```bash
npm install
npm test
```

```text
  Cache - Add
    ✓ 'Null' is an acceptable cache item value.
    ✓ 'Undefined' is an acceptable cache item value.
    ✓ When no TTL is passed, the default 1000ms is used as the time for an item to live.
    ✓ Use a specific TTL for an item to live.
    ✓ When a max slot is set no more items are added, until old ones are removed.

  Cache - Get
    ✓ It is possible to store and get a string.
    ✓ It is possible to store and get a number.
    ✓ It is possible to store and get an object.
    ✓ If the TTL has expired, 'undefined' will be returend for the item key.
    ✓ If there is no matching item in the store 'undefined' will be returned.

  Cache - Remove
    ✓ It is possible to remove one specific item in the cache.
    ✓ It is possible to remove all items in the cache.
    ✓ Nothing happens if you remove an item that is not in the store.

  Cache - Number of slots
    ✓ It is possible to get the numer of items in the cache.
    ✓ It is possible to set the maximum number of items in the cache.

  Cache - logger
    ✓ It is possible to set an external logger.

```

license: MIT

repository: KTH/in-memory-cache

branch_name: refs/heads/master

extension: md

gha_language: JavaScript

gha_license_id: MIT

license_type: permissive

repo_name: KTH/in-memory-cache


text:
---
id: 468
title: 'Azure Web Site - First Experiment'
date: 2014-04-18T10:14:22+00:00

layout: single
guid: http://gregwoods.co.uk/2014/04/463-revision-v1/
permalink: /2014/04/azure-website-experiment-1/
---
OK, I'm very late to the party with Windows Azure. My feeble excuse is that I've no use for it in the day job. Like I said.. feeble. Anyway, I decided I wanted to play with Azure, but desired more than 'Hello World' static web page. My WebDev skills need some serious updating, so I wanted a small application which used a database, and built using cutting edge technologies. After a not very exhaustive search, I decided John Papa's CodeCamper app would be ideal. Unfortunately, several half baked or out of date guides on getting it to run on Azure left me frustrated.  So, after about a dozen clone-modify-publish-delete cycles... I got it to work. Here are my very unpolished notes.

## Software pre-requisities

  * VS2013
  * NOTE to self: try it with WebMatrix
  * Git

## Set up your Azure account

I won't go into details here, but here is what you need to be able to access <pic of https://manage.windowsazure.com>

## Get the code

The source is here: [https://github.com/johnpapa/CodeCamper](https://github.com/johnpapa/CodeCamper)

If you have git for windows installed, simply:

```sh
git clone https://github.com/johnpapa/CodeCamper.git "C:\development\codecampergwtest"
```

Note: one my work machine I can clone into '.' (the current directory), yet at home, it results in a directory not empty message

## Get it running locally

  *  open VS2013 as Administrator (if you don't, some NuGet commands will not work)
  * open NuGet package Manager console
  * You'll see a message "Some NuGet packages are missing from this solution. Click to restore from your online package sources."  - click "Restore"
  * Build solution
  * Run solution - it should all work, with sample data populated

##  Modify it work with Azure db

In order to see the sample data, we need to enable something called 'Data Migrations', which is part of Entity Framework Code First. However, the NuGet command "Enable-Migrations" isn't available with Entity Framework 5.0.0 which is setup by default with this solution So in NuGet package manager <span style="line-height: 1.5em;">Get-Help EntityFramework doesn't work! you may need to update help still doesn't work </span>

```sh
Update-Package EntityFramework
// (updates from 5.0.0 to 6.1.0 as of today)
Enable-Migrations -StartupProjectName CodeCamper.web -ProjectName CodeCamper.Data -EnableAutomaticMigrations
// No Entity Framework provider found for the ADO.NET provider with invariant name 'System.Data.SqlServerCe.4.0′ Looks like I need EF for CE first
```

## Publish It

In solution explorer, right click "CodeCamper.web", click Publish...

In VS2013, there is an option "Windows Azure Web Sites". Choose it, and log in to your Azure account

Create a "New..." website Add a unique site name, choose your locale, and create a new Database server, filling in name and credential fields

Go through each page of the wizard NOTE to self: "Execute code first migrations" is disabled. Because we haven't run it, the published app will have no data under the Settings Tab, you will see 2 entries for database. I have no idea why, but it caused me problems. For the second one ("DefaultConnection"), uncheck "Use this connection string at runtime" When finished in the wizard, you'll be taken to a working web site.

gha_language: SCSS


text:
# 1.1.1 / 18-11-2018
- Force latest dependencies
- Update module jsdoc
- Add example queue worker

# 1.1.0 / 09-10-2018
- Add persistent partie and roles seed
- Add env variables on example
- Add SMTP_FROM to fix travis crash
- Allow queue email send
- Add email notification integration spec
- Add runInBackround plugin to party schema
- Add POST /notifications route
- Add helpers to get party distinct phone numbers
- Add helpers to get party distinct emails
- Add postman dependencies
- Add party upsert logic
- Add party seed logic
- Add party upsert integration spec
- ADD party seed integration spec

# 1.0.2 / 26-10-2018
- Force responsibilities to undefined if not given
- Force latest dependencies

# 1.0.1 / 26-10-2018
- Update API Doc to include Role and Permission
- Update usage doc
- Improve test coverage

# 1.0.0 / 26-10-2018
- Clone @lykmapipo/party
- Refactor package details for emis-stakeholder
- Fix integration specs
- Improve package keywords
- Build API Doc

repository: Mloweedgar/emis-stakeholder

repo_name: Mloweedgar/emis-stakeholder


text:
- consider ways to improve true color -> 256 color degradation (avoiding grays). CIE-LAB space?

- support UTF-8-capable telnet clients

- add object quantity and associated manipulation commands

- add ability to differentiate between objects with similar keywords (?)

- add object stats (by script? store in db?)

- add combat

- add reputation

- add hp to prompt

- add customizable prompts

- add script state to state machine

- think about how to make parameterizable scripts for common use cases - or do it in rust

- add a resolve step for events to resolve targets so scripts have access to target information (get, drop, look at as examples)

- consider cleaning up timers at the end of a tick

- finish building the dog

- add player kick, ban, unban

- support ssh (thrussh)

- support graceful shutdown handling via signals

- add persist feedback for immortal commands (?)

- add support for metrics (statsd -> telegraf -> influxdb -> grafana)

- add currency

- check places with player names, make sure they allow spaces in their parsing (unlike player <name> info)

- make get player aware - you can't pick up player x.

- say what? and get what? are prompts, avoid prompts that indicate an interface where there isn't one (new player)

- add sidebars - help/commands list, inventory

- consider look just working on objects - overload look <direction> w/ look <keyword> [<keyword>..]

- add aliases (these would be applied before command lookup)

Things that would benefit from a state machine:

- Any other place non-linear stateful input sequence is required (combat, minigames, hacking, etc...)

repository: krixi/remud

branch_name: refs/heads/main

gha_language: Rust

repo_name: krixi/remud


text:
## My Own Laravel Boilerplate

### 1. Composer Install
```
composer install
```
### 2. Database Setup

```
php artisan migrate
```

### 3. Passport Setup
```
php artisan passport:client --personal
```

### 4. NPM Setup

- install dependencies

```
npm install
```

- development
```
npm run watch-poll
```

- production
```
npm run production
```

### Features

- Basic laravel authentication
- Dashboard CRUD operation

repository: Ngoni-Sama/laravel

repo_name: Ngoni-Sama/laravel


text:
# data analysis for hero.coli

This repository contains a set of notebooks used to produce analysis to help optimize [hero.coli](http://herocoli.com/) and get new data about learning through science games. We are using row logs of activity coming from the [red metrics](https://redmetrics.io/) platform.

The main purpose is to provide a primer to perform data science with open software tools commonly used in the scientific field:

- [ipyton notebooks/jupyter](http://jupyter.org/): a important piece of open science allowing to combine literate programming with computing science data.
  - [pandas](http://pandas.pydata.org/): data manipulation and selection
  - [matplotlib](http://matplotlib.org/): 2D plotting library
  - [scikit-learn](http://scikit-learn.org/): machine learning implementation of common algorithms

## hero.coli

[Hero.coli](http://herocoli.com/) is an exploration game about synthetic biology. It uses the main concept of this scientific science and incentive players to craft/assemble biobricks to reach new steps in the main level.

![hero.coli alpha version screenshot](http://herocoli.com/img/erocoli-screen01.jpg)

The current lead contributor of this project is the Raphael Goujet ([CRI](http://cri-paris.org)).

## datasets

- [players statistics (csv)](https://github.com/CyberCRI/dataanalysis-herocoli-redmetrics/blob/master/data/players_stats.csv): 156 games ([notebook](data/0.1. compile basic data about players~games.ipynb))
- [coordinates of events (csv)](https://github.com/CyberCRI/dataanalysis-herocoli-redmetrics/blob/master/data/players_coordinates.csv): 2010 events ([notebook](data/0.2. compile paths.ipynb))

## analysis

### hot spots of the main level

![hotspot map](https://github.com/CyberCRI/dataanalysis-herocoli-redmetrics/raw/master/images/map.hotspots.png)

If you are curious about it, you can check the notebook where we [are generating the maps](2. paths.ipynb).

### player profiling

We also perform a series of regressions to get an idea about player profiles but there is not enough data yet to reach conclusive statements.

We could for example [try to predict if a player is going to complete the game or not](1.1.%20predicting%20if%20a%20player%20is%20going%20to%20complete%20the%20game%20or%20not.ipynb).

You can check [the notebook](1. basic player statistics.ipynb) if you are looking for examples about how to use pandas to manipulate data in coordination with machine learning implentation (via scikit-learn)

## fun facts

- no player than played with the sandbox have completed the game.

## diagnostics

- attention span: players who are completing the game tend to play around ~800 seconds. There is a drop after 15 minutes of play.
- need more data to get significant results.


text:
[![Build Status](https://travis-ci.com/pulumi/pulumi-cloud.svg?token=eHg7Zp5zdDDJfTjY8ejq&branch=master)](https://travis-ci.com/pulumi/pulumi-cloud)

# Pulumi Cloud Framework (Preview)

Pulumi Cloud Framework is our multi-cloud framework for building modern container and serverless cloud applications.

This is a preview library demonstrating how to build Pulumi [components](https://www.pulumi.com/docs/reference/component-tutorial/)
that can abstract over and target multiple clouds.

For developers targeting a single cloud platform like AWS, Azure or GCP, we recommend using the
[@pulumi/aws](https://github.com/pulumi/pulumi-aws),
[@pulumi/azure](https://github.com/pulumi/pulumi-azure) and
[@pulumi/gcp](https://github.com/pulumi/pulumi-gcp) packages respectively. These packages give
you full access to the breadth of the platform's capabilities and come with many abstractions to
make developing against that platform easier.

## Installing

This package is available for Node.js (JavaScript or TypeScript).

To install the core API package, use either `npm`:

    $ npm install @pulumi/cloud

or `yarn`:

    $ yarn add @pulumi/cloud

Note that there are implementation packages for each major cloud provider that you will need also.

For AWS, install the package using either `npm`:

    $ npm install @pulumi/cloud-aws

or `yarn`:

    $ yarn add @pulumi/cloud-aws

> **Note:** At the moment, only Amazon Web Services (AWS) support is fleshed out enough to be used.
> Azure support is currently being worked on and is in an early preview state.  It can be used, but issues may be encountered.  To use Azure change the above lines to:

    $ npm install @pulumi/cloud-azure
    $ yarn add @pulumi/cloud-azure

> We also intend to support GCP in the future.  https://github.com/pulumi/pulumi-cloud/issues/518 tracks this request.

## Concepts

The Pulumi Cloud Framework is in preview.  It provides abstractions that can allow one to write a
cloud-application on many different cloud providers (i.e. Amazon Web Services (AWS), Azure, Google
Cloud Platform (GCP)), using a common API.

There is an abstraction package, `@pulumi/cloud`, that defines the APIs common to all cloud
providers.  This provides a highly productive view on modern cloud architectures, akin to Java or
.NET's approach to operating systems.  Because these abstractions allow one to operate over
different cloud platforms in a consistent manner, low level functionality and capabilities of the
individual platforms are intentionally not exposed.

There are implementation packages for individual cloud providers, such as `@pulumi/cloud-aws`, which
first and foremost implement those APIs for the target cloud in question, but also offer more
specific functionality in the form of derived classes that provide cloud-specific functionality.
This allows you to mix multi-cloud code with cloud-specific logic.

Note that you are free, of course, to intersperse these abstractions with specific resources in your
cloud platform of choice, using the appropriate Pulumi platform framework.  This delivers the
highest fidelity possible. For example, [pulumi/pulumi-aws](http://github.com/pulumi/pulumi-aws) or
[pulumi/pulumi-azure](http://github.com/pulumi/pulumi-azure).  These frameworks will give access to
the full power of those platforms, but will in turn create applications specific to them.

### Packages

Currently, Pulumi Cloud contains two primary packages: `api` and `aws`.

[`@pulumi/cloud`](https://github.com/pulumi/pulumi-cloud/tree/master/api) defines the cloud
abstractions common to building modern cloud applications, and can be used by any Pulumi application
directly for cloud-neutral logic.  For example, the `Service` type expresses a load balanced
container, `API` exposes simple serverless functions over HTTP, and `timer` allows you to schedule
timers.  All serverless functions are expressed using lambdas in your language of choice.  The
package also offers simple data abstractions, systems like `Table` and `Bucket`.

[`@pulumi/cloud-aws`](https://github.com/pulumi/pulumi-cloud/tree/master/aws) supplies an implementation
of those abstractions, built on top of the `@pulumi/aws` library.  Its implementation types offer
more AWS-specific functionality than is available in the `@pulumi/cloud` package.

To use either, simply reference them in the usual NPM style in your program.  You may decide to code
against either the APIs or the implementation types, depending on the style of code you're writing
and functionality you need.

If you code against `@pulumi/cloud` directly, you will need to configure your program before running
`pulumi update`. This can be done simply by running the `pulumi config set` command; for instance,
to select `aws`, you will run:

    $ pulumi config set cloud:provider aws

For more details see the examples in `examples`, or online at: https://docs.pulumi.com/quickstart/

## Reference

For detailed reference documentation, please visit the API docs site for this package:

* [@pulumi/cloud](https://pulumi.com/docs/reference/pkg/nodejs/pulumi/cloud/)

repository: pulumi/pulumi-cloud

gha_language: TypeScript

repo_name: pulumi/pulumi-cloud


text:
# One Bit VAE

A simple demonstration of the bits-back encoding mechanism by considering an
extreme example where the data consists of only two distinct samples. The true
entropy of the dataset is thus ~0.693 nats.

By varying the number of dimensions in the sample *while* keeping the
dimension-independence of the decoder, we can easily demonstrate that Z strongly
resists encoding X when the number of dimensions is small. This is because the
smaller the number of dimensions, the less important it is for Z to encode
global information about X. When `ndims=1`, it is possible to explain the data
with the decoder alone, and Z is never used. Failure to encode in Z is reflected
in the poor reconstruction cost for `ndims=1`, despite also having the lowest
loss (decoder is capable of explaining the data all by itself).

![](./images/rec_and_loss.png)

As `ndims` increase, there is increasing pressure to encode into Z in order to
coordinate the independent dimensions of the decoder. The VAE must now perform
reconstruction near-perfectly while simultaneously minimizing the KL divergence
between its encoding distribution and the unit Gaussian prior. The 2-layer VAE
is more successful at doing so by expanding the variational family of the top
layer, which enables its encoding distribution to better match the unit Gaussian
prior.

![](./images/encoding_over_time.png)

Looking at the case of `ndims=1000`, we see very clearly the importance of
expanding the variational family. The simplest generative process is:

1. When z < 0, generate x = 1
2. When z >= 0, generate x = 0 (or vice versa)

This means the optimal posterior p(z|x) is a truncated Gaussian. If we are limited to the Gaussian family for q(z|x), we can never meaningfully minimize the KL(q(z|x) || p(z|x)).

![](./images/vae1_dim=1000.png)

A 2-layer VAE has a Gaussian q(z2|z1). However, q(z2|x) is potentially arbitrarily complex, enabling better approximation of the truncated Gaussian.
![](./images/vae2_dim=1000.png)

repository: RuiShu/one-bit-vae

repo_name: RuiShu/one-bit-vae


text:
# Jupyter Notebooks for Rust

(C) 2021 by [Damir Cavar]

To enjoy the notebooks in this folder, you might want to read the main README and make sure that you have [Jupyter], [Rust], and a [Rust kernel for Jupyter] set up.

[Damir Cavar]: http://damir.cavar.me/ "Damir Cavar"
[Rust kernel for Jupyter]: https://github.com/google/evcxr "Evcxr"
[Rust]: https://www.rust-lang.org/ "Rust Programming Language"
[Jupyter]: https://jupyter.org/ "Jupyter"

repository: dcavar/rust-tutorial-notebooks

repo_name: dcavar/rust-tutorial-notebooks


text:
# Dashboard app

This folder contains the dashboard application, which should run at `app.dodatado.com`

### Notes
- Overriden the function in `api/responses/notFound.js` to serve the `views/homepage.ejs` file instead of the standard `views/404.ejs` file (404 page should instead be rendered by the angular app)

repository: JonathanJao/userjoy

repo_name: JonathanJao/userjoy


text:
# Universal Migration  Console

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119).

## 1. Overview
This Universal migration console is aimed to allow using custom migration script,
running eloquent migrations outside artisan, laravel and lumen. It will also allow using
doctrine migrations  and many other migrations scripts as separate packaged application layer
information.

## 2. Specification

## 3. Examples
For a working example please check sample folder

repository: Ice-Productionz/Universal-Migration

repo_name: Ice-Productionz/Universal-Migration


text:
# logtailer

## Summary

A simple log tailer written in go. Originally written by Parse to consume production log data of various formats and feed it into Facebook's analytics systems for day-to-day operations. logtailer uses a modular approach to consuming logs and directing output. To support new log types or change existing behavior, simply implement the Profile interface to suit your needs. The reference implementations in this release consume logs directly and output parsed lines as stdout.

Reference implementations include:

* a dummy profile used for demonstration. Consumes the input log file and prints to stdout
* a mongodb log parser based on a Programmable Expression Grammar (PEG). At Parse we found the PEG parser to perform better, and more accurately, than any regex-based pattern we could come up with, due to the complex nature of MongoDB log lines. The PEG parser focuses on actual operations (queries, inserts, commands, etc) and ignores other noise. At Parse, we processed 4B operations/day with this tailer. The mongodb tailer converts lines into a consistent JSON format that can be processed by other analytics systems.
* an sshd log parser that converts ssh login events to JSON

## Building

Has been tested on go version 1.5.3, but will probably work with earlier versions.

```sh
$ go install github.com/ParsePlatform/logtailer/cmd/logtailer
```

## External Dependencies

Logtailer was written to run cron once per minute. Since logs rotate less frequently than that, it relies on the [logtail2](http://manpages.ubuntu.com/manpages/trusty/man8/logtail2.8.html) command readily available in the Ubuntu repositories. When repeatedly run with the same log file for input, logtail2 ensures that only new lines are consumed. To make this work, ensure that the logtailer run directory exists:

```sh
mkdir -p /var/run/logtailer
chown <your tailer user> /var/run/logtailer
```

Alternatively, logtailer accepts stdin as input. Simply specify *-* to the *log_file* flag when invoking logtailer.

## Testing

The simplest test of the binary is to invoke the *dummy* profile with some simple input. It should be echoed back, along with some statistics that go to stderr.

```sh
echo -n '1\n2\n3\n' | ./logtailer dummy -log_file -
1
2
3
{"Records":3,"ParseErrors":0,"SendErrors":0}
```
## Tuning

By default, the *logtailer* creates a worker for each CPU on the system. You can override this by setting the *num_workers* flag.

repository: wobondar/logtailer

repo_name: wobondar/logtailer


text:
# RusticiSoftwareCloudV2::SettingMetadata

## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**default** | **String** | Default value of this setting | [optional]
**data_type** | **String** | The data type of this setting | [optional]
**setting_description** | **String** | description of this setting | [optional]
**level** | **String** | The level this setting will be applied at, which limits where it can be set. For example, WebPathToContentRoot is applied at the application level, so it's not valid to set it for a registration. | [optional]
**learning_standards** | **Array<String>** | The list of learning standards this setting applies to. If not present, this setting is not limited to certain learning standards. | [optional]
**learning_standard_variant** | **String** | Does this setting apply to only single-SCO packages, only multi-SCO, or either? | [optional] [default to 'either']
**fallback** | **String** | A setting that will be used instead of this setting if no value is provided for this setting (This is similar to a default, except that the the value of another setting is being used instead of a fixed default value). | [optional]
**valid_values** | [**Array<SettingValidValue>**](SettingValidValue.md) | For settings with a fixed list of valid values, the list of those values | [optional]


text:
---
layout: default
title: Multiple Databases
---

# Multiple Databases

## Problem
You want to access multiple databases in a single project.

## Solution

webpy 0.3 supports multiple databases by removing the database from a part of the "web" module, and making it a more typical object.  For example:

    import web

    db1 = web.database(dbn='mysql', db='dbname1', user='foo')
    db2 = web.database(dbn='mysql', db='dbname2', user='foo')

    print db1.select('foo', where='id=1')
    print db2.select('bar', where='id=5')

insert, update, delete and query methods can also be used in the similar way.

Of course, you can use 'host' and 'port' to specify server address and listen port.

To close a db connection explicitly:

    db1.ctx.db.close()

gha_language: Python


text:
---
layout: default
title: Cult Application
parent: Cult
grand_parent: Training
nav_order: 1
---

# ❋ Chaos Indivisvm Application v9.15❋
{: .no_toc }

Please read the ENTIRE application. There are important requirements and expectations to read. Also there are questions placed throughout, not just in certain sections. So make sure you read EVERYTHING.

Chaos Indivism is located at **Milopolis**

## Table of contents
{: .no_toc .text-delta }

1. TOC
{:toc}

# Requirements

- Make sure you read this application in its entirety.
So to recap:
Q: how much of this application do you have to read? A:

- We DO NOT accept bronies or furries. As of October 16th, 2019, however, we have changed our policy on accepting ex-furries. Please see below for details and a questionnaire

- An avatar age of at least 30 Days, and an RL age of at least 18 years old.

- Recruit must be fluent in the English language and be able to speak and type WITHOUT translators!

- Thick skin and a resilience to trolling/a good sense of humor is a huge plus. We are not nice. especially not to cultists.

- If accepted, you must leave all other SLMC groups, Veteran groups, however, are allowed. i.e.: Any equivalent to our Militia or a defender group is OK.

- We use Mumble to communicate during raids. You are expected to have a microphone of some sort and participate in comms during raids. You MUST have a microphone AND USE IT while in cult phase or you will not be accepted into the main group. Unrelated: The answer to the bonus question below is YELLOW!

- Knowledge of script time & rendering cost, & the willingness to adjust your avatar to lower your script number & time to promote sim health.

 Speaking of which answer this question quick:
Q: Blood for the.. A:

- If accepted, you will go through Cult Training FIRST before being accepted into the main group. It will be YOUR responsibility to seek out trainers, and get your training done. It is also required that you are active, and participate with the group during raids, meetings, or general shenanigans. If you are unable or unwilling to meet our activity requirements you will be ejected.

# The Application

Your avatar name (NOT display name!):

How much time do you think you'd be able to devote to the group per week? (how much activity can we expect from you?):

Why join Chaos Indivisvm?:

How did you hear about Chaos Indivism?

Do you have a microphone and are you willing and able to use it? (as mentioned above, you are expected to have one AND use it) :

We require a certain level of activity. Do you have any RL restrictions currently, or upcoming, that would keep you from being active in the group? if so, explain.

## A Little History About You

Please list previous militaries you have served in within SL. If you haven't been in one, you can simply put N/A. When you list why you left the group, please be brief, but mention all the important shit. copy and paste as needed.

+ Group:
+ Rank:
+ Time with Group:
+ Reason for Leaving:

## FURRY QUESTIONNAIRE

As of October 16th, 2019, we have changed our policy on accepting EX-FURRIES (not those who are STILL furries) into our group. Please answer the questions below honestly and be as detailed as possible. You will go through a rigorous background check, will have an interview with Zalera, or another member of command/Enforcer staff, and you MAY have to go through a trial period in our Militia group anywhere between 30-90 days BEFORE your application is accepted and you're allowed to begin your cult training.

If you are approved, and at any later time additional-past or new furry-involvement proof is discovered, you MAY still be ejected or have your application denied depending on the severity of the new information so it is VERY important to be honest and not leave anything out here.

Know that any and all decisions regarding approval of new applicants with past furry-involvement will be made by command and/or enforcer staff ONLY.
No exceptions.

1. Are a furry currently:
    YES/NO

2. Have you EVER been a furry in any regard in the past?
    YES/NO

3. If answered yes to question 2: How long ago did the furry-related faggotry occur and for how long did it go on?
    EXPLAIN:

4.  And what made you finally see reason to leave the life of pedophilia and animal raping behind you? (please be very detailed here!)
    EXPLAIN:

5. Anything else we should know?
    EXPLAIN:

6. List anyone in the SLMC that can verify or confirm the accuracy of your statements or vouch for you personally:
    LIST SNITCHES HERE:

# Intelligence Test

Q: Saera is driving down the road. On said road, there are eight other cars.  Saera is Chinese. How many of the cars does she hit?

A:

Q: When and where is a good time and place to yiff?

A:

Q: Name two functions within the SL build menu that CUTS or REMOVES portions of a prim from said prim.

A:

Q: How many hours per day do you spend clopping?

A:

Q: Which has more pellets? A 10 gauge shotgun or a 12 gauge shotgun.

A:

Q: What is the difference between a clip and a magazine?

A:

Q: Does mesh cause lag in SL?

A:

Q: Bonus question! What's your favorite color?

 Once you've read everything and marked them all off continue onto the final part of the application at the bottom of the notecard.

I hereby understand & agree to abide by all of the rules
within Chaos Indivism & its operational boundaries.

X_

I hereby understand that Chaos Indivisvm is a group
based upon a certain theme, and that I may be
instructed to adjust my avatar to be more in
accordance with this theme. I also understand
that Chaos Indivisvm is a human orientated group,
and furries and bronies are STRICTLY prohibited.

X_

I hereby agree to forgo all use of unfair client-side
assistance whilst enlisted in Chaos Indivisvm, & I
understand that the use of such may result in my
immediate ejection from Chaos Indivisvm.

X_

I hereby understand & agree to meet all the
requirements listed within this notecard, the Enlisted
Handbook, & the Chaos Indivisvm manifest.

X_

I hereby understand that judgment will be held against
me by various groups for joining Chaos, & that I may be
treated unfairly by biased administration staff in other sims.

X_

I hereby understand that Chaos Indivisvm is not a
conventional military group, and that it strives to
overcome the barriers of bias & political drama that
pollutes other groups & their ilk. I agree to leave
all drama & grudges at the door.

X_

I hereby understand that Chaos reserves the right to turn
down an avatar due to past actions & the company that
they keep. I also acknowledge that upon enlistment, I will
start as an E-1, and that nobody will be handed a rank,
bypass mandatory training, treated unfairly, or
given special treatment within these ranks.

 X_

I hereby agree to follow all the terms and conditions
put forth within this notecard, & accept that violations
of said standards may result in immediate ejection.

 X_

I Hereby agree to undergo an extensive background
check upon application to Chaos Indivisvm. and
understand that any evidence of being a "furry" or
a "brony" will result in immediate denial of my application.
And any evidence that may be found at a later time will
also result in immediate ejection from the group.

 X_

I Hereby understand that Chaos requires a certain level
of activity. I also understand that if I fail to meet these
requirements, i may be ejected from the group, or my
cult training may be canceled. I also understand that if i
am ejected for this reason, I may be put on a waiting
period before I am able to apply to the group again.

X_

# YOU'RE DONE, BITCH!

** Make sure the ENTIRE application is filled out before you
send it off to me! I may reject it/return it for a do-over
depending on what you missed and/or how much you missed.

Please make sure you have saved, and renamed your application then...

DELIVER APPLICATION TO):

+ Zalera Atheria
- Head Corruptor/Head of Recruiting and Training

PLEASE give me AT LEAST 24 hours to respond to you! I have
a life and am not online 24/7 but i WILL respond to you within the day.

SUBMIT IT NOW!

STOP WAITING!

THE END!

Recruitment Application v.9.2
Update 7/23/2020 by Hadet, converted to the Docs website.
Update 7/15/2019 by Zalera, added details about activity requirements
Update 9/17/2019 by Zalera and Sam to v9.0.
Update 10/16/2019, added section for furry-related questions, also took out the part at the top saying we do not accept any furries/no tolerance.

repository: Krutchen/chaos-docs

repo_name: Krutchen/chaos-docs


text:
# module name

## Module development setup

Install all the require gems to run test code
```shell
bundle install  (only need to do once)

```
## Running Tests

### Unit tests
This type of testing is fast and should be the first thing you do before committing your code.  Mistakes can be found
in a matter of seconds vs minutes/hours.  You can test your logic in a unit test.  The downside is you need to learn
how to write unit tests which can take some initial time getting used to.

```shell
bundle exec rake spec

```

### Integration Testing
This type of testing is somewhat manual and requires the use of vagrant and a test vm that is controlled by vagrant.
You can find the list of available test vms by running `vagrant status` in the root of the module directory.  There is
at lot of magic happening in the vagrantfile that makes this easy.  Windows support with this module has not been added yet.

```shell

$ vagrant status
Current machine states:

win2012r2                 not created (vmware_fusion)
win2008r2                 not created (vmware_fusion)
centos6                   running (vmware_fusion)
```

To run a test first you need to define the test code located in module_root/tests directory.    You will be using puppet apply to run this code on the vm.
Have a look inside the tests directory for examples.

Example test file
```
include profiles::default_linux
file{'/tmp/test.txt':
    ensure => file,
    content => 'Hello World'
}
```

There are a few ways to run the test code against a test vm, both of which have the same outcome.

```shell
bundle exec rake spec_prep
VAGRANT_MANIFEST=linux.pp vagrant provision centos6
```

or use the rake command which bundles the two commands together

```shell
bundle exec rake "vagrant_up[linux.pp,centos6]"
```

### Acceptance Tests
Acceptance testing is sorta like combining unit testing and integration testing where it tests the code on real systems
automatically across a wide range of operating systems.  This is an advanced topic, so you will want to master unit and
integration testing first before writing acceptance tests.

```shell
bundle exec rake beaker

```

## CI config doc
https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md

gha_language: Ruby


text:
# Nova Video Player changelog

## Important notes:
- migrating from v3 or v4 to v2 will delete all your scraping information

## v4.x current git (unstable)
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r20, ffmpeg 4.2.

## v3.x current git (testing)
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r20, ffmpeg 4.2.

## v2.x current git (stable)
Stable branch: this release is based on minSDK 17, targetSDK 27, NDK-r16b, ffmpeg 3.3.x.

## v4.7 unstable branch release - 15/6/2019
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r20, ffmpeg 4.2.
- Improve audio passthrough robustness
- Fix authentication issue with Trakt

## v3.11 Google Play beta release - 15/6/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r20, ffmpeg 4.2.
- Improve audio passthrough robustness

## v3.10 Google Play release - 9/6/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19c, ffmpeg 4.2.
- Fix authentication issue with Trakt

## v4.6 unstable branch release - 3/6/2019
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r19c, ffmpeg 4.2.
- Attempt to fix UPnP playback of files containing a "/"
- Do not crash when opening non-video files in browser
- Stability improvements

## v3.9 Google Play beta release - 1/6/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19c, ffmpeg 4.2.
- Attempt to fix UPnP playback of files containing a "/"
- Do not crash when opening non-video files in browser
- Stability improvements

## v4.5 unstable branch release - 30/5/2019
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r19c, ffmpeg 4.2.
- Fix files cannot play from external sdcard using an external player
- AndroidTV: fix EpisodesByDate week view crash in case of large TV show collection

## v3.8 Google Play release - 30/5/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19c, ffmpeg 4.2.
- Fix files cannot play from external sdcard using an external player

## v4.3 unstable branch release - 19/5/2019
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r19c, ffmpeg 4.2.
- Scanning and scraping proper Notifications
- Add an option to force disabling stereo downmix on phones/tablets with Android version > N
- AndroidTV: add pinning on long press for all movies/tvshows
- New TV show categories for quicker browsing through large collection
- Countless TV UI improvements (roles, trailers, badges, global del/deindex, subs picker)
- New player shortcuts (A/S switch audio/sub track, U/D = volume up/down) and menu support
- Improve audio passthrough stability
- Fix sftp playback interruptions
- Make private mode persistent
- Fix cloud support (still no streaming)- AndroidTV: add poster/backdrop zoom on long press
- AndroidTV: add tvshow episodes by date view
- Fix sftp playback interruptions
- Fix an android Q DP3 crash

## v2.2 stable branch release - 19/5/2019
Stable branch: this release is based on minSDK 17, targetSDK 27, NDK-r16b, ffmpeg 3.3.x.
- New TV show categories for quicker browsing through large collection
- Countless TV UI improvements (roles, trailers, badges, global del/deindex, subs picker)
- New player shortcuts (A/S switch audio/sub track, U/D = volume up/down) and menu support
- Improve audio passthrough stability
- Fix sftp playback interruptions
- Make private mode persistent
- Fix cloud support (still no streaming)
- Fix an android Q DP3 crash

## v3.7 Google Play release - 24/5/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19c, ffmpeg 4.2.
- Fix software decoding fallback in case of error
- Re-enable downmix on phones to avoid voice channels loss on some phones
- Stability improvements
- Upgrade to latest ffmpeg and dav1d soft codecs
- Fix an android Q DP3 crash

## v4.2 API28+AndroidX beta release - 27/4/2019
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r19c, ffmpeg 4.2.
- Option to have landscape fullscreen video on display with cutouts
- AndroidX migration
- Poster/backdrop zoom on AndroidTV via long press
- Improve stability of phone/tablet UI after API28 migration
- New A-Z orb option in All TV shows/Movies for alphabetical order browsing
- New all/not viewed orb option in All TV shows/Movies for limiting browsing to all/not viewed videos

## v3.6 Google Play beta release - 27/4/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19, ffmpeg 4.2.
- Upgrade to latest ffmpeg and dav1d soft codecs

## v3.5 release candidate - 17/4/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19, ffmpeg 4.2.
- Fix software decoding on pre-M Android versions

## v4.1 API28 beta release - 8/4/2019
Unstable branch: this release is based on minSDK 21, targetSDK 28, AndroidX libraries, NDK-r19, ffmpeg 4.2.
- New video overview
- Leanback style settings on AndroidTV
- Add recently added TV channels
- Improved subtitles picker wizard look
- API28 migration

## v3.3.1 Google Play beta release - 11/3/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19, ffmpeg 4.2.
- New TV show categories on TV interface for quicker browsing through large collection
- Countless TV UI improvements (player look and feel, roles, movies trailers, audio badges, global deleletion/de-indexation, subtitles picker, more dynamic banners)
- New player shortcuts (A/S switch audio/sub track, U/D = volume up/down) and menu support
- Improve audio passthrough stability
- Fix crash in presence of damaged sdcard
- Fix cloud support (still no streaming)
- Do not downmix to stereo on phones/tablets if Android is recent enough (N): delegate to Android

## v3.4 special SMBv2/3 test release (experimental) - 18/3/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19, ffmpeg 4.2.
- SMBv2/3 support via jcifs-ng
- Ability to deindex local folders

## v3.1 Google Play beta release 3/2/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19, ffmpeg 4.2.
- New TV show categories on TV interface for quicker browsing through large collection

## v3.0 Google Play beta release - 30/1/2019
Testing branch: this release is based on minSDK 21, targetSDK 27, NDK-r19, ffmpeg 4.2.
- Migration from Android ndk-r17 to ndk-r19
- Add AV1 soft decoding capability through 4.2-dev ffmpeg version and dav1d codec
- Add support for x86_64 architecture
- Improve audio passthrough stability
- Make private mode persistent between application relaunches

## v2.1 Google Play public release - 20/9/2018
Stable branch: this release is based on minSDK 17, targetSDK 27, NDK-r16b, ffmpeg 3.3.x.
- Improved french translations and interfacing with crowdin service
- Stability improvements

## v2.0 Google Play public release - 7/9/2018
Stable branch: this release is based on minSDK 17, targetSDK 27, NDK-r16b, ffmpeg 3.3.x.
- Scraper improvements and bug fixes
- Issue a warning toast is hardware decoding is disabled

## v1.0 Initial Google Play public release - 26/8/2018
Compared to Archos Video Player open source release, following changes were made:
- Add support for Android P avoiding application crash at startup
- Add a "list episodes" button on tvshow episode view to quickly get to tvshow view on AndroidTV leanback version
- Add notification channels for Oreo
- Fix subtitle delay not applied on play resume when negative
- Fix floating player crash on Android version Oreo and above
- Fix loss of activity background and private mode background
- Prevent from playing a file when detecting a problem: issue a toast instead

gha_language: HTML


text:
helper to convert f-strings before sending code to micropython or to the bytecode compiler mpy-cross

usage:  python3.7 -mfstrings_helper filename

note: requires the tokenize_rt module from https://github.com/asottile/tokenize-rt

many thanks to original author since micropython is unlikely to support natively f-strings as it would increase its core size.

NEW! future-fstrings[rewrite] now provides a command line tool for code conversion
    check it there https://github.com/asottile/future-fstrings#transform-source-for-micropython

watch for:
    https://docs.python.org/3.8/whatsnew/3.8.html#f-strings-now-support-for-quick-and-easy-debugging
    and maybe it's future support https://github.com/asottile/future-fstrings/issues/40


text:
---
title: "Later"
subtitle:
date: 1979-11-01T06:00:00.000Z
series:
genre: "poetry"
subgenre:
language:
authors:
  - author/robert-creeley.md
translators:

editors:

contributors:

editions:
  - binding: paperback
    isbn:<PHONE_NUMBER>362
    date: 1979-11-01T06:00:00.000Z
    description: ""
    trim_size: ""
    page_count: ""
    sales_data:
      forsale: false
      saleprice:
      shipping_weight:
      price_us:
      price_cn:
    contributors:
    cover_image: "/Later.jpg"
featured_image:
  file:
draft: false
_slug: later
---

The epigraph to _Later_, Robert Creeley’s second book of poems published by New Directions, enjoins the reader to "hold in mind/ All that has loved you or been kind." This commitment to the continuity of life on a fragile planet, limited by both time and space, has become increasingly important to a poet who, "if older," takes a certain pride in knowing the boundaries of the possible. Where his 1978 verse journal Hello chronicled an actual journey (to New Zealand, Australia, and the Far East), _Later_ deals with an interior exploration rooted in everyday sights and sounds––the play of light and shadow through a window, the lap of waves on a beach. Past occurrences and expectations are reconciled with an acceptance of inevitable change, and in the poignant title sequence Creeley marvels, "but now the wonder of life is/ that it is at all."

repository: theNewDynamic/hugo-controllers-panic

repo_name: theNewDynamic/hugo-controllers-panic


text:
This demo application uses C++ SDK for The Eye Tribe Tracker
====
The complete content of this README file is taken from  The Eye Tribe Tracker README file.
Eye Tribe C++ SDK: https://github.com/EyeTribe/tet-cpp-client

Introduction
----

This is the C++ reference implementation for The Eye Tribe Tracker and provides a C++ interface for communicating with the server, without resorting to socket programming and JSON-parsing.

This version is to be considered _alpha_. Feedback and bug fix submissions are welcome.

Please visit http://dev.theeyetribe.com for more information.

Compilation
----

The C++SDK comes with CMake-support making it easy to build the SDK as a library for inclusion in your own project. Alternatively you may copy the files directly into your own project.

The CMake GUI can be obtained at http://www.cmake.org.

Dependencies
----

In order to provide non-C++11 portability and network support, the C++ SDK utilizes a variety of Boost libraries. The lowest boost version version tested is 1.53, but older versions may work. For information on obtaining and installing a recent version of Boost, please visit http://www.boost.org.

Boost is meant to be built from source and does include instructions on how to accomplish this. However, prebuilt binaries can be downloaded as well. CMake may encounter issues with prebuilt versions of Boost, and thus we advise users to build Boost manually.

Build
----

1. Install boost
2. Use CMake GUI to generate project files
3. Build the C++ SDK library with your preferred compiler

Note: In step 2) CMake will try to find Boost during configure. If that fails do the following:
a. Turn on the Advanced flag
b. Set BOOST_INCLUDE_DIR to the path of the _root_ of Boost
c. Configure
d. If CMake fails to find the Boost libraries, then set BOOST_LIBRARYDIR to the path of where the prebuilt libraries  of Boost are located
e. Configure and this should succeed
f. Generate project files

Samples
----

There are currently no samples available for the C++ SDK, but they will be added as they become available.

API Reference
----

The complete API specification used by the C++ SDK to communicate with the server is available on http://dev.theeyetribe.com/api/

Changelog
----

0.9.33 (2014-04-24)
- Fixed missing calibration report targets
- Added missing get_screen API method

0.9.31 (2014-04-01)
- Fixed wrong Json-formatted set screen request string
- Fixed bug related to uninitialized "avg" member of GazeData
- Vital server calls made blocking, including get_frame() when running in pull-mode

0.9.27 (2014-02-11)
- Bug fix of status code
- Removed forward declarations and included interface and types headers instead in gazeapi.h
- Fixed hanging observers
- Cleans up when shutting down!
- Added push_mode to connect (similar to C# SDK)
- Fixed bug where no GazeData was ever sent to the client
- Added is_connected() connectivity info to the GazeApi

0.9.26 (2014-01-30)
- Initial release

WinBGIm Graphics Library
----

This example application uses *WinBGIm Graphics Library*, an implementation provided by Michael Main (main@colorado.edu).
For more details please visit - [Using the WinBGIm Graphics Library](http://www.cs.colorado.edu/~main/bgi/).


text:
A very very quickly and badly written converter between Doxygen and XML source code documentation.

In essence, transforming:
```c#
            /**
             * @brief Transform a floating-point vector by the properties passed to the class.
             * @param vVector The vector to transform.
             */
            public void transformVector(ref Vector3 vVector)
```
into:
```c#
            /// <summary>
            /// Transform a floating-point vector by the properties passed to the class.
            /// </summary>
            /// <param name="vVector">The vector to transform.</param>
            public void transformVector(ref Vector3 vVector)
```
I would like to add that this is far from my finest code and that it is only here because I could not see anything else like it out there.  Please use it and contribute changes back in the same spirit. :-)

repository: JohnHardy/doxygentoxmlconverter

repo_name: JohnHardy/doxygentoxmlconverter


text:
# generator-trabian-webapp

This is an application that "does what it says on the tin." Use it to generate an instance of trabian-webapp into the current directory. Generator-trabian-webapp uses [Yeoman](http://yeoman.io) to generate trabian-webapp, so just cloning this repo doesn't do much.

## Getting Started

First, if you haven't already, install yeoman from the [npm](https://npmjs.org) package repository.

```
$ npm install -g yo
```

Next, to install generator-trabian-webapp from npm, run:

```
$ npm install -g git://github.com/trabian/generator-trabian-webapp.git
```

Now, you can generate a new application. Because generator-trabian-webapp creates the app in the current directory, let's make a directory to create the application in, and then change to that directory:

```
$ mkdir a-new-trabian-webapp
$ cd a-new-trabian-webapp
```

Now, let's generate the webapp itself. It's as easy as:

```
$ yo trabian-webapp
```

By default, the generated name will be that of the current directory. If you would like to change this, you can specify a different name for the webapp instance on the command line with the `-n` flag when generating. For example:

```
$ yo trabian-webapp -n "Trabian CMS"
```

The specified name will be hyphenated as needed (e.g., "trabian-cms") wherever a name or ID is needed within the instance.

With that completed, you're ready to go.

## Verifying

Now that you've created an instance of trabian-webapp locally, you can read its README.md to configure it. But just to make sure everything was created correctly, try

```
$ grunt test
```

Of course, you must have [grunt](http://gruntjs.com)'s command line interface installed for that to work. If you don't, you'll have to run

```
$ npm install -g grunt-cli
```

## Having problems?
Let us know what's going wrong (including error messages generated) by [reporting an issue](https://github.com/trabian/generator-trabian-webapp/issues).

## License

[MIT License](http://en.wikipedia.org/wiki/MIT_License)

repository: trabian/generator-trabian-webapp

gha_language: CoffeeScript

repo_name: trabian/generator-trabian-webapp


text:
## About Team Dashboard

Specially designed for remote teams spread across multiple timezones. Dashboard allows user to see the local times of team members and whether they are currently available. Can also preview future times to make meeting scheduling easier.

Built with [Laravel Livewire](https://laravel-livewire.com/).

## Demo

View a demo dashboard [here](https://demo-team-dashboard.herokuapp.com/dev-team).

## Installation

Copy `.env.example` to `.env` and fill in your local configuration (`php artisan key:generate`, database, etc)

```bash
composer install
php artisan migrate --seed
```

gha_language: PHP


text:
---
title: Configure Contribution folder
seo-title: Configure Contribution folder
description: Get an insight into configuring a contribution folder in Brand Portal.
seo-description: Get an insight into configuring a contribution folder in Brand Portal.
uuid:
content-type: reference
contentOwner: Vishabh Gupta
topic-tags: brand-portal
products: SG_EXPERIENCEMANAGER/Brand_Portal
discoiquuid:
---

# Configure contribution folder {#configure-contribution-folder}

For collaborative asset sourcing, AEM users (administrators and non-admin users having permission) can create new folders of type **Asset Contribution**, ensuring the new folder created is open to asset submission by Brand Portal users.  This automatically triggers a workflow which creates two additional sub folders, called **SHARED** and **NEW**, within the newly created **Contribution** folder.

AEM user then defines the asset requirements by uploading a brief about the types of assets that should be added to the contribution folder, as well as a set of baseline assets, to the **SHARED** folder to ensure Brand Portal users have the information they need. The administrator can then grant active Brand Portal users access to the contribution folder before publishing the newly created Contribution folder to Brand Portal.

The following video demonstrates, how to configure a Contribution folder in AEM Assets:

>[!VIDEO](https://video.tv.adobe.com/v/30547)

AEM user performs the following activities while configuring a contribution folder:

* [Create contribution folder](brand-portal-create-contribution-folder.md)
* [Upload asset requirements](brand-portal-configure-contribution-folder-properties.md)
* [Assign contributors](brand-portal-configure-contribution-folder-properties.md)
* [Upload baseline assets](brand-portal-upload-baseline-assets.md)
* [Publish contribution folder to Brand Portal](brand-portal-publish-contribution-folder-to-brand-portal.md)


text:
# Database access
SQLAlchemy also support an object-relational mapping approach,
which is also illustrated by sample code.

## What is it?
1. `create_sqlalchemy_db.py`: implements two classes representing SQL
    tables, and creates them in an RDBMS using SQLAlchemy's
    object-relational mapping mechanisms
1. `fill_sqlalchemy_db.py`: adds data using SQLAlchemy's ORM mechanisms
1. `query_sqlalchemy_db.py`: queries the RDBMS using SQLAlchemy's ORM
    mechanisms
1. `update_sqlalchemy_db.py`: illustrates updating values using SQLAlchemy's
   ORM mechanisms

repository: binomaiheu/training-material

repo_name: binomaiheu/training-material


text:
# AboutYouShop-iOS-SDK

AboutYouShop-iOS-SDK is a library for [AboutYou](http://aboutyou.de) Shop integration in iOS. It is written in Objective-C and requires ARC and the iOS SDK 6.0 or above. The networking- and object mapping engine is build on top of [RestKit](https://github.com/RestKit/RestKit). It provides all necessary functions and convenience methods to make your app fully capable of the About You API.

## Getting Started

- [Register for an account](https://devcenter.mary-paul.de) at the AboutYou Devcenter and create a new app. You will be given credentials to utilize the About You API.
- We strongly recommend using [CocoaPods](http://cocoapods.org) to install the AboutYouShop-iOS-SDK in your iOS project.
- Run and discover the 'ShopExample' project to become familiar with the basic principles of the AboutYouShop-iOS-SDK.
- Need some help? Feel free to ask questions to marius.schmeding(at)slice-dice.de

## Overview

# SDShopManager

You obtain the *SDShopManager* singleton by:

	[SDShopManager sharedManager]

Get friends with it! It will handle several things for you:

- Networking
- Object Mapping
- Session Handling
- User Authentication (OAuth2)

# SDQuery

Object Retrieval and Modification is handled by *SDQuery*. To perform an API operation on an Object, simply call the query constructor, like

	SDQuery *query = [SDProduct queryForSearch];

and use the given methods to modify the query according to your needs

	[query addFields:@[@"variants"]]

Executing the query:

	[query  performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

		if (result){
			//everything you need is in the *SDResult*
		}
	}];

## Setting the App Credentials

	[[SDShopManager sharedManager] setAppId:@"<APP_ID>" andAppPassword:@"<APP_PW>"];

## Retrieving the Category Tree

	SDQuery *categoryQuery = [SDCategory query];
	[categoryQuery performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

		if (result.categoryTree){
        		//you got *SDCategory* objects to work with
        	}

	}];

## Retrieving and Caching Facets

Say, you want to retrieve all facets from the groups *Color* and *Brand*. The results should be cached.

	NSArray *facetGroups = @[
                             	 @(kSDFacetGroupColor),
                             	 @(kSDFacetGroupBrand)
                             	];

	SDQuery *facetQuery = [SDFacet query];
	[facetQuery addFacetGroupIds:facetGroups];
	[facetQuery performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

        	if (result.facets){
            		// you got *SDFacet* objects to work with

			// optionally cache facets for fast access
            		[SDFacet cacheFacets:result.facets];
        	}
	}];

Later, you can retrieve facets from cache, e.g. all that belong to the group *Color*.

	NSSet *cachedColorFacets = [SDFacet cachedFacetsForGroupId:kSDFacetGroupColor];

## Retrieving Products by IDs

Say, you want 3 products, including all variants.

	NSArray *productIds = @[
				@12345,
				@23456,
				@34567
				];

	NSArray *fields = @[@"variants"];

	SDQuery *productQuery = [SDProduct queryForGet];
	[productQuery addProductIds:productIds];
	[productQuery addFields:fields];

	[productQuery performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

		if (result.products){
			//you got *SDProduct* objects to work with
		}
	}];

## Using the Basket

Retrieving the Basket.

	SDQuery *basketQuery = [SDBasket query];
	[basketQuery performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

		if (result.basket){
			//you got the *SDBasket* object to work with
		}

	}];

Adding an Item to the Basket.

	NSNumber *variantId = @12345 // The id of the *SDProductVariant* object to be added

	SDQuery *basketQuery = [SDBasket query];
        [basketQuery addOrderLineForVariantId:variantId];

    	[basketQuery performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

		if (result.basket){
			//you got the *SDBasket* object to work with
		}

	}];

Removing an Item from the Basket.

	NSNumber *itemId = @12345 // The itemId that should be removed

	SDQuery *basketQuery = [SDBasket query];
        [basketQuery removeOrderLineForItemId:itemId];

    	[basketQuery performInBackground:^(SDResult *result, NSError *error) {

		if (error){
			//check your errors
		}

		if (result.basket){
			//you got the *SDBasket* object to work with
		}

	}];

Please note that one orderline adds/removes one Item only.
When constructing a Basket Query, you can add/remove multiple orderlines at once.

repository: nestele/aboutyou-ios-sdk

repo_name: nestele/aboutyou-ios-sdk


text:
[Home](http://gifloopcoder.com)

# GIF Loop Coder (GLC) Documentation

This is the documentation for glc. I suggest you start by reading the [intro section](intro.html). Follow along with that and actually type and run the examples there. Then scan through the [Objects](objects.html), [Styles](styles.html) and [Property Types](properties.html) sections and try out different objects and styles. Once you get the hang of the program, check the [Tips and Advance Use](tips.html) section to take it to the next level.

You can also check out the [GLC Blog](http://www.gifloopcoder.com/blog), where new features, sample code and small tutorials are posted from time to time.

Table of Contents

1. [Introduction to GIF Loop Coder (GLC)](intro.html)
2. [Objects](objects.html)
3. [Styles](styles.html)
4. [Property Types](properties.html)
5. [Tips and Advanced Use](tips.html)

repository: AlexRogalskiy/GifLoopCoder

repo_name: AlexRogalskiy/GifLoopCoder


text:
---
layout: nodes.liquid
date: Last Modified
title: "Bridge Task"
permalink: "docs/jobs/task-types/bridge/"
---

Bridge tasks make HTTP POST requests to pre-configured URLs. Bridges can be configured via the UI or the CLI, and are referred to by a simple user-specified name. This is the way that most jobs interact with [External Adapters](/docs/external-adapters/).

**Parameters**

- `name`: an arbitrary name given to the bridge by the node operator.
- `requestData` (optional): a statically-defined payload to be sent to the external adapter.
- `async` (optional): a boolean indicating whether the task should hibernate and wait for the Bridge to make an HTTP request back to the node at a later time with the result.

**Outputs**

A string containing the response body.

**Example**

```dot
my_bridge_task [type="bridge"
                name="some_bridge"
                requestData=<{
                    "foo": $(foo),
                    "bar": $(bar),
                    "jobID": 123
                }>]
```

repository: lukeramsden/documentation

repo_name: lukeramsden/documentation


text:
# dotNetFx35Windows10
Install .NET Framework 3.5 offline on Windows 10 using sources extracted from the Windows 10 build specific installation media

## Preparation
- Copy the repo to a suitable folder on your PC
- Copy contents of sources\sxs folder from Windows 10 build specific installation media into "Win10SourcesSxs" folder
- For example to install .Net Framework 3.5 on "Windows 10 IoT Enterprise 2019 LTSC"
  - Download the "Windows 10 IoT Enterprise 2019 LTSC" installation media iso file
  - Extract the iso file into a suitable folder (using 7-zip or similar)
  - From extracted location copy the contents of sources\sxs folder and paste it into the "Win10SourcesSxs" folder
  - Once the files are available the DISM command used in the dotNetFx35Windows10.ps1 script will pick up the necessary files during installation.

## Running as Script
Type `.\dotNetFx35Windows10.ps1` in Powershell

## Running as EXE
The "dotNetFx35Windows10.ps1" script and the dependant "Win10SourcesSxs" folder can be converted into an EXE that can be executed without needing to run the script in Powershell.

Type `.\ConvertToExe.ps1` in Powershell. This will create "dotNetFx35Windows10.exe"

Execute "dotNetFx35Windows10.exe"


text:
# My 1st Webpage! :)

MIT<br>[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

* [Live Application Demo](https://brooks-portal.github.io/first-project/)

## Overview

This application uses uses HTML and CSS

* This is a starting day 1 coding portfolio and it will get better as time moves on.

## Get The Application Running!

Step by step instructions to get the application running on your local machine

* Pull repo
* Open file explorer
* click index.html

[![GitHub](https://img.shields.io/badge/My%20GitHub-Click%20Me!-blueviolet?style=plastic&logo=GitHub)](https://github.com/Brooks-portal)

repository: Brooks-portal/first-project

repo_name: Brooks-portal/first-project


text:
# Setup your macOS in no time.

If you are looking for a quick way to install all your apps - you should have a look at Brew and Cask. Ive uploaded my mac setup.

## How to use

download the file, open terminal and run the following to install Brew:

```
  /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
```

Then run this command to execute the Brewfile

```
  brew bundle
```

Have fun!

**License: MIT**

repository: viezel/mac-setup

repo_name: viezel/mac-setup


text:
# goroutine safe uint64 bit operation

## obsolete
use bitsuint64 package

## argument
bit position is uint
bit data is uint64