text:
---
layout: post
title: "PCB Ruler"
date: 2019-10-10
---

Note: code for this project is available
[here](https://github.com/mwyoung/Adafruit-PCB-Ruler).

### Project Goals
The main goals of this project was to create a ruler with more footprints than the
[Adafruit PCB Ruler](https://github.com/adafruit/Adafruit-PCB-Ruler) it was based on. This
design also is only 101mm in length so that it can be built very cheaply at PCB
manufactures such as JLCPCB.

Please also note that this ruler is **for reference only**, and should not be used for
precise measurements. Finally, like the Adafruit ruler it is under a CC BY-SA 3.0 license.

### Changes
The major changes compared to Version 1 (below) is that all of the parts used come from
either KiCad built-in libraries or KiCad online libraries
([Jumper.pretty](https://github.com/mwyoung/Adafruit-PCB-Ruler/tree/master/Jumper.pretty)
and
[Package_BGA.pretty](https://github.com/mwyoung/Adafruit-PCB-Ruler/tree/master/Package_BGA.pretty),
with update scripts for the latest version included).

Other changes include reformatting the drill holes to go up every 2 interval, parts, the
scales, a schematic for adding parts easier, and tying all of the pin 1s together to make
it easier to distinguish which one is which. The ruler now has inches in both 1/10 and
1/16 along with 100mm along with a protractor with 15° markers. Finally, there is more
resistors, diodes, transistors, QF\* and BGA parts on the ruler along with 1 to 2.54 mm
holes for pins.

### Images

Note: JLCJLCJLCJLC option is for JLCPCB to place the text of the printing. If using this
supplier, make sure the board is 1.6mm is width so it does not bend, and can also be added
onto another order for ~$4 for 5 PCB rulers.

### Version 1
The [first version](https://github.com/mwyoung/Adafruit-PCB-Ruler/tree/v1-ruler) of the
ruler only contains parts from the Adafruit ruler and a bit more information. It has also
been adapted to the KiCad format along with being 101mm in length. The only major changes
in this version is reorganization, moving some drill holes, and removing the Adafruit logo
(but still leaving attribution).

#### Images

Images


text:
## 2.Abbreviations and Definitions

Abbreviations used in this document are collected in the table below

---------------------------------------------------------
Abbreviation     Meaning
------------     ----------------------------------------
**BT**               Bluetooth

**CID**              Center Information Display

**DID**              Data Identifier

**DTC**              Diagnostic Trouble Code

**ECU**              Electronic Control unit

**GPS**              Global Positioning System

**GUI**              Graphical User Interface

**HDOP**             Horizontal Dilution of Precision

**HMI**              Human Machine Interface

**IVI**              In Vehicle Infotainment

**JSON**             JavaScript Object Notation

**PDOP**             Positional Dilution of Position

**RPC**              Remote Procedure Call

**SDE**              Software Development Environment

**SDL**              SmartDeviceLink

**SEE**              Software Engineering Environment

**TTS**              Text To Speech

**VDOP**             Vertical Dilution of Precision

**VR**               Voice Recognition

**UTC**              Universal Time Coordinate

------------------------------------------------------------

The list of terms used in the document and their definitions is provided in the table below.

+-------------------------------+------------------------------------------------------------------------------------------------------+
| **Term**                      | **Definition**                                                                                |
+===============================+======================================================================================================+
| Data Identifier (DID)         | Addressed memory locations of the ECU.                                                               |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| Diagnostic Trouble Code       | In the automotive industry, codes that are prescribed by SAE standards to help track problems in a  vehicle detected by its on-board computer.                                                                                |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| JSON                          | Is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for     machines to parse and generate.
- Is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages.                                                                                |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| GPS                           | The Global Positioning System is a space-based satellite navigation system that provides location (using not less than four satellites simultaneously) and time information to anyone who exploits GPS    receiver. When installed in a car, a GPS unit can provide useful information about the car's position  and the best travel routes to a given destination.            |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| E911 override                 | Occurs in case of a car accident – when the airbag deploys or, in certain vehicles, the emergency fuel pump shutoff is activated. The vehicle system (in case of relevant version) should react inappropriate way [3] when this override happens.                                                                                |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| VR                            | Voice recognition is the technology by which sounds, words or phrases spoken by humans are converted into electrical signals and these signals are transformed into coding patterns to which meaning has been assigned.
Relating to automotive, voice recognition aims to enable drivers to control entertainment and navigation systems simply by using their voices.     |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| Command                       | This is an option that a user can select either via voice recognition (VR) or through the on-screen menu during a user-initiated interaction.                                                                                |
+-------------------------------+------------------------------------------------------------------------------------------------------+
| Phoneme                       | A phoneme is the basic unit of sound in a language.                                                  |
+-------------------------------+------------------------------------------------------------------------------------------------------+

repository: KhrystynaDubovyk/RequirementsTest

branch_name: refs/heads/master

extension: md

filename: 02.Abbreviations and Definitions.md

gha_language: Lua

license_type: permissive

repo_name: KhrystynaDubovyk/RequirementsTest


text:
# STAC API - Core Specification

- [STAC API - Core Specification](#stac-api---core-specification)
  - [Link Relations](#link-relations)
  - [Example Landing Page for STAC API - Core](#example-landing-page-for-stac-api---core)
  - [Extensions](#extensions)

- **OpenAPI specification:** [openapi.yaml](openapi.yaml) describes the core endpoints ([rendered version](https://api.stacspec.org/v1.0.0-beta.3/core)),
  and [commons.yaml](commons.yaml) is the OpenAPI version of the core [STAC spec](../stac-spec) JSON Schemas.
- **Conformance URI:** <https://api.stacspec.org/v1.0.0-beta.3/core>
- **Extension [Maturity Classification](../extensions.md#extension-maturity):** Pilot
- **Dependencies**: None

The base of a STAC API is its landing page. This resource is the starting point to discover what behaviors
the API supports via the `conformsTo` values and link relations.
This behavior in a RESTful API is known as
[Hypermedia as the Engine of Application State (HATEOAS)](https://en.wikipedia.org/wiki/HATEOAS).
STAC API relies heavily on hypermedia for API resource navigation.

There are a few requirements for the returned document:

- The returned JSON must be a valid [STAC Catalog](../stac-spec/catalog-spec/catalog-spec.md), and it can provide any number of 'child' links
to navigate down to additional Catalog, [Collection](../stac-spec/collection-spec/README.md), and [Item](../stac-spec/item-spec/README.md) objects.
- The `links` section is a required part of STAC Catalog, and serves as the list of API endpoints. These can live at any location, the
client must inspect the the `rel` (relationship) to understand what capabilities are offered at each location.
- The `conformsTo` section must provide the capabilities of this service. This is the field
  that indicates to clients that this is a STAC API and how to access conformance classes, including this
  one. The relevant conformance URI's are listed in each part of the
  API specification. If a conformance URI is listed then the service must implement all of the required capabilities.

Note the `conformsTo` JSON object follows exactly the structure of OGC API - Features [declaration of conformance
classes](http://docs.opengeospatial.org/is/17-069r3/17-069r3.html#_declaration_of_conformance_classes), except is available directly under
the landing page. This is a slight break from how OGC API does things, as STAC feels it is important for clients to be able to understand
conformance in a single request. Implementers choosing to also implement the OGC API - Features and/or
STAC API - Features conformance classes must also implment the `/conformance` endpoint.

This particular catalog provides the ability to browse down to child STAC Collection objects through its `child` links, and also provides the search
endpoint to be able to search across items in its collections. Note though that none of those links are required, other servers may provide
different conformance classes and a different set of links.

The only requirements of the STAC API core class are to provide a valid STAC Catalog that includes a valid `conformsTo` JSON object
in it. Any API implementing that is considered a valid STAC API, and clients can inspect the document to figure out what other
capabilities are on offer and how to reach them.

The root endpoint (`/`) is most useful when it presents a complete `Catalog` representation of all the data contained in the API, such
that all `Collection` and `Item` objects can be navigated to by transitively traversing links from this root. This spec does not require any
API endpoints from OAFeat or STAC API to be implemented, so the following links may not exist if the endpoint has not been implemented.

## Link Relations

The following Link relations should exist in the Landing Page (root).

| **rel**        | **href**             | **From**       | **Description**                                                                                |
| -------------- | -------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `root`         | `/`                  | STAC Core      | The root URI                                                                                |
| `self`         | `/`                  | OAFeat         | Self reference, same as root URI                                                                                |
| `service-desc` | `/api` (recommended) | OAFeat OpenAPI | The OpenAPI service description. Uses the `application/vnd.oai.openapi+json;version=3.0` media type to refer to the OpenAPI 3.0 document that defines the service's API |
| `child`        | various              | STAC Core      | The child STAC Catalogs & Collections. Provides curated paths to get to STAC Collection and Item objects                                                                |

Additionally, a `service-doc` endpoint is recommended.

| **rel**       | **href**                  | **From**       | **Description**                                                                                |
| ------------- | ------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------- |
| `service-doc` | `/api.html` (recommended) | OAFeat OpenAPI | An HTML service description.  Uses the `text/html` media type to refer to a human-consumable description of the service |

It is also valid to have `item` links from the landing page, but most STAC API services are used to
serve up a large number of features, so they typically
use several layers of intermediate `child` links before getting to Item objects.  Note that the `items` (plural)
link will be used by APIs implementing STAC API - Features to link from a Collection to the items in that collection.

## Example Landing Page for STAC API - Core

This JSON is what would be expected from an api that only implements STAC API - Core. In practice,
most APIs will also implement other conformance classes, and those will be reflected in the `links` and
`conformsTo` fields.  A more typical Landing Page example is in
the [overview](../overview.md#example-landing-page) document.

```json
{
    "stac_version": "1.0.0",
    "id": "example-stac",
    "title": "A simple STAC API Example",
    "description": "This Catalog aims to demonstrate the a simple landing page",
    "conformsTo" : [
        "https://api.stacspec.org/v1.0.0-beta.3/core"
    ],
    "links": [
        {
            "rel": "self",
            "type": "application/json",
            "href": "https://stacserver.org"
        },
        {
            "rel": "root",
            "type": "application/json",
            "href": "https://stacserver.org"
        },
        {
            "rel": "service-desc",
            "type": "application/vnd.oai.openapi+json;version=3.0",
            "href": "https://stacserver.org/api"
        },
        {
            "rel": "service-doc",
            "type": "text/html",
            "href": "https://stacserver.org/api.html"
        },
        {
            "rel": "child",
            "type": "application/json",
            "href": "https://stacserver.org/collections/sentinel-2",
        },
        {
            "rel": "child",
            "type": "application/json",
            "href": "https://stacserver.org/collections/landsat-8",
        }
    ]
}
```

## Extensions

None.

repository: sbrunato/stac-api-spec

repo_name: sbrunato/stac-api-spec


text:
# Dispatch

[![Latest Stable Version](https://poser.pugx.org/packaged/dispatch/version.png)](https://packagist.org/packages/packaged/dispatch)
[![Total Downloads](https://poser.pugx.org/packaged/dispatch/d/total.png)](https://packagist.org/packages/packaged/dispatch)
[![Build Status](https://travis-ci.org/packaged/dispatch.png)](https://travis-ci.org/packaged/dispatch)
[![Dependency Status](https://www.versioneye.com/php/packaged:dispatch/badge.png)](https://www.versioneye.com/php/packaged:dispatch)
[![HHVM Status](http://hhvm.h4cc.de/badge/packaged/dispatch.png)](http://hhvm.h4cc.de/package/packaged/dispatch)
[![Coverage Status](https://coveralls.io/repos/packaged/dispatch/badge.png)](https://coveralls.io/r/packaged/dispatch)

Asset Management Middleware for Stack PHP

## Basic Installation

The following should be included in your public/index.php file

    $dispatchConfig = new \Packaged\Config\Provider\ConfigSection('dispatch');
    $dispatchConfig->addItem('run_on', 'path');
    $dispatchConfig->addItem('run_match', 'assets');
    $dispatchConfig->addItem('aliases', ['ali' => 'src/res']);
    $dispatchConfig->addItem('css_config', ['minify' => 'false']);
    $dispatchConfig->addItem('ext_config', [/*Config Options*/]);

    $dispatcher = new \Packaged\Dispatch\Dispatch($app, $dispatchConfig);
    $dispatcher->setBaseDirectory(dirname(__DIR__));

    //By md5 hashing the files based on the project root, runtime hashes are
    //not required, and will perform much faster
    $dispatcher->setFileHashTable(
      [
        'src/res/css/base.css' => 'd5364e0d4c0174e4a30cea9a03af036d',
        'assets/003.JPG'       => '8c0d1206f71976e45cd138ed30645519'
      ]
    );

You can then add into the request through either

Stack PHP Method

    $app = (new \Stack\Builder())
      ->push([$dispatcher, 'prepare'])
      ->resolve($app);

Raw Call

    $app = $dispatch->handle($request)

### Using Dispatch

There are a few types of asset manager you can use to generate static resource
uris.  An asset manager defines a route path by which processing should start
 when searching for your specified resources.

#### Config Options

##### run\_on / run_match

These options determine how asset paths are generated.

| run\_on Option | run_match Default | Description                            |
| ------------- | ----------------- | -------------------------------------- |
| path          | res               | //domain.tld/ **res** /*resource_url*    |
| subdomain     | static.           | // **static.** domain.tld/*resource_url* |
| domain        | (current domain)  | // **domain.tld** /*resource_url*        |

#### Asset Type

    $am = \Packaged\Dispatch\AssetManager::assetType();

By default, this type will search in /assets, assuming you want to store your
assets within that folder in the base of your project.  If you want to change
the default assets path, you can use the 'assets_dir' config item, relative to
your project base.

#### Alias Type

    $am = \Packaged\Dispatch\AssetManager::aliasType('alias');

Alias types are used for common paths, which you may want to group assets,
which could be a deep path within your source or vendor directories.
Aliases can be configured in the config as a keyed array within the 'aliases'
config item

#### Source Type

    $am = \Packaged\Dispatch\AssetManager::sourceType();

Source type will load data from your source folder.  By default this is 'src'
however, if you store your source files in another directory, this can be
changed using the 'source_dir' config item.

#### Vendor Type

    $am = \Packaged\Dispatch\AssetManager::vendorType('vendor','package');

Vendor type will set the base to a vendors folder specified by composer, this
will usually be /vendor/{vendor}/{package}

#### Automatic Detection

    $am = new \Packaged\Dispatch\AssetManager(new Class());

By passing through a class into the constructor for the asset manager, dispatch
will automatically detect to see if the class is within your source directory
or created by a vendor package.  This will give you either a vendor type or
source type.

### Generating Resource Uris

Now you have your asset manager object, you can generate resource uris to use
within your project.  All you need to do is pass the relative path (from the
asset manager base), to the method 'getResourceUri', and a full uri will be
returned.

    <!--[if lt IE 9]>
    <script src="<?= $am->getResourceUri('javascripts/ie.js'); ?>"></script>
    <![endif]-->

### CSS & JS Global Store

For simplicity within your code, you are also able to add css and js files to a
store for the render, which can be pulled out on demand.  This allows you to
include relevant css or js files based on sub classes, controllers views etc and
in a global layout, simply include any that have been built up.

To include your css files, you just need to call requireCss on your assetManager

    $am->requireCss(
      [
        'stylesheets/bootstrap',
        'stylesheets/theme',
        'stylesheets/widgets',
      ]
    );

You can also include css files with options for things like delayed js or print

    $am->requireCss('stylesheets/print',['media' => 'print']);

To then render the urls out to the page, you have two options.

Option 1.  Get the uris yourself, with their options, and render them

    $uris = AssetManager::getUrisByType('css');
    //Options is a key value array or options sent through by requireCss
    foreach($uris as $uri => $options)
    {
      echo '<link href="'. $uri .'" rel="stylesheet" type="text/css">';
    }

The same functionality is also available for javascript, by replacing css
with js in method names and parameters.

We recommed using AssetManager::TYPE_CSS and AssetManager::TYPE_JS within your
code, however, for shorter examples, the string version is also valid.

## Custom Asset Types

Custom assets are used if you need an asset to be dispatched with a specific
mime type, or your asset must be rendered or compiled before being dispatched.
Simply create a class implementing IAsset (you can extend AbstractAsset) and
register it with AssetResponse.

The following example will cause all requested files with the extension 'ext' to
be served with the 'application/x-my-asset' content type, and return an MD5 hash
of the file contents.

    class MyAsset extends AbstractAsset
    {
      public function getExtension()
      {
        return 'ext';
      }

      public function getContentType()
      {
        return "application/x-my-asset";
      }

      public function getContent()
      {
        return md5(parent::getContent());
      }
    }

    AssetResponse::addAssetType('ext', '\MyAsset');

repository: AmiSMB/bbkdisplay

repo_name: AmiSMB/bbkdisplay


text:
Clone the repository.

Edit config.yaml providing your callsign, password, and a list of stations to monitor.

And then
```
pip3 install aprslib
pip3 install pyyaml
pip3 install flask-restful
pip3 install flask_cors

sudo apt-get install python3-twisted
```
Now edit stationservice.service:
1.  WorkingDirectory should be where you cloned the repository.
1.  Environment should be where your site packages are, and the current working directory.
```
sudo cp stationservice.service /etc/systemd/user/stationservice.service
sudo systemctl daemon-reload
```

Start the service with `sudo systemctl start stationservice.service`.
Stop the service with `sudo systemctl stop stationservice.service`.


text:
# novaway/elasticsearch-bundle

A bundle to add debug information to elasticsearch/elasticsearch and ruflin/elastica in your Symfony Applications

## Usage

The bundle provides a Elastica\Client override, throwing events during search, and displaying it in the symfony toolbar.

## Installation
```
composer require novaway/elasticsearch-bundle
```

## Service configuration

You probably want to register the Novaway\ElasticsearchBundle\Elastica\Client as a service, and set Elastica\Client as its alias
```yml
# config/services.yaml
services:
...
    Novaway\ElasticsearchBundle\Elastica\Client:
        arguments:
            $config:
                url: '%elasticsearch_host%'

    Elastica\Client: '@Novaway\ElasticsearchBundle\Elastica\Client'
```
And voila, when you use this client for search, the queries and requests will be collected, and added to the SymfonyToolbar

## Configuration

```yml
# config/package/novaway_elasticsearch.yaml
novaway_elasticsearch:
    logging:
        enabled: false # if true, log every search request with a LoggerInterface service
        logger: 'logger' #the logger service id
```

## License

This bundle is under the MIT license. See the complete license [in the bundle](https://github.com/novaway/elasticsearch-bundle/blob/master/LICENSE)

license: MIT

repository: novaway/elasticsearch-bundle

gha_language: PHP

gha_license_id: MIT

repo_name: novaway/elasticsearch-bundle


text:
# Game of Life in parallel

This project is focused on the implementation of [Conway's Game of Life](https://en.wikipedia.org/wiki/Conway%27s_Game_of_Life) with parallel processing. The following techonologies were used: MPI, OpenMp and CUDA. In total 6 programs were made in order to create meaningful benchmarks:
* simple serial C program
* MPI with serial I/O
* MPI with async I/O
* MPI with collective I/O
* MPI with collective I/O + OpenMP
* CUDA

## Getting Started

The following steps are required in order to set up your enviroment and run the above programs.

### Prerequisites

At first you will need to ensure that you have a compiler compatible with OpenMP. Use the following command to check the version of `gcc` that you are using (version 4.4 or newer is required):
```
gcc --version
```
Then you will need to install MPI and CUDA.
```
sudo apt-get install mpich
sudo apt-get install nvidia-cuda-toolkit
```

### Installing

1) Get a copy of the project
```
git clone https://github.com/v-pap/Game-of-Life-in-parallel.git
```
2) Go into the directory
```
cd Game of Life
```
3) Choose which version you would like to build
```
make <version_name>
```

Where `<version_name>` can be `game`, `cuda`, `mpi`, `async`, `collective` or `openmp`.

## Using the program(s)

In order to run the program(s) you will have to use one one of the following commands:

* For the simple C program and the CUDA version
```
./a.out <width> <height> <input_file>
```
* For all the MPI or MPI + OpenMP versions
```
mpiexec -n <x> ./a.out <width> <height> <input_file>
```

Notes about the arguments:

The `<input_file>` must be a text file containing `<height>` rows and `<width>` columns and the acceptable values are `0` or `1` (in the current version of the project width should be equal to height). The script `generate.sh` generates valid inputs with randomized values.

Once the executable of any version of the Game of Life has finished running, an output file will be generated which contains the array of the last generation that was calculated.

Each source file contains two constants, `GEN_LIMIT` and `SIMILARITY_FREQUENCY` (which are defined on the preprocessor section). The default values are 1000 and 3 respectively and their values can be changed (this requires recompilation of the source file). The `GEN_LIMIT` constant describes the maximum amount of generations to be calculated. The `SIMILARITY_FREQUENCY` constant describes how often two consecutive generations will be compared for similarity. If the two generations are found similar then the program will exit. The removal of the similarity check can be achieved by removing the `#define CHECK_SIMILARITY` macro and then recompiling the source file.

## Authors

* [v-pap](https://github.com/v-pap)

* [vsakkas](https://github.com/vsakkas)

* [aakordas](https://github.com/mahcloudservers)

## License

This project is licensed under the MIT License


text:
# Project 1  [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Chuck Norris, The Man, The Myth, The Legend!

Chuck Norris Fan Page allows the user to interact with information about Chuck Norris. This website is the ultimate Chuck Norris fanpage, where a user can see Facts, Film history and much more. Using a combination of html, css, and javascript a user is able to interact with the website.

### Collaborators
Alicia Gorton -
Chad Coleman -
Audra Dagenais

### Interface/Developement
#### Tech/Framework used:
* HTMl
* CSS
* JavaScript
* JQuery
* AJAX
* API
* Bulma framework
* Git/GitHub
* Agile/Kanban Workflows

#### API References:
* https://api.chucknorris.io/jokes/random
* https://giphy.com/explore/chuck-norris
* https://codepen.io/akuma4114/pen/vYGLbNg
* https://imdb-api.com/en/API/Posters/k_bU3y02ls/chuck_movie_id

### Challenges
* Time management - Staying on deadlines of milestones - Project management
* Github merging - learning about gitignore/ Ds.store
* Coding main,js file - used a lot of resources TA’s, AskBCS Learning Assistantand and Tutors.
* Coding in a new framework (BULMA) and understanding how to use it with CSS - A lot of google FU

### Upcoming/Future Features
* Future Features:
    * Additional API’s for more Chuck.
    * Improve on the user experience:
        * Adding more dynamic styling to the page
        * Adding a short video or mini-player
    * Improve on the accessibility:
        * Add to our accessibility for everyone.
        * Making sure our webpage can be enjoyed by everyone.

    * Chuck himself: As his career changes so can the evolution of the website to reflect current information.
        * Guest appearance: like talk shows or tv shows
        * Meet and Greets he may attend
        * Any upcoming projects he my be involved in

### Known Bugs
* Ds.Store error from Apple.
* Getting the Api's to talk to the website.

### The following image demonstrates the application functionality:

### The following links to the application:

#### REPOSITORY LOCATIONS
##### Please read, this project was forked from the main branch. This branch only reflects my changes since the project ended. Majority of my commits can be seen at the Repository Link below.

* Deployment Link: https://the-magic-dragon.github.io/The-Magic-D-Project-/
* Repository Link: https://github.com/The-Magic-Dragon/The-Magic-D-Project-.git

## License

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

Copyright (c) 2020 Alicia Gorton, Chad Coleman, and  Audra Dagenais

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.

branch_name: refs/heads/main


text:
---
layout: post
microblog: true
date: 2017-06-06 11:57 +0300
guid: http://desparoz.micro.blog/2017/06/06/thanks-again-for.html
---
Thanks again for this great little plug-in. It certainly provides an interesting way to credit those people who are actively interacting.

On my implementation I notice that anyone who replies to a post via the  micro.blog interface will show by name, but the link will only be to micro.blog - not to their profile, or their blog.

Is this a limitation of the way things are at the moment, or do I need to configure things differently?


text:
# BASH

## Resources
 - [x] [Bash History](https://catonmat.net/the-definitive-guide-to-bash-command-line-history)

gha_language: Jupyter Notebook


text:
[![MIT Licence](https://badges.frapsoft.com/os/mit/mit.svg?v=103)](https://opensource.org/licenses/mit-license.php)

# HtmlParser test

I'm busy writing an HTML parser.
You can find it in another repository.

This parser needs to be tested against real world HTML.
The more the better of course.

This project implements the 'Gauntlet' test tool.
Written for the sole purpose of testing the HtmlParser.

## Features

The tool manages a repository of downloaded HTML.

There are features for creating the repository.
Downloading HTML from hostnames.
Redownloading hostnames that failed the first time.
Parsing the newly downloaded HTML.
Parsing all the HTML in the repository.
Calculating statistics.
And some more housekeeping things.

## Using it

Check out the code from github.
Run `make build` to just create the jar.
Run `make install` to build the jar and copy it to `/usr/local/bin`.

Feel free to create aliases if necessary.

The tool has a command line interface.
Try -h for help.

repository: codemonstur/htmlparser-test

gha_language: Java

repo_name: codemonstur/htmlparser-test


text:
## Packages and Crates

The first parts of the module system we’ll cover are packages and crates. A
crate is a binary or library. The *crate root* is a source file that the Rust
compiler starts from and makes up the root module of your crate (we’ll explain
modules in depth in the [“Defining Modules to Control Scope and
Privacy”][modules]<!-- ignore --> section). A *package* is one or more crates
that provide a set of functionality. A package contains a *Cargo.toml* file
that describes how to build those crates.

Several rules determine what a package can contain. A package can contain
at most one library crate. It can contain as many binary crates
as you’d like, but it must contain at least one crate (either library or
binary).

Let’s walk through what happens when we create a package. First, we enter the
command `cargo new`:

```console
$ cargo new my-project
     Created binary (application) `my-project` package
$ ls my-project
Cargo.toml
src
$ ls my-project/src
main.rs
```

When we entered the command, Cargo created a *Cargo.toml* file, giving us a
package. Looking at the contents of *Cargo.toml*, there’s no mention of
*src/main.rs* because Cargo follows a convention that *src/main.rs* is the
crate root of a binary crate with the same name as the package. Likewise, Cargo
knows that if the package directory contains *src/lib.rs*, the package contains
a library crate with the same name as the package, and *src/lib.rs* is its
crate root. Cargo passes the crate root files to `rustc` to build the library
or binary.

Here, we have a package that only contains *src/main.rs*, meaning it only
contains a binary crate named `my-project`. If a package contains *src/main.rs*
and *src/lib.rs*, it has two crates: a binary and a library, both with the same
name as the package. A package can have multiple binary crates by placing files
in the *src/bin* directory: each file will be a separate binary crate.

A crate will group related functionality together in a scope so the
functionality is easy to share between multiple projects. For example, the
`rand` crate we used in [Chapter 2][rand]<!-- ignore --> provides functionality
that generates random numbers. We can use that functionality in our own
projects by bringing the `rand` crate into our project’s scope. All the
functionality provided by the `rand` crate is accessible through the crate’s
name, `rand`.

Keeping a crate’s functionality in its own scope clarifies whether particular
functionality is defined in our crate or the `rand` crate and prevents
potential conflicts. For example, the `rand` crate provides a trait named
`Rng`. We can also define a `struct` named `Rng` in our own crate. Because a
crate’s functionality is namespaced in its own scope, when we add `rand` as a
dependency, the compiler isn’t confused about what the name `Rng` refers to. In
our crate, it refers to the `struct Rng` that we defined. We would access the
`Rng` trait from the `rand` crate as `rand::Rng`.

Let’s move on and talk about the module system!

[modules]: ch07-02-defining-modules-to-control-scope-and-privacy.html
[rand]: ch02-00-guessing-game-tutorial.html#generating-a-random-number

repository: rust-lang-cn/book-cn

gha_language: Rust

repo_name: rust-lang-cn/book-cn


text:
OutlineView
===========

Illustrates how to populate a simple `OutlineView` using an `NSViewOutlineDataSource` that in
turn, uses an object tree of animal classes.

Author
------

Ported to Xamarin.Mac by Bryan Costanich.

repository: undeadinu/mac-samples

repo_name: undeadinu/mac-samples


text:
# SamuROI
If you use this software, please cite:

## Requirements
SamuROI requires the following python packages:
- python
- numpy
- matplotlib
- opencv
- h5py
- scikit-image
- pyqt
- pillow

## Installation via conda (recommended)
It is recommended to install SamuROI via the conda package manager,
since conda comes with packages for scikit-image, opencv and pyqt.
`conda install samuroi`

## Installation via pip
To install SamuROI via pip make sure to satisfy the following dependencies
manually:
- opencv
- scikit-image
- pyqt

repository: fjohenning/SamuROI

repo_name: fjohenning/SamuROI


text:
# EnvConfigs

> My Personal Environment's Configuration and Setup
>
> -- Domin

## Initial preparation

1. Obtain [current repository](https://github.com/DominikJaniec/EnvConfigs) by cloning it, or what is more likely at fresh environment, by [downloading ZIP archive](https://github.com/DominikJaniec/EnvConfigs/archive/refs/heads/main.zip) and extracting it. Then place that `EnvConfig` within desired `Repos` _Home Directory_ - e.g. `~/Repos` or `D:\Repos`.

2. Using [`!elevate-session.ps1`](!elevate-session.ps1) script, start [_PowerShell_](https://docs.microsoft.com/en-us/powershell/) session (`PSSession`) elevated to the _Administrator Role_.

3. Set necessary [execution policy](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1) for the whole machine:

   ```PowerShell
   Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy RemoteSigned -Confirm
   ```

4. Install [_Chocolatey_](https://chocolatey.org/about): a package manager for Windows, using elevated `PSSession`:

   ```PowerShell
   ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1')) `
       | Invoke-Expression
   ```

## Software via Chocolatey

1. Execute prepare script: [`> .\Choco\!prepare.ps1`](Choco/!prepare.ps1)
   * Optional script's parameter: `-PkgLevel (core|tools|dev|full)`
   * Default value is assumed to be: `-PkgLevel full`
   * Each value encompass all previous levels.

2. That script requires _Chocolatey_ and have to be executed from `PSSession` elevated to _Admin_.

3. What does that script do?
   * Will turn on `choco`'s feature: [_Use Remembered Arguments For Upgrades_](https://docs.chocolatey.org/en-us/configuration#general-1).
   * Will install every [defined applications](Choco/packages.txt) according to selected packages level.
   * Some packages or their dependencies may require reboot after installation.

## Shells & Git configuration

1. Execute prepare script: [`> .\Shells\!prepare.ps1`](Shells/!prepare.ps1)
   * Script provides a single switch: `-PwshAllUsers`.

2. That script have to be executed from `PSSession` elevated to _Admin_ from target user.
   * This requirement could be lifted, when creating `SymbolicLink` will be available to normal users.

3. What does that script do?
   * Will make symbolic-links at _Home_ (`~/`) directory of current user with Bash and Git configuration files: [`.bash_profile`](Shells/.bash_profile) + [`.bashrc`](Shells/.bashrc), and [`.gitconfig`](Shells/.gitconfig).
   * Will install pwsh-modules: [`posh-git`](https://www.powershellgallery.com/packages/posh-git) and [`oh-my-posh`](https://www.powershellgallery.com/packages/oh-my-posh), which are utilized by `Profile.ps1` for more user friendly UX of terminal.
   * Symbolic-link will also be created for profile-file for PowerShell at [`~/Documents/PowerShell/Profile.ps1`](Shells/Profile.ps1) - no profile for old but yet default PowerShell 5.
   * When `-PwshAllUsers` is provided, the Pwsh is set up with Profile and Modules for [All Users](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_profiles) under `C:/Program Files/PowerShell`.

## System Windows configuration

1. Execute prepare script: [`> .\System\!prepare.ps1`](System/!prepare.ps1)
   * Script has a few switches. When any of then is present, only related changes will be executed. Script by default executes all of them.
   * Available switches: `-AssocTxtfile`, `-CtxMenuCleanUp`, `-ProcessExpSchedule`, `-WinExplorerPrepare`, `-DittoConfigSetup`, `-FluxConfigSetup`, `-HWiNFO64ConfigSetup`, `-UpdateScriptInstall`.

2. That script have to be executed from `PSSession` elevated to _Admin_ from target user.

3. What does that script do?
   * `-AssocTxtfile`: Will setup every [defined files' extensions](System/txtfile_extensions.txt) to be treated as Text-Based files by _Windows Explorer_.
   * `-CtxMenuCleanUp`: Will clean up context menu of folders from unnecessary [defined entries](System/unwanted_cmds.txt).
   * `-WinExplorerPrepare`: Will fix _Explorer's_ display configuration and organize [_Quick Access_](https://support.microsoft.com/en-us/help/4027032/windows-pin-remove-and-customize-in-quick-access) with a few handy folders. This script expect that there is a parent directory called `Repos` and one of theirs sibling is called `Personal` - both of them will be pinned.
   * `-ProcessExpSchedule`: Will schedule [_Process Explorer_](https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) by _Mark Russinovich_ to start on _Logon_.
   * `-DittoConfigSetup`: Will load into Register non-default-personal [Ditto's](https://ditto-cp.sourceforge.io/) configuration.
   * `-FluxConfigSetup`: Will import Register-based [f.lux's](https://justgetflux.com/) configuration adjusted for Domin's lifestyle.
   * `-HWiNFO64ConfigSetup`: Will configure [HWiNFO64](https://www.hwinfo.com/) to sense CPU and GPU temperatures of CGL.
   * `-UpdateScriptInstall`: Will link [`update-system.bat`](System/update-system.bat) into `PATH` available directory, so _Admin_ can request and execute whole _System_ update.

## Visual Studio Code

1. Execute prepare script: [`> .\VSCode\!prepare.ps1`](VSCode/!prepare.ps1)
   * Optional multi-value parameter: `-Extensions`: defines which _extensions groups_ will be installed. Available values: `core`, `tools`, `dev`, `webdev`, `work`, `extra` - where `all` matches to every extension and multiple values are separated by comma.
   * There are two additional _switches_: `SkipExtra` and `SkipWork`, which excludes matched group even explicitly requested.
   * By default `-Extensions` assumes `all` group, for ease of use.

2. That script requires installed _VS Code_, which could be download from [Microsoft](https://code.visualstudio.com/docs/?dv=win).

3. What does that script do?
   * Will link configuration files ([`settings.json`](VSCode/settings.json), [`keybindings.json`](VSCode/keybindings.json)) at User Code's profile directory.
   * Will install every [defined extensions](VSCode/extensions.txt) for _VS Code_ according to selected _extensions-group_.

## Visual Studio 2017

1. Extensions and configuration presented in [file: `VSCommunity.md`](VSCommunity.md).
2. Download and install it from [Microsoft (_Community_ version)](https://www.visualstudio.com/pl/vs/community/).

## Keyboard

1. Use any _Ergodox_ compatible devices and load [`recent.hex`](Keyboard/recent.hex) layout.
2. More details one can find at: [`Keyboard/README.md`](Keyboard/README.md).

----

## Assumptions and remarks

* Chapters presented above are set in the proposed order of execution of steps for configuration setup.
* Initial placement of `EnvConfigs` repository is very important and should be under desired `Repos`:
  * Many _prepare script_ (i.e. `!prepare.ps1`) will make symbolic-links into files located here.
  * The _prepare script_ of `System` will pin as _favorites_ and _decorate_ a parent directory as `Repos`.
  * Every _prepare script_ should be run from this repository's root directory via _PowerShell_.
* It is required to have [_PowerShell_](https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-windows?view=powershell-7.1) in version greater then `3.0`. Fortunately, Windows 10 currently comes with version `5.1` - to check it, one can type: `$PSVersionTable.PSVersion` within running `PSSession`.
* Almost all scripts expect to be run within _PowerShell_ session with elevated permissions to the _Administrator Role_. To obtain elevated PowerShell console, just execute:

   ```sh
   PowerShell.exe -NoProfile -File ".\!elevate-session.ps1"
   ```

## Track the `EnvConfigs` repository

1. While preparing fresh environment, current repository was probably just downloaded as ZIP without any _Git Tracking_ ability - as there were no `git` available at beginning of setup.
   * It is **not recommended** to _clone_ it again in desired place, as it should be already in expected `Repos` _Home Directory_.
   * It is **strongly encouraged** to restore _Git_ support within current directory - to easily track future configuration changes.

2. To reestablish _Git_ support within current repository, one should use favorite terminal under their own user account and call in order:

   ```sh
   git init --initial-branch=main
   git remote add origin https://github.com/DominikJaniec/EnvConfigs.git
   git fetch
   git reset origin/main --mixed
   git branch --set-upstream-to=origin/main
   git status
   ```

repository: DominikJaniec/EnvConfigs

repo_name: DominikJaniec/EnvConfigs


text:
# Tool Chain

The following tools are in common use in CC development

## General

1. [Venv](https://docs.python.org/3/library/venv.html) - Python virtual environment
1. [Vue CLI](https://cli.vuejs.org/) - Tooling for Vue development
1. [Vue development tools](https://github.com/vuejs/vue-devtools) - Browser plugin for Vue

## Revision Control

1. [Git](https://git-scm.com/) - distributed revision control
    - [Pro Git Book](https://git-scm.com/book/en/v2) - free on-line
    - [Getting Git Right](https://www.atlassian.com/git) - tutorial
    - [Git Cheatsheet](https://ndpsoftware.com/git-cheatsheet.html) - nifty interactive visual cheat sheet
    - [Git Learning Lab](https://lab.github.com/)
    - [Learn Git Branching](https://learngitbranching.js.org/) - interactive tutorial
    - [Learning Resources](https://try.github.io/) for Git
1. [GitHub](https://github.com) - Git hosting
    - [Learning Resources](https://try.github.io/) for GitHub

## Testing

### User Interface

1. [Vue Test Utils](https://vue-test-utils.vuejs.org/) - Vue-specific test utilities
    - [Vue Testing Handbook](https://lmiller1990.github.io/vue-testing-handbook/) - Gentle intro to Vue Test Utils
1. [Jest](https://jestjs.io/en/) - Test runner
1. [Mocha](https://mochajs.org/) - Test framework
1. [Chai](https://www.chaijs.com/) - Assertion library
1. [Sinon](https://sinonjs.org/) - Spies, stubs, and mocks for JavaScript

### RESTful API

1. [Postman](https://www.getpostman.com/) - API test tool
1. [Pytest](https://docs.pytest.org/en/latest/contents.html#toc) - Python testing

### End-to-End

1. [Cypress](https://www.cypress.io/) - Cool new testing environment

## Dev Ops

1. [Linode](https://www.linode.com/) - Hosting provider
1. [Circle CI](https://circleci.com/) - Continuous integration and deployment
1. [Ansible](https://www.ansible.com/) - Automation

## Development Environment

1. [PyCharm](https://www.jetbrains.com/pycharm/)
1. [Visual Studio Code](https://code.visualstudio.com/)

repository: corpus-christi/corpus-christi

branch_name: refs/heads/development

gha_language: Vue

repo_name: corpus-christi/corpus-christi


text:
# Joannify
This program replaces all pictures on the page with Joanna's face.  In the future, we hope to implement random pictures of Joanna's face instead of just one measly photo of Joanna's face.

#BETA:
To run: Go to about:debugging in your firefox browser. Click load temporary add-on and navigate to and click joannify.js. Now every photo in your browser, when you right click and select view image, turns into a photo of Joanna!

gha_language: JavaScript


text:
TelemetryService

Description

Multithreaded Client-server service for collecting telemetry over TLS. Meaning CPU load, num of cores, RAM, HDD.

Requirements

* OpenSSL

Script provides:

1. Client-side
2. Server-side
3. Bash-script for solving dependencies
4. Bash daemon set-up

Explanations

You can run both applications as systemd services using provided bash script.
You need to run  TelemetryAgent/Sservice/config.sh and enter "client" or "server" when script asked. So agent will have gone setup as follows. Also you may accept them to autorun on boot (or not if you rehect the option : -) )

Demo

_runs only for linux_

repository: mstrielnikov/TelemetryAgent

repo_name: mstrielnikov/TelemetryAgent


text:
# Human Pose Estimation Model Serving on Multi-Model-Server (MMS)

## Installation

1. Build the image for the MMS:
    ```bash
    $ docker build -t human-pose-mms .
    ```
2. Prepare the deployment model with model-archiver:
    ```bash
    $ docker run --rm -it -v $(pwd):/tmp human-pose-mms:latest bash

    $ model-archiver --model-name pose --model-path /tmp/service --handler handler:handle --runtime python3 --export-path /tmp
    ```
3. Start the MMS:
    ```bash
    $ docker run --rm -it -p 8080:8080 -p 8081:8081 -v $(pwd):/tmp mms-human-pose:latest multi-model-server --start --mms-config /tmp/config.properties --models posenet=pose.mar --model-store /tmp
    ```

##  Testing

Send a request with curl:
```bash
curl -X POST http://localhost:8080/predictions/posenet/ -T example.jpg
```

## Running Client
1. Install python packages from [here](client/requirements.txt)
2. Run the client
    ```bash
    $ python client/cli.py
    ```

## Note
This repository is not for production use for sure!!!. Please read it [on medium](https://medium.com/@bedilbek/serve-human-pose-on-mms-44fcb5239ea0) to learn more about this repository.

Thanks to the [Joshua Earle](https://unsplash.com/@joshuaearle) for [photo](example.jpg) [on Unsplash](https://unsplash.com/photos/ICE__bo2Vws)

repository: bedilbek/human-pose-mms

repo_name: bedilbek/human-pose-mms


text:
# Master's thesis at UCLouvain

### Design of an ultra-low-power energy-harvesting audio sensor for ecosystem monitoring

Here are the source files of my Master's thesis at UCLouvain (June 2020).

It includes all the simulations required for this work:
* **Audio processing**: C code for the microcontroller and Matlab code to process the data (plot the graphs) received from the board
* **BOM**: Excel file with the bill of materials
* **IV mic**: Matlab code to plot the IV curves (current/voltage) of different microphones
* **Microcontroller**: Wisebatt simulation to provide a rough estimate of the whole system power consumption
* **Microphone**: LTspice and Matlab codes for the microphone/AFE subsystem (AC and noise)
* **PCB**: KiCad and Eagle files for the PCB design (schematic and PCB layout)
* **Power management**: Matlab and Excel files for measurements about the supercapacitor, solar cells, PMU and luminosity
* **Thesis source code**: LaTeX source code of the Master's thesis

![alt text](https://github.com/MartinBraquet/master-thesis-UCLouvain/blob/master/Thesis%20source%20code/img/real_PCB_with_MCU.png)

![alt text](https://github.com/MartinBraquet/master-thesis-UCLouvain/blob/master/Thesis%20source%20code/img/Spectrogram.png)

![alt text](https://github.com/MartinBraquet/master-thesis-UCLouvain/blob/master/Thesis%20source%20code/img/Noise_Current.png)

repository: MartinBraquet/master-thesis-UCLouvain

repo_name: MartinBraquet/master-thesis-UCLouvain


text:
# Generic error handler

An easy to integrate error handler setup, made for PHP applications without one.

## What does it do?

It intercepts PHP errors, notices etc. and writes them into the PHP error log.

## Getting started

### Composer
```shell script
$ composer require sjoorm/generic-error-handler
```

```php
// TBD
```

### Direct installation

1. determine your include path by `php -i | grep include_path`
1. place [release](https://github.com/sjoorm/generic-error-handler/releases/latest) version in it
1. optional: edit `error_log` directive in your `php.ini` to write into the file instead of web server error log
1. add the following code to your entry point (e.g. Wordpress `wp-config.php`)
```php
require_once('generic-error-handler/init.php');
```

## Credits

Based on [Symfony/error-handler](http://github.com/symfony/error-handler) and [Seldaek/monolog](https://github.com/Seldaek/monolog).

repository: sjoorm/generic-error-handler

repo_name: sjoorm/generic-error-handler


text:
# docker-stash: A Docker image for Stash.

[![Build status](https://travis-ci.org/ahaasler/docker-stash.svg?branch=master)](https://travis-ci.org/ahaasler/docker-stash)
[![Docker Repository on Quay.io](https://quay.io/repository/ahaasler/stash/status "Docker Repository on Quay.io")](https://quay.io/repository/ahaasler/stash)
[![Release](https://img.shields.io/github/release/ahaasler/docker-stash.svg?style=flat)](https://github.com/ahaasler/docker-stash/releases/latest)
[![Docker Stars](https://img.shields.io/docker/stars/ahaasler/stash.svg?style=flat)](https://hub.docker.com/r/ahaasler/stash/)
[![Docker Pulls](https://img.shields.io/docker/pulls/ahaasler/stash.svg?style=flat)](https://hub.docker.com/r/ahaasler/stash/)
[![Image Size](https://img.shields.io/imagelayers/image-size/ahaasler/stash/latest.svg?style=flat)](https://imagelayers.io/?images=ahaasler/stash:latest)

## Features

* Runs on a production ready *OpenJDK* 8 - [Zulu](http://www.azulsystems.com/products/zulu "Zulu: Multi-platform Certified OpenJDK") by Azul Systems.
* Ready to be configured with *Nginx* as a reverse proxy (https available).
* Built on top of *Debian* for a minimal image size.

## Usage

```bash
docker run -d -p 7990:7990 -p 7999:7999 ahaasler/stash
```

### Parameters

You can use this parameters to configure your stash instance:

* **-s:** Enables the connector security and sets `https` as connector scheme.
* **-n <proxyName>:** Sets the connector proxy name.
* **-p <proxyPort>:** Sets the connector proxy port.
* **-c <contextPath>:** Sets the context path (do not write the initial /).

This parameters should be given to the entrypoint (passing them after the image):

```bash
docker run -d -p 7990:7990 -p 7999:7999 ahaasler/stash <parameters>
```

> If you want to execute another command instead of launching stash you should overwrite the entrypoint with `--entrypoint <command>` (docker run parameter).

### Nginx as reverse proxy

Lets say you have the following *nginx* configuration for stash:

```
server {
	listen                          80;
	server_name                     example.com;
	return                          301 https://$host$request_uri;
}
server {
	listen                          443;
	server_name                     example.com;

	ssl                             on;
	ssl_certificate                 /path/to/certificate.crt;
	ssl_certificate_key             /path/to/key.key;
	location /stash {
		proxy_set_header X-Forwarded-Host $host;
		proxy_set_header X-Forwarded-Server $host;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_pass http://<IP_ADDRESS>:7990;
		proxy_redirect off;
	}
}
```

> This is only an example, please secure you *nginx* better.

For that configuration you should run your stash container with:

```bash
docker run -d -p 7990:7990 -p 7999:7999 ahaasler/stash -s -n example.com -p 443 -c stash
```

### Persistent data

The stash home is set to `/data/stash`. If you want to persist your data you should use a data volume for `/data/stash`.

#### Binding a host directory

```bash
docker run -d -p 7990:7990 -p 7999:7999 -v /home/user/stash-data:/data/stash ahaasler/stash
```

Make sure that the stash user (with id 782) has read/write/execute permissions.

If security is important follow the Atlassian recommendation:

> Ensure that only the user running Stash can access the Stash home directory, and that this user has read, write and execute permissions, by setting file system permissions appropriately for your operating system.

#### Using a data-only container

1. Create the data-only container and set proper permissions:

	* **Lazy way (preferred)** - Using [docker-stash-data](https://github.com/ahaasler/docker-stash-data "A data-only container for docker-stash"):

		```bash
docker run --name stash-data ahaasler/stash-data
		```

	* *I-wan't-to-know-what-I'm-doing* way:

		```bash
docker run --name stash-data -v /data/stash busybox true
docker run --rm -it --volumes-from stash-data debian bash
		```

		The last command will open a *debian* container. Execute this inside that container:

		```bash
chown 782:root /data/stash; chmod 770 /data/stash; exit;
		```

2. Use it in the stash container:

	```bash
docker run --name stash --volumes-from stash-data -d -p 7990:7990 -p 7999:7999 ahaasler/stash
	```

### PostgreSQL external database

A great way to connect your Stash instance with a PostgreSQL database is
using the [docker-stash-postgres](https://github.com/ahaasler/docker-stash-postgres "A PostgreSQL container for docker-stash")
image.

1. Create and name the database container:

	```bash
docker run --name stash-postgres -d ahaasler/stash-postgres
	```

2. Use it in the Stash container:

	```bash
docker run --name stash --link stash-postgres:stash-postgres -d -p 7990:7990 -p 7999:7999 ahaasler/stash
	```

3. Connect your Stash instance following the Atlassian documentation:
[Connecting Stash to PostgreSQL](https://confluence.atlassian.com/display/STASH/Connecting+Stash+to+PostgreSQL#ConnectingStashtoPostgreSQL-ConnectStashtothePostgreSQLdatabase "Connecting Stash to PostgreSQL").

>  See [docker-stash-postgres](https://github.com/ahaasler/docker-stash-postgres "A PostgreSQL container for docker-stash")
for more information an configuration options.

## Thanks

* [Docker](https://www.docker.com/ "Docker") for this amazing container engine.
* [PostgreSQL](http://www.postgresql.org/) for this advanced database.
* [Atlassian](https://www.atlassian.com/ "Atlassian") for making great products. Also for their work on [atlassian-docker](https://bitbucket.org/atlassianlabs/atlassian-docker "atlassian-docker repo") which inspired this.
* [Azul Systems](http://www.azulsystems.com/ "Azul Systems") for their *OpenJDK* docker base image.
* And specially to you and the entire community.

## License

This image is licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for the full license text.

repository: ahaasler/docker-stash

gha_language: Shell

repo_name: ahaasler/docker-stash


text:
# Symbulate

*Symbulate* is a Python package which provides a user friendly
 framework for specifying and conducting simulations from probability models.

# Installation Instructions

It is recommended that you first install the
[Anaconda distribution](https://www.anaconda.com/download/), which
is a Python environment with many scientific packages installed
(including all of the packages that Symbulate is built on).

The fastest way to get up and running with Symbulate is to run the
command `pip install symbulate` at the command line.

# Documentation

Please see the [documentation](https://dlsun.github.io/symbulate/index.html) for examples of how to use Symbulate.

repository: bdatko/symbulate

repo_name: bdatko/symbulate


text:
---
title: Version Information for Zen Cart, PHP and MySQL
description: Version Information for Zen Cart, PHP and MySQL
category: first_steps
weight: 10
---

To find out what version of Zen Cart or PHP or MySQL you are currently using, there are two options that both get you what you need.

You can click [Version](/user/admin_pages/admin_version/) on the top right navigation menu.      ![Version Link](/images/skinny_version.png)

Or you can go to [Admin > Tools > Server/Version Info](/user/admin_pages/tools/server_info/).       ![Tools Version Link](/images/tools_server_version.png)

<br>

Either of these options will take you to the [Server/Version Info](/user/admin_pages/tools/server_info) page.

On that screen you will see a lot of detail about your server configuration. Your Zen Cart version will be shown, as well as your server's PHP version, MySQL version, database parameters, PHP settings, and more.

You can also see your database upgrade history.

Version information is particularly important if you are upgrading Zen Cart
or your hoster is upgrading PHP.  You want to be sure you have a
[compatible PHP for your Zen Cart version](/user/first_steps/server_requirements/).


text:
# Joylogics CloudFormation Templates

## S3_Website_for_WP2Static.yaml
[![Launch Stack](https://cdn.rawgit.com/buildkite/cloudformation-launch-stack-button-svg/master/launch-stack.svg)](https://console.aws.amazon.com/cloudformation/home#/stacks/new?stackName=build-s3-website-for-wp2static&templateURL=https://jl-cloudformation.s3.us-east-1.amazonaws.com/S3_Website_for_WP2Static.yaml)
### Usecase
Create a simple, low-cost static website hosted on S3 to be used with WP2Static (WordPress plugin).
### Prerequisites
* Route 53 Hosted Zone to place the DNS record for the website's URL.
### Parameters
* HostedZone - The DNS name of an existing Amazon Route 53 hosted zone (E.g., "joylogics.com")
* SubdomainName - The subdomain name of the website (E.g, "www")
### Creates
* S3 bucket for hosting - named from the URL. (E.g., "www.joylogics.com")
* An IAM User in this account specifically for uploading content to the S3 bucket.
* DNS record in the HostedZone.
### Outputs
* WebsiteURL: The URL of the website
* BucketName: Name of S3 bucket for the website
* S3BucketUser: IAM User for pushing data to the S3 bucket
* S3UserAccessKeyID: Access Key ID for the IAM User
* S3UserSecretAccessKey: Secret Access Key for the IAM User

## WordPress_Single_Instance.yaml
This [version](https://github.com/awslabs/aws-cloudformation-templates/blob/e5362c99375ca49d4da56973c95dda81742667e0/aws/solutions/WordPress_Single_Instance.yaml) was copied from [awslabs cloudformation templates repo](https://github.com/awslabs/aws-cloudformation-templates).

[![Launch Stack](https://cdn.rawgit.com/buildkite/cloudformation-launch-stack-button-svg/master/launch-stack.svg)](https://console.aws.amazon.com/cloudformation/home#/stacks/new?stackName=build-s3-website-for-wp2static&templateURL=https://jl-cloudformation.s3.us-east-1.amazonaws.com/WordPress_Single_Instance.yaml)
### Usecase
Create an EC2 instance with WordPress installed on it.
### Prerequisites
If you have not done so, create an EC2 KeyPair which is needed for accessing the EC2 instance via SSH.
This is needed in those cases you'll want to maintain/manage the OS and the software installed on it.
For example, you would want to apply security patches.
Note the SSHLocation can be used to lock down the source IP address for the EC2 instance as well.
### Parameters
* DBName: The WordPress database name
* DBPassword: The WordPress database admin account password
* DBRootPassword: MySQL root password
* DBUser: The WordPress database admin account username
* InstanceType: WebServer EC2 instance type
* KeyName: Name of an existing EC2 KeyPair to enable SSH access to the instances
* SSHLocation: The IP address range that can be used to SSH to the EC2 instances
### Creates
* An EC2 instance with WordPress installed in it.
* Security Group for the EC2 instance
### Outputs
* PublicIP: EC2 public IP
* WebsiteURL: WordPress Website

repository: joylogics/cloudformation

repo_name: joylogics/cloudformation


text:
---
title: blogc
repo: blogc/blogc
homepage: https://blogc.rgm.io/
language:
  - C
license:
  - BSD-3-Clause
templates:
  - Custom
description: A blog compiler.
startertemplaterepo: blogc/blogc-netlify
---

blogc is a blog compiler. It converts source files and templates into blog/website resources. It is designed to be used with `make` or any other similar build tool. It is also stateless and idempotent, no state is shared between blogc binary calls.


text:
<!--
title: Serverless Framework - AWS Lambda Events - Event Bridge
menuText: EventBridge Event
menuOrder: 15
description:  Setting up AWS EventBridge Events with AWS Lambda via the Serverless Framework
layout: Doc
-->

<!-- DOCS-SITE-LINK:START automatically generated  -->

### [Read this on the main serverless docs site](https://www.serverless.com/framework/docs/providers/aws/events/event-bridge)

<!-- DOCS-SITE-LINK:END -->

# EventBridge Event

The [EventBridge](https://aws.amazon.com/eventbridge/) makes it possible to connect applications using data from external sources (e.g. own applications, SaaS) or AWS services. The `eventBridge` event types helps setting up AWS Lambda functions to react to events coming in via the EventBridge.

## Setting up a scheduled event

```yml
functions:
  myFunction:
    handler: index.handler
    events:
      - eventBridge:
          schedule: rate(10 minutes)
          input:
            key1: value1
```

## Setting up event pattern matching

```yml
functions:
  myFunction:
    handler: index.handler
    events:
      - eventBridge:
          pattern:
            source:
              - aws.cloudformation
            detail-type:
              - AWS API Call via CloudTrail
            detail:
              eventSource:
                - cloudformation.amazonaws.com
```

## Using a different Event Bus

The `eventBridge` event source will use the `default` event bus (the one AWS uses internally) when none is explicitly specified.

The Serverless Framework will create the `eventBus` for you if you just provide a name for it. It will re-use an existing event bus if you provide an event bus `arn`.

**NOTE:** The Serverless Framework won't manage (e.g. create or remove) the event bus if it's provided via an `arn`.

### Creating an event bus

```yml
functions:
  myFunction:
    handler: index.handler
    events:
      - eventBridge:
          eventBus: custom-saas-events
          pattern:
            source:
              - saas.external
```

### Re-using an existing event bus

```yml
- eventBridge:
    eventBus: arn:aws:events:us-east-1:12345:event-bus/custom-private-events
    pattern:
      source:
        - custom.private
    inputTransformer:
      inputPathsMap:
        eventTime: '$.time'
      inputTemplate: '{"time": <eventTime>, "key1": "value1"}'
```

## Using different input types

You can specify different input types which will produce different input values for the Lambda function.

```yml
functions:
  myFunction:
    handler: index.handler
    events:
      - eventBridge:
          pattern:
            source:
              - 'aws.ec2'
            detail-type:
              - 'EC2 Instance State-change Notification'
            detail:
              state:
                - pending
          input:
            key1: value1
            key2: value2
            stageParams:
              stage: dev
      - eventBridge:
          pattern:
            source:
              - 'aws.ec2'
            detail-type:
              - 'EC2 Instance State-change Notification'
            detail:
              state:
                - pending
          inputPath: '$.stageVariables'
      - eventBridge:
          pattern:
            source:
              - 'aws.ec2'
            detail-type:
              - 'EC2 Instance State-change Notification'
            detail:
              state:
                - pending
          inputTransformer:
            inputPathsMap:
              eventTime: '$.time'
            inputTemplate: '{"time": <eventTime>, "key1": "value1"}'
```

repository: DeepHiveMind/serverless

repo_name: DeepHiveMind/serverless


text:
{
  "title": "@djnavarro @lingtax @kylehamilton Bookdown is being annoying with my URL - so if you're looking for this and can't find it try https://t.co/bag21zlzDP for the most recent version on git",
  "date": "2018-12-30"
}

# blogdown

> **Aline Deschamps** (@alinedeschamps; 6/2): @charlyx @jessfraz Oh my god, so many amazing things ! 😀 Go look at : Shiny, Blogdown, RStudio addins, ... And #rstats ! 😉  [↪](https://twitter.com/xieyihui/status/1079036629187207169)

<!-- -->

> **Steph Locke** (@TheStephLocke; 2/0): @jessfraz @nigelainscoe Well, there's a lot of ❤for Docker right now in the R community! Check out:
> https://t.co/RahyTj9hMt
> https://t.co/a35d7QX4Ru
> >
> In terms of data analysis, the {tidyverse} and {DataExplorer} are great
> For dashboards, {flexdashboard} is super helpful
> And R ❤@GoHugoIO so {blogdown}  [↪](https://twitter.com/xieyihui/status/1079040834409037824)

<!-- -->

> **Andriy Gazin** (@AndriyGazin; 1/0): @taraskaduk я почав з blogdown, але потім вирішив працювати без посередників :)  [↪](https://twitter.com/xieyihui/status/1079159306455576576)

<!-- -->

> **Eric Krantz** (@EricLeeKrantz; 1/0): @_ColinFay Start a blog with blogdown, and get comfortable with Hugo, css, html.  [↪](https://twitter.com/xieyihui/status/1079155179478532101)

<!-- -->

> **Taras Kaduk** (@taraskaduk; 0/0): @AndriyGazin blogdown FTW! Верстается на HUGO, пишется в R (RMarkdown) 🙌🏼  [↪](https://twitter.com/xieyihui/status/1079157945596817409)

<!-- -->

> **RPubs recent entry** (@RPubsRecent; 0/0): Intro to Blogdown https://t.co/AElcSQGXm5  [↪](https://twitter.com/xieyihui/status/1079105529824333830)

<!-- -->

# bookdown

> **Dr Emily Kothe** (@emilyandthelime; 6/3): @djnavarro @lingtax @kylehamilton Bookdown is being annoying with my URL - so if you're looking for this and can't find it try https://t.co/bag21zlzDP for the most recent version on git  [↪](https://twitter.com/xieyihui/status/1079013960504864770)

<!-- -->

> **Francesco Grossetti** (@contefranz; 0/0): @xieyihui hi there! Any ideas why I am getting "unexpected EOF while parsing" with this Python chunk in #bookdown? I am literally stuck! Please find knitr config in the second image attached. Thanks in advance! #rstats https://t.co/lrdbjkfPdm  [↪](https://twitter.com/xieyihui/status/1079027973959966720)

<!-- -->

# knitr

> **Davis Vaughan** (@dvaughan32; 3/1): @CMastication Just goes to show how well thought out the programming of RStudio itself is so that they could reuse pieces of the autocompletion engine for Python. Same with the generic knitr chunk engine idea in general  [↪](https://twitter.com/xieyihui/status/1079167880300773377)

<!-- -->

> **Jozef Hajnala** (@jozefhajnala; 2/2): Ever wanted to use 📊 #highcharts in your R Markdown html rendered by knitr and disliked the size of the generated html? Here is a small #rstats function to include only the necessary minimum in the output: https://t.co/rzADCRPcvn  [↪](https://twitter.com/xieyihui/status/1079122804136652803)

<!-- -->

> **Apoorva Lal** (@ApoorvaRed; 1/0): @CMastication I really like Atom + Hydrogen + knitr / Pweave. The subpar vim mode in Rstudio makes it a non-starter for me.  [↪](https://twitter.com/xieyihui/status/1079168089613164544)

<!-- -->

> **Mim** (@mim_djo; 1/0): added a new tab using #Python #altair, all gracefully generated using #rstats #knitr, yes, rmarkdown accept other languages too,  open source rocks https://t.co/QIE9J7iSxg  [↪](https://twitter.com/xieyihui/status/1078981430053560320)

<!-- -->

repository: cgpu/twitter-blogdown

repo_name: cgpu/twitter-blogdown


text:
---
title: Overview
page_title: Changes And Backward Compatibility Overview - RadWindow
description: Check our Web Forms article about Overview.
slug: window/changes-and-backward-compatibility/overview
tags: overview
published: True
position: 0
---

# Changes And Backward Compatibility Overview

## Telerik RadWindow for ASP.NET AJAX

A complete list of all changes can be found on Release History page: [https://www.telerik.com/products/aspnet-ajax/whats-new/release-history.aspx](https://www.telerik.com/products/aspnet-ajax/whats-new/release-history.aspx)

## Telerik RadWindow for ASP.NET AJAX Q2 2010

When the RadWindow's *ContentTemplate* element is used, then the control will not call its DataBind() method. This method is called in order to evaluate the databinding expressions that set RadWindow's properties. For example, setting the RadWindow's *OpenerElementID* property using the code shown bellow will not not work if the *ContentTemplate* element is used.

````ASP.NET
<telerik:RadWindow RenderMode="Lightweight"
	ID="RadWindowDetails"
	runat="server"
	OpenerElementID="<%# ButtonOpenWindow.ClientID %>">
</telerik:RadWindow>
````

A complete list of all changes can be found on Release History page: [https://www.telerik.com/products/aspnet-ajax/whats-new/release-history.aspx](https://www.telerik.com/products/aspnet-ajax/whats-new/release-history.aspx)

## Telerik RadWindow for ASP.NET AJAX Q1 2010

With the new version, the controls in the RadWindow's ContentTemplate are available to the page without using FindControl method. This could lead to problems if you have declared controls with the same ID in the RadWindow's content template and in the page.

## Telerik RadWindow for ASP.NET AJAX Q3 2009

* When a **RadWindow** is declared in **RadWindowManager** it preserves its ViewState which was not so in previous versions. This could lead to backwards incompatibility when the **VisibleOnPageLoad** property is used in this configuration with the idea to show the **RadWindow** only once. Possible solutions for this case are the following ones:

* Set **EnableViewState = "false"** for the **RadWindowManager**

	* Reset the **VisibleOnPageLoad** property to **false** with code when suitable, depending on the particular scenario

	* Show the **RadWindow** through registering a script from the server instead.

	* The **ClientCallBackFunction** property is removed and not used anymore. The arguments can be received in the OnClientClose function like shown in the [Using RadWindow as a Dialog]({%slug window/how-to/using-radwindow-as-a-dialog%}) article.

## Telerik RadWindow for ASP.NET AJAX Q2 2009

RadWindow for ASP.NET AJAX which is part of the Q2 2009 release is fully backwards compatible with its previous version (Q1 2009).

## Telerik RadWindow for ASP.NET AJAX Q1 2009

* Total redesign of the skins, which aims for a uniformity of the appearance of all controls in the suite in the cases they are used to build RIAs

* Refactoring of the CSS code to achieve better understanding, easier maintenance and handle problems with global styles

* Changes to the CSS classes, so now all controls for ASP.NET AJAX comply with a common naming convention. For example was: **radwindow radwindow_Default** now: **RadWindow RadWindow_Default**

## Telerik RadWindow for ASP.NET AJAX Q3 2008

RadWindow for ASP.NET AJAX which is part of the Q3 2008 release is fully backwards compatible with its previous version (Q2 2008).

## Telerik RadWindow for ASP.NET AJAX Q2 2008

RadWindow for ASP.NET AJAX which is part of the Q2 2008 release is fully backwards compatible with its previous version (Q1 2008).

## Important - differences between RadWindow for ASP.NET and RadWindow for ASP.NET AJAX:

**RadWindow for ASP.NET AJAX** control has changed slightly, because of moving to the ASP.NET Ajax framework and to the Telerik.Web.UI suite. A number of property and method names have changed, and a few properties and methods have been removed.

* On the Server-side, there have been some changes to the **RadWindowManager** and **RadWindow** classes:

* The following properties have been removed:

	|  **Class**  |  **Property**  |
	| ------ | ------ |
	|RadWindowManager|UseClassicWindows|
	|RadWindowManager|SingleNonMinimizedWindow|
	|RadWindow|Splash|

* For both classes, the following property names have changed:

	|  **Old name**  |  **New name**  |
	| ------ | ------ |
	|Behavior|Behaviors|
	|InitialBehavior|InitialBehaviors|

* On the client-side, the API is completely changed to match the naming convention of the new framework. The following property names are changed:In **RadWindowManager** class:

	|  **Old name**  |  **New name**  |
	| ------ | ------ |
	|Open|open|
	|GetWindowByName|getWindowByName|
	|GetWindowById|getWindowById|
	|GetActiveWindow|getActiveWindow|
	|GetWindowObjects|get_windows|
	|GetWindows|GetWindows|
	|Cascade|cascade|
	|Tile|tile|
	|RestoreAll|restoreAll|
	|MaximizeAll|maximizeAll|
	|MinimizeAll|minimizeAll|
	|ShowAll|showAll|
	|CloseAll|closeAll|
	|CloseActiveWindow|closeActiveWindow|
	|MinimizeActiveWindow|minimizeActiveWindow|
	|RestoreActiveWindow|restoreActiveWindow|

* In **RadWindow** class:

	|  **Old name**  |  **New name**  |
	| ------ | ------ |
	|GetWindowManager|get_windowManager|
	|GetContentFrame|get_contentFrame|
	|GetLeftPosition - removed|N/A|
	|GetTopPosition - removed|N/A|
	|GetTitlebar - removed|N/A|
	|GetStatusbar - removed|N/A|
	|SetOpenerElementId|set_openerElementID|
	|SetStatus|set_status|
	|GetStatus|get_status|
	|SetModal|set_modal|
	|SetWidth|set_width|
	|SetHeight|set_height|
	|GetWidth|get_width|
	|GetHeight|get_height|
	|SetOffsetElementId|set_offsetElementID|
	|SetTitle|set_title|
	|MoveTo|moveTo|
	|Center|center|
	|SetSize|setSize|
	|Show|show|
	|Hide|hide|
	|GetUrl|get_navigateUrl|
	|SetUrl|setUrl|
	|Reload|reload|
	|SetActive|setActive|
	|Minimize|minimize|
	|Restore|restore|
	|Maximize|maximize|
	|Close|close|
	|TogglePin|togglePin|
	|IsMaximized|isMaximized|
	|IsMinimized|isMinimized|
	|IsModal|isModal|
	|IsClosed|isClosed|
	|IsPinned|isPinned|
	|IsVisible|isVisible|
	|IsActive|isActive|
	|IsBehaviorEnabled|isBehaviorEnabled|

## See Also

 * [RadWindow Object]({%slug window/client-side-programming/radwindow-object%})

 * [RadWindowManager Object]({%slug window/client-side-programming/radwindowmanager-object%})

 * [Migration from RadWindow for ASP.NET (Classic) to RadWindow for ASP.NET AJAX]({%slug window/changes-and-backward-compatibility/migration-from-radwindow-for-asp.net-(classic)-to-radwindow-for-asp.net-ajax%})

 * [Using RadWindow as a Dialog]({%slug window/how-to/using-radwindow-as-a-dialog%})

repository: telerik/ajax-docs

gha_language: C#

repo_name: telerik/ajax-docs


text:
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="content/MudBlazor-GitHub-NoBg-Dark.png">
    <source media="(prefers-color-scheme: light)" srcset="content/MudBlazor-GitHub-NoBg.png">

  </picture>

# Material Design components for Blazor
![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/mudblazor/mudblazor/build-test-mudblazor.yml?branch=dev&logo=github&style=flat-square)
![Codecov](https://img.shields.io/codecov/c/github/MudBlazor/MudBlazor?logo=codecov&logoColor=white&style=flat-square&token=4BBNQPPATD)
[![GitHub](https://img.shields.io/github/license/mudblazor/mudblazor?color=594ae2&logo=github&style=flat-square)](https://github.com/mudblazor/MudBlazor/blob/master/LICENSE)
[![GitHub Repo stars](https://img.shields.io/github/stars/mudblazor/mudblazor?color=594ae2&style=flat-square&logo=github)](https://github.com/mudblazor/MudBlazor/stargazers)
[![GitHub last commit](https://img.shields.io/github/last-commit/mudblazor/mudblazor?color=594ae2&style=flat-square&logo=github)](https://github.com/mudblazor/mudblazor)
[![Contributors](https://img.shields.io/github/contributors/mudblazor/mudblazor?color=594ae2&style=flat-square&logo=github)](https://github.com/mudblazor/mudblazor/graphs/contributors)
[![Discussions](https://img.shields.io/github/discussions/mudblazor/mudblazor?color=594ae2&logo=github&style=flat-square)](https://github.com/mudblazor/mudblazor/discussions)
[![Discord](https://img.shields.io/discord/786656789310865418?color=%237289da&label=Discord&logo=discord&logoColor=%237289da&style=flat-square)](https://discord.gg/mudblazor)
[![Twitter](https://img.shields.io/twitter/follow/MudBlazor?color=1DA1F2&label=Twitter&logo=Twitter&style=flat-square)](https://twitter.com/MudBlazor)
[![Nuget version](https://img.shields.io/nuget/v/MudBlazor?color=ff4081&label=nuget%20version&logo=nuget&style=flat-square)](https://www.nuget.org/packages/MudBlazor/)
[![Nuget downloads](https://img.shields.io/nuget/dt/MudBlazor?color=ff4081&label=nuget%20downloads&logo=nuget&style=flat-square)](https://www.nuget.org/packages/MudBlazor/)

MudBlazor is an ambitious Material Design component framework for Blazor with an emphasis on ease of use and clear structure. It is perfect for .NET developers who want to rapidly build web applications without having to struggle with CSS and Javascript. MudBlazor, being written entirely in C#, empowers you to adapt, fix or extend the framework. There are plenty of examples in the documentation, which makes understanding and learning MudBlazor very easy.

## Documentation & Demo
- [MudBlazor.com](https://mudblazor.com)
- [Try.MudBlazor.com](https://try.mudblazor.com/)

### Why is MudBlazor so successful?
 - Clean and aesthetic graphic design based on Material Design.
 - Clear and easy to understand structure.
 - Good documentation with many examples and source snippets.
 - All components are written entirely in C#, no JavaScript allowed (except where absolutely necessary).
 - Users can make beautiful apps without needing CSS (but they can of course use CSS too).
 - No dependencies on other component libraries, 100% control over components and features.
 - Stability! We strive for a complete test coverage.
 - Releasing often so developers can get their PRs and fixes in a timely fashion.

## Prerequisities
| MudBlazor | .NET | Support |
| :--- | :---: | :---: |
| 1.x.x - 2.0.x | .NET 3.1 | Ended 03/2021 |
| 5.x.x | .NET 5 | Ended 01/2022 |
| 6.0.x | [.NET 6](https://dotnet.microsoft.com/download/dotnet/6.0) | :heavy_check_mark: |
| 6.1.x | [.NET 6](https://dotnet.microsoft.com/download/dotnet/6.0) & [.NET 7](https://dotnet.microsoft.com/en-us/download/dotnet/7.0) | :heavy_check_mark: |

## Stats
![Alt](https://repobeats.axiom.co/api/embed/db53a44092e88fc34a4c0f37db12773b6787ec7e.svg "Repobeats analytics image")

## Contributing
- Check out the [contribution guidelines](/CONTRIBUTING.md) if you want to help improve MudBlazor.

## Getting Started
- Full installation instructions can be found at [mudblazor.com](https://mudblazor.com/getting-started/installation)
- Alternatively use one of our templates from the [MudBlazor.Templates](https://github.com/mudblazor/Templates) repo.
### Quick Installation Guide

Install Package
```
dotnet add package MudBlazor
```
Add the following to `_Imports.razor`
```razor
@using MudBlazor
```
Add the following to the `MainLayout.razor` or `App.razor`
```razor
<MudThemeProvider/>
<MudDialogProvider/>
<MudSnackbarProvider/>
```
Add the following to `index.html` (client-side) or `_Host.cshtml` (server-side) in the `head`
```razor
<link href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,700&display=swap" rel="stylesheet" />
<link href="_content/MudBlazor/MudBlazor.min.css" rel="stylesheet" />
```
Add the following to `index.html` or `_Host.cshtml` in the `body`
```razor
<script src="_content/MudBlazor/MudBlazor.min.js"></script>
```

Add the following to the relevant sections of `Program.cs`
```c#
using MudBlazor.Services;
```
```c#
builder.Services.AddMudServices();
```

### Usage
```razor
<MudText Typo="Typo.h6">MudBlazor is @Text</MudText>
<MudButton Variant="Variant.Filled" Color="Color.Primary" OnClick="ButtonOnClick">@ButtonText</MudButton>

@code {
  public string Text { get; set; } = "????";
  public string ButtonText { get; set; } = "Click Me";
  public int ButtonClicked { get; set; }

  void ButtonOnClick()
  {
      ButtonClicked += 1;
      Text = $"Awesome x {ButtonClicked}";
      ButtonText = "Click Me Again";
  }
}
```

repository: Garderoben/MudBlazor

branch_name: refs/heads/dev

repo_name: Garderoben/MudBlazor


text:
# Nosql Encoding Ability.

[![Build Status](https://secure.travis-ci.org/snowyu/node-nosql-encoding.png?branch=master)](http://travis-ci.org/snowyu/node-nosql-encoding)

[![NPM](https://nodei.co/npm/nosql-encoding.png?stars&downloads&downloadRank)](https://nodei.co/npm/nosql-encoding/)

Add the encoding ability to the [abstract-nosql](https://github.com/snowyu/node-abstract-nosql) database.

# Usage

## Add the Encoding ability to a nosql database

    npm install nosql-encoding

```js

var addEncodingFeatureTo = require("nosql-encoding")
var LevelDB  = addEncodingFeatureTo(require("leveldown-sync"))

var db = LevelDB('location')
db.open({keyEncoding: 'text', valueEncoding: 'json'})

```

## Develop a nosql database with encoding ability

There is no need to force inherited from the Encoding class.

Please let the user decide whether to use the Encoding feature.

# Encoding Codec

See [buffer-codec](https://github.com/snowyu/node-buffer-codec).

repository: snowyu/node-nosql-encoding

repo_name: snowyu/node-nosql-encoding


text:
Temperature & humidity monitor
==============================

A small app for monitoring the humidity and temperature using a Raspberry Pi with SenseHat.

Sample usage:

    csruntime --host localhost -w 0 monitor-tweet.calvin --attr-file twitter_credentials.json

or, without twitter output

    csruntime --host localhost -w 0 monitor-print.calvin

The allowed range can be changed by modifying the following lines

    humid_range : std.SetLimits(lower=40, upper=80)
    temp_range: std.SetLimits(lower=20, upper=33)

and substituting whatever temperature and humidity is suitable. Note: Temperature is in centigrade (C).

When a value falls outside of the given interval, the background of the
SenseHat display will change to red and a tweet with the offending value will
be sent (if the twitter credentials are correctly configured in the
twitter\_credentials.json file)

__NOTE__: Do _not_ use this application for monitoring live animals if their
well-being and/or life depends on it functioning correctly! It has not been
tested extensively and it cannot be guaranteed to function the way you expect
it to.

Installation
============

Using [`raspbian jessie lite`](https://www.raspberrypi.org/downloads/raspbian/), with a working calvin installation,
run `install-deps.sh` to install necessary dependencies for this example. Note: It may be a good idea to expand the file
if this is not already done using [`raspi-config`](https://www.raspberrypi.org/documentation/configuration/raspi-config.md).

repository: imriss/calvin-base

gha_language: Python

repo_name: imriss/calvin-base


text:
# Bookmark-Manager

## If you want to run this project in your system please follow the steps below :

1. Create a virtual environment in your system.
2. Clone this project.
3. Run the Requirements.txt (pip install -r requirements.txt) .
4. Run the migrations.
5. create superuser for accessing admin panel.
6. Run the Django Server.
7. Follow the listed Url for accessing the Project Properly .

	- Endpoint which allows storing of any Customer's bookmark
		- http://localhost:8000/api/create/

	- Endpoint which allows browsing and filtration of API endpoint with the following query parameters:
	customer_id, latitude, longitude, source_name, title_contains etc.
		- http://localhost:8000/api/browse/

	- Endpoint which allows storing Customer.
		- http://localhost:8000/api/customer/

	- Endpoint which allows Detail and List view of all customer and can perform Update and delete operation.
		- http://localhost:8000/api/customer/1/

	- Endpoint which allows storing Bookmark .
		- http://localhost:8000/api/bookmark/

	- Endpoint which allows Detail and List view of all customer and can perform Update and delete operation.
		- http://localhost:8000/api/bookmark/1/

* `You can check filtering functionality by clicking Filter Button`
* `You can also check searching functionality by clicking Search bar `

###### I am sure all functions will be working properly.

### You can use any Browser .

##### For Create Bookmark :- http://localhost:8000/api/create/

###### Screenshot

##### For Browse Bookmark  :
- http://localhost:8000/api/browse/

###### Screenshot

##### For create and listing all Customer   :
- http://localhost:8000/api/customer/

###### Screenshot

##### For Retrieve, Update, PartialUpdate and Delete Customer :
- http://localhost:8000/api/customer/1/

###### Screenshot

##### For create and listing all Bookmark   :
- http://localhost:8000/api/bookmark/

###### Screenshot

##### For Retrieve, Update, PartialUpdate and Delete Bookmark :
- http://localhost:8000/api/bookmark/1/

###### Screenshot

repository: arabindamahato/Bookmark-Manager

repo_name: arabindamahato/Bookmark-Manager


text:
---
title: /resequenceList
position: 1.6
type: put
description: Re-order annotations in a list
---

###### Payload:

~~~ json
 {
  "canvas_id": "<Canvas ID>",
  "layer_id": "<Layer ID>",
  "annotation_ids": [ "<AnnotationID>", ... ]
}
~~~

repository: gigamorph/gp-test

repo_name: gigamorph/gp-test


text:
# Adding passes to LLPC

The process of creating and adding a pass to LLPC is very similar to LLVM's process.
You first need to create your pass. See https://llvm.org/docs/WritingAnLLVMNewPMPass.html for the LLVM documentation explaining how to create a pass.
As an example, here is the minimal code required to create a module pass:

```
class MyPass : public llvm::PassInfoMixin<MyPass> {
public:
  llvm::PreservedAnalyses run(llvm::Module &module, llvm::ModuleAnalysisManager &analysisManager) {
    // do something with the module...
    return llvm::PreservedAnalyses::none();
  }
  static llvm::StringRef name() { return "Full name of the pass"; }
};
```

Please, implement a static `name()` function like in this example for each pass added to LLPC so the passes can easily be identified in logs.
Once the pass is created, it needs to be registered to LLPC.

## Register a front-end pass

To register a front-end pass, you need to add an entry to the LLPC front-end pass registry (`llpc/lower/PassRegistry.inc`). For example:

`LLPC_PASS("short-name", MyPass)`

* `short-name` is a unique dash-separated short name used to identify the pass. This short name is for example used for the `--print-after` option to print LLVM IR after a given pass short name (e.g. `--print-after=short-name`).
* `MyPass` is the name of the pass class.

## Register a middle-end pass

The process to register a middle-end pass is the same. The middle-end pass registry file is `lgc/patch/PassRegistry.inc`.

repository: GPUOpen-Drivers/llpc

detected_licenses: MIT Apache-2.0 NCSA

repo_name: GPUOpen-Drivers/llpc


text:
WRAPPER.ECLASS
Section: eclass-manpages (5)
Updated: Sep 2020
Index Return to Main Contents
NAME
wrapper.eclass - create a shell wrapper script
FUNCTIONS
make_wrapper <wrapper> <target> [chdir] [libpaths] [installpath]
Create a shell wrapper script named wrapper in installpath (defaults to the bindir) to execute target (default of wrapper) by first optionally setting LD_LIBRARY_PATH to the colon-delimited libpaths followed by optionally changing directory to chdir.
MAINTAINERS
<EMAIL_ADDRESS>REPORTING BUGS
Please report bugs via https://bugs.gentoo.org/
FILES
wrapper.eclass
SEE ALSO
ebuild(5)
https://gitweb.gentoo.org/repo/gentoo.git/log/eclass/wrapper.eclass
Index
NAME
FUNCTIONS
MAINTAINERS
REPORTING BUGS
FILES
SEE ALSO
This document was created by man2html, using the manual pages.
Time: 00:27:04 GMT, October 11, 2020

gha_language: HTML