parlarjb

[translation:info] Compiling c source...
[platform:execute] make  in /var/folders/7+/7+jU+2VeFbq7ekX49vUWQk+++TQ/-Tmp-/usession-default-2/testing_1
[platform:Error] nonfuncnodes_1.c:36271: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36445: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36463: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36487: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36565: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36661: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36667: warning: initialization from incompatible pointer type
[platform:Error] nonfuncnodes_1.c:36781: warning: initialization from incompatible pointer type

parlarjb

[~]$ . ~/Dropbox/virtualenvs/test-ve/bin/activate
(test-ve)[~]$ env
TERM_PROGRAM=Apple_Terminal
PIP_REQUIRE_VIRTUALENV=true
TERM=xterm-color
SHELL=/bin/bash
TMPDIR=/var/folders/Fa/FacyiprjEi0p5Y5+BOWNok+++TM/-Tmp-/
Apple_PubSub_Socket_Render=/tmp/launch-614YNz/Render
TERM_PROGRAM_VERSION=273.1
OLDPWD=/Users/parlarjb/Dropbox/virtualenvs/test-ve/bin

parlarjb

(test-ve)[~]$ ls -lR /Users/parlarjb/Dropbox/virtualenvs/test-ve
total 16
drwxr-xr-x  39 parlarjb  staff  1326  3 Jun 13:21 Lib
drwxr-xr-x  11 parlarjb  staff   374  3 Jun 13:26 bin
drwxr-xr-x   3 parlarjb  staff   102 25 May 16:23 cachedir
lrwxr-xr-x   1 parlarjb  staff    38  3 Jun 13:19 jython.jar -> /Users/parlarjb/jython2.5.2/jython.jar
-rw-r--r--   1 parlarjb  staff  3193  2 Mar 23:11 registry

/Users/parlarjb/Dropbox/virtualenvs/test-ve/Lib:
total 1256

parlarjb

[translation:ERROR] Error:
[translation:ERROR]  Traceback (most recent call last):
[translation:ERROR]    File "translate.py", line 308, in main
[translation:ERROR]     drv.proceed(goals)
[translation:ERROR]    File "/home/oracle/parlarjb/pypy-pypy-release-1.6/pypy/translator/driver.py", line 810, in proceed
[translation:ERROR]     return self._execute(goals, task_skip = self._maybe_skip())
[translation:ERROR]    File "/home/oracle/parlarjb/pypy-pypy-release-1.6/pypy/translator/tool/taskengine.py", line 116, in _execute
[translation:ERROR]     res = self._do(goal, taskcallable, *args, **kwds)
[translation:ERROR]    File "/home/oracle/parlarjb/pypy-pypy-release-1.6/pypy/translator/driver.py", line 286, in _do
[translation:ERROR]     res = func()

parlarjb

test

parlarjb

#!/usr/bin/python

from __future__ import division
import Image
import sys, os
import base64, zlib
import photos, console

class Img(object):
  def __init__(self, mode, size, data):

parlarjb

### Keybase proof

I hereby claim:

  * I am parlarjb on github.
  * I am parlar (https://keybase.io/parlar) on keybase.
  * I have a public key whose fingerprint is F367 757E 8FF5 ED85 DA7E  6C57 8D4A D399 5C37 9F93

To claim this, I am signing this object:

parlarjb

Easy UI Regression Testing with Wraith and TravisCI

Introduction

In the past four years, I've learned the hard way about how painful it can be to try and update a codebase used by a large number of applications. Changes that seem innocent can break a specific use case that wasn't anticipated. Do enough manual regression testing and you will catch the bugs, but it's' costly and time consuming process. When things are costly and time consuming, they usually stop being done.

This is why I focus a lot of my efforts towards build process automation. Computers are fantastic about doing boring, repetitive work and never complaining. If you can get them to do the boring chores for you, you spend more time doing the fun, challenging work.

UI Regression testing is one of those spots where I'm looking for automation scripts to take over. Not only because playing "spot the difference" between your builds is boring, but also because [we're horrible at it](http://en.wikipedia.org/wiki/Chan

parlarjb

At mycloud.rackspace.com, each file inside of a Container has an actions widget. One of the items in the widget is "Edit Headers".

![](https://dl.dropboxusercontent.com/u/2384988/Screen%20Shot%202014-08-29%20at%202.58.28%20PM.png)

The available headers are:

![](https://dl.dropboxusercontent.com/u/2384988/Screen%20Shot%202014-08-29%20at%203.00.05%20PM.png)

Containers themselves also have an actions widget, but that widget does *not* include "Edit Headers".

parlarjb

Git workflow

Introduction

On Cloud Atlas, we switched to a heavily modified version of the “git flow” workflow, based on http://nvie.com/posts/a-successful-git-branching-model/ and https://www.atlassian.com/git/workflows#!workflow-gitflow

The basic premise is this: We run one main branch, develop, and whenever we want to begin preparing for a release, we create a Release_x.y.z branch off of develop. It is these Release_x.y.z branches that get deployed to staging and then production.