msarahan

quasiben

from pyspark import SparkContext
from pyspark import SparkConf
import os
import sys

if __name__ == "__main__":

    conf = SparkConf()
    conf.setAppName("version-check")

prayashm

from bokeh.plotting import figure, curdoc
from bokeh.driving import linear
from impact import from_csv, reader

import random

p = figure(plot_width=1000, plot_height=600)
r1 = p.line([], [], color="firebrick", line_width=2)
r2 = p.line([], [], color="limegreen", line_width=2)
r3 = p.line([], [], color="limegreen", line_width=2)

thomasdarimont

import json
import logging

from flask import Flask, g
from flask_oidc import OpenIDConnect
import requests

logging.basicConfig(level=logging.DEBUG)

app = Flask(__name__)

tonykwon

0. create users then hide dnsrun and dnslog users from the login window
    $ sh create-user-group.sh
    $ sudo defaults write /Library/Preferences/com.apple.loginwindow HiddenUsersList -array-add dnsrun dnslog

1. Install daemontools -> http://cr.yp.to/daemontools.html

    $ mkdir /package
    $ cd /package
    $ curl http://cr.yp.to/daemontools/daemontools-0.76.tar.gz -o daemontools-0.76.tar.gz
    $ tar -xvzf daemontools-0.76.tar.gz

mcg1969

Conda proposal: virtual hotfixing via build groups

In this note, I propose a modification to conda and to its implied package specification that will provide, in my view, a solution to a common pitall of the conda ecosystem, and will provide additional performance benefits as well.

Motivation

With conda, as with many package ecosystems, it is often necessary for a package to place version constraints on its dependencies to ensure that they interoperate properly. In practice, such constraints must balance two competing concerns:

• if the constraints are specified too tightly, then packages will often unable to coexist, because their version constraints will conflict. For example, if package A depends on B <2.0, and package C depends on B >2.0, then packages A, B, and C cannot coexist. The tighter the constraints, the more likely this is to happen.
• on the other hand, if the constraints are specifed too loosely, then packages will often break if one of their dependencies ce

kalefranz

#!/usr/bin/env python
import hashlib
import json
import logging
import logging.handlers
import os
import shutil
import sys
import tempfile
import urllib

transitive-bullshit

// NOTE: this adds a filename and line number to winston's output
// Example output: 'info (routes/index.js:34) GET 200 /index'

var winston = require('winston')
var path = require('path')
var PROJECT_ROOT = path.join(__dirname, '..')

var logger = new winston.logger({ ... })

// this allows winston to handle output from express' morgan middleware

kakawait

import sys, os

# The path where you put the only.py file
sys.path.append(os.path.abspath('../sphinx-ext/'))

# Add any Sphinx extension module names here, as strings. They can be extensions
# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
extensions = ['scope']

ragingwind

Backend Architectures

Twitter

ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats

• Introduce Gizzard of Twitter - 트위터의 새로운 분산 관리 라이브러리 Gizzard를 소개합니다.
• The Architecture Twitter Uses to Deal with 150M Active Users, 300K QPS, a 22 MB/S Firehose, and Send Tweets in Under 5 Seconds
• Scaling Twitter: Making Twitter 10000 Percent Faster