text:
gdstruct - GDS - General Data Structure
=======================================

A General Data Structure (GDS) is a universal, composable data structure, used to store any kind of data.
This could be for example the definition of configurations, specifications and data sets.
Typical usage is the definition of configurations, specifications and data sets.
The GDS language is a special DSL (domain specific language) for defining general data structures.
It uses a succinct, indentation-sensitive syntax which makes data clearer and more readable.
The building blocks for general data structures are hashes and arrays.

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

~~~
gem install gdstruct
~~~

A Short Example
===============

~~~ruby
require "gdstruct"

h = GDstruct.c( <<-EOS )
:
  a val a
  b val b
EOS

# => h = { a: 'val a', b: 'val b' }
~~~

An Introduction
===============

The GDS language uses two basic symbols (__:__ and __,__) for the creation of hashes and arrays.

A colon (__:__) is used to define a hash.
A comma (__,__) is used to define an array.

Use indentation with two spaces for the definition of elements and for nested structures.
Tab characters are not allowed for indentation.

## General Example

~~~
,
  v1
  : k2 v2
  : k31 v31 | k32 v32 | k33 v33
    k34 v34
    k35 v35 | k36 v36
  :
    k41 v41
    k42 v42
    k43,
    k44, 1 | 2 | 3
      4 | 5
      6
      7
      8 | 9
      :k441 v441
  v5

# =>  [ 'v1', { k2: 'v2' }, { k31: 'v31', k32: 'v32', k33: 'v33', k34: 'v34', k35: 'v35', k36: 'v36' },
        { k41: 'v41', k42: 'v42', k43: [], k44: [1, 2, 3, 4, 5, 6, 7, 8, 9, { k441: 'v441' } ] }, 'v5' ]
~~~

## Motivation and Features

  * the focus is on the essential data
  * structure and hierarchy is expressed using indentation (whitespace-sensitive) - avoids curly braces and square brackets
  * uses a succinct and minimalist syntax - tries to avoid unnecessary characters
  * in many cases colons, commas and quotes are not necessary
  * less text makes data clearer and more readable
  * for configuration and specification - replacement for XML, JSON, YAML
  * for data/database seeding
  * less text and less potential errors using schema definitions
  * supports block comments, which could be nested
  * allows also the definition of hash and array structures in a kind of restricted classic Ruby like syntax
  * provides an alternative for Ruby hash and array definition without using eval(); can be used as a protection against code injection vulnerabilities, e.g. on web servers

## Schema specifiers

Schema specifiers can be used to predefine the keys of a hash or subhash.
When you specify the values you no longer need to name the key for each value.
This facilitates the input for hashes and prevents typos for keys.
In combination with the pipe symbol (__\|__), which allows to define multiple values on a single line,
this features a slim and clearly arranged, table-like style for data.

~~~
$country(name,capital,area,population,vehicleRegistrationCode,iso3166code,callingCode)
, $country   /*
    name            capital            area (km^2)   population      vehicleRegistrationCode   iso3166code   callingCode
  ---------------------------------------------------------------------------------------------------------------------------- */
  : Deutschland   | Berlin           |    357_385  |    82_521_653 | D                       | DE          | 49
  : USA           | Washington, D.C. |  9_833_520  |   325_719_178 | USA                     | US          | 1
  : China         | Beijing          |  9_596_961  | 1_403_500_365 | CHN                     | CN          | 86
  : India         | New Dehli        |  3_287_469  | 1_339_180_000 | IND                     | IN          | 91
  : Austria       | Vienna           |     83_878  |     8_822_267 | A                       | AT          | 43
  : Denmark       | Copenhagen       |     42_921  |     5_748_769 | DK                      | DK          | 45
  : Canada        | Ottawa           |  9_984_670  |    36_503_097 | CDN                     | CA          | 1
  : France        | Paris            |    643_801  |    66_991_000 | F                       | FR          | 33
  : Russia        | Moscow           | 17_075_400  |   144_526_636 | RUS                     | RU          | 7
~~~
transforms to
~~~
[
  { :name=>"Deutschland", :capital=>"Berlin", :area=>357385, :population=>82521653, :vehicleRegistrationCode=>"D", :iso3166code=>"DE", :callingCode=>49 },
  { :name=>"USA", :capital=>"Washington, D.C.", :area=>9833520, :population=>325719178, :vehicleRegistrationCode=>"USA", :iso3166code=>"US", :callingCode=>1 },
  { :name=>"China", :capital=>"Beijing", :area=>9596961, :population=>1403500365, :vehicleRegistrationCode=>"CHN", :iso3166code=>"CN", :callingCode=>86 },
  { :name=>"India", :capital=>"New Dehli", :area=>3287469, :population=>1339180000, :vehicleRegistrationCode=>"IND", :iso3166code=>"IN", :callingCode=>91 },
  { :name=>"Austria", :capital=>"Vienna", :area=>83878, :population=>8822267, :vehicleRegistrationCode=>"A", :iso3166code=>"AT", :callingCode=>43 },
  { :name=>"Denmark", :capital=>"Copenhagen", :area=>42921, :population=>5748769, :vehicleRegistrationCode=>"DK", :iso3166code=>"DK", :callingCode=>45 },
  { :name=>"Canada", :capital=>"Ottawa", :area=>9984670, :population=>36503097, :vehicleRegistrationCode=>"CDN", :iso3166code=>"CA", :callingCode=>1 },
  { :name=>"France", :capital=>"Paris", :area=>643801, :population=>66991000, :vehicleRegistrationCode=>"F", :iso3166code=>"FR", :callingCode=>33 },
  { :name=>"Russia", :capital=>"Moscow", :area=>17075400, :population=>144526636, :vehicleRegistrationCode=>"RUS", :iso3166code=>"RU", :callingCode=>7 }
]
~~~

Futher Information
==================

You will find futher information here [https://urasepandia.de/gds.html](https://urasepandia.de/gds.html)

Maintainer
==========

Uli Ramminger<EMAIL_ADDRESS>
Copyright
=========

Copyright (c) 2018 Ulrich Ramminger

See MIT-LICENSE for further details.


text:
# ![LOGO](logo.png) Hangouts Chat **flow**ground Connector

## Description

A generated **flow**ground connector for the Hangouts Chat API (version v1).

Generated from: https://api.apis.guru/v2/specs/googleapis.com/chat/v1/swagger.json

Generated at: 2019-05-23T12:13:02+03:00

## API Description

Enables bots to fetch information and perform actions in Hangouts Chat.

## Authorization

This API does not require authorization.

## Actions

### Lists spaces the caller is a member of.

*Tags:* `spaces`

#### Input Parameters
* `pageSize` - _optional_ - Requested page size. The value is capped at 1000.
Server may return fewer results than requested.
If unspecified, server will default to 100.
* `pageToken` - _optional_ - A token identifying a page of results the server should return.
* `alt` - _optional_ - Data format for response.
    Possible values: json, media, proto.
* `callback` - _optional_ - JSONP
* `fields` - _optional_ - Selector specifying which fields to include in a partial response.
* `key` - _optional_ - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
* `oauth_token` - _optional_ - OAuth 2.0 token for the current user.
* `prettyPrint` - _optional_ - Returns response with indentations and line breaks.
* `quotaUser` - _optional_ - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
* `uploadType` - _optional_ - Legacy upload protocol for media (e.g. "media", "multipart").
* `upload_protocol` - _optional_ - Upload protocol for media (e.g. "raw", "multipart").

### Deletes a message.

*Tags:* `spaces`

#### Input Parameters
* `name` - _required_ - Required. Resource name of the message to be deleted, in the form
"spaces/*/messages/*"

Example: spaces/AAAAMpdlehY/messages/UMxbHmzDlr4.UMxbHmzDlr4
* `access_token` - _optional_ - OAuth access token.
* `alt` - _optional_ - Data format for response.
    Possible values: json, media, proto.
* `callback` - _optional_ - JSONP
* `fields` - _optional_ - Selector specifying which fields to include in a partial response.
* `key` - _optional_ - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
* `oauth_token` - _optional_ - OAuth 2.0 token for the current user.
* `prettyPrint` - _optional_ - Returns response with indentations and line breaks.
* `quotaUser` - _optional_ - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
* `uploadType` - _optional_ - Legacy upload protocol for media (e.g. "media", "multipart").
* `upload_protocol` - _optional_ - Upload protocol for media (e.g. "raw", "multipart").

### Returns a message.

*Tags:* `spaces`

#### Input Parameters
* `name` - _required_ - Required. Resource name of the message to be retrieved, in the form
"spaces/*/messages/*".

Example: spaces/AAAAMpdlehY/messages/UMxbHmzDlr4.UMxbHmzDlr4
* `access_token` - _optional_ - OAuth access token.
* `alt` - _optional_ - Data format for response.
    Possible values: json, media, proto.
* `callback` - _optional_ - JSONP
* `fields` - _optional_ - Selector specifying which fields to include in a partial response.
* `key` - _optional_ - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
* `oauth_token` - _optional_ - OAuth 2.0 token for the current user.
* `prettyPrint` - _optional_ - Returns response with indentations and line breaks.
* `quotaUser` - _optional_ - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
* `uploadType` - _optional_ - Legacy upload protocol for media (e.g. "media", "multipart").
* `upload_protocol` - _optional_ - Upload protocol for media (e.g. "raw", "multipart").

### Updates a message.

*Tags:* `spaces`

#### Input Parameters
* `name` - _required_ - Resource name, in the form "spaces/*/messages/*".

Example: spaces/AAAAMpdlehY/messages/UMxbHmzDlr4.UMxbHmzDlr4
* `updateMask` - _optional_ - Required. The field paths to be updated.

Currently supported field paths: "text", "cards".
* `alt` - _optional_ - Data format for response.
    Possible values: json, media, proto.
* `callback` - _optional_ - JSONP
* `fields` - _optional_ - Selector specifying which fields to include in a partial response.
* `key` - _optional_ - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
* `oauth_token` - _optional_ - OAuth 2.0 token for the current user.
* `prettyPrint` - _optional_ - Returns response with indentations and line breaks.
* `quotaUser` - _optional_ - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
* `uploadType` - _optional_ - Legacy upload protocol for media (e.g. "media", "multipart").
* `upload_protocol` - _optional_ - Upload protocol for media (e.g. "raw", "multipart").

### Lists human memberships in a space.

*Tags:* `spaces`

#### Input Parameters
* `pageSize` - _optional_ - Requested page size. The value is capped at 1000.
Server may return fewer results than requested.
If unspecified, server will default to 100.
* `pageToken` - _optional_ - A token identifying a page of results the server should return.
* `parent` - _required_ - Required. The resource name of the space for which membership list is to be
fetched, in the form "spaces/*".

Example: spaces/AAAAMpdlehY
* `callback` - _optional_ - JSONP
* `fields` - _optional_ - Selector specifying which fields to include in a partial response.
* `key` - _optional_ - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
* `oauth_token` - _optional_ - OAuth 2.0 token for the current user.
* `prettyPrint` - _optional_ - Returns response with indentations and line breaks.
* `quotaUser` - _optional_ - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
* `uploadType` - _optional_ - Legacy upload protocol for media (e.g. "media", "multipart").
* `upload_protocol` - _optional_ - Upload protocol for media (e.g. "raw", "multipart").

### Creates a message.

*Tags:* `spaces`

#### Input Parameters
* `parent` - _required_ - Required. Space resource name, in the form "spaces/*".
Example: spaces/AAAAMpdlehY
* `threadKey` - _optional_ - Opaque thread identifier string that can be specified to group messages
into a single thread. If this is the first message with a given thread
identifier, a new thread is created. Subsequent messages with the same
thread identifier will be posted into the same thread. This relieves bots
and webhooks from having to store the Hangouts Chat thread ID of a thread (created earlier by them) to post
further updates to it.

Has no effect if thread field,
corresponding to an existing thread, is set in message.
* `alt` - _optional_ - Data format for response.
    Possible values: json, media, proto.
* `callback` - _optional_ - JSONP
* `fields` - _optional_ - Selector specifying which fields to include in a partial response.
* `key` - _optional_ - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
* `oauth_token` - _optional_ - OAuth 2.0 token for the current user.
* `prettyPrint` - _optional_ - Returns response with indentations and line breaks.
* `quotaUser` - _optional_ - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
* `uploadType` - _optional_ - Legacy upload protocol for media (e.g. "media", "multipart").
* `upload_protocol` - _optional_ - Upload protocol for media (e.g. "raw", "multipart").

## License

**flow**ground :- Telekom iPaaS / googleapis-com-chat-connector

Copyright © 2019, [Deutsche Telekom AG](https://www.telekom.de)

contact<EMAIL_ADDRESS>
All files of this connector are licensed under the Apache 2.0 License. For details
see the file LICENSE on the toplevel directory.

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
---
title: "Triangles"
excerpt: "Three sides turn out to be incredibly useful."
date: "2020-06-12"
categories:
- "math"
header:
   teaser: "/assets/images/gillespedia/income-tax-chart.png"
mathjax: true
---

# Definition

A triangle is a closed, three-sided polygon. It's the easiest polygon to drawn.

## Components

Three edges.
Three corners.
Three angles.
An inside.
An outside.
Two dimensions.

## Kinds of Triangles

We categorize triangles into two different sets based on two different factors.

### Triangle Types by Their Biggest Angle

Obtuse
Right
Acute

### Triangle Types by Side Length Relations

Equilateral
Isocalese
Scalene

All equilateral triangles are acute. All equilateral triangles are also isocalese triangles.

# Trigonometry

Stuff

## SOHCAHTOA

Stuff

#

license: MIT

gha_language: HTML

gha_license_id: MIT


text:
---
heading: Facebook
seo: Endpoint Setup | Facebook | Cloud Elements API Docs
title: Endpoint Setup
description: Integrate Facebook into your application via the Cloud Elements APIs.
layout: docs
breadcrumbs: /docs/elements.html
elementId: 222
parent: Back to Element Guides
order: 2
---
## Endpoint Setup

Log in to your Facebook developer account at [https://developers.facebook.com/](https://developers.facebook.com/).

1. Select “My Apps” > “Add a New App”
![Facebook Connected App step 1](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI1.png)

2. Select “Website”
![Facebook Connected App step 2](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI2.png)

3. Click “Create New Facebook App ID”
![Facebook Connected App step 3](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI3.png)

4. Select “Choose a category”

5. Click “Create App ID”
![Facebook Connected App step 4](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI4.png)

6. Click “Skip Quick Start”
![Facebook Connected App step 5](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI5.png)

7. Under Settings > Under Basic: Copy the App ID

8. Copy the App Secret
![Facebook Connected App step 6](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI5.png)

9. Under Settings > Under Basic > Client OAuth Settings:  Input your app’s callback URL
![Facebook Connected App step 7](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI7.png)

10. Click “Save Changes”
![Facebook Connected App step 8](http://cloud-elements.com/wp-content/uploads/2015/12/FacebookAPI8.png)

Your app will need to be approved by Facebook prior to putting it in production.  You can create a “Test App” by selecting “Test App” in the left hand menu of the My App dashboard.

Once you are ready to release to production, you will need to submit your app for testing.  You can read more about the process at: [https://developers.facebook.com/docs/facebook-login/review/requirements](https://developers.facebook.com/docs/facebook-login/review/requirements)

Next [create an instance](facebook-create-instance.html).

repository: davewilks/Dave-Devportal

gha_language: JavaScript

repo_name: davewilks/Dave-Devportal


text:
---
ref: mueller2023certified
title: "Certified Training: Small Boxes are All You Need"
authors: Mark Niklas Müller*, Franziska Eckert*, Marc Fischer, Martin Vechev
year: 2023
month: 05
venue: ICLR (Spotlight)
projects: safeai
bibtex: '@inproceedings{
			mueller2023certified,
			title={Certified Training: Small Boxes are All You Need},
			author={Mark Niklas M{\"{u}}ller and Franziska Eckert and Marc Fischer and Martin T. Vechev},
			booktitle={The Eleventh International Conference on Learning Representations},
			year={2023},
			url={https://openreview.net/forum?id=7oFuxtJtUMH}
		}'
paper: https://openreview.net/forum?id=7oFuxtJtUMH
code: https://github.com/eth-sri/sabr
slides: https://files.sri.inf.ethz.ch/website/slides/mueller2023sabr_slides.pdf
#poster: https://files.sri.inf.ethz.ch/website/slides/mueller2021boosting_poster.pdf
image: assets/images/SABR.png
#talk: https://iclr.cc/virtual/2021/poster/3359
---

To obtain, deterministic guarantees of adversarial robustness, specialized training methods are used. We propose, SABR, a novel such certified training method, based on the key insight that propagating interval bounds for a small but carefully selected subset of the adversarial input region is sufficient to approximate the worst-case loss over the whole region while significantly reducing approximation errors. We show in an extensive empirical evaluation that SABR outperforms existing certified defenses in terms of both standard and certifiable accuracies across perturbation magnitudes and datasets, pointing to a new class of certified training methods promising to alleviate the robustness-accuracy trade-off.


text:
---
layout: post
title: How to open flipkart.com on mobile without app
date: '2016-02-13T10:47:00.000+05:30'
author: pawneshwer
comments: true
categories:
- how-to
description: open flipkart mobile version without app,open flipkart on mobile browser,open flipkart mobile site without app,no need to download flipkart app on mobile
keywords: open flipkart mobile version without app,open flipkart on mobile browser,open flipkart mobile site without app,no need to download flipkart app on mobile
modified_time: '2016-02-22T23:42:09.472+05:30'
blogger_id: tag:blogger.com,1999:blog-1967791069058877982.post-7433222531828751232
blogger_orig_url: http://www.edablogs.com/2016/02/how-to-open-flipkartcom-on-mobile-without-app.html
redirect_from:
- /2016/02/how-to-open-flipkartcom-on-mobile-without-app.html
---

{% include JB/setup %}

## open flipkart.com on mobile without app

Flipkart restricted mobile users to use flipkart mobile app. So now when you try to open flipkart.com on mobile browser then you will automatically redirect to Playstore to download mobile app. And if you already installed mobile app then app will open automatically. But using flipkart app consume memory and RAM. And if you are 2G users then this will take too much time to download mobile app from Playstore.

So here is solution for this problem, by this solution you don’t need to open or download flipkart mobile app. And you can browse flipkart mobile site which is designed to work on mobile browsers few months ago but after that flipkart decided to force users to download flipkart app.

[![](https://1.bp.blogspot.com/-hzBgwlkTyiE/Vr672gOH6nI/AAAAAAAAIRI/x8JNn9mn8p4/s1600/Screenshot_2016-02-13-10-26-40%2Bcopy.png)](https://1.bp.blogspot.com/-hzBgwlkTyiE/Vr672gOH6nI/AAAAAAAAIRI/x8JNn9mn8p4/s1600/Screenshot_2016-02-13-10-26-40%2Bcopy.png)

Solution is quite easy. Simply open following URL.

### [dl.flipkart.com](dl.flipkart.com "flipkart mobile site")

when you enter this URL in mobile browser then flipkart mobile site will open instead of flipkart app.


text:
---
title: DNS66 Host-based Blocker for Android
author: PipisCrew
date: 2016-10-28
categories: [android]
toc: true
---

Is a host-based blocker for Android devices that is easy to setup and does not require root or special permissions.

http://www.ghacks.net/2016/10/25/dns66-host-based-blocker-for-android/

origin - http://www.pipiscrew.com/?p=6228 dns66-host-based-blocker-for-android


text:
# Gradle Example

This is an example project that leverages protoc-gen-doc. You can test it out by running `gradle generateProto`.

After a successful run, you should see `grpc-docs.md` in the _build/generated/source/proto/main/doc_ directory.

repository: pseudomuto/protoc-gen-doc

gha_language: Go

repo_name: pseudomuto/protoc-gen-doc


text:
---
hrs_structure:
  division: '5'
  volume: '14'
  title: '37'
  chapter: '708'
  section: 708-852
type: hrs_section
tags:
  - Crime
  - Criminal Proceeding
menu:
  hrs:
    identifier: HRS_0708-0852
    parent: HRS0708
    name: 708-852 Forgery in the second degree
weight: 22315
title: Forgery in the second degree
full_title: 708-852 Forgery in the second degree
---
**§708-852 Forgery in the second degree.** (1) A person commits the offense of forgery in the second degree if, with intent to defraud, the person falsely makes, completes, endorses, or alters a written instrument, or utters a forged instrument, or fraudulently encodes the magnetic ink character recognition numbers, which is or purports to be, or which is calculated to become or to represent if completed, a deed, will, codicil, contract, assignment, commercial instrument, or other instrument which does or may evidence, create, transfer, terminate, or otherwise affect a legal right, interest, obligation, or status.

(2) Forgery in the second degree is a class C felony. [L 1972, c 9, pt of §1; am L 1988, c 155, §3; gen ch 1992; am L 1997, c 243, §3]

Case Notes

Charges in indictment held sufficient though inarticulately drawn. 55 H. 621, 525 P.2d 571 (1974).

There was substantial evidence which a reasonable mind might accept as adequate to convict defendant. 79 H. 175 (App.), 900 P.2d 172 (1995).

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
# Title : Note Taker

  ## Table of Contents
  * [Title](#Title)
  * [Description](#Description)
  * [Installation](#Installation)
  * [License](#license)
  * [Contributors](#Contributors)
  * [Preview](#Preview)
  * [Questions](#Questions)

  ## Description:
  This application can be used to write, save, and delete notes that you have written. This application will use an express backend and save and retrieve note data from a JSON file.

   Direct link to application: https://note-taker-hw1.herokuapp.com/

  ## Installation
  Clone the repository to your local development environment.

  git clone https://github.com/sxiong6901/NoteTaker
  Navigate to the developer-profile-generator folder using the command prompt.

  Run npm install to install all dependencies. To use the application locally, run node server.js in your CLI, and then open http://localhost:3000 in your preferred browser. The Note Taker app is live on Heroku for you to use as well.

  ## License
  MIT License - URL: https://github.com/sxiong6901/NoteTaker/blob/main/LICENSE

  ## Contributors
  https://github.com/sxiong6901

  ## Preview
  ![Testing](https://github.com/sxiong6901/NoteTaker/blob/main/assets/Test.gif)

  ## Questions
  If you have any questions, contact sxiong6901 on GitHub.

branch_name: refs/heads/main


text:
# eCommerceStoreIonic
Complete eCommerce Store With Powerful Vite biz back end ASP.net based CMS designed for eCommerce

For Webservices please refer this link

eCommerce app powered by Vitebiz

ViteCommerce is a starter project to create eCommerce Store Mobile app in Ionic!
This project is the product of many years of iterative development and combined community knowledge from secure asp.net based backend projects.

Website: http://www.vitebiz.com/

Twitter: @vitebiz

Let’s start

Choose one of the following options:

Download the latest stable release from Github

Create a new account in Vite biz eCommerce   http://www.vitebiz.com/storeadmin/Login.aspx

Upload logo files and Items which you want to upload

Get API key & userid from vitebiz

Update app.js file

Have fun!

How to integrate vite biz with your app

In App.js file :

   $rootScope.UserId=1124;
  $rootScope.Token='rbPCXgaW';

Modify these two variables with your details from vitebiz.com

Features

Complete eCommerce Webstore .

Includes:

Create / Modify Attributes

Manage Currencies

Multi Location options

Dynamic payment gateway integration

Multiple Currencies

Hosted Solution

And many more features

For Webservices please refer this link

Web Services Documentation  http://www.vitebiz.com/documents/ecommerceapp/

 Hire Developer  for your Custom needs

or <a<EMAIL_ADDRESS>send Email to Mandip


text:
# Build an SAP Fiori Application and Attach It to a Transport Request on an ABAP System

Build an application based on SAPUI5 or SAP Fiori with Jenkins and attach the build result to a transport request in an SAP ABAP system.

Generally, you can choose between two technical ways to attach a binary to an ABAP transport request: We support uploads through RFC and through OData. Which option to use depends on the version of your ABAP system. For AS ABAP 7.50 SP08, 7.51 SP07, or 7.52 SP03 and newer, use the OData-based upload, for older versions, use the RFC-based upload.

## Prerequisites

* You have set up your [Docker environment](https://docs.docker.com/get-started/).
* You have set up project “Piper”. See [guided tour](../../../guidedtour/).
* You have a transport request. In General it is possible to create a transport request on the fly. But the example here is based on an already existing transport request.
* Depending on the version of the ABAP system: Docker image for attaching binaries to transport requests via RFC available. Due to legal reasons there is no pre-build docker image. How to create the docker image is explained [here](https://github.com/SAP/devops-docker-images/tree/master/node-rfc)

### Project Prerequisites

This scenario requires additional files in your project and in the execution environment on your Jenkins instance.

On the project level, provide and adjust the following template:

| File Name | Description | Position |
|-----|-----|-----|
| [`mta.yaml`](https://github.com/SAP/jenkins-library/blob/master/documentation/docs/scenarios/rfc-upload/files/mta.yaml) | This file controls the behavior of the multitarget application (MTA) toolset. | Place the `mta.yaml` file in your application root folder and adjust the values in brackets with your data. |

Depending on the modules in your MTA, additional configuration files are required, e.g. `pom.xml`  or `package.json`.

## Context

This scenario combines various different steps to create a complete pipeline.

In this scenario, we want to show how to build an application based on SAPUI5 or SAP Fiori by using the MTA concept and how to attach the build result to a transport request inside an ABAP system. This document comprises the [mtaBuild](../../../steps/mtaBuild/) step and the [transportRequestUploadRFC](../../../steps/transportRequestUploadRFC/) respectively the [transportRequestUploadCTS](../../../steps/transportRequestUploadCTS/) step.

In case of an RFC based upload the binary is not streamed to the ABAP endpoint. Instead an URL pointing to the binary needs to be provided. Hence the binary must be published first so that it can be accessed via HTTP. This can happen by uploading the binary to a blob store or by archiving the artifact on Jenkins. The corresponding URL needs to be provided when the artifact is attached to the transport request.

The transport request can be created on the fly (see [transportRequestCreate](../../../steps/transportRequestCreate/)) or we can use an already existing transport request. In case we use an already existing transport request Id the transport request Id needs to be provided in the git commit history (see  [transportRequestReqIDFromGit](../../../steps/transportRequestReqIDFromGit/)) or the transport request Id needs to be provided inside the job (e.g. as a job parameter).

The transport request can be closed by the pipeline job (see [transportRequestRelease](../../../steps/transportRequestRelease/)).

This is an example of a Git commit message containing the transport request ID:

```
The headline

The body. The blank line above is mandatory (Git standard).
TransportRequest: <YOUR TRANSPORT REQUEST ID>
```

By default, the Git commits between the merge base with the base branch (default: `master`) and the current branch head are traversed.

![This pipeline in Jenkins Blue Ocean](images/pipeline.png)

**Screenshot: Build and Deploy Process in Jenkins**

## Examples

### Upload via RFC

#### Jenkinsfile

Following the convention for pipeline definitions, use a `Jenkinsfile`, which resides in the root directory of your development sources.

```groovy
@Library('piper-lib-os') _

pipeline {

    agent any

    stages {
        stage("prepare") {
            steps {
                deleteDir()
                checkout scm
                setupCommonPipelineEnvironment script: this
            }
        }

        stage('build') {
            steps {
                // It depends on your project, what needs to be done here. Maybe it's sufficient to zip the sources
                mtaBuild script: this
            }
        }

        stage('publish') {
            steps {
                // This uploads the binary into a blob store so that it can be attached to a transport request later
                sh "curl --upload-file <deployable> <BLOB_STORE/path/to/application>"

                // OR (in case there is no BLOB_STORE available)

                // This makes the artifact available on Nexus. The URL is the following:
                // <JENKINS_URL>/job/<JOB_NAME>/<BUILD_NUMBER>/artifact/<DEPLOYABLE>. Nota bene: this format is not an Jenkins API.
                // The build number can be retrieved during the build through ${currentBuild.number}
                archiveArtifacts artifacts: <deployable>
            }
        }

        // This attaches the deployable to a transport request
        stage('attach') {
            steps {
                transportRequestUploadRFC script: this,
                                           transportRequestId: '<TRANSPORT_REQUEST_ID>', // This can be omitted if present inside a Git commit message
                                           applicationUrl: '<THE_URL_TO_THE_DEPLOYABLE_ACCORDING_TO_PUBLISH_STAGE>'
            }
        }
    }
}
```

#### Configuration (`.pipeline/config.yml`)

This is a basic configuration example, which is also located in the sources of the project.

```yaml
steps:
  transportRequestUploadRFC:
    changeManagement:
      endpoint: 'https://your.rfc.endpoint.com/' # e.g. example.com'
      credentialsId: 'RFC' # The ID under which the credentials are provided on Jenkins defaults to 'CM'
      instance: '01' # needs to be adjusted
      client: '001' # needs to be adjusted
    abapPackage: 'YOURPACK'
    applicationName: 'YOURAPP'
    applicationDescription: 'Your application description'
    dockerImage: 'my/rfc-client'
```

### Upload via ODATA

#### Jenkinsfile

Following the convention for pipeline definitions, use a `Jenkinsfile`, which resides in the root directory of your development sources.

```groovy
@Library('piper-lib-os') _

pipeline {

    agent any

    stages {
        stage("prepare") {
            steps {
                deleteDir()
                checkout scm
                setupCommonPipelineEnvironment script: this
            }
        }

        stage('build') {
            steps {
                // It depends on your project, what needs to be done here.
                // Use the SAPUI5 toolset to build your SAPUI5 application
                // and run the build command of the npmExecuteScripts step.
                npmExecuteScripts(script: this, runScripts: ['build'])
            }
        }
        // Get the transport request id from your git commit message.
        stage('request') {
            steps {
                transportRequestReqIDFromGit( script: this )
            }
        }
        // This attaches the deployable to a transport request.
        // Note: ODATA/CTS does not support the mtaBuild tool.
        stage('attach') {
            steps {
                transportRequestUploadCTS script: this)
            }
        }
    }
}
```

#### Configuration (`.pipeline/config.yml`)

This is a basic configuration example, which is also located in the sources of the project.

```yaml
steps:
  transportRequestUploadCTS:
    changeManagement:
      endpoint: 'http://your.odata.endpoint/'
      credentialsId: 'CTS' # The ID under which the credentials are provided on Jenkins defaults to 'CM'
      clientOpts: '' # additional java options, e.g. '-Djavax.net.ssl.trustStore=/path/to/truststore.jks'
      client: '001'
    abapPackage: 'YOURPACK'
    applicationName: 'YOURAPP'
    applicationDescription: 'Your description'
```

## Parameters

For the detailed description of the relevant parameters, see:

* [transportRequestUploadCTS](../../../steps/transportRequestUploadCTS/)
* [transportRequestReqIDFromGit](../../../steps/transportRequestReqIDFromGit/)
* [npmExecuteScripts](../../../steps/npmExecuteScripts/)

repository: SAP/jenkins-library

repo_name: SAP/jenkins-library


text:
# Observability Overview

This document attempts to explain how the different components in Open Cluster Management Observabilty come together to deliver multicluster fleet observability. We do leverage several open source projects: [Grafana](https://github.com/grafana/grafana), [Alertmanager](https://github.com/prometheus/alertmanager), [Thanos](https://github.com/thanos-io/thanos/), [Observatorium Operator and API Gateway](https://github.com/observatorium), [Prometheus](https://github.com/prometheus/prometheus); We also leverage a few [Open Cluster Mangement projects](https://open-cluster-management.io/) namely - [Cluster Manager or Registration Operator](https://github.com/open-cluster-management/registration-operator), [Klusterlet](https://github.com/open-cluster-management/registration-operator), [multicloud operators placementrule](https://github.com/open-cluster-management/multicloud-operators-placementrule). The multicluster-observability operator is the root operator which pulls in all things needed.

## Conceptual Diagram

![Conceptual Diagram of the Components](docs/images/observability_overview_in_ocm.png)

## Associated Github Repositories

Component |Git Repo	| Description
---  | ------ | ----
MCO Operator | [multicluster-observability-operator](https://github.com/open-cluster-management/multicluster-observability-operator) | Operator for monitoring. This is the root repo. If we follow the Readme instructions here to install, the code from all other repos mentioned below are used/referenced.
Endpoint Operator | [endpoint-metrics-operator](https://github.com/open-cluster-management/endpoint-metrics-operator) | Operator that manages  setting up observability and data collection at the managed clusters.
Observatorium Operator | [observatorium-operator](https://github.com/open-cluster-management/observatorium-operator) | Operator to deploy the Observatorium project. Inside the open cluster management, at this time, it means metrics using Thanos. Forked from main observatorium-operator repo.
Metrics collector | [metrics-collector](https://github.com/open-cluster-management/metrics-collector) | Scrapes metrics from Prometheus at managed clusters, the metric collection being shaped by configuring allow-list.
RBAC Proxy | [rbac_query_proxy](https://github.com/open-cluster-management/rbac-query-proxy) | Helper service that acts a multicluster metrics RBAC proxy.
Grafana | [grafana](https://github.com/open-cluster-management/grafana) | Grafana repo -  for  dashboarding and metric analytics. Forked from main grafana repo.
Dashboard Loader | [grafana-dashboard-loader](https://github.com/open-cluster-management/grafana-dashboard-loader) | Sidecar proxy to load grafana dashboards from configmaps.
Management Ingress | [management-ingress](https://github.com/open-cluster-management/management-ingress) | NGINX based ingress controller to serve Open Cluster Management services.
Observatorium API | [observatorium](https://github.com/open-cluster-management/observatorium) | API Gateway which controls reading, writing of the Observability data to the backend infrastructure. Forked from main observatorium API repo.
Thanos Ecosystem | [kube-thanos](https://github.com/open-cluster-management/kube-thanos) | Kubernetes specific configuration for deploying Thanos. The observatorium operator leverages this configuration to deploy the backend Thanos components.

## Quick Start Guide

### Prerequisites

- go version v1.15+.
- docker version 17.03+.
- kubectl version v1.16.3+.
- Access to a Kubernetes v1.11.3+ cluster.

Use the following quick start commands for building and testing the Multicluster Observability Operator:

### Clone the Repository

Check out the multicluster-observability-operator repository.

```
$ git clone git@github.com:open-cluster-management/multicluster-observability-operator.git
$ cd multicluster-observability-operator
```

### Build the Operator

Build the multicluster-observability-operator image and push it to a public registry, such as Quay.io.

```
$ make -f Makefile.prow build
$ docker build -f Dockerfile -t quay.io/<YOUR_USERNAME_IN_QUAY>/multicluster-observability-operator:latest .
$ docker push quay.io/<YOUR_USERNAME_IN_QUAY>/multicluster-observability-operator:latest
```

### Run the Operator in the Cluster

1. Before you deploy the Multicluster Observability Operator in the cluster, you need to installed the following dependencies:

- The [cert-manager](https://github.com/open-cluster-management/cert-manager) is deployed into the cluster
- The following required CRDs are installed in the cluster:
  * [clustermanagementaddons.addon.open-cluster-management.io](https://github.com/open-cluster-management/api/blob/main/addon/v1alpha1/0000_00_addon.open-cluster-management.io_clustermanagementaddons.crd.yaml)
  * [managedclusteraddons.addon.open-cluster-management.io](https://github.com/open-cluster-management/api/blob/main/addon/v1alpha1/0000_01_addon.open-cluster-management.io_managedclusteraddons.crd.yaml)
  * [placementrules.apps.open-cluster-management.io](https://github.com/open-cluster-management/multicloud-operators-placementrule/blob/main/deploy/crds/apps.open-cluster-management.io_placementrules_crd.yaml)

2. Then deploy the CRDs of the Multicluster Observability Operator:

```
$ kubectl apply -f deploy/crds/observability.open-cluster-management.io_multiclusterobservabilities_crd.yaml
$ kubectl apply -f deploy/req_crds
```

3. Create the `open-cluster-management` and `open-cluster-management-observability` namespaces if they doesn't exist:

```
$ kubectl create ns open-cluster-management
$ kubectl create ns open-cluster-management-observability
```

4. Deploy the minio service which acts as storage service of the multicluster observability:

```
$ git clone --depth 1 git@github.com:open-cluster-management/observability-e2e-test.git
$ kubectl apply -f observability-e2e-test/cicd-scripts/e2e-setup-manifests/minio
```

5. Replace the operator image and deploy the Multicluster Observability Operator:

```
$ operator_image=quay.io/<YOUR_USERNAME_IN_QUAY>/multicluster-observability-operator:latest
$ sed -i "s~image:.*$~image: ${operator_image}~g" deploy/operator.yaml
$ kubectl apply -f deploy
```

6. Deploy the Multicluster Observability Operator CR:

```
$ kubectl apply -f deploy/crds/observability.open-cluster-management.io_v1beta1_multiclusterobservability_cr.yaml
```

7. Verify all the components for the Multicluster Observability are starting up and runing:

```
$ kubectl -n open-cluster-management-observability get pod
NAME                                                              READY   STATUS    RESTARTS   AGE
alertmanager-0                                                    2/2     Running   0          5m
grafana-6878c8b44-kxx6k                                           2/2     Running   0          5m
minio-79c7ff488d-rqmfg                                            1/1     Running   0          5m
observability-observatorium-observatorium-api-8646457ff9-6kw5v    1/1     Running   0          5m
observability-observatorium-thanos-compact-0                      1/1     Running   0          5m
observability-observatorium-thanos-query-fdc9b77b-7hxgc           1/1     Running   0          5m
observability-observatorium-thanos-query-frontend-8764896b99597   1/1     Running   0          5m
observability-observatorium-thanos-receive-controller-86982stcb   1/1     Running   0          5m
observability-observatorium-thanos-receive-default-0              1/1     Running   0          5m
observability-observatorium-thanos-rule-0                         2/2     Running   0          5m
observability-observatorium-thanos-store-memcached-0              2/2     Running   0          5m
observability-observatorium-thanos-store-shard-0-0                1/1     Running   0          5m
observatorium-operator-845dc69ccf-gdzn2                           1/1     Running   0          5m
rbac-query-proxy-559b788777-ssmls                                 1/1     Running   0          5m
```

### Uninstall the Operator in the Cluster

1. Delete the Multicluster Observability Operator CR:

```
$ kubectl apply -f deploy/crds/observability.open-cluster-management.io_v1beta1_multiclusterobservability_cr.yaml
```

2. Delete the Multicluster Observability Operator:

```
$ kubectl delete -f deploy
```

3. Delete the minio service:

```
$ kubectl delete -f observability-e2e-test/cicd-scripts/e2e-setup-manifests/minio
```

4. Delete the `open-cluster-management` and `open-cluster-management-observability` namespaces:

```
$ kubectl delete ns open-cluster-management open-cluster-management-observability
```

5. Then delete the CRDs of the Multicluster Observability Operator:

```
$ kubectl delete -f deploy/crds/observability.open-cluster-management.io_multiclusterobservabilities_crd.yaml
$ kubectl delete -f deploy/req_crds
```

6. Delete the dependencies


text:
[![npm](https://img.shields.io/npm/v/npm.svg)](https://github.com/MacKentoch/react-native-ibeacons)

# react-native-ibeacons

![logo](./images/RN-iBeacon.png)

`react-native-ibeacons`: add beacon technology in your React Native application for both iOS and Android.

This repository is born to keep alive and up to date these 2 original awesome:
- [ibeacon for android](https://github.com/mmazzarolo/react-native-beacons-android)
- [ibeacon for iOS](https://github.com/frostney/react-native-ibeacon)

If you want to know more about just have a look at [my medium article](https://medium.com/@erwan.datin/mmazzarolohow-to-play-with-ibeacons-in-a-react-native-application-5cef754b2edc#.e2bvgplvy).

## Install (iOS and Android)

> Ensure to have NodeJS >= v6.x.
>
> You must run on **real devices** (*don't forget to active Bluetooth when running*).

**Mobile Version compatibility:**

> - **iOS** `minimum version`
>   -  8.0
> - **Android** `minimum version`
>   - 21 (*alias LOLLIPOP*)

### 1. get modules
*via npm:*
```javascript:
npm install react-native-ibeacons
```
*or via yarn:*
```javascript:
yarn install react-native-ibeacons
```
### 2. link to your application

```javascript
react-native link react-native-ibeacons
```
### 3.a configuration specific to iOS

> IMPORTANT: you have to set `Bluetooth` and `localization service` in background Modes

![ios: active background mode](./images/bgmode.gif)

### 3.b configuration specific to Android

Nothing (lucky Android :smile:).

## 4 usage

### 4.a iOS

```javascript
var React = require('react-native');
var {DeviceEventEmitter} = React;

var Beacons = require('react-native-ibeacon');

// Define a region which can be identifier + uuid,
// identifier + uuid + major or identifier + uuid + major + minor
// (minor and major properties are numbers)
var region = {
    identifier: 'Estimotes',
    uuid: 'B9407F30-F5F8-466E-AFF9-25556B57FE6D'
};

// Request for authorization while the app is open
Beacons.requestWhenInUseAuthorization();

Beacons.startMonitoringForRegion(region);
Beacons.startRangingBeaconsInRegion(region);

Beacons.startUpdatingLocation();

// Listen for beacon changes
var subscription = DeviceEventEmitter.addListener(
  'beaconsDidRange',
  (data) => {
    // data.region - The current region
    // data.region.identifier
    // data.region.uuid

    // data.beacons - Array of all beacons inside a region
    //  in the following structure:
    //    .uuid
    //    .major - The major version of a beacon
    //    .minor - The minor version of a beacon
    //    .rssi - Signal strength: RSSI value (between -100 and 0)
    //    .proximity - Proximity value, can either be "unknown", "far", "near" or "immediate"
    //    .accuracy - The accuracy of a beacon
  }
);
```

### 4.b Android

```javascript
import { DeviceEventEmitter } from 'react-native'
import Beacons from 'react-native-beacons-android'

// Tells the library to detect iBeacons
Beacons.detectIBeacons()

// Start detecting all iBeacons in the nearby
try {
  await Beacons.startRangingBeaconsInRegion('REGION1')
  console.log(`Beacons ranging started succesfully!`)
} catch (err) {
  console.log(`Beacons ranging not started, error: ${error}`)
}

// Print a log of the detected iBeacons (1 per second)
DeviceEventEmitter.addListener('beaconsDidRange', (data) => {
  console.log('Found beacons!', data.beacons)
})
```

## license
The MIT License (MIT)

Copyright (c) 2017 Erwan DATIN

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.

repository: ismaeldcom/react-native-ibeacons

repo_name: ismaeldcom/react-native-ibeacons


text:
---
title: Getting Your API Key
category: documentation
position: 3
description: Instructions on how to get your unique API Key for authenticating CloudHealth API calls.
parameters:
  - name:
    content:
content_markdown: |-
  #### How CloudHealth Validates API Requests
  You need an API Key in order to make authenticated requests to the CloudHealth API service.

  An API Key is a globally unique identifier (GUID) that CloudHealth generates for each user in the platform. When you make an API request, this GUID uniquely identifies and authenticates you as the originator of the request.

  To request an API key, click on My Profile in your user settings.

  ![](images/user-profile.png)

  In your profile settings, scroll to the API Key section and click **Get API Key**. Then click **Save Profile Changes**.

  ![](images/generate-api-key.png)

  Include this GUID with each API request to authenticate into the CloudHealth platform.

  #### Periodic Key Rotation
  While securing your API Key is important, it is also essential to periodically rotate your API key for security reasons. To update your key, return to your profile settings and click **Get API Key** to create a new one. Then click **Save Profile Changes**. When you generate an API Key, the previous key becomes invalid.

  The API enforces all the same authentication and authorization checks as the CloudHealth Platform. Therefore, users in an organization can only see data scoped to their organization. Additionally, the API enforces any restrictions to user roles.
---

gha_language: SCSS


text:
# jQuery getPath

jQueryGetPath is a simple jQuery extension to get the CSS Path of any element in the DOM as uniquely as possible.

## Quick start

1. Install using bower
   ```bash
   bower install jquery-get-path
   ```
   Include the jQueryGetPath.js file in your project

2. Download source from GitHub

## How do I use it in my code ?

   ```js
   jQuery(element).getPath(); //That's all you need
   ```

[Demo](http://htmlpreview.github.io/?https://github.com/arjshiv/jQueryGetPath/blob/master/dist/index.html)

## Features

* Works with jQuery 1.x and 2.x
* Easy to use
* Errs on the side of specificity

## Browser support

* Chrome *(latest 2)*
* Firefox *(latest 2)*
* Internet Explorer 8+
* Opera *(latest 2)*
* Safari *(latest 2)*

## Contributing

Anyone and everyone is welcome to [contribute](CONTRIBUTING.md).

## License

The code is available under the [MIT license](LICENSE.txt).

## Credits
Credit to [HTML5 Boilerplate](https://github.com/h5bp/html5-boilerplate) for helping me build out this sample

repository: arjshiv/jQueryGetPath

repo_name: arjshiv/jQueryGetPath


text:
# **Running detachable base fw tests**

FAFT is currently not supported for detachable base tests because it does not
support two ECs on the same device.
[Tracking bug](https://issuetracker.google.com/36075961). Because of this,
the firmware tests for detachable bases were written as scripts that need to be
manually run on the DUT. Setting up and running the tests takes approximately
1-2 hours and keyboard EC firmware updates are fairly infrequent
(once a year on average pre-FSI, and ~once post-FSI).
([Test plan](https://docs.google.com/document/d/184RiP2QupCRg5REyNaGTVskHrgLHpLs5PutMzbsgfFo/edit?pli=1))

# **Prepare Host and DUT**

Tests already come installed in the DUT ChromeOS test image at
**‘/usr/local/bin/hammertests’**. Before you start, ensure that the test folder
exists in the test image.

A list of current devices with detachable base mappings is as follows:

|       Device         |Detachable keyboard            |
|----------------------|-------------------------------|
|Poppy                 |Hammer
|Soraka                |Staff
|Nocturne              |Whiskers
|Krane                 |Masterball
|Kodama                |Magnemite

## ON HOST

 1.  Create a [chroot](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md#Create-a-chroot)
     from [ToT checkout](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md#Get-the-source-code).

 2.  Obtain the images that will be used in the tests. Obtain the base ec image
from GoldenEye/ BCS/ APFE.
[Usually the dev will have supplied the image in the testing request bug or
indicated where to download it from, because these tests are typically run
before RO is locked in the firmware branch].

 5.  Select build # you want to test.

 6.  Select board name.

 7.  Download the ‘`firmware_from_source.tar`’ file and unzip.

		Change directory into the unzipped folder then cd into the base
		ec firmware folder (e.g. staff).

		Inside the base ec firmware folder, copy *ec.bin* into the
		chroot created in step 1. You can rename this file if you wish
		to indicate that it’s base firmware e.g. *staff_ec.bin*.

 10.  Flash the keyboard EC with the image obtained in step 2, following the
 steps below:

      a. Expose the servo header in the base keyboard by partially opening the
      back and/ or cutting out the covering to expose the servo header. Note
      that for some devices (tablets), removing the entire back cover will
      result in the keyboard not working as the pogo pins will detach.

      b. Use servo v4 + micro to flash the base firmware. **Ensure that the
      tablet is not powering the base and is completely detached when flashing
      the firmware** using the commands below. Run these commands inside chroot
      to flash the base ec firmware (this assumes you’re in the top-level
      directory of the tot checkout and inside chroot)

		E.g. for staff:

		Start servod

			sudo servod -b hammer

		Power the base:

			dut-control spi1_vref:pp3300 spi1_buf_en:on spi1_buf_on_flex_en:on

		 Flash the base with ec image (refer to device: base mapping at the start of
		 this document):

			src/platform/ec/util/flash_ec --board=hammer --image=staff_ec.bin.
		You should see the flashing completing successfully.

		Power off the base:

			dut-control spi1_vref:off spi1_buf_en:off spi1_buf_on_flex_en:off

		c. Reconnect the base to the tablet and check that keyboard/
		trackpad works i.e. type a key and see output on the display,
		move the trackpad and see output on the display.

3.  Generate the images needed for tests, from the base ec image obtained in
step 5 following the steps below:

	a.   **Inside chroot**: Run the shell script
	[gen_test_images.sh](https://chromium.googlesource.com/chromiumos/third_party/autotest/+/HEAD/server/cros/faft/gen_test_images.sh) that generates the necessary
	images, supplying ec.bin as the first argument for the BOARD name
	(where board is the name of the detachable base) and the IMAGE name as
	the second argument e.g. for staff:

		./src/third_party/autotest/files/server/cros/faft/gen_test_images.sh staff staff_ec.bin

	**The above script needs to run inside chroot  of the DUT host**

	Ensure that the ec.bin image used above is the same image running on the
	base ec of the DUT. If they are different, RW verification will fail
	during testing.

	You should then see the following 17 images created:

	1.  *EC_RW.bin*
	2. *staff_corrupt_first_byte.bin*
	3. *staff.dev.hex*
	4. *staff.dev.rb9*
	5. *key.vbprik2*
	6. *staff_corrupt_first_byte.bin.hex*
	7. *staff.dev.rb0*
	8. *staff.dev.rb9.hex*
	9. *key.vbpubk2*
	10. *staff_corrupt_last_byte.bin*
	11. *staff.dev.rb0.hex*
	12. *staff.bin*
	13. *staff_corrupt_last_byte.bin.hex*
	14. *staff.dev.rb1*
	15. *staff.bin.hex*
	16. *staff.dev*
	17. *staff.dev.rb1.hex*

    There is one image file that must be **manually** included in the images
	folder. For first-time firmware qualification e.g. of a new keyboard,
	include a copy of the firmware and name it *'BASE_NAME_older.bin'* where
	BASE_NAME is the keyboard name e.g. *staff_older.bin*.
	For revised firmware qualifications i.e. qualifying new version of
	RO/RW but not the first RO/RW, include an image of the older firmware
	and also name it '*BASE_NAME_older.bin*'. The image
	'*BASE_NAME_older.bin*'is used to test that RW updates can happen with
	the new firmware. In the case of first time firmware, the tests still
	check that RW region is updatable even though the older image is the
	same as the newer image.
	b. Copy the new images folder in your chroot into the DUT from the host
	via ssh (ensure ssh test keys are added to the shell window first):

		scp -r images root@dut.ip.address:/usr/local/bin/hammertests.

## ON DUT

Flash the DUT with a test ChromeOS image. The test image already has the base
tests in the folder **'/usr/local/bin/hammertests’.** You should see the
following tests.

1.  flash_wrong_address.py

2.  rb_protection.py

3.  rb_rw_protected.py

4.  ro_boot_valid_rw.py

5.  ro_stay_ro.py

6.  ro_update_rw.py

7.  rw_no_update_ro.py

8.  transfer_touchpad_works.py

9.  verify_pairing.py

You should also see the following control files

1.  hammertests_control.py

2.  hammertests_control_rb.py

3.  hammertests_control_tp.py

Disable verified boot on DUT so that hammerd does not make it’s own decisions.
The tests disable hammerd but it will be enabled on reboot. We need it to be
disabled persistently by renaming the ‘hammerd’ file to ‘hammerd.out’ so that
it doesn’t execute.
Run the following commands on the DUT console:

    /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 2
    /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 4

**Reboot** the DUT then rename hammerd

    mv /usr/bin/hammerd /usr/bin/hammerd.out

# TEST EXECUTION

To run the tests, simply run each of the **control files** in the DUT from the
/usr/local/bin/hammertests directory. You can do this directly on the DUT or ssh
via the host. E.g.

	./hammertests_control.py

Each control file runs a number of tests, and creates log folders corresponding
to each of the tests outlined above. Some tests have several iterations.

|       Control file   |Tests executed                 |
|----------------------|-------------------------------|
|hammertests_control.py|flash_wrong_address.py
|                      |rb_rw_protected.py
|                      |ro_boot_valid_rw.py
|                      |ro_stay_ro.py
|                      |ro_update_rw.py
|                      |rw_no_update_ro.py
|                      |verify_pairing.py

Image that should be flashed on DUT for hammertests_control.py:
*$BASE_NAME_ec.bin (locked)*
This **locked** image should be supplied by the dev who requests the testing and
attached in the testing request bug.

|       Control file     |Tests executed      |
|------------------------|--------------------|
|hammertests_control_rb.py|rb_protection.py

Image that should be flashed on DUT for hammertests_control_rb.py:
*$BASE_NAME.dev.rb1 (rollback version = 1)*
This image is in the ‘images’ folder which is generated by the script
[gen_test_images.sh](https://chromium.googlesource.com/chromiumos/third_party/autotest/+/HEAD/server/cros/faft/gen_test_images.sh)

|       Control file      |Tests executed             |
|-------------------------|---------------------------|
|hammertests_control_tp.py|transfer_touchpad_works.py

Image that should be flashed on DUT for hammertests_control_tp.py:
*$BASE_NAME_ec.bin (unlocked)*
This **unlocked** image should be supplied by the dev who requests the testing
and attached in the testing request bug.

After running all the tests, **attach the log files** to the request bug.

# Manual Tests

**RO cannot update RW with dev signed image:**

-   Flash the image *staff.dev* generated by ./genimages_staff.sh and verify on
the ec console that RW update fails due to failed signature verification.

**Keyboard:**

Run command `evtest` on DUT and check that each key works.
(https://docs.google.com/document/d/1tA8QknZ37TBrZelneOWtzHtPNGbC5aDDel6PeOV5tZQ/edit#heading=h.vagnagl3dytt).

**Keyboard backlight works**

-   Can control backlight using:

	    echo $VALUE > /sys/class/leds/hammer::kbd_backlight/brightness

-   Or via powerd:

	    backlight_dbus_tool --increase_keyboard

Keyboard backlight not advertised on SKUs where backlight not available

Implemented here: [https://issuetracker.google.com/67722756](https://issuetracker.google.com/67722756).

TODO(drinkcat): give system path to keyboard backlight to distinguish devices
that have backlight support from those that don't

**Trackpad:**

**Touchpad works**

Needed:

-   Base running RW version b under test with trackpad FW v2

Steps:

-   Manual testing

-   Check that touchpad works

-   1 to 5 finger swipes

-   Click using touchpad works

**I2C passthrough interface does not work**

(to be active only when WP is off, for Elan usage)

-   WP on, cannot update the touchpad FW over I2C

	    touchpad_updater -f FW_IMAGE

-   WP off (through servo or physically remove the screw), can update the
touchpad FW over I2C:

	    touchpad_updater -f FW_IMAGE

**Trackpad dimensions are correct**

No errors of this kind in EC console:

[1.430530 reset rv 0 buf=0000]

[1.432640 max=3206/1832 width=124/124 adj=0 dpi=800/800]

*[1.432948 *** TP mismatch!]*

[1.433585 elan_tp_init:0]

See [https://issuetracker.google.com/67982128](https://issuetracker.google.com/67982128) for example.

We only really need to test for version update when we release new TP firmware


text:
# Node and Client Types

There are two types of clients in the Nimiq Network: NodeJS Clients and Browser Clients. Both types use the same isomorphic JavaScript code base and can run any of the three node types: Full, Light and Nano. Some combination of Node/Client types will, in the long run, be more common that others (i.e Browser Clients will mainly be light/nano nodes, and they won’t necessarily participate as miners).

## Client Types

Depending on the platform (Browser/NodeJS) used to run the Client, it will work as a Browser Client or a NodeJS Client. Another main difference between the two of them is that Browser Clients store the Blockchain data in [IndexedDB](https://developers.google.com/web/ilt/pwa/working-with-indexeddb#what_is_indexeddb) (which has a limited capacity of ~50MB) whereas NodeJS Clients rely on [LevelDB](https://github.com/google/leveldb) (with no size constraint). To maintain a common codebase through Client Types we developed [JungleDB](https://github.com/nimiq-network/jungle-db).

### NodeJS Client

NodeJS Clients are meant to run on servers and, thanks to their virtually unlimited storage capacity and publicly routable IP address, act as backbone of the network. They communicate with each other via [WebSockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket), and they act as entry point and signaling server for Browser Clients to establish browser-to-browser WebRTC connections.

Browser APIs are restricted to secure origins. This means that NodeJS Clients need to provide an encrypted connection for Browser Clients to connect to them. This requires a domain and an SSL certificate.

### Browser Client

Browser Clients are built upon browser engines and therefore they are completely installation-free. To connect to the network, they establish a WebSocket connection to at least one NodeJS Client. Once they have established their first connection, they start to establish browser-to-browser connections using the NodeJS Client as signaling server. Browser Clients can also act as signaling server for further browser-to-browser connections.

By using [Babel](https://babeljs.io/) older browser versions are supported, WebRTC functionality is a requirement so only browsers that support WebRTC can connect to the network.

An easy way to understand the different Clients/Nodes Types is to have a look at [the most simple web application on top of the Nimiq Blockchain](https://demo.nimiq.com/).

## Node Types

Distinct Node types are used for different usecases and they differentiate from one another in the amount of data they need to download in order to join and synchronize with the network, which directly affects the time it takes each Node type to establish consensus and be able to process and validate transactions.

### Full Nodes

Nodes of this type download the full blockchain thus requiring more storage. We expect this node type to be used solely with NodeJS Clients although theoretically it could run also in a browser.

### Light Nodes

This type of nodes securely sync to almost full consensus by downloading just about 100 MB. To do that they use a LightChain which is initialized by using NiPoPoWs instead of the full blockchain history, but after initialization, it behaves as a regular full blockchain.

### Nano Nodes

The preferred Node type for the Browser Clients since they require less data to be downloaded (~ 1MB) in order to establish consensus.


text:
---
id: 5477
title: Dirk Nowitzki
date: 2021-04-06T20:01:39+00:00
author: Laima
layout: post
guid: https://ukdataservers.com/dirk-nowitzki/
permalink: /04/06/dirk-nowitzki/
---

* some text
{: toc}

## Who is Dirk Nowitzki

7-foot scoring machine who led the Dallas Mavericks to an NBA Championship in 2011, becoming the first ever European-born player in league history to win the NBA Finals MVP Award.

## Prior to Popularity

After being called a freak because of being so tall, he gave up handball and tennis to focus on basketball.

## Random data

He was named to 11 consecutive All-Star games between 2002 and 2012 and 4 All-NBA First Teams from 2005 to 2009.

## Family & Everyday Life of Dirk Nowitzki

He grew up in Wurzburg with his sister, Silke, and his parents, Jorg and Helen. He married Jessica Olsson in 2012 and they have children named Morris, Malaika and Max.

## People Related With Dirk Nowitzki

He became the golden boy for Mavericks owner Mark Cuban.


text:
---
layout: default
---

# 1994-12-19 - Re: NSA's text search algorithm

## Header Data

From: "Ian Farquhar"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: 7e4993c82ce2aa03ddd63005623aeb1163c2acf2b930563ac4bf4c54a2506ac3

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1994-12-19 23:12:57 UTC

Raw Date: Mon, 19 Dec 94 15:12:57 PST

## Raw message

```
{% raw  %}From: "Ian Farquhar"<EMAIL_ADDRESS>Date: Mon, 19 Dec 94 15:12:57 PST
To<EMAIL_ADDRESS>Subject: Re: NSA's text search algorithm
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

On Dec 20,  2:33am<EMAIL_ADDRESS>wrote:
> Subject: NSA's text search algorithm
> "Ian Farquhar"<EMAIL_ADDRESS>> > I always imagined that the development of [NSA's text scanning]
> > algorithm itself predated email, and started back with cable and
> > telex traffic.
>
> Stat text scanning is ancient, but has probably not been used on the scale
> and efficiency that the NSA would require for net traffic.
>
> > > Earlier this year, the agency began soliciting collaborations from
> > > business to develop commercial applications of their technique.
> >
> > Has anyone got any further information about how this algorithm works?
> > It sounds like Rishab has somewhat better info than was publicly
> If you read NSA's note carefully, you easily rule out
> NLP ("independent of...language") and sophisticated neural nets ("very
fast").

You can rule out both of them on the grounds that the original release
claimed that it was ammendable to hardware implementation.  I speculated
some clever form of CAM plus stats engine.

							Ian.

{% endraw %}
```

## Thread

+ Return to [December 1994](/archive/1994/12)

+ Return to "["Ian Farquhar" <ianf@sydney.sgi.com>](/authors/ian_farquhar_ianf_at_sydney_sgi_com_)"
+ Return to "[rishab@dxm.ernet.in](/authors/rishab_at_dxm_ernet_in)"

+ 1994-12-19 (Mon, 19 Dec 94 13:29:58 PST) - [NSA's text search algorithm](/archive/1994/12/caba46f73f535e160b8fbd3aca60982621d216cfd00edd8e2e891292bb9bdc2f) -<EMAIL_ADDRESS>  + 1994-12-19 (Mon, 19 Dec 94 15:12:57 PST) - Re: NSA's text search algorithm - _"Ian Farquhar"<EMAIL_ADDRESS>


text:
---
layout: page
title: Camping
permalink: /camping
tags: campings
---

## Resources

### Websites
* [Pitch up](https://www.pitchup.com/)
* [Pegs and pitches](https://pegsandpitches.co.uk/)
* [Campsites](https://campsites.co.uk/)
* [Cool camping](https://coolcamping.com/)
* [Nearly wild camping](https://nearlywildcamping.org/)
* [Warm showers](https://www.warmshowers.org/) - Host and be hosted by cyclists.
* [BritStop](https://www.britstops.com/) - One off payment then stay for free at many different places.
* [Rail Hike Camp](https://felt.com/map/Rail-Hike-Camp-kv9BQ3TnpTvud8TM43gTqpB) - Campsites close to train stations.
* [British Mountaineering Club huts](https://www.thebmc.co.uk/organisations/huts)

### Good-looking sites
* [Private camps in Cotswold woodland](https://www.hipcamp.com/en-GB/land/england-gloucestershire-private-camps-in-cotswold-woodland-6p0h8x9p?adults=1&children=0) - Wild-ish spots for groups up to 10 people.

### Articles
* [Best Wild Camping Spots in the UK](https://adventurequeens.co.uk/2017/11/03/best-wild-camping-spots-in-the-uk/)
* [15 of Britain's best almost-wild, off-grid campsites](https://www.theguardian.com/travel/2021/mar/20/15-best-almost-wild-camping-off-grid-campsites-britain-uk)

branch_name: refs/heads/develop


text:
---
layout: page
title: Interactions
permalink: /selenium/lessons/interactions.html
description: "A look at the basic interactions we can do with Selenium WebDriver"
comments: true
signoff: true
---
[Course Home](../course) \| [Code Examples](https://github.com/FriendlyTester/Selenium-WebDriver-Examples/blob/master/java/src/test/java/lessons/D_Interactions.java){:target="_blank"}

Let's recap. We can now open a browser, navigate to our test site, and find elements on the page that we wish to interact with. So what are these interactions, what can we do with WebDriver?

This lesson is going to cover the basics.

### click()
This method is as straight forward as it sounds, it will click on the element.
Note though, WebDriver will only click on elements that are visible, and there is some rather complicated logic to determine if an element is visible. There is a [talk](https://www.youtube.com/watch?v=hTa1KI6fQpg) on this very topic by David Burns one of the selenium contributors.

### getText()
This method instructs WebDriver to return the text contained within an element.
```html
<div>
<p>I'm Richard</p>
<span>I created this course</span>
</div>
```

WebDriver will return all the text between the opening tag and the closing tag. So if we took the HTML above and the following code
```java
Driver.findElement(By.tagName("p")).getText();
```
it would return 'I'm Richard'. As that is all the text between \<p> and \</p>.
Now if we asked WebDriver to return the text contained in the \<div>, we'd get the contents of the \<p> tag and the \<span>.
So we'd get
```text
I'm Richard
I created this course
```

### sendKeys()
The most common usage for SendKeys() is to populate text fields. We can instruct WebDriver to find an input and populate it with our required text.
```java
Driver.findElement(By.id("firstname")).sendKeys("richard");
```
This would result in WebDriver looking for an element with the ID of 'firstname' and if it finds it, it'll try and type 'richard' into it.

We can also use SendKeys() to send actually key presses. For example, if your site does some behaviour after populating some text in a field and pressing enter, we can simulate that with keys.
```java
Driver.findElement(By.id("firstname")).sendKeys(Keys.ENTER);
```

### getAttribute()
This is a fantastic method, even more so in recent years with the additional attributes introduced with HTML5.
This method allows you to ask WebDriver to return you the value of any attribute on an element.

The most common usage is probably 'value'. On an input field, this will return you the text within the input.
Other common usages are to read the placeholder text to validate a form, get the classes, ID, names of elements. Also as mentioned, to read data attributes which are becoming more common.
```java
Driver.findElement(By.id("firstname")).getAttribute("value");
```
This would look for an element with the id 'firstname', and return the value in the attribute input. Important to note that getText() won't have the same behaviour as this. getText() won't return you the value of an input field. Also, if you investigate this, you'll very rarely see 'value' as an attribute when inspecting some HTML, but trust me, it works.

### Driver Interactions
We also have a few ways in which we can interact with the Driver, or in other terms, the browser itself.
Those are getTitle() and getCurrentUrl().

getTitle() - Will return you the text in the tab.
getCurrentUrl() - Does what you're thinking it does, it returns you the URL in the address bar.

### [Next Lesson ➔](../lessons/screenshots)


text:
# Alert message and Toast Message

This will be useful to show alert view or some kind of alert information to the user. It may be a success message or failure message
then you can also show simple toast message to the user.

# Screen shots

# Installation

Just drag and drop the "AlertView.h" and "AlertView.m" file from source files into your project,
and make sure you check the "Copy items into destination group's folder" box

###### - Then import AlertView.h and set the cradViewDelegate wherever you need it.

```objective-c
#import "AlertView.h"

@interface ViewController ()<alertViewDelegate>
```

# Usage

Creation is very simple just send the message to show in the alert with Yaxis where should show the message and also send
whether its success message or failure message as BOOL. Don forget to send position type before that create object for the
class and set delegate.

position 1 -> Top
position 2 -> Bottom

Code for showing alert message
```objective-c

AlertView *alert = [[AlertView alloc]init];
alert.delegate=self;

- (IBAction)showSuccessAlertTop:(id)sender
{
    [alert showAlert:self.view alertString:@"Welcome to the wonderful world. With advanced of activating account and new login widgets, you will definitely have a great experience of using"
           size:64 type:YES position:1];
}

- (IBAction)showFailureAlertTop:(id)sender
{
  [alert showAlert:self.view alertString:@"uhh! oh Looks like server is down. Come back later"
         size:64 type:NO position:1];
}

- (IBAction)showSuccessAlertBottom:(id)sender
{
     [alert showAlert:self.view alertString:@"Welcome to the wonderful world. With advanced of activating account and new login widgets, you will definitely have a great experience of using"
            size:64 type:YES position:2];
}

- (IBAction)showFailureAlertBottom:(id)sender
{
    [alert showAlert:self.view alertString:@"uhh! oh Looks like server is down. Come back later"
           size:64 type:NO position:2];
}
```
Code for showing toast message and for that send only message which should be shown.

```objective-c
- (IBAction)showToast:(id)sender
{
  [alert makeToast:@"Welcome to the wonderful world. With advanced of activating account and new login widgets, you will definitely have a great experience of using"];
}
```

Note : This is my first try so please feel free to comment or even you can tell me if i have to improve anything
or even small mistakes in the coding. Thanks

# Get in touch
If you want to contact me mail at<EMAIL_ADDRESS>or
Just tweet me : [@iam_vijay7](https://twitter.com/iam_vijay7)

# License

 The MIT License (MIT)

 Copyright (c) 2015 Vijay Subramaniyam

 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.


text:
# KExpress Standard Template

This template is created for kexpress v1.0.x using sequelize as the ORM library.
If you want to create a new project from this template, please execute following command:

    kexpress-cli create kinuxroot/kexpress-template-multi-sequelize <projectName>
    cd <projectName>
    npm install

Then you need to create your interfaces in init directory.
There are some example apps in `init` directory.

    npm run init

Then please modify the store.js in config directory and run tools to initialize database.

    vim config/dev/store.js
    npm run tools


text:
# G54LDO coursework
* Grade: 93 / 100
* Comments:
>## Correct Spreadsheet Model
>Developed a correct linear model for this problem. (7.5)
>The solver parameter settings are set correctly. (7.5)
>Produced the correct solution based on the designed model. (7.5)
>As different requirements are considered in the problem, separate models for each objective were designed and both models are reasonably well connected. There is no particular innovative aspects in the spreadsheet modelling. (3.5)
>### 26 out of 30
>## Quality of Spreadsheet Model
>The data, decision variables, objective function and constraints are clearly identified. The solution is well presented. (5)
>The spreadsheet layout and formatting are clear and well presented. (5)
>It used random points to represent each place and then automatically generate a route map from the solution. (4)
>It used three functions to detect the out path from a place and then used the VLOOKUP function to determine the corresponding place point. (4)
>### 18 out of 20
>## Correct and Clear LP-Solve Model
>The linear model and the produced solution are correct. (7.5)
>Excellent descriptive comments are included to clarify each part of the model. (7.5)
>The algebraic model corresponds fully to the spreadsheet model. (7.5)
>Two scripts from the MathProg were generated. One automatically eliminates the subtours (based on the findings from the spreadsheet model) and in the other one the constraints are added manually. Both scripts are solvable in polynomial time and produce the same output. Excellent work, well done. (7.5)
>### 30 out of 30
>## Quality of Demonstration Video
>Good graphical and sound quality. Well-structured presentation and within the maximum length. (5)
>Good explanation of both models in Excel and LP-Solve. Clearly explains correspondence between models and solutions. A minor issue is that it missed to explain the solver settings. (4)
>Good explanation of the own understanding accomplished for the design and solution of the model. (5)
>It fully explained the specific features included in the spreadsheet model and its usability for detecting subtours and then execute their elimination automatically. (5)
>### 19 out of 20


text:
# CS188Project3
An Android app that provides a list of things to do for patients that need therapy. Software Engineering - Project 3 - Fall 2016

## Disclaimer
The icons were retrieved from [Flat Icons](http://www.flaticon.com/)

## Using the Source Code
1. Clone the project

  ```
    $ git clone https://github.com/maheshgaya/CS188Project3.git
    $ cd CS188Project3/
  ```

2. This project uses Firebase Authentication For Google and Email Sign-in. You need to get the configuration file from
the [Google Firebase Console](https://console.firebase.google.com).

  **Steps:**

  1. Click on "Create a new project" in the Firebase Console to create a new project
  2. Give it a useful name, choose your region, and click on "Create Project"
  3. Click on "Add Firebase to your Android App"
  4. The package name should be "com.example.kelly.mmelk" (without quotes). You can also give it a nickname
  5. Now on your computer terminal, generate a SHA1 key with the following statement :

      ```
      $ keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore -list -v
      ```

      **(Note: you can leave the password blank)**

     Copy the SHA1 and put that into the "Debug signing certificate SHA-1" field.
  6. Then click on "Add App". Make sure you download the "google-services.json"
  7. Add the "google-services.json" to the "app" directory
  8. Now, go back to the Firebase console and select "Develop" -> "Authentication" on the left navigation menu
  9. Go to "Sign-in method" and enable "Google" and "Email/Password"

3. Import the project in Android Studio

  ```
    File -> New -> Import Project -> (Choose CS188Project3/MMELK/)
  ```
4. Run the app on an Android phone. **KNOWN ISSUE:** Emulators will not work as they currently don't support the latest version of Firebase API

## Contributing to the Source Code
1. Fork this repository by clicking on the Fork button on the top right corner
2. [Clone](https://help.github.com/articles/cloning-a-repository/) your own repository on your desktop
3. Commit your changes to your own repository
4. Once you are ready for your patch, create a [pull request](https://yangsu.github.io/pull-request-tutorial/)

## License

  Copyright 2016 CS188 Project 3 Group 1

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: maheshgaya/TherapyApp

repo_name: maheshgaya/TherapyApp


text:
9.0.22 / 2017-09-27
===================

  * fix: query string recording where value is an array ([#917](https://github.com/node-nock/nock/issues/917))
  * docs(README): link to license file, link to contributors, update Copyright years
  * chore(LICENSE): MIT
  * chore(CHANGELOG): v9.0.21

9.0.21 / 2017-09-25
===================

  * 9.0.21
  * fix: compare falsy header values & numbers correctly
  * test: match number header values
  * multiple interceptors override headers from unrelated requests
  * Add an error code to NetConnectNotAllowedError
    This is in line with nodejs error codes. I chose `ENETUNREACH` because it clearly defines the reason why the http request failed.
    https://nodejs.org/api/all.html#errors_error_code
  * chore(CHANGELOG): v9.0.20

9.0.20 / 2017-09-24
===================

  * 9.0.20
  * fix: match headers with falsy values (again)
    follow up for https://github.com/node-nock/nock/pull/973/files#r140647611
  * Switch from jshint to eslint ([#885](https://github.com/node-nock/nock/issues/885))
    - Remove pre-commit hooks
    - Fix a broken unit test (bug caught by lint)
    - Minor lint + style cleanup
    Closes [#868](https://github.com/node-nock/nock/issues/868)
  * changed Real HTTP request documentation to be more readable
  * docs(CHANGELOG): 9.0.19

9.0.19 / 2017-09-22
===================

  * 9.0.19
  * Improve Nock Back documentation
  * Fix file permissions of intercept test
  * Fix allowUnmocked when last interceptor was removed.
  * Do not abort a an already aborted request, do not emit an error twice
    Fixes [#882](https://github.com/node-nock/nock/issues/882)
    When a request is aborted, "nock" emits an "abort"-error.
    If the client reacts on that error by aborting the request (this is what
    "popsicle" does), the code will end in an endless loop.
    This commit makes that the the "abort"-code is only executed, if the
    request has not already been aborted.
  * fix broken link: allow-unmocked-requests-on-a-mocked-hostname
  * fix: Specified request body not properly enforced ([#921](https://github.com/node-nock/nock/issues/921))
  * Minor change in example code `scope(` => `var scope = nock(`
  * nockBack.setMode: Improve error message
  * chore(CHANGELOG): v9.0.18

9.0.18 / 2017-09-20
===================

  * 9.0.18
  * fix(recorder): don’t JSON.stringify output if output_objects is not enabled
    This is a follow up fix for https://github.com/node-nock/nock/pull/959
  * feat: promisify nock back ([#798](https://github.com/node-nock/nock/issues/798))
  * chore(CHANGELOG) v9.0.17

9.0.17 / 2017-09-19
===================

  * 9.0.17
  * 835 support regex for both host and port with allowUnmocked
  * 835-added-fail-test-case
  * docs(README) - fix info about mocking ([#971](https://github.com/node-nock/nock/issues/971))
  * Document replyWithFile using Content-Type header
  * fix readme typo
    add missing closing paren
  * fix grammar
    change `the response event will occur immediately, but the IncomingMessage not it's end event until after the delay` -> `the response event will occur immediately, but the IncomingMessage will not emit it's end event until after the delay`
  * Improve Match Logging
    Currently, matching logging does not include the method or path of the request.  I have added these to make debugging non-matches easier.
  * Update README.md
    please review for accuracy. I actually don't know how it behaves but this section was very confusing to read.
  * fix: printing recorded requests with output_objects resulted in output of [Object Object]
  * chore(CHANGELOG): 9.0.16

9.0.16 / 2017-09-18
===================

  * 9.0.16
  * fix: match headers with falsy values
  * test: match headers with falsy values
  * chore(travis): don’t build twice for PRs and retry npm install
  * chore(travis): don’t test in node v7
    It’s no longer supported
  * chore: remove console logs in tests
  * docs(CHANGELOG): update for 9.0.15

9.0.15 / 2017-09-18
===================

  * 9.0.15
  * fix: `nock.define()` respects badheaders option
  * test: `nock.define()` ignores badheaders option
  * docs(README): document `nock.recorder.clear()`

9.0.14 / 2017-07-17
===================

  * Fixes for Node 8
  * Merge pull request [#948](https://github.com/node-nock/nock/issues/948) from martinkuba/master
    Fix for [#947](https://github.com/node-nock/nock/issues/947)
  * www.amazon.com does not return any data
  * Merge pull request [#929](https://github.com/node-nock/nock/issues/929) from martinkuba/node8
    Updates to unblock Node 8
  * Merge pull request [#942](https://github.com/node-nock/nock/issues/942) from michaelnisi/browserify
    Skip browserify test because zombie fails @7.10
  * Skip browserify test because zombie fails @7.10
  * wrap http.get on Node 8 only
  * workaround for socket hang up
  * fix recorder when calling res.end(data)
  * use req.setHeader()
  * override http.get
  * added Node 8 to Travis
  * Merge pull request [#667](https://github.com/node-nock/nock/issues/667) from ksmith97/master
    Updated debug namespace to match file.

9.0.13 / 2017-04-10
===================

  * 9.0.13: Revert [#863](https://github.com/node-nock/nock/issues/863)
  * Merge pull request [#880](https://github.com/node-nock/nock/issues/880) from node-nock/revert-v9.0.12-issue-863
    Revert "Merge branch 'fasterize-fix_match_body'"
  * Revert "Merge branch 'fasterize-fix_match_body'"
    This reverts commit 8333e3aef1e79dc2ed96dca819124f4a18f1af4d, reversing
    changes made to 30881e2a72dbb950e771f912c5f9ddbcb91c0acd.

9.0.12 / 2017-04-10
===================

  * 9.0.12: Use key length in array/object comparison
  * Merge branch 'fasterize-fix_match_body'
    * fasterize-fix_match_body:
    [[#863](https://github.com/node-nock/nock/issues/863)] Fix matchBody for object and array comparison
  * Merge branch 'fix_match_body' of https://github.com/fasterize/nock into fasterize-fix_match_body
    * 'fix_match_body' of https://github.com/fasterize/nock:
    [[#863](https://github.com/node-nock/nock/issues/863)] Fix matchBody for object and array comparison
  * [[#863](https://github.com/node-nock/nock/issues/863)] Fix matchBody for object and array comparison

9.0.11 / 2017-03-29
===================

  * 9.0.11: Fixes for [#856](https://github.com/node-nock/nock/issues/856) (pending mocks) and [#425](https://github.com/node-nock/nock/issues/425) (multipart forms)
  * Merge pull request [#834](https://github.com/node-nock/nock/issues/834) from delijati/master
    PR [#834](https://github.com/node-nock/nock/issues/834): Don't remove newlines from multipart form reqests
  * Merge pull request [#857](https://github.com/node-nock/nock/issues/857) from disrupticons/fixing-issue-856
    Fix [#856](https://github.com/node-nock/nock/issues/856): nock.cleanAll() should remove pending mocks
  * fixing test description

9.0.10 / 2017-03-28
===================

  * 9.0.10: Versioned tested and better .npmignore
  * adding test for multipart match body
  * Merge pull request [#858](https://github.com/node-nock/nock/issues/858) from fabiosantoscode/patch-1
    Add some big folders to .npmignore
  * Add some big folders to .npmignore
  * Remove pending mocks from scopes on nock.cleanAll()
  * Merge pull request [#842](https://github.com/node-nock/nock/issues/842) from node-nock/feature-832-versioned-tests
    Feature [#832](https://github.com/node-nock/nock/issues/832): Versioned tests
  * [#832](https://github.com/node-nock/nock/issues/832) Add glob as dev dep
  * [#832](https://github.com/node-nock/nock/issues/832) Add integration tests to travis
  * [#832](https://github.com/node-nock/nock/issues/832) Cleanup sub dep install script
  * [#832](https://github.com/node-nock/nock/issues/832) Add tests for request & popsicle
  * [#832](https://github.com/node-nock/nock/issues/832) Remove socketTimeout test
  * [#832](https://github.com/node-nock/nock/issues/832) Run got tests using common test runner
  * 832 Versioned tests for got module
  * 832 Add sub dep install from NR
  * Changelog v9.0.9

9.0.9 / 2017-02-28
==================

  * 9.0.9: Revert PR [#802](https://github.com/node-nock/nock/issues/802)
  * Merge pull request [#840](https://github.com/node-nock/nock/issues/840) from node-nock/revert-802-fix-754
    Revert "Fix request timeout no working"
  * Revert "Fix request timeout no working"
  * Changelog v9.0.8

9.0.8 / 2017-02-27
==================

  * 9.0.8: Fix for [#754](https://github.com/node-nock/nock/issues/754)
  * Merge pull request [#836](https://github.com/node-nock/nock/issues/836) from node-nock/greenkeeper-superagent-3.5.0
    Update superagent to version 3.5.0 🚀
  * Merge pull request [#802](https://github.com/node-nock/nock/issues/802) from aleung/fix-754
    Fix request timeout no working

9.0.7 / 2017-02-23
==================

  * Changelog
  * 9.0.7: Fix for [#610](https://github.com/node-nock/nock/issues/610)
  * Merge pull request [#829](https://github.com/node-nock/nock/issues/829) from yodeyer/fixQs
    Fix interceptor if query have no query strings


text:
---
aliases:
- /2007/08/07/history-of-the-left-session-ii-1917
title: History of the Left
subtitle: 'Session II: 1917'
date: 2007-08-07
series:

 - History of the Left
tags:
- '1917'
media-type: ["audio"]
series:
- Teach-in
- History of the Left
speakers:
- Chris Cutrone
---

_A lecture by Platypus Affiliated Society member [Chris Cutrone](/speakers/chris-cutrone) on the history of the Left that led up to the 1917 Russian Revolution, given on August 12, 2007. Part of the History of the Left lecture series held in the summer of 2007._

## Audio Recording

{{% audio src="https://archive.org/download/HistoryOfTheLeft1917/HistoryOfTheLeft-UpTo1917.mp3" %}}


text:
# Bet-Calculator
A Bet calculator based on decimal european odds

This calculator class will only work with sports when there is a draw match possible. It was made for you bet an
amount of money in one house, and other amount in other house. And either result is, you will have return of your
investment with profit. But, if there is a result you dont expect, you will lose everything.

## Why it doesn't work with sports when there is no draw?
Because the decimal odds of this sport was made to not profit the player that work this way, you can look for,
but you will not find odds that fits in this calculation.

## For Whom it was designated?
For people who wants to profit in more security way, altough they will have more profit if bet in the exact result

repository: felipeAraujo/Bet-Calculator

repo_name: felipeAraujo/Bet-Calculator


text:
---
external help file: HPESimpliVity-help.xml
Module Name: HPESimpliVity
online version: https://github.com/atkinsroy/HPESimpliVity/blob/master/Docs/Get-SvtPolicy.md
schema: 2.0.0
---

# Get-SvtPolicy

## SYNOPSIS
Display HPE SimpliVity backup policy rule information

## SYNTAX

```
Get-SvtPolicy [[-PolicyName] <String[]>] [[-RuleNumber] <Int32>] [-Raw] [<CommonParameters>]
```

## DESCRIPTION
Shows the rules of backup policies from the SimpliVity Federation

## EXAMPLES

### EXAMPLE 1
```
Get-SvtPolicy
```

Shows all policy rules for all backup policies

### EXAMPLE 2
```
Get-SvtPolicy -PolicyName Silver, Gold
```

Shows the rules from the specified backup policies

### EXAMPLE 3
```
Get-SvtPolicy | Where RetentionDay -eq 7
```

Show all policy rules that have a 7 day retention

### EXAMPLE 4
```
Get-SvtPolicy -PolicyName Gold -Raw
```

Display the specified policy in raw JSON from the Simplivity API.

## PARAMETERS

### -PolicyName
Display information about the specified backup policy only

```yaml
Type: String[]
Parameter Sets: (All)
Aliases: Name

Required: False
Position: 1
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -RuleNumber
If a backup policy has multiple rules, more than one object is displayed.
Specify the rule number
to display just that rule.
This is useful when a rule needs to be edited or deleted.

```yaml
Type: Int32
Parameter Sets: (All)
Aliases:

Required: False
Position: 2
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### -Raw
Display output as JSON, rather than a formatted PowerShell object.
This parameter might useful in troubleshooting
and maintaining the module.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### System.String
## OUTPUTS

### HPE.SimpliVity.Policy
## NOTES
Author: Roy Atkins, HPE Services

## RELATED LINKS

[https://github.com/atkinsroy/HPESimpliVity/blob/master/Docs/Get-SvtPolicy.md](https://github.com/atkinsroy/HPESimpliVity/blob/master/Docs/Get-SvtPolicy.md)

repository: atkinsroy/HPESimpliVity

gha_language: PowerShell

repo_name: atkinsroy/HPESimpliVity


text:
# check-mk_signal-cli
Send check_mk notifications via signal-cli (requires https://github.com/AsamK/signal-cli)

Store script at /omd/sites/\<YOUR-SITE\>/share/check_mk/notifications

Adjust \<SIGNAL-CLI-PATH\>, \<USER-SENDER\>, and \<USER-RECEIVER\>

Integrate at WATO / Notifications, select Notification Method "Send via Signal"

Messages will look like:
\<HOSTNAME\>: \<NEW-HOSTSTATE\> after \<OLD-HOSTSTATE\> (\<OLD-STATE-DURATION\>) at \<LONG-DATE-TIME\>

signal.py is an alternative implementation that uses Python instead of bash and requires that signal-cli is available on the system DBus
Rename to "signal" and use instead of the original signal (bash) file


text:
# Breakbeam and RFID proof of concept

This was the first Proof of concept I worked on when thinking out how to build this project.

You can see a video of it [here on my vimeo channel](https://vimeo.com/331064511)

![fusion demo 1](readme_attachments/fusion-demo1.gif)
![fusion demo 2](readme_attachments/fusion-demo2.gif)

![poc](readme_attachments/front.jpg)
![poc](readme_attachments/back.jpg)

After talking through with Terri as far as what we wanted to build and how we thought it should work and look it was clear that the first things that we needed to prove out were:

-   Can we get the break beam sensors and RFID sensor to work together?
-   Will the timing work?
-   Can we physically build out, wire, and program a fork that represents the lanes the machine will use and the funnel for the rfid sensor?

Once I proved this out I moved on to designing the prototype for the game.

repository: chris-schmitz/pegasus

repo_name: chris-schmitz/pegasus


text:
## Mixed models in genetics

h2r

* [paper](https://www.researchgate.net/publication/236253076_Bayesian_inference_of_mixed_models_in_quantitative_genetics_of_crop_species) for pedigrees (sib-pairs) + JAGS code
          * Code in a better format from the thesis http://alexandria.cpd.ufv.br:8000/teses/genetica%20e%20melhoramento/2012/247890f.pdf
* JAGS applied to twin studies http://scheibehenne.de/Scheibehenne.et.al.Appetite2014.onlineSupplement.pdf
      * similar example https://www.utwente.nl/bms/omd/Medewerkers/vandenbergfiles/schwabevandenbergBG2013.pdf
* Animan model in Stan https://groups.google.com/forum/#!topic/stan-users/2eZ11QG_pbU

Fine mapping

* http://cc.oulu.fi/~misillan/Assoc_Map_WinBUGS_1.txt from http://cc.oulu.fi/~misillan/

## Mixed models

General notes

* By Ben Bolker: https://www.nceas.ucsb.edu/system/files/mixed.pdf

Scripts

* Correlation between RE https://github.com/mclark--/Miscellaneous-R-Code/blob/master/ModelFitting/Bayesian/rstan_MixedModelSleepstudy_withREcorrelation.R

Tutorials

* Fitting linear mixed models using JAGS and Stan: A tutorial http://www.ling.uni-potsdam.de/~vasishth/JAGSStanTutorial/SorensenVasishthMay12014.pdf
    * Model under study: `RTi = beta0 + beta1 * conditioni + ei`
* Workshop "Practical Data Analysis with JAGS using R": http://bendixcarstensen.com/Bayes/Cph-2012/pracs.pdf

Discussions

* JAGS model for `lmer(y ~ a + x + a:x + (1 + a | id))`: http://stats.stackexchange.com/a/28655/8598

Blog posts

* glmer2stan: https://hlplab.wordpress.com/2013/12/13/going-full-bayesian-with-mixed-effects-regression-models/
* http://people.ucsc.edu/~abrsvn/general-random-effects-jags.html
      * Lecture: http://www.unc.edu/courses/2010fall/ecol/563/001/docs/lectures/lecture28.htm

repository: variani/study

repo_name: variani/study