decasia

App.Key.reopen
  ################################################
  ##### Transaction setup handlers
  ################################################

  transactionArray: []

  setupTransaction: ->
    @set 'transactionArray', []

coderberry

Ember.Test.registerAsyncHelper('submitForm',
  function(app, selector, context) {
    var $el = findWithAssert(selector, context);
    Ember.run(function() {
      $el.submit();
    });
  }
);

// Example Usage

jcoglan

// fs_stat :: String -> (Error -> Stat -> ()) -> ()
var fs_stat = _.curry(fs.stat, 2);

// paths :: [String]
var paths = ['file1.txt', 'file2.txt', 'file3.txt'];

// tmp :: [(Error -> Stat -> ()) -> ()]
var tmp = paths.map(oneparam(fs_stat));

// async.parallel :: [(Error -> a -> ()) -> ()] -> (Error -> [a] -> ()) -> ()

belison

Ember.Application.initializer({
  name: 'currentUser',

  initialize: function(container, application) {
    var user,
        store = container.lookup('store:main'),
        attributes = $('meta[name="current-user"]').attr('content');
        
    if (attributes) {
      var serializer = store.serializerFor(App.User);

jcoglan

An ActiveRecord conundrum

I'm going to describe a weird problem I faced when using ActiveRecord today. To protect the innocent, I'm not going to talk about the app I'm actually working on but will instead discuss a hypothetical but isomorphic database design for a clone of the popular blogging platform Tumblr.

Tumblr lets you publish various different sorts of content. We might be tempted to shove all these types in a big STI table, but the types are all quite different from one another and so we give them their own tables.

PetrKaleta

# List of environments and their heroku git remotes (id: 'remote_name')
HEROKU_ENVIRONMENTS = {
  staging: 'staging-remote-name',
  production: 'production-remote-name'
}

namespace :deploy do
  # Create rake tasks to deploy on Heroku environments
  #   $ rake -T deploy
  #   rake deploy:production  # Deploy to production

tomdale

/*
  Example usage:

  import logger from "app/system/logger";
  var LOG = logger.loggerFor("topic"');

  LOG.log({
    event: "data received",
    secondary: {
      resource: "photo",

ptrhvns

Clean Code - Martin
Code Complete - McConnell
Compilers - Aho
Computer Networks (5th Edition) - Tanenbaum
Design Patterns - Gamma, et al
Domain-Driven Design - Evans
Growing Object-Oriented Software, Guided by Tests - Freeman, et al
Introduction to Automata Theory, Languages, and Computation - Hopcroft
Purely Functional Data Structures - Okasaki
Refactoring - Fowler

pond

# This monkey patches the PostgreSQL adapter to use asynchronous
# communication when doing its "SELECT 1" check for is-connection-active.
# One symptom of this problem is stalled processing queues in Sidekiq.
# See also:
#
# https://github.com/rails/rails/issues/12867
#
# At the time of writing we have seen indefinite blocking down in the C
# library's "poll()" method due to the out-of-box Rails code using blocking
# I/O, in multithreaded environments - one thread gets stuck in the I/O and

mojombo

# Run the given block +num+ times and then print out the mean, median, min,
# max, and stddev of the run. For example:
#
# irb> stats(10) { sleep(rand / 100) }
# mean:   5.99ms
# median: 6.76ms
# min:    1.49ms
# max:    9.28ms
# stddev: 2.54ms
def stats(num)