| require 'net/http' | |
| require 'uri' | |
| def download(url) | |
| Thread.new do | |
| thread = Thread.current | |
| body = thread[:body] = [] | |
| url = URI.parse url | |
| Net::HTTP.new(url.host, url.port).request_get(url.path) do |response| |
| 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) |
| 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 |
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 1000)| source 'https://rubygems.org' | |
| gem 'sinatra' | |
| gem 'sinatra-contrib', require: 'sinatra/streaming' | |
| group :development do | |
| gem 'thin' | |
| gem 'pry-rails' | |
| end |
Rails flash messages with AJAX requests
| package main | |
| import ( | |
| "flag" | |
| "log" | |
| "net/http" | |
| "os" | |
| ) |
| #!/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 |
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
