00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:01:40  * defunctzombiechanged nick to defunctzombie_zz
00:11:14  <chrisdickinson>woot: http://ci.testling.com/chrisdickinson/cssauron-html
00:15:43  <substack>oh excellent
00:16:03  <substack>except for chrome and the others aren't showing up on the latest commit
00:16:10  * jez0990joined
00:16:11  * jez0990quit (Changing host)
00:16:11  * jez0990joined
00:16:47  <chrisdickinson>haha, yeah, i think it's just getting a bit laggy -- was wondering that myself initially since i hit the browser badge url and all of 'em showed up, then realized "oh duh, it's because i added a commit to change the readme"
00:18:22  <chrisdickinson>so, the preference is to run tape directly, but in my experience with plate / cssauron-html, it's been hard to get debugging information out of the failing tests with vanilla tape
00:18:59  <chrisdickinson>also, it's sort of surprising (coming from other test frameworks) that a failing test doesn't throw an exception -- the test case will keep on chugging until it finishes
00:19:15  <substack>the browsers weren't being killed
00:19:17  <substack>is why
00:19:22  <substack>so they got all backed up
00:19:24  <substack>cleaning up
00:19:33  <chrisdickinson>ah, sorry about that!
00:20:22  <isaacs>mbalho: https://twitter.com/lawnrocket/status/284453438362906624
00:20:50  <substack>ok all cleaned up
00:22:33  <chrisdickinson>(sorry for the exposition, just wanted to maybe add a data point in the "using ci.testling.com" experience, if that helps.)
00:22:52  <substack>it's great!
00:24:05  <chrisdickinson>(for instance, with plate, it's hard to tell where things are going wrong on older browsers: http://ci.testling.com/chrisdickinson/plate)
00:24:36  <chrisdickinson>admittedly, plate's a bit large for a standalone node module.
00:26:00  <chrisdickinson>oof, just got a weird error when trying to rebuild plate, too
00:26:07  <chrisdickinson>"npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/chrisdickinson/repos/66aaf08dfc7d58f744076a55a4388a1157d07ec8.1356654466643/node_modules/testling/node_modules/browserify/test/wrap'"
00:26:14  * fotoveritequit (Remote host closed the connection)
00:28:43  <mbalho>isaacs: :D!
00:31:40  * yorickquit (Changing host)
00:31:41  * yorickjoined
00:53:44  <chrisdickinson>substack: any idea what's going on here: http://ci.testling.com/chrisdickinson/plate ?
00:55:42  * rvagg_quit (Quit: Leaving)
00:56:02  * rvagg_joined
00:57:22  <substack>not sure
00:57:45  <chrisdickinson>i don't think it's anything i changed
01:07:03  <chrisdickinson>substack: next question: how would one go about using https://github.com/substack/node-shimify on the command line?
01:10:30  <substack>just use cat
01:10:54  <substack>cat shim.js <(browserify main.js)
01:10:57  <substack>> bundle.js
01:13:01  <chrisdickinson>ah
01:13:06  <chrisdickinson>-p seems to work too?
01:14:13  * yorickquit (Remote host closed the connection)
01:14:15  <substack>plugins will be completely different in v2.0
01:14:19  <substack>best to not get attached to them
01:14:24  <chrisdickinson>'kk
01:29:24  * jez0990quit (Ping timeout: 248 seconds)
01:31:35  <chrisdickinson>substack: is there a way to tell ci.testling.com that you need shimify?
01:32:08  <chrisdickinson>also, sorry for bugging you so much!
01:33:09  <substack>chrisdickinson: put it in the scripts field
01:33:15  <chrisdickinson>ah, awesome, thanks
01:33:46  <substack>although I think showing a green badge for a browser that needs shims is misleading
01:34:18  <substack>better off not including browsers that need shims at all
01:34:36  <substack>or just inlining the shim functions
01:34:39  <substack>there aren't very many
01:34:49  <substack>isArray, forEach, map, filter
01:34:53  <substack>bind perhaps
01:42:53  <mbalho>substack: https://github.com/maxogden/blocking
01:43:43  <mbalho>substack: you have to click a bit before stuff appears
01:45:06  * fotoveritejoined
01:54:17  <chrisdickinson>substack: so, the problem is that browserify's "events" module uses Array#indexOf
01:54:46  <chrisdickinson>my module goes out of its way not to use that, but tape uses it :|
01:56:42  <chrisdickinson>hilarity abounds: "this.setTimeout = function() { … }", where "this" === "window" is totally okay in IE, all versions. setTimeout = function() { } is broken in IE<=8.
01:56:59  <isaacs>st_luke: why is this not your avatar everywhere? http://www.flickr.com/photos/matthewbergman/8123827845/in/photostream/lightbox/
01:57:22  <chrisdickinson>though, plate appears to be okay most everywhere now: http://ci.testling.com/chrisdickinson/plate
01:58:20  <st_luke>isaacs: it might be too intense
01:58:34  <isaacs>st_luke: NO IT IS PERHAPS INTENSE ENOUGH
01:59:37  <chrisdickinson>also, it appears to have choked. not processing safari at all, nor ie9, nor ff4.
02:00:03  <chrisdickinson>st_luke: is that… mid-tackle?
02:00:43  <st_luke>chrisdickinson: go to the next one in the set
02:01:53  <st_luke>I don't remember what was happening, I think maybe nuno was trying to kiss me. he's portuguese.
02:05:00  <chrisdickinson>mbalho: working on some stuff so that you can `require` your glsl modules and get a JS getter/setter object for uniforms
02:05:02  <chrisdickinson>also, neat!
02:05:34  <chrisdickinson>(ideally it'll work with https://github.com/chrisdickinson/texture.js and friends.)
02:07:01  <st_luke>isaacs: ok updated
02:13:44  <mbalho>chrisdickinson: whoa texture.js is cool, i havent even tried to make webgl work in node, is support pretty good?
02:14:13  <chrisdickinson>mbalho: it's kind of new territory, it seems!
02:14:22  <mbalho>ya i was just looking into it today
02:14:23  <chrisdickinson>mbalho: but i'm working on a few projects to make it better, hopefully!
02:14:33  <chrisdickinson>http://github.com/chrisdickinson/glslify
02:14:33  <mbalho>also there is a webcl spec in progress
02:14:41  <chrisdickinson>i know, i'm super excited about it.
02:14:56  <chrisdickinson>(glslify is basically browserify for glsl)
02:15:25  <chrisdickinson>working on "programify" to generate JS files that export programs with the aforementioned getters/setters for uniforms
02:15:46  <mbalho>whoa
02:16:09  <chrisdickinson>devongovett is working on something that translates glsl to js for non-webgl enabled browsers (something that's kind of on my list too)
02:16:14  * nk109joined
02:16:24  <mbalho>haha
02:16:48  <chrisdickinson>but yeah, it's definitely a space that needs to be filled on npm
02:21:14  <chrisdickinson>mbalho: belatedly, an example program using glslify: http://glsl.heroku.com/e#5174.0
02:28:44  * devaholicquit (Ping timeout: 255 seconds)
02:30:58  <isaacs>st_luke: did you cla?
02:31:04  <isaacs>st_luke: http://nodejs.org/cla.html
02:31:06  <isaacs>st_luke: you can do it onlien
02:31:19  <mbalho>substack: https://github.com/mbostock/topojson/wiki/Specification
02:34:57  <st_luke>isaacs: done
02:35:01  <st_luke>can I print that out and hang it on the wall?
02:36:39  <isaacs>st_luke: no, it's a violation of the cla
02:36:54  <isaacs>st_luke: actually, you're not allowed to use a printer ever again
02:36:59  <isaacs>sry
02:37:41  <isaacs>NO TAKEBACKS!
02:40:08  <isaacs>st_luke: too bad you're not in #libuv or #Node.js
02:40:21  <isaacs>02:42 < MI6> joyent/node: Luke Arduini master * 192192a : Colorize API stabilitity index headers in docs Noted in @shtylman's #389 - http://git.io/7wmCkw
02:40:57  <st_luke>isaacs: I'm in #node.js!
02:55:53  * captain_morganquit (Read error: No route to host)
02:56:27  <fotoverite>I think I might make it my mission to get every nodejs dev to have a avatar taken by me
02:56:32  <fotoverite>Is that possible I wonder.
02:56:38  <fotoverite>Also Colorizer for the win!
03:03:07  * jibayquit (Remote host closed the connection)
03:28:56  <mbalho>i only do hand drawn avatars now
03:29:20  <fotoverite>:/ though I think Substack would be harder now to get.
03:31:13  <substack>isaacs: `npm-search` shows up in the search results but when I try to install it I get npm ERR! 404 'npm-search' is not in the npm registry.
03:31:26  <substack>tj why you gotta unpublish
03:33:00  <rvagg_>I don't think you can ever ask 'why' of tj
03:33:12  <fotoverite>Feel the same about DHH
03:34:45  <substack>unpublishing bad ideas is a bad idea
03:34:56  <substack>the best argument against the bad idea is to implement it well
03:35:35  <fotoverite>what about deprecating bad ideas to a namespace?
03:37:35  <chrisdickinson>http://i.imgur.com/wpESs.png
03:37:40  <chrisdickinson>(woo hand drawn avatars.)
03:38:04  <chrisdickinson>(disclaimer: i live in portland, if that makes the text make any more sense.)
03:38:32  * slaskisjoined
03:40:21  <chrisdickinson>substack: any thoughts re: Array#indexOf being brought in with the events module in tape (through its dependence on the stream builtin module)?
03:42:26  <substack>chrisdickinson: https://github.com/substack/node-browserify/commit/a09aab7f2a6280834ca84765c2ba342ad7fdab2b
03:42:29  <substack>upgrade
03:43:00  <substack>testling-ci is on browserify 1.16.6
03:43:01  <chrisdickinson>ah, cool
03:44:03  <chrisdickinson>hmm
04:03:16  * ralphtheninjaquit (Ping timeout: 260 seconds)
04:26:06  <Raynos>substack: tj unpublished because I asked for the name then didnt do antyhing
04:26:37  <substack>!
04:26:56  <substack>asking for names, how quaint!
04:27:06  <substack>there are so many possible names
04:27:08  <substack>just take one
04:33:38  <chrisdickinson>substack: do you have a library for requestAnimationFrame?
04:39:10  <substack>nope
04:40:24  * rvagg_quit (Ping timeout: 244 seconds)
04:46:25  <jden>fotoverite: my current fb profile pic was taken by you at cascadia
04:46:42  <fotoverite>1 down 500 to go
04:52:15  * defunctzombie_zzchanged nick to defunctzombie
04:53:31  <defunctzombie>Raynos: what name?
04:53:41  <jden>perchance, anyone know whom I should ask about problems running couchdb on ec2?
04:54:42  <mbalho>yea jasonsmith
04:54:51  <mbalho>in #couchdb
04:54:54  <mbalho>or just use iriscouch
04:56:31  <jden>hmm, that would be a good person to ask :) it's his gist I'm having trouble with
04:57:05  <chrisdickinson>substack: :D https://github.com/chrisdickinson/raf
04:58:16  <st_luke>jden: what's the issue?
04:59:27  <jden>st_luke: compiled from source on stock AMI, stuck in a crash loop at startup, and I'm not sure what to make of the erlang stacktrace in the logs
04:59:48  * rvagg_joined
05:01:00  <st_luke>jden: are you running out of memory? are you starting couch with the binary or via an init script? any luck stracing it?
05:01:41  <st_luke>what distro is the ami based on?
05:02:13  <jden>hmmm... memory! I'm running on a micro, this sounds like a promising avenue of inquiry. Amazon's AMIs are based on RHEL
05:02:49  <st_luke>I hate running couch on rhel personally
05:03:27  <jden>any particular hangups?
05:04:00  <st_luke>dependencies
05:04:05  <st_luke>cat /etc/issue
05:04:05  <st_luke>?
05:05:41  <st_luke>but if you're using the iriscouch batteries included script thing then that should be taken care of
05:09:42  <jden>starting from scratch with a fresh instance. let's see if this goes better.
05:10:22  <st_luke>well
05:10:30  <st_luke>doing the same thing over and over again and expecting different results
05:10:48  <jden>that's the trick: doing new things
05:11:22  <st_luke>is there any particular reason you're doing it on rhel?
05:11:57  <st_luke>if you're going to build it again try something new!
05:12:48  <jden>everything at work is on AWS running stock AMIs on EC2. I'm trying to 1) set up stuff that will place nice and 2) learn more about our existing stuff.
05:13:17  <jden>I'm new to sysadmin stuff. Don't tell anyone, but I'm a recovering .Net developer
05:13:56  <fotoverite>why a micro?
05:14:06  <fotoverite>they really have trouble compiling a lot of shit.
05:14:57  <jden>fotoverite: doesn't have to be, I guess. didn't figure I needed anything more
05:15:38  <defunctzombie>jden: don't start with aws
05:15:51  <defunctzombie>aws is very complicated and not a good place to start imho
05:16:01  <defunctzombie>jden: just get a small VPS from linode or rackspace
05:16:03  <defunctzombie>and have at it
05:16:22  <dools>yeah aws is weird
05:17:09  <jden>YCombinator is such a monoculture. you're not truly YC if you're not running AWS and mixpanel :/
05:17:52  <dools>it's a monoculture for more reasons than that :)
05:17:58  <st_luke>my favorite thing about aws is the uptime
05:18:43  <dools>because even though their uptime sucks balls, at least everyone else is down, too?
05:19:16  <jden>no one ever got fired for being down when AWS was down?
05:19:48  <st_luke>actually I don't know why people use aws. there are cheap/reliable VPSs all over the place. maybe I'm biased because I've worked in the industry for so long.
05:19:51  <st_luke>anyway, time to get a taco
05:20:28  <jden>st_luke: AWS gives YC companies multiple tens of thousands of dollars of hosting credits :/
05:23:20  <dools>ah! really
05:23:45  <dools>we have a similar thing at this networking/co-working hub fishburners.org in sydney ... this company called ninefold juices everyone up with $100 credit
05:25:37  <jden>but look at the stock photograph on their website! grafiti! bmx! they're so edgy!
05:26:05  <jden>s/photograph/photography/
05:30:34  <fotoverite>st_luke: what taco truck these days?
05:38:31  <st_luke>I'm not really sure of the name of it, it hangs around n7 late at night
05:38:40  <st_luke>it's pretty cold in ny right now, not a bad time to be unemployed
05:51:45  * devaholicjoined
05:57:18  <defunctzombie>it is only going to get colder
06:01:24  <st_luke>I can stay inside all winter
06:03:49  * slaskisquit (Quit: slaskis)
06:10:47  * AvianFluquit (Remote host closed the connection)
06:23:58  * st_lukequit (Remote host closed the connection)
06:37:47  * stlsaintjoined
06:37:47  * stlsaintquit (Changing host)
06:37:47  * stlsaintjoined
06:42:03  * defunctzombiechanged nick to defunctzombie_zz
08:13:30  * mikealquit (Quit: Leaving.)
08:18:51  * mikealjoined
08:38:40  * mikealquit (Read error: Connection reset by peer)
08:39:23  * mikealjoined
10:53:14  * jibayjoined
11:07:49  * rvagg_quit (Quit: Leaving)
11:14:26  * owen1quit (Ping timeout: 255 seconds)
11:26:38  * owen1joined
11:46:50  * owen1quit (Ping timeout: 255 seconds)
12:02:24  * yorickjoined
12:02:25  * yorickquit (Changing host)
12:02:25  * yorickjoined
12:16:16  * owen1joined
12:37:24  * devaholicquit (Ping timeout: 264 seconds)
13:04:03  * ITproquit (Ping timeout: 276 seconds)
13:04:48  * ITprojoined
13:09:18  * ITproquit (Ping timeout: 245 seconds)
13:10:42  * devaholicjoined
13:14:33  * ITprojoined
13:21:18  * ITproquit (Read error: Connection reset by peer)
13:22:08  * ITprojoined
13:33:01  * ITproquit (Ping timeout: 265 seconds)
13:34:32  * ITprojoined
13:45:48  * ITproquit (Ping timeout: 252 seconds)
13:49:36  * ITprojoined
14:07:40  * devaholicquit (Read error: Operation timed out)
14:07:45  * ITproquit (Ping timeout: 276 seconds)
14:10:15  * ITprojoined
14:41:03  * AvianFlujoined
14:48:08  * devaholicjoined
14:59:25  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
14:59:25  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
15:12:39  * AvianFluquit
15:13:08  * AvianFlujoined
15:34:20  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
15:34:20  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
15:41:04  * AvianFluquit (Quit: Leaving)
15:41:33  * AvianFlujoined
15:41:36  * ranndeerchanged nick to rannmann
15:45:29  <pkrumins>isaacs: is there a way to run npm and force it not to use cache?
16:05:58  * st_lukejoined
16:14:43  * shuaibjoined
16:22:09  * devaholicquit (Ping timeout: 252 seconds)
16:35:42  * defunctzombie_zzchanged nick to defunctzombie
16:53:56  * paul_irish_changed nick to paul_irish
16:56:51  * yorickquit (Remote host closed the connection)
17:05:24  * st_lukequit (Ping timeout: 248 seconds)
17:07:06  * mikealquit (Quit: Leaving.)
17:10:12  * st_lukejoined
17:28:44  * mikealjoined
17:35:29  <isaacs>pkrumins: well, the "cache" is just where it downloads stuff
17:35:38  <isaacs>pkrumins: but you can force it to use a different cache
17:35:46  <isaacs>pkrumins: by doing --cache=/some/other/folder
17:39:55  <pkrumins>oh i see, i'll then just --cache=/home/user/.npm/random_dir
17:40:17  <pkrumins>the problem is cache often gets messed up, and npm doesnt know that, so all subsequent builds who depend on a messed up module will fail
17:42:03  <pkrumins>isaacs: more awesome would be if i could do --cache=none
17:43:33  <fotoverite>++ pkrumins
17:44:52  <isaacs>pkrumins: right, but like i said, it's not JUST a cache. it's a working dir. it's where npm unpacks stuff.
17:45:06  <isaacs>pkrumins: it actually does need that dir to function
17:45:14  <pkrumins>oh
17:45:23  <defunctzombie>isaacs: why not just use /tmp ?
17:45:27  <isaacs>pkrumins: you can do --cache=./foo and then rm -rf foo after the command
17:45:42  <isaacs>defunctzombie: because /tmp is often a very small memmapped volume
17:45:53  <isaacs>defunctzombie: and npm is a lot faster if you DO keep the cache around
17:46:01  <isaacs>because couchdb is great at serving 304s
17:46:02  <defunctzombie>gotcha
17:46:07  <defunctzombie>hahaha
17:47:54  <pkrumins>chrisdickinson, can you try running your test now? i want to see if it works now
18:13:55  <mbalho>someone show this to dominic http://blog.makerbar.com/?p=254
18:14:03  * defunctzombiechanged nick to defunctzombie_zz
19:15:00  * defunctzombie_zzchanged nick to defunctzombie
19:18:52  <chrisdickinson>pkrumins: sorry for the delay, but are you talking about the plate tests?
19:19:46  <pkrumins>yes plate.
19:20:06  <pkrumins>i just checked http://ci.testling.com/chrisdickinson/plate and it seems it's working for the last test
19:20:28  <pkrumins>but it would still be nice if you ran one test
19:20:33  <chrisdickinson>for some reason IE8 didn't report any results. just bumped the version
19:21:01  <chrisdickinson>solved it by removing "testling" and "platoon" from devDeps
19:21:19  <chrisdickinson>thanks for looking into it!
19:21:37  <pkrumins>i made testling-ci not to cache npm module
19:21:38  <pkrumins>i made testling-ci not to cache npm modules
19:21:42  <pkrumins>which i thought was the problem
19:22:01  * chrisdickinsonnods
19:24:36  <pkrumins>not looking good
19:26:00  <chrisdickinson>yeah, weird. so opera 10 reports ok, but it's only running 35 tests, while opera 12 runs 'em all and fails on just one.
19:26:08  <pkrumins>yes just 35
19:26:18  <pkrumins>i'm in the logs right now trying to understand what happened
19:26:41  <pkrumins>i'm seeing just 34 tests in the logs too
19:26:54  <chrisdickinson>hmmm
19:27:04  <pkrumins>but it says 35 in the ui
19:27:35  <chrisdickinson>seems like there's an odd race condition happening somewhere.
19:28:22  <chrisdickinson>i've actually been creating the bundle by hand and running it in IE8 / FF3 / chrome latest directly and they seem to pass all the tests
19:28:27  <chrisdickinson>i should probably re-check that
19:33:01  <chrisdickinson>could it be hitting the "unresponsive script" dialog, maybe?
19:33:23  <chrisdickinson>(my hand-compiled bundle passes on IE8 with 1071 tests)
19:33:41  <chrisdickinson>(there'll be a little variance as a few of them test a random number of iterations.)
19:34:28  <pkrumins>i disabled unresponsive script error in some IEs
19:34:31  <pkrumins>but i now forgot which
19:37:24  <st_luke>hij1nx: nice vines logo
19:41:30  <st_luke>defunctzombie: are you still considering doing that animation library?
19:53:33  <defunctzombie>st_luke: yea, mostly cause I still have not found a good solution to slideup/down :)
20:02:31  * defunctzombiechanged nick to defunctzombie_zz
20:07:49  <st_luke>defunctzombie_zz: ok, I need a slideup animation for my new startup's website
20:07:55  <st_luke>Get Your Ash to Mars
20:08:03  <st_luke>I'm going into the funeral business
20:20:51  <jjjjohnnny>i can
20:20:56  <jjjjohnnny>t stop
20:24:17  * defunctzombie_zzchanged nick to defunctzombie
20:24:41  <defunctzombie>st_luke: wut
20:28:14  <defunctzombie>st_luke: I will get a repo up today and hopefully get a basic version working
20:29:34  <st_luke>defunctzombie: getyourashtomars.com
20:29:36  <st_luke>have to get a website up
20:30:37  * owen1quit (Ping timeout: 265 seconds)
20:32:11  * owen1joined
20:40:28  * owen1quit (Ping timeout: 252 seconds)
20:46:05  * owen1joined
22:09:01  * owen1quit (Ping timeout: 252 seconds)
22:20:08  * owen1joined
22:23:31  * yorickjoined
22:28:44  * ralphtheninjajoined
22:40:45  * stlsaintquit (Ping timeout: 244 seconds)
22:46:32  * owen1quit (Ping timeout: 255 seconds)
22:48:05  * owen1joined
23:06:21  * ralphtheninjaquit (Read error: Operation timed out)
23:09:06  * ralphtheninjajoined
23:25:09  <substack>whoa awesome, testling-ci got a mention in http://www.smashingmagazine.com/2012/12/22/talks-to-help-you-become-a-better-front-end-engineer-in-2013/
23:26:24  * defunctzombiechanged nick to defunctzombie_zz
23:27:41  <st_luke>dope
23:29:26  <st_luke>how the fuck is it friday
23:32:19  * st_lukequit (Remote host closed the connection)
23:44:33  <mbalho>substack: nice
23:56:28  * shuaibquit (Quit: Textual IRC Client: http://www.textualapp.com/)