lengarvey

The problem

On Ruby 2.2.0dev URI.parse has been changed so that it uses RFC3986. This changes the semantics of URIs in some subtle ways. Probably most importantly it means that square brackets "[", "]" and a few other characters should be percent-encoded, primarily in the query string.

Unfortunately the implementation on ruby-trunk doesn't provide an encoding functionality. I raised a bug explaining this: https://bugs.ruby-lang.org/issues/9990 but here's a quick script to demonstrate the issue:

url = "https://bugs.ruby-lang.org/projects/ruby-trunk/issues?set_filter=1&f[]=status_id&op[status_id]=o"
puts URI.encode(url)
URI.parse(URI.encode(url))

minikomi

package main

import (
	"flag"
	"log"
	"net/http"
	"os"
)

minikomi

• 1 slam dunk lifestyle knife city
• 2 Hydra Island Champion
• 3 Prince Jammy Champion
• 4 What You Talking About (Roska Remix) Redlight
• 5 Bowser's Castle Champion
• 6 Chasing Crazy (Trim remix) BRACKLES feat CHERRI V
• 7 Do You Mind (Crazy Cousins Remix) Paleface feat. Kyla
• 8 Buck n Bury (feat. Juiceman) El-B
• 9 Animal Prints (feat. Okmalumkoolkat) LV
• 10 Basscone Redlight

yaauie

My general thoughts on Resque Next is that it should be more of a protocol and an interface than an end-all-be-all solution for delayed work in Ruby, that it should provide at least one implementation for each of the interfaces, but that it should leave further implementation up to third-parties and separate include-if-you-want-it gems (that may be published to either the resque org or elsewhere).

This includes the dependency on Redis. When a consumer out-grows Redis and needs to use a queueing service that has actual, non-emulated queueing semantics, they shouldn't have to rewrite all of their worker code and start over from

tpope

#!/usr/bin/env ruby
# Install in PATH as foremux

if %w(help --help -h).include?(ARGV.first)
  $stderr.puts <<-help
Usage:
  foremux [PROCESS]

Options:
  -e, [--env=ENV]           # Specify an env file to load, defaults to .env

estahn

if ENV.key?('SELENIUM_REMOTE')
  Capybara.register_driver :selenium do |app|
    require 'selenium-webdriver'
    profile = Selenium::WebDriver::Firefox::Profile.from_name 'default'
    capabilities = Selenium::WebDriver::Remote::Capabilities.firefox(:firefox_profile => profile)
    
    Capybara::Selenium::Driver.new(app, { :browser => :remote, :desired_capabilities => capabilities })
  end
end

kratiahuja

Pre-req

The below guide only applies to addons. If your app is using process.env.EMBER_CLI_FASTBOOT, please create an in-repo addon and follow this guide.

Testing guidelines

When you make the changes to make sure your addons are backward compatible for upcoming FastBoot build changes, make sure to test all the usecases as follows:

1. An app running the current FastBoot double builds. Your app should boot and function correctly in browser and FastBoot.
2. An app running with the proposed FastBoot build changes here. Your app should boot and function correctly in browser and FastBoot.
3. An app having ember-cli-fastboot not installed. Make sure the fastboot initializers or vendor files are not running in browser.

Use cases

linjunpop

Rails flash messages with AJAX requests

original: http://stackoverflow.com/a/10167659/656428

krisleech

require 'sidekiq'
require 'active_job'

ActiveJob::Base.queue_adapter = :sidekiq

class Foo < ActiveJob::Base
  queue_as :default
  
  def perform
    sleep 10

mebens

camera = {}
camera._x = 0
camera._y = 0
camera.scaleX = 1
camera.scaleY = 1
camera.rotation = 0

function camera:set()
  love.graphics.push()
  love.graphics.rotate(-self.rotation)