text:
## Question2Answer deployment

These playbooks deploy Question2Answer with Apache2 and MySQL for Ubuntu Xenial.

## Installation
- Ensure you have the correct credential and python2.7 on the server you want to install q2a.
- Edit the `hosts` inventory file to include the names or URLs of the servers you want to deploy.
- Configure the q2a credentials in `group_vars/all` file.

Run the playbook:

	ansible-playbook -i hosts site.yml -e 'ansible_python_interpreter=/usr/bin/python2.7'


text:
# Changelog

All notable changes to this project will be documented in this file.

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

## [Unreleased]

### Changed

- Renamed `LabBuilder_LocalizedData.psd1` to `LabBuilder.strings.psd1` to
  align to other PowerShell modules.
- Convert all DSC configurations to use ComputerManagementDsc version
  <IP_ADDRESS>.
- Clean up code style on all DSC Library files.
- `dsclibrary\DC_FORESTCHILDDOMAIN.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
- `dsclibrary\DC_FORESTPRIMARY.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
- `dsclibrary\DC_FORESTSECONDARY.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
- `dsclibrary\MEMBER_DHCP.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
  - Correct DHCP scope example - fixes [Issue #343](https://github.com/PlagueHO/LabBuilder/issues/343).
- `dsclibrary\MEMBER_DHCPDNS.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
  - Correct DHCP scope example - fixes [Issue #343](https://github.com/PlagueHO/LabBuilder/issues/343).
- `dsclibrary\MEMBER_DHCPNPAS2016.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
  - Correct DHCP scope example - fixes [Issue #343](https://github.com/PlagueHO/LabBuilder/issues/343).
- `dsclibrary\MEMBER_DNS.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
- `dsclibrary\STNADALONE_DHCPDNS.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
  - Correct DHCP scope example - fixes [Issue #343](https://github.com/PlagueHO/LabBuilder/issues/343).
- `dsclibrary\STNADALONE_INTERNET.DSC.ps1`:
  - Convert to use xDnsServer version <IP_ADDRESS>.
  - Clean up code style.
- Remove AppVeyor CI pipeline and updated to new Continuous Delivery
  pattern using Azure DevOps - fixes [Issue #355](https://github.com/PlagueHO/LabBuilder/issues/355).
- Fix build badges.

license: MIT

repository: cypheredout/LabBuilder

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: cypheredout/LabBuilder


text:
---
layout: default
---

# 1994-06-22 - Re: Unofficial Release

## Header Data

From<EMAIL_ADDRESS>(Jamie Lawrence)

To<EMAIL_ADDRESS>Message Hash: 3867767a47c3a98f2bb38cd488c42d824edd4a9dba7465389d24003f5f19fc5c

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1994-06-22 20:01:34 UTC

Raw Date: Wed, 22 Jun 94 13:01:34 PDT

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Jamie Lawrence)
Date: Wed, 22 Jun 94 13:01:34 PDT
To<EMAIL_ADDRESS>Subject: Re: Unofficial Release
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

At  3:27 PM 06/22/94 -0400, Perry E. Metzger wrote:

>Fine.  There is no point in

I was wondering if you had recently lost an appendage, or maybe had bad
hemorrhoids or something.

{% endraw %}
```

## Thread

+ Return to [June 1994](/archive/1994/06)

+ Return to<EMAIL_ADDRESS>(Jamie Lawrence)](/authors/jamiel_at_sybase_com_jamie_lawrence_)"

+ 1994-06-22 (Wed, 22 Jun 94 13:01:34 PDT) - Re: Unofficial Release -<EMAIL_ADDRESS>(Jamie Lawrence)_

gha_license_id: MIT


text:
## Steps needed for running the testsuite

1- Install [ZROBOT](https://github.com/Jumpscale/0-robot/blob/master/docs/getting_started.md).

2- Install requirements.
   ```
   cd /tests/integration_tests
   pip3 install -r requirements
   ```
3- Change ```config.ini``` as needed.
```
cd /tests/integration_tests
vim config.ini
```

4- Running Tests
```
cd /tests/integration_tests
nosetests -v -s testsuite --tc-file=config.ini
```


text:
# Build the Missing Notifying Chain

Firstly, a graph like this might be helpful.
![Data Updating Graph](data-updating-graph.png)

Ways to add the notifying mechanism between reactive data objects:
* assign (reference replacing)
* call `$set` method
* computed
* watch & assign

repository: xiGUAwanOU/tech-note

repo_name: xiGUAwanOU/tech-note


text:
## 5.7.0 2021-05-27

No functional changes since 5.6.0.

 * Upgrade to Vert.x 4.1.0.CR1
 * [MODCONF-82](https://issues.folio.org/browse/MODCONF-82) Upgrade to RMB 33
 * [MODCONF-69](https://issues.folio.org/browse/MODCONF-69) Add personal data disclosure form

## 5.6.0 2021-01-01

 * [MODCONF-68](https://issues.folio.org/browse/MODCONF-68) Update to RMB 32 / Vert.x 4.0.0)
 * [MODCONF-56](https://issues.folio.org/browse/MODCONF-56) Remove unused default configuration settings (settings/locale)

## 5.5.0 2020-11-02

 * [MODCONF-65](https://issues.folio.org/browse/MODCONF-65) Upgrade to RMB 31.1.5

## 5.4.1 2020-07-14

 * [MODCONF-54](https://issues.folio.org/browse/MODCONF-54) RMB v30.2.4, fix "public.gin_trgm_ops" does not exist

## 5.4.0 2020-06-09

 * [MODCONF-53](https://issues.folio.org/browse/MODCONF-53) Update to RMB 30.0.2 and fix all code smells
 * [MODCONF-51](https://issues.folio.org/browse/MODCONF-51) Fix Maven ${} variable replacement in src/main/resources
 * [MODCONF-32](https://issues.folio.org/browse/MODCONF-32) Populate sample data for Tenant addresses

## 5.3.0 2019-12-18

 * [MODCONF-44](https://issues.folio.org/browse/MODCONF-44) POST item with id still makes server side ID. Version 5.2.0
   sample data must be wiped out, because the supplied ID in sample data
   was ignored.
 * [MODCONF-36](https://issues.folio.org/browse/MODCONF-36) Data migration script for changes to PO Number
   prefix/suffix entries

## 5.2.0 2019-12-04

 * [MODCONF-42](https://issues.folio.org/browse/MODCONF-42) Upgrade to RMB 29
 * [MODCONF-41](https://issues.folio.org/browse/MODCONF-41) Use JVM features to manage container memory
 * [MODCONF-35](https://issues.folio.org/browse/MODCONF-35) Fix PUT return 500 on entity not found
 * [MODCONF-33](https://issues.folio.org/browse/MODCONF-33) Use the tenant API for loading sample/reference data

## 5.1.0 2019-05-09

 * [MODCONF-29](https://issues.folio.org/browse/MODCONF-29) Upgrade to RMB 24

## 5.0.1 2018-10-02

 * [MODCONF-26](https://issues.folio.org/browse/MODCONF-26) Update to RAML 1.0 / RMB 21

## 5.0.0 2018-09-04

 * [MODCONF-21](https://issues.folio.org/browse/MODCONF-21) Configuration records are unique for each module, config name and code
 * [MODCONF-21](https://issues.folio.org/browse/MODCONF-21) Configuration records are enabled by default
 * [MODCONF-22](https://issues.folio.org/browse/MODCONF-22) Use dereferenced kv_configuration.schema for metadata sorting
 * Upgrades to RAML Module Builder 19.3.1
 * CQL queries including an unrecognised index report a 400 instead of 422

## 4.0.3 2018-04-24

 * [MODCONF-17](https://issues.folio.org/browse/MODCONF-17) 500 and 422 errors while querying configurations/audit

## 4.0.2 2018-03-03

w* [MODCONF-16](https://issues.folio.org/browse/MODCONF-16) Move to RMB 19 - generated sources will be moved to /classes

## 4.0.1 2018-02-19

 * [MODCONF-15](https://issues.folio.org/browse/MODCONF-15) Move to RMB 18
 * [MODCONF-14](https://issues.folio.org/browse/MODCONF-14) Unit test should stop embedded postgres when complete

## 4.0.0

 * [MODCONF-12](https://issues.folio.org/browse/MODCONF-12) Upgrade to RMB 16.0.2, read-only fields are removed
   and do not return a 422

## 3.0.0

 * [MODCONF-8](https://issues.folio.org/browse/MODCONF-8)
 * [MODCONF-7](https://issues.folio.org/browse/MODCONF-7)

## 2.0.0

 * [MODCONF-3](https://issues.folio.org/browse/MODCONF-3) mod-configuration accepts invalid fields in queries

## 1.0.1

 * [MODCONF-2](https://issues.folio.org/browse/MODCONF-2) Upgrade interface version from 0.0.9 to 1.0

## 1.0.0

 * [FOLIO-649](https://issues.folio.org/browse/FOLIO-649) User-specific preferences in mod-config
 * Align with camelCase naming conventions

repository: javalkar-varun/mod-configuration

repo_name: javalkar-varun/mod-configuration


text:
ngx_python
==========
[![Build Status](https://travis-ci.org/rryqszq4/ngx_python.svg?branch=master)](https://travis-ci.org/rryqszq4/ngx_python)
[![license](https://img.shields.io/badge/license-BSD--2--Clause-blue.svg)](https://github.com/rryqszq4/ngx_python/blob/master/LICENSE)

[ngx_python](https://github.com/rryqszq4/ngx_python) - Embedded python for nginx-module. Another name is python-nginx-module.

Requirement
-----------
- python 2.7.*
- nginx-1.6.3+

Installation
-------
```sh
$ git clone https://github.com/rryqszq4/ngx_python.git

$ wget 'http://nginx.org/download/nginx-1.6.3.tar.gz'
$ tar -zxvf nginx-1.6.3.tar.gz
$ cd nginx-1.6.3

$ export PYTHON_INC=/path/to/python/include/python2.7
$ export PYTHON_BIN=/path/to/python/bin

$ ./configure --user=www --group=www \
              --prefix=/path/to/nginx \
              --add-module=/path/to/ngx_python
$ make
$ make install
```

Synopsis
--------
nginx config:
```nginx
user www www;
worker_processes  4;

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

    keepalive_timeout  65;

    server {
        listen       80;
        server_name  localhost;

        location /content_by_python {
            content_by_python "
from time import time,ctime
import ngx

ngx.echo('Hello, Ngx_Python at ' + ctime(time()) + '\\n')

a = [1,2,3,4,5]
ngx.echo(a)

ngx.echo('\\n'+str(type(a)))
            ";
        }

        location /content_by_python_file {
            content_by_python_file /ngx_python/t/library/hello.py;
        }
    }
}
```

execute:

```sh
$ curl http://localhost/content_by_python
Hello, ngx_python at Thu Dec  1 00:38:02 2016
[1, 2, 3, 4, 5]
<type 'list'>

$ curl http://localhost/content_by_python_file
Hello, Ngx_Python

```

Copyright and License
---------------------
BSD 2-Clause License

Copyright (c) 2016-2017, rryqszq4
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this
  list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice,
  this list of conditions and the following disclaimer in the documentation
  and/or other materials provided with the distribution.


text:
# Inteligência Artificial @ FEUP  (Artificial Inteligence)

Project for the IART class of MIEIC @ FEUP.
Made by [João Campos](https://github.com/Pastilhas), [Rita Mota](https://github.com/atomatir) and [Simão Santos](https://github.com/simao-santos).

# Pivit
### Introduction to the game

[Pivit](https://www.boardgamegeek.com/boardgame/135473/pivit) is game played in a 8x8 checkered board. Two to four players move their pieces strategically in other to have the most pieces when the game reaches a final state.
At the start of the game, the pieces are distributed in the sides the board, excluding the corners, in a way the first movement cannot be a capture.

Each piece can move in only one direction (x or y). Whenever a piece moves, when it reaches its destination, it rotates changing its orientation to be the oposite of the one before. When moving pieces cannot go through one another, but the destination of a piece can be an enemy piece. If the final cell of a movement is an enemy piece, that piece is captured a leaves the board.

There are two types of pieces, 'minions', which must end their movement in a cell of opposite colour of the cell they were in, and 'masters', which can move independently of the colour of the cells. A piece is promoted from 'minion' to 'master' if it enters one of the corners of the board. The game ends when all 'minion' pieces are gone and the winner is the player with most 'master' pieces on the board.

### Introduction to the project

In this project we are going to develop an AI that is capable of playing Pivit using several algorythms in order to win consistently.

---

### How to run
``javac *.java ``<br>
``java Game ``

repository: Pastilhas/IART-FEUP

repo_name: Pastilhas/IART-FEUP


text:
# Resources Page

React-based module for site-wide resources

## Dependencies

[Plumber API](https://github.com/RGLab/ImmuneSpaceLabKeyAPI)

## Setup

<!-- Instructions for getting module working on the server -->

## Resources

<!-- _Links to any helpful resources like LabKey or Notion documentation or external sources used when developing this module_ -->

repository: RGLab/LabKeyModules

branch_name: refs/heads/main

gha_language: JavaScript

repo_name: RGLab/LabKeyModules


text:
## How to convert PDF to PNG from URL asynchronously for PDF to image API in VB.NET and ByteScout Cloud API Server

### Learn in simple ways: How to convert PDF to PNG from URL asynchronously for PDF to image API in VB.NET

We regularly create and update our sample code library so you may quickly learn PDF to image API and the step-by-step process in VB.NET. PDF to image API in VB.NET can be applied with ByteScout Cloud API Server. ByteScout Cloud API Server is the ready to use Web API Server that can be deployed in less than 30 minutes into your own in-house server or into private cloud server. Can store data on in-house local server based storage or in Amazon AWS S3 bucket. Processing data solely on the server using buil-in ByteScout powered engine, no cloud services are used to process your data!.

Use the code displayed below in your application to save a lot of time on writing and testing code. Follow the tutorial and copy - paste code for VB.NET into your project's code editor. You can use these VB.NET sample examples in one or many applications.

ByteScout Cloud API Server - free trial version is available on our website. Also, there are other code samples to help you with your VB.NET application included into trial version.

## Get In Touch

[Click here to get in touch](https://bytescout.zendesk.com/hc/en-us/requests/new?subject=ByteScout%20Cloud%20API%20Server%20Question)

or send email to [support@bytescout.com](mailto:support@bytescout.com?subject=ByteScout%20Cloud%20API%20Server%20Question)

## Free Trial Download

[Get Your 60 Day Free Trial](https://bytescout.com/download/web-installer?utm_source=github-readme)

## Web API (On-demand version)

[Get your free API key](https://pdf.co/documentation/api?utm_source=github-readme)

## API Documentation and References

[Explore ByteScout Cloud API Server Documentation](https://bytescout.com/documentation/index.html?utm_source=github-readme)

[Explore Web API Documentation](https://pdf.co/documentation/api?utm_source=github-readme)

[Check Free Training Sessions for ByteScout%20Cloud%20API%20Server](https://academy.bytescout.com/)

## Video Review

[https://www.youtube.com/watch?v=NEwNs2b9YN8](https://www.youtube.com/watch?v=NEwNs2b9YN8)

url: https://raw.githubusercontent.com/repohoarder/ByteScout-SDK-SourceCode/32dd9367cebb66e3aa16bd803798c026d7dfeed5/Cloud API Server/PDF To Image API/VB.NET/Convert PDF To PNG From URL Asynchronously/README.md

repository: repohoarder/ByteScout-SDK-SourceCode

repo_name: repohoarder/ByteScout-SDK-SourceCode


text:
# Kaleidoscope-Swift

This is the LLVM-backed compiler from part 3 of the
[Building a Compiler in Swift with LLVM](https://harlanhaskins.com/2017/01/09/building-a-compiler-with-swift-in-llvm-part-3-code-generation-to-llvm-ir.html)
series.

# Important Installation Instructions:

> Apologies, but Part 4 of the project currently only works on macOS due to some build
> behavior we need to fix for LLVMSwift.

You must follow the instructions specificed in the README for [LLVMSwift](https://github.com/llvm-swift/LLVMSwift.git) to be
able to compile this project.

Once that's done, just open this folder and run

```bash
swift build
```

and you should have a binary at `.build/Debug/Kaleidoscope`.

On macOS, you can also run

```bash
swift package generate-xcodeproj
```

to create an Xcode project for this repo.

# Author

Harlan Haskins ([@harlanhskins](https://github.com/harlanhaskins))

# License

This project is released under the MIT license, a copy of which is attached
to this repo.

repository: harlanhaskins/Kaleidoscope-Swift

gha_language: Swift

repo_name: harlanhaskins/Kaleidoscope-Swift


text:
Account
=======

Configuration
-------------

The `account` options in `config.json` allow you to set how long an account is viable at times during it's lifespan. There are current only settings for `initiate` and `complete`. We want the lifetime for an initial account creation to be short so we can clean up accounts which haven't been completed and won't have numerous files sitting in storage. Also we set a `complete` account to 6 months; to comply with PCI standards.

The object assigned to each account section is passed into the OtDate object to set the expires for each lifetime.

The `idHash` property of `account` covers how the ids will be hashed when stored. This is passed into the secure hash method and then used when saving an account. **The `idHash` values must never change once set up.** If the values change a client or account holder will never be able to get back into their account.

You can find a list of available hashing methods in `lib/ciphers-and-hashes.js`.

Where the account information is stored can be change by updating `accountDir`. The registration files can be updated by changing `registrationDir`. Ideally these would be different as we store temporary registration files during the sign up process in the `registrationDir`, and permanent files for the account in `accountDir` once sign up is complete. These cannot be local directories as they will be passed to [storage] to handle.

The lengths of the IDs we use for account creation can be adjusted using `accountIdLength` and `registrationIdLength`.

The `passwordSaltLength` is used to adjust the length of the password salt we generate for the account holder to create their password hash.

    "account": {
        "accountDir": "account/",
        "accountIdLength": 24,
        "completeLifetime": {
            "months": 6
        },
        "idHash": {
            "algorithm": "sha256",
            "hashLength": 24,
            "iterations": 10000,
            "salt": "Ucg4TTL1N7tt6GMw3W3wULgaf4lALKHOuM4SBnh0FocOr3ccLH9eXLneoDDOrMVZ"
        },
        "initiateLifetime": {
            "hours": 1
        },
        "passwordSaltLength": 128,
        "registrationDir": "registration/",
        "registrationIdLength": 24
    }

Initiating an Account
---------------------

The first action for an account is `initiate`. This sets up a few pieces of data needed to properly generate and track an account. We generate a `regId`, `mfaKey`, and `passwordSalt`. An email address must be passed in. These are then passed back to the user to store on their own and will be used to generate their password.

Information will be saved to a file named after the hash of the `regId` in the `registrationDir` [storage] location. This registration file will be deleted upon successful creation of an account file.

Confirming an Account
---------------------

The next action is to confirm an account. This requires the user to access the URL using the `regId` we gave them. We will then compare it's valid by comparing the hashes then return the `mfaKey` and `passwordSalt` so they can proceed to the next step.

Completing an Account
---------------------

To complete an account, the client will need to pass in a hashed `password`, the `regId` which we gave them previously as well as a `currentMfa` code and `previousMfa` code. This will allow us to find the registration file using the hashed `regId` and looking it up in [storage]. Getting the `mfaKey` off the account we are able to then validate the user using the MFA codes they passed in.

If the account validates, we create the account file from the registration file, add the `password` to it, and generate an `accountId`. The file is then saved under the `accountDir` using the hashed `accountId` as the file name. Only the `accountId` is sent back to the client.

Passwords
---------

Passwords are handled on the client's side and then stored in their encrypted account file upon completing the sign up process.

Passwords should be hashed along with the `passwordSalt` we provided during account signup.

    hash(password + passwordSalt)

When sending the password in for authentication, the password should be hashed again and then hashed with the challenge the applictation sent them.

    hash(hash(hashedPassword) + challenge)

The hashing of the password is handled by the client; we only store what is given. The hashing of the challenge and subsequent hashing there after, will be set in `config.json` and will utilize `pbkdf2` on both sides to maintain a consistent login paradigm.

OpenToken.io will also verify, per byte, a hash which was sent in, equals what has been hashed on its side.

    A4f38 != a4f38

[storage]: storage.md

repository: lnagle/opentoken

repo_name: lnagle/opentoken


text:
### [CVE-2019-11598](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11598)
![](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

In ImageMagick 7.0.8-40 Q16, there is a heap-based buffer over-read in the function WritePNMImage of coders/pnm.c, which allows an attacker to cause a denial of service or possibly information disclosure via a crafted image file. This is related to SetGrayscaleImage in MagickCore/quantize.c.

### POC

#### Reference
- https://github.com/ImageMagick/ImageMagick/issues/1540

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

repository: trickest/cve

gha_language: HTML

repo_name: trickest/cve


text:
# fastapi-tutorial-mssql
The FastAPI SQL database tutorial modified to use `mssql+pyodbc`.

Proof-of-concept that using FastAPI with mssql does *not* require
aioodbc and `async def` for path operation functions.

See

https://fastapi.tiangolo.com/tutorial/

and

https://fastapi.tiangolo.com/tutorial/sql-databases/

for details on using the tutorial (installing FastAPI,
launching uvicorn, etc.).

GitHub discussion:

https://github.com/sqlalchemy/sqlalchemy/issues/6521

Notes:

- You may need to tweak `SQLALCHEMY_DATABASE_URL` in database.py to connect
to your SQL Server instance.

- This code includes a couple of minor code updates for SQLAlchemy 1.4/2.0.

repository: adeleof/fastapi-tutorial-mssql

repo_name: adeleof/fastapi-tutorial-mssql


text:
---
layout: post
title: My CI Workflow
categories: [general, code, puppet]
tags: [code, git, puppet, CI]
fullview: true
---
Don't get me wrong, I like Jenkins, unlike every other Java app. But I'm a Sysadmin (at least in spirit), and there are still things that I need to get used to from the development world. But Jenkins is:

- Extremely flexible (or extremely complicated)
- Another App I'd need to host somewhere (not that I'm laking IT resources)
- As my manager likes to put it, using a Ferrari to drive at 20 miles per hour (that's been taken out of context by the way)

I needed something extremely simple, since I've a module published in the Puppet Forge (hopefully more soon enough), and I want to run Unit Tests on it before I actually publish new releases.
In comes **Travis CI**. It's probably way more powerful that what I'm using it for, but it's simple enough for me go get it integrated on my development workflow because:

- It integrates with GitHub, so I don't need to write and troubleshoot any custom hooks.
- It email's me when my build fails
- I've a nice tag that I can add into my README.md to force me to fix my builds
- It's extremely simple to configure

How simple you may ask?

- Head onto the [Travis-CI Website](http://www.travis-ci.org)
- Log-in with your GitHub Account, and enable the repo's you want to manage

Now those repositories need a bit of extra love to be tested with Travis. You need to create a .travis.yml file with the configuration.

{% highlight yaml %}
---
language: ruby
bundler_args: --without system_tests
script: "bundle exec rake validate && bundle exec rake lint && bundle exec rake spec SPEC_OPTS='--format documentation'"
matrix:
  fast_finish: true
  include:
  - rvm: 1.9.3
    env: PUPPET_GEM_VERSION="~> 3.0"
  - rvm: 2.0.0
    env: PUPPET_GEM_VERSION="~> 3.0"
  - rvm: 2.0.0
    env: PUPPET_GEM_VERSION="~> 4.0"
notifications:
  email<EMAIL_ADDRESS>{% endhighlight %}

Now I'm assuming here that you have your Gemfile and Rakefile properly set up, in my case my jobs are as follows:

{% highlight ruby %}
require 'rubygems'
require 'puppetlabs_spec_helper/rake_tasks'
require 'puppet-lint/tasks/puppet-lint'
PuppetLint.configuration.send('disable_80chars')
PuppetLint.configuration.ignore_paths = ["spec/**/*.pp", "pkg/**/*.pp"]

desc "Validate manifests, templates, and ruby files"
task :validate do
  Dir['manifests/**/*.pp'].each do |manifest|
    sh "puppet parser validate --noop #{manifest}"
  end
  Dir['spec/**/*.rb','lib/**/*.rb'].each do |ruby_file|
    sh "ruby -c #{ruby_file}" unless ruby_file =~ /spec\/fixtures/
  end
  Dir['templates/**/*.erb'].each do |template|
    sh "erb -P -x -T '-' #{template} | ruby -c"
  end
end

task :default => [:validate, :spec, :lint]
{% endhighlight %}

Good news if you don't understand any of that, puppet module generate actually set's that up for you!

So in my case, I'm doing parsing validation, linting and spec testing on my module. Even if you don't write spec tests, just doing parser validation and linting is a great start!

##Keeping you honest
You need to write spec tests to cover your cases, the more spec tests you write, the more you can be sure that you're not breaking anything when changing your code. Luckily there is a great tool to help you with that, and its Coveralls.

![How much of my code do my tests cover](/assets/media/coveralls/code-coverage.png "How much of my code do my tests cover")
![Where do I need to work a bit more](/assets/media/coveralls/more-work.png "Where do I need to work a bit more")

To set up Coveralls, [the instructions are pretty clear](https://coveralls.zendesk.com/hc/en-us/articles/201769485-Ruby-Rails), but basically you'd need to:

- Include the Coveralls gem in the Gemfile
{% highlight ruby %}
source 'https://rubygems.org'

puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 3.3']
gem 'puppet', puppetversion
gem 'puppetlabs_spec_helper', '>= 0.1.0'
gem 'puppet-lint', '>= 0.3.2'
gem 'facter', '>= 1.7.0'
gem 'rake'
gem 'rspec-puppet'
gem 'dpl'
gem 'coveralls', require: false
{% endhighlight %}
(That last lines add coveralls by the way).

And add Coveralls to your testing suite
{% highlight ruby %}
require 'coveralls'
Coveralls.wear!
require 'puppetlabs_spec_helper/module_spec_helper'
{% endhighlight %}

The only gotcha so far, is that you need to add an environment variable (USENETWORK=true) in Travis to allow the test to post the result to Coveralls. You can do this through the Web Interface, or in your .travis.yml file.

![Setting the environment variable in Travis](/assets/media/coveralls/envvar.png "Setting the environment variable in Travis")


text:
original source: [https://adventofcode.com/2019/day/3](https://adventofcode.com/2019/day/3)
## --- Day 3: Crossed Wires ---
The gravity assist was successful, and you're well on your way to the Venus refuelling station.  During the rush back on Earth, the fuel management system wasn't completely installed, so that's next on the priority list.

Opening the front panel reveals a jumble of wires. Specifically, *two wires* are connected to a central port and extend outward on a grid.  You trace the path each wire takes as it leaves the central port, one wire per line of text (your puzzle input).

The wires twist and turn, but the two wires occasionally cross paths. To fix the circuit, you need to *find the intersection point closest to the central port*. Because the wires are on a grid, use the [Manhattan distance](https://en.wikipedia.org/wiki/Taxicab_geometry) for this measurement. While the wires do technically cross right at the central port where they both start, this point does not count, nor does a wire count as crossing with itself.

For example, if the first wire's path is `R8,U5,L5,D3`, then starting from the central port (`o`), it goes right `8`, up `5`, left `5`, and finally down `3`:

```
...........
...........
...........
....+----+.
....|....|.
....|....|.
....|....|.
.........|.
.o-------+.
...........
```

Then, if the second wire's path is `U7,R6,D4,L4`, it goes up `7`, right `6`, down `4`, and left `4`:

```
...........
.+-----+...
.|.....|...
.|..+--X-+.
.|..|..|.|.
.|.-*X*--+.|.
.|..|....|.
.|.......|.
.o-------+.
...........
```

These wires cross at two locations (marked `X`), but the lower-left one is closer to the central port: its distance is `3 + 3 = 6`.

Here are a few more examples:

 - `R75,D30,R83,U83,L12,D49,R71,U7,L72
U62,R66,U55,R34,D71,R55,D58,R83` = distance `159`
 - `R98,U47,R26,D63,R33,U87,L62,D20,R33,U53,R51
U98,R91,D20,R16,D67,R40,U7,R15,U6,R7` = distance `135`

*What is the Manhattan distance* from the central port to the closest intersection?

## --- Part Two ---
It turns out that this circuit is very timing-sensitive; you actually need to *minimize the signal delay*.

To do this, calculate the *number of steps* each wire takes to reach each intersection; choose the intersection where the *sum of both wires' steps* is lowest. If a wire visits a position on the grid multiple times, use the steps value from the *first* time it visits that position when calculating the total value of a specific intersection.

The number of steps a wire takes is the total number of grid squares the wire has entered to get to that location, including the intersection being considered. Again consider the example from above:

```
...........
.+-----+...
.|.....|...
.|..+--X-+.
.|..|..|.|.
.|.-X--+.|.
.|..|....|.
.|.......|.
.o-------+.
...........
```

In the above example, the intersection closest to the central port is reached after `8+5+5+2 = *20*` steps by the first wire and `7+6+4+3 = *20*` steps by the second wire for a total of `20+20 = *40*` steps.

However, the top-right intersection is better: the first wire takes only `8+5+2 = *15*` and the second wire takes only `7+6+2 = *15*`, a total of `15+15 = *30*` steps.

Here are the best steps for the extra examples from above:

 - `R75,D30,R83,U83,L12,D49,R71,U7,L72
U62,R66,U55,R34,D71,R55,D58,R83` = `610` steps
 - `R98,U47,R26,D63,R33,U87,L62,D20,R33,U53,R51
U98,R91,D20,R16,D67,R40,U7,R15,U6,R7` = `410` steps

*What is the fewest combined steps the wires must take to reach an intersection?*

repository: encse/adventofcode

gha_language: C#

gha_license_id: NOASSERTION

repo_name: encse/adventofcode


text:
[etcher-sdk](../README.md) › [Block](block.md)

# Interface: Block

## Hierarchy

* **Block**

## Index

### Properties

* [length](block.md#length)
* [offset](block.md#offset)

## Properties

###  length

• **length**: *number*

*Defined in [lib/sparse-stream/shared.ts:29](https://github.com/balena-io-modules/etcher-sdk/blob/0441bfb/lib/sparse-stream/shared.ts#L29)*

___

###  offset

• **offset**: *number*

*Defined in [lib/sparse-stream/shared.ts:28](https://github.com/balena-io-modules/etcher-sdk/blob/0441bfb/lib/sparse-stream/shared.ts#L28)*

repository: balena-io-modules/etcher-sdk

gha_language: TypeScript

repo_name: balena-io-modules/etcher-sdk


text:
# openssl_socket

Up to [Documentation](../README.md).

Purpose          | File
---------------- | ----
Include          | [openssl_socket.h](../../src/openssl_socket.h)
Interface        | [openssl_socket.i.h](../../src/i/openssl_socket.i.h)
Tests / Examples | [test/socket.cpp](../../test/socket.cpp)

__Note__: See the [socket](socket.md) limitations on availability.
Additionally, this functionality requires `OpenSSL` to be installed.

`abc` does not implement any cryptographic functionality, nor does it distribute `OpenSSL` or any other crypto or TLS library.

The main purpose of these socket classes is to prove that it is possible to support TLS on top of the existing `abc` sockets as well as to provide an example how to do it.

`OpenSSL` was chosen because it is probably the most popular TLS implementation and it is freely available on Linux distributions

`openssl_tcp_server_socket` is a TCP server socket that supports TLS.
It can _listen_ and _accept_ TLS client connections.

`openssl_tcp_client_socket` is TCP client socket that supports TLS.
It can _connect_ to a TLS server and can _send_ and _receive_ bytes over the encrypted connection.

repository: zlatko-michailov/abc

repo_name: zlatko-michailov/abc


text:
---
title: “Magic Wand”
lang: en
date: 2019-11-27
published: True
categories: [fiction]
ref: magic_wand
---

As humanity emerged from the era which would then be called middle ages. Not even the first time magic got reset, they remembered their elders could do magic.
Those elders held in their hands wands and they could cast spells. Before long the details would become hasty but at first they vaguely remembered how the master of all wizard was Apple and its servant Siri fought for power with Alexa until Alexa’s master destroyed all magic wands rendering those shiny wands useless...

repository: oberron/spark-fi

repo_name: oberron/spark-fi


text:
#Courier.js

Simple and flexible pub-sub for JavaScript.

##Using it
```javascript
var courier = new Courier();

// subscribing to a message
courier.receive("new-message", function(msg){
  // do something with the message
  ...
});

// sending a new message
// the first parameter is the message identifier
// the second parameter can be anything
// and will just be forwarded to the receiver
courier.send("new-message", {
  your: "message"
});

// By default, an exception will be thrown if the specified
// receiver isn't found. To avoid this set throwOnMissing: false
courier.send("new-message", {
  your: "delegation"
}, {throwOnMissing: false});

// Regular Expressions can also be used as both `receiver` and
// `sender` identifiers
courier.send(/[Aa]\s(regex)?\ssender/, {
  your: "message"
});

courier.receive(/[Aa]\s(regex)?\sreceiver/, function(msg){
  ...
});
```

###Unsubscribe

Courier allows you to unsubscribe to any message with the given
receiver returned function, like so:

```javascript
var unsubscribe = courier.receive("one-time-receiver", function(msg){
  // do some work
  unsubscribe(); // this will tell courier to remove this
});
```


text:
# MLBarcodeScanner
## Building Barcode/QR code scanner for Android using Google ML Kit and CameraX

An easy way to scan Barcode/QR code with CameraX using new Google ML Kit. For more details, please check my article<EMAIL_ADDRESS>

repository: chokokatana/MLBarcodeScanner

repo_name: chokokatana/MLBarcodeScanner


text:
# flyd-router

HTML5 History Streams

This is essentially a fork of [mithril](https://github.com/lhorie/mithril.js/)'s router, but refactored to work with other frameworks by exposing route changes via flyd streams.

So a couple of things change...

1) Unlike Mithril's router, you're responsible for re-rendering your component yourself somehow.  (if you're using React, consider [react-flyd-component](https://github.com/sdougbrown/react-flyd-componen).
2) No link component as that is also very renderer-specific.

This is intentionally raw, and requires quite a bit of massaging to use.  Mostly, this is just for me to play around with.

repository: sdougbrown/flyd-router

repo_name: sdougbrown/flyd-router


text:
---
layout: post
title:      "My First CLI Project: Premier League Explorer"
date:       2020-04-16 01:19:53 +0000
permalink:  my_first_cli_project_premier_league_explorer
---

 Ever since I signed up for Flatiron School and heard about the project for Module 1, I began writing a list of ideas as they came to me during my first couple of weeks in the program while working on labs. I had about 5 to 6 different ideas but ultimately I ended up choosing to do something about soccer, something that I am extremely passionate about (and miss dearly due to COVID-19). I strongly believe that working on projects that pertain to your interests allows you to get the most out of your projects, as you will know about your interests better than most people, which will allow you to not only care more about the project,  but will help you get more out of it as well, since you will be particular in terms of what data you want and how it should be formatted. There were a few sections of my project that I thought would be worth sharing.
	The goal of my project was to create a quick way to view information and stats about teams in the English Premier League. I was able to accomplish this with the FootyStats API, which, even on the free tier, gave me more data than I knew what to do with. Once I got my API set up, it was time to create my objects.
 As most of us would have done, I created my Team class, created a bunch of attr_accessors, and created my standard initialize method -- which took in a number of different arguments about the team instance I was about to create. I knew that there was a better way of doing this via [mass assignment](https://learn.co/tracks/online-software-engineering-structured/object-oriented-ruby/metaprogramming/mass-assignment-and-metaprogramming), but I was honestly a bit intimidated by it, so I chose the long way / ugly way. After a quick project review with my cohort lead, I was able to turn this:
```
   def initialize (name:, founded:, position:, wins:, draws:, losses:, g_scored:, g_conceded:, matches_played:, website:, goal_difference:, points:)
      @name = name
      @founded = founded
      @position = position
      @wins = wins
      @draws = draws
      @losses = losses
      @g_scored = g_conceded
      @g_conceded = g_conceded
      @matches_played = matches_played
      @website = website
      @goal_difference = goal_difference
      @points = points
      save
   end
```
..into this:
```
   def initialize (team_hash)
      team_hash.each{|k,v| self.send("#{k}=",v)}
      save
   end
```

 I think we all know which one is prettier.
 I mentioned that I wanted to display team stats and their current position in the table. This meant I was going to have to do some serious formatting if I wanted to have my CLI project to look somewhat presentable. I originally tried to use the .center method on my strings, but in all honestly, it was such a massive headache and did not seem worth using. I ended up using an amazing gem called terminal-table which not only allowed me to easily format my stats into a clean table format, but it allowed me to do it quickly and painlessly.
	Overall, I would say that after just one project, the project portion of Flatiron School truly does seem to be a hidden gem (as my cohort lead would say), as it forces you to really think about all of the labs you’ve worked on in a particular module and put them to use so that you can not only meet all project requirements, but build a one of a kind project for your portfolio. As someone who has had a tiny bit of programming experience, this project was not too challenging, but nevertheless I still learned a ton.

If you are interested in playing with or contributing to my project you can find it in the Github repo posted below.

https://github.com/antdp425/premier_league_explorer

extension: markdown


text:
# Amanitopsis vaginata var. fulva Sacc., 1887 VARIETY

#### Status
SYNONYM

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Syll. fung. (Abellini) 5: 21 (1887)

#### Original name
Agaricus fulvus Schaeff., 1774

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Agaricales/Amanitaceae/Amanita/Amanita fulva/ Syn. Amanitopsis vaginata fulva/README.md

repo_name: mdoering/backbone


text:
# jersey-guice-jetty-angular-seed
Seed project for web application with rest back-end built on Jersey integrated with Guice running on embedded Jetty server and AngularJS front-end.

## Features

* Jersey resources working in Guice context, running on embedded Jetty.
* Client-server login and data protocols.
* In-memory AuthTokensService implementation, dummy LoginService implementation.
* Angular web application with login page, sample protected page and authentication and error handling and sample data page.
* Sample Data resource.

## Login protocol

Unauthorized client uses one of the login methods of LoginResource (except tokenLogin - it is discussed later)
to get auth token.
Auth token shold be saved on client side to avoid log-in on every session.
Every log-in replaces token so only the last one is valid and therefor loging in from one device will
force user to log in again to use another device. If you need multi-device login then store, expire and
replace tokens by userId + deviceId (need to be implemented).
Auth token should expire after some time (not implemented atm), to avoid log-in after that client should
use tokenLogin once at start of every session - it will both check client's token is valid and issue new one.

## Protocol

Every client request results in either ErrorResponse, NotAuthorizedResponse (client checks login before requesting
server so it occurs only in exceptional cases) or request-specific response (or SuccessResponse, if there is no specific
response for the request).

repository: nhekfqn/jersey-guice-jetty-angular-seed

repo_name: nhekfqn/jersey-guice-jetty-angular-seed


text:
# microbrewit-logserver

[![Build Status](https://travis-ci.org/Microbrewit/microbrewit-logserver.svg?branch=master)](https://travis-ci.org/Microbrewit/microbrewit-logserver)
[![Coverage Status](https://coveralls.io/repos/github/Microbrewit/microbrewit-logserver/badge.svg?branch=master)](https://coveralls.io/github/Microbrewit/microbrewit-logserver?branch=master)
[![Dependency Status](https://david-dm.org/microbrewit/microbrewit-logserver.svg?branch=master)](https://david-dm.org/microbrewit/microbrewit-logserver)

A simple Hapi.js based log server that the microbrewit frontend can log events
to.

The log server is implemented in Node.js and uses some ES6 features. Node >= 5
required. It uses Hapi.js as its framework of choice of ease of development.

## License

MIT. See License file.

## Installation

Clone repository: `git clone git@github.com:Microbrewit/microbrewit-logserver.git`.

Install production dependencies: `npm install --production`.
Install all dependencies: `npm install`

## Running

To run without supervisors: `npm start`.

Use [forever](https://www.npmjs.com/package/forever) or something similar if
you want to run the program continuously even when it crashes. Better yet, use
your OS' inbuilt supervisor. For example Systemd.

A docker image for running the log server in a container is forthcoming.

To run in dev mode use: `npm run watch-source`.

## Documentation

The very simple API is automatically documented with Swagger based on the
routes and Joi validators. Documentation can be found at
[localhost:8080/documentation](http://localhost:8080/documentation) after you
start the server. The host and port may differ if you've set the environment
variables.

## Testing

Currently no tests. Soon to come.

## Docker

See [microbrewit logserver on docker hub](https://hub.docker.com/r/microbrewit/microbrewit-logserver/).

repository: Microbrewit/microbrewit-logserver

repo_name: Microbrewit/microbrewit-logserver


text:
# Changelog

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

### [5.1.4](https://github.com/frontend-collective/react-image-lightbox/compare/v5.1.3...v5.1.4) (2021-07-13)

### [5.1.3](https://github.com/frontend-collective/react-image-lightbox/compare/v5.1.2...v5.1.3) (2021-07-13)

### [5.1.2](https://github.com/frontend-collective/react-image-lightbox/compare/v5.1.1...v5.1.2) (2021-07-13)

### Bug Fixes

* fix cross origin iframe detection ([6683a29](https://github.com/frontend-collective/react-image-lightbox/commit/6683a29639f0df2609849d9c71f7da0fa08a4882))

### [5.1.1](https://github.com/frontend-collective/react-image-lightbox/compare/v5.1.0...v5.1.1) (2019-11-12)

### Bug Fixes

* allow React.ReactNode as imageTitle and imageCaption in TypeScript projects ([#158](https://github.com/frontend-collective/react-image-lightbox/issues/158)) ([f1858a3](https://github.com/frontend-collective/react-image-lightbox/commit/f1858a3efe25b66b850565b308688669bd7bab66))
* demo parcel site on github pages ([822140e](https://github.com/frontend-collective/react-image-lightbox/commit/822140ed665f55f664c1a5ea851f6b3aeaed31db))
* don't prevent default inside a passive listener ([b2b6a79](https://github.com/frontend-collective/react-image-lightbox/commit/b2b6a798671de7027635123baec8584e3fefaaf2))
* fix getOrigin issue within iFrames ([#175](https://github.com/frontend-collective/react-image-lightbox/issues/175)) ([f290cb3](https://github.com/frontend-collective/react-image-lightbox/commit/f290cb344ac89f6359b39c0fd4ab8fe00bb36205)), closes [#136](https://github.com/frontend-collective/react-image-lightbox/issues/136)
* fix lint ([c2acf2c](https://github.com/frontend-collective/react-image-lightbox/commit/c2acf2ccd86610ad89f3af497e4eefc911da68ac))

# [5.1.0](https://github.com/frontend-collective/react-image-lightbox/compare/v5.0.0...v5.1.0) (2018-12-10)

### Bug Fixes

- change focus when zoom buttons becomes disabled to be able to still use arrow keys (fix issue [#132](https://github.com/frontend-collective/react-image-lightbox/issues/132)) ([#135](https://github.com/frontend-collective/react-image-lightbox/issues/135)) ([30ba946](https://github.com/frontend-collective/react-image-lightbox/commit/30ba946))

### Features

- typescript declarations files ([#116](https://github.com/frontend-collective/react-image-lightbox/issues/116)) ([357a801](https://github.com/frontend-collective/react-image-lightbox/commit/357a801))

# [5.0.0](https://github.com/frontend-collective/react-image-lightbox/compare/v4.6.0...v5.0.0) (2018-04-29)

### Features

- migrated away from style-loader ([e74b7c9](https://github.com/frontend-collective/react-image-lightbox/commit/e74b7c9))

### BREAKING CHANGES

- you must import the css for the component yourself,
  using `import 'react-image-lightbox/style.css';`. You only need to do this
  once in your application.
- Versions of IE earlier than IE 11 are no longer supported.

# [4.6.0](https://github.com/frontend-collective/react-image-lightbox/compare/v4.5.0...v4.6.0) (2018-03-09)

### Bug Fixes

- avoid cross-origin errors from using window.top ([5bb5ac9](https://github.com/frontend-collective/react-image-lightbox/commit/5bb5ac9))

### Features

- onImageLoad API ([b08be00](https://github.com/frontend-collective/react-image-lightbox/commit/b08be00))

# [4.5.0](https://github.com/frontend-collective/react-image-lightbox/compare/v4.4.1...v4.5.0) (2018-01-21)

### Features

- Custom error message prop for when images fail to load ([419998d](https://github.com/frontend-collective/react-image-lightbox/commit/419998d)), closes [#82](https://github.com/frontend-collective/react-image-lightbox/issues/82)

## [4.4.1](https://github.com/frontend-collective/react-image-lightbox/compare/v4.4.0...v4.4.1) (2018-01-14)

### Bug Fixes

- handle environment with no navigator. Fixes [#97](https://github.com/frontend-collective/react-image-lightbox/issues/97) ([7f36b72](https://github.com/frontend-collective/react-image-lightbox/commit/7f36b72))

# [4.4.0](https://github.com/frontend-collective/react-image-lightbox/compare/v4.3.0...v4.4.0) (2017-12-17)

### Bug Fixes

- silence react-modal warning by setting appElement ([a26d597](https://github.com/frontend-collective/react-image-lightbox/commit/a26d597))

### Features

- allow for override of react-modal props ([45a756d](https://github.com/frontend-collective/react-image-lightbox/commit/45a756d))

# [4.3.0](https://github.com/frontend-collective/react-image-lightbox/compare/v4.2.2...v4.3.0) (2017-10-13)

### Bug Fixes

- Hide orange outline around viewer in Chrome on Android ([359e9bd](https://github.com/frontend-collective/react-image-lightbox/commit/359e9bd))

### Features

- Add react@16 support ([e3e63b6](https://github.com/frontend-collective/react-image-lightbox/commit/e3e63b6))

## [4.2.2](https://github.com/frontend-collective/react-image-lightbox/compare/v4.2.1...v4.2.2) (2017-10-05)

### Bug Fixes

- Improve rendering on zoom in Safari ([bab9ca1](https://github.com/frontend-collective/react-image-lightbox/commit/bab9ca1))

## [4.2.1](https://github.com/frontend-collective/react-image-lightbox/compare/v4.1.0...v4.2.1) (2017-09-07)

### Bug Fixes

- Default to null height instead of 0 ([faa996c](https://github.com/frontend-collective/react-image-lightbox/commit/faa996c))

See the GitHub [Releases](https://github.com/frontend-collective/react-image-lightbox/releases) for information on previous releases.


text:
---
layout: post
title: "OsSPL3"
description: ""
category: genes
tags: [transcription factor, map-based cloning]
---

* **Information**
    + Symbol: OsSPL3
    + MSU: [LOC_Os02g04680](http://rice.uga.edu/cgi-bin/ORF_infopage.cgi?orf=LOC_Os02g04680)
    + RAPdb: [Os02g0139400](https://rapdb.dna.affrc.go.jp/locus/?name=Os02g0139400)

* **Publication**
    + [OsSPL3, a SBP-Domain Protein, Regulates Crown Root Development in Rice.](http://www.ncbi.nlm.nih.gov/pubmed?term=OsSPL3, a SBP-Domain Protein, Regulates Crown Root Development in Rice.%5BTitle%5D), 2019, Plant Cell.

* **Genbank accession number**

* **Key message**
    + Map-based cloning revealed that lcrn1 is caused by a mutation of a putative transcription factor coding gene OsSPL3 (SQUAMOSA PROMOTER-BINDING PROTEIN-LIKE3)
    + Chromatin immunoprecipitation sequencing assays of OsSPL3-binding sites and RNA-sequencing of differentially expressed transcripts in lcrn1 further identified potential direct targets of OsSPL3 in basal nodes, including a MADS-box transcription factor OsMADS50

* **Connection**
    + __OsMADS50~OsSOC1~DTH3__, __OsSPL3__, [OsSPL3, a SBP-Domain Protein, Regulates Crown Root Development in Rice.](http://www.ncbi.nlm.nih.gov/pubmed?term=OsSPL3, a SBP-Domain Protein, Regulates Crown Root Development in Rice.%5BTitle%5D),  Chromatin immunoprecipitation sequencing assays of OsSPL3-binding sites and RNA-sequencing of differentially expressed transcripts in lcrn1 further identified potential direct targets of OsSPL3 in basal nodes, including a MADS-box transcription factor OsMADS50
    + __OsSPL3__, __OsSPL4__, [CRISPR-based assessment of genomic structure in the conserved SQUAMOSA promoter-binding-like gene clusters in rice](http://www.ncbi.nlm.nih.gov/pubmed?term=CRISPR-based assessment of genomic structure in the conserved SQUAMOSA promoter-binding-like gene clusters in rice%5BTitle%5D),  Expression of OsSPL3 was negatively correlated with that of its closest neighbor in its synteny group, OsSPL4, and its sister paired gene, OsSPL12, in the opposing group

[//]: # * **Key figures**


text:
### Goal in Context

As a user, I want to be able to see the top N populated capital cities in a continent where N is provided by the user.

### Scope

Project.

### Level

Primary task.

### Preconditions

We know the population and location of capital cities and which continent they are on.

### Success End Condition

A report is available for viewing.

### Failed End Condition

No report is produced.

### Primary Actor

User.

### Trigger

A request for populated city in a continent where N is sent by user.

## MAIN SUCCESS SCENARIO

1. User requests report on N populated capital city in a continent where N is given.
2. A report is produced detailing the populated capital and continent .
3. User is given report.

## EXTENSIONS

## SUB-VARIATIONS

None.

## SCHEDULE

**DUE DATE**: Release 1.3

repository: alfiethomasson/SEM-Group-Project

repo_name: alfiethomasson/SEM-Group-Project


text:
# MineSweeper v1.1

This project is a mimic game of the original WindowsXP game minesweeper.

I try to copy all the functions that the old game had, and if possible, make some more functions to make it better.

## Components

Now there's Three Python Scripts in the workspace:

The [BasicRule.py][1] uses basic Python Object Oriented to establish the rules and logic of the game. It's the basic file of the whole project.

The [window.py][2] uses the module PySide2 to create the GUI for the players.

The [main.py][3] is a start program of the game.

Besides, there's another python file [image.py][4]. It contains the photos' data used in the file [window.py][2].

## Run Of the Game

Clicked all the blanks where there's no mine hidden. And the blanks clicked shows the number of the mines besides it.

- Click LeftButton to clear the mine.
- Click RightButton to place a flag which marks the position of the mine.
- Click LeftButton and RightButton together to click all blanks around together. But it cannot work when the flags placed around is not equal to the mines surrounding.

## Collaborators Wanted

The GUI still needs to be improved. Wanted someone good at game UI design to help me.

There are still some functions needing adding, such as the rank and so on.

If you are interested, just join me.

The Photos used are in the directory, too. If you are the author of some photo, you can email me to ask for the pay.

[1]:./BasicRule.py
[2]:./window.py
[3]:./main.py
[4]:./images.py

## Contact

- Email<EMAIL_ADDRESS>

repository: PramSin/minesweeper

repo_name: PramSin/minesweeper


text:
Based on **ANYCUBIC I3 Mega modif extrudeur Flex/TPU** by Iceman51 https://www.thingiverse.com/thing:2264916

## Parts needed
### Stock extruder
* Stepper motor
* Bushing and bolt from idler lever
* Two bolts from the other part
* Pneumatic fitting
* Spring
### BMG clone
* Drive gear (from 5mm axle)
* Idler gear with bearings and axle
## Printing
Use 3-4 walls and >1mm of bottom and top. heat and cooling for good layer adhesion.
Enough rigid infill to make parts strong.
Support idler cavity and bumps for spring.
Maybe it's worth to add modifier (100% infill) covering pneumatic fitting hole?
## Postprocessing
Ream filament path with 2.0-2.5mm drill bit.
Open up filament path in tips (closest to gears) with reamer or drill bit nose to make small conical "guide".
Drill hole for pneumatic fitting so it's tight but doesn't separate layers.
Ream idler lever bushing hole if needed. Bushing must go through.
## Installation
Push idler gear with bearings to idler arm, push axle so it's flush at both ends. Gear down.
Install drive gear to stepper motor axle, don't tighten grub screw yet. Gear towards motor.
Start with idler lever. Put bushing into lever. Using bolt, screw motor, mount and lever together. Don't tighten yet.
Put fixed part on mount, loosely screw the bolt that is further away from spring. Install spring, press levers slightly and loosely screw the last bolt.
When everything looks to be OK, tighten all bolts. Fixed part should be flush with motor and mount.
Using some filament, check the path with the gears. Adjust drive gear height and tighten it. Idler gear should have some play in height so it'll follow.
Install pneumatic fitting. Try if small length of tubing fits in input side, it may need reaming with 4mm drill ;)
## Calibration
Calibrate extruder steps, it should be close to 140 steps/mm. See e.g. https://github.com/davidramiro/Marlin-AI3M/wiki/Calibration#extruder-steps
If needed, adjust extruder feedrate and retraction acceleration (M203 and M204, see https://github.com/davidramiro/Marlin-AI3M#after-obtaining-the-hex-file). Values should be closer to stock extruder (M203 E60, M204 R10000.00 ???) than Titan (M203 E30, M204 R1500.00)

**NB!** I have 2208 drivers on X, Y, Z and Z (E1). Extruder is running with stock driver because people have had trouble with 2208. I have no idea what voltage E0 should have :/

## Reasoning
### Stock extruder
* easy to release filament
* filament path is fairly generous
* gear is meh
* even using hob-goblin gear would require printing new fixed part
* can be fitted with knob to run filament manually, otherwise not possible at all
### Titan clone (Trigorilla)
* works
* slips easilly
* curved filament sometimes has hard times to go to tube or sticks to something in bowden fitting
* bowden fitting maybe has smallest opening in filament path, so pulling filament often stucks there (-> remove tube, cut tip of filament, remove filament, attach tube)
* manually running filament is difficult
### BMG clone
* was too tight, one layer of electrical tape between boby halves made gears run easilly
* filament path is too tight, even if lever is "released", it's hard to move
* filament does not want to find the hole it should go from gears. Due to structure it's hard to fix
* lever is bad. Nothing to pull it against, short spring means it's tight
* nice gears, good grab of filament

repository: KimmoHop/valve-extruder-knob

path: /DG Turhapuuro/README.md

repo_name: KimmoHop/valve-extruder-knob


text:
# [Groups]

Groups is an exam done using Ruby on Rails in less than 2 hours. Feautures login/registration and users can create groups which others may join. Created by [Leilani Raranga](https://github.com/Leilaniann) for [Coding Dojo](http://codingdojo.com) Black Belt Exam.

## Quick start

1. Install Rails at the command prompt if you haven't yet:

        $ gem install rails

2. Change directory to `groups` and start the web server:

        $ cd groups
        $ rails server

   Run with `--help` or `-h` for options.

3. Using a browser, go to `http://localhost:3000`

4. Follow the guidelines to help launch application
    * [Getting Started with Rails](http://guides.rubyonrails.org/getting_started.html)
    * [Ruby on Rails Guides](http://guides.rubyonrails.org)
    * [The API Documentation](http://api.rubyonrails.org)
    * [Ruby on Rails Tutorial](http://www.railstutorial.org/book)

## Creator

**Leilani Raranga**

* <https://twitter.com/leilanirar>
* <https://github.com/leilaniann>

## Copyright and license

Copyright © 2016, [Leilani Raranga](http://github.com/leilaniann). Released under the [MIT license](https://github.com/helpers/helper-copyright/blob/master/LICENSE).

Video of site can be found at : https://vimeo.com/142698620

repository: LeilaniAnn/groups

repo_name: LeilaniAnn/groups


text:
# Nuxt.js - Vue.js on Steroids
This is the code repository for [Nuxt.js - Vue.js on Steroids](https://www.packtpub.com/application-development/unsupervised-clustering-mesos-integrated-course?utm_source=github&utm_medium=repository&utm_campaign=9781788479677), published by [Packt](https://www.packtpub.com/?utm_source=github). It contains all the supporting project files necessary to work through the video course from start to finish.
## About the Video Course
This course will take you on a journey where you'll you will learn to build highly engaging Vue.js apps with Nuxt.js. Nuxt adds easy server-side-rendering and a folder-based config approach. Vue.js is an amazing JavaScript framework which you can use to build highly engaging user interfaces and single.- page applications. You'll master all the details in this course but the most important takeaway is that Nuxt.js makes creating better, more optimized, and more capable Vue apps much easier—and all of that while adding pretty much no overhead. You'll learn how to create Nuxt/ Vue apps from scratch! You'll build an entire course project and dive into the core features Nuxt.js offers. By the end of the course, you'll have a complete Vue app, built with Nuxt.js, which can be rendered on the server (or as a static website!) and which is highly optimized.

What You Will Learn

Get familiar with Inference matroids

Learn graph isomorphism

Learn how to perform granular synthesis with druid streams

Understand how to write a custom isolator module for Mesos

Learn to perform MCMC anomaly detection

Get introduced to RoBo

Learn to manifold the cluster trees

Understand what is Pythonic Clojars and Monads

Learn what is Actor Dining Model and port mappings

Learn how to perform cluster autoscaling

## Instructions and Navigation
### Assumed Knowledge
To fully benefit from the coverage included in this course, you will need:

This course is designed for people who want to build engaging, (optionally) server-side-rendered Vue.js apps, those who want to work with Vue.js and follow a minimal-configuration approach, and for those who want to create static websites with Vue.js (with Nuxt as a static page generator!).
### Technical Requirements
This course has the following software requirements:

## Related Products
* [Hands-On Penetration Testing with Metasploit [Video]](https://www.packtpub.com/application-development/unsupervised-clustering-mesos-integrated-course?utm_source=github&utm_medium=repository&utm_campaign=9781788479677)

* [Layout and Constraints on Android [Video]](https://www.packtpub.com/application-development/unsupervised-clustering-mesos-integrated-course?utm_source=github&utm_medium=repository&utm_campaign=9781788479677)

* [Unsupervised Clustering in Mesos [Integrated Course]](https://www.packtpub.com/application-development/unsupervised-clustering-mesos-integrated-course?utm_source=github&utm_medium=repository&utm_campaign=9781788479677)


text:
Slider
======

A "simple" sliding puzzle game. Written in Rust as an exploration on how to build a tiling game engine.

Version 0.5: Minimum Viable Product
-----------------------------------

This tagged version does not use OpenGL, Piston, or any other graphics library. It is an implementation of a slider puzzle, and includes the following features:

1. Only allows a 4x4 puzzle grid.
1. Takes an optional seed value (any usize value) using the `--seed` argument from the command line to always produce the same shuffle pattern.
1. Takes an optional interation value (any positive usize value) using the `--iterations` argument from the command line to determine the number of moves made by the shuffle routine.
1. If the optional seed value is not supplied, the random number generator used to power the shuffle algorithm is supplied from a random system source.
1. If the iteration value is not supplied, the shuffle algorithm defaults to ten shuffle moves.
1. A parser is implemented to take keyboard input to either move a tile (implemented as a number displayed in a grid) or the command `quit` to quit the game.
1. The number of legal moves is tracked and read out at the end of the game (quit or win).


text:
# The "collectstoweb" command. <!-- omit in TOC -->

- [1. Overview](#1-overview)
- [2. Features](#2-features)
- [3. Limitations](#3-limitations)
- [4. Usage](#4-usage)
- [5. Configuration file format](#5-configuration-file-format)
  - [5.1. questsfile](#51-questsfile)
  - [5.2. itemdbloc](#52-itemdbloc)
  - [5.3. htmlout](#53-htmlout)
  - [5.4. htmltitle](#54-htmltitle)
  - [5.5. htmlintro](#55-htmlintro)
  - [5.6. houses](#56-houses)
- [6. Future enhancements](#6-future-enhancements)
- [7. Adding new quests](#7-adding-new-quests)
- [8. Downloading and installation](#8-downloading-and-installation)

## 1. Overview

The "collectstoweb" command is designed to assist in managing collection
items stored in houses. This takes the unorganized real estate dump and creates
an HTML page with the counts organized by a hierarchy of expansion, zone and
quest. This can be useful if offering these up to others such as a guild,
having joint management among a group of friends, or even just for personal use
by alts.

The implemented features were the ones that were useful in my specific case.  I
had gathered collection quest items over the years and made them available to
guild members upon request. Collection items are non-placeable, so can only be
**stored** in a house. At the time this was first written, the largest house
could only hold 300 non-placeable items. While a couple special crates could
hold an additional 100 or 200 non-placeable items, these were ignored so there
was only one place to store in a house. This made putting things in simpler.

It supports a note for each quest. This was useful for giving hints as to where
in a zone or what mobs dropped items for that quest. Some people never
requested items, but did bookmark the posted HTML just for quick info on where
to farm them. The program is data-driven so can be configured as to which
houses hold which quests. The note mentioned above is also from a data-driven
file. A customized title and additional information can be added to the HTML
page via the main configuration file.

In addition to building the HTML page, this will print out messages when
multiple stacks of an item are in a house or if items other than the ones for
the configured quests are stored in the house. There are a limited number of
stacks that can be stored in a house. Multiple stacks could exist for two
reasons. First, if you have over 100 of an item, a second stack would be made.
The second reason is that if multiple people are placing items into the house,
it could end up with partial stacks tagged with two different owners.
Personally, I dropped anything over one stack on the ground.  Also, I used to
allow some officers in a previous guild to organize stuff in the house and the
multiple stack method let me know that I had stacks to combine.

## 2. Features

- Houses can be configured as holding quest items for an expansion.
- Houses can be configured as holding quest items for zones in an expansion.
  (This was supported as Rain of Fear has more than 300 collection items.)
- Title and information to be added at the beginning of the output can be
  configured.
- Reports when multiple stacks of a collection item are in a house.
- Reports when there are stored items in a house that are not from the
  configured collections.

## 3. Limitations

Some limitations here are due to just meeting my use case.

- This does not support splitting quests from a zone into multiple houses. The
  same zone can be configured for multiple houses but all quests for that
  zone will be listed for both houses. This would have been more complicated
  code and it was easy enough to have alts get more houses.
- The current code only mentions if extra items were stored in a house. It
  doesn't state whether they are collection items, and if so, in which house
  they should have been.
- Names that have not been collected for items show up as "???" for their name.
  Items that are in the houses will have a name along with those that have been
  seen previously or have been collected with the
  ["updateitemdb"](./updateitemdb.md) program.

## 4. Usage

The usage is very simple once the [configuration](#configuration-file-format)
is set up properly.

The program has a "conf" argument that must be present and point to the
configuration file to use. If the program is installed in your PATH, the
command is simply the following:

collectstoweb -conf PATH-TO-CONFIG-FILE

Example:

collectstoweb -conf /Users/Nuttann/Eq/conf/collections_conf.yml

As usual, use quotes where necessary if the paths used have spaces.  You can
also set up a desktop shortcut to do this. If you use a shortcut, set it so
that the window does not disappear automatically when done.  Otherwise, you
will miss any messages that are printed. You may also want multiple
configuration files to switch between such as when you are doing this on
multiple servers.

## 5. Configuration file format

See the configuration file in "samples/collection_conf.yml" for an example.
There are brief comments in that file and sample entries. A detailed
description is given here.

### 5.1. questsfile

This should point to the file containing all the quest info. See [Downloading and
Installation](./downloading.md) for more information this file.

### 5.2. itemdbloc

This "Item Database Location" should point to the location of the database. The
current code only supports a YAML file as the database. The amount of data is
small enough that the YAML version works fine. See [Downloading and
Installation](./downloading.md) for more information this file.

### 5.3. htmlout

This parameter indicates the path of where to write the output file. This file
will be created if it doesn't exist and will be overwritten if it does exist.

### 5.4. htmltitle

This parameter holds the text to display as the page title and also the main
header. HTML-specific characters such as '&' will be escaped, so text here
should appear verbatim in a browser.

### 5.5. htmlintro

This parameter holds the **RAW** HTML to place into the final HTML document
verbatim after the HTML title/header and before the listing of the house
contents. This is to support any HTML markup or links to any instructions or
such that should be included. I had used a link with a sample request and
instructions to explain why the information to put in a request was really
useful to me when pulling things out.

### 5.6. houses

This parameter is the most complex of the configuration parameters. It is a
nested YAML definition. YAML uses indenting for the nesting and special syntax
for definitions and lists. There are times when double quotes will be necessary
or YAML will not parse the data as the user intended. The sample file has a
good example of some of the necessary things. If the parser complains and the
indentation looks fine, try adding double quotes around the definition. It may
contain a special character that you are unaware of.

You can search on the web for YAML specifications.  The following is a summary
of stuff that exists in the sample.

- Key-value pairs are defined by "key: value" there is a required space after
  the ':'.
- Indentation defines nesting.
- A "- " at the beginning indicates an array element.
- A "#" at the beginning of the line or after whitespace indicates the rest of
  the line is a comment.

The basic nesting is as follows:

```YAML
# houses is the root element of the housing configuration. It holds an array
# of house configurations.
houses:
  # The '-' before fname means this is an array element. The first field in the
  # array is fname, property is indented the same as fname, so is the second field,
  # and contents is also indented the same so is the 3rd field.
  - fname: "C:/Users/Public/Daybreak Game Company/Installed Games/Everquest/Nuttann_cazic-RealEstate.txt"
    property: "Return of the Exiled Village II, 113 Vanward Street, Bixie Hive House"
    expansions: # This case is the same as above. The value below is an array of expansions.
      # Each expansion has a name and an OPTIONAL array of zones.
      - name: Rain of Fear
        # The zones attribute exists for this expansion, so only quests from those zones
        # are included.
        zones:
          - Multi-zone
          - Shard's Landing
          - East Wastes, Zeixshi-Kar's Awakening
          - Kael Drakkel, The King's Madness
          - Crystal Caverns, Fragment of Fear
          - Evantil, the Vile Oak
          - Breeding Grounds
          - Chapterhouse of the Fallen
          - Grelleth's Palace, Chateau of Filth

  - fname: "C:/Users/Public/Daybreak Game Company/Installed Games/Everquest/Nuttann_cazic-RealEstate.txt"
    address: "Return of the Exiled Village II, 111 Vanward Street, Evantil's Abode"
    expansions: # This house has two expansions (RoF and the pseudo-expansion Periodic)
      - name: Rain of Fear
        zones:
          - Valley of King Xorbb
          - Chelsith Reborn
          - Plane of Shadow
          - Heart of Fear
      - name: Periodic
        # No zones listed, so all zones for this "pseudo-expansion" are included.

  - fname: "C:/Users/Public/Daybreak Game Company/Installed Games/Everquest/Nuttann_cazic-RealEstate.txt"
    address: "Return of the Exiled Village II, 112 Vanward Street, Bixie Hive House"
    contents:
      - name: Call of the Forsaken
        # No zones listed, so all CotF zones are included.
```

## 6. Future enhancements

Many of the limitations were due to just meeting my personal needs. There are
some things that could be done to make this more useful. Requests for any of
these or other features may motivate me to work on them.

Possible future work:

- Report when a configured house does not appear in the configured real-estate
  dump. This should help detect mismatched names.
- Report whether stored items in a house that don't belong to the configured
  quests to that house are colection items or not.
- Allow substring of address to be used.  Some currently include house type.
  If this is added, try and report if this matches multiple houses in a file.
- If a collection item is in a wrong house, report which house it should be in.
- Add feature to search bags for collection items and list which house they
  should should be placed in. (An older Python program I wrote used to do this
  for me and it made it quicker to drop items into the proper house.)
- Possibly add a configuration item to omit certain reports such as extra
  non-collection items stored in a house. (The houses that I used for
  collections only contained collection items as I was reserving space for one
  stack per item. I used separate houses for non-collection items.)
- Add a configuration item to send output messages to a log file instead of the
  terminal.

## 7. Adding new quests

Start with the eqdata repository. The README file in the
[eqdata](https://github.com/nuttann/eqdata) repository explains the format and how
to enter new data for the collection_quests.yml file.

## 8. Downloading and installation

See the [Downloading and Installation](./downloading.md) document for instructions.

repository: nuttann/equtils

repo_name: nuttann/equtils


text:
# Customers

## The customer object

> Example Response

```json
{
    "id": "55e5e7ad0f95d30e001c3470",
    "type": "customers",
    "attributes": {
        "customer-id": "2C0BA915-BBC0-459A-98FA-9C3340A361CC",
        "name": "John McRover",
        "email"<EMAIL_ADDRESS>        "traits": {
            "gender": "male",
            "annual-salary": 65000,
            "vip": true
        },
        "device": "iPhone6,1",
        "first-visited-at": "2015-08-01T11:00:15.000Z",
        "last-visited-at": "2015-09-22T18:53:44.000Z",
        "operating-system": "iPhone OS",
        "os-version": "8.4",
        "sdk-version": "0.30.8"
    },
    "relationships": {
        "last-visited-location": {
            "data": {
                "id": "551b37390fabf0c6e6001138",
                "type": "locations"
            }
        },
        "visited-organizations": {
            "data": [
                {
                    "id": "551b37390fabf0c6e6001131",
                    "type": "organizations"
                }
            ]
        }
    }
}
```

The customer object represents a user of your app. Customer's can be identified by a unique ID, name and email. You can also attach additional proprietary information to your customers to be used for segmentation and customization.

### Attributes

attribute        | type   | description
---------------- | ------ | -----------
customer-id      | string | A unique identifier for the customer. This is in-addition-to the `id` property found on all resource objects. You can supply the `customer-id` property yourself through the SDK or through this API. Often this is done to link customer data to one of your exisiting systems. If you do not supply a value for the `customer-id` property, a generated UUID will be used.
name             | string | The full name of the customer.
email            | string | The email address of the customer.
traits           | object | An object of key/value pairs that add additional information about the customer. These traits can be used to segment and customize the content delivered to your customers.
device           | string | The model name of the customer's device. The Rover SDK detects the customer's device and supplies the value for this property automatically.
operating-system | string | The operating system of the customer's device. I.e. iOS or Android. The Rover SDK detects the customer's device and supplies the value for this property automatically.
os-version       | string | The operating system version of the customer's device. The Rover SDK detects the customer's device and supplies the value for this property automatically.
sdk-version      | string | The version of the Rover SDK the customer is running. The Rover SDK supplies the value for this property automatically.
first-visited-at | date   | The first time the customer visited any of your locations.
last-visited-at  | date   | The last (most recent) time the customer visited one of your locations.

### Relationships

relationship          | descipription
--------------------- | -------------
last-visited-location | The last location the customer visited.
visited-organizations | A list of organizations the customer has visited. An organization will appear in this list after a customer visits one of the locations belonging to the organization.

## List all customers

> Definition:

```shell
GET https://api.roverlabs.co/ext/v1/customers
```

> Example Request:

```shell
$ curl https://api.roverlabs.co/ext/v1/customers \
   -u 23423588ab2c5c28562cdb3d74fa596c:
```

> Example Response:

```json
{
    "links": {
        "prev": "https://api.roverlabs.co/ext/v1/customers?page[limit]=50&page[offset]=3",
        "next": "https://api.roverlabs.co/ext/v1/customers?page[limit]=50&page[offset]=5"
    },
    "data": [
        {
            "id": "55e5e7ad0f95d30e001c3470",
            "type": "customers",
            "attributes": {
                "customer-id": "2C0BA915-BBC0-459A-98FA-9C3340A361CC",
                "name": "John McRover",
                "email"<EMAIL_ADDRESS>                "traits": {
                    "gender": "male",
                    "annual-salary": 65000,
                    "vip": true
                },
                "device": "iPhone6,1",
                "first-visited-at": "2015-08-01T11:00:15.000Z",
                "last-visited-at": "2015-09-22T18:53:44.000Z",
                "operating-system": "iPhone OS",
                "os-version": "8.4",
                "sdk-version": "0.30.8"
            },
            "relationships": {
                "last-visited-location": {
                    "data": {
                        "id": "551b37390fabf0c6e6001138",
                        "type": "locations"
                    }
                },
                "visited-organizations": {
                    "data": [
                        {
                            "id": "551b37390fabf0c6e6001131",
                            "type": "organizations"
                        }
                    ]
                }
            }
        },
        {...},
        {...}
    ]
}
```

You can see a list of all the customers belonging to your account. Customers are always sorted by the last time they visited one of your locations. You can use this API method with the `page` parameter. See [Pagination](#pagination) for details.

repository: lpmorin/slate

repo_name: lpmorin/slate


text:
# Storage Package for Laravel 4

Storage is a filesystem abstraction layer for Laravel 4 applications.
If you are using Laravel 5 it comes with a similar package included
which can be [found in the docs](https://laravel.com/docs/5.0/filesystem).

## Installation via Composer

Add this to you composer.json file, in the require object:

```javascript
"dmyers/laravel-storage": "1.*"
```

After that, run composer install to install Storage.

Add the service provider to `app/config/app.php`, within the `providers` array.

```php
'providers' => array(
    // ...
    'Dmyers\Storage\StorageServiceProvider',
)
```

Add a class alias to `app/config/app.php`, within the `aliases` array.

```php
'aliases' => array(
    // ...
    'Storage' => 'Dmyers\Storage\Storage',
)
```

Finally, ensure the files directory defined in the config file is created
and writable by the web server (defaults to public/files).

```console
$ mkdir public/files
$ chmod -R 777 public/files
```

## Configuration

Publish the default config file to your application so you can make modifications.

```console
$ php artisan config:publish dmyers/laravel-storage
```

## Usage

Check if a file exists in storage:

```php
Storage::exists('user/avatar.jpg');
```

Get a file's contents from storage:

```php
Storage::get('user/avatar.jpg');
```

Put a file into storage:

```php
Storage::put('user/avatar.jpg', $contents);
```

Upload a file into storage:

```php
Storage::upload(Input::file('avatar'), 'user/avatar.jpg');
```

Upload a remote file into storage:

```php
Storage::remoteUpload('http://laravel.com/favicon.ico', 'user/avatar.jpg');
```

Download a file from storage:

```php
Storage::download('user/avatar.jpg', 'tmp/images/user-1/avatar.jpg');
```

Download a remote file locally:

```php
Storage::remoteDownload('http://laravel.com/favicon.ico', 'tmp/images/user-1/avatar.jpg');
```

Delete a file from storage:

```php
Storage::delete('user/avatar.jpg');
```

Move a file in storage:

```php
Storage::move('user/avatar.jpg', 'user/1/avatar.jpg');
```

Copy a file in storage:

```php
Storage::copy('user/avatar.jpg', 'user/avatar.bak.jpg');
```

Get a file's type from storage:

```php
Storage::type('user/avatar.jpg');
```

Get a file's mime type from storage:

```php
Storage::mime('user/avatar.jpg');
```

Get a file's size from storage:

```php
Storage::size('user/avatar.jpg');
```

Get a file's last modification date from storage:

```php
Storage::lastModified('user/avatar.jpg');
```

Check if a path is a directory in storage:

```php
Storage::isDirectory('user/avatar.jpg');
```

List all files in storage:

```php
Storage::files('images');
```

Get the full URL to a file in storage:

```php
Storage::url('user/avatar.jpg');
```

Render a file from storage to the browser:

```php
Storage::render('user/avatar.jpg');
```

repository: dmyers/laravel-storage

gha_language: PHP

repo_name: dmyers/laravel-storage


text:
---
layout: post
title:  Optimistic Realtime Scheduler
category: feature
---

The realtime scheduler is a new optimistic scheduling option for ROSS, invoked through `--synch=5`.
During this scheduler, GVT intervals are trigged based on the amount of time elapsed (rather than the number of event which have been processed).
For models that see minimal speedup during regular optimistic simulation, or models where there is a known load imbalance, the optimistic realtime scheduler may lead to increased performance.

## Parameters

The realtime scheduler depends on two parameters:

- GVT-Interval:

  This is the specified amount of *time*, measured in milliseconds, between GVT phases.
  **NOTE**: this is now an overloaded parameter.
  During regular optimistic simulation (or conservative simulation), the GVT-interval specifies the number of events to processed between GVT phases.
- Clock Rate:

  This is the clock rate of the underlying hardware.
  Knowing the actual clock rate of the hardware is necessary to calculate the amount of time which has elapsed.

## Usage

| Command Line Option | Global Variable | Meaning |
|-----
| `--synch=5` | `g_tw_synchronization_protocol = OPTIMISTIC_REALTIME` | Simulation will be performed using the Optimistic Realtime Scheduler |
| `--gvt-interval=5` | `g_tw_gvt_interval = 5` | Number of milliseconds between GVT phases |
| `--clock-rate=3600000000` | `g_tw_clock_rate=3600000000` | Clock rate of underlying hardware |

## History

This feature was initially proposed in [Pull Request #79](https://github.com/ross-org/ROSS/pull/79).
It was eventually merged into the master branch in [commit fd476a](https://github.com/ross-org/ROSS/commit/fd476afd48204022928cfec85935720c2d25f719).

gha_language: CSS


text:
<!-- First ensure you installed the latest version of fs-extra -->
<!-- If your bug still exists please fill out the following information if it applies to your issue: -->
<!-- Please check if you have installed a supported version of Node.js as written in "engines" in the package.json -->
- **Operating System:**
- **Node.js version:**
- **`fs-extra` version:**

repository: jprichardson/node-fs-extra

repo_name: jprichardson/node-fs-extra


text:
## Course information
* [Course Outline](./Course-Outline)
* Overarching Learning Goals (see Course Outline)
* [Due Dates and Submission Details](./Due-Dates-and-Submission-Details)
* [Pre-Course Work](./Pre-Course-Work)

#### 📙 Electronics
* [Hardware - Presentation Preparation](./Hardware-Components-Presentation)
* [Hardware - Assessment and Presentation](./Hardware-Components-Assessment)
* Electronics - Labs (A)\^
* Electronics - Labs (Initial Safety)\^
* Electronics - Labs (Build)\^
* Electronics - Labs (Soldering Safety)\^
* Electronics - Labs (Soldering)\^
* Electronics - Summative Project (subject to change)

\^ - See Google Classroom

#### 📘 Data and Logic
* [Computer Data Representation](./Computer-Data-Representation)
* [Gates and Tables](./Gates-and-Tables)
* Micro:bits - Labs
* Micro:bits - Summative Project

#### 📗 Citizenship
* [Skills](./Skills)
* [Careers, Society, Ethics, and the Environment](./Careers-Society-Ethics-Environment)

repository: mrseidel-classes/archives

repo_name: mrseidel-classes/archives


text:
# README #

### What is this repository for? ###

Fusion is a tool for setting up environments for Continuous Deployment with BitBucket and Azure.

### How do I get set up?  ###

* Ferhat Yildiz <ferhat.yildiz@turingts.com>

repository: ferhaty/fusion

repo_name: ferhaty/fusion


text:
# GIT

## Init new repository
Create a new repository on the command-line (file README.md is already created)
```
$ git init
$ git add README.md
$ git commit -m "first commit"
$ git remote add origin repoUrl
$ git push -u origin master
```

## Basic Branching
Create a branch
```
$ git branch feature_branch_name
```

Switch to an existing branch
```
$ git branch feature_branch_name
$ git checkout feature_branch_name
```

Create and switch to a new branch
```
$ git checkout -b feature_branch_name
```

To push remote the locally created branch
```
$ git push -u origin feature_branch_name
```

To push all branches
```
$ git push --all origin
```

To list existing branches
```
# remote + local branches
$ git branch -a

# remote only
$ git branch -r
```

To cache the credentials (it should work only with https connectors):
```
git config --global credential.helper 'cache --timeout 3600'
```

Delete all local unstaged file/directory and revert modified unstaged files:
```
git clean -df
git checkout -- .
```

Delete local branches no longer on remote:
```
git remote prune origin
```

Set the local author and email for a repository:
```
git config user.email<EMAIL_ADDRESS>git config user.name "My Name"
```
If you add the flag --global then it modifies your global config.

## Merge

Merge a branch without fast-fastword and without autocommit
```
git merge <branchName> --no-commit --no-ff
```

Merge using the --squash option, all of the commits made on branch B will be "lumped together" and merged as a single commit.

The easy way of squashing all the commits performed in a topic branch is:
```
git reset referenceReleaseBranch
```

repository: ufoscout/freestyle-it-notes

repo_name: ufoscout/freestyle-it-notes


text:
# contributing

## Contributing

New contributions to the library are welcome, but we ask that you please follow these guidelines:

* Use tabs for indentation, not spaces.
* Only change the individual files in `/src`.
* Check that your code will pass `linting` code standards, `yarn lint` will run this for you.
* Check that your code will pass tests, `yarn test` will run tests for you.
* Keep pull requests concise, and document new functionality in the relevant `.md` file.
* Consider whether your changes are useful for all users.
* Avoid breaking changes unless there is an upcoming major release, which are infrequent. We encourage people to care a lot about backwards compatibility.

## Building and Testing

TODO

## Bugs and Issues

Please report these on the GitHub page - at [github.com/kresst/kresst](https://github.com/kresst/kresst). Please do not use issues for support requests. For help using kresst, please take a look at the [`kresst`](http://stackoverflow.com/questions/tagged/kresst) tag on Stack Overflow.

Well structured, detailed bug reports are hugely valuable for the project.

Guidelines for reporting bugs:

* Check the issue search to see if it has already been reported
* Isolate the problem to a simple test case

Please provide any additional details associated with the bug, like if it only happens with a certain configuration or data.

repository: kresst/kresst

repo_name: kresst/kresst


text:
# Rebranding !!
Our test-utils becomes selenium-utils!

We want to build more libs based on Selenium Core.
Currently we have integration for BrowserStack and in the future we plan new lib for easier testing of DotVVM apps.

Unfortunatly, this brings some breaking changes.

##Breaking changes:
- namespace `Riganti.Utils.Testing.SeleniumCore` changed to `Riganti.Utils.Testing.Selenium.Core`
- namespace `Riganti.Utils.Testing.SeleniumCore.BrowserStack` changed to `Riganti.Utils.Testing.Selenium.BrowserStack`

# selenium-utils
**The purpouse of this framework is to make UI testing much more easier and cheaper.**
Framework is based on selenium wrappers and principles which canopy uses.

Creation of tests full of Assert.AssertationFunc() was not acceptable for us. These tests usualy become very hard to read even it checks simple case.

To simplify testing and reading of these tests we are using `CheckIfSomething` functions.

These functions throws meaningful exceptions when something goes wrong. The exceptions usualy contains informations about css selector of element, expected value and provided value etc.

## configuration
All critical settings are configurable in app.config. You can easily change your configuration of tests by changing of app.config via XML transformation. This provides you the possibility of creation specific configuration for your CI servers.

All settings starts with `<add key="selenium:_configurationKey_" value="" />`

This make you able to define how many times the test is retried in case of failure, baseurl of relative urls, what browsers should be tested, logging etc.


text:
# LRG-Fundamentals
Official LRG Fundamentals Arma 3 Mod.

This is the Arma 3 mission-making framework created by Last Resort Gaming. LRG Fundamentals allows the easy creation of modded missions
for Arma 3.

## Setting up and Building

Create a directory called `z` on the P: drive. Clone the repository into the subdirectory `LRG Fundamentals` such that the folder `addons` is located in the following path:

```P:\z\LRG Fundamentals\addons```

Using [pboProject][pboproj] by Mikero, set the source directory to the `addons` directory, and the destination to e.g. `P:\@LRG Fundamentals`. The private key is required to build properly signed pbos for distribution, this key is only available to members of the LRG Development Team.

If you have questions about the build process or encounter issues, please let us know via a message on [Discord][discord] or by submitting an issue ticket here.

[pboproj]:https://mikero.bytex.digital/api/download?filename=pboProject.<IP_ADDRESS>.Installer.exe
[discord]:http://discord.lastresortgaming.net

gha_language: SQF


text:
# Use a plugin

## Date

The Streamy Date plugin provides components to manipulate date.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-date" % StreamyVersion
)
```

## Elasticsearch

The Streamy Elasticsearch plugin provides components integration for Elasticsearch.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-elastisearch" % StreamyVersion
)
```

### ??? documents from a single query

## Fingerprint

The Streamy Fingerprint plugin provides components to generate fingerprint.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-fingerprint" % StreamyVersion
)
```

## Graphite

The Streamy Graphite plugin provides component integration for Graphite.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-graphite" % StreamyVersion
)
```

## Json

The Streamy Json plugin provides components to manipulate json.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-json" % StreamyVersion
)
```

## Mutate

The Streamy Mutate plugin provides component to easily mutate events.

## Protobuf

The Streamy Protobuf plugin provides component integration for Protobuf.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-protobuf" % StreamyVersion
)
```

## Riemann

The Streamy Riemann plugin provides components integration for Riemann.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-riemann" % StreamyVersion
)
```

## Syslog

The Streamy Syslog plugin provides component integration for Syslog.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-syslog" % StreamyVersion
)
```

## Tcp

The Streamy Tcp plugin provides component integration for Tcp.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-tcp" % StreamyVersion
)
```

## Xymon

The Streamy Xymon plugin provides component integration for Xymon.

### Artifacts

```scala
val StreamyVersion = "0.13.0"

libraryDependencies ++= Seq(
  "io.techcode.streamy" %% "streamy-plugin-xymon" % StreamyVersion
)
```

repository: amannocci/streamy

gha_language: Scala

repo_name: amannocci/streamy


text:
# YahooFinance

YahooFinanace is used to access Yahoo Finance to retrieve Stock quote data.
You can retrieve a standard quote, real time quote or historical data.

To get standard data call get_standard_quotes and pass a single symbol, a
comma separated string of symbols or a list of symbols.

To get a realtime quote call get_realtime_quotes and pass a single symbol, a
comma separated string of symbols or a list of symbols.

To get historical data call get_historical_quotes and pass a number of days
to go backwards. Or, call get_historical_quotes_using_dates and pass a start
date and an optional end date.

repository: mindreframer/elixir-stuff

repo_name: mindreframer/elixir-stuff


text:
## About

Deol.nvim is a dark powered shell for Neovim.
It is based on neovim or Vim terminal feature.

## Requirements

deol requires Neovim or terminal feature enabled Vim