text:
# MaterialSpinner
[![Android Arsenal](https://img.shields.io/badge/Android%20Arsenal-MaterialSpinner-brightgreen.svg?style=flat)](http://android-arsenal.com/details/1/1720)

Spinner with Material Design

This library provides you a Spinner with the Material style. You can use it like any regular Spinner.
Add floating label text, hint and error messages.

## Screenshots
![MaterialSpinner](./screenshots/screenshot.gif)

## Gradle Dependency
Use this dependency in your build.gradle file to reference this library in your project

```groovy
compile 'com.github.ganfra:material-spinner:2.0.0'
```

If you use other libraries requiring appcompat-v7 like [MaterialEditText](https://github.com/rengwuxian/MaterialEditText/) make sure to exclude them if you have issue at compile time :
```groovy
compile ('com.github.ganfra:material-spinner:2.0.0'){
        exclude group: 'com.android.support', module: 'appcompat-v7'
}
```

## Thanks

Many thanks to Matías Dumrauf to help me supporting this library!

## Usages

In the xml :

```xml
<fr.ganfra.materialspinner.MaterialSpinner
        android:id="@+id/spinner"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        app:msp_multiline="false"
        app:msp_dropDownHintView="@layout/my_custom_dropdown_hint_item_layout"
        app:msp_hintView="@layout/my_custom_hint_item_layout"
        app:msp_hint="hint"
        app:msp_enableFloatingLabel="false"
        app:msp_enableErrorLabel="false"
        app:msp_floatingLabelText="floating label"
        app:msp_baseColor="@color/base"
        app:msp_highlightColor="@color/highlight"
        app:msp_errorColor="@color/error"
        app:msp_typeface="typeface.ttf"
        app:msp_thickness="2dp"
        app:msp_hintColor="@color/hint"
        app:msp_arrowColor="@color/arrow"
        app:msp_arrowSize="16dp"
        app:msp_alignLabels="false"
        app:msp_floatingLabelColor="@color/floating_label"/>
```
You can set a hint and a floating label text. If no floating label text is provided, the hint will be set instead.

Java side, you use it like a regular spinner, setting an adapter to it.
```java
 String[] ITEMS = {"Item 1", "Item 2", "Item 3", "Item 4", "Item 5", "Item 6"};
 ArrayAdapter<String> adapter = new ArrayAdapter<String>(this, android.R.layout.simple_spinner_item, ITEMS);
 adapter.setDropDownViewResource(android.R.layout.simple_spinner_dropdown_item);
 spinner = (MaterialSpinner) findViewById(R.id.spinner);
 spinner.setAdapter(adapter);
```

If you need to set an error message, you can do it the same way than with an EditText :
```java
 //Activate
 spinner.setError("Error");
 //Desactivate
 spinner.setError(null);
```
You can choose to have a scrolling animation or to set the error message on multiple lines with the "msp_multiline" attribute in xml (default is true).

## License

    Copyright 2017 François Ganard

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

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

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

repository: codedevote/MaterialSpinner

repo_name: codedevote/MaterialSpinner


text:
Loopback example
----------------

### Build hardware

##### Dependencies:
* Vivado 2017.4

##### Steps
* Run `vivado -mode batch -source ./create_project.tcl` from the command line
* Open Vivado project in ./vivado\_loopback
* Generate bitstream through Vivado
* Program the FPGA using the Vivado Hardware Server

### Build Software

##### Dependecies
* GCC >= 5.0
* The VerCoLib-PCIe Linux driver, see [the driver Readme](../../software/linux_driver/README.md) for build instructiions.

##### Steps
* Do either of these steps:
  * Create udev rules such that the FPGA running the loopback bitfile is called `fpga_1` and all channels are called `fpga_1_<tx|rx>_<id>`.
  * Change the `'/dev/fpga_1_tx_2'` and '`/dev/fpga_1_rx_1'` filenames in [`software/loopback.cpp`](./software/loopback.cpp) to reflect the device files on your system.
* Run `make` in [./software](./software).
* Run the executable `loopback` in ./software.

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
# deployer.composer

![Packagist Version](https://img.shields.io/packagist/v/codenamephp/deployer.composer)
![Packagist PHP Version Support](https://img.shields.io/packagist/php-v/codenamephp/deployer.composer)
![Lines of code](https://img.shields.io/tokei/lines/github/codenamephp/deployer.composer)
![GitHub code size in bytes](https://img.shields.io/github/languages/code-size/codenamephp/deployer.composer)
![CI](https://github.com/codenamephp/deployer.composer/workflows/CI/badge.svg)
![Packagist Downloads](https://img.shields.io/packagist/dt/codenamephp/deployer.composer)
![GitHub](https://img.shields.io/github/license/codenamephp/deployer.composer)

## What is it?

This package adds deployer tasks and a command factory for running composer on the command line.

## Installation

Easiest way is via composer. Just run `composer require codenamephp/deployer.composer` in your cli which should install the latest version for you.

## Usage

Just use the built in tasks in your deployer file or create your own by using the command factory and a command runner or just
extend `\de\codenamephp\deployer\composer\task\AbstractComposerTask`

branch_name: refs/heads/release

gha_language: PHP


text:
---
title: Support Out-of-Tree Azure Cloud Provider
authors:
  - "@andrewsykim"
  - "@dstrebel"
  - "@feiskyer"
owning-sig: sig-cloud-provider
reviewers:
  - "@dstrebel"
  - "@justaugustus"
  - "@khenidak"
  - "@feiskyer"
approvers:
  - "@feiskyer"
  - "@khenidak"
  - "@hogepodge"
  - "@jagosan"
editor: "@feiskyer"
creation-date: 2019-01-29
last-updated: 2020-01-18
status: implementable
---

# Supporting Out-of-Tree Azure Cloud Provider

## Table of Contents

<!-- toc -->
- [Release Signoff Checklist](#release-signoff-checklist)
- [Summary](#summary)
- [Motivation](#motivation)
  - [Goals](#goals)
  - [Non-Goals](#non-goals)
- [Proposal](#proposal)
  - [Documentation](#documentation)
  - [Implementation Details/Notes/Constraints](#implementation-detailsnotesconstraints)
  - [Risks and Mitigation](#risks-and-mitigation)
    - [API throttling](#api-throttling)
    - [Azure credential provider](#azure-credential-provider)
- [Design Details](#design-details)
  - [Test Plan](#test-plan)
  - [Graduation Criteria](#graduation-criteria)
  - [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
  - [Version Skew Strategy](#version-skew-strategy)
- [Implementation History](#implementation-history)
- [Technical Leads are members of the Kubernetes Organization](#technical-leads-are-members-of-the-kubernetes-organization)
- [Subproject Leads](#subproject-leads)
- [Meetings](#meetings)
<!-- /toc -->

## Release Signoff Checklist

- [X] k/enhancements issue in release milestone and linked to KEP (https://github.com/kubernetes/enhancements/issues/667)
- [X] KEP approvers have set the KEP status to `implementable`
- [X] Design details are appropriately documented
- [X] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [X] Graduation criteria is in place
- [X] "Implementation History" section is up-to-date for milestone
- [X] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

## Summary

Build support for the out-of-tree Azure cloud provider. This involves a well-tested version of the cloud-controller-manager
that has feature parity to the kube-controller-manager.

## Motivation

Motivation for supporting out-of-tree providers can be found in the [Cloud Controller Manager KEP](/keps/sig-cloud-provider/20180530-cloud-controller-manager.md).
This KEP is specifically tracking progress for the Azure cloud provider.

### Goals

- Develop/test/release the Azure cloud-controller-manager
- Kubernetes clusters running on Azure should be running the cloud-controller-manager.

### Non-Goals

- Removing in-tree Azure cloud provider code, this effort falls under the [KEP for removing in-tree providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20190125-removing-in-tree-providers.md).

## Proposal

We propose a set of repositories from the Kubernetes organization to host our cloud provider implementation. Since AzureFile/AzureDisk are also depending on Azure cloud provider, three new projects would be setup:

- [kubernetes/cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure) would be the main repository for Azure cloud controller manager.
- [kubernetes-sigs/azuredisk-csi-driver](https://github.com/kubernetes-sigs/azuredisk-csi-driver) would be the repository for AzureDisk CSI plugin.
- [kubernetes-sigs/azurefile-csi-driver](https://github.com/kubernetes-sigs/azurefile-csi-driver) would be the repository for AzureFile CSI plugin.

Those projects would be subprojects under [SIG Cloud Provider provider-azure](https://github.com/kubernetes/community/tree/master/sig-cloud-provider#provider-azure).

### Documentation

Example manifests, node labels/annotations, service labels/annotations and persistent volumes would be added per [Cloud Provider Documentation KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20180731-cloud-provider-docs.md):

```
cloud-provider-azure/
└── docs
    │── example-manifests
    |   |── in-tree/
    |   |   ├── apiserver.manifest                 # an example manifest of apiserver using the in-tree integration of this cloud provider
    |   |   ├── kube-controller-manager.manifest   # an example manifest of kube-controller-manager using the in-tree integration of this cloud provider
    |   |   └── kubelet.manifest                   # an example manifest of kubelet using the in-tree integration of this cloud provider
    |   └── out-of-tree/
    |       ├── apiserver.manifest                 # an example manifest of apiserver using the out-of-tree integration of this cloud provider
    |       ├── kube-controller-manager.manifest   # an example manifest of kube-controller-manager using the out-of-tree integration of this cloud provider
    |       ├── cloud-controller-manager.manifest  # an example manifest of cloud-controller-manager using the out-of-tree integration of this cloud provider
    |       └── kubelet.manifest                   # an example manifest of kubelet using out-of-tree integration of this cloud provider
    └── resources
        |── node/
        |   ├── labels.md        # outlines what annotations that can be used on a Node resource
        |   ├── annotations.md   # outlines what annotations that can be used on a Node resource
        |   └── README.md        # outlines any other cloud provider specific details worth mentioning regarding Nodes
        |── service/
        |   ├── labels.md        # outlines what annotations that can be used on a Service resource
        |   ├── annotations.md   # outlines what annotations that can be used on a Service resource
        |   └── README.md        # outlines any other cloud provider specific details worth mentioning regarding Services
        └── persistentvolumes/
            ├── azuredisk
            |   └── README.md    # outlines CSI drivers of AzureDisk and link to CSI repository
            └── azurefile
                └── README.md    # outlines CSI drivers of AzureFile and link to CSI repository
```

### Implementation Details/Notes/Constraints

- The core of Azure cloud provider would be moved to [kubernetes-sigs/cloud-provider-azure](https://github.com/kubernetes-sigs/cloud-provider-azure).
- The storage drivers would be moved to [kubernetes-sigs/azuredisk-csi-driver](https://github.com/kubernetes-sigs/azuredisk-csi-driver) and [kubernetes-sigs/azurefile-csi-driver](https://github.com/kubernetes-sigs/azurefile-csi-driver).
- The credential provider is still under discussion on [kubernetes/cloud-provider#13](https://github.com/kubernetes/cloud-provider/issues/13).

### Risks and Mitigation

#### API throttling

Before CCM, kubelet supports getting Node information by cloud provider's instance metadata service. This includes:

- NodeName
- ProviderID
- NodeAddresses
- InstanceType
- AvailabilityZone

But with CCM, this is not possible anymore because the above functionalities have been moved to cloud controller manager.

Since API throttling is a main issue for large clusters, we have added caches for Azure resources in KCM. Those caches would also be added to CCM. But even with caches, there would still be API throttling issues on cluster provisioning stages and nodes initialization durations would be much longer than KCM because of throttling.

This issue is being tracked on [kubernetes/cloud-provider#30](https://github.com/kubernetes/cloud-provider/issues/30). Its status would be updated later when it's discussed through sig cloud-provider.

#### Azure credential provider

Azure credential provider is also depending on cloud provider codes. Though Azure Managed Service Identity (MSI) is a way to avoid explicit setting of credentials, MSI is not available on all cases (e.g. MSI may not be authorized to specific ACR repository).

This issue is being tracked on KEP [Support Instance Metadata Service with Cloud Controller Manager](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/azure/20190722-ccm-instance-metadata.md). It has been marked as implementable and would be implemented in cloud-provider-azure.

## Design Details

### Test Plan

Azure Cloud Controller provider is reporting conformance test results to TestGrid as per the [Reporting Conformance Test Results to Testgrid KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0018-testgrid-conformance-e2e.md).

See [report](https://testgrid.k8s.io/provider-azure-cloud-provider-azure) for more details.

### Graduation Criteria

- Azure cloud controller manager is moving to GA
  - Feature compatible with KCM
  - Conformance tests are passed and published to testgrid
- CSI drivers for AzureDisk/AzureFile are moving to GA
  - Feature compatible with KCM
  - Conformance tests are passed and published to testgrid
- Azure credential provider is still supported in Kubelet
  - Feature compatible with KCM
  - Conformance tests are passed and published to testgrid

### Upgrade / Downgrade Strategy

Upgrade/Downgrade Azure cloud controller manager and CSI drivers together with other master components. The versions for Azure cloud controller manager and CSI drivers should be chosen according to the version skew strategy below.

### Version Skew Strategy

For each Kubernetes minor releases (e.g. v1.15.x), dedicated Azure cloud controller manager would be released. For CSI drivers, however, they would be released based on [CSI specification versions](https://kubernetes-csi.github.io/docs/).

- The version matrix for Azure cloud controller manager would be documented on [kubernetes/cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure/blob/master/README.md#current-status).
- The version matrix for CSI drivers would be documented on [kubernetes-sigs/azuredisk-csi-driver](https://github.com/kubernetes-sigs/azuredisk-csi-driver#container-images--csi-compatibility) and [kubernetes-sigs/azurefile-csi-driver](https://github.com/kubernetes-sigs/azurefile-csi-driver#container-images--csi-compatibility).

## Implementation History

See [kubernetes/cloud-provider-azure#pulls](https://github.com/kubernetes/cloud-provider-azure/pulls?utf8=%E2%9C%93&q=+is%3Apr+), [kubernetes-sigs/azuredisk-csi-driver#pulls](https://github.com/kubernetes-sigs/azuredisk-csi-driver/pulls?utf8=%E2%9C%93&q=is%3Apr++) and [kubernetes-sigs/azurefile-csi-driver#pulls](https://github.com/kubernetes-sigs/azurefile-csi-driver/pulls?utf8=%E2%9C%93&q=is%3Apr++).

## Technical Leads are members of the Kubernetes Organization

The Leads run operations and processes governing this subproject.

- @khenidak
- @feiskyer

## Subproject Leads

- @dstrebel
- @justaugustus

## Meetings

Sig-Azure meetings is expected to have biweekly. SIG Cloud Provider will provide zoom/youtube channels as required. We will have our first meeting after repo has been settled.

Meeting Time: Wednesdays at 09:00 PT (Pacific Time) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=20:00&tz=PT%20%28Pacific%20Time%29).

- [Meeting notes and Agenda](https://docs.google.com/document/d/1SpxvmOgHDhnA72Z0lbhBffrfe9inQxZkU9xqlafOW9k/edit).
- [Meeting recordings](https://www.youtube.com/watch?v=yQLeUKi_dwg&list=PL69nYSiGNLP2JNdHwB8GxRs2mikK7zyc4).

repository: arrikto/kubernetes-enhancements

gha_language: Go

repo_name: arrikto/kubernetes-enhancements


text:
This is a very **simple** GitHub action; it just runs in `Rscript` whatever you provide as the `args` field (see below).
This action is meant for **generic** R projects with **arbitrary build environments**; you therefore [**have to bring your own dockerfile**](http://www.maxheld.de/ghactions/articles/ghactions.html#docker).
Such a `Dockerfile` has to exist at the root of your repository.

Whatever you pass `Rscript` will simply run *in* an image build from that `Dockerfile`.
Hence the name: **bring-your-own-dockerfile**.

You can find popular Docker images for R projects at the [Rocker Project](https://www.rocker-project.org/).

You can use the `ghactions::use_dockerfile()` function to set up a simple `Dockerfile` in your repository.

If you're using this action on your own, remember that **this action expects a built image called `repo:latest` in your `/github/workspace`.**
Use `ghactions::build_image()` to build such an image from your `Dockerfile` first.

If this all sounds rather complicated, consider the [short documentation](http://www.maxheld.de/ghactions/articles/ghactions.html#docker).

## Environment Variables

None so far.

## Secrets

nada.

## Required Arguments

Whatever your provide in `args` simply gets appended to the `Rscript` call.
So just imagine `Rscript` in front of it; if it is a valid shell command, you're good to go.
Remember that `Rscript` is the ([now preferred](https://stackoverflow.com/questions/18306362/run-r-script-from-command-line/18306656#18306656)) way to run R from a system shell (*not* the R console).
We have to use `Rscript`, because there's no GUI that could hook us up directly to the R console in our non-interactive image run.
[Here](https://stat.ethz.ch/R-manual/R-devel/library/utils/html/Rscript.html) is the full documentation.

A typical `args` example is

```bash
"-e 'rmarkdown::render_site()'"
```

which is appended to `Rscript` by this action, so you're really running

```bash
Rscript -e 'rmarkdown::render_site()'
```

which `Rscript` passes to the R console, where you know it as

```r
rmarkdown::render_site()
```

## Optional Arguments

Nope.

## Example Usage

Here is a complete `main.workflow` that first builds your (byod) image, and then runs `rmarkdown::render_site()` on it.
You can also get this automatically by running one of the `ghactions::website()` function in the ghactions package.

```
workflow "Build then render" {
  on = "push"
  resolves = "Render rmarkdown"
}

action "Build image" {
  uses = "actions/docker/cli@c08a5fc9e0286844156fefff2c141072048141f6"
  args = "build --tag=repo:latest ."
}

action "Render rmarkdown" {
  needs = "Build image"
  uses = "maxheld83/ghactions/Rscript-byod@master"
  args = "-e 'rmarkdown::render_site()'"
}
```

Of course, you can also use the visual workflow editor in GitHub, which is highly recommended.

The cryptic-seeming `uses = "maxheld83/ghactions/Rscript-byod@master"` in the above is simply a way to take a *particular* version of this action as a dependency.
The part after `@` is a git tag, or release from my (= the action developer's) repo.
It is generally recommended to specify dependencies in GitHub actions as narrowly as you can.
That way, your workflow won't break if the maintainer of the action changes things up.

license: MIT

gha_license_id: MIT


text:
Oval HR Solutions

World famous astrologer Lolita needs a Horoscope-as-a-Service (HaaS) application,
because she is tired of doing all these complex astrological calculations by hand.
Using Laravel and SQL database of your choice, create an application that:

  1. Generates horoscopes for all 12 Zodiac signs for a given year. Each sign can have
  from 1 (really shitty day) to 10 (super amazing day).
  2. Day scores are generated randomly for each day and stored in the database.
  3. Shows a calendar for a given year and Zodiac sign.
  4. Days should be colored from #ff0000 (really shitty) to #00ff00 (super amazing).
  5. Shows the best month on average (by score) for a Zodiac sign in a given year.
  6. Shows which Zodiac sign has the best year (by score)

**BONUS POINTS: Generate a sentence that describes what happens to an astrological
sign on a given day. Sentence should make sense, be relevant to the score of the day (1 -
10), and should not be repetitive.

path: /ASSIGNMENT DESCRIPTION.md

filename: ASSIGNMENT DESCRIPTION.md


text:
# Better Than Takeout Chicken Fried Rice

## Ingredients

- 1 cup rice

- 3 chicken breasts, cooked and shredded (I recommend slow cooker chicken teriyaki)

- 1 onion, diced

- 2 cloves garlic, minced

- 1/2 cup frozen peas

- 4 carrots, diced

- 2 eggs

- 3 tablespoons sesame oil (or you can substitute butter!)

- 1/4 cup soy sauce

- Optional: sesame seeds

## Method

1. Prepare 1 cup rice with two cups water in a rice cooker or on the stovetop.
---
2. Meanwhile, heat sesame oil in a large skillet over medium heat. Add onion, garlic, peas, and carrots. Cook for 5-7 minutes.
---
3. Crack eggs into pan and scramble, mixing with vegetables.
---
4. Add rice, chicken, and soy sauce to pan. Stir to combine and remove from heat.
---

## References and Acknowledgments

[Better Than Takeout Chicken Fried Rice](http://rachelschultz.com/2012/07/14/better-than-takeout-chicken-fried-rice/)

repository: troyerta/recipes

gha_language: Python

repo_name: troyerta/recipes


text:
# Airbrussh Change Log

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

Airbrussh is in a pre-1.0 state. This means that its APIs and behavior are subject to breaking changes without deprecation notices. Until 1.0, version numbers will follow a [Semver][]-ish `0.y.z` format, where `y` is incremented when new features or breaking changes are introduced, and `z` is incremented for lesser changes or bug fixes.

## [Unreleased]

* Your contribution here!
* Added Rubocop enforcement to Travis
* Airbrussh now has decent test coverage, and is tested by Travis against a matrix of Ruby and SSHKit versions ([@robd](https://github.com/robd))
* Changes to support the new SSHKit formatter API, as introduced in [SSHKit #257](https://github.com/capistrano/sshkit/pull/257) ([@robd](https://github.com/robd))

## [0.4.1][] (2015-05-06)

* Fix `Marshal.dump` warnings by removing `deep_copy` workaround that it is no longer needed for the latest SSHKit ([#10](https://github.com/mattbrictson/airbrussh/issues/10)).

## [0.4.0][] (2015-05-03)

* Changes to ensure compatibility with the upcoming version of SSHKit ([ec3122b](https://github.com/mattbrictson/airbrussh/commit/ec3122b101de53f2304723da842d5c8b6f70f4f3)).
* Explicitly specify UTF-8 encoding for source files, for Ruby 1.9.3 compatibility ([#9](https://github.com/mattbrictson/airbrussh/issues/9)).

## [0.3.0][] (2015-03-28)

* New `config.banner` option allows startup message to be disabled or changed (suggestion from [@justindowning](https://github.com/justindowning))
* New `config.command_output` option gives full control of whether airbrussh shows or hides the stderr and stdout data received from remote commands; see the usage section of the README for further explanation (suggestion from [@carlesso](https://github.com/carlesso))

## [0.2.1][] (2015-03-02)

* Un-pin SSHKit dependency now that SSHKit 1.7.1 has been released.

## [0.2.0][] (2015-03-02)

* Pin SSHKit dependency at `~> 1.6.1` to avoid a [bug in 1.7.0](https://github.com/capistrano/sshkit/issues/226) that causes command exit statuses to be omitted from the log.

## 0.0.1 (2015-02-19)

* Initial release

[Semver]: http://semver.org
[Unreleased]: https://github.com/mattbrictson/airbrussh/compare/v0.4.1...HEAD
[0.4.1]: https://github.com/mattbrictson/airbrussh/compare/v0.4.0...v0.4.1
[0.4.0]: https://github.com/mattbrictson/airbrussh/compare/v0.3.0...v0.4.0
[0.3.0]: https://github.com/mattbrictson/airbrussh/compare/v0.2.1...v0.3.0
[0.2.1]: https://github.com/mattbrictson/airbrussh/compare/v0.2.0...v0.2.1
[0.2.0]: https://github.com/mattbrictson/airbrussh/compare/v0.0.1...v0.2.0

repository: mattbrictson/chandler

gha_language: Ruby

repo_name: mattbrictson/chandler


text:
## Tooltips

After multiple iterations, we have a working tooltip solution via this [pull request](https://github.com/ppy/osu/pull/653). A combined effort between myself and jorolf, these new tooltips should reflect what we used to have in osu-stable but at the same time add a new feel via animations.

Note that these are not heavily deployed throughout the interface yet; this will happen over time.

## Minor changes

- Sliderbars sound effects have been tamed a bit.
- Fixed chat timestamps being in 12-hour time.
- [API updates](https://github.com/ppy/osu/pull/657) to allow statistics to be shown at the results screen.
- Taiko drumroll [conversion fixes](https://github.com/ppy/osu/pull/656/commits/8facf473d15ce5555af24b12b23c71ed475d6b3f) and tick [design changes](https://github.com/ppy/osu/pull/656/commits/a958c99e2264454f1cc5dd0f704bfe380bbabfe8).
- Fix for lag when [watching taiko in autoplay](https://github.com/ppy/osu/pull/656/commits/61090d918c4adfac59d06057c90483d135f735f6).
- Glow of health bar [changes](https://github.com/ppy/osu/pull/656/commits/6e3018f36da0afa59e226096632e23d6e7f0e134) when objects are successfully hit.

## New release available

2017.420.0 is now available from [github releases](https://github.com/ppy/osu/releases/tag/v2017.420.0) (or via auto-update if you already have lazer installed)!

This build sees the **initial release of the results screen** to the public. As mentioned multiple times, the design is not yet complete, but it's a huge leap forward from what we've had until now! You can click through to the results screen from leaderboards at song select, or play a map and experience it for yourself.


text:
Core Role
=========

This installs the common utilities and configurations used to interact with a unix system.
It is based upon buffersandbeer's preferences.

Contents:
- tmux
- vim
- zsh
- misc unix tools

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

Currently only Debian distributions supported

Role Variables
--------------

None

Dependencies
------------

None

Example Playbook
----------------

    - hosts: core
      roles:
         - role-core

License
-------

BSD

Author Information
------------------

I am buffersandbeer

repository: net-shaper/role-core

repo_name: net-shaper/role-core


text:
# node-gyp-install

Manually download node/iojs header files for usage with node-gyp.

``` sh
npm install -g node-gyp-install
```

[![build status](http://img.shields.io/travis/mafintosh/node-gyp-install.svg?style=flat)](http://travis-ci.org/mafintosh/node-gyp-install)

## Usage

To download the node/iojs header files for the node/iojs version you currently
have installed simply run

``` sh
node-gyp-install
```

Afterwards installing native modules that uses node-gyp using iojs should *just work*

``` sh
node-gyp-install
npm install level # does not explode \o/
```

Per default node-gyp-install will install header files for your current node version.
To see all available options see `node-gyp-install --help`.

### Download From Mirrors

To use a mirror of the node/iojs header files, set `$NVM_NODEJS_ORG_MIRROR` and `$NVM_IOJS_ORG_MIRROR`.

Take an example for users from China:

``` sh
export NVM_NODEJS_ORG_MIRROR=http://npm.taobao.org/mirrors/node
export NVM_IOJS_ORG_MIRROR=http://npm.taobao.org/mirrors/iojs
```

### Download From Secure Mirrors

To use private mirrors that need some https/tls configuration e.g. for client authentification you
can pass some more environment settings:

``` sh
export NODE_GYP_INSTALL_PASSPHRASE=mysecret
export NODE_GYP_INSTALL_REJECTUNAUTHORIZED=false
export NODE_GYP_INSTALL_PFX=/path/to/my/key.p12
export NODE_GYP_INSTALL_CERT=/path/to/my/cert.crt
export NODE_GYP_INSTALL_KEY=/path/to/my/key.key
export NODE_GYP_INSTALL_CA=/path/to/my/ca.crt
```

This variables refers to the according options of the https.request() function.
Please have a look to [nodejs tls api documentation](https://nodejs.org/api/tls.html)
for more details.

## Programmatic usage

You can also use this as a module

``` js
var install = require('node-gyp-install')
install(function (err) {
  console.log('header files installed', err)
})
```

## License

MIT

repository: mafintosh/node-gyp-install

gha_language: JavaScript

repo_name: mafintosh/node-gyp-install


text:
[![Build Status](https://travis-ci.org/schultyy/os_type.svg?branch=master)](https://travis-ci.org/schultyy/os_type)

# os_type
Rust library to detect the operating system type

## Usage

Include this into your `Cargo.toml`:

```toml
[dependencies]
os_type="0.1.0"
```

In your code:

```rust
extern crate os_type;

fn foo() {
      match os_type::current_platform() {
        os_type::OSType::OSX => /*Do something here*/,
        _ => None
    }
}
```

Note that right now it detects only `OS X` and `RedHat/CentOS`. If you need support for more OS types,
I am looking forward to your Pull Request.

## License

MIT


text:
---
name: Issues and Bugs
about: Create a report to help us improve
title: "[ISSUES AND BUGS]"
labels: ''
assignees: psudo-dev

---

## Option

Choose your option with an "x"

-  [ ] Issues and Bugs
   -  [ ] Oni UI
   -  [ ] Nebula Syntax
-  [ ] Other

## Summary

<!--- Provide a general summary of the subject -->

## Description

<!--- Provide a more detailed description of the subject -->

## Print Screen

<!--- If necessary, provide a print screen or screen recording to help understand the issue better -->

## Possible Solution

<!--- If possible, suggest a solution or anything that might help with the issue. -->

## Testing

<!--- Check the VSCode Customization page and test your solution to see if works. Some TextMate and Semantic Tokens unintentionally change some unexpected scope, the suggestion would be to test it with a more extensive code snippet. -->

### VSCode Customization Quick Guide

[VSCode Customization - Quick Guide](./CUSTOMIZATION.md)

## Snippet

Language:
Extensions:

<!--- In case it's necessary to download some extension for language support that affects the Syntax, like Babel for Javascript -->

Snippet:

<!--- Provide a snippet so it can be tested -->

## Message

<!--- If there is anything else you would like to add, feel free to write here or just message me! Thanks! -->

## Your Environment

<!--- Include as many relevant details about the environment you deem necessary -->

-  Operating System:
-  VSCode Version:
-  Theme Version:

repository: psudo-dev/nebula-oni-theme

branch_name: refs/heads/main

repo_name: psudo-dev/nebula-oni-theme


text:
# Transaction Manager

[![Author](https://img.shields.io/badge/author-@RemiSan-blue.svg?style=flat-square)](https://twitter.com/RemiSan)
[![Build Status](https://img.shields.io/travis/remi-san/transaction-manager/master.svg?style=flat-square)](https://travis-ci.org/remi-san/transaction-manager)
[![Quality Score](https://img.shields.io/scrutinizer/g/remi-san/transaction-manager.svg?style=flat-square)](https://scrutinizer-ci.com/g/remi-san/transaction-manager)
[![Software License](https://img.shields.io/badge/license-MIT-brightgreen.svg?style=flat-square)](LICENSE)
[![Packagist Version](https://img.shields.io/packagist/v/remi-san/transaction-manager.svg?style=flat-square)](https://packagist.org/packages/remi-san/transaction-manager)
[![Coverage Status](https://img.shields.io/scrutinizer/coverage/g/remi-san/transaction-manager.svg?style=flat-square)](https://scrutinizer-ci.com/g/remi-san/transaction-manager/code-structure)
[![SensioLabsInsight](https://insight.sensiolabs.com/projects/f83d5077-8374-4fbd-a20c-b2aba6c496af/small.png)](https://insight.sensiolabs.com/projects/f83d5077-8374-4fbd-a20c-b2aba6c496af)

A simple transaction manager with a naive implementation.

It provides a common interface to manage transactions.

If you want to make a class transactional, implement the `Transactional` interface.

Transaction Manager
-------------------
Two `TransactionManager` implementations are provided allowing you to manage multiple `Transactional` classes in the same logic transaction.

- `SimpleTransactionManager` is a naive implementation preventing from beginning a transaction more than once.
- `MultipleTransactionManager` allows you to begin the transaction more than once but only commits if `commit` is called the same number of times as `beginTransaction`.

Implementations
---------------
Some `Transactional` implementations are provided:

 - `TransactionalQueuePublisher` to publish in an AMQP queue with [`Burrow`](https://github.com/Evaneos/Burrow) in a transaction
 - `DoctrineDbalTransactionManager` to deal with [`Doctrine DBAL`](https://github.com/doctrine/dbal) transactions
 - `DoctrineEntityManager` to deal with [`Doctrine ORM`](https://github.com/doctrine/doctrine2) transactions
 - `TransactionalEmitter` to emit `Events` with the [`PHP League` lib](https://github.com/thephpleague/event) in a transaction
 - `TransactionalCommandBus` to handle `Commands` with the [`PHP League` lib](https://github.com/thephpleague/tactician) in a transaction

repository: remi-san/transaction-manager

repo_name: remi-san/transaction-manager


text:
# ProjectDeployer
The goal of ProjectDeployer is to be a project deployment framework for programmers.

It differs from tools like ansible and chef in the sense that instead of describing
a desired state through configuration, ProjectDeployer feels more like writing a script
of deployment stuff to do.

Configuration is still needed but in ProjectDeployer, configuration is exactly what it
sounds like and not "configuration programming" i.e. creating tasks and actions
through complex configuration. This way you end up with a simple to understand
configuration, and a groovy script (or java program) that describes what should be done which greatly
improves readability and debugging ability.

Assuming the following config file:
```xml
<deploymentConfig>
    <!-- Deployment example for an application called glow -->
    <global>
        <sshUser>pernyf</sshUser>
        <!-- source can be sshpass, prompt, cert, keyring -->
        <sshPasswordSource>prompt</sshPasswordSource>
    </global>
    <environment name="test">
        <target name="backend">
            <host>behost1.test.alipsa.se:22022</host>
        </target>
        <target name="frontend">
            <host>fehost1.test.alipsa.se:22022</host>
        </target>
    </environment>
    <environment name="prod">
        <target name="backend">
            <host>behost1.prod.alipsa.se:22022</host>
            <host>behost2.prod.alipsa.se:22022</host>
        </target>
        <target name="frontend">
            <host>fehost1.prod.alipsa.se:22022</host>
            <host>fehost2.prod.alipsa.se:22022</host>
        </target>
    </environment>
</deploymentConfig>
```
...The following deploy script (named deployGlow.groovy) can be written to deploy to either test or prod environments
```groovy
@Grab('se.alipsa:ProjectDeployer:1.0.0')
import se.alipsa.pd.*

String serverUser = "glow"
String alipsaNexus ="http://localhost:8080/nexus"
String backendServiceName = "glow-backend.service"
String frontEndServiceName = "glow-frontend.service"
String javaVersion="11.0.10"
String baseTargetDir="/usr/local/glow"

File glowBackendJar
File glowFrontEndZip

def pd = ProjectDeployer.create("myDeploymentConfig.xml")
pd.addSetupActions {
    glowBackendJar = pd.fetchFromRepository(alipsaNexus, "se.alipsa:glow-backend:1.2")
    glowFrontEndZip = pd.fetchFromRepository(alipsaNexus, "se.alipsa:glow-frontend:1.2")
}

// d is an instance of Deployment (there is one Deployment for each host)
pd.createActions "backend", { d ->
    {
        d.createServerUser(serverUser)
        d.stopService(backendServiceName)
        String javaHome = d.installJava(javaVersion, baseTargetDir)
        d.copy( fromFile: glowBackendJar,
                toFile: "${baseTargetDir}/backend/${glowBackendJar.getName()}",
                owner: serverUser,
                permissions: "g=rwx,u=rwx,o=r")
        d.createService(
                name: backendServiceName,
                exec: "${javaHome}/bin/java -jar ${glowBackendJar.getName()}",
                runas: serverUser)
        d.startService(backendServiceName)
    }
}

pd.createActions "frontend", { d ->
    {
        d.createServerUser(serverUser)
        d.stopService(frontEndServiceName)
        String nginxVersion = d.ssh("sudo apt update && sudo apt install nginx && sudo nginx -v")
        println("nginx version is now ${nginxVersion}")
        String zipPath = "${baseTargetDir}/frontend/${glowFrontEndZip.getName()}"
        d.copy(glowFrontEndZip, zipPath, "g=rw,u=rw,o=r")
        d.ssh("unzip ${zipPath}")
        d.createService(name: frontEndServiceName,
                content: """[Unit]
                Description=The NGINX HTTP server
                After=syslog.target network-online.target remote-fs.target nss-lookup.target
                Wants=network-online.target

                [Service]
                Type=forking
                PIDFile=/run/nginx.pid
                ExecStartPre=/usr/sbin/nginx -t
                ExecStart=/usr/sbin/nginx
                ExecReload=/usr/sbin/nginx -s reload
                ExecStop=/bin/kill -s QUIT $MAINPID
                PrivateTmp=true

                [Install]
                WantedBy=multi-user.target"""
                )
        d.startService(frontEndServiceName)
    }
}
// relevant actions will now run on each host
// this.args[0] is the first argument passed to this script
// it will be validated against existing environments
pd.deploy args[0]
```
You can then deploy to test as follows:
`groovy deployGlow.groovy test`

repository: perNyfelt/ProjectDeployer

repo_name: perNyfelt/ProjectDeployer


text:
# Sup

A Slack client with a UI similar to WhatsApp, supports Web, Android, Desktop.

**Do not use this for work, it's experiemental and you might miss important messages due to bugs and
missing features.**

[Open Webapp](https://arnnis.github.io/Sup)

## Screenshots

| Mobile         | Tablet         |
| -------------- | -------------- |
| ![][mobilegif] | ![][tabletgif] |

## Install

- [Web](https://arnnis.github.io/Sup) - Web version using react-native-web
- [Android](https://github.com/arnnis/Sup/releases/latest) - Android apk
- [Windows](https://github.com/arnnis/Sup/releases/latest) - Windows version using electron
- [Linux](https://github.com/arnnis/Sup/releases/latest) - Linux version using electron

[mobilegif]: https://user-images.githubusercontent.com/58140889/71323716-8ecdfc00-24eb-11ea-8740-1325d4457ccc.gif
[tabletgif]: https://user-images.githubusercontent.com/58140889/71326898-5394f280-2516-11ea-8efd-93fb0cab643b.gif
[conversation]: https://user-images.githubusercontent.com/56032649/65983227-eda24d00-e489-11e9-9d31-ed6d392237e3.png
[workspaces]: https://user-images.githubusercontent.com/56032649/65982799-0100e880-e489-11e9-87c0-ae898f3603dc.png

## Contributing
Run the following to start webpack development server:
```sh
yarn web
```
To start desktop development server:
```sh
yarn desktop
```

To run android:
```sh
yarn android
```

To run ios:
```sh
yarn ios
```

To build for desktop:
```sh
yarn desktop:release
```

To build for android:
```sh
yarn android:release
```

To build for web:
```sh
yarn web:release
```

repository: mkamranhamid/slack-as-whatsapp

repo_name: mkamranhamid/slack-as-whatsapp


text:
## Virtual Proctor using Amazon Rekognition

Proctoring is the act of supervising an exam or course online.

Using web-based applications, virtual proctoring platforms allow test takers to be virtually monitored by a human via the webcam on their computer.
To increase the scale of the test taking and improve a human proctor’s ability to monitor students, virtual proctoring services are now implementing AI/ML to support the human proctor.

Virtual Proctor is a solution that leverages Amazon Rekognition to show a scalable way to conduct online testing.

It shows how you can implement rules such as:

- Detecting objects of interest (such as mobile phone)
- Detecting the number of people present
- Recognizing the person who is taking a test
- Detecting unsafe content (such as explicit adult content or violent content)

You can also use [Amazon Rekognition Custom Labels](https://aws.amazon.com/rekognition/custom-labels-features/) to detect other custom objects of interest.

### Index

- [Architecture](#architecture)
- [Usage](#usage)
  - [Prerequisites](#prerequisites)
  - [Deployment](#deployment)
  - [Accessing the application](#accessing-the-application)
- [Remove the application](#remove-the-application)
- [Making changes to the code and customization](#making-changes-to-the-code-and-customization)
- [Samples]
- [Contributing](#contributing)

### Architecture

### Usage

#### Prerequisites

To deploy the sample application, you will require an AWS account. If you don’t already have an AWS account, create one at <https://aws.amazon.com> by following the on-screen instructions. Your access to the AWS account must have IAM permissions to launch AWS CloudFormation templates that create IAM roles.

To use the sample application you will require a [modern browser](https://caniuse.com/#feat=stream) and a webcam.

#### Deployment

The demo application is deployed as an [AWS CloudFormation](https://aws.amazon.com/cloudformation) template.

> **Note**
> You are responsible for the cost of the AWS services used while running this sample deployment. There is no additional cost for using this sample. For full details, see the following pricing pages for each AWS service you will be using in this sample. Prices are subject to change.
>
> - [Amazon Rekognition Pricing](https://aws.amazon.com/rekognition/pricing/)
> - [Amazon S3 Pricing](https://aws.amazon.com/s3/pricing/)
> - [Amazon Cognito Pricing](https://aws.amazon.com/cognito/pricing/)
> - [Amazon CloudFront Pricing](https://aws.amazon.com/cloudfront/pricing/)

1. Deploy the latest CloudFormation template by following the link below for your preferred AWS region:

| Region                                        | Launch Template                                                                                |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **US East (N. Virginia)** (us-east-1)         | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-us-east-1.s3.us-east-1.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml)                |
| **US East (Ohio)** (us-east-2)                | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=us-east-2#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-us-east-2.s3.us-east-2.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml)                |
| **US West (Oregon)** (us-west-2)              | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-us-west-2.s3.us-west-2.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml)                |
| **EU (Ireland)** (eu-west-1)                  | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-eu-west-1.s3.eu-west-1.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml)                |
| **Asia Pacific (Sydney)** (ap-southeast-2)    | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=ap-southeast-2#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-ap-southeast-2.s3.ap-southeast-2.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml) |
| **Asia Pacific (Singapore)** (ap-southeast-1) | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=ap-southeast-1#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-ap-southeast-1.s3.ap-southeast-1.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml) |
| **Asia Pacific (Mumbai)** (ap-south-1)        | [![Launch the VirtualProctor Stack with CloudFormation](docs/deploy-to-aws.png)](https://console.aws.amazon.com/cloudformation/home?region=ap-south-1#/stacks/new?stackName=VirtualProctor&templateURL=https://solution-builders-ap-south-1.s3.ap-south-1.amazonaws.com/amazon-rekognition-virtual-proctor/latest/template.yaml)             |

2. If prompted, login using your AWS account credentials.
3. You should see a screen titled "_Create Stack_" at the "_Specify template_" step. The fields specifying the CloudFormation template are pre-populated. Click the _Next_ button at the bottom of the page.
4. On the "_Specify stack details_" screen you may customize the following parameters of the CloudFormation stack:

   - **Stack Name:** (Default: VirtualProctor) This is the name that is used to refer to this stack in CloudFormation once deployed.
   - **AdminEmail:** The email address you wish to setup as the initial user of this Amazon Rekognition Virtual Proctor deployment.
   - **MinConfidence:** (Default: 85) Specifies the minimum confidence level for the labels to return.
   - **ObjectsOfInterestLabels** (Default "Mobile Phone,Cell Phone"): Comma-delimited list of labels used to detect Objects of interest.
   - **CreateCloudFrontDistribution** (Default: true) Creates a CloudFront distribution for accessing the web interface of the solution.
   - **ResourcePrefix:** (Default: VirtualProctor) Resource prefix to apply to resource names when creating statically named resources.

   When completed, click _Next_

5. [Configure stack options](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-add-tags.html) if desired, then click _Next_.
6. On the review you screen, you must check the boxes for:

   - "_I acknowledge that AWS CloudFormation might create IAM resources_"
   - "_I acknowledge that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND_"

   These are required to allow CloudFormation to create a Role to allow access to resources needed by the stack and name the resources in a dynamic way.

7. Click _Create Change Set_
8. On the _Change Set_ screen, click _Execute_ to launch your stack.
   - You may need to wait for the _Execution status_ of the change set to become "_AVAILABLE_" before the "_Execute_" button becomes available.
9. Wait for the CloudFormation stack to launch. Completion is indicated when the "Stack status" is "_CREATE_COMPLETE_".
   - You can monitor the stack creation progress in the "Events" tab.
10. Note the _url_ displayed in the _Outputs_ tab for the stack. This is used to access the application.

#### Accessing the Application

The application is accessed using a web browser. The address is the _url_ output from the CloudFormation stack created during the Deployment steps.

When accessing the application for the first time, you need to use the Admin e-mail provided during Stack Creation as the username. A temporary password will be sent to the same e-mail address. After authentication, it will be necessary to create a new password and click "Change".

To manage users, you can use the [Cognito Users Pool console](https://console.aws.amazon.com/cognito/users).

### Remove the application

To remove the application open the AWS CloudFormation Console, click the Virtual Proctor project, right-click and select "_Delete Stack_". Your stack will take some time to be deleted. You can track its progress in the "Events" tab. When it is done, the status will change from "_DELETE_IN_PROGRESS_" to "_DELETE_COMPLETE_". It will then disappear from the list.

### Making changes to the code and customization

The [contributing guidelines](CONTRIBUTING.md) contains some instructions about how to run the front-end locally and make changes to the back-end stack.

### Samples

[Python Samples](./python-samples) contains python snippets for virtual proctoring usecases

## Contributing

Contributions are more than welcome. Please read the [code of conduct](CODE_OF_CONDUCT.md) and the [contributing guidelines](CONTRIBUTING.md).

## License Summary

This library is licensed under the MIT-0 License. See the LICENSE file.


text:
---
title: "EV7: Day 15: Prässebo to Göteborg"
excerpt: "57 km - 350 hm"
categories:
  - EuroVelo7
tags:
  - Sweden
  - Hotel
---
The headwind was still going strong today. To avoid the rain to the east of us, we didn't follow the official Sverigeleden route into Göteborg, but decided to take the (way) less scenic shortcut along the highway and along the _[Göta Kanal](https://www.gotakanal.se/en/)_.

Once we had checked in and took a shower we used the remaining day for sightseeing.

Göteborg is clearly a cycle city with lots of dedicated bike lanes - and they're heavily used, too. We love it!
## Photos

{% include photos day="15" no="5" %}

## Route

{% include komoot id="87871799" %}


text:
Delaunay
=====

[![Build Status](https://travis-ci.org/Yonaba/delaunay.png)](https://travis-ci.org/Yonaba/delaunay)
[![Coverage Status](https://coveralls.io/repos/Yonaba/delaunay/badge.png?branch=master)](https://coveralls.io/r/Yonaba/delaunay?branch=master)
[![License](http://img.shields.io/badge/Licence-MIT-brightgreen.svg)](LICENSE)

*delaunay* is a Lua module for [delaunay triangulation](http://en.wikipedia.org/wiki/Delaunay_triangulation) of a convex polygon.

##Download

###Git

````
git clone http://github.com/Yonaba/delaunay.git
````

###Archive

* [zip](https://github.com/Yonaba/delaunay/archive/delaunay-0.1-1.zip) | [tar.gz](https://github.com/Yonaba/delaunay/archive/delaunay-0.1-1.tar.gz) | [all](http://github.com/Yonaba/delaunay/tags)

###LuaRocks

````
luarocks install delaunay
````

###MoonRocks

````
luarocks install --server=http://rocks.moonscript.org/manifests/Yonaba delaunay
````

##Installation
Copy the file [delaunay.lua](http://raw.github.com/Yonaba/delaunay/master/delaunay.lua) inside your project folder,
call it with [require](http://pgl.yoyo.org/luai/i/require) function. It will return the `Delaunay` module, keeping safe the global environment.

##Usage

The module provides 3 classes:

* `Point`
* `Edge`
* `Triangle`

It also provides a single function named `triangulate`. This function accepts
a variable list (*vararg* `...`) of instances of class `Point`. Assuming those
points are the vertices of a convex polygon, it returns a table of instances of the class `Triangle` forming a *Delaunay triangulation* of the given polygon.

A basic code example:
```lua
local Delaunay = require 'Delaunay'
local Point    = Delaunay.Point

-- Creating 10 random points
local points = {}
for i = 1, 10 do
  points[i] = Point(math.random() * 100, math.random() * 100)
end

-- Triangulating de convex polygon made by those points
local triangles = Delaunay.triangulate(unpack(points))

-- Printing the results
for i, triangle in ipairs(triangles) do
  print(triangle)
end
````

See the [documentation](http://yonaba.github.io/delaunay/doc) for more details.

##Testing
###Specification

This repository include unit tests. You can run them using [Telescope](https://github.com/norman/telescope) with the following command from the root foolder:

```
lua tsc -f specs/*
```

###Performance

You can run the random performance tests included with the following command from the root folder:

```lua
lua performance/bench.lua
````

##License
This work is under [MIT-LICENSE](http://www.opensource.org/licenses/mit-license.php).

Copyright (c) 2013 Roland Yonaba

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

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

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

[![Bitdeli Badge](https://d2weczhvl823v0.cloudfront.net/Yonaba/delaunay/trend.png)](https://bitdeli.com/free "Bitdeli Badge")

repository: roelofvkr/luaforwindows

repo_name: roelofvkr/luaforwindows


text:
# YouTube-Sentiment-Analysis

Scrape all the YouTube comments using api , and filter the comments

## Description :
This project works by scraping YouTube comments and identify the sentiment of comments.

The directory FancySentiment shows the WordCloud (most frequent words) of the comments.

The directory CommentSentiment shows the positive/negative sentiment (using NaiveBayesClassifier) of the comments.

## Prerequisite :
_Python 3_

_pip(Python Package Index) :_

> $ sudo apt-get install python3-pip

_requests package :_

> $ sudo pip3 install requests

_lxml package :_

> $ sudo apt-get install libxml2-dev libxslt1-dev python-dev

> $ pip3 install lxml

_matplotlib package :_

> $ sudo pip3 install matplotlib

_nltk package :_

> $ sudo pip3 install nltk

_wordcloud package :_

> $ sudo pip3 install wordcloud

## Running the file :
First input the __API key__ in the file.

__CommentSentiment/comment_extract.py__

__FancySentiment/comment_downloader.py__

Then run the __driver.py__ file.


text:
# MongoDb - Aula 02 - Exercício
autor: Maicon Giovani LC Ferreira

## Crie uma database chamada be-mean-pokemons;

```
> use be-mean-pokemons
switched to db be-mean-pokemons

```
## Liste quais databases você possui nesse servidor;

```
> show dbs
be-mean            0.004GB
be-mean-instagram  0.000GB
be-mean-pokemons   0.000GB
local              0.000GB
test               0.000GB

```
## Liste quais coleções você possui nessa database;

```
>show collections
>

```

## Insira pelo menos 5 pokemons A SUA ESCOLHA;

```
var pokemon = [
	{'name':'Trevenant', 'description': 'It can control trees at will. It will trap people who harm the forest, so they can never leave.', 'type':'Ghost', 'attack': 110, 'defense': 76, 'height': 4.11},
	{'name':'Yveltal', 'description': 'When this legendary Pokémons wings and tail feathers spread wide and glow red, it absorbs the life force of living creatures.', 'type':'Dark', 'attack': 131, 'defense': 95, 'height': 19.00},
	{'name':'Steelix', 'description': 'Steelix lives even further underground than Onix. This Pokémon is known to dig toward the earths core. There are records of this Pokémon reaching a depth of over six-tenths of a mile underground.', 'type':'Steel', "attack": 85, "defense": 200, "height": 30.05},
	{'name':'Marowak', 'description': 'Marowak is the evolved form of a Cubone that has overcome its sadness at the loss of its mother and grown tough. This Pokémons tempered and hardened spirit is not easily broken.', 'type':'Ground', "attack": 80, "defense": 110, "height": 3.03},
	{'name':'Kadabra', 'description': 'Kadabra emits a peculiar alpha wave if it develops a headache. Only those people with a particularly strong psyche can hope to become a Trainer of this Pokémon.', 'type':'Psychic', "attack": 35, "defense": 30, "height": 4.03}]

	> db.pokemons.insert(pokemon)
	BulkWriteResult({
		"writeErrors" : [ ],
		"writeConcernErrors" : [ ],
		"nInserted" : 5,
		"nUpserted" : 0,
		"nMatched" : 0,
		"nModified" : 0,
		"nRemoved" : 0,
		"upserted" : [ ]
	})

```

## Liste os pokemons existentes na sua coleção;

```
> db.pokemons.find()
{ "_id" : ObjectId("57362f9b1bd514b027750cdb"), "name" : "Trevenant", "description" : "It can control trees at will. It will trap people who harm the forest, so they can never leave.", "type" : "Ghost", "attack" : 110, "defense" : 76, "height" : 4.11 }
{ "_id" : ObjectId("57362f9b1bd514b027750cdc"), "name" : "Yveltal", "description" : "When this legendary Pokémons wings and tail feathers spread wide and glow red, it absorbs the life force of living creatures.", "type" : "Dark", "attack" : 131, "defense" : 95, "height" : 19 }
{ "_id" : ObjectId("57362f9b1bd514b027750cdd"), "name" : "Steelix", "description" : "Steelix lives even further underground than Onix. This Pokémon is known to dig toward the earths core. There are records of this Pokémon reaching a depth of over six-tenths of a mile underground.", "type" : "Steel", "attack" : 85, "defense" : 200, "height" : 30.05 }
{ "_id" : ObjectId("57362f9b1bd514b027750cde"), "name" : "Marowak", "description" : "Marowak is the evolved form of a Cubone that has overcome its sadness at the loss of its mother and grown tough. This Pokémons tempered and hardened spirit is not easily broken.", "type" : "Ground", "attack" : 80, "defense" : 110, "height" : 3.03 }
{ "_id" : ObjectId("57362f9b1bd514b027750cdf"), "name" : "Kadabra", "description" : "Kadabra emits a peculiar alpha wave if it develops a headache. Only those people with a particularly strong psyche can hope to become a Trainer of this Pokémon.", "type" : "Psychic", "attack" : 35, "defense" : 30, "height" : 4.03 }

```

## Busque o pokemon da sua escolha, pelo nome, e armazene-o em uma variável chamada poke;

```
> var name = {'name':'Yveltal'}
> var poke = db.pokemons.findOne(name)
> poke
{
	"_id" : ObjectId("57362f9b1bd514b027750cdc"),
	"name" : "Yveltal",
	"description" : "When this legendary Pokémons wings and tail feathers spread wide and glow red, it absorbs the life force of living creatures.",
	"type" : "Dark",
	"attack" : 131,
	"defense" : 95,
	"height" : 19
}

```

## Modifique sua description e salvê-o;

```
> poke.description = 'Pokémon fadaum que avua e eu nunca peguei '
> db.pokemons.save(poke)
WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 })

```


text:
The proxy pattern provides a surrogate/placeholder for another object to control the access to it.

In simple words, it just adds additional behaviour to control the access to the underlying object.

repository: vigak/DesignPatterns

gha_language: Java

repo_name: vigak/DesignPatterns


text:
---
layout: post
title: Chapter 7 - Massive machine-type communications technologies (MTC)
category: Wireless Networking
description: MTC
---

# Massive machine-type communications technologies (MTC)

### IoT

-  Internet of Thing

![IOT](https://cdn-images-1.medium.com/max/1600/1*lVfJFrxmv5WYXnfm7Tbf3A.png)

### Consumer vs Industrial IoT domains

-  **Industrial IoT** is similar to the **consumer IoT**,
-  but the difference is that it has this is used in a commercial area that is **industries**.

![will industrial iot be bigger than consumer iot novotech](https://pbs.twimg.com/media/CGRbsRcVIAImNBP.png)

### Contemporary IoT connectivity Solution

-  ![img](https://www.murata.com/~/media/webrenewal/campaign/events/asean/es/connectivity/connect_7_world.ashx?la=en-sg&w=600)

-  They connect with each other using different standards for different applications

### Short-Range Access Technologies for IoT

-  **Historical** solutions (Bluetooth, IEEE 802.15.4, IETF stacks,…) are evolving to maintain competitiveness in growing IoT market
-  ***IEEE 802.11ah***(HaLow), low-cost, large-scale connectibity across massive deployments
-  ***Unlicensed Low-Power Wide Area (LPWA)*** networks rapidly emerge to support early stages of the IoT development, until standardized cellular M2M solutions enter the market.

![802.11ah](https://images.techhive.com/images/article/2016/01/wi-fi-802.11ah-100636515-primary.idge.jpg)

### Next-Generation Wireless IoT Technology

- **Fifth-generation** (5G) wireless technology is targeting to *offer support* for numerous **IoT applications**

![iOT_2](https://res.cloudinary.com/engineering-com/image/upload/w_640,h_640,c_limit,q_auto,f_auto/infographic-blazing-5G_leesa2.jpg)
![5G speed](https://static.techspot.com/articles-info/1582/images/2018-02-25-image.png)

### 5G Performance Targets Are Set Clearly

-  IMT-2020

![Diagram of the enhancement of key capabilities from IMT-Advanced to IMT-2020](https://pbs.twimg.com/media/Dm5p_lBWwAAmwTO.jpg:large)

![IMT-2020](https://i.imgur.com/5cWIiq4.png)

### Tactile Internet

-  The Tactile Internet will be the next evolution of the Internet of Things (IoT), encompassing human-to-machine and machine-to-machine interaction.
-  It will enable real-time interactive systems with a raft of industrial, societal and business use cases.

![Tactile Interent](https://i.imgur.com/PjUeQf0.png)

path: /_posts/Wireless Networking/2019-05-10-WN-07-Massive machine-type communications technologies (MTC).md

gha_language: HTML


text:
# No slug to handle the url http://lightning.simpdev.net/
Slug:
Title:  Lightning - Home
Menu:  Home
Enabled:  true
Position:  1

Lightning  - Following the path of least resistance.

##What is Lightning?

Lightning is a micro toolkit to simplify getting your content on your site, without getting in your way.  Lightning is open source and free.

It is made up of:

* An asp.net module to identify your content.
* Flat files to store your content.
* Markdown to parse your content.
* Razor to render your content.

##Features

* Simplicity.
	* The code:  Small, concise and clean.
	* Content:  Flat files.  Publish via ftp, dropbox, file share, xcopy, etc.
	* Deployment:  Deploy from source, ftp, dropbox, file share, xcopy, etc.  Simply as possible.
	* Ui:  Templates use razor to offer full flexibility.
* Speed.
	* Execution:  Less code means less cpu.
	* Caching:  Cache as much processing as possible.  Cache content reading and parsing.  Cache content processing.

##To do

There is lots to do.

* More testing.  There is no automated testing.
* More templates.  Give Lightning more style.
* More docs.  Define what Lightning can do.
* More examples.  Show how much power this simple toolkit has to offer.
* More everything.  The sky is the limit.

##License

Free for commercial and private use.

* Apache 2.0


text:
After unzipping the source code, you should run `install.sh`.
This will install dependencies and build BOLeRo. If you want
to use BOLeRo, you should source env.sh. This will set necessary
environment variables (PATH, LD_LIBRARY_PATH, ...). For
more details, take a look at our documentation online:

    https://rock-learning.github.io/bolero/

repository: rock-learning/bolero

gha_license_id: NOASSERTION

repo_name: rock-learning/bolero


text:
The Fat Man is a tactical nuclear catapult weapon.

According to terminals found inside the [Fort Strong][strong] armory in [Boston][boston], the Fat Man was conceived, developed and tested at the location. Houses were built to mimic an urban area, to see how much damage the weapon would cause in an urban environment.

The M42 Fat Man is an effective mortar/artillery weapon, allowing a person to bombard a large area with good precision and deadly force. It uses a [mini nuke][mini] for ammunition which when fired, results in a small nuclear blast.

[strong]: http://fallout.wikia.com/wiki/Fort_Strong_armory
[boston]: http://fallout.wikia.com/wiki/Boston
[mini]: http://fallout.wikia.com/wiki/Mini_nuke


text:
# BlockDemo

[![CI Status](https://img.shields.io/travis/peng-xiaohua/BlockDemo.svg?style=flat)](https://travis-ci.org/peng-xiaohua/BlockDemo)
[![Version](https://img.shields.io/cocoapods/v/BlockDemo.svg?style=flat)](https://cocoapods.org/pods/BlockDemo)
[![License](https://img.shields.io/cocoapods/l/BlockDemo.svg?style=flat)](https://cocoapods.org/pods/BlockDemo)
[![Platform](https://img.shields.io/cocoapods/p/BlockDemo.svg?style=flat)](https://cocoapods.org/pods/BlockDemo)

## Example

To run the example project, clone the repo, and run `pod install` from the Example directory first.

## Requirements

## Installation

BlockDemo is available through [CocoaPods](https://cocoapods.org). To install
it, simply add the following line to your Podfile:

```ruby
pod 'BlockDemo'
```

## Author

peng-xiaohua<EMAIL_ADDRESS>
## License

BlockDemo is available under the MIT license. See the LICENSE file for more info.

repository: peng-xiaohua/BlockDemo

repo_name: peng-xiaohua/BlockDemo


text:
# BPMN Backend

- Entry point: `BPMNDirectDiagramMarshaller` which implements `DiagramMarshaller`
- Actual unmarshalling from XML is delegated to Eclipse BPMN2 library
- Mapping between Eclipse BPMN2 data model to Stunner BPMN data model is performed through **Converter** classes

## Unmarshalling

Unmarshalling converts an **Eclipse BPMN2** document into a **Stunner Diagram**.
There are a few differences between the Eclipse BPMN2 data model and the Stunner graph representation:

BPMN is an XML document, therefore the Eclipse BPMN2 implementation exposes the document as a **tree**.

The tree of the BPMN2 model, however, contains 3 different subtrees:
1. the tree of flow elements (shapes of the diagram, including visible edges a.k.a. `SequenceFlow`s) rooted
   at the `bpmn2:process` element.
2. the tree of the layout of the shapes: rooted at`bpmndi:BPMNDiagram`, it contains `BPMNShape`s and `BPMNEdge`s with their
  coordinates on the canvas. These coordinates are **absolute**.
3. the tree of the simulation properties, rooted at `bpmn2:relationship`

Each section may refer to another; in particular, section 2. and 3. refer to
elements defined in section 1.; moreover there may be cross-references within elements of section 1.

The main differences with BPM are that
- in Stunner, Nodes and Edges are distinct entities, while, in a BPM document,
 SequenceFlows are represented together with other Elements
- each Stunner POJO aggregates all of 1., 2., 3.

In fact, a stunner `Node` represents an Element (e.g. a `Task`)
with all of its other properties, such as position on the canvas, simulation properties, etc.
There is also an additional constraint: coordinates may be relative to a container,
whereas they are always absolute in the BPMN2 model (e.g. a `Lane` may contain
a `Task`: in Stunner this `Task`'s position will be relative to the `Lane`'s.
but the `BPMNShape` will report absolute coordinates)

Although conversion can be seen as a **visit** of the BPMN2 document tree,
the entire visit is driven by the the `Process` subtree (1.), because it contains
all of the visible elements of the diagram. However, every time an element of the `Process`
subtree is visited, all of the potential cross-references must be resolved,
thus a `Context` wrapper has to be brought along.

The visit is implemented as a series of **`Converters`** that **delegate** to each other.
For instance, there is a Converter for `FlowElements` (children of the document root, `Definitions`)
that delegates to one Converter for each subtype of `FlowElement`, e.g., `TaskConverter`, `StartEventConverter`, etc.
Each of such converters checks the type of the element that is being visited,
and if it *matches* (that is, this converter is able to *convert* that type to a Node or an Edge),
then it dispatches the conversion, which results in returning
a Stunner `Node` or a Stunner `Edge`.

The visit is separate for nodes and edges. A few passes are implemented:

- a pass over the nodes, that is:
    - a pass over all child of a `Process`, excepted sequence flows; including
      `SubProcess`es, which may contain other children
    - a pass over the lanes (which are not included as children of a `Process`)

- a pass over the edges; includes
    - sequence flows, ignored in the previous pass
    - boundary elements, which are represented as a special kind of edge

Please also notice that the total number of Stunner edges is usually greater
that the number of edges in a BPM: in fact, in Stunner, edges may represent
both an edge that is **drawn** on the canvas, and a **relationship** between
two nodes. The former would be an element that has an actual representation
in the BPM; the latter encodes parent/child or docking relationships.
But, while the first kind of edges is actually generated during the
visit of BPM edges (SequenceFlows), the latter are really generated
during the visit of Nodes!

The parent/child edges form a "tree of subgraphs", whose root is the whole Diagram.
The Diagram "contains" other nodes of the graph (i.e., it has an edge to them);
and each Node inside such a graph may "contain" other nodes, in such a way,
that by walking all of the relationship edges, all of the nodes in the graph
are visited.

**Note.** For the reader familiar with common design patterns, because the visit is type-driven, it is -- of course --
implemented through a rendition of the traditional Visitor pattern. However, because the Visitor pattern
really implements a form of "pattern matching",  we have deemed more readable to implement a helper for "pattern matching"
(actually, *type matching*, see Section "Utilities" and the JavaDoc for details). Moreover,
as opposed to the Visitor pattern, this makes it possible to avoid defining an `accept()` method
on each Stunner POJO, leaving it agnostic to any implementation detail of this visit.

### Implementation

#### Converters To Stunner model

- A **Converter _to_ the Stunner model** is a class (basically, a function) that converts an Eclipse BPMN2 object into:

- a `BPMNNode`, i.e.:  a wrapper for a `Node<? extends View<? extends BPMNViewDefinition>, ?>` ,
 enhanced with:
     - ability to record parent/child relationship; in other words, a `BPMNNode` may be child/parent of other `BPMNode`s
     - ability to "contain" `BPMNEdge`s (see below); in other words a `BPMNNode` may represent a subgraph (e.g. in the case of a `(Sub)Process`)
- a `BPMNEdge`, i.e.: a wrapper for an `Edge<? extends View<? extends BPMNViewDefinition>, ?>`

- Converter classes form a delegation tree. The root of such a tree is the converter for the Diagram root, called "Process"
when converting *to* the Stunner model, called "ViewDefinitionConverter" when converting *from* the Stunner model.
The delegation tree follows the hierarchy and structure of the BPMN data model.

- For instance, a Process converter will convert all of the FlowElements contained in the Process section.
A suitable conversion method is invoked, depending on the type of each FlowElement. The way matching is done,
is describe through code, using a `Match` helper (see Utilities section)

- Each converter is responsible of handling a set of classes from Eclipse BPMN2 model. For instance,
  `TaskConverter` handles `Task`s. It instances a `Node`/`Edge` object (throught the `TypedFactoryManager` -- see below)
  for the recognized type, and fills its fields with all the supported values in the original model.
  At the end of the conversion it usually **return the element**, and/or, in some cases, it may **add it to the canvas**
  (e.g., subprocess converters return their subprocess node, but also add in their child nodes).

  Fields from the Eclipse BPMN2 model, for convenience, are generally accessed through a `PropertyReader`.

#### Property Readers

`PropertyReader`s are returned from a `PropertyReaderFactory`. They retrieve properties from
  each Eclipse BPMN2 instance especially implementing custom logic for
  extended drools-related attributes, such as
  - `<bpmn2:extensionElements>` (e.g. `elementname`)
  - `itemDefinition`s / `dataInput`s / `dataOutput`s (e.g. `Subject`, `Comment`)
  - attributes under the`drools:` namespace (e.g. `drools:docker`)
  - attributes under the `color:` namespace (e.g. `color:background-color`)
  - bounds/shape/edge data defined in the `BPMNDiagram/BPMNPlane/BPMNShape` section

  For instance, for `BusinesRuleTask task`:

      BusinessRuleTaskPropertyReader p = propertyReaderFactory.of(task);
      // look up the extended name under the `elementname` extension metadata,
      // falling back onto the regular <bpmn2:businessRuleTask name="...">
      String name = p.getName();

      // look for the documentation sequence and return a string
      String documentation = p.getDocumentation();

      // returns a stunner-compatible representation of the coordinates, bounds
      // of this element
      Bounds b = p.getBounds();

      // returns background formatting of the element
      BackgroundSet backgroundSet = p.getBackgroundSet();

      // ... etc.

See [docs/extending.md] for more information on extending PropertyReaders.

#### GraphBuilder

A `GraphBuilder` object issues commands to the canvas while building the graph.
  It is a wrapper around:
   - `GraphCommandExecutionContext`
   - `GraphCommandFactory`
   - `GraphCommandManager`

`GraphBuilder` is used for convenience, to avoid explicitly creating command instances.
 It also implements custom logic for some actions. For example, in the case of adding child nodes,
 it translates the coordinates of a child node into the new reference system (the parent boundaries).

`GraphBuilder` builds the entire graph (`GraphBuilder#buildGraph(BpmnNode)`)
once all the conversions have took place: it traverses the entire directed graph described by the `BPMNNode`s
starting from the "root node", which represents the root of the diagram, and visiting
the parent/child relations in each BPMNNode and the `BPMNEdge` they may contain.

## Marshalling

In this case we visit the Stunner graph and convert it back into a BPMN2 tree.

The Stunner graph is represented as a bag of nodes. Each node contains references
to its **inbound** edges and its **outgoing** edges.

The visit is performed as follows: first the "root node" of the diagram is found,
then we implement the following passes

- nodes:
    - a pass over the root process node
    - then, a pass on all non-root nodes, including
        - a pass over all subprocesses (with all its subchildren)
        - a pass over all lanes

- let us now call E the union of all inbound and outgoing edges for all nodes in the Graph;
  then the folowing passes are implemented
    - a pass over all Child edges in E
    - a pass over all Dock edges in E
    - a pass over all SequenceFlow edges in E

During this passes, all the references to the graph nodes are resolved as
correctly assigned to the BPM nodes.

### Converters From Stunner Model

A **Converter _from_ the Stunner model** is a class that converts a
Stunner `Node<? extends View<? extends BPMNViewDefinition>, ?>` to a `PropertyWriter`. A `PropertyWriter`
is a wrapper around an Eclipse BPMN2 element (see below)

#### Property Writers

`PropertyWriter`s are returned from a `PropertyWriterFactory`. They store properties to
  each Eclipse BPMN2 instance especially implementing custom logic for
  extended drools-related attributes, such as
  - `<bpmn2:extensionElements>` (e.g. `elementname`)
  - `itemDefinition`s / `dataInput`s / `dataOutput`s (e.g. `Subject`, `Comment`)
  - attributes under the`drools:` namespace (e.g. `drools:docker`)
  - attributes under the `color:` namespace (e.g. `color:background-color`)
  - bounds/shape/edge data defined in the `BPMNDiagram/BPMNPlane/BPMNShape` section

  For instance, for `BusinesRuleTask task`:

      BusinessRuleTaskPropertyReader p = propertyWriterFactory.of(task);
      // write the extended name under the `elementname` extension metadata,
      // and add a regular (whitespace trimmed) <bpmn2:businessRuleTask name="...">
      p.setName(name);

      // look set the documentation sequence from the given string
      p.setDocumentation(documentation);

      // converts stunner representation of the coordinates to bounds
      // of this element
      p.setBounds(node.getContent().getBounds());

      // ... etc.

See [docs/extending.md] for more information on extending PropertyWriters.

### Utilities

#### Custom Attributes, Elements

Custom attributes and elements have been defined in form of singletons under the `customproperties`
subpackage of `org.kie.workbench.common.stunner.bpmn.backend.converters`.

Under this package, we define `CustomAttribute`s (such as `"drools:packageName"`),
`CustomElement`s such as `<elementname>` in the form of singleton objects that read/write
such attributes to a given element.

For example:

    public String getPackage() {
        return CustomAttribute.packageName.of(element).get();
    }

    public void setPackage(String value) {
        CustomAttribute.packageName.of(process).set(value);
    }

Please notice that these singletons are not supposed to be used directly,
but their getters and setters will be generally wrapped in a `PropertyReader`
or `PropertyWriter`, respectively. For instance `getPackage()` is a member
of `ProcessPropertyReader`, and `setPackage()` is a member of `ProcessPropertyWriter`.

#### Misc

In order to minimize casts (mostly for legibility, cosmetic reasons) the following classes exist:

   - `TypedFactoryManager`: a wrapper around `FactoryManager` that creates
     an instance of `Node<T,U>`, `Edge<T,U>`, `Graph<T,U>`, with proper type parameters. Examples:

         Node<View<StartNoneEvent>, Edge> node =
            factoryManager.newNode(nodeId, StartNoneEvent.class);

        Graph<DefinitionSet, Node> graph =
                typedFactoryManager.newGraph(
                        definitionsId, BPMNDefinitionSet.class);

   - `Match` and `VoidMatch` provide a fluent interface to type matching (`instanceof`)
      avoiding explicit casts. Moreover it provides shorthands for skipping unhandled types (`ignore()`)
      or marking them as currently unsupported (`missing()`). Each branch of a `Match`
      expects a `Function` that consumes the input and returns a `Node<T,U>` or an `Edge<T,U>`.
      A `VoidMatch` implements a side-effecting `Match`, i.e. a `Match` that does not return a value.

      An example from `TaskConverter`:

              // a match for Task subclasses that returns Node<? extends View<? extends BPMNViewDefinition?>>
              Match.ofNode(Task.class, BPMNViewDefinition.class)
                      .when(org.eclipse.bpmn2.BusinessRuleTask.class, t -> {
                          // t is already casted to BusinessRuleTask
                          Node<View<BusinessRuleTask>, Edge> node =
                            factoryManager.newNode(t.getId(), BusinessRuleTask.class);
                            BusinessRuleTask definition = node.getContent().getDefinition();
                            BusinessRuleTaskPropertyReader p = propertyReaderFactory.of(task);

                            definition.setGeneral(new TaskGeneralSet(
                                    new Name(p.getName()),
                                    new Documentation(p.getDocumentation())
                            ));

                          ...
                          return node;
                      })
                      .when(org.eclipse.bpmn2.ScriptTask.class, t -> { ... })
                      .when(org.eclipse.bpmn2.UserTask.class, userTaskConverter::convert) // method references
                      .missing(org.eclipse.bpmn2.ServiceTask.class) // report this as missing
                      .missing(org.eclipse.bpmn2.ManualTask.class)
                      .ignore(SomeClassYouSkip.class)
                      .orElse(t -> {
                          /* handle the default case: NoneTask */
                      })
                      .apply(task)
                      .asSuccess().value();

repository: danielzhe/kie-wb-common

repo_name: danielzhe/kie-wb-common


text:
# Posts Library

#### This project uses react-router-dom and has multiple pages. It aim is to has posts and offer functionality for adding and removing them. It uses the API provided from http://reduxblog.herokuapp.com/

#### How to start:
     1.Install NodeJs
     2.Run commands:
     * 'npm install' in the project root directory
     * 'npm start' in the project root directory
     3. Open 'localhost:8080'

     Note: Webpack will build automatically after every save

repository: branimir-kirilov/Learning-React

repo_name: branimir-kirilov/Learning-React


text:
---
title: 'reset - CLI command'
description: 'Clears all the cached Nx artifacts and metadata about the workspace and shuts down the Nx Daemon.'
---

# reset

Clears all the cached Nx artifacts and metadata about the workspace and shuts down the Nx Daemon.

## Usage

```shell
nx reset
```

Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`.

repository: nrwl/nx

gha_language: TypeScript

repo_name: nrwl/nx


text:
---
title: "Apache Redirect for http to https via .htaccess"
date: 2020-07-10T00:20:25+08:00
tags: [apache, webserver, .htaccess, redirect]
draft: false
---

Generic way to do it but would result into duplicate URLs, e.g. https://example.com & https://www.example.com
```
RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
```

To avoid the duplicate URLs, do the following:
```
## 1. Redirect all non-https except www to https://www
RewriteCond %{HTTP_HOST} !foo\.example\.com [NC]  # exclude foo.example.com domain
RewriteCond %{HTTP_HOST} !bar\.example\.net [NC]  # exclude foo.example.net domain
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

## 2. Redirect for http://www to https://www
## NOTE: HTTP_HOST already starts with "www" (e.g. www.example.com) so it's no longer
## hardcoded in the RewriteRule. Otherwise, it would become www.www.example.com which
## is clearly wrong.
RewriteCond %{HTTP_HOST} !foo\.example\.com [NC]  # exclude foo.example.com domain
RewriteCond %{HTTP_HOST} !bar\.example\.net [NC]  # exclude foo.example.net domain
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

## 3. Redirect all https to https://www except those https://www
RewriteCond %{HTTP_HOST} !foo\.example\.com [NC]  # exclude foo.example.com domain
RewriteCond %{HTTP_HOST} !bar\.example\.net [NC]  # exclude foo.example.net domain
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTP:X-Forwarded-Proto} https
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
```

See https://www.drupal.org/docs/7/modules/domain-access/htaccess-changes-optional for some other examples.

repository: icasimpan/quicktasks-webserver

repo_name: icasimpan/quicktasks-webserver


text:
# TeaLinuxOS XI Website
This site is built with Hugo. Pull requests welcome!

## Developing
Start a dev server at localhost:1313

## NOTE
>
for local development change on `config.toml` > `baseURL` value to **http://localhost:1313**
which in production setting change to **your.domain.example**


text:
Role Name
=========

Install Prometheus Blackbox_Exporter from github repository

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

nope

Role Variables
--------------

all variables are defined in defaults:

```yaml
---
# defaults file for blackbox_exporter

prometheus_user: prometheus
prometheus_group: prometheus
prometheus_install_path: '/opt/prometheus'
prometheus_config_path: '/etc/prometheus'
prometheus_pid_path: '/var/run/prometheus'
prometheus_loglevel: 'info'

prometheus_blackbox_exporter_install_path: '{{ prometheus_install_path }}'
prometheus_blackbox_exporter_config_path: '{{ prometheus_config_path }}'
prometheus_blackbox_exporter_pid_path: '{{ prometheus_pid_path }}'
prometheus_blackbox_exporter_user: '{{ prometheus_user }}'
prometheus_blackbox_exporter_group: '{{ prometheus_group }}'
prometheus_blackbox_exporter_loglevel: '{{ prometheus_loglevel }}'
prometheus_blackbox_exporter_listen: '{{ prometheus_blackbox_exporter_listen_ip }}:{{ prometheus_blackbox_exporter_listen_port }}'
prometheus_blackbox_exporter_listen_port: '9115'
prometheus_blackbox_exporter_listen_ip: ''
prometheus_blackbox_exporter_version: '0.14.0'
prometheus_blackbox_exporter_config: 'blackbox.yml'

enable_ufw: false
prometheus_blackbox_exporter_src_access:
  - "{{ ansible_default_ipv4.network }}/{{ ansible_default_ipv4.netmask }}"
```

For typical deployment you can eventually define enable ufw fw and define src access list
Based on defined variables you can set variables common for all prometheus stack

Dependencies
------------

If you want to set fw, you need to have ufw role

Example Playbook
----------------

Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:

```yaml
    - hosts: servers
      roles:
         - role: blackbox_exporter
```

License
-------

BSD

Author Information
------------------

Tomasz Baczynski


text:
# Fitness Flow
  ![license](https://img.shields.io/badge/license-MIT-critical?./license/MIT)

  ## Description
This project was designed to allow fitness enthusiasts, athletes and newcomers a place to interact and comment with other fitness enthusiasts.

  * Link for Heroku deployment [Heroku](https://fitnessflow.herokuapp.com/)
  * Link for GitHub Repository [GitHub](https://github.com/jidlebir/FitnessFlow.git)

  ## Table of Contents
  * [Installation](#Installation)
  * [Usage](#Usage)
  * [License](#License)
  * [Languages](#Languages)

  * [Questions](##Questions)

  ## Installation
    This application is deployed to Heroku. Use the above Heroku link to access the app. If you are a new user, select the "login" button and "sign up" to have full access.

  ## Usage
    This application requires a new user to sign up with the following:
    * Email
    * Username
    * Password (Length min 4 characters)
    * Once a user account is created you have the ability to add comments to other users posts. You have the ability to add, edit update and delete your posts.
    * Security - This blog will automatically log you out after two minutes of inactivity to safeguard unauthorized access to your posts and comments.

  ![image](./public/img/fitnessflow.PNG)

  ## Languages
  ![language](https://img.shields.io/badge/JavaScript-critical)  ![language](https://img.shields.io/badge/ES6-critical)  ![language](https://img.shields.io/badge/Node-critical)
  ![language](https://img.shields.io/badge/Insomnia-critical)  ![language](https://img.shields.io/badge/mysql2-critical)  ![language](https://img.shields.io/badge/Express-critical)  ![language](https://img.shields.io/badge/Sequelize-critical)  ![language](https://img.shields.io/badge/Handlebars-critical) ![language](https://img.shields.io/badge/dotenv-critical) ![language](https://img.shields.io/badge/bcrypt-critical) ![language](https://img.shields.io/badge/JawsDB-mySQL-critical) ![language](https://img.shields.io/badge/Express-Session-critical) ![language](https://img.shields.io/badge/Semantic-critical)

  ## License
  ![license](https://img.shields.io/badge/license-MIT-critical)

  This application currently is licensed with MIT.

  ## Contribute
  Contributor privileges are open to ALL that want to positively contribute to this project

  ## Questions
  Please feel free to email us with any comments, questions or concerns at<EMAIL_ADDRESS>
  A7063P [GitHub Account](https://github.com/a7063p)
  Jidlebir [GitHub Account](https://github.com/jidlebir)
  JenMol86 [GitHub Account](https://github.com/JenMol86)
  AbigailGAdams [GitHub Account](https://github.com/abigailGadams)

repository: abigailGadams/FitnessFlow

repo_name: abigailGadams/FitnessFlow