FileMerge (opendiff) can really come in handy when you need to visually compare merging conflicts. Other times it's just a nice visual way to review your days work.
The following method works by creating a simple bash script (git-diff-cmd.sh) that sets us up with the proper command line arguments for Git to pass off files to FileMerge.
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
| // | |
| // Regular Expression for URL validation | |
| // | |
| // Author: Diego Perini | |
| // Created: 2010/12/05 | |
| // Updated: 2018/09/12 | |
| // License: MIT | |
| // | |
| // Copyright (c) 2010-2018 Diego Perini (http://www.iport.it) | |
| // |
| <!-- Run the application using "mvn jetty:run" --> | |
| <plugin> | |
| <groupId>org.mortbay.jetty</groupId> | |
| <artifactId>maven-jetty-plugin</artifactId> | |
| <version>6.1.9</version> | |
| <configuration> | |
| <scanIntervalSeconds>5</scanIntervalSeconds> | |
| <contextPath>/</contextPath> | |
| <connectors> | |
| <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector"> |
Just install this in your apps like so:
gem 'test-spec-mini', :git => 'git://gist.github.com/1806986.git', :require => 'mini'
| // jQuery no-double-tap-zoom plugin | |
| // Triple-licensed: Public Domain, MIT and WTFPL license - share and enjoy! | |
| (function($) { | |
| var IS_IOS = /iphone|ipad/i.test(navigator.userAgent); | |
| $.fn.nodoubletapzoom = function() { | |
| if (IS_IOS) | |
| $(this).bind('touchstart', function preventZoom(e) { | |
| var t2 = e.timeStamp |
| ;; (require '[clojure.string :as str] '[clojure.java.shell :as shell] '[taoensso.timbre :as timbre]) | |
| (defn with-free-port! | |
| "Attempts to kill any current port-binding process, then repeatedly executes | |
| nullary `bind-port!-fn` (which must return logical true on successful | |
| binding). Returns the function's result when successful, else throws an | |
| exception. *nix only. | |
| This idea courtesy of Feng Shen, Ref. http://goo.gl/kEolu." | |
| [port bind-port!-fn & {:keys [max-attempts sleep-ms] |
| ## Name of the riak node | |
| -name [email protected] | |
| ## Cookie for distributed erlang. All nodes in the same cluster | |
| ## should use the same cookie or they will not be able to communicate. | |
| -setcookie riak | |
| ## Heartbeat management; auto-restarts VM if it dies or becomes unresponsive | |
| ## (Disabled by default..use with caution!) | |
| ##-heart |
| (ns wikiparse.core | |
| (:require [clojure.java.io :as io] | |
| [clojure.data.xml :as xml] | |
| [clojure.zip :refer [xml-zip]] | |
| [clojure.data.zip.xml :refer [xml-> xml1-> text]]) | |
| (:import [ org.apache.commons.compress.compressors.bzip2 BZip2CompressorInputStream]) | |
| (:gen-class :main true)) | |
| (defn bz2-reader | |
| "Returns a streaming Reader for the given compressed BZip2 |
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t
