text:
---
uid: crmscript_ref_NSUserAgent_GetCredentialTypesForUserType
title: NSCredentialType[] GetCredentialTypesForUserType(Integer userType)
intellisense: NSUserAgent.GetCredentialTypesForUserType
keywords: NSUserAgent, GetCredentialTypesForUserType
so.topic: reference
---

# NSCredentialType[] GetCredentialTypesForUserType(Integer userType)

Get available credential types that can be used for the specified user type.

**Parameters:**
 - **userType** The user type to retrieve credential types for
     - Enum: 0 = Unknown
     - Enum: 1 = InternalAssociate
     - Enum: 2 = ResourceAssociate
     - Enum: 3 = ExternalAssociate
     - Enum: 4 = AnonymousAssociate
     - Enum: 5 = SystemAssociate

**Returns:** NSCredentialType[]

```crmscript
NSUserAgent agent;
Integer userType;
NSCredentialType[] res = agent.GetCredentialTypesForUserType(userType);
```

repository: stianol/crmscript

repo_name: stianol/crmscript


text:
# tippy.css
## Pure CSS tooltips.
Create tooltips with ease, without JavaScript.

### How to use

First, include the stylesheet at the top of your page.

```html
<link rel="stylesheet" href="path/to/tippy.min.css">
```

For the simplest case, add the property `data-tippy` to an element with your tooltip text as the value. You can do this to links, spans, divs, and even buttons. (Well, in most browsers. We'll get to that.)

```html
<button data-tippy="I am a tooltip!">...</button>
<a href="http://www.google.com" data-tippy="Link to Google">...</a>
<span data-tippy="Hello world">...</span>
<div data-tippy="Full width element">...</div>
```

### Tooltip positions

By default, tooltips appear below the element to which they belong. By including the `data-tippy-pos` property, you can control how they appear. There are four potential values: "up", "down", "left", and "right".

```html
<button data-tippy="I am a tooltip!" data-tippy-pos="up">
<button data-tippy="I am a tooltip!" data-tippy-pos="down">
<button data-tippy="I am a tooltip!" data-tippy-pos="left">
<button data-tippy="I am a tooltip!" data-tippy-pos="right">
```

### Special animations

The tooltips don't have much by way of default animation. They fade in, but that's it. There are two optional animation types, however. Include the `data-tippy-animate` property and one of two values, "slide" or "bubble".

### Browser support

Tippy.css has been tested in Internet Explorer 9-11 and the latest versions of Chrome, Firefox, Edge (yay Windows 10 Insider program), Vivaldi (my browser of choice), and Safari.

### Known issues

* Tooltips are created by using the `::before` and `::after` pseudo-elements, so tooltips on any element that doesn't have those, like images or input fields, won't appear.

 You can work around this by wrapping the element in a span or a div, though, like this:

 ```html
 <div data-tippy="Super awesome picture">
    <img src="cats-rule.jpg">
 </div>
```

* If your stylesheet is using pseudo-elements on certain elements, you will run into conflicts. This will result in weird behavior or non-working tooltips.

* HTML inside tooltips will not work, so don't even try.

* Tooltips don't work on `<button>` elements in Internet Explorer. I don't know why. :/

* The bubble animation uses the `clip-path` property, and (as of this writing) only works in Chrome, Vivaldi, and Safari.

* Tooltips on links that underline on hover get underlined in Edge.

* Tooltips on buttons get included in the focus outline.
  You can override this behavior with this code:
  ```css
  button[data-tippy]:focus {
    outline: none;
  }
  ```
  I won't include this code in the stylesheet, however. Removing the button's outline will remove its accessibility, so think carefully before you implement this.
  Learn more at [www.outlinenone.com](http://www.outlinenone.com).

### License

Tippy.css has been released under the [MIT license](LICENSE).

license: MIT

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
# hack-a-thing-1-fockus
# The team: Manzi Bryan and Abubakar Kasule

# Acknowledgements

Boilerplate from: https://www.npmjs.com/package/electron-react-webpack-boilerplate

# Short description of what you attempted to build
We wanted to build a pdf reader for people who were in a time crunch. The PDF is ultimately supposed to make an annoying sound/flashing lights when the user leaves the application and a future iteration should alert the user's 'buddy' who would then presumably pressure their friend to get back to work. We wanted to build the pdf reader using Electron which is based on react but allows you to build Desktop Applications.

# Who did what (if you worked with someone else)
Manzi Bryan: Worked on designing the UI of the application, built the front end of the landing page and set up the system for sending the path of the PDFs chosen by the user (or the URL to the PDF reader).

Abubakar Kasule: Worked on the UI/UX of the application as well. He also built the PDF reader and handled the routing from the front end to the actual PDF reader.

# What you learned
We learned how to work with Electron, how to interact with computer file systems which is surprisingly difficult and also learned

# What didn’t work
We weren't able to figure out how to make a sound/flashing lights when the user leaves the screen and because we prioritized that over the "buddy" system, we haven't implemented the buddy system either.


text:
---
id: tracks
title: Configuring tracks
---

All tracks can contain:

- `trackId` - internal track ID, must be unique
- `name` - displayed track name
- `assemblyNames` - an array of assembly names a track is associated with, often
  just a single assemblyName
- `category` - (optional) array of categories to display in a hierarchical track
  selector

Example `config.json` containing a track config for a BigBed file:

```json
{
  "assemblies": [
    ...the hg19 assembly...
  ],
  "tracks": [
    {
      "type": "FeatureTrack",
      "trackId": "repeats_hg19",
      "name": "Repeats",
      "assemblyNames": ["hg19"],
      "category": ["Annotation"],
      "adapter": {
        "type": "BigBedAdapter",
        "bigBedLocation": {
          "uri": "https://jbrowse.org/genomes/hg19/repeats.bb",
        }
      }
    }
  ]
}
```

repository: GMOD/jbrowse-components

branch_name: refs/heads/main

gha_language: TypeScript

repo_name: GMOD/jbrowse-components


text:
<!--
 This work is licensed under a Creative Commons Attribution 3.0
 Unported License.

 http://creativecommons.org/licenses/by/3.0/legalcode
-->

# prototype-a-physical-network-api

## Status

implementable

## Table of Contents

<!--ts-->
   * [Title](#title)
      * [Status](#status)
      * [Table of Contents](#table-of-contents)
      * [Summary](#summary)
      * [Motivation](#motivation)
         * [Goals](#goals)
         * [Non-Goals](#non-goals)
      * [Proposal](#proposal)
         * [User Stories [optional]](#user-stories-optional)
            * [Story 1](#story-1)
            * [Story 2](#story-2)
         * [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
         * [Risks and Mitigations](#risks-and-mitigations)
      * [Design Details](#design-details)
         * [Work Items](#work-items)
         * [Dependencies](#dependencies)
         * [Test Plan](#test-plan)
         * [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
         * [Version Skew Strategy](#version-skew-strategy)
      * [Drawbacks [optional]](#drawbacks-optional)
      * [Alternatives [optional]](#alternatives-optional)
      * [References](#references)

<!-- Added by: stack, at: 2019-02-15T11:41-05:00 -->

<!--te-->

## Summary

The Metal³ project is currently centered around an API for managing physical
hosts.  This proposal is to explore expanding the scope to also include an API
for managing physical network devices.  This exploration would be done by
starting with a prototype that can configure some aspects of a top-of-rack
(ToR) switch.

## Motivation

Metal³ follows the paradigm of Kubernetes Native Infrastructure (KNI), which is
an approach to use Kubernetes to manage underlying infrastructure.  Managing
the configuration of some physical network devices is closely related to
managing physical hosts.

As bare metal hosts are provisioned or later repurposed, there may be
corresponding physical network changes that must be made, such as reconfiguring
a ToR switch port.  If the provisioning of the physical host is managed through
a Kubernetes API, it would be convenient to be able to reconfigure related
network devices using a similar API.

### Goals

Produce a `physical-network-api` prototype, which includes the following:

* A `Switch` CRD with one or more fields that corresponding to switch
  configuration, ideally with a vendor neutral definition.  Note that the CRD
  definition may be simplified for PoC purposes and the data model would likely
  be revisited in more detail post-PoC.
* A demonstration of using this prototype API to configure a switch
* A documented retrospective that includes lessons learned and proposed next
  steps
* Evaluate the re-use of a single existing network device configuration
  technology

### Non-Goals

Out of scope:

* Testing with anything more than a single switch model
* Prototyping an API for anything beyond a Switch
* Full configuration possibilities of a switch
* Evaluation of all potential technologies that could be re-used for network
  device configuration.  Future prototypes can be done to consider other
  alternatives if desired.

These items may become in scope after a prototype is reviewed and next steps
discussed.

## Proposal

The prototype should explore the re-use of [Ansible
Networking](https://docs.ansible.com/ansible/latest/network/index.html) to
perform device configuration.  Ansible includes modules for managing the
configuration of many different network devices.  Creation of CRDs in this new
API can use modeling from Ansible as inspiration, particularly if there is any
vendor neutral modeling already done there.

Another project that could be used as inspiration is the [Ansible Networking
Neutron ML2 Driver](https://networking-ansible.readthedocs.io/en/latest/) which
created a Python API to abstract generic switch configuration on top of Anisble
networking modules.  Note that the relevant part of the driver was split out
into the
[ansible-network/network-runner](https://github.com/ansible-network/network-runner)
repository.

The [operator-sdk](https://github.com/operator-framework/operator-sdk) project
includes some support for Ansible operators.  One approach could be to use an
ansible operator to run playbooks that use the roles from the [network-runner
repository](https://github.com/ansible-network/network-runner). Another
approach could be to build a new API (gRPC, for example) around
`network-runner`, and have a controller written in golang call that. Another
relevant Python tool to consider is
[kopf](https://github.com/zalando-incubator/kopf).  Other approaches to Ansible
networking re-use can be considered and discussed in the read-out from the
prototype.

### User Stories [optional]

#### Story 1

As a consumer of Metal³, when creating or updating a `BareMetalHost` resource,
I would also like to create or update a `Switch` resource to re-configure a
switch port that is attached to one of the network interfaces on the
`BareMetalHost`.

### Implementation Details/Notes/Constraints [optional]

None

### Risks and Mitigations

None

## Design Details

* To be determined during prototype implementation

### Work Items

* Define enough of a `Switch` CRD for a prototype
* Explore approaches to driving ansible from a golang based Kubernetes
  controller
* Implement `Switch` controller which uses Ansible to drive reconciliation

### Dependencies

None

### Test Plan

TBD

It would be desirable to have a way to test this in `metal3-dev-env` for simple
development and testing.  This would also be needed for CI purposes in the
future if this project is pursued.

As part of wrapping up the prototype, it is desirable to demonstrate the
resulting code against a real switch.

### Upgrade / Downgrade Strategy

None for the prototype

### Version Skew Strategy

None for the prototype

## Drawbacks [optional]

None

## Alternatives [optional]

There are certainly alternative prototypes that could be developed, but the
proposal is to start with the one described in this document.  Summaries of
possible future prototypes can be added to this section.

## References

* https://docs.ansible.com/ansible/latest/network/index.html
* https://networking-ansible.readthedocs.io/en/latest/
* https://github.com/operator-framework/operator-sdk
* https://github.com/zalando-incubator/kopf


text:
# Change Log
This project adheres to [Semantic Versioning](http://semver.org/).

This CHANGELOG follows the format listed at [Keep A Changelog](http://keepachangelog.com/)

## [Unreleased]
### [1.1.0] - 2017-08-09
### Removed
- removed `mysql` gem dep as we have `mysql2` and `mysql` does not work on ruby 2.4 and has been abandoned. (@majormoses)

### Changed
- check-percona-cluster-size.rb: converted to use `mysql2` gem (@majormoses)
- check-wsrep-ready.rb: converted to use `mysql2` gem (@majormoses)

### Added
- ruby 2.4 testing to travis (@majormoses)
- slack badge (@majormoses)

## [1.0.0] - 2016-09-25
### Added
- Ruby 2.3.0 support
- Add `check-wsrep-ready` to check the ready status of a cluster (@aberrios85)

### Removed
- Ruby 1.9.3 support

### Changed
- Update to rubocop 0.40 and cleanup

## [0.0.2] - 2015-07-14
### Changed
- updated sensu-plugin gem to 1.2.0

## 0.0.1 - 2015-06-11
### Added
- initial release
- added ability to use ini files

[Unreleased]: https://github.com/sensu-plugins/sensu-plugins-percona/compare/1.1.0...HEAD
[1.1.0]: https://github.com/sensu-plugins/sensu-plugins-percona/compare/1.0.0...1.1.0
[1.0.0]: https://github.com/sensu-plugins/sensu-plugins-percona/compare/0.0.2...1.0.0
[0.0.2]: https://github.com/sensu-plugins/sensu-plugins-percona/compare/0.0.1...0.0.2

repository: sensu-plugins/sensu-plugins-percona

gha_language: Ruby

gha_license_id: MIT

repo_name: sensu-plugins/sensu-plugins-percona


text:
### 2015-11-11

#### objective-c
* [
      ibireme
      /
      YYText
](https://github.com/ibireme/YYText):
      Powerful text framework for iOS to display and edit rich text.

* [
      SergioChan
      /
      SCCinemaAnimation
](https://github.com/SergioChan/SCCinemaAnimation):
      An iOS native implementation of a Cinema Animation Application. See more at https://dribbble.com/shots/2339238-Animation-for-Cinema-Application. iOS上电影购票的动效实现

* [
      Overcoat
      /
      Overcoat
](https://github.com/Overcoat/Overcoat):
      The perfect accessory for Mantle and AFNetworking.

* [
      coderyi
      /
      NetworkEye
](https://github.com/coderyi/NetworkEye):
      a iOS network debug library iOS网络调试库，NetworkEye可以监控App内HTTP请求并显示请求相关的详细信息，方便App开发的网络调试。

* [
      SergioChan
      /
      SCTrelloNavigation
](https://github.com/SergioChan/SCTrelloNavigation):
      An iOS native implementation of a Trello Animated Navagation. See more at https://dribbble.com/shots/2114816-Trello-Navigation. iOS上类似trello的导航动效控件实现。

* [
      ibireme
      /
      YYWebImage
](https://github.com/ibireme/YYWebImage):
      Asynchronous image loading framework.

* [
      AFNetworking
      /
      AFNetworking
](https://github.com/AFNetworking/AFNetworking):
      A delightful iOS and OS X networking framework

* [
      CoderMJLee
      /
      MJRefresh
](https://github.com/CoderMJLee/MJRefresh):
      An easy way to use pull-to-refresh.

* [
      victorBaro
      /
      VBFPopFlatButton
](https://github.com/victorBaro/VBFPopFlatButton):
      Flat button with 9 different states using POP

* [
      SnapKit
      /
      Masonry
](https://github.com/SnapKit/Masonry):
      Harness the power of AutoLayout NSLayoutConstraints with a simplified, chainable and expressive syntax. Supports iOS and OSX Auto Layout

* [
      coderyi
      /
      Monkey
](https://github.com/coderyi/Monkey):
      Monkey is a GitHub third party client for iOS,to show the rank of coders and repositories.

* [
      bang590
      /
      JSPatch
](https://github.com/bang590/JSPatch):
      JSPatch bridge Objective-C and Javascript using the Objective-C runtime. You can call any Objective-C class and method in JavaScript by just including a small engine. JSPatch is generally use for hotfix iOS App.

* [
      ReactiveCocoa
      /
      ReactiveCocoa
](https://github.com/ReactiveCocoa/ReactiveCocoa):
      Streams of values over time

* [
      jessesquires
      /
      JSQMessagesViewController
](https://github.com/jessesquires/JSQMessagesViewController):
      An elegant messages UI library for iOS

* [
      yuantiku
      /
      YTKNetwork
](https://github.com/yuantiku/YTKNetwork):
      YTKNetwork is a high level request util based on AFNetworking.

* [
      facebook
      /
      xctool
](https://github.com/facebook/xctool):
      A replacement for Apple's xcodebuild that makes it easier to build and test iOS or OSX apps.

* [
      PureLayout
      /
      PureLayout
](https://github.com/PureLayout/PureLayout):
      The ultimate API for iOS & OS X Auto Layout — impressively simple, immensely powerful. Objective-C and Swift compatible.

* [
      JustinFincher
      /
      JZMultiChoicesCircleButton
](https://github.com/JustinFincher/JZMultiChoicesCircleButton):
      Multi choice circle button with cool 3d parallax effect

* [
      jdg
      /
      MBProgressHUD
](https://github.com/jdg/MBProgressHUD):
      MBProgressHUD + Customizations

* [
      ccgus
      /
      fmdb
](https://github.com/ccgus/fmdb):
      A Cocoa / Objective-C wrapper around SQLite

* [
      CoderMJLee
      /
      MJExtension
](https://github.com/CoderMJLee/MJExtension):
      A fast, convenient and nonintrusive conversion between JSON and model. Your model class don't need to extend another base class. You don't need to modify any model file.

* [
      kevinzhow
      /
      PNChart
](https://github.com/kevinzhow/PNChart):
      A simple and beautiful chart lib used in Piner and CoinsMan for iOS

* [
      FuzzyAutocomplete
      /
      FuzzyAutocompletePlugin
](https://github.com/FuzzyAutocomplete/FuzzyAutocompletePlugin):
      A Xcode 5+ plugin that adds more flexible autocompletion rather than just prefix-matching.

* [
      alcatraz
      /
      Alcatraz
](https://github.com/alcatraz/Alcatraz):
      Package manager for Xcode

* [
      ChenYilong
      /
      ParseSourceCodeStudy
](https://github.com/ChenYilong/ParseSourceCodeStudy):
      Facebook开源的Parse源码分析【系列】

#### go
* [
      docker
      /
      docker
](https://github.com/docker/docker):
      Docker - the open-source application container engine

* [
      golang
      /
      go
](https://github.com/golang/go):
      The Go programming language

* [
      gogits
      /
      gogs
](https://github.com/gogits/gogs):
      Gogs (Go Git Service) is a painless self-hosted Git service.

* [
      kubernetes
      /
      kubernetes
](https://github.com/kubernetes/kubernetes):
      Container Cluster Manager from Google

* [
      avelino
      /
      awesome-go
](https://github.com/avelino/awesome-go):
      A curated list of awesome Go frameworks, libraries and software

* [
      ajstarks
      /
      svgo
](https://github.com/ajstarks/svgo):
      Go Language Library for SVG generation

* [
      spf13
      /
      hugo
](https://github.com/spf13/hugo):
      A Fast and Flexible Static Site Generator built with love by spf13 in GoLang

* [
      svent
      /
      sift
](https://github.com/svent/sift):
      A fast and powerful open source alternative to grep

* [
      robbiev
      /
      numberwang
](https://github.com/robbiev/numberwang):
      Easily copy file names from shell command output

* [
      cortesi
      /
      devd
](https://github.com/cortesi/devd):
       A local webserver for developers

* [
      getlantern
      /
      lantern
](https://github.com/getlantern/lantern):

 Open Internet for everyone. Lantern is a free desktop application that delivers fast, reliable and secure access to the open Internet for users in censored regions. It uses a variety of techniques to stay unblocked, including P2P and domain fronting. Lantern relies on users in uncensored regions acting as access points to the open Internet.

* [
      Comcast
      /
      Canticle
](https://github.com/Comcast/Canticle):
* [
      henrylee2cn
      /
      pholcus
](https://github.com/henrylee2cn/pholcus):
      [爬虫框架 (golang)] Pholcus（幽灵蛛）是一款纯Go语言编写的高并发、分布式、重量级爬虫软件，支持单机、服务端、客户端三种运行模式，拥有Web、GUI、命令行三种操作界面；规则简单灵活、批量任务并发、输出方式丰富（mysql/mongodb/csv/excel等）、有大量Demo共享；同时她还支持横纵向两种抓取模式，支持模拟登录和任务暂停、取消等一系列高级功能。

* [
      spf13
      /
      viper
](https://github.com/spf13/viper):
      Go configuration with fangs

* [
      wicast
      /
      xj2s
](https://github.com/wicast/xj2s):
      A small tool for Golang to generate Golang struct from a xml/json file

* [
      alexflint
      /
      go-arg
](https://github.com/alexflint/go-arg):
      Struct-based argument parsing in Go

* [
      deis
      /
      helm
](https://github.com/deis/helm):
      Helm - The Kubernetes Package Manager

* [
      gin-gonic
      /
      gin
](https://github.com/gin-gonic/gin):
      Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.

* [
      mholt
      /
      caddy
](https://github.com/mholt/caddy):
      Fast, cross-platform HTTP/2 web server with HTTPS on by default

* [
      variadico
      /
      noti
](https://github.com/variadico/noti):
      Display a notification after a terminal process finishes.

* [
      astaxie
      /
      beego
](https://github.com/astaxie/beego):
      beego is an open-source, high-performance web framework for the Go programming language.

* [
      junegunn
      /
      fzf
](https://github.com/junegunn/fzf):

 A command-line fuzzy finder written in Go

* [
      yuroyoro
      /
      gommit-m
](https://github.com/yuroyoro/gommit-m):
      gommit-m - Command Line Client for commit-m (http://commit-m.minamijoyo.com)

* [
      centrifugal
      /
      centrifugo
](https://github.com/centrifugal/centrifugo):
      Real-time messaging (Websockets or SockJS) server in Go

* [
      Repo2
      /
      y
](https://github.com/Repo2/y):
      Be faster with Y. The simplest ORM-like framework for Golang.

#### javascript
* [
      uber
      /
      react-map-gl
](https://github.com/uber/react-map-gl):
* [
      Webschool-io
      /
      be-mean-instagram
](https://github.com/Webschool-io/be-mean-instagram):
      Curso voltado a ensinar o stack conhecido como MEAN(MongoDb, Express, Angular e Node.js) para criarmos um sistema igual do Instagram.

* [
      rackt
      /
      react-router
](https://github.com/rackt/react-router):
      A complete routing solution for React.js

* [
      rain1017
      /
      memdb
](https://github.com/rain1017/memdb):
      Distributed Transactional In-Memory Database (全球首个支持分布式事务的MongoDB)

* [
      nix23
      /
      gridifier
](https://github.com/nix23/gridifier):
      Async Responsive Html Grids

* [
      a1k0n
      /
      jsxm
](https://github.com/a1k0n/jsxm):
      FastTracker 2 .xm module player in Javascript

* [
      benoitvallon
      /
      react-native-nw-react-calculator
](https://github.com/benoitvallon/react-native-nw-react-calculator):
      Mobile, desktop and website Apps with the same code

* [
      facebook
      /
      react-native
](https://github.com/facebook/react-native):
      A framework for building native apps with React.

* [
      jaredreich
      /
      notie.js
](https://github.com/jaredreich/notie.js):
      A clean and simple notification plugin (alert/growl style) for javascript, with no dependencies.

* [
      AllThingsSmitty
      /
      jquery-tips-everyone-should-know
](https://github.com/AllThingsSmitty/jquery-tips-everyone-should-know):
      A collection of simple tips to help up your jQuery game

* [
      cdmedia
      /
      simplestore
](https://github.com/cdmedia/simplestore):
      A clean, responsive storefront boilerplate with no database or backend

* [
      matt-curtis
      /
      Fluid-for-Sketch
](https://github.com/matt-curtis/Fluid-for-Sketch):
      Sketch-flavored Auto Layout-like Constraints

* [
      facebook
      /
      react
](https://github.com/facebook/react):
      A declarative, efficient, and flexible JavaScript library for building user interfaces.

* [
      rackt
      /
      redux
](https://github.com/rackt/redux):
      Predictable state container for JavaScript apps

* [
      vuejs
      /
      vue
](https://github.com/vuejs/vue):
      Simple yet powerful library for building modern web interfaces.

* [
      airbnb
      /
      javascript
](https://github.com/airbnb/javascript):
      JavaScript Style Guide

* [
      angular
      /
      angular.js
](https://github.com/angular/angular.js):
      HTML enhanced for web apps

* [
      getify
      /
      You-Dont-Know-JS
](https://github.com/getify/You-Dont-Know-JS):
      A book series on JavaScript. @YDKJS on twitter.

* [
      mbostock
      /
      d3
](https://github.com/mbostock/d3):
      A JavaScript visualization library for HTML and SVG.

* [
      react-toolbox
      /
      react-toolbox
](https://github.com/react-toolbox/react-toolbox):
      A set of React components implementing Google's Material Design specification with the power of CSS Modules

* [
      openproject
      /
      ganchai
](https://github.com/openproject/ganchai):
       干柴（客户端、服务端）

* [
      babel
      /
      babel
](https://github.com/babel/babel):
      Babel is a compiler for writing next generation JavaScript.

* [
      sindresorhus
      /
      ava
](https://github.com/sindresorhus/ava):
      Futuristic test runner

* [
      webpack
      /
      webpack
](https://github.com/webpack/webpack):
      A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

* [
      nodejs
      /
      node
](https://github.com/nodejs/node):
      Node.js JavaScript runtime

#### ruby
* [
      thoughtbot
      /
      administrate
](https://github.com/thoughtbot/administrate):
      A Rails engine that helps you put together a super-flexible admin dashboard.

* [
      Homebrew
      /
      homebrew
](https://github.com/Homebrew/homebrew):

 The missing package manager for OS X.

* [
      guidomb
      /
      carthage_cache
](https://github.com/guidomb/carthage_cache):
      A tool that allows to cache Carthage/Build folder in Amazon S3.

* [
      Thibaut
      /
      devdocs
](https://github.com/Thibaut/devdocs):
      API Documentation Browser

* [
      franzejr
      /
      ruby-tricks
](https://github.com/franzejr/ruby-tricks):
      Ruby Tricks

* [
      jondot
      /
      awesome-react-native
](https://github.com/jondot/awesome-react-native):
      An "awesome" type curated list of React Native components, news, tools, and learning material

* [
      rails
      /
      rails
](https://github.com/rails/rails):
      Ruby on Rails

* [
      caskroom
      /
      homebrew-cask
](https://github.com/caskroom/homebrew-cask):
      A CLI workflow for the administration of Mac applications distributed as binaries

* [
      fastlane
      /
      fastlane
](https://github.com/fastlane/fastlane):
      Connect all iOS deployment tools into one streamlined workflow

* [
      discourse
      /
      discourse
](https://github.com/discourse/discourse):
      A platform for community discussion. Free, open, simple.

* [
      jekyll
      /
      jekyll
](https://github.com/jekyll/jekyll):
      Jekyll is a blog-aware, static site generator in Ruby

* [
      spree
      /
      spree
](https://github.com/spree/spree):
      Spree is a complete open source e-commerce solution for Ruby on Rails.

* [
      realm
      /
      jazzy
](https://github.com/realm/jazzy):
      Soulful docs for Swift & Objective-C

* [
      bbatsov
      /
      rubocop
](https://github.com/bbatsov/rubocop):
      A Ruby static code analyzer, based on the community Ruby style guide.

* [
      chef
      /
      inspec
](https://github.com/chef/inspec):
      InSpec: Auditing and Testing Framework

* [
      gitlabhq
      /
      gitlabhq
](https://github.com/gitlabhq/gitlabhq):
      GitLab is version control for your server

* [
      mitchellh
      /
      vagrant
](https://github.com/mitchellh/vagrant):
      Vagrant is a tool for building and distributing development environments.

* [
      solidusio
      /
      solidus
](https://github.com/solidusio/solidus):
      Solidus, Rails eCommerce System

* [
      CocoaPods
      /
      CocoaPods
](https://github.com/CocoaPods/CocoaPods):
      The Cocoa Dependency Manager.

* [
      elastic
      /
      logstash
](https://github.com/elastic/logstash):
      logstash - transport and process your logs, events, or other data

* [
      cantino
      /
      huginn
](https://github.com/cantino/huginn):
      Build agents that monitor and act on your behalf. Your agents are standing by!

* [
      plataformatec
      /
      devise
](https://github.com/plataformatec/devise):
      Flexible authentication solution for Rails with Warden.

* [
      IFTTT
      /
      polo
](https://github.com/IFTTT/polo):
      Polo travels through your database and creates sample snapshots so you can work with real world data in development.

* [
      sass
      /
      sass
](https://github.com/sass/sass):
      Sass makes CSS fun again.

* [
      dkhamsing
      /
      frankenstein
](https://github.com/dkhamsing/frankenstein):
      Checks for live URLs and correct READMEs

repository: josephyzhou/github-trending

gha_language: Go

repo_name: josephyzhou/github-trending


text:
        The
         AWS
        Cloud Provider for
         Kubernetes

# cloud-provider-aws
The AWS cloud provider provides the interface between a Kubernetes cluster and AWS service APIs. This project allows a Kubernetes cluster to provision, monitor and remove AWS resources necessary for operation of the cluster.

    See the online documentation here

## Compatibility with Kubernetes

The AWS cloud provider is released with a specific semantic version that correlates with the Kubernetes upstream version. The major and minor versions are equivalent to the compatible upstream release, and the patch version is reserved to denote subsequent releases of the cloud provider code for that Kubernetes release.  Currently, for a given cloud provider release version, compatibility is ONLY guaranteed between that release and the corresponding Kubernetes version, meaning you need to upgrade the cloud provider components every time you upgrade Kubernetes, just like you would do for the kube controller manager.  See the [external cloud provider versioning KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/1771-versioning-policy-for-external-cloud-providers) for more details.

| Kubernetes Version          | Latest AWS Cloud Provider Release Version     |
|-----------------------------|-----------------------------------------------|
| v1.27                       | v1.27.1                                       |
| v1.26                       | v1.26.1                                       |
| v1.25                       | v1.25.3                                       |
| v1.24                       | v1.24.4                                       |
| v1.23                       | v1.23.6                                       |
| v1.22                       | v1.22.7                                       |
| v1.21                       | v1.21.6                                       |
| v1.20                       | v1.20.4                                       |
| v1.19                       | v1.19.0-alpha.1                               |
| v1.18                       | v1.18.0-alpha.1                               |

## Migration from In-Tree
The in-tree cloud provider code has mostly stopped accepting new features, so future development for the AWS cloud provider should continue here.  The in-tree plugins will be removed in a future release of Kubernetes.

## Components

### AWS Cloud Controller Manager
The AWS Cloud Controller Manager is the controller that is primarily responsible for creating and updating AWS loadbalancers (classic and NLB) and node lifecycle management.  The controller loops that are migrating out of the kube controller manager include the route controller, the service controller, the node controller, and the node lifecycle controller.  See the [cloud controller manager KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2392-cloud-controller-manager) for more details.

##### Container Images
AWS Cloud Controller Managed container images are available in `registry.k8s.io/provider-aws/cloud-controller-manager`.

### AWS Credential Provider
The AWS credential provider is a binary that is executed by kubelet to provide credentials for images in ECR.  Refer to the [credential provider extraction KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2133-out-of-tree-credential-provider) for more details.

### Volume Plugins
All the EBS volume plugin related logic will be in maintenance mode. For new feature request or bug fixes, please create issue or pull request in [EBS CSI Driver](https://github.com/kubernetes-sigs/aws-ebs-csi-driver)

repository: kubernetes/cloud-provider-aws

repo_name: kubernetes/cloud-provider-aws


text:
---
title: "Set Theory in Statistics"
draft: false
weight: 9
katex: true
---

### Representing Elements and Sets
- An element is an object
- Specifically, an element can be an individual number, word, set, etc.
- For example, $\text{\textbraceleft}{3, 4}\text{\textbraceright}$ is an element of the set $\text{\textbraceleft}{1, 2, \text{\textbraceleft}{3, 4}\text{\textbraceright}}\text{\textbraceright}$
- For example, $\text{\textbraceleft}{a, b}\text{\textbraceright}$ is an element of the set $\text{\textbraceleft}{\text{\textbraceleft}{a, b}\text{\textbraceright}, c}\text{\textbraceright}$
- A set is made up of elements
- Since an element can be a set, then a set can contain other sets as well
- For example, $\text{A}$ is a valid set if $\text{A} = \text{\textbraceleft}{1,2,3}\text{\textbraceright}$, since $1$, $2$, and $3$ are all valid elements of a set
- Also, $\text{B}$ is a valid set if $\text{B} = \text{\textbraceleft}{1,2,\text{\textbraceleft}{3,4}\text{\textbraceright}}\text{\textbraceright}$, since $1$, $2$, and $\text{\textbraceleft}{3, 4}\text{\textbraceright}$ are all valid elements of a set
- Also, $\text{C}$ is a valid set if $\text{C} = \text{\textbraceleft}{red,blue,green}\text{\textbraceright}$, since the colors $red$, $blue$, and $green$ are all valid elements of a set

### Set Notation
- A set is a unique sequence of observable outcomes
- For example, $\text{\textbraceleft}{1,2,3,4,5,6}\text{\textbraceright}$ could be a set, representing the outcomes of rolling a single die
- An event is a set of outcomes that is written as a capital letter
- For example, we could denote a set that represents the outcomes of rolling a single die as the following:

$$
\text{A} = \text{\textbraceleft}{1,2,3,4,5,6}\text{\textbraceright}
$$

- Keep in mind that events are written as a normal, capital letter, whereas a random variable is written as an italicized, capital letter
- A realization of a random variable is written as a italicized, lower-case letter

### Denoting Random Variables
- As a reminder, a random variable is a function that maps a single value from a sample space to any single, real-number realization
- Typically, we denote a random variable as the following:

$$
X: \Omega \to \R
$$

$$
\text{such } \text{that } \omega \mapsto X(\omega)
$$

$$
\text{such } \text{that } \omega \in \Omega
$$

$$
\text{such } \text{that } X(\omega) \in \R
$$

- Here, $\Omega$ is a set that represents the domain of the random variable function
- $\R$ is a set that represents the range of the random variable function
- $\omega$ represents an element, or a single value, from the set $\Omega$
- $X(\omega)$ represents an element, or a single value, from the set $\R$
- $X(\omega)$ also represents a realization of the random variable function

### Denoting Probability
- As a reminder, probability represent a function that maps a single value from the sample space to a realization that is in the interval of 0 and 1
- Typically, the output of the random variable function becomes the input of the probability function
- Therefore, the sample space will represent the range of the random variable
- We denote a probability as the following:

$$
P: \Omega \to [0,1]
$$

$$
\text{such } \text{that } \omega \mapsto P(\omega)
$$

### Denoting Events
- Sometimes, we don't want our function to map a single value from $\Omega$, or we don't want our function to map to $\R$
- In this situation, we would create an event
- For example, we could have the following:
	- Let $\Omega$ denote the sample space
	- Let $\text{A}$ be an event that is a subset of $\R$
	- Let $X$ be our random variable
- We could then define our random variable as the following:

$$
X: \Omega \to \text{A}
$$

$$
\text{such } \text{that } \omega \mapsto X(\omega)
$$

$$
\text{such } \text{that } \text{A} \subset \R
$$

$$
\text{such } \text{that } \omega \in \Omega
$$

$$
\text{such } \text{that } X(\omega) \in \text{A}
$$

- Here, $\Omega$ is a set that represents the domain of the random variable function
- The set $\text{A}$ is a set that represents the range of the random variable function
- Also, $\text{A}$ is an event that is a subset of all real numbers
- $\omega$ represents an element, or a single value, from the set $\Omega$
- $X(\omega)$ represents an element, or a single value, from the event $\text{A}$

### Another Example of Denoting Events
- Let's say we have the following situation:
	- An event $\text{A}$ is a subset of $\Omega$
	- $\R$ is a set of all real numbers
	- $X$ is our random variable
- We could define our random variable as the following:

$$
X: \text{A} \to \R
$$

$$
\text{such } \text{that } \omega \mapsto X(\omega)
$$

$$
\text{such } \text{that } \text{A} \subset \Omega
$$

$$
\text{such } \text{that } \omega \in \text{A}
$$

$$
\text{such } \text{that } X(\omega) \in \R
$$

- Here, the event $\text{A}$ is a set that represents the domain of the random variable function
- $\R$ is a set that represents the range of the random variable function
- Also, $\text{A}$ is an event that is a subset of the sample space
- $\omega$ represents an element, or a single value, from the set $\text{A}$
- $X(\omega)$ represents an element, or a single value, from the set $\R$

### One Last Example of Denoting Events
- Let's say the following is true:
	- Let $\text{A}$ be an event that represents the set {red, white, blue}
	- Let $\text{B}$ be an event that represents the set {cat, dog}
	- Let $X$ be our random variable
	- Let $\Omega$ be our sample space, which is the set of all colors
- We could define our random variable as the following:

$$
X: \text{A} \to \text{B}
$$

$$
\text{such } \text{that } \omega \mapsto X(\omega)
$$

$$
\text{such } \text{that } \text{A} = \text{\textbraceleft}{red, white, blue}\text{\textbraceright}
$$

$$
\text{such } \text{that } \text{B} = \text{\textbraceleft}{cat, dog}\text{\textbraceright}
$$

$$
\text{such } \text{that } \omega \in \text{A}
$$

$$
\text{such } \text{that } X(\omega) \in \text{B}
$$

- Here, the event $\text{A}$ is a set that represents the domain of the random variable function
- Also, the event $\text{B}$ is a set that represents the range of the random variable function
- The set $\text{A}$ is an event that is a subset of our sample space (i.e. colors)
- The set $\text{B}$ is an event that is a subset of animals
- $\omega$ represents an element, or a single value, from the event $\text{A}$
- $X(\omega)$ represents an element, or a single value, from the event $\text{B}$

### Remarks on Mathematical Notation
- As stated previously, a random variable $X$ is a function defined as the following:

$$
X: \Omega \to \R
$$

- However, we often refer to $X$ using the following shorthand formula:

$$
X(\omega) \text{ such} \text{ that } \omega \in \Omega
$$

- Probability functions can be written in many ways:

$$
p_{X}(x) \equiv P(X = x) \equiv P(\text{\textbraceleft}{s \in S : X(s) = x}\text{\textbraceright})
$$

- We can generally denote sets as the following:

$$
S \equiv \text{\textbraceleft}{\text{type of each element in list} : \text{range of each element}}\text{\textbraceright}
$$

- Here are a few examples showing how we can denote different sets:

$$
S \equiv \text{\textbraceleft}{i \in \R : 1 \le i \le 6, x \text{ is odd}}\text{\textbraceright}
$$

$$
S \equiv \text{\textbraceleft}{(i, j) : 1 \le i \le 6, 1 \le j \le 6}\text{\textbraceright}
$$

- We can also denote realizations as the following:

$$
X(s) \equiv X((i, j)) = i + j
$$

### Further Notation
- We can define sets as long as they obey either of the following notations:

$$
\text{\textbraceleft}{\text{an element}}\text{\textbraceright} \in \text{\textbraceleft}{\text{a set}}\text{\textbraceright}
$$

$$
\text{\textbraceleft}{\text{a set}}\text{\textbraceright} \in \text{\textbraceleft}{\text{a collection of sets}}\text{\textbraceright}
$$

$$
\text{\textbraceleft}{\text{a set}}\text{\textbraceright} \subset \text{\textbraceleft}{\text{a set}}\text{\textbraceright}
$$

$$
\text{\textbraceleft}{\text{a collection of sets}}\text{\textbraceright} \subset \text{\textbraceleft}{\text{a collection of sets}}\text{\textbraceright}
$$

- For example, we can write $a \in \text{A}$
	- Where $\text{A}$ is an event (which is a set)
	- Where $a$ is an outcome or realization of $\text{A}$
- We can also write $\text{A} \in ℑ$
	- Where $\text{A}$ is an event (which is a set)
	- Where $ℑ$ is an algebra (which is a collection of sets)
- Or, we can write $\text{A} \subset \text{B}$
	- Where $\text{A}$ and $\text{B}$ are both events (which are sets)
- We can also write $ℑ_{0} \subset ℑ_{1}$
	- Where $ℑ_{0}$ is an algebra (which is a collection of sets) that is contained within an algebra $ℑ_{1}$ (which is larger a collection of sets)

### Reference
- [List of Mathematical Symbols Wiki](https://en.wikipedia.org/wiki/List_of_mathematical_symbols)
- [What Exactly is a Random Variable](https://math.stackexchange.com/questions/240673/what-exactly-is-a-random-variable)
- [Lexture Notes on Random Variables](http://www.columbia.edu/~ww2040/4106S11/lec0125.pdf)
- [Probability, Statistics and Stochastic Processes](http://bactra.org/prob-notes/srl.pdf)
- [Regressors as Fixed and Random Variables](https://stats.stackexchange.com/questions/246047/independent-variable-random-variable)
- [Basic Theory of Stochastic Processes Slides](http://www.phdeconomics.sssup.it/documents/Lesson3.pdf)


text:
## What does this PR Do?

## Remaining Work (If WIP Status)

## Where should the reviewer start?

## How has this been tested?

## Any background context you want to provide?

## Screenshots (if appropriate)

## Questions:
- How will this be deployed?
- Are there any migrations that need to be run?
- Are there any changes in environment variables or configs that need to happen?
- Does the README or Wiki need to be updated for this PR?

repository: testdouble/satisfaction

repo_name: testdouble/satisfaction


text:
# Webscrapping-nodejs

A webscrapping tool built with nodejs 12.3.1 and puppeteer 1.17.0.

## Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

### Installing and starting environment

Clone the project
```bash
$ git clone https://github.com/leo-bianchi/webscrapping-nodejs.git
```

```bash
$ cd webscrapping-nodejs
```
### Building and running container

Build Container
```bash
$ docker build -t ubuntu/node-scrapping .
```

Run Container
```bash
$ docker run -it --rm --network host ubuntu/node-scrapping
```

### API's runs at port 3000

If you are on linux, on browser type:
```bash
localhost:3000/url
```

Windows:
On browser type:
```
<IP_ADDRESS>:3000/url
```

## Authors

*   **Leonardo Bianchi** - *Initial work* - [leo-bianchi](https://github.com/leo-bianchi)

## Built With

*   [Nodejs](https://nodejs.org/en/) - The framework used. Nodeenv, by default, install the lastest nodejs version. When I build this project, nodejs was on 12.3.1 release.
*   [NPM](https://www.npmjs.com) - Dependencies Management.
*   [Puppeteer](https://github.com/GoogleChrome/puppeteer) - Used lib for web scrapping.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details

repository: gbmadeira/webscrapping-nodejs

repo_name: gbmadeira/webscrapping-nodejs


text:
# JoinItems

Fork of the plugin by iSach and modified to work on OB-Minecraft.
Configure items to be added to a players inventory on joining a server or respawning.

Simple Join Items plugin.

compiled with Spigot 1.20.

Compiled with Java 17.

Uses Maven.

Original github [here](https://github.com/iSach/JoinItems)


text:
---------------------------
## Collapsible-Toolbar-Helper
----------------------------

A combination of custom CollapsibleToolbar and Collapsing Text to give you the same effect as App Bar Layout from the Desgin support library sans the use of a Toolbar

-----------
## ScreenShot
----------

![Screenshot](https://github.com/melvinjlobo/Collapsible-Toolbar-Helper/blob/master/CollabpsibleToolbarHelper.gif)

--------------
## BACKGROUND :
--------------

# CollapsibleToolbarHelper :
Although the new design support library allows us to do some cool stuff, the available sample code  does not cover the potential that it has been built for. Most of the samples that I came across, including the cheese square example by Chris Banes, create the application so that minimum code has to be written.

**But what if I want a different layout and implementation?**
My main requirement was that I did NOT require a Toolbar for my design. When going through the AOSP code for CollapsibleTollbarLayout in the design support library, I realized that it has a tight integration with the Toolbar. So, Initially, I decided to work around that.

Few of them are listed below:

1. [Thanks Grzesiek Gajewski](https://lab.getbase.com/introduction-to-coordinator-layout-on-android/)
2. [Thanks Saul Molinero](http://saulmm.github.io/mastering-coordinator/)
3. [Thanks Rafa Vazquez](https://gitlab.com/Sloy/collapsing-avatar-toolbar/blob/bf1c86c61021cb77bc28c1669475b116ef1a4e5a/library/src/main/java/com/sloydev/collapsingavatartoolbar/CollapsingAvatarToolbar.java)

In a nutshell, it all boils down to a few things:

1. Coordinator Layout controls the "behavior" of its children which implement
    [CoordinatoLayout.Behavior](http://developer.android.com/reference/android/support/design/widget/CoordinatorLayout.Behavior.html)
  Check out NestedScrollView "Behavior" or AppBarLayout "Behavior" or FAB "Behavior" for implementations

2. AppBarLayout calls on a [OnOffsetChangedListener](http://developer.android.com/reference/android/support/design/widget/AppBarLayout.OnOffsetChangedListener.html) implementation when it scrolls,
   which can be used to do stuff. Check out OnOffsetChangedListener in
   CollapsingToolbarLayout

Well, that was my premise of creating the CollapsibleToolbarHelper. It of course is derived heavily from the AOSP code, but with a few modifications. It supports the following collapse modes:
	- MOVE_ON_SCROLL = The children move when the collapsible toolbar collapses to hit the bottom of that view
    - PARALLAX_ON_SCROLL = THe usual parallax, move and then hide when the Toolbar collapses
    - PIN_ON_SCROLL = Stays at the position where it is laid out originally
    - HIDE_ON_COLLAPSE = Stays at its location and hides when the toolbar is collapsed
    - SHOW_ON_COLLAPSE = Is hidden at the location that it is supposed to and appears
    after the Toolbar has collapsed
**Note that it has to be used as a direct child of AppBarLayout since it depends on the OffsetChangedListener of the AppBarLayout to collapse and expand.**

# CollapsibleTextLayout :
  Since I was designing the CollapsibleToolbar, I required a CollapsibleText as well. But the default CollapsibleTextHelper is coupled too tightly with the CollapsingToolbarLayout and not public to be modified. So, taking inspirations
from AOSP, Chris banes' [Philm](https://github.com/chrisbanes/philm/blob/master/app/src/main/java/app/philm/in/view/CollapsingTitleLayout.java) and Nick Butchers [Plaid](https://github.com/nickbutcher/plaid/blob/master/app/src/main/java/io/plaidapp/util/CollapsingTextHelper.java), I wrote my own CollapsingTextlayout.

I know that there is a lot of room for improvement and that there are obvious optimizations and feature enhancements, but the main objective of re-writing these widgets was learning. I have collected all the ideas from the given references and tried to simplify the implementation as much as possible. The code is commented and should be self explanatory.

Interested? Well go ahead, download and use the widgets.
_______

# Usage
```xml
<android.support.design.widget.CoordinatorLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:fitsSystemWindows="true">

    <android.support.design.widget.AppBarLayout
        android:id="@+id/app_bar"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:paddingTop="5dp"
        android:paddingBottom="30dp"
<EMAIL_ADDRESS>        >

        <abysmel.com.collapsibletoolbarhelper.widgets.CollapsibleToolbarHelper
            android:id="@+id/toolbar_layout"
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            app:layout_scrollFlags="scroll|exitUntilCollapsed"
            android:gravity="center_vertical"
            android:layout_marginTop="10dp"
            android:background="@android:color/transparent"
            >

	        <!--Note that the position has to be set with respect to the collapsed toolbar. So,
	            aligning it in center initially (centerInParent="true") will NOT work as it will remain
	            at its position even after the Toolbar collapses. Also note that the initially set the
	            alpha of the view to zero and NOT the visibility to gone, as the view will then have never
	            been drawn which will throw all calculations haywire for show_on_collapse. Wish there
	            was a better way to do this-->
            <ImageView
                android:layout_width="wrap_content"
                android:layout_height="wrap_content"
<EMAIL_ADDRESS>	            android:src="@mipmap/hello"
	            android:layout_marginLeft="10dp"
	            android:alpha="0"
                app:layout_marginTopPercent = "3%"
                app:collapseMode="show_on_collapse"/>

            <!-- Title -->
            <abysmel.com.collapsibletoolbarhelper.widgets.CollapsibleTextLayout
<EMAIL_ADDRESS>                android:layout_height="wrap_content"
                android:layout_width="wrap_content"
                app:layout_widthPercent="59%"
                android:layout_alignParentLeft="true"
                app:layout_marginTopPercent = "1%"
                app:layout_marginBottomPercent = "1%"
                app:layout_marginLeftPercent="5%"
                android:textColor="@android:color/white"
                app:collapseMode="pin_on_scroll"
                app:textToShow = "Hello World"
                app:expandedTextColor = "@android:color/white"
                app:collapsedTextColor = "@android:color/white"
                app:typefaceFamilyPrimary = "sans-serif-light"
                app:typefaceFamilySecondary = "sans-serif-medium"
                app:isMultiFaceted="true"
                app:typefaceSplitPosition="5"
                app:expandedTextSize = "62dp"
                app:collapsedTextSize = "32dp"
                app:maxExpandedTextSize = "62dp"
                />

            <!-- The hello number edit button -->
            <ImageView
<EMAIL_ADDRESS>                android:layout_width="wrap_content"
                android:layout_height="wrap_content"
                android:layout_alignParentRight="true"
                app:layout_marginTopPercent = "3%"
                app:layout_marginBottomPercent = "1%"
                app:layout_marginRightPercent = "4%"
                android:layout_marginLeft="10dp"
                android:src="@mipmap/pencil"
                app:collapseMode="hide_on_collapse"/>

            <!-- The hello Number -->
            <TextView
<EMAIL_ADDRESS>                android:layout_height="wrap_content"
                android:layout_width="wrap_content"
                app:layout_widthPercent="40%"
                app:layout_marginTopPercent = "1%"
                app:layout_marginBottomPercent = "1%"
                app:layout_marginRightPercent = "1%"
<EMAIL_ADDRESS><EMAIL_ADDRESS>                android:gravity="end"
                android:text="@string/hello_no_sign"
                android:textColor="@android:color/white"
                android:textSize="@dimen/hello_no_size"
                app:collapseMode="pin_on_scroll"/>

            <!-- Version -->
            <TextView
                android:id="@+id/version"
                app:layout_widthPercent="40%"
                android:layout_height="wrap_content"
                android:layout_width="wrap_content"
<EMAIL_ADDRESS>                android:layout_marginTop="5dp"
                android:layout_alignParentLeft="true"
                app:layout_marginLeftPercent="5%"
                android:text="@string/version"
                android:textColor="@android:color/white"
                android:textSize="@dimen/version_no_size"
                app:collapseMode="parallax_on_scroll"
                 />

            <!-- E-mail Address -->
            <TextView
<EMAIL_ADDRESS>                app:layout_widthPercent="40%"
                android:layout_height="wrap_content"
                android:layout_width="wrap_content"
<EMAIL_ADDRESS>                android:layout_alignParentRight="true"
                android:gravity="end"
                app:layout_marginRightPercent="5%"
                android:text="@string/emailaddress"
                android:textColor="@android:color/white"
                android:textSize="@dimen/mail_address_size"
                app:collapseMode="parallax_on_scroll"
                 />
        </abysmel.com.collapsibletoolbarhelper.widgets.CollapsibleToolbarHelper>
    </android.support.design.widget.AppBarLayout>
</android.support.design.widget.CoordinatorLayout>
```
-------
## REFERENCES
--------
- [Philm](https://github.com/chrisbanes/philm/blob/master/app/src/main/java/app/philm/in/view/CollapsingTitleLayout.java)
- [Plaid](https://github.com/nickbutcher/plaid/blob/master/app/src/main/java/io/plaidapp/util/CollapsingTextHelper.java)
- [AutoFit TextView](https://github.com/grantland/android-autofittextview)
-  [Grzesiek Gajewski](https://lab.getbase.com/introduction-to-coordinator-layout-on-android/)
- [Saul Molinero](http://saulmm.github.io/mastering-coordinator/)
- [Rafa Vazquez](https://gitlab.com/Sloy/collapsing-avatar-toolbar/blob/bf1c86c61021cb77bc28c1669475b116ef1a4e5a/library/src/main/java/com/sloydev/collapsingavatartoolbar/CollapsingAvatarToolbar.java)

----------
## LICENSE
-------

The MIT License (MIT)

Copyright (c) 2016 Melvin Lobo

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.

____

[![Android Arsenal](https://img.shields.io/badge/Android%20Arsenal-Collapsible%20Toolbar-green.svg?style=flat)](https://android-arsenal.com/details/1/3001)


text:
---
# MIC33153 click

MIC33153 click is a DC-DC adjustable step-down (buck) converter that is designed to deliver a substantial amount of current to very demanding loads, with the voltage output up to 3.5V.

[click Product page](https://www.mikroe.com/mic33153-click)

---

#### Click library

- **Author**        : MikroE Team
- **Date**          : Jan 2020.
- **Type**          : SPI type

# Software Support

We provide a library for the Mic33153 Click
as well as a demo application (example), developed using MikroElektronika
[compilers](https://shop.mikroe.com/compilers).
The demo can run on all the main MikroElektronika [development boards](https://shop.mikroe.com/development-boards).

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

## Library Description

> This library contains API for Mic33153 Click driver.

#### Standard key functions :

- Config Object Initialization function.
> void mic33153_cfg_setup ( mic33153_cfg_t *cfg );

- Initialization function.
> MIC33153_RETVAL mic33153_init ( mic33153_t *ctx, mic33153_cfg_t *cfg );

- Click Default Configuration function.
> void mic33153_default_cfg ( mic33153_t *ctx );

#### Example key functions :

- This function writes 12-bit value to DAC and that causes that output voltage be seted on determined value.
> void mic33153_write_dac ( mic33153_t *ctx, const uint16_t value_dac );

- This function enables or disables output voltage depending on the state value.
> void mic33153_enable_out ( mic33153_t *ctx, uint8_t state );

- This function hecks state of PG (INT) pin. If state is 1 that means that output voltage is above 92% of its steady
- state voltage. If state is 0 that means that output voltage is below 86% of its steady state voltage.
> uint8_t mic33153_check_power_good ( mic33153_t *ctx );

## Examples Description

> This app enables step-down (buck) converter.

**The demo application is composed of two sections :**

### Application Init

> Initializes click driver.

```c

void application_init ( void )
{
    log_cfg_t log_cfg;
    mic33153_cfg_t cfg;

    /**
     * Logger initialization.
     * Default baud rate: 115200
     * Default log level: LOG_LEVEL_DEBUG
     * @note If USB_UART_RX and USB_UART_TX
     * are defined as HAL_PIN_NC, you will
     * need to define them manually for log to work.
     * See @b LOG_MAP_USB_UART macro definition for detailed explanation.
     */
    LOG_MAP_USB_UART( log_cfg );
    log_init( &logger, &log_cfg );
    log_info( &logger, "---- Application Init ----" );

    //  Click initialization.

    mic33153_cfg_setup( &cfg );
    MIC33153_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    mic33153_init( &mic33153, &cfg );
    Delay_ms( 100 );
}

```

### Application Task

> Activates the output voltage of the device, and then sets output voltage to various different values.
> All data is being logged on USB UART.

```c

void application_task ( void )
{
    mic33153_enable_out( &mic33153, MIC33153_OUT_ENABLE );

    mic33153_write_dac ( &mic33153, MIC33153_VOLTAGE_1000MV );
    log_printf( &logger, "Output voltage set to 1000mV\r\n" );
    Delay_ms(2000);

    mic33153_write_dac ( &mic33153, MIC33153_VOLTAGE_1500MV );
    log_printf( &logger, "Output voltage set to 1500mV\r\n" );
    Delay_ms(2000);

    mic33153_write_dac ( &mic33153, MIC33153_VOLTAGE_2000MV );
    log_printf( &logger, "Output voltage set to 2000mV\r\n" );
    Delay_ms(2000);

    mic33153_write_dac ( &mic33153, MIC33153_VOLTAGE_2500MV );
    log_printf( &logger, "Output voltage set to 2500mV\r\n" );
    Delay_ms(2000);

    mic33153_write_dac ( &mic33153, MIC33153_VOLTAGE_3000MV );
    log_printf( &logger, "Output voltage set to 3000mV\r\n" );
    Delay_ms(2000);

    mic33153_write_dac ( &mic33153, MIC33153_VOLTAGE_3200MV );
    log_printf( &logger, "Output voltage set to 3200mV\r\n" );
    Delay_ms(2000);

    log_printf( &logger, "-----------------------------------\r\n" );
}

```

The full application code, and ready to use projects can be  installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

**Other mikroE Libraries used in the example:**

- MikroSDK.Board
- MikroSDK.Log
- Click.Mic33153

**Additional notes and informations**

Depending on the development board you are using, you may need
[USB UART click](https://shop.mikroe.com/usb-uart-click),
[USB UART 2 Click](https://shop.mikroe.com/usb-uart-2-click) or
[RS232 Click](https://shop.mikroe.com/rs232-click) to connect to your PC, for
development systems with no UART to USB interface available on the board. The
terminal available in all Mikroelektronika
[compilers](https://shop.mikroe.com/compilers), or any other terminal application
of your choice, can be used to read the message.

---

gha_language: C

gha_license_id: NOASSERTION


text:
---
author: nate
date: '2011-09-23 17:24:56'
layout: post
slug: scalatra-on-dotcloud
status: publish
title: Scalatra on Dotcloud
wordpress_id: '274'
categories:
- Misc
---

I couldn't easily find information on this, so here's a summary for those that go after me.

A working example is in the sbt-scalatra-on-dotcloud branch of my fork of my friend's sbt-scalatra-example project.  If it gets merged in, I'll update this post.

The sbt-scalatra-example project combines two great technologies.  The first is Scalatra, a super light-weight web framework for Scala that's modeled after Ruby's Sinatra.  The second is the simple-build-tool (sbt), a tool for building Scala applications that's more like rake (config file written in real programming language) than make or ant/maven (config file written in an abstract form).  I was able to run the example, but I wanted to try out deploying to dotcloud, and doing that requires a war file (according to the java service documentation).

The biggest thing I had to figure out is that as of version 0.10 of sbt, web application support is now in the xsbt-web-plugin plugin.  Just knowing that would have saved me an hour this morning. Setting that up and tweaking a few other files means I can now do this:

``` plain
$ sbt clean package-war
... snip ...
[info] Packaging /home/user/sbt-scalatra-example/target/scala-2.9.1.final/sbt-scalatra-example.war ...
[info] Done packaging.
[success] Total time: 13 s, completed Sep 23, 2011 3:57:00 PM

$ cp target/scala-2.9.1.final/sbt-scalatra-example.war dotcloud/ROOT.war

$ dotcloud create sbtscalatra
Created application "sbtscalatra"

$ cd dotcloud && dotcloud push sbtscalatra
... snip ...
Deployment finished. Your application is available at the following URLs
www: http://sbtscalatra-xxx.dotcloud.com/
```

Of course, this assumes you've installed sbt (brew install sbt on the mac) and signed up and configured Dotcloud.

Have fun.

extension: markdown


text:
# Grafeo Utils
| Banner | Link |
| ------ | ----- |
| ![travis-banner](https://travis-ci.org/lkskstlr/grafeo-utils.svg?branch=master) | [travis](https://travis-ci.org/lkskstlr/grafeo-utils?branch=master) |
| ![pypi-banner](https://img.shields.io/pypi/v/grafeo.svg) | [pypi](https://pypi.python.org/pypi/grafeo) |

**This is work in progress and right now not even in alpha. The implementation is most likely not cryptographically sound. Do not use this within any production system. Any help is appreciated, just reach out via github issues :)**

**Cryptographically authenticated supply chain storage protocol.**

---

# Overview
Grafeo is a cryptographic protocol to insure supply chain information authenticity. It works for distributed and centralized databases and does not require trust in any central organization.

This repository contains python utils to interface said protocol without hustle.

# Requirements

* Python (3.6)
* [nacl](https://github.com/pyca/pynacl)
* [requests](https://github.com/requests/requests)

# Installation
Install using `pip`:
```bash
pip install grafeo
```

repository: lkskstlr/grafeo-utils

repo_name: lkskstlr/grafeo-utils


text:
##Create HELM Chart
- helm create <chart-name>
- Name of the chart provided here will be the name of the directory where the chart is created and stored.

```
Let's understand the relevance of these files and folders created for us:

Chart.yaml: This is the main file that contains the description of our chart
values.yaml: this is the file that contains the default values for our chart
templates: This is the directory where Kubernetes resources are defined as templates
charts: This is an optional directory that may contain sub-charts
```

##HELM Commands for Chart
- helm lint <chart-full-path>
#This is a simple command that takes the path to a chart and runs a battery of tests to ensure that the chart is well-formed

- helm template <chart-full-path>
#This will generate all templates with variables without a Tiller Server, for quick feedback, and show the output. Now that we know everything is OK, we can deploy the chart:

- helm install --name <release-name> <chart-full-path>
#Run this command to install the chart into the Kubernetes cluster:

- helm ls --all
#We would like to see which charts are installed as what release.

- helm upgrade <release-name> <chart-full-path>
#This command helps us to upgrade a release to a specified or current version of the chart or configuration:

- helm rollback <release-name> <release-version>
#This is the command to rollback a release to the previous version:

- helm delete --purge <release-name>
#We can use this command to delete a release from Kubernetes:

repository: hariyopmail/DevOps

path: /DevOpsMasterClass/Kubernetes_Devops/Package & Deploy HELM/HELM/Create-helm-chart.md

repo_name: hariyopmail/DevOps


text:
# Hiera Bulk Edit

This tool facilitates the programmatic bulk editing of Hiera YAML files (or any YAML files really).

By allowing the execution of arbitrary python code on the YAML data in memory, a powerful and flexible interface for programmatically updating human-edited Hiera data is provided.  The heavy lifting is done by Anthon van der Neut's [Ruamel](https://bitbucket.org/ruamel/yaml) Python library, and we respect most of the human-edited formatting and commenting of the input file.

# Why Python

Because [there is only one](https://www.ruby-forum.com/topic/6877080) YAML parser that preserves formatting and comments and it's a Python library!

# Install dependencies

Install the Ruamel YAML library:

```
$ pip install -r requirements.txt
```

You should end up with ruamel.yaml version 0.12.7 or higher:

```
$ pip list ruamel.yaml |grep ruamel
ruamel.ordereddict (0.4.9)
ruamel.yaml (0.12.7)
```

# Usage

```
$ hiera-bulk-edit.py <paths> <code_file>.py
```

Note that Bash Globbing and Brace Expansion are supported in `<paths>`.

## Example usage

```
$ hiera-bulk-edit.py '*/control_repo/hieradata' do_stuff_to_hiera.py
```

## Example code files

The following example replaces all `hiera['foo']['bar']` keys
with the values specified:

```python
try:
    # 'hiera' is the Ruamel Dictionary structure that represents the
    # Hiera file's YAML data. The purpose of the block of code is always
    # to edit this dictionary in some way before the calling script
    # writes it back to disk.

    hiera['foo']['bar'] = {
        'key1': 'val1',
        'key2': 'val2',
    }

except:
    # We would get to here if, for example, the Hiera file does not contain the
    # key hiera['foo'].
    e = sys.exc_info()[0]

    # The following variables are also available from the calling script's scope:
    #   'f' is the filename of the file being edited.
    print "Got %s when updating %s" % (e, f)
```

### Adding a key with formatting

```python
# add_a_key_with_quotes.py
# http://stackoverflow.com/questions/39262556/preserve-quotes-and-also-add-data-with-quotes-in-ruamel

from ruamel.yaml.scalarstring import SingleQuotedScalarString, DoubleQuotedScalarString

hiera['foo'] = SingleQuotedScalarString('bar')
hiera['bar'] = DoubleQuotedScalarString('baz')
```

This will add two new keys to the bottom of each YAML file.

### Deleting all keys starting with a pattern

```python
# delete_all_fluentd_keys.py
for k in hiera.keys():
    if k.startswith('fluentd'):
        hiera.pop(k)
```

### More examples

Look in the `code_file_examples` directory.

## Variables in the code file

### hiera

The Hiera YAML data is stored in a Python Dictionary called `hiera`.

### f

The file name of the YAML file being edited is stored in `f`.

## Known issues

The Ruamel library does not preserve all indentation styles but normalises the input file.  Inconsistencies in the human-edited indentation would be reset by the Bulk Edit script.  Likewise, whitespaces are not always preserved.

The Ruamel project is still in beta and other bugs may come to light.  Proceed cautiously and check all diffs before merging changes.

## Acknowledgements

All credit to Anthon van der Neut for Ruamel.yaml, and in particular for his help on Stack Overflow and his quick response to bug reports.

gha_language: Python


text:
# Preferences

*Property syntax for Android's SharedPreferences.*

For use in Kotlin. This library uses Kotlin's property delegation to make
using SharedPreferences as easy as accessing a property on an object. It
relies on the `appCtx` module of this library to allow usage in `object` in
Kotlin, and can support storage on device encrypted storage for devices
supporting Direct Boot. See [the source code](
/src/main/java/splitties/preferences) for more information

### Usage
Define your preferences in an `object` that extends
`splitties.preferences.Preferences`, like in the example below:
```kotlin
import splitties.preferences.Preferences

object GamePreferences : Preferences("gameState") {
    var magicNumber by intPref(0) // The property name is used as the key.
    var currentLevel by IntPref("currentLevel", 1)
    var bossesFought by IntPref("bossBattleVictories", 0)
    var lastTimePlayed by LongPref("lastSessionTime", 0L)
    var pseudo by StringPref("playerPseudo", "Player 1")
    var favoriteCharacter by stringOrNullPref()
}
```

Then just use the properties:

```kotlin
fun setResponseOfTheUltimateQuestionOfLifeTheUniverseAndEverything() {
    GamePreferences.magicNumber = 42
}

fun doSomeMagic() {
    toast("Magic: ${GamePreferences.magicNumber}!")
}

fun resetProgress() {
    GamePreferences.edit { // Batch edit
        currentLevel = 1
        bossesFought = 0
    }
}
```

The supported types are:
* `Boolean`
* `Int`
* `Float`
* `Long`
* `String`
* `String?`
* `Set<String>`
* `Set<String>?`

For **default SharedPreferences**, make an `object` that extends
`DefaultPreferences` instead of `Preferences`.

#### Why `object` and not `class`?

Using a `class` instead of an `object` is not recommended because it would
mean you can instantiate it multiple times, while the underlying preferences
xml file is cached for the rest of your app's process lifetime once loaded,
so in a `class` you'd be allocating the delegates more times than needed,
leading to an additional, unneeded, small pressure on the garbage collector.

However, you may make an abstract subclass of `Preferences` for specific
use cases where adding logic to base `Preferences` or sharing some
properties may be desirable. (If you do, please open an issue to tell us
about this use case. It may become an example shown here.)

## Download

```groovy
implementation "com.louiscad.splitties:splitties-preferences:$splitties_version"
```

repository: tanghb/Splitties

repo_name: tanghb/Splitties


text:
# ghost-backupper
A docker image for manually archiving and backing up a ghost blog

## Usage Details

### Environment Variables
 - `USER_ID` - The user id that will create the archives. Ex. `1000`
 - `GROUP_ID` - The group id that will be assigned to the created user. Ex. `1000`
 - `WEBSITE_NAME` - The name that will prepend the archives names

repository: dannycarrera/ghost-backupper

repo_name: dannycarrera/ghost-backupper


text:
# Conda Cross-platform Setup

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

## Installation

A [*conda virtual environment*](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html) is provided for isolation and reproducibility. If `conda` is not already available on the system (e.g. through Anaconda), Miniconda will be automatically downloaded and installed.

### Windows

Clone or download the repository and navigate to `bin` directory. Double click on:

- `install.bat` to install the software;

- `uninstall.bat` to uninstall the software. Note: `conda` will not be removed.

### Linux/macOS

Clone or download the repository and open a terminal in the root directory. Run:

- `./bin/install.sh` to install the software;

- `./bin/uninstall.sh` to uninstall the software. Note: `conda` will not be removed.

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

## Usage

### Windows

Navigate to `bin` directory and double click on `jupyter-notebook.bat`.

### Linux/macOS

Open a terminal in the root directory and run `./bin/jupyter-notebook.sh`.

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

## Contact

<EMAIL_ADDRESS>
---------------------------------------------------------------------------------------------------------

repository: lucadellalib/conda-cross-platform-setup

repo_name: lucadellalib/conda-cross-platform-setup


text:
# googclass-to-es6class

Transform a google closure class defined using goog.defineClass into an es6 class

For example:

```javascript
const Parent = goog.require('some.ns.Parent');

const FooBar = goog.defineClass(Parent, {
  /**
   * Creates a new instance of...
   * @param {Object} name
   */
  constructor: function(name) {
    this.name = name;
  }
});

exports = FooBar;
```

Will be transformed into:

```javascript
const Parent = goog.require('some.ns.Parent');

class FooBar extends Parent {
  /**
   * Creates a new instance of...
   * @param {Object} name
   */
  constructor(name) {
    super(name);

    this.name = name;
  }
}

exports = FooBar;
```

## How to use it

### Install from npm

```shell
npm i goog-class-to-es6 -g
```

### Transform a file

Provide the name of the file. The transformed class will be written to stdout:

```shell
goog-class-to-es6 some_goog_define_class.js
```

Do inline replacement. The file will be overwritten.

```shell
goog-class-to-es6 -i some_goog_define_class.js
```

Write to another file

```shell
goog-class-to-es6 some_goog_define_class.js output_file_es6.js
```

## Testing

```shell
# 1. Clone this repo
# 2. Install
npm i
# 3. Test
npm test
```

## Changelog

* 1.4.0 Add empty line at the end of file if original file has it.
* 1.5.0 Skip files without goog.defineClass.
* 1.6.0 Add support for functions declared like: foo() {
* 1.7.0 Escape closure type casts because Babel strips them.

gha_language: JavaScript


text:
# Spotify Discography CLI

Create and update Spotify discography playlists.

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/spotify-discography-cli.svg)](https://npmjs.org/package/spotify-discography-cli)
[![License](https://img.shields.io/npm/l/spotify-discography-cli.svg)](https://github.com/jakubito/spotify-discography-cli/blob/master/package.json)

<!-- toc -->

- [Spotify Discography CLI](#spotify-discography-cli)
- [Installation](#installation)
- [First-time setup](#first-time-setup)
- [Usage](#usage)
- [Track history](#track-history)
- [Automation](#automation)
- [Commands](#commands)
- [Data storage](#data-storage)
- [Bug reporting](#bug-reporting)
- [License](#license)
<!-- tocstop -->

# Installation

## NPM / Yarn

```
npm install -g spotify-discography-cli
```

or

```
yarn global add spotify-discography-cli
```

## Standalone tarballs

You can download standalone tarballs from [Releases](https://github.com/jakubito/spotify-discography-cli/releases) section. These include the node binary so you don't have to have Node / NPM / Yarn installed.

# First-time setup

In order to use this app, you have to provide a Spotify app's client ID and secret. To obtain these, you have to create a new app within Spotify dashboard:

1. Log in to [Spotify Dashboard](https://developer.spotify.com/dashboard/) with your account.
2. Click on **Create an app** and provide title and description of your choice (e.g. _Spotify Discography CLI_)
3. Check both checkboxes and click on **Create**
4. On the app page, click on **Edit Settings**
5. Add `http://localhost:10101` to your **Redirect URIs** field and click "Save"
6. You should see your app's client ID and secret in top left

Once you have client ID and secret, run

```
spotify-discography init
```

You will be asked for client ID and secret followed by authorization with Spotify. Once authorized, you should see a success message.

That's it! You can now start using the app.

# Usage

## Create a new discography

To create a new discography playlist for specific artist, you have to get that artist's ID first. There are many ways to get an artist's ID. The easiest one is to go to an artist's page in the web player and check the url - the ID is highlighted in bold: https//open.spotify.com/artist/**5oDtp2FC8VqBjTx1aT4P5j**

Once you have artist ID, run

```
spotify-discography create ARTIST_ID
```

for example

```
spotify-discography create 5oDtp2FC8VqBjTx1aT4P5j
```

This will create a new discography private playlist and display hyperlink in supported terminals.

## Update an existing discography

It is possible to update an existing playlist with new releases. In this case, you have to provide **both** artist and playlist IDs. The process of getting a playlist's ID is the same as it is for an artist - open a playlist in web player and check the url.

Once you have both artist and playlist IDs, run

```
spotify-discography update ARTIST_ID PLAYLIST_ID
```

for example

```
spotify-discography update 5oDtp2FC8VqBjTx1aT4P5j 6pyiISrb7yoHw7YDhV7xH8
```

# Track history

Each time you create or update a playlist, the information about tracks added is saved on disk. On each update, this data is loaded and checked against. In other words, if you delete a track from a playlist, it won't be added again on next update.

You can override this behaviour using `--force` flag when updating a playlist. This will ignore track history and force add all missing tracks.

# Automation

To automate playlist updates, the easiest way is to set up a cron job. The following example updates the playlist with new releases once a day:

```
0 0 * * * /Users/jakubito/Documents/spotify-discography/bin/spotify-discography update 2CIMQHirSU0MQqyYHq0eOx 3igxuZDwGlXocuh9b2T14D
```

# Commands

<!-- commands -->

- [`spotify-discography config [CONFIG_KEY] [CONFIG_VALUE]`](#spotify-discography-config-config_key-config_value)
- [`spotify-discography create ARTIST_ID`](#spotify-discography-create-artist_id)
- [`spotify-discography help [COMMAND]`](#spotify-discography-help-command)
- [`spotify-discography init`](#spotify-discography-init)
- [`spotify-discography reset`](#spotify-discography-reset)
- [`spotify-discography update ARTIST_ID PLAYLIST_ID`](#spotify-discography-update-artist_id-playlist_id)

## `spotify-discography config [CONFIG_KEY] [CONFIG_VALUE]`

display / update config

```
USAGE
  $ spotify-discography config [CONFIG_KEY] [CONFIG_VALUE]

ARGUMENTS
  CONFIG_KEY    [optional] config key - one of "authServerPort", "userId", "clientId", "clientSecret", "accessToken",
                "refreshToken", "tokenExpiration"

  CONFIG_VALUE  [optional] config value to save

OPTIONS
  -h, --help  show CLI help

EXAMPLES
  $ spotify-discography config clientId 9d08c83130e2933e6a440541371fb458

  $ spotify-discography config clientId
  9d08c83130e2933e6a440541371fb458

  $ spotify-discography config
  authServerPort: 10101
  clientId:       9d08c83130e2933e6a440541371fb458
```

_See code: [src/commands/config.ts](https://github.com/jakubito/spotify-discography-cli/blob/v1.0.2/src/commands/config.ts)_

## `spotify-discography create ARTIST_ID`

create new discography playlist

```
USAGE
  $ spotify-discography create ARTIST_ID

ARGUMENTS
  ARTIST_ID  [required] Spotify artist ID

OPTIONS
  -h, --help  show CLI help

EXAMPLE
  $ spotify-discography create 5oDtp2FC8VqBjTx1aT4P5j
  Creating new playlist... done
  SHY FX Discography
```

_See code: [src/commands/create.ts](https://github.com/jakubito/spotify-discography-cli/blob/v1.0.2/src/commands/create.ts)_

## `spotify-discography help [COMMAND]`

display help for spotify-discography

```
USAGE
  $ spotify-discography help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI
```

_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v3.1.0/src/commands/help.ts)_

## `spotify-discography init`

initialize config and authorize with Spotify

```
USAGE
  $ spotify-discography init

OPTIONS
  -h, --help  show CLI help
```

_See code: [src/commands/init.ts](https://github.com/jakubito/spotify-discography-cli/blob/v1.0.2/src/commands/init.ts)_

## `spotify-discography reset`

reset config to default values

```
USAGE
  $ spotify-discography reset

OPTIONS
  -h, --help  show CLI help
```

_See code: [src/commands/reset.ts](https://github.com/jakubito/spotify-discography-cli/blob/v1.0.2/src/commands/reset.ts)_

## `spotify-discography update ARTIST_ID PLAYLIST_ID`

update existing discography playlist

```
USAGE
  $ spotify-discography update ARTIST_ID PLAYLIST_ID

ARGUMENTS
  ARTIST_ID    [required] Spotify artist ID
  PLAYLIST_ID  [required] Spotify playlist ID

OPTIONS
  -f, --force  ignore history and force add all missing tracks
  -h, --help   show CLI help

EXAMPLE
  $ spotify-discography update 5oDtp2FC8VqBjTx1aT4P5j 6pyiISrb7yoHw7YDhV7xH8
  Updating playlist... done
  SHY FX Discography
```

_See code: [src/commands/update.ts](https://github.com/jakubito/spotify-discography-cli/blob/v1.0.2/src/commands/update.ts)_

<!-- commandsstop -->

# Data storage

All application data is stored locally on your computer:

- Unix: `~/.config/spotify-discography-cli`
- Windows: `%LOCALAPPDATA%\spotify-discography-cli`

# Bug reporting

If you find a bug, please send me an e-mail to<EMAIL_ADDRESS>or open an issue here on github.

# License

ISC

license: ISC

repository: jakubito/spotify-discography-cli

gha_license_id: ISC

repo_name: jakubito/spotify-discography-cli


text:
# refactored-waffle
Spike repo for testing actions and workflows for validating OpenAPI schema versions

The action uses a containerized version of [openapitools/openapi-diff](https://github.com/OpenAPITools/openapi-diff)

Possible alternative to the diff lib could be [tufin/oasdiff](https://github.com/Tufin/oasdiff)

Install Act to work on the action locally:
```
brew install act
```

If using [act](https://github.com/nektos/act) to dev the action locally run the command below:

```
act pull_request -e /act_data/pull_request.json -s GITHUB_TOKEN=[TOKEN] --privileged --bind
```

or if you are using env and secret files.

```
act pull_request -e /act_data/pull_request.json --env-file ${HOME}/.config/act/.env --secret-file ${HOME}/.config/act/vault.env --privileged --bind
```

Running act currently pollutes the repo root with the following directories and files but are ignored in .gitignore:

```
_actions
base
head
workflow
results
```

### Other scripts

This repo contains a ruby script that can be used to generate a change set between two sets of OpenAPI schemas.  There are example diff set schemas checked into this repo as well.
Generate changesets by running the following command from the root.

```
ruby ./.github/workflows/generate_changeset.rb $PWD/schemas/base/descriptions $PWD/schemas/head/descriptions
```

repository: nickfloyd/refactored-waffle

repo_name: nickfloyd/refactored-waffle


text:
## UNFINISHED & NOT ON PACKAGIST!

# Keeps track of the original UTM (or other analytics) parameters

[![Latest Version on Packagist](https://img.shields.io/packagist/v/spatie/laravel-analytics-tracker.svg?style=flat-square)](https://packagist.org/packages/spatie/laravel-analytics-tracker)
[![GitHub Tests Action Status](https://img.shields.io/github/workflow/status/spatie/laravel-analytics-tracker/run-tests?label=tests)](https://github.com/spatie/laravel-analytics-tracker/actions?query=workflow%3Arun-tests+branch%3Amaster)
[![Total Downloads](https://img.shields.io/packagist/dt/spatie/laravel-analytics-tracker.svg?style=flat-square)](https://packagist.org/packages/spatie/laravel-analytics-tracker)

Cross domain analytics is hard. This package helps you to keep track of the visitor's original UTM parameters, referer header and other analytics parameters. You can then submit these parameters along with a form submission or add them to a link to another domain you track.

## Support us

[<img src="https://github-ads.s3.eu-central-1.amazonaws.com/laravel-utm-forwarder.jpg?t=1" width="419px" />](https://spatie.be/github-ad-click/laravel-utm-forwarder)

We invest a lot of resources into creating [best in class open source packages](https://spatie.be/open-source). You can support us by [buying one of our paid products](https://spatie.be/open-source/support-us).

We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on [our contact page](https://spatie.be/about-us). We publish all received postcards on [our virtual postcard wall](https://spatie.be/open-source/postcards).

## Installation

You can install the package via composer:

```bash
composer require spatie/laravel-analytics-tracker
```

The package works via a middleware that needs to be added to the `web` stack in your `kernel.php` file. Make sure to register this middleware after the `StartSession` middleware.

```php
// app/Http/Kernel.php

protected $middlewareGroups = [
    'web' => [
        // ...
        \Illuminate\Session\Middleware\StartSession::class,
        // ...

        \Spatie\AnalyticsTracker\Middleware\TrackAnalyticsParametersMiddleware::class,
    ],
];
```

To configure the tracked parameters or how they're mapped on the URL parameters, you can publish the config file using:

```bash
php artisan vendor:publish --provider="Spatie\AnalyticsTracker\AnalyticsTrackerServiceProvider"
```

This is the contents of the published config file:

```php
return [
    /*
     * These are the analytics parameters that will be tracked when a user first visits
     * the application. The configuration consists of the parameter's key and the
     * source to extract this key from.
     *
     * Available sources can be found in the `\Spatie\AnalyticsTracker\Sources` namespace.
     */
    'tracked_parameters' => [
        [
            'key' => 'utm_source',
            'source' => Spatie\AnalyticsTracker\Sources\RequestParameter::class,
        ],
        [
            'key' => 'utm_medium',
            'source' => Spatie\AnalyticsTracker\Sources\RequestParameter::class,
        ],
        [
            'key' => 'utm_campaign',
            'source' => Spatie\AnalyticsTracker\Sources\RequestParameter::class,
        ],
        [
            'key' => 'utm_term',
            'source' => Spatie\AnalyticsTracker\Sources\RequestParameter::class,
        ],
        [
            'key' => 'utm_content',
            'source' => Spatie\AnalyticsTracker\Sources\RequestParameter::class,
        ],
        [
            'key' => 'referer',
            'source' => Spatie\AnalyticsTracker\Sources\CrossOriginRequestHeader::class,
        ],
    ],

    /**
     * We'll put the tracked parameters in the session using this key.
     */
    'session_key' => 'tracked_analytics_parameters',

    /*
     * When formatting an URL to add the tracked parameters we'll use the following
     * mapping to put tracked parameters in URL parameters.
     *
     * This is useful when using an analytics solution that ignores the utm_* parameters.
     */
    'parameter_url_mapping' => [
        'utm_source' => 'utm_source',
        'utm_medium' => 'utm_medium',
        'utm_campaign' => 'utm_campaign',
        'utm_term' => 'utm_term',
        'utm_content' => 'utm_content',
        'referer' => 'referer',
    ],
];
```

## Usage

The easiest way to retrieve the tracked parameters is by resolving the `TrackedAnalyticsParameters` class:

```php
use Spatie\AnalyticsTracker\AnalyticsBag;

app(AnalyticsBag::class)->get(); // returns an array of tracked parameters
```

You can also decorate an existing URL with the tracked parameters. This is useful to forward analytics to another domain you're running analytics on.

```blade
<a href="{{ app(\Spatie\AnalyticsTracker\AnalyticsTracker::class)->decorateUrl('https://mywebshop.com/') }}">
    Buy this product on our webshop
</a>

Will link to https://mywebshop.com?utm_source=facebook&utm_campaign=blogpost
```

## Testing

``` bash
composer test
```

## Changelog

Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.

## Contributing

Please see [CONTRIBUTING](.github/CONTRIBUTING.md) for details.

## Security Vulnerabilities

Please review [our security policy](../../security/policy) on how to report security vulnerabilities.

## Credits

- [Alex Vanderbist](https://github.com/AlexVanderbist)
- [All Contributors](../../contributors)

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

repository: rGaillard/laravel-utm-forwarder

repo_name: rGaillard/laravel-utm-forwarder


text:
# ☁ AWS EC2 Alfred workflow

* ✨ Create and manage AWS EC2 instances to run kafka-docker-playground

* 🪄 Open EC2 instances directly in Visual Studio code using [Remote Development](https://code.visualstudio.com/docs/remote/ssh) (over SSH)

![Example](example.png)

❗ You need [Alfred](https://www.alfredapp.com) [powerpack](https://www.alfredapp.com/shop/) to be able to use that workflow.

## 🎯 Commands available

![Example](commands.png)

## ☑ Prerequisites

* `aws` should be installed: `brew install awscli` and correctly [configured](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-prereqs.html) with credentials.
* `jq` should be installed: `brew install jq`
* `code` should be installed:
  * open Visual Studio Code
  * Then press the keys command-shift-P (or ⌘-⇧-P), a text field should appear, stating with a >.
  * Now, type "Shell Command: Install ‘code’ command in PATH", and click on the option.

## 🛠 Configuration

Configure directly within Alfred

![Example](config.png)

## ⬇ Download

Click [here](https://github.com/vdesabou/kafka-docker-playground/raw/master/cloudformation/aws-ec2-kafka-docker-playground.alfred5workflow)

repository: vdesabou/kafka-docker-playground

gha_language: Shell

repo_name: vdesabou/kafka-docker-playground


text:
# Count words occurrence

[![npm version](https://badge.fury.io/js/count-words-occurrence.svg)](https://badge.fury.io/js/count-words-occurrence) [![Build Status](https://travis-ci.org/samouss/count-words-occurrence.svg?branch=master)](https://travis-ci.org/samouss/count-words-occurrence)

## Installation

```
npm install --save count-words-occurrence
```

## Usage

Import the module in your application:

```js
// From ES6
import countWords from 'count-words-occurrence'

// From CJS
const countWords = require('count-words-occurrence');

// From global
const countWords = countWordsOccurrence.default;

// Then use it juste like that:
const result = countWords(input, options);
```

## Documentation

```js
countWords(input, options);
```

#### **input**

Type: `string`

#### **options.caseSensitive**

Type: `boolean` | default: `false`

#### **options.minLength**

Type: `number` | default: `2`

The minimum length of words to count.

#### **options.predicates**

Type: `Array<(x: string) => boolean>` | default: `[]`

An array of functions to apply to each word for enable custom filters.

## Run the test

```
npm test
```


text:
# PhyDNet - Disentangling Physical Dynamics from Unknown Factors for Unsupervised Video Prediction
[Vincent Le Guen](https://www.linkedin.com/in/vincentleguen/),  [Nicolas Thome](http://cedric.cnam.fr/~thomen/)

Code for our CVPR 2020 paper "Disentangling Physical Dynamics from Unknown Factors for Unsupervised Video Prediction": https://arxiv.org/abs/2003.01460

<img src="https://github.com/vincent-leguen/PhyDNet/blob/master/images/fig1.png" width="500">

## Abstract
Leveraging physical knowledge described by partial differential equations (PDEs) is an appealing way to improve unsupervised video prediction methods. Since physics is too restrictive for describing the full visual content of generic videos, we introduce PhyDNet, a two-branch deep architecture, which explicitly disentangles PDE dynamics from unknown complementary information. A second contribution is to propose a new  recurrent physical cell (PhyCell), inspired from data assimilation techniques, for performing PDE-constrained prediction in latent space. Extensive experiments conducted on four various datasets show the ability of PhyDNet to outperform state-of-the-art methods. Ablation studies also highlight the important gain brought out by both disentanglement and PDE-constrained prediction. Finally, we show that PhyDNet presents interesting features for dealing with  missing data and long-term forecasting.

## Code

In main.py, there is an example on how to run PhyDNet on the Moving MNIST dataset.

If you find this code useful for your research, please cite our [paper](https://papers.nips.cc/paper/8672-shape-and-time-distortion-loss-for-training-deep-time-series-forecasting-models):

```
@incollection{leguen20phydnet,
title = {Disentangling Physical Dynamics from Unknown Factors for Unsupervised Video Prediction},
author = {Le Guen, Vincent and Thome, Nicolas},
booktitle = {Computer Vision and Pattern Recognition (CVPR)},
year = {2020}
}
```

repository: vincent-leguen/PhyDNet

repo_name: vincent-leguen/PhyDNet


text:
### [CVE-2015-9139](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9139)
![](https://img.shields.io/static/v1?label=Product&message=Snapdragon%20Mobile%2C%20Snapdragon%20Wear&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Vulnerability&message=Improper%20Input%20Validation%20in%20Modem&color=brighgreen)

### Description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810, and SD 820, improper input validation can occur while negotiating an SSL handshake.

### POC

#### Reference
- http://www.securityfocus.com/bid/103671

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

repository: trickest/cve

gha_language: HTML

repo_name: trickest/cve


text:
##`/products/<imei>/lock_software`

> A `PUT` request to this endpoint will lock the software on the unit to the specified software.

```python
    url = "https://smartapi.bboxx.co.uk/v1/products/000000000000/lock_software"
    data = json.dumps({"software": <software_id> or <software_name>})
    headers = {'Content-Type': 'application/json', 'Authorization': 'Token token=' + A_VALID_TOKEN}

    r = requests.put(url=url, data=data, headers=headers)

    print r.json()
    >>> {
        "status": "success",
        "message": "#866771029490827 updated and locked to software_version <version_name>",
        "data": {
            "software_lock_id": <id>,
            "software_lock_name": <name>,
    }
```

> A `PUT` request with blank payload will remove the software lock.

```python
    url = "https://smartapi.bboxx.co.uk/v1/products/000000000000/lock_software"
    data = json.dumps({"software": None})
    headers = {'Content-Type': 'application/json', 'Authorization': 'Token token=' + A_VALID_TOKEN}

    r = requests.put(url=url, data=data, headers=headers)

    print r.json()
    >>> {
        "status": "success",
        "message": "#866771029490827 software_lock is now removed",
        "data": {
            "software_lock_id": None,
            "software_lock_name": None,
        }
    }
```

This endpoint is used to update the software a unit. The imei of the unit to be enbaled is specified in the url.
A lock is removed by making a `PUT` request to this endpoint with a blank payload.

    | value
---:|:------
__endpoint__ | `/products/<imei>/lock_software`
__method__ | `PUT`
__url_params__ | `product_imei` _(str)_
__payload__ | {"software": <id> or <name>}
__response__ | 200
__permissions__ | __`SYSTEM`__

The endpoint accepts both `software_version_type_id` or `name`. A complete list of the available software versions types can retreived from the `/software_version_type_id` endpoint.

A unit can have its software "locked" to a certain version. If the software is locked then it cannot be updated. See `Software and Locking` for more information.

repository: BBOXX/slate

repo_name: BBOXX/slate


text:
# Toggle Shadow Tool
[![works badge](https://cdn.rawgit.com/nikku/works-on-my-machine/v0.2.0/badge.svg)](https://github.com/nikku/works-on-my-machine)

A simple addon that adds a tool to enable and disable render-to-texture shadows in Garry's Mod.

[Steam Workshop](http://steamcommunity.com/sharedfiles/filedetails/?id=157560152)

## Usage
 - Use primary fire to disable the shadow on an object.
 - Use secondary fire to re-enable a shadow.
 - Use reload to toggle the shadow of an object as well as any constrained objects.
 - Disable all shadows from the option in the Tool menu.
 - Change shadow distance from the option in the Tool menu.

## Compatibility
This addon probably shouldn't interfere with other addons. It it intended to run in Sandbox mode, but it will probably work in any gamemode that is based on Sandbox mode and retains the Tool Gun.

This addon has Duplicator support.

## License
This addon is licensed under the MIT License. Read LICENSE.txt for full terms.

## Contributing
Feel free to create a pull request if you think you have something to contribute to this addon.

If you have a bug report or feature suggestion, make an issue.

repository: clickdevin/toggle-shadow-tool

repo_name: clickdevin/toggle-shadow-tool