text:
<!-- BEGIN MUNGE: GENERATED_TOC -->
- [v1.2.7](#v127)
  - [Downloads for v1.2.7](#downloads-for-v127)
    - [Client Binaries](#client-binaries)
    - [Server Binaries](#server-binaries)
  - [Changelog since v1.2.6](#changelog-since-v126)
    - [Other notable changes](#other-notable-changes)
- [v1.2.6](#v126)
  - [Downloads for v1.2.6](#downloads-for-v126)
  - [Changelog since v1.2.5](#changelog-since-v125)
    - [Other notable changes](#other-notable-changes-1)
- [v1.2.5](#v125)
  - [Downloads for v1.2.5](#downloads-for-v125)
  - [Changes since v1.2.4](#changes-since-v124)
    - [Other notable changes](#other-notable-changes-2)
- [v1.2.4](#v124)
  - [Downloads for v1.2.4](#downloads-for-v124)
  - [Changes since v1.2.3](#changes-since-v123)
    - [Other notable changes](#other-notable-changes-3)
- [v1.2.3](#v123)
  - [Downloads for v1.2.3](#downloads-for-v123)
  - [Changes since v1.2.2](#changes-since-v122)
    - [Action Required](#action-required)
    - [Other notable changes](#other-notable-changes-4)
- [v1.2.2](#v122)
  - [Downloads for v1.2.2](#downloads-for-v122)
  - [Changes since v1.2.1](#changes-since-v121)
    - [Other notable changes](#other-notable-changes-5)
- [v1.2.1](#v121)
  - [Downloads for v1.2.1](#downloads-for-v121)
  - [Changes since v1.2.0](#changes-since-v120)
    - [Other notable changes](#other-notable-changes-6)
- [v1.2.0](#v120)
  - [Downloads for v1.2.0](#downloads-for-v120)
  - [Changes since v1.1.1](#changes-since-v111)
    - [Major Themes](#major-themes)
    - [Other notable improvements](#other-notable-improvements)
    - [Experimental Features](#experimental-features)
    - [Action required](#action-required-1)
    - [Known Issues](#known-issues)
      - [Docker Known Issues](#docker-known-issues)
        - [1.9.1](#191)
    - [Provider-specific Notes](#provider-specific-notes)
      - [Various](#various)
      - [AWS](#aws)
      - [GCE](#gce)
<!-- END MUNGE: GENERATED_TOC -->

<!-- NEW RELEASE NOTES ENTRY -->

# v1.2.7

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.7

filename | sha256 hash
-------- | -----------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes.tar.gz) | `53db157923c17fa7a0addb3e4dfe7d1b9194b9266a87d371a251d5bb790a1832`
[kubernetes-src.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-src.tar.gz) | `e6e46831706743d8263581d0575507cf5ffc265096d22e5e84cf1c3ae925db5e`

### Client Binaries

filename | sha256 hash
-------- | -----------
[kubernetes-client-darwin-386.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-darwin-386.tar.gz) | `8418767e45c62c2ef5f9b4479ed02af64e190ce07dcbafa1920e93e71f419c55`
[kubernetes-client-darwin-amd64.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-darwin-amd64.tar.gz) | `41d742c2c55e7686311978eaaddee3844b990a0fe49fa8597158bcb0ee4c05c9`
[kubernetes-client-linux-386.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-linux-386.tar.gz) | `619e0a450cddf10ed1d42ed1d6330d41a75b9c1e00eb654cbe4b0422cd6099c5`
[kubernetes-client-linux-amd64.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-linux-amd64.tar.gz) | `9a5fcd87514b88eb25173e574aef5b5343816c07ab5947d06787c9f12c40f54a`
[kubernetes-client-linux-arm.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-linux-arm.tar.gz) | `fd6e39b4a56e03448382825f27f4f30a2e981a8d20f4a8cedbd084bbb4577d42`
[kubernetes-client-windows-386.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-windows-386.tar.gz) | `862625cb3d9445cff1b09e4ebcdb60dd93b5b2dc34bb6022d2eeed7c8d8bc5d8`
[kubernetes-client-windows-amd64.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-client-windows-amd64.tar.gz) | `054337e41187e39950de93e4670bc78a95b6901cc2f95c50ff437d9825ae94c5`

### Server Binaries

filename | sha256 hash
-------- | -----------
[kubernetes-server-linux-amd64.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-server-linux-amd64.tar.gz) | `fef041e9cbe5bcf8fd708f81ee2e2783429af1ab9cfb151d645ef9be96e19b73`
[kubernetes-server-linux-arm.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.7/kubernetes-server-linux-arm.tar.gz) | `ce02d7bcd75c31db4f7b9922c19ea2a3312b0ba579b0dcd96b279b661eca18a8`

## Changelog since v1.2.6

### Other notable changes

* Test x509 intermediates correctly ([#34524](https://github.com/kubernetes/kubernetes/pull/34524), [@liggitt](https://github.com/liggitt))

# v1.2.6

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.6

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.6/kubernetes.tar.gz) | `50023455d00af52c41a7158b4bd117b2dfd4a100` | `cf0411bcb620eb13b08b93578efffc43`

## Changelog since v1.2.5

### Other notable changes

* Fix watch cache filtering ([#28967](https://github.com/kubernetes/kubernetes/pull/28967), [@liggitt](https://github.com/liggitt))
* Fix problems with container restarts and flocker ([#25874](https://github.com/kubernetes/kubernetes/pull/25874), [@simonswine](https://github.com/simonswine))

# v1.2.5

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.5

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.5/kubernetes.tar.gz) | `ddf12d7f37dfef25308798d71ad547761d0785ac` | `69d770df8fa4eceb57167e34df3962ca`

## Changes since v1.2.4

### Other notable changes

* Retry Pod/RC updates in kubectl rolling-update ([#27509](https://github.com/kubernetes/kubernetes/pull/27509), [@janetkuo](https://github.com/janetkuo))
* GCE provider: Create TargetPool with 200 instances, then update with rest ([#27865](https://github.com/kubernetes/kubernetes/pull/27865), [@zmerlynn](https://github.com/zmerlynn))
* GCE provider: Limit Filter calls to regexps rather than large blobs ([#27741](https://github.com/kubernetes/kubernetes/pull/27741), [@zmerlynn](https://github.com/zmerlynn))
* Fix strategic merge diff list diff bug ([#26418](https://github.com/kubernetes/kubernetes/pull/26418), [@AdoHe](https://github.com/AdoHe))
* AWS: Fix long-standing bug in stringSetToPointers ([#26331](https://github.com/kubernetes/kubernetes/pull/26331), [@therc](https://github.com/therc))
* AWS kube-up: Increase timeout waiting for docker start ([#25405](https://github.com/kubernetes/kubernetes/pull/25405), [@justinsb](https://github.com/justinsb))
* Fix hyperkube flag parsing ([#25512](https://github.com/kubernetes/kubernetes/pull/25512), [@colhom](https://github.com/colhom))
* kubectl rolling-update support for same image ([#24645](https://github.com/kubernetes/kubernetes/pull/24645), [@jlowdermilk](https://github.com/jlowdermilk))
* Return "410 Gone" errors via watch stream when using watch cache ([#25369](https://github.com/kubernetes/kubernetes/pull/25369), [@liggitt](https://github.com/liggitt))

# v1.2.4

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.4

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.4/kubernetes.tar.gz) | `f3aea83f8f0e16b2b41998a2edc09eb42fd8d945` | `ab0aca3a20e8eba43c8ff9d672793618`

## Changes since v1.2.3

### Other notable changes

* Ensure status is not changed during an update of PV, PVC, HPA objects ([#24924](https://github.com/kubernetes/kubernetes/pull/24924), [@mqliang](https://github.com/mqliang))
* GCI: Add two GCI specific metadata pairs ([#25105](https://github.com/kubernetes/kubernetes/pull/25105), [@andyzheng0831](https://github.com/andyzheng0831))
* Add an entry to the salt config to allow Debian jessie on GCE. ([#25123](https://github.com/kubernetes/kubernetes/pull/25123), [@jlewi](https://github.com/jlewi))
    * As with the existing Wheezy image on GCE, docker is expected to already be installed in the image.
* Fix DeletingLoadBalancer event generation. ([#24833](https://github.com/kubernetes/kubernetes/pull/24833), [@a-robinson](https://github.com/a-robinson))
* GCE: Prefer preconfigured node tags for firewalls, if available ([#25148](https://github.com/kubernetes/kubernetes/pull/25148), [@a-robinson](https://github.com/a-robinson))
* Drain pods created from ReplicaSets in 'kubectl drain' ([#23689](https://github.com/kubernetes/kubernetes/pull/23689), [@maclof](https://github.com/maclof))
* GCI: Update the command to get the image ([#24987](https://github.com/kubernetes/kubernetes/pull/24987), [@andyzheng0831](https://github.com/andyzheng0831))
* Validate deletion timestamp doesn't change on update ([#24839](https://github.com/kubernetes/kubernetes/pull/24839), [@liggitt](https://github.com/liggitt))
* Add support for running clusters on GCI ([#24893](https://github.com/kubernetes/kubernetes/pull/24893), [@andyzheng0831](https://github.com/andyzheng0831))
* Trusty: Add retry in curl commands ([#24749](https://github.com/kubernetes/kubernetes/pull/24749), [@andyzheng0831](https://github.com/andyzheng0831))

# v1.2.3

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.3

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.3/kubernetes.tar.gz) | `b2ce4e0c72562d09ba06e3c0913f0bd78da0285e` | `69e75650de30d5a52d144799e94a168d`

## Changes since v1.2.2

### Action Required

* Make watch cache treat resourceVersion consistent with uncached watch ([#24008](https://github.com/kubernetes/kubernetes/pull/24008), [@liggitt](https://github.com/liggitt))

### Other notable changes

* Fix unintended change of Service.spec.ports[].nodePort during kubectl apply ([#24180](https://github.com/kubernetes/kubernetes/pull/24180), [@AdoHe](https://github.com/AdoHe))
* Flush conntrack state for removed/changed UDP Services ([#22573](https://github.com/kubernetes/kubernetes/pull/22573), [@freehan](https://github.com/freehan))
* Allow setting the Host header in a httpGet probe ([#24292](https://github.com/kubernetes/kubernetes/pull/24292), [@errm](https://github.com/errm))
* Bridge off-cluster traffic into services by masquerading. ([#24429](https://github.com/kubernetes/kubernetes/pull/24429), [@cjcullen](https://github.com/cjcullen))
* Version-guard Kubectl client Guestbook application test against deployments ([#24478](https://github.com/kubernetes/kubernetes/pull/24478), [@ihmccreery](https://github.com/ihmccreery))
* Fix goroutine leak in ssh-tunnel healthcheck. ([#24487](https://github.com/kubernetes/kubernetes/pull/24487), [@cjcullen](https://github.com/cjcullen))
* Fixed mounting with containerized kubelet ([#23435](https://github.com/kubernetes/kubernetes/pull/23435), [@jsafrane](https://github.com/jsafrane))
* Do not throw creation errors for containers that fail immediately after being started ([#23894](https://github.com/kubernetes/kubernetes/pull/23894), [@vishh](https://github.com/vishh))
* Honor starting resourceVersion in watch cache ([#24208](https://github.com/kubernetes/kubernetes/pull/24208), [@ncdc](https://github.com/ncdc))
* Fix TerminationMessagePath ([#23658](https://github.com/kubernetes/kubernetes/pull/23658), [@Random-Liu](https://github.com/Random-Liu))
* Fix gce.getDiskByNameUnknownZone logic. ([#24452](https://github.com/kubernetes/kubernetes/pull/24452), [@a-robinson](https://github.com/a-robinson))
* kubelet: add RSS memory to the summary API ([#24015](https://github.com/kubernetes/kubernetes/pull/24015), [@yujuhong](https://github.com/yujuhong))
* e2e: adapt kubelet_perf.go to use the new summary metrics API ([#24003](https://github.com/kubernetes/kubernetes/pull/24003), [@yujuhong](https://github.com/yujuhong))
* e2e: fix error checking in kubelet stats ([#24205](https://github.com/kubernetes/kubernetes/pull/24205), [@yujuhong](https://github.com/yujuhong))
* Trusty: Avoid unnecessary in-memory temp files ([#24144](https://github.com/kubernetes/kubernetes/pull/24144), [@andyzheng0831](https://github.com/andyzheng0831))
* Allowing type object in kubectl swagger validation ([#24054](https://github.com/kubernetes/kubernetes/pull/24054), [@nikhiljindal](https://github.com/nikhiljindal))
* Add ClusterUpgrade tests ([#24150](https://github.com/kubernetes/kubernetes/pull/24150), [@ihmccreery](https://github.com/ihmccreery))
* Trusty: Do not create the docker-daemon cgroup ([#23996](https://github.com/kubernetes/kubernetes/pull/23996), [@andyzheng0831](https://github.com/andyzheng0831))

# v1.2.2

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.2

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.2/kubernetes.tar.gz) | `8dede5833a1986434adea80749624f81a0db7bb4` | `72a5389f22827fb5133fdc3b7bfb9b3a`

## Changes since v1.2.1

### Other notable changes

* Trusty: Update heapster manifest handling code ([#23434](https://github.com/kubernetes/kubernetes/pull/23434), [@andyzheng0831](https://github.com/andyzheng0831))
* Support addon Deployments, make heapster a deployment with a nanny. ([#22893](https://github.com/kubernetes/kubernetes/pull/22893), [@Q-Lee](https://github.com/Q-Lee))
* Create a new Deployment in kube-system for every version. ([#23512](https://github.com/kubernetes/kubernetes/pull/23512), [@Q-Lee](https://github.com/Q-Lee))
* Use SCP to dump logs and parallelize a bit. ([#22835](https://github.com/kubernetes/kubernetes/pull/22835), [@spxtr](https://github.com/spxtr))
* Trusty: Regional release .tar.gz support ([#23558](https://github.com/kubernetes/kubernetes/pull/23558), [@andyzheng0831](https://github.com/andyzheng0831))
* Make ConfigMap volume readable as non-root ([#23793](https://github.com/kubernetes/kubernetes/pull/23793), [@pmorie](https://github.com/pmorie))
* only include running and pending pods in daemonset should place calculation ([#23929](https://github.com/kubernetes/kubernetes/pull/23929), [@mikedanese](https://github.com/mikedanese))
* A pod never terminated if a container image registry was unavailable ([#23746](https://github.com/kubernetes/kubernetes/pull/23746), [@derekwaynecarr](https://github.com/derekwaynecarr))
* Update Dashboard UI addon to v1.0.1 ([#23724](https://github.com/kubernetes/kubernetes/pull/23724), [@maciaszczykm](https://github.com/maciaszczykm))
* Ensure object returned by volume getCloudProvider incorporates cloud config ([#23769](https://github.com/kubernetes/kubernetes/pull/23769), [@saad-ali](https://github.com/saad-ali))
* Add a timeout to the sshDialer to prevent indefinite hangs. ([#23843](https://github.com/kubernetes/kubernetes/pull/23843), [@cjcullen](https://github.com/cjcullen))
* AWS kube-up: tolerate a lack of ephemeral volumes ([#23776](https://github.com/kubernetes/kubernetes/pull/23776), [@justinsb](https://github.com/justinsb))
* Fix so setup-files don't recreate/invalidate certificates that already exist ([#23550](https://github.com/kubernetes/kubernetes/pull/23550), [@luxas](https://github.com/luxas))

# v1.2.1

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.1

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.1/kubernetes.tar.gz) | `1639807c5788e1c6b1ab51fd30b723fb5debd865` | `235a1da47972c96a560d718d3256ca4f`

## Changes since v1.2.0

### Other notable changes

* AWS: Fix problems with >2 security groups ([#23340](https://github.com/kubernetes/kubernetes/pull/23340), [@justinsb](https://github.com/justinsb))
* IngressTLS: allow secretName to be blank for SNI routing ([#23500](https://github.com/kubernetes/kubernetes/pull/23500), [@tam7t](https://github.com/tam7t))
* Heapster patch release to 1.0.2 ([#23487](https://github.com/kubernetes/kubernetes/pull/23487), [@piosz](https://github.com/piosz))
* Remove unnecessary override of /etc/init.d/docker on containervm image. ([#23593](https://github.com/kubernetes/kubernetes/pull/23593), [@dchen1107](https://github.com/dchen1107))
* Change kube-proxy & fluentd CPU request to 20m/80m. ([#23646](https://github.com/kubernetes/kubernetes/pull/23646), [@cjcullen](https://github.com/cjcullen))
* make docker-checker more robust ([#23662](https://github.com/kubernetes/kubernetes/pull/23662), [@ArtfulCoder](https://github.com/ArtfulCoder))
* validate that daemonsets don't have empty selectors on creation ([#23530](https://github.com/kubernetes/kubernetes/pull/23530), [@mikedanese](https://github.com/mikedanese))
* don't sync deployment when pod selector is empty ([#23467](https://github.com/kubernetes/kubernetes/pull/23467), [@mikedanese](https://github.com/mikedanese))
* Support differentiation of OS distro in e2e tests ([#23466](https://github.com/kubernetes/kubernetes/pull/23466), [@andyzheng0831](https://github.com/andyzheng0831))
* don't sync daemonsets with selectors that match all pods ([#23223](https://github.com/kubernetes/kubernetes/pull/23223), [@mikedanese](https://github.com/mikedanese))
* Trusty: Avoid reaching GCE custom metadata size limit ([#22818](https://github.com/kubernetes/kubernetes/pull/22818), [@andyzheng0831](https://github.com/andyzheng0831))
* Update kubectl help for 1.2 resources ([#23305](https://github.com/kubernetes/kubernetes/pull/23305), [@janetkuo](https://github.com/janetkuo))
* Removing URL query param from swagger UI to fix the XSS issue ([#23234](https://github.com/kubernetes/kubernetes/pull/23234), [@nikhiljindal](https://github.com/nikhiljindal))
* Fix hairpin mode ([#23325](https://github.com/kubernetes/kubernetes/pull/23325), [@MurgaNikolay](https://github.com/MurgaNikolay))
* Bump to container-vm-v20160321 ([#23313](https://github.com/kubernetes/kubernetes/pull/23313), [@zmerlynn](https://github.com/zmerlynn))
* Remove the restart-kube-proxy and restart-apiserver functions ([#23180](https://github.com/kubernetes/kubernetes/pull/23180), [@roberthbailey](https://github.com/roberthbailey))
* Copy annotations back from RS to Deployment on rollback ([#23160](https://github.com/kubernetes/kubernetes/pull/23160), [@janetkuo](https://github.com/janetkuo))
* Trusty: Support hybrid cluster with nodes on ContainerVM ([#23079](https://github.com/kubernetes/kubernetes/pull/23079), [@andyzheng0831](https://github.com/andyzheng0831))
* update expose command description to add deployment ([#23246](https://github.com/kubernetes/kubernetes/pull/23246), [@AdoHe](https://github.com/AdoHe))
* Add a rate limiter to the GCE cloudprovider ([#23019](https://github.com/kubernetes/kubernetes/pull/23019), [@alex-mohr](https://github.com/alex-mohr))
* Add a Deployment example for kubectl expose. ([#23222](https://github.com/kubernetes/kubernetes/pull/23222), [@madhusudancs](https://github.com/madhusudancs))
* Use versioned object when computing patch ([#23145](https://github.com/kubernetes/kubernetes/pull/23145), [@liggitt](https://github.com/liggitt))
* kubelet: send all recevied pods in one update ([#23141](https://github.com/kubernetes/kubernetes/pull/23141), [@yujuhong](https://github.com/yujuhong))
* Add a SSHKey sync check to the master's healthz (when using SSHTunnels). ([#23167](https://github.com/kubernetes/kubernetes/pull/23167), [@cjcullen](https://github.com/cjcullen))
* Validate minimum CPU limits to be >= 10m ([#23143](https://github.com/kubernetes/kubernetes/pull/23143), [@vishh](https://github.com/vishh))
* Fix controller-manager race condition issue which cause endpoints flush during restart ([#23035](https://github.com/kubernetes/kubernetes/pull/23035), [@xinxiaogang](https://github.com/xinxiaogang))
* MESOS: forward globally declared cadvisor housekeeping flags ([#22974](https://github.com/kubernetes/kubernetes/pull/22974), [@jdef](https://github.com/jdef))
* Trusty: support developer workflow on base image ([#22960](https://github.com/kubernetes/kubernetes/pull/22960), [@andyzheng0831](https://github.com/andyzheng0831))

# v1.2.0

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.2/examples)

## Downloads for v1.2.0

binary | sha1 hash | md5 hash
------ | --------- | --------
[kubernetes.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.2.0/kubernetes.tar.gz) | `52dd998e1191f464f581a9b87017d70ce0b058d9` | `c0ce9e6150e9d7a19455db82f3318b4c`

## Changes since v1.1.1

### Major Themes

  * <strong>Significant scale improvements</strong>. Increased cluster scale by 400% to 1000 nodes with 30,000 pods per cluster.
Kubelet supports 100 pods per node with 4x reduced system overhead.
  * <strong>Simplified application deployment and management. </strong>
     * Dynamic Configuration (ConfigMap API in the core API group) enables application
configuration to be stored as a Kubernetes API object and pulled dynamically on
container startup, as an alternative to baking in command-line flags when a
container is built.
     * Turnkey Deployments (Deployment API (Beta) in the Extensions API group)
automate deployment and rolling updates of applications, specified
declaratively. It handles versioning, multiple simultaneous rollouts,
aggregating status across all pods, maintaining application availability, and
rollback.
  * <strong>Automated cluster management: </strong>
     * Kubernetes clusters can now span zones within a cloud provider. Pods from a
service will be automatically spread across zones, enabling applications to
tolerate zone failure.
     * Simplified way to run a container on every node (DaemonSet API (Beta) in the
Extensions API group): Kubernetes can schedule a service (such as a logging
agent) that runs one, and only one, pod per node.
     * TLS and L7 support (Ingress API (Beta) in the Extensions API group): Kubernetes
is now easier to integrate into custom networking environments by supporting
TLS for secure communication and L7 http-based traffic routing.
     * Graceful Node Shutdown (aka drain) - The new “kubectl drain” command gracefully
evicts pods from nodes in preparation for disruptive operations like kernel
upgrades or maintenance.
     * Custom Metrics for Autoscaling (HorizontalPodAutoscaler API in the Autoscaling
API group): The Horizontal Pod Autoscaling feature now supports custom metrics
(Alpha), allowing you to specify application-level metrics and thresholds to
trigger scaling up and down the number of pods in your application.
  * <strong>New GUI</strong> (dashboard) allows you to get started quickly and enables the same
functionality found in the CLI as a more approachable and discoverable way of
interacting with the system. Note: the GUI is enabled by default in 1.2 clusters.

<img src="docs/images/newgui.png" width="" alt="Dashboard UI screenshot showing cards that represent applications that run inside a cluster" title="Dashboard UI apps screen">

### Other notable improvements

  * Job was Beta in 1.1 and is GA in 1.2 .
     * <code>apiVersion: batch/v1 </code>is now available.  You now do not need to specify the <code>.spec.selector</code> field — a [unique selector is automatically generated ](http://kubernetes.io/docs/user-guide/jobs/#pod-selector)for you.
     * The previous version, <code>apiVersion: extensions/v1beta1</code>, is still supported.  Even if you roll back to 1.1, the objects created using
the new apiVersion will still be accessible, using the old version.   You can
continue to use your existing JSON and YAML files until you are ready to switch
to <code>batch/v1</code>.  We may remove support for Jobs with  <code>apiVersion: extensions/v1beta1 </code>in 1.3 or 1.4.
  *  HorizontalPodAutoscaler was Beta in 1.1 and is GA in 1.2 .
     * <code>apiVersion: autoscaling/v1 </code>is now available.  Changes in this version are:
        * Field CPUUtilization which was a nested structure CPUTargetUtilization in
HorizontalPodAutoscalerSpec was replaced by TargetCPUUtilizationPercentage
which is an integer.
        * ScaleRef of type SubresourceReference in HorizontalPodAutoscalerSpec which
referred to scale subresource of the resource being scaled was replaced by
ScaleTargetRef which points just to the resource being scaled.
        * In extensions/v1beta1 if CPUUtilization in HorizontalPodAutoscalerSpec was not
specified it was set to 80 by default while in autoscaling/v1 HPA object
without TargetCPUUtilizationPercentage specified is a valid object. Pod
autoscaler controller will apply a default scaling policy in this case which is
equivalent to the previous one but may change in the future.
     * The previous version, <code>apiVersion: extensions/v1beta1</code>, is still supported.  Even if you roll back to 1.1, the objects created using
the new apiVersions will still be accessible, using the old version.  You can
continue to use your existing JSON and YAML files until you are ready to switch
to <code>autoscaling/v1</code>.  We may remove support for HorizontalPodAutoscalers with  <code>apiVersion: extensions/v1beta1 </code>in 1.3 or 1.4.
  * Kube-Proxy now defaults to an iptables-based proxy. If the --proxy-mode flag is
specified while starting kube-proxy (‘userspace’ or ‘iptables’), the flag value
will be respected. If the flag value is not specified, the kube-proxy respects
the Node object annotation: ‘net.beta.kubernetes.io/proxy-mode’. If the
annotation is not specified, then ‘iptables’ mode is the default. If kube-proxy
is unable to start in iptables mode because system requirements are not met
(kernel or iptables versions are insufficient), the kube-proxy will fall-back
to userspace mode. Kube-proxy is much more performant and less
resource-intensive in ‘iptables’ mode.
  * Node stability can be improved by reserving [resources](https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/proposals/node-allocatable.md) for the base operating system using --system-reserved and --kube-reserved Kubelet flags
  * Liveness and readiness probes now support more configuration parameters:
periodSeconds, successThreshold, failureThreshold
  * The new ReplicaSet API (Beta) in the Extensions API group is similar to
ReplicationController, but its [selector](http://kubernetes.io/docs/user-guide/labels/#label-selectors) is more general (supports set-based selector; whereas ReplicationController
only supports equality-based selector).
  * Scale subresource support is now expanded to ReplicaSets along with
ReplicationControllers and Deployments. Scale now supports two different types
of selectors to accommodate both [equality-based selectors](http://kubernetes.io/docs/user-guide/labels/#equality-based-requirement) supported by ReplicationControllers and [set-based selectors](http://kubernetes.io/docs/user-guide/labels/#set-based-requirement) supported by Deployments and ReplicaSets.
  * “kubectl run” now produces Deployments (instead of ReplicationControllers) and
Jobs (instead of Pods) by default.
  * Pods can now consume Secret data in environment variables and inject those
environment variables into a container’s command-line args.
  * Stable version of Heapster which scales up to 1000 nodes: more metrics, reduced
latency, reduced cpu/memory consumption (~4mb per monitored node).
  * Pods now have a security context which allows users to specify:
     * attributes which apply to the whole pod:
        * User ID
        * Whether all containers should be non-root
        * Supplemental Groups
        * FSGroup - a special supplemental group
        * SELinux options
     * If a pod defines an FSGroup, that Pod’s system (emptyDir, secret, configMap,
etc) volumes and block-device volumes will be owned by the FSGroup, and each
container in the pod will run with the FSGroup as a supplemental group
  * Volumes that support SELinux labelling are now automatically relabeled with the
Pod’s SELinux context, if specified
  * A stable client library release\_1\_2 is added. The library is [here](pkg/client/clientset_generated/), and detailed doc is [here](docs/devel/generating-clientset.md#released-clientsets). We will keep the interface of this go client stable.
  * New Azure File Service Volume Plugin enables mounting Microsoft Azure File
Volumes (SMB 2.1 and 3.0) into a Pod. See [example](https://github.com/kubernetes/kubernetes/blob/release-1.2/examples/azure_file/README.md) for details.
  * Logs usage and root filesystem usage of a container, volumes usage of a pod and node disk usage are exposed through Kubelet new metrics API.

### Experimental Features

  * Dynamic Provisioning of PersistentVolumes: Kubernetes previously required all
volumes to be manually provisioned by a cluster administrator before use. With
this feature, volume plugins that support it (GCE PD, AWS EBS, and Cinder) can
automatically provision a PersistentVolume to bind to an unfulfilled
PersistentVolumeClaim.
  * Run multiple schedulers in parallel, e.g. one or more custom schedulers
alongside the default Kubernetes scheduler, using pod annotations to select
among the schedulers for each pod. Documentation is [here](http://kubernetes.io/docs/admin/multiple-schedulers.md), design doc is [here](docs/proposals/multiple-schedulers.md).
  * More expressive node affinity syntax, and support for “soft” node affinity.
Node selectors (to constrain pods to schedule on a subset of nodes) now support
the operators {<code>In, NotIn, Exists, DoesNotExist, Gt, Lt</code>}  instead of just conjunction of exact match on node label values. In
addition, we’ve introduced a new “soft” kind of node selector that is just a
hint to the scheduler; the scheduler will try to satisfy these requests but it
does not guarantee they will be satisfied. Both the “hard” and “soft” variants
of node affinity use the new syntax. Documentation is [here](http://kubernetes.io/docs/user-guide/node-selection/) (see section “Alpha feature in Kubernetes v1.2: Node Affinity“). Design doc is [here](https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/design/nodeaffinity.md).
  * A pod can specify its own Hostname and Subdomain via annotations (<code>pod.beta.kubernetes.io/hostname, pod.beta.kubernetes.io/subdomain)</code>. If the Subdomain matches the name of a [headless service](http://kubernetes.io/docs/user-guide/services/#headless-services) in the same namespace, a DNS A record is also created for the pod’s FQDN. More
details can be found in the [DNS README](https://github.com/kubernetes/kubernetes/blob/release-1.2/cluster/saltbase/salt/kube-dns/README.md#a-records-and-hostname-based-on-pod-annotations---a-beta-feature-in-kubernetes-v12). Changes were introduced in PR [#20688](https://github.com/kubernetes/kubernetes/pull/20688).
  * New SchedulerExtender enables users to implement custom
out-of-(the-scheduler)-process scheduling predicates and priority functions,
for example to schedule pods based on resources that are not directly managed
by Kubernetes. Changes were introduced in PR [#13580](https://github.com/kubernetes/kubernetes/pull/13580). Example configuration and documentation is available [here](docs/design/scheduler_extender.md). This is an alpha feature and may not be supported in its current form at beta
or GA.
  * New Flex Volume Plugin enables users to use out-of-process volume plugins that
are installed to “/usr/libexec/kubernetes/kubelet-plugins/volume/exec/” on
every node, instead of being compiled into the Kubernetes binary. See [example](examples/volumes/flexvolume/README.md) for details.
  * vendor volumes into a pod. It expects vendor drivers are installed in the
volume plugin path on each kubelet node. This is an alpha feature and may
change in future.
  * Kubelet exposes a new Alpha metrics API - /stats/summary in a user friendly format with reduced system overhead. The measurement is done in PR [#22542](https://github.com/kubernetes/kubernetes/pull/22542).

### Action required

  * Docker v1.9.1 is officially recommended. Docker v1.8.3 and Docker v1.10 are
supported. If you are using an older release of Docker, please upgrade. Known
issues with Docker 1.9.1 can be found below.
  * CPU hardcapping will be enabled by default for containers with CPU limit set,
if supported by the kernel. You should either adjust your CPU limit, or set CPU
request only, if you want to avoid hardcapping. If the kernel does not support
CPU Quota, NodeStatus will contain a warning indicating that CPU Limits cannot
be enforced.
  * The following applies only if you use the Go language client (<code>/pkg/client/unversioned</code>) to create Job by defining Go variables of type "<code>k8s.io/kubernetes/pkg/apis/extensions".Job</code>).  We think <strong>this is not common</strong>, so if you are not sure what this means, you probably aren't doing this.  If
you do this, then, at the time you re-vendor the "<code>k8s.io/kubernetes/"</code> code, you will need to set <code>job.Spec.ManualSelector = true</code>, or else set <code>job.Spec.Selector = nil.  </code>Otherwise, the jobs you create may be rejected.  See [Specifying your own pod selector](http://kubernetes.io/docs/user-guide/jobs/#specifying-your-own-pod-selector).
  * Deployment was Alpha in 1.1 (though it had apiVersion extensions/v1beta1) and
was disabled by default. Due to some non-backward-compatible API changes, any
Deployment objects you created in 1.1 won’t work with in the 1.2 release.
     * Before upgrading to 1.2, <strong>delete all Deployment alpha-version resources</strong>, including the Replication Controllers and Pods the Deployment manages. Then
create Deployment Beta resources after upgrading to 1.2. Not deleting the
Deployment objects may cause the deployment controller to mistakenly match
other pods and delete them, due to the selector API change.
     * Client (kubectl) and server versions must match (both 1.1 or both 1.2) for any
Deployment-related operations.
     * Behavior change:
        * Deployment creates ReplicaSets instead of ReplicationControllers.
        * Scale subresource now has a new <code>targetSelector</code> field in its status. This field supports the new set-based selectors supported
by Deployments, but in a serialized format.
     * Spec change:
        * Deployment’s [selector](http://kubernetes.io/docs/user-guide/labels/#label-selectors) is now more general (supports set-based selector; it only supported
equality-based selector in 1.1).
        * .spec.uniqueLabelKey is removed -- users can’t customize unique label key --
and its default value is changed from
“deployment.kubernetes.io/podTemplateHash” to “pod-template-hash”.
        * .spec.strategy.rollingUpdate.minReadySeconds is moved to .spec.minReadySeconds
  * DaemonSet was Alpha in 1.1 (though it had apiVersion extensions/v1beta1) and
was disabled by default. Due to some non-backward-compatible API changes, any
DaemonSet objects you created in 1.1 won’t work with in the 1.2 release.
     * Before upgrading to 1.2, <strong>delete all DaemonSet alpha-version resources</strong>. If you do not want to disrupt the pods, use kubectl delete daemonset <name>
--cascade=false. Then create DaemonSet Beta resources after upgrading to 1.2.
     * Client (kubectl) and server versions must match (both 1.1 or both 1.2) for any
DaemonSet-related operations.
     * Behavior change:
        * DaemonSet pods will be created on nodes with .spec.unschedulable=true and will
not be evicted from nodes whose Ready condition is false.
        * Updates to the pod template are now permitted. To perform a rolling update of a
DaemonSet, update the pod template and then delete its pods one by one; they
will be replaced using the updated template.
     * Spec change:
        * DaemonSet’s [selector](http://kubernetes.io/docs/user-guide/labels/#label-selectors) is now more general (supports set-based selector; it only supported
equality-based selector in 1.1).
  * Running against a secured etcd requires these flags to be passed to
kube-apiserver (instead of --etcd-config):
     * --etcd-certfile, --etcd-keyfile (if using client cert auth)
     * --etcd-cafile (if not using system roots)
  * As part of preparation in 1.2 for adding support for protocol buffers (and the
direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not
correct.
Other client authors should double check that you are sending proper
accept and content type headers, or set no value (in which case JSON is the
default).
An example using curl:
<code>curl -H "Content-Type: application/json" -XPOST -d
'{"apiVersion":"v1","kind":"Namespace","metadata":{"name":"kube-system"}}' "[http://<IP_ADDRESS>:8080/api/v1/namespaces](http://<IP_ADDRESS>:8080/api/v1/namespaces)"</code>
  * The version of InfluxDB is bumped from 0.8 to 0.9 which means storage schema
change. More details [here](https://docs.influxdata.com/influxdb/v0.9/administration/upgrading/).
  * We have renamed “minions” to “nodes”.  If you were specifying NUM\_MINIONS or
MINION\_SIZE to kube-up, you should now specify NUM\_NODES or NODE\_SIZE.

### Known Issues

  * Paused deployments can't be resized and don't clean up old ReplicaSets.
  * Minimum memory limit is 4MB. This is a docker limitation
  * Minimum CPU limits is 10m. This is a Linux Kernel limitation
  * “kubectl rollout undo” (i.e. rollback) will hang on paused deployments, because
paused deployments can’t be rolled back (this is expected), and the command
waits for rollback events to return the result. Users should use “kubectl
rollout resume” to resume a deployment before rolling back.
  * “kubectl edit <list>” will open the editor multiple times, once for each
resource in the list.
  * If you create HPA object using autoscaling/v1 API without specifying
targetCPUUtilizationPercentage and read it using kubectl it will print default
value as specified in extensions/v1beta1 (see details in [#23196](https://github.com/kubernetes/kubernetes/issues/23196)).
  * If a node or kubelet crashes with a volume attached, the volume will remain
attached to that node. If that volume can only be attached to one node at a
time (GCE PDs attached in RW mode, for example), then the volume must be
manually detached before Kubernetes can attach it to other nodes.
  * If a volume is already attached to a node any subsequent attempts to attach it
again (due to kubelet restart, for example) will fail. The volume must either
be manually detached first or the pods referencing it deleted (which would
trigger automatic volume detach).
  * In very large clusters it may happen that a few nodes won’t register in API
server in a given timeframe for whatever reasons (networking issue, machine
failure, etc.). Normally when kube-up script will encounter even one NotReady
node it will fail, even though the cluster most likely will be working. We
added an environmental variable to kube-up ALLOWED\_NOTREADY\_NODES that
defines the number of nodes that if not Ready in time won’t cause kube-up
failure.
  * “kubectl rolling-update” only supports Replication Controllers (it doesn’t
support Replica Sets). It’s recommended to use Deployment 1.2 with “kubectl
rollout” commands instead, if you want to rolling update Replica Sets.
  * When live upgrading Kubelet to 1.2 without draining the pods running on the node,
the containers will be restarted by Kubelet (see details in [#23104](https://github.com/kubernetes/kubernetes/issues/23104)).

#### Docker Known Issues

##### 1.9.1

  * Listing containers can be slow at times which will affect kubelet performance.
More information [here](https://github.com/docker/docker/issues/17720)
  * Docker daemon restarts can fail. Docker checkpoints have to deleted between
restarts. More information [here](https://github.com/kubernetes/kubernetes/issues/20995)
  * Pod IP allocation-related issues. Deleting the docker checkpoint prior to
restarting the daemon alleviates this issue, but hasn’t been verified to
completely eliminate the IP allocation issue. More information [here](https://github.com/kubernetes/kubernetes/issues/21523#issuecomment-191498969)
  * Daemon becomes unresponsive (rarely) due to kernel deadlocks. More information [here](https://github.com/kubernetes/kubernetes/issues/21866#issuecomment-189492391)

### Provider-specific Notes

#### Various

   Core changes:

  * Support for load balancers with source ranges

#### AWS

Core changes:

  * Support for ELBs with complex configurations: better subnet selection with
multiple subnets, and internal ELBs
  * Support for VPCs with private dns names
  * Multiple fixes to EBS volume mounting code for robustness, and to support
mounting the full number of AWS recommended volumes.
  * Multiple fixes to avoid hitting AWS rate limits, and to throttle if we do
  * Support for the EC2 Container Registry (currently in us-east-1 only)

With kube-up:

  * Automatically install updates on boot & reboot
  * Use optimized image based on Jessie by default
  * Add support for Ubuntu Wily
  * Master is configured with automatic restart-on-failure, via CloudWatch
  * Bootstrap reworked to be more similar to GCE; better supports reboots/restarts
  * Use an elastic IP for the master by default
  * Experimental support for node spot instances (set NODE\_SPOT\_PRICE=0.05)

#### GCE

  * Ubuntu Trusty support added

Please see the [Releases Page](https://github.com/kubernetes/kubernetes/releases) for older releases.

repository: kubernetes/kubernetes

gha_language: Go

repo_name: kubernetes/kubernetes


text:
# TokenCoreX

[![Build status](https://travis-ci.org/consenlabs/token-core.svg?branch=dev)](https://travis-ci.org/consenlabs/token-core)
[![Gitter chat](https://badges.gitter.im/gitterHQ/gitter.svg)](https://gitter.im/imtoken-wallet/token-core)

Next generation core inside imToken Wallet.

A cross-platform library that implements crypto wallet functions for blockchains, exporting c interfaces in Protobuf
protocol. This library totally wrote in Rust, and now provides friendly interfaces for the mobile platform including
ReactNative, iOS, and Android.

TokenCoreX welcomes contribution from everyone. See [CONTRIBUTING.md](./CONTRIBUTING.md) for help getting started.
In all communications and contributions, this project follows the [Code of Conduct](./CODE_OF_CONDUCT.md)

## Goals
* Abstration interfaces that provide crypto wallet common logic with multi blockchain support
* Cross platform, on mobile, desktop, server side
* Multi keystore support, with file, HSM, KMS, hardware-wallet

## Packages
* `tcx` wallet interface wrapper
* `tcx-bch` | `tcx-btc-fork` | `tcx-tron` | `tcx-ckb` packages contain particular chain operations
* `tcx-chain` keystore and signer interface
* `tcx-proto` protobuf datastructure definition
* `tcx-constants` blockchain spec definition
* [`tcx-primitive` | `tcx-crypto`] low level component

## Examples
We provide three example applications,

* [ReactNative](examples/RN), full functions including all expose API, and e2e testing
* [iOS](examples/iOSExample)
* [Android](examples/android)

## Test Coverage
We can use [tarpaulin](https://github.com/xd009642/tarpaulin) to know the coverage rate.

The easy way to run coverage test is using docker,

```
docker run --security-opt seccomp=unconfined -v "${PWD}:/volume" xd009642/tarpaulin sh -c "cargo tarpaulin --out Html"
```

After couple minutes, it will generate html report of project root directory named `tarpaulin-report.html`.

## Code Styles
This project is using pre-commit. Please run `cargo clean && cargo test` to install the git pre-commit hooks on you clone.

Every time you will try to commit, pre-commit will run checks on your files to make sure they follow our style standards
and they aren't affected by some simple issues. If the checks fail, pre-commit won't let you commit.

## Read More
* [How to build project](docs/BUILD.md)
* [Crypto keys abstraction design (Chinese)](docs/KEYS.zh.md)
* [Architecture design (Chinese)](docs/TECH.zh.md)
* [How to add more blockchain support](docs/INTEGRATION.md)
* [Security](SECURITY.md) including the bug bounty program
* [FAQ](docs/FAQ.md)

## License
Apache Licence v2.0

repository: consenlabs/token-core

branch_name: refs/heads/dev

extension: md

gha_language: Rust

license_type: permissive

repo_name: consenlabs/token-core


text:
# AoE2-Scripts

Collection of Age of Empires 2 scripts and macros.

## How to use them?

- You can download any of the pre-compiled binaries directly from this repository and use them.

- If you're not okay with running these pre-compiled binaries for security reasons (which is good), you can always take a look at the source code and compile them yourself.

## What do they do?

### [ConvertMonk.au3](ConvertMonk.au3)

Automatically deselect a monk from a group of monks for easy multi conversions.

Check out this [youtube video](http://www.youtube.com/watch?v=F-MIimH9Kz8&t=0m24s) for more details.

- Run `ConvertMonk.exe` and feed the key you would like to use as a macro.
- Run AoE2 and select some units, place your mouse pointer on the first unit and press F10 key, so the script knows where to click at when deselecting a monk.

- You're done.
- Edit the created `ConvertMonk.ini` to change your macro key or coordinates.

### [MacrosCBA.au3](MacrosCBA.au3)

- An easy way to queue army on all buildings of one type. Press F8 and F11 to enable or disable hotkeys.

Ctrl+a - Arbalest

Ctrl+e - Halberdier

Ctrl+v - Paladin

Ctrl+g - Eagle Warrior

Ctrl+r - Skirmisher

Ctrl+c - Camel

Ctrl+b - Huskarl

Ctrl+f - Hand Cannoneer

Ctrl+x - Cavarly Archer

## Disclaimer

Please don't use these scripts in multiplayer to keep the AoE experience pleasant for everyone. These scripts have only been created to show people what can be done to exploit the game.

## License

`The MIT License`

license: MIT

branch_name: refs/heads/master


text:
# Change Log

This project adheres to [Semantic Versioning](https://semver.org/).

## 5.1.0

- Change order rules to be more permissive with modifier-parent selectors.

## 5.0.0

- Support stylelint@14.
- Upgraded all extended configs and plugins to latest versions.
- Use plugin stylelint-order instead of @udyux/stylelint-order seeing as the added feature has been implemented.

## 2.0.0

- Dropped Node.js 6 support. Node.js 8.7.0 or greater is now required.
- Removed stylelint@9 as a peer dependency. stylelint 10 or greater is now required.

repository: udyux/stylelint-config-udyux

gha_language: JavaScript

gha_license_id: MIT

repo_name: udyux/stylelint-config-udyux


text:
# Auto-creating Debezium Change Data Topics Example

## Prerequisites for this example

- Installed Docker and `docker-compose`
- Installed `curl` (and optionally `json_pp`)
- Cloned or downloaded this example

## Usage

You can find the documentation of the Change Data Topics Auto-creation in the Debezium Docs[]

### Start Docker Containers

To spin up some example infrastructure like Kafka, Debezium and a Postgres database you
have to execute from this example directory (`./topic-auto-create` directory):

```bash
$ DEBEZIUM_VERSION=2.1 docker-compose up -d

  Creating network "topic-auto-create_default" with the default driver
  Creating topic-auto-create_zookeeper_1 ... done
  Creating topic-auto-create_postgres_1  ... done
  Creating topic-auto-create_kafka_1     ... done
  Creating topic-auto-create_connect_1   ... done
```

### Connector Config

Then we use the following connector config for a Postgres connector to capture the `inventory`
schema where the default config for topics should be `replication.factor = 1`, `partitions = 5`,
the topic should be key compacted with `cleanup.policy = "compact"`, and all messages should
be forced to GZIP compression on harddisk with `compression.type = "gzip"`.

Some topics of captured tables that have a name starting with `product` should go to topics
that have a retention time of 3 months / 90 days with `cleanup.policy": "delete"` and
`retention.ms =<PHONE_NUMBER>`, `replication.factor = 1`, `partitions = 20`, and just use the
compression format that's chosen by the producer with `compression.type": "producer"`.

```json
{
    "name": "inventory-connector",
    "config": {
        "connector.class": "io.debezium.connector.postgresql.PostgresConnector",
        "tasks.max": 1,
        "database.hostname": "postgres",
        "database.port": 5432,
        "database.user": "postgres",
        "database.password": "postgres",
        "database.dbname" : "postgres",
        "topic.prefix": "dbserver1",
        "schema.include.list": "inventory",

        "topic.creation.default.replication.factor": 1,
        "topic.creation.default.partitions": 5,
        "topic.creation.default.cleanup.policy": "compact",
        "topic.creation.default.compression.type": "gzip",
        "topic.creation.default.delete.retention.ms" :<PHONE_NUMBER>,

        "topic.creation.groups": "productlog",

        "topic.creation.productlog.include": "dbserver1\\.inventory\\.product.*",
        "topic.creation.productlog.replication.factor": 1,
        "topic.creation.productlog.partitions": 10,
        "topic.creation.productlog.cleanup.policy": "delete",
        "topic.creation.productlog.compression.type": "producer",
        "topic.creation.productlog.retention.ms":<PHONE_NUMBER>
    }
}
```

### Sending connector config

```bash
$ curl -X PUT -H "Accept: application/json" -H "Content-Type: application/json" -d @connector.json "http://localhost:8083/connectors/inventory-connector/config" | json_pp

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2154  100  1009  100  1145   1318   1496 --:--:-- --:--:-- --:--:--  2815
{
   "config" : {
      "connector.class" : "io.debezium.connector.postgresql.PostgresConnector",
      "database.dbname" : "postgres",
      "database.hostname" : "postgres",
      "database.password" : "postgres",
      "database.port" : "5432",
      "topic.prefix" : "dbserver1",
      "database.user" : "postgres",
      "name" : "inventory-connector",
      "schema.include.list" : "inventory",
      "tasks.max" : "1",
      "topic.creation.default.cleanup.policy" : "compact",
      "topic.creation.default.compression.type" : "gzip",
      "topic.creation.default.delete.retention.ms" : "2592000000",
      "topic.creation.default.partitions" : "5",
      "topic.creation.default.replication.factor" : "1",
      "topic.creation.groups" : "productlog",
      "topic.creation.productlog.cleanup.policy" : "delete",
      "topic.creation.productlog.compression.type" : "producer",
      "topic.creation.productlog.retention.ms" : "7776000000",
      "topic.creation.productlog.include" : "dbserver1\\.inventory\\.product.*",
      "topic.creation.productlog.partitions" : "10",
      "topic.creation.productlog.replication.factor" : "1"
   },
   "name" : "inventory-connector",
   "tasks" : [],
   "type" : "source"
}
```

### Validating the result

```bash
## Login into the Kafka container
$ docker exec -it topic-auto-create_kafka_1 bash

## Check the orders topic, if the `default` group config was applied
$ /kafka/bin/kafka-topics.sh --bootstrap-server $HOSTNAME:9092 --describe --topic dbserver1.inventory.orders

Topic: dbserver1.inventory.orders       PartitionCount: 5       ReplicationFactor: 1    Configs: compression.type=gzip,cleanup.policy=compact,segment.bytes=1073741824,delete.retention.ms=2592000000

## Check the products topic, if the `productlog` group config was applied
$ /kafka/bin/kafka-topics.sh --bootstrap-server $HOSTNAME:9092 --describe --topic dbserver1.inventory.products

Topic: dbserver1.inventory.products     PartitionCount: 10      ReplicationFactor: 1    Configs: compression.type=producer,cleanup.policy=delete,segment.bytes=1073741824,retention.ms=7776000000
```

### Cleanup

Exit from the docker container back to the example dir then destroy and remove the containers with:

```bash
docker-compose down
```

repository: debezium/debezium-examples

branch_name: refs/heads/main

repo_name: debezium/debezium-examples


text:
---
layout: page
title: Getting started
order: 0
permalink: /getting-started/
---

Corbel platform is very easy to install and configure. You have following options to get corbel:

1. [Download the last release](https://github.com/bq/corbel/releases/)
2. If you use maven, just add the dependency to your pom.xml

gha_language: HTML


text:
# Common Issues

## `NoAvailablePixelFormat`

By far, the most common issue I receive every week is about receiving
`NoAvailablePixelFormat`, it is after all a fairly opaque error.

So what does this error mean? Well, to quote @tomaka:

> Glutin queries the system for the configuration you request (multisampling,
sRGB, depth buffer size, etc.) and if the system doesn't support this
configuration, then `NoAvailablePixelFormat` is returned.

### Debugging on Linux.

On Linux, like on other platforms, debugging this issue is relatively
straightforward. First, we need to know what configs are supported by your
hardware, and what that hardware is. This is trivial, just type the following
into your terminal:

```
$ lspci; glxinfo; glinfo; eglinfo
```

Next, track down what attributes glutin is passing to
`eglChooseConfig`/`glXChooseFBConfig`, and compare that to the attributes of the
configs available.

### Debugging on Windows.

Similar to linux, you are going to want to figure out what attributes glutin is
requesting from `ChoosePixelFormatARB`/`ChoosePixelFormat`/`eglChooseConfig`,
however figuring out what to compare them to is less trivial.

The simplest solution I know of is to download the [OpenGL Extension Viewer by
realtech](http://realtech-vr.com/admin/glview). You can then go to the "Display
modes & pixel formats" tab and take a look at all the configs supported by WGL,
I believe? I'm not what the equivalent for EGL is, unfortunately.

 See:
https://github.com/rust-windowing/glutin/issues/1219

repository: dabreegster/glutin

repo_name: dabreegster/glutin


text:
# myreads-react

![](myreads-react-demo.gif)
I developed this app for [React Nanodegree on Udacity](https://github.com/udacity/reactnd-project-myreads-starter). I used [Create React App](https://github.com/facebookincubator/create-react-app) to bootstrap the project.

* install all project dependencies with `npm install`
* start the development server with `npm start`

## Folder Structure
```bash
├── README.md - This file.
├── SEARCH_TERMS.md # The whitelisted short collection of available search terms for the app to work.
├── package.json
├── public
│   ├── favicon.ico
│   └── index.html
└── src
    ├── App.css
    ├── App.js
    ├── App.test.js
    ├── BooksAPI.js # A JavaScript API for the provided Udacity backend.
    ├── icons
    │   ├── add.svg
    │   ├── arrow-back.svg
    │   └── arrow-drop-down.svg
    ├── index.css
    └── index.js
```

## Backend Server

The backend server is provided by Udacity. The backend API uses a fixed set of cached search results and is limited to a particular set of search terms, which can be found in [SEARCH_TERMS.md](SEARCH_TERMS.md). That list of terms are the _only_ terms that will work with the backend.

repository: zyfsju/myreads-react

repo_name: zyfsju/myreads-react


text:
# BalloonSimulator

BalloonSimulator is a free and open source solution to teaching children K-8 about the relationships of radius to surface area, volume, mass, and vertical (and horizonal if wind is enabled) tension forces. BalloonSimulator includes an in-engine graphing utility and exporting of data to .csv format and screenshots, fully customizible, modular, and simple to use.

This product is fully commented and documented.

- [x] Windows Support
- [x] Mac Support
- [x] Linux Support (will have to build your own archive)

Downloads:
(Windows/Mac)
https://github.com/Class41/BalloonSimulator/tree/master/Builds

Created as part of the FALL UMSL CS4500 2019 semester

gha_language: C#


text:
# code

## Scripts

### `get-members.py`

#### Usage

Prints a list of usernames to stdout.

Usage is `python3 get-members.py [senate|house] [D|R]`.

```shell
$ python3 get-members.py senate D
```


text:
# What have we done in this step

We've Dockerized!

The first step was adding a new npm script, `start`, which can be run to start our app via npm. We've added this as a tiny touch of developer expereince.

Next, we went ahead and created `Dockerfile` and `.dockerignore`. In the dockerfile we've scaffolded out an extremely basic setup:

**Dockerfile:**

- Use the latest Node.js LTS with Alpine Linux
- Create an application directory
- Copy over the `package.json` and `package-lock.json` from the current directory
- Run `npm ci` to install dependencies rapidly
- Copy the dependencies into the app directory
- Run `npm start`

**.dockerignore:**

- Ignore `node_modules`
- Ignore npm's debug file

Next, we'll _need_ to run a command to actually build the Docker image from the `Dockerfile`. To do this, run the following command after replacing `<YOUR_DOCKER_HUB_USERNAME>` with your [Docker Hub](https://hub.docker.com/) username:

```bash
docker build -t <YOUR_DOCKER_HUB_USERNAME>/step-by-step-express .
```

It's worth noting that `<YOUR_DOCKER_HUB_USERNAME>/step-by-step-express` can be any string – this is just the one I've decided to use personally, as it's more easily identifyable. You're not required to include your Docker Hub username nor the repo/project name, but this does seem to be the naming convention the Docker community has standardized on.

From there, we'll want to run the Docker image, publshing (`-p`) port 8080 and running it in detached mode (`-d`). You'll need to have Docker locally installed for this step!

```bash
docker run -p 8080:8080 -d <YOUR_DOCKER_HUB_USERNAME>/step-by-step-express
```

Next, you're going to want to publish this image to Docker Hub – this just requires a few steps:

```bash
docker login # log in with your Docker Hub credentials
```

```bash
docker push <YOUR_DOCKER_HUB_USERNAME>/step-by-step-express # push the image you built to hub.docker.com (the public registry)
```

Now, your app can be consumed on the public internet extremely easily! This is great any host that can deploy from Docker images, like [App Service](https://azure.microsoft.com/services/app-service/?WT.mc_id=stepbystepexpress-github-ticyren).

Additionally, since this step now has a Dockerfile you could even automatically build the Dockerfile on every commit and deploy it to production using something like App Service's [Deployment](https://docs.microsoft.com/azure/devops/pipelines/apps/cd/deploy-docker-webapp?view=azure-devops&WT.mc_id=stepbystepexpress-github-ticyren) functionality or [Azure Pipelines](https://docs.microsoft.com/azure/devops/pipelines/languages/docker?view=azure-devops&tabs=yaml&WT.mc_id=stepbystepexpress-github-ticyren) for ease of use \o/


text:
## Laravel App Engine

*NOTE:* This package is under active development and is not yet posted on packagist

This package modifys and adds functionality to Laravel to get Laravel working on Google App Engine. I hope someday this package is not needed but for the time being is.

### Getting Started

* Install the package
* Comment out the `mcrypt` extension check on line 27-32 of `vendor/laravel/framework/src/Illuminate/Foundation/start.php`
* Comment out the default laravel Encryption service provider in `app/config/app.php` and replace it with `LaravelAppEngine\Encryption\EncryptionServiceProvider'`

### Encryption Service Provider
This is a drop in extension to the Encryption class that changes the implementation to use Open SSL because Mcrypt is not yet support by App Engine. I have filed a [bug report](https://code.google.com/p/googleappengine/issues/detail?id=9332&q=language%3DPHP&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log) which at the time of writing this has been started and well requested. So please star that issue as I do not like changing core functionality of Laravel.

### License
The Laravel framework is open-sourced software licensed under the [MIT license](http://opensource.org/licenses/MIT)

### Author

Alex Rhea
<EMAIL_ADDRESS>

repository: arhea/laravel-appengine

repo_name: arhea/laravel-appengine


text:
### Type of issue

* [ ] Bug in MO4 sniffer rule.
* [ ] Bug in MO4 auto-fixer.
* [ ] Bug in MO4 documentation.
* [ ] Request to extend MO4 sniffer with specific rule.
* [ ] Request to extend MO4 auto-fixer for specific rule.
* [ ] Request to extend MO4 documentation.
* [ ] Other (explain):

### Description

Please describe what issue you're experiencing or what you want
to change. Please don't forget add additional information such as
steps to reproduce!

### Technical details

* PHP version:
* PHPCS version:
* MO4 version:
* OS:

gha_language: PHP


text:
# LaraOutPress (Laravel Output Press)
This is simply compress your final out of Larvel Application and serve to the browser.

### How to install

~~~bash
	composer require vrkansagara/lara-out-press
~~~

### How to activate this compression middleware in your application

Add the ServiceProvider to the providers array in `config/app.php`

```php
 Vrkansagara\LaraOutPress\ServiceProvider::class,
```

Copy the package config to your local config with the publish command:

```shell
php artisan vendor:publish --provider="Vrkansagara\LaraOutPress\ServiceProvider"
```

Enable on single environment `.env`

~~~bash
      VRKANSAGARA_COMPRESS_ENVIRONMENT='${APP_ENV}'
~~~

Enable on multiple environment `.env`

~~~bash
      VRKANSAGARA_COMPRESS_ENVIRONMENT='prod,testing,dev,local'
~~~

Enable this compressor  by placing bellow code in `.env` file.

~~~bash
    VRKANSAGARA_COMPRESS_ENABLED = true
~~~

### Display usage on each page.

Set ` $debug = 1; ` in ` AfterMiddleware.php `

### TO Do List

- [x] Compress browser output.
- [x] Add middleware key in configuration.
- [x] Remove `env()` function usage in run time.
- [] Combine all CSS
- [] Combine all JavaScript files.
- [] Compress using varis algorithms.
- [] Versioning the compressed file.
- [] Except route(s),middleware,group,prefix

### Task

- [x] Add analytics before compress and after compress.
- [x] Migrate code to laravel package format.

### Code Assumption
This code is developed with the mind set of each request is filtered by this middleware. So most of the code will not be flexi.

Improvement and suggestion are always welcome.

repository: cygnet-vrkansagara/LaraOutPress

repo_name: cygnet-vrkansagara/LaraOutPress


text:
# Goal

Create a minigame that creates a character and completes a few puzzles in order to level up a created character.

The actual learning outcomes I hope to achieve is the ability to fletch out a side project in this format. Once the front-end pieces fit together, I plan to expand the project into something I'll add a backend to.

# Roadmap

[x] - set up environment
[x] - set up create a character
[x] - figure out levelling system
[x] - set up a blog / logging location for me.
[x] - add routing
[x] - split pages
[x] - create registration
[x] - create delete account
[x] - create log in
[x] - create log out
[x] - persist sessions (challenge on codesandbox)
[x] - delete character system
[x] - List of all characters
[ ] - Create a class stat system (refactor characters)
[ ] - create a battlefield
[ ] - create AI
[ ] - create levelling system
[ ] - create weakness triangle
[ ] - turn based combat
[ ] - styling
[ ] - expand roadmap

repository: CodeColde/electron-turn-based-game

gha_language: TypeScript

repo_name: CodeColde/electron-turn-based-game


text:
# Kin node.js server and Unity app in 10 minutes
### Heroku ready Implementation of the [Kin SDK for Node.js](https://github.com/kinecosystem/kin-sdk-node)

If you follow the steps below, you should have a running Kin app (client and server) in 10-15 minutes. (A more detailed tutorial can be found [here](https://medium.com/kinblog/building-a-kin-powered-app-with-unity-cf8deef56bdb) but this code has the latest updates)
## I. Server set up
1. Create a new app on [Heroku](https://dashboard.heroku.com/apps) and provision (add) [redis cloud](https://elements.heroku.com/addons/rediscloud). (To use redis, you will need a credit card to authenticate your identity, but the service is free)
2. Under *settings* add the following config vars:

    a). appID - random alphanumeric 4 character string

    b). PRIVATE_KEY - Generate a keypair [here](https://laboratory.kin.org/index.html#account-creator?network=public) and paste the secret provided

    c). SALT - random string. (Generate a new keypair and use the secret for the salt)

3. Take the *public* key you generated in step 2(b), and paste it on the friendbot and fund it with free test kin.
4. Clone this repository on your desktop, and push it to your heroku app.
5. On heroku, click the *resources* tab for your app and make sure **both** worker and web dynos are on.

#### Finally
Find your app's url from the *settings* tab and access it with the following variable:
```javascript
?createChannels=true
```
e.g.
https://my-server.herokuapp.com?createChannels=true

This is a one time function you run, to create [channels](https://docs.kin.org/nodejs/sdk#channels) for your account. You can re-run this function if you change your private key and/ or salt (or if you change from Test to Production environments). If everything went well, your server should have given you the 'OK' sign.

### Usage
Simply call the server with GET/POST to perform the following functions:
1. Fund a new account (create it on the blockchain)

    GET: fund = 1

   POST: address, memo, amount

2. Send a payment to an account

   GET: request = 1

   POST: address, id, memo, amount

3. Whitelist a transaction for the client

   GET: whitelist = 1

   POST: address, id, memo, amount

#### Variables
1. **address:** The blockchain address you wish to make a payment to
2. **memo:** Memo to add to your transaction
3. **amount:** Amount to send for your transaction
4. **id:** A unique id for your client (optional)

## II. Client set up
1. Download this [sample app](https://github.com/hitwill/kin-sdk-unity-tutorial) and open with Unity.
2. Open *Assets/Scripts/Tutorial.cs* and in *Start()* update the following variables:
```csharp
 void Start()
    {
        string url = "https://mykin-server.com"; //url to your server
        string serverAddress = "GAFWC...VLIZZ"; //*public* key from step 2(b) in server set up
    }
```
3. Compile and run on an **android device** or emulator. The SDK will not work running on the editor.

## Porting to your client
The client code all sits in *Assets/Scripts/KinWrapper.cs*. You can copy that file and attach it to an empty object in the first scene of your app or game. All the details of how the code works can be found in the tutorial linked at the start.

repository: hitwill/kin-nodejs-server

repo_name: hitwill/kin-nodejs-server


text:
# RBHUD

[![Version](https://img.shields.io/badge/version-0.0.3-green.svg?style=flat)](http://cocoapods.org/pods/RBHUD)
[![License](https://img.shields.io/badge/license-MIT-blue.svg?style=flat)](http://cocoapods.org/pods/RBHUD)
[![Platform](http://img.shields.io/badge/iOS-8.3%2B-blue.svg?style=flat)]()
[![Language](http://img.shields.io/badge/Swift-2.2-orange.svg?style=flat)]()

HUD written in **Swift** - Ready to use, no muss, no fuss...

![RBHUD written in Swift](https://github.com/robertBojor/RBHUD/blob/master/hud_gif.gif)

## How To
### Install it using CocoaPods

```
use_frameworks!
pod "RBHUD", :git => "https://github.com/robertBojor/RBHUD.git", :tag => "0.0.3"
```

After running `pod update`, and opening the workspace file, you will need add the framework in the **Linked Frameworks and Libraries** and also under the **Build Phases > Link Binary With Libraries**. Once correctly linked, just build once to make sure it works, and you did everything correctly.

All you'll need now is to `import RBHUD` in the classes where you want to use it - That's it!

### Install it manually
Download the archived repo, unzip it on your drive somewhere and just drag the RBHUD.swift file into your project and start using it - That's it!

### Use it in your project
- Declare a variable in your ViewController
```
let hud = RBHUD.sharedInstance
```
- Configure the HUD using any of the 15 available options. Ommitting any of the configuration variables will make the HUD load the defaults ( the actual values seen below )
```
self.hud.backdropOpacity = 0.8    // The opacity of the background
self.hud.backdropUsesBlur = true    // Option for the background if it should use a blur effect or not
self.hud.backdropBlurStyle = UIBlurEffectStyle.Dark   // The blur style, if it's using a blue effect
self.hud.backdropColor = UIColor(red:0.23, green:0.26, blue:0.29, alpha:1)    // The background color of the overlay, if not using a blur effect

self.hud.progressViewLineWidth = 1.0    // The progress indicator line width
self.hud.progressViewSize = 64.0   // The progress indicator's size on the screen
self.hud.progressViewPadding = 10.0   // The top and bottom padding between the progress indicator and any other elements on the screen
self.hud.progressViewStrokeColor = UIColor.whiteColor()   // The color of the progress view stroke line
self.hud.progressViewFillColor = UIColor.clearColor()   // The fill color of the progress view

self.hud.successViewLineWidth = 1.0     // The line width for the success mark
self.hud.successViewStrokeColor = UIColor.greenColor()      // The line color for the success mark

self.hud.errorViewLineWidth = 1.0       // The line width for the error mark
self.hud.errorViewStrokeColor = UIColor.redColor()      // The line color for the error mark

self.hud.labelAnimationDistance = 50.0    // The distance the text labels have to travel when appearing
self.hud.labelFontName = "HelveticaNeue-Light"    // The font name for the text labels
self.hud.labelTitleFontSize = 20.0    // The font size for the title label
self.hud.labelTitleTextColor = UIColor.whiteColor()   // The text color of the title label

self.hud.labelSubtitleFontSize = 13.0   // The font size for the subtitle label
self.hud.labelSubtitleTextColor = UIColor.whiteColor()    // The text color for the subtitle label
```

- Call the show method
```
self.hud.showLoader(inView:UIView!, withTitle:String?, withSubTitle:String?, withProgress:Bool)
```
The `showLoader` method has 4 parameters, 2 of which are optional:

- `inView:UIView` is the view in which you want the HUD to be shown in, usually `self.view`
- `withTitle:String?` is the text string that will be shown as a title when the loader is presented. When sending this as `nil`, the HUD will not present a title text
- `withSubTitle:String?` is the text string that will be shown as a subtitle when the loader is presented. When sending this as `nil`, the HUD will not present a subtitle text
- `withProgress:Bool` If you want the HUD to present an undeterminate progress indicator, set this to `true`, otherwise set this to `false`

If at any step in your code, you need to update the HUD's look, like for example change the title text and add a progress indicator, you can do so by calling the `showLoader` method again using the new parameters, and the HUD will update itself with the new data while still being presented.

- Call the show with a success mark method
```
self.hud.showWithSuccess(self.view, withTitle: "Success", withSubTitle: "The task ended up successfully!")
```
The `showWithSuccess` method has 3 parameters, 2 of which are optional:

- `inView:UIView` is the view in which you want the HUD to be shown in, usually `self.view`
- `withTitle:String?` is the text string that will be shown as a title when the loader is presented. When sending this as `nil`, the HUD will not present a title text
- `withSubTitle:String?` is the text string that will be shown as a subtitle when the loader is presented. When sending this as `nil`, the HUD will not present a subtitle text

- Call the show with an error mark method
```
self.hud.showWithError(self.view, withTitle: "Oops", withSubTitle: "En error occured!")
```
The `showWithError` method has 3 parameters, 2 of which are optional:

- `inView:UIView` is the view in which you want the HUD to be shown in, usually `self.view`
- `withTitle:String?` is the text string that will be shown as a title when the loader is presented. When sending this as `nil`, the HUD will not present a title text
- `withSubTitle:String?` is the text string that will be shown as a subtitle when the loader is presented. When sending this as `nil`, the HUD will not present a subtitle text

Both `showWithError` and `showWithSuccess` methods are going to close the HUD in a few seconds, so there's no need to call the hide method.

- Call the hide method when you're done with your the long action
```
self.hud.hideLoader()
```

## Usage examples

The standard way of using the HUD will resemble the code below...
```
self.hud.showLoader(self.view, withTitle:"Testing", withSubTitle:nil, withProgress:true)
    dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), { () -> Void in
    // Your longer task code goes here...
    dispatch_async(dispatch_get_main_queue(), { () -> Void in
        self.hud.hideLoader()
    })
})
```

If at any step in your code, you need to update the HUD's look, like for example change the title text and add a progress indicator, you can do so by calling the `showLoader` method again using the new parameters, and the HUD will update itself with the new data while still being presented. For example:
```
func someMethod()
{
    self.hud.showLoader(self.view, withTitle:"Testing", withSubTitle:nil, withProgress:true)
    dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), { () -> Void in
        // Your longer task code goes here...
        if self.thisVar == 0 {
            self.hud.showLoader(self.view, withTitle:"New title", withSubTitle:"and subtitle", withProgress:false)
            self.someOtherMethod()
        }
        dispatch_async(dispatch_get_main_queue(), { () -> Void in
            self.hud.hideLoader()
        })
    })
}

func someOtherMethod()
{
    // Your logic here...
    dispatch_async(dispatch_get_main_queue(), { () -> Void in
        self.hud.hideLoader()
    })
}
```

The Xcode project attached to the repo also contains exmaples of calling and hiding the HUD.

## ToDo

- Add an option for the overlay to partially cover the screen, rounded corners included

## Author

Robert Bojor<EMAIL_ADDRESS>
## License

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

repository: LuizZak/RBHUD

repo_name: LuizZak/RBHUD


text:
# Cocoa Pasteboards

This repository contains implementation of cut, copy and paste operations using pasteboards (NSPasteboard).

[Cocoa macOS Examples](https://github.com/NikolaGrujic91/Cocoa-macOS-Examples)

![image missing](App.png "Application UI")


text:
---
title: 'Vue'
---

It's available as [npm package](https://www.npmjs.com/package/@microlink/vue).

```bash
npm install @microlink/vue --save
```

The Vue bundle is based on the [Vanilla](/docs/sdk/integrations/vanilla) version, but exported as a CommonJS Vue plugin/component.

Since it doesn't include the peer dependencies, you'll need to install those too:

```bash
npm install react react-dom styled-components --save
```

After that, you’re ready to import the Microlink SDK into your Vue project, either globally or on-demand.

#### Globally

###### App.js

```js
import Vue from 'vue'
import Microlink from '@microlink/vue'

Vue.use(Microlink)
```

###### MyComponent.vue

```vue
<template>
  <Microlink url="https://microlink.io" />
</template>
```

#### On-demand

```vue
<template>
  <Microlink url="https://microlink.io" />
</template>

<script>
import { Microlink } from '@microlink/vue'

export default {
  name: 'MyComponent',
  components: { Microlink }
}
</script>
```

Importing the SDK globally allows you to define global API options, this is handy for setting an API key for your whole application.

```js
import Vue from 'vue'
import Microlink from '@microlink/vue'

Vue.use(Microlink, { apiKey: 'MyApiKey' })
```

The Vue integration supports any [Microlink API](/docs/api/getting-started/overview) query parameter, just pass them as props.

```vue
<template>
  <Microlink url="https://www.youtube.com/watch?v=9P6rdqiybaw" size="large" />
</template>
```

<Microlink url='https://www.youtube.com/watch?v=9P6rdqiybaw' size="large" media='video' />

Although it's shipped with default styles, you can customize it using [CSS Classnames](docs/sdk/getting-started/considerations/#css-classnames)

```vue
<template>
  <div id="app">
    <Microlink url="https://www.youtube.com/watch?v=9P6rdqiybaw" />
  </div>
</template>

<style>
#app /deep/ .microlink_card {
  font-family: 'Nitti, "Microsoft YaHei", 微软雅黑, monospace';
  max-width: 100%;
}
</style>
```

<Microlink url='https://www.youtube.com/watch?v=9P6rdqiybaw' media='video' style={{fontFamily: 'Nitti, "Microsoft YaHei", 微软雅黑, monospace', maxWidth: '100%'}} />

repository: microlinkhq/www

repo_name: microlinkhq/www


text:
# TaxRates API

## Rates by Street Address

```shell
curl "https://api.taxrates.avalara.com/address?Line1=435+Ericksen+Ave+NE&City=Bainbridge%20Island&Region=WA&PostalCode=98110" \
  -H "Authorization: AvalaraApiKey meowmeowmeow"
```

```ruby
require 'json'
require 'net/http'
uri = URI("https://api.taxrates.avalara.com/address?Line1=435+Ericksen+Ave+NE&City=Bainbridge%20Island&Region=WA&PostalCode=98110")
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_PEER
result = http.get(uri.request_uri,
    'Authorization' => 'AvalaraApiKey meowmeowmeow')
JSON.parse(result.body)
```

> The above command returns JSON structured like this:

```json
{
   "totalRate":9.500000,
   "rates":[
      {
         "rate":3.00000,
         "name":"SEATTLE",
         "type":"City"
      },
      {
         "rate":6.500000,
         "name":"WASHINGTON",
         "type":"State"
      }
   ]
}
```

### HTTP Request

`GET http://api.taxrates.avalara.com/address?<address>`

### Query Parameters

| Parameter | Required | Description                                                  | Example            |
|---------|----------|----------|--------------------------------------------------------------|
| street  | Required | first line of the address           | "1101 Alaskan Way" |
| city  | Optional  | city of the address                 | "Seattle", "Montreal", "Bournemouth" |
| state  | Required | state  or region of the address       | "WA", "QC", "Washington", "Quebec" |
| country | Required | country code in ISO 3166-1 alpha-3 format   | "USA", "CAN", "GBR"      |
| postal | Optional | zip code of the address             | "98101", "V8X 3X4", "BH1 1AA" |

### Response Attributes

Attribute | Type | Description
----------|------|-------
totalRate | double | Contains the total tax rate for the location in question. Note that it is not a percentage; in the example above, the totalRate of 0.086 represents a tax rate of 8.6%.
rates | rate array | Each object in the rates array represents a single jurisdiction's contribution to the totalRate.
rate.rate | double | Note that a rate field may not always be present; in these cases, the contribution is 0.0%.
rate.name | string | TBD
rate.type | string | TBD

## Rates by Zip Code

```shell
curl "https://api.taxrates.avalara.com/address?country=USA&postal=98101" \
  -H "Authorization: AvalaraApiKey meowmeowmeow" \
  -H "Accept: text/json"
```

```ruby
require 'json'
require 'net/http'
uri = URI("https://api.taxrates.avalara.com/address?country=USA&postal=98101")
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_PEER
result = http.get(uri.request_uri,
    'Authorization' => 'AvalaraApiKey meowmeowmeow')
JSON.parse(result.body)
```

> The above command returns JSON structured like this:

```json
{
   "totalRate":9.500000,
   "rates":[
      {
         "rate":3.00000,
         "name":"SEATTLE",
         "type":"City"
      },
      {
         "rate":6.500000,
         "name":"WASHINGTON",
         "type":"State"
      }
   ]
}
```

### HTTP Request

`GET http://api.taxrates.avalara.com/postal?<address>`

### Query Parameters

| Parameter | Required | Description                                                  | Example            |
|---------|----------|----------|--------------------------------------------------------------|
| country | Required | country code in ISO 3166-1 alpha-3 format   | "USA", "CAN", "GBR"      |
| postal | Required | zip code of the address             | "98101", "V8X 3X4", "BH1 1AA" |

### Response Attributes

Attribute | Type | Description
----------|------|-------
totalRate | double | Contains the total tax rate for the location in question. Note that it is not a percentage; in the example above, the totalRate of 0.086 represents a tax rate of 8.6%.
rates | rate array | Each object in the rates array represents a single jurisdiction's contribution to the totalRate.
rate.rate | double | Note that a rate field may not always be present; in these cases, the contribution is 0.0%.
rate.name | string | TBD
rate.type | string | TBD

repository: anyarms/slate

repo_name: anyarms/slate


text:
# Open Source mentorship programs

## What is this?

When I started out with my Open Source journey, I genuinely wish I had resources to help me get started earlier than I did! This project is a compilation of some awesome mentorship programs in the universe of Open Source. It is not an exhaustive compilation & is geared towards tech. However it is not limited to just technical internships & aims to be as extensive as possible via contributions.

## What this is (definitely) not!

I am not affiliated with any of these organizations & am not advertising the programs on their behalf. This is a curation based on my research & amendments/additions will be accepted, if they meet the contributing criteria. Please read the [Contributing Guide]() for more. Additionally, this list doesn't include open source fests/conferences that might host workshops/seminars.

## Contents

- [Technical internships](technical-internships/)
- [Advocacy internships]()
- [Documentation internships](documentation-internships/)
- [STEM internships]()
- [FAQ]()

## Credits/Attribution

As aforementioned, this is a project geared towards helping out folks start their journey in the Open Source world. Most of the content here is curated from my research on getting involved & is envisioned to be maintained/updated via contributions from the community. The licensing details are available in the [LICENSE](https://github.com/divya-mohan0209/FOSS-mentorship-programs/blob/main/LICENSE) file.


text:
## Ona Privacy Policy

We take your privacy seriously. At Ona we collect and manage user data according to the following Privacy Policy.

### Data Collected

We collect anonymous data from every visitor of the Website to monitor traffic and fix bugs.   This includes information on web requests including IP addresses of site visitors, browser type and time of visit.   When registering an account, we ask you to provide certain personal information such as your name and email to create your user profile.  We will not share your personal information with third parties.  Your password, which you will use to access the site, is stored encrypted and thus never accessible to Ona.  Lost passwords can therefore only be reset and not retrieved.

You are able to view, change and remove your data associated with your profile.  If you wish to delete your account please contact us at<EMAIL_ADDRESS>and we will assist you in this request as soon as possible.

Minors and children under the age of 13 should not use any services offered by Ona.  By using the Website, you represent that you are above the age of 13 and have the legal capacity to enter into a binding agreement.

### User Data

We only use your personal information to provide you with Ona services or to communicate with you about our services or the Website.

We take the privacy, confidentiality and security of any data you submit or upload to Ona very seriously, because it is your data.  You retain ownership of the data.   We will never share or access your data, unless granted permission by you, in order to provide you with technical assistance.

In order to comply with the law, we may release account and other personal information to comply on issues related to national security or to protect the rights of Ona and its users.

### Protecting Your Data

Ona is committed to protecting the data you entrust to us.  We employ industry standard best practices (both technical and administrative) to protect against unauthorized access of your data.  We cannot guarantee, however, its absolute security. To protect from loss of data, we do frequent system and incremental backups which are stored encrypted in data centers across different geographic zones.

To further protect your data,  we encourage you never to share your login information and to change your passwords regularly.

If you have any questions regarding our security and backup procedures please contact us at<EMAIL_ADDRESS>
### Changes to the Privacy Policy

We reserve the right to modify this privacy statement at any time, so please review it frequently.  If we make material changes to this policy, we will notify you here or by means of a notice on our homepage so that you are aware of any changes with relation to what information we collect, how we use it, and under what circumstances, if any, we disclose it.

Should you have any questions or concerns about our Privacy Policy please contact us as<EMAIL_ADDRESS>

repository: kobotoolbox/kobocat

gha_language: Python

repo_name: kobotoolbox/kobocat


text:
# :ticketbox

:ticketbox is a fast, minimalistic case/ticket management software. It has many features, some of them are:

 - Create tickets, ticket categories, users, groups, assets, businesses and asset locations.
 - Easy updating the status of tickets, including important information about them
 - View the most necessary information in your dashboard, including charts that distribute ticket activity by week or month, public activity of your agents or the top hot tickets that are pending or in progress right now.
 - View your assets by location (e.g. by floor or building), users by business and other useful stuff.

## Screenshots

![](https://farm9.staticflickr.com/8599/16711063632_cf26837c30_z.jpg)

![](https://farm9.staticflickr.com/8570/16092174483_f8678d44df_z.jpg)

![](https://farm9.staticflickr.com/8647/16525992599_15e4a04177_z.jpg)

![](https://farm9.staticflickr.com/8629/16710833041_fd51e7eeee_z.jpg)

## Requirements

* [Bundler](http://gembundler.com)
* [ImageMagick](http://www.imagemagick.org/script/install-source.php)

## Built With

- [Ruby on Rails](https://github.com/rails/rails) — The backend API is a Rails app.
- [MySQL](http://www.mysql.com/) — Our main database is in MySQL.
- [Semantic UI](http://semantic-ui.com) — We use Semantic UI for the design of the app.

Plus lots of Ruby Gems, a complete list of which is at the *root* folder of the project.

## Instructions

Please don't freak out by the absence of tests. I am currently building my knowledge and soon I will add lots of them.

First create the database:
` rake db:create `

Then create the tables:
 `rake db:schema:load`

## Contributing

:ticketbox is **100% free** and **open-source**. We encourage and support an active, healthy community that
accepts contributions from the public – including you!

We look forward to seeing your pull requests!

## Copyright / License

To be Updated

## Dedication

:ticketbox is built to make us more [productive and happy.]()

repository: iamvazu/ticketbox

repo_name: iamvazu/ticketbox


text:
# $highestServerRole

This function returns the current server's highest role

```javascript
bot.command({
name: "role",
code: `$serverName's Highest Role:
$highestServerRole`
})
```

repository: XzFirzal/documentation

repo_name: XzFirzal/documentation


text:
# Third-Party-programs

Three external tools are needed by WirelessDisplayClientGUI, and like
WirelessDisplayClientGUI itself, they all run on the presentation-computer:

- A VNC-server,
- ffmpeg,
- A tool to mangage screen-resolutions of the local computer.

These three tools are not started directly by WirelessDisplayClientGUI, but
they are started using the scripts in the directory
[Scripts/<Operating-System>]. Have a look at the [README.md] in the directory
[Scripts] for furhter information.

Note: If you plan to use only VNC or only ffmpeg, it is not necessary to
install the other tool, since WirelessDisplayClientGUI does start a script
if you don't start it.

## For Linux

For Linux the [ThirdParty]-folder can remain empty. The scripts in
[Scripts/Linux] use x11vnc, ffmpeg and xrandr. These programs are best
installed with the packagemanager from your Linux-distro.

## For macos

TODO

## For Windows

The programs TightVNC, version 1.3.10
[see here](https://www.tightvnc.com/download/1.3.10/tightvnc-1.3.10_x86.zip),
and ffmpeg
[see here](https://ffmpeg.zeranoe.com/builds/win64/static/ffmpeg-4.2.2-win64-static.zip)
are used as streaming-source by the scripts in [Scripts\Windows]. The ffmpeg
zip-File is about 60MB large. As long as github doesn't complain, I provide a
copy of both zip-files in my repository
[Third-party-tools](https://github.com/lzukw/Third-party-tools).

For managing the local screen-resolution
[ScreenRes](https://github.com/lzukw/ScreenRes) is used. This repository
contains the executable screenres.exe, which depends on ??? Microsoft C++
Runtime 2015 TODO find out real name ???. On most Windows-systems this is
installed. If not you can also download the few .dll-files manually and
place them in the same folder as sreenres.exe.

Download the zip-Files (ffmpeg, tightvnc) to the [ThirdParty]-folder and
extract them.

Clone the screenres-repository or download it as zip and extract it - also
to the [ThirdParty]-folder.

Double-check the paths to the executables. The original sripts (batch-files)
in [Scripts\Windows] look for the three executeables here:

- [..\..\ThirdParty\ffmpeg-4.2.2-win64-static\bin\ffplay.exe]
- [..\..\ThirdParty\tightvnc-1.3.10_x86\vncviewer.exe]
- [..\..\ThirdParty\ScreenRes\screenres.exe]

If the paths are not correct you can either modify the folder-structure in
[ThirdParty] or modify the batch-files in [Scripts\Windows].

repository: lzukw/WirelessDisplayServer

repo_name: lzukw/WirelessDisplayServer


text:
---
title: XNAT Quick Start Guide
description: Getting started with an XNAT deployment step-by-step
draft: false
---

This quick start guide will follow a progression starting from the most basic single instance XNAT deployment
up to a full XNAT service.

Please be aware that this is a guide and not considered a production ready service.

## Prerequisites

* a Kubernetes service. You can use Microk8s on your workstation if you do not have access to a cloud service.
* Kubectl client installed and configured to access your Kubernetes service
* Helm client installed

## What settings can be modified and where?

```bash
helm show values ais/xnat
```

## Just XNAT

Create minimal helm values file `~/values.yaml`

```yaml
---
global:
  postgresql:
    postgresqlPassword: "xnat"
```

```bash
# Setup AIS Helm charts
helm repo add ais https://australian-imaging-service.github.io/charts
helm repo update

# Deploy minimal XNAT
# This command is also used to action changes to the `values.yaml` file
helm upgrade xnat ais/xnat --install --values ~/values.yaml --namespace xnat-demo --create-namespace

# From another terminal you can run the following commnad to watch deployment of resources
watch kubectl -nxnat-demo get all,pv,pvc

# From another terminal run the following command and
# access XNAT web UI from a browser with address `http://localhost:8080`
kubectl -nxnat-demo port-forward service/xnat-xnat-web-0 8080:80
```

Things to watch out for.
* This deployment will utilise the default storage class configured for your Kubernetes service.
  If there is no storage class set as default this deployment will not have any persistent volume(s)
  provisioned and will not complete.
  Out of scope for this document is how to manually create a Persistent Volume and bind to a Persistent Volume Claim.

```bash
kubectl get sc
```
```
NAME                          PROVISIONER            RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
microk8s-hostpath (default)   microk8s.io/hostpath   Delete          Immediate           false                  145d
```
You can see that Microk8s has a default storage class. However if this was not the case or another storage class was to be used the following would need to be added to your `values.yaml` file.

```yaml
---
global:
  postgresql:
    postgresqlPassword: "xnat"
  storageClass: "microk8s-hostpath"
```

You should be seeing something similar to the following

```
$ kubectl -nxnat-demo get all,pvc
NAME                    READY   STATUS    RESTARTS   AGE
pod/xnat-postgresql-0   1/1     Running   30         27d
pod/xnat-xnat-web-0     1/1     Running   30         27d

NAME                               TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
service/xnat-xnat-web-headless     ClusterIP   None             <none>        80/TCP           27d
service/xnat-postgresql-headless   ClusterIP   None             <none>        5432/TCP         27d
service/xnat-postgresql            ClusterIP   <IP_ADDRESS>    <none>        5432/TCP         27d
service/xnat-xnat-web              ClusterIP   <IP_ADDRESS>   <none>        80/TCP           27d
service/xnat-xnat-web-dicom-scp    NodePort    <IP_ADDRESS>   <none>        8104:31002/TCP   27d

NAME                               READY   AGE
statefulset.apps/xnat-postgresql   1/1     27d
statefulset.apps/xnat-xnat-web     1/1     27d

NAME                                             STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
persistentvolumeclaim/xnat-xnat-web-archive      Bound    pvc-81a7308c-fb64-4acd-9a04-f54dbc6e1e0b   1Ti        RWX            microk8s-hostpath   27d
persistentvolumeclaim/xnat-xnat-web-prearchive   Bound    pvc-357f45aa-79af-4958-a3fe-ec3714e6db13   1Ti        RWX            microk8s-hostpath   27d
persistentvolumeclaim/data-xnat-postgresql-0     Bound    pvc-45d917d7-8660-4183-92cb-0e07c59d9fa7   8Gi        RWO            microk8s-hostpath   27d
persistentvolumeclaim/cache-xnat-xnat-web-0      Bound    pvc-f868215d-0962-4e99-95f5-0cf09440525f   10Gi       RWO            microk8s-hostpath   27d
```

repository: Australian-Imaging-Service/charts

gha_language: Smarty

repo_name: Australian-Imaging-Service/charts


text:
## AzureADGetUserInfo - Get user infromation from Azure Active Directory.

##### DLL's to reference
System.Net.Http.dll </br>
Newtonsoft.Json.dll </br>

You'd need to store the API specific information from the portal.

ApplicationId </br>
TenantId </br>
Secret </br>

These fields should be sent when calling the API.

**Access token**      - Access token

**User ID**          - User ID

repository: Ayehu/custom-activities

repo_name: Ayehu/custom-activities


text:
abstract_planning_representation_net
====================================

Abstract Planning Representation Net learns a 3-dimensional abstract representation for a high-dimensional robot motion planning problem which can be used to support classical planners (e.g., A*) through a highly informed heuristic or coarse-to-fine planning.

This repository contains the framework to extend a given high-dimensional planner by such an abstract representation. In detail, it contains methods to
- generate training data for the CNN,
- train the CNN, and
- use the CNN as a planning heuristic.

The software is implemented in C++ and PyTorch, using ROS for communication.

Please see the see the respective paper for further information:
"Learning Abstract Representations for Robot Locomotion Planning in High-dimensional Configuration Spaces" by Tobias Klamt and Sven Behnke.

Generate Training Data
----------------------
See the `src/training_data_generator.cpp` file to specifiy your planning problem:
- In the constructor, specify the parameters for your desired training data.
- According to your robot representation you need to specify the function `TransformAbstractPoseToDetailedPose`.

Start the necessary ros nodes:
```
roslaunch planning_abstraction_net planning_framework.launch
```
In another terminal, trigger the training data generation:
```
rosservice call /planning_abstraction_net/generate_training_data_from_random
```

Train the CNN
-------------
Specify the path to your training data in `scripts/abstraction_learning_training.py` and start the training:
```
python abstraction_learning_training.py
```

Use the CNN as a Planning Heuristic
-----------------------------------
Specify the name of your desired network checkpoint in the function `handle_load_network` in `abstraction_learning_ros_interface.py`.
Start the CNN ROS interface:
```
python abstraction_learning_ros_interface.py
```
In another terminal, trigger checkpoint loading:
```
rosservice call /abstraction_learning_network/load_network
```

In the `src/planner.cpp` make sure to call the `Init()` function as soon as the desired map is available. This triggers precomputation of the abstract representation and only needs to be done once per map.

As soon as a planning goal is set, give this to the heuristic server with `m_heuristic_server.SetGoal()`.
Now, the heuristic server provides you a heuristic to that goal for an arbitrary detailed pose in the map which you get with `m_heuristic_server.GetHeuristic()`.

License
-------
abstract_planning_representation_net is released under BSD-3.

Contact
-------
If you have any questions, mail Tobias Klamt (klamt@ais.uni-bonn.de).