| # This is an example of how to use database_cleaner gem and | |
| # RSpec tags to make `after_commit` hook play nice with | |
| # `use_transactional_fixtures`. | |
| # Simply mark the specs that use after_commit with | |
| # `:uses_after_commit` tag. | |
| # ... | |
| require 'database_cleaner' |
| --- /tmp/java/src/configure 2012-07-25 11:34:49.000000000 -0500 | |
| +++ configure 2013-04-21 22:56:40.000000000 -0500 | |
| @@ -1,4 +1,4 @@ | |
| -#! /bin/sh | |
| +#! /bin/bash | |
| # Guess values for system-dependent variables and create Makefiles. | |
| # Generated by GNU Autoconf 2.65. | |
| # | |
| @@ -3252,9 +3252,10 @@ | |
| java_version=`$JAVA -version 2>&1 | sed -n -e 's/^java version[^0-9"]*"\([^"]*\)"/\1/p'` |
| <!-- Include Mixpanel and init before this. --> | |
| <!-- Place at the bottom of your layout (ex: app/views/layouts/application.html.erb) --> | |
| <% if content_for :mixpanel %> | |
| <%= javascript_tag(yield :mixpanel) %> | |
| <% end %> |
| #install instructions at https://newrelic.com/docs/server/server-monitor-installation-ubuntu-and-debian | |
| base: | |
| pkgrepo.managed: | |
| - humanname: Newrelic PPA | |
| - name: deb http://apt.newrelic.com/debian/ newrelic non-free | |
| # - dist: precise | |
| - file: /etc/apt/sources.list.d/newrelic.list | |
| - keyid: 548C16BF | |
| - keyserver: subkeys.pgp.net |
(I guarantee nothing. No warranty I am not responsible blah blah blah. Seems to work great for me so far. Thanks to Tyler Bird who I forked this from.)
This installs a patched ruby 1.9.3-p448 with the railsexpress patchsets: https://github.com/skaes/rvm-patchsets
When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.
So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.
Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?
I'm going to cover three things in this post:
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <!-- iOS 10, macOS Sierra, and friends bring a new logging subsystem that's | |
| supposed to scale from the kernel, up to frameworks, and up to apps. It defaults | |
| to a more regimented, privacy-focused approach that large apps and complex | |
| systems need. | |
| It, along with Activity Tracing introduced in iOS 8 and macOS Yosemite and the | |
| Console app in macOS Sierra, hope to help you graduate from caveman debugging to |
| require "money" | |
| class Decorator < BasicObject | |
| undef_method :== | |
| def initialize(component) | |
| @component = component | |
| end | |
| def method_missing(name, *args, &block) |
| [ | |
| { | |
| "keys": ["ctrl+w"], | |
| "command": "run_multiple", | |
| "args": { | |
| "commands": [ | |
| {"command": "find_under_expand", "args": null, "context": "window"}, | |
| {"command": "show_panel", "args": {"panel": "find"}, "context": "window"} | |
| ] | |
| } |
| # We need this to fix the random timeout error that we were seeing in CI. | |
| # May be related to: http://code.google.com/p/selenium/issues/detail?id=1439 | |
| Capybara.register_driver :selenium_with_long_timeout do |app| | |
| client = Selenium::WebDriver::Remote::Http::Default.new | |
| client.timeout = 120 | |
| Capybara::Driver::Selenium.new(app, :browser => :firefox, :http_client => client) | |
| end | |
| Capybara.javascript_driver = :selenium_with_long_timeout |