kesor

source :rubygems

gem 'json', '= 1.5.4'  # knife/chef 11.0 and 11.20 is broken with json 1.5.5/1.7.7
gem 'vagrant'
gem 'vagrant-hostmaster'

Hydrotoast

class AdversarialSearchAI {
	private PieceType piece;

	public AdversarialSearchAI(PieceType piece) {
		this.piece = piece;
	}

	/**
	 * Returns the best move given the state of the game
	 */

fnichol

MetadataChopper

MetadataChopper.extract('metdata.rb') # => [ "rvm", "0.9.1" ]

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

jtimberman

% vagrant up --no-provision $VAGRANTBOX
% vagrant ssh $VAGRANTBOX
vagrant$ wget -O - http://opscode.com/chef/install.sh | sudo bash
vagrant$ rm /tmp/chef*{rpm,deb}
vagrant$ exit
% vagrant package $VAGRANTBOX
% rm -rf ~/.vagrant.d/boxes/$VAGRANTBOX
% vagrant box add $VAGRANTBOX package.box

sperlic

# -*- coding: utf-8 -*-
"""MyCompany Fabric script.

* Deploy code
* Set up a local development environment

There are two ways to deploy the myrepo code:

1.  :func:`deploy` will do a full virtualenv installation/update and expand a
    tarball of the specified git revision (defaults to HEAD) to a timestamped

krosenvold

           <plugin>
               <groupId>org.apache.maven.plugins</groupId>
               <artifactId>maven-compiler-plugin</artifactId>
               .....
               <dependencies>
                   <dependency>
                       <groupId>org.codehaus.plexus</groupId>
                       <artifactId>plexus-compiler-javac</artifactId>
                       <version>1.8.6</version>
                   </dependency>

jtimberman

#!./bin/knife exec

# A knife exec script to change chef node's name, preserving all the attributes.
#
# Usage: knife exec rename-node.rb old-name new-name
#
# Script retrieves the Node object, changes its 'name' attribute,
# creates new Node object with updated name and rest of attributes
# untouched. Then it deletes old Node and Client objects from
# database, and logs into the server to update it:

chowey

var jade = require('jade'),
    runtime = require('jade/lib/runtime'),
    spawn = require('child_process').spawn,
    fs = require('fs');

function parse(str, filename){
  var options = {filename: filename, compileDebug: true};
  try {
    // Parse
    var parser = new jade.Parser(str, filename, options)

emk

-- This is a Hive program. Hive is an SQL-like language that compiles
-- into Hadoop Map/Reduce jobs. It's very popular among analysts at
-- Facebook, because it allows them to query enormous Hadoop data
-- stores using a language much like SQL.

-- Our logs are stored on the Hadoop Distributed File System, in the
-- directory /logs/randomhacks.net/access.  They're ordinary Apache
-- logs in *.gz format.
--
-- We want to pretend that these gzipped log files are a database table,