Strava OAuth2 Strategy for OmniAuth

This is the un-official gem for Quiver. It exports Quiver notes to text files.

Ultimate user notification tool for web apps

An automated unpacking tool for *nix, using Ruby 1.9.2

The tool relies on the presence of the command-line tools.

Convenience library without a single monkey-patch.

UnionpaySmart SDK for Ruby

simple extension to Hashie::Mash for non rubyified keys, all keys are converted to camelCase

Collect and package your code into ActiveRecord model, let's easily use

Unreliable helps uncover bugs in Rails apps that rely on ambiguous database ordering. Installing it makes both your app and your test suite more robust.

an opinionated Ruby wrapper for Responsys REST API

unReSTful API client

Capture unseen IP addresses connection attempts and report them to Airbrake

The library for expanding short urls provided by url shortening services

Use the http://unshort.me API to unshort URL from many providers.

The official command line interface for http://unshuffle.me/

Sitemap Consumer

Problem: While Cucumber is an awesome tool, for some kinds of tests it's default behaviour becomes an obstacle. Testing large batches of input against a slow error prone system is the source of much frustration. Cucumber will skip remaining steps on failure or error. This is especially problematic if the test input is a dynamic collection, *(e.g. results of a database query). This is opposed to a static collection testing which is solved by a Scenario Outline. Solution: We need to step putside Cucumber's default pass/fail/error handling. Capture all failures and errors in collections. Log errors and failures. Generate a pass/fail manifest against the test inputs. Do not use this for normal BDD style testing, Cucumber's default behaviour is perfect for that. Public Interface: This is a works in progress so I expect changes as usage reveals more. In your cucumber env.rb Before do |scenario| setup_unstoppable end After do |scenario| print unstoppable_failures(scenario) print unstoppable_errors(scenario) end In a step definition wrap any operation that you do not wish to stop execution like so unstoppable do expect(thing).to be(exected_thing) end This helper method does the following: runs executes the block catches any exception 2a. adds error to errors collection if an error 2b. adds expectation failure to failures collection if error is an RSpec::Expectations::ExpectationNotMetError logs error/failure

Make a proc or lambda unstrict about its arguments.

Leightweight dependency API for your POROs