Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| # More Info here: http://unicorn.bogomips.org/Unicorn/OobGC.html | |
| # require 'unicorn/oob_gc' | |
| # GC every two requests that hit /expensive/foo or /more_expensive/foo | |
| # in your app. By default, this will GC once every 5 requests | |
| # for all endpoints in your app | |
| # Example: | |
| # use Unicorn::OobGC, 2, %r{\A/(?:admin/work_items/ast|admin/work_items/lp)} | |
| # Use at least one worker per core if you're on a dedicated server, | |
| # more will usually help for _short_ waits on databases/caches. |
| // Creates a UIColor from a Hex string. | |
| func colorWithHexString (hex:String) -> UIColor { | |
| var cString:String = hex.stringByTrimmingCharactersInSet(NSCharacterSet.whitespaceAndNewlineCharacterSet()).uppercaseString | |
| if (cString.hasPrefix("#")) { | |
| cString = cString.substringFromIndex(1) | |
| } | |
| if (countElements(cString) != 6) { | |
| return UIColor.grayColor() |
| // Barcode.swift | |
| import UIKit; | |
| import AVFoundation; | |
| @objc(BarcodeScanner) | |
| public class BarcodeScanner: UIView, AVCaptureMetadataOutputObjectsDelegate { | |
| let session : AVCaptureSession = AVCaptureSession() | |
| var previewLayer : AVCaptureVideoPreviewLayer! |
http://angular.github.io/protractor/#/api
Note: Most commands return promises, so you only resolve their values through using jasmine expect API or using .then(function()) structure
Based on this post: https://spagettikoodi.wordpress.com/2015/01/14/angular-testing-cheat-sheet/ by @crystoll
browser.get('yoururl'); // Load address, can also use '#yourpage'The issue:
..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.
(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)
touch-action CSS property can be used to disable this behaviour.
touch-action: manipulationThe user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
