00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:08:23  * xyxnechanged nick to Nexxy
00:08:58  * yorickquit (Remote host closed the connection)
00:26:35  * dlmanningquit (Remote host closed the connection)
00:31:06  * ins0mniaquit (Ping timeout: 256 seconds)
00:31:50  * jcrugzzquit (Ping timeout: 246 seconds)
00:32:15  * mikolalysenkoquit (Ping timeout: 276 seconds)
00:49:48  * nicholasfjoined
00:54:20  * nicholasfquit (Ping timeout: 256 seconds)
00:57:52  * stagasjoined
01:07:21  * dominictarrquit (Quit: dominictarr)
01:11:06  * dguttmanquit (Quit: dguttman)
01:15:24  * sveisveijoined
01:20:31  * dominictarrjoined
01:36:04  * thatguydanjoined
01:48:47  * dominictarrquit (Ping timeout: 255 seconds)
02:03:01  * dguttmanjoined
02:41:34  * st_lukejoined
02:50:20  * nicholasfjoined
02:52:12  * fallsemojoined
02:54:42  * nicholasfquit (Ping timeout: 264 seconds)
03:09:16  * kenperkinsquit (Quit: Computer has gone to sleep.)
03:10:56  * fallsemoquit (Quit: Leaving.)
03:22:46  * thatguydanquit (Ping timeout: 256 seconds)
03:25:06  * thatguydanjoined
03:37:57  * st_lukequit (Remote host closed the connection)
04:01:48  * timoxleyjoined
04:21:17  * timoxleyquit (Quit: Computer has gone to sleep.)
04:28:37  * dguttmanquit (Quit: dguttman)
04:36:50  * dguttmanjoined
04:38:30  * mikolalysenkojoined
04:50:51  * nicholasfjoined
04:55:06  * nicholasfquit (Ping timeout: 256 seconds)
05:07:26  * dguttmanquit (Quit: dguttman)
05:14:32  * jcrugzzjoined
05:22:32  * AvianFluquit (Remote host closed the connection)
05:28:01  <guybrush>so i want to implement permissions and thought about putting a perm-hash in every data-object which needs perms, no i wonder how i can solve this efficently with streams
05:28:41  <guybrush>the problem i see is, that i have to get the data first - look at permissions and then pass it along
05:29:58  <guybrush>so i have to buffer at least the whole data in memory for permission-checks
05:30:41  <guybrush>so maybe putting perms into the data-set itself is not so good?
05:31:52  <guybrush>but if i dont put it into every data-object i want to do perms on, i would have to do another backend-query
05:33:04  <guybrush>or maybe just keep the perms in memory since it wouldnt take so much memory anyway
05:35:43  <guybrush>or just use a relational database :p
05:47:11  * mikolalysenkoquit (Ping timeout: 260 seconds)
05:49:44  * st_lukejoined
06:53:03  * mikolalysenkojoined
06:57:56  * mikolalysenkoquit (Ping timeout: 255 seconds)
07:25:37  * shuaibjoined
08:16:14  * shuaibquit (Ping timeout: 252 seconds)
08:17:52  * shuaibjoined
08:20:26  * dominictarrjoined
08:26:56  * shuaibquit (Ping timeout: 252 seconds)
08:30:14  * shuaibjoined
08:34:51  * gozalaquit (Quit: Connection closed for inactivity)
08:36:20  * nicholas_joined
09:01:58  * dominictarrquit (Quit: dominictarr)
09:51:38  * thatguydanquit (Ping timeout: 252 seconds)
09:57:41  * stagasquit (Remote host closed the connection)
10:05:08  * jcrugzzquit (Ping timeout: 256 seconds)
10:06:20  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
10:06:20  <rowbit>/!\ ATTENTION: (default-local) o.jabnoune@... successfully signed up for developer browserling plan ($20). Cash money! /!\
10:31:25  * jcrugzzjoined
10:39:31  * calvinfoquit (Ping timeout: 264 seconds)
10:40:14  * jcrugzzquit (Ping timeout: 255 seconds)
10:56:04  * ins0mniajoined
10:57:24  * calvinfojoined
11:02:57  <rowbit>/!\ ATTENTION: (default-local) n.pellerin@... successfully signed up for developer browserling plan ($20). Cash money! /!\
11:02:57  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
11:32:24  * shuaibquit (Ping timeout: 272 seconds)
11:36:10  * shuaibjoined
12:38:57  * st_lukequit (Remote host closed the connection)
12:46:15  * ins0mniaquit (Ping timeout: 260 seconds)
12:54:29  * fallsemojoined
13:10:08  * AvianFlujoined
13:10:08  * nicholas_quit (Read error: Connection reset by peer)
13:10:32  * nicholas_joined
13:37:24  * kevino80joined
13:43:16  * djcoinjoined
13:44:36  <djcoin>Has someone encoutered issues using dominictarr / JSONStream module ? I got a Int32Array error (has no method slice)
13:44:52  <djcoin>https://github.com/dominictarr/JSONStream/blob/master/index.js#L22
13:45:50  * shuaibquit (Ping timeout: 252 seconds)
13:52:43  * fallsemoquit (Quit: Leaving.)
13:55:07  * tmcwjoined
13:56:44  <djcoin>It would be cool to bypass this if (process.browser) { Int32Array } stuff
13:56:48  <djcoin>composability ...
14:01:38  * jcrugzzjoined
14:05:57  * jcrugzzquit (Ping timeout: 248 seconds)
14:07:43  * shuaibjoined
14:12:31  * fallsemojoined
14:22:45  <Domenic_>You should be able to use typed arrays in both places
14:28:34  * kenperkinsjoined
14:32:45  * mikolalysenkojoined
14:39:16  * nicholas_quit (Read error: Connection reset by peer)
14:39:47  * nicholas_joined
14:49:27  <djcoin>Domenic_: if you have a browser that has typed arrays
14:49:49  <djcoin>In my case, chromium Version 23.0.1271.97 (171054), the slice method is missing
14:49:56  <djcoin>older browser won"t have anything
14:54:55  * dguttmanjoined
15:09:13  * owen1quit (Ping timeout: 245 seconds)
15:15:46  <hij1nx>mbalho: did you see the video about dead fish?
15:46:27  * defunctzombie_zzchanged nick to defunctzombie
15:46:56  * shuaibquit (Ping timeout: 252 seconds)
15:49:15  * shuaibjoined
15:53:57  * owen1joined
15:55:55  * djcoinquit (Quit: WeeChat 0.3.9.2)
15:59:25  * dlmanningjoined
16:02:31  * jcrugzzjoined
16:08:36  * shuaibquit (Ping timeout: 264 seconds)
16:10:27  * shamajoined
16:11:13  * shuaibjoined
16:14:13  * dominictarrjoined
16:18:12  * shuaibquit (Ping timeout: 264 seconds)
16:18:41  * dguttmanquit (Quit: dguttman)
16:22:25  * thl0joined
16:39:29  * thl0quit (Remote host closed the connection)
16:43:14  * nicholas_quit (Read error: Connection reset by peer)
16:43:41  * nicholas_joined
16:43:49  <Domenic_>defunctzombie: just recommended zuul to a coworker, we might see it getting some solid use soon, woo.
16:44:14  <Domenic_>of course it uses a pretty old browserify version, hrm.
16:44:21  <Domenic_>and it's version-locked :-/
16:45:00  <Domenic_>almost feel it would be better of using peerDependencies so it picked up whatever versions you already had installed for browserify and mocha
17:04:28  * dguttmanjoined
17:06:08  * shuaibjoined
17:10:09  * dominictarrquit (Quit: dominictarr)
17:11:38  <defunctzombie>Domenic_: nice
17:11:47  <defunctzombie>Domenic_: I can update the version if needed
17:12:06  <defunctzombie>Domenic_: it shouldn't use peer deps cause it should just work, maybe use peer deps for the mocha stuff
17:12:16  <defunctzombie>but not for browserify, cause that is unrelated
17:12:38  <Domenic_>i guess i'm just wary of slightly different bundling behaviors between real code and tests
17:12:40  <defunctzombie>Domenic_: open an issue on updating the packages and I will remember to do it
17:12:58  <Domenic_>will do
17:13:01  <defunctzombie>Domenic_: probably hard to catch all those cases
17:13:12  <defunctzombie>so we make best effort to just keep what we can up to date
17:14:47  <Domenic_>sure but if it used peer deps it would use whatever bundling behavior your main app used :)
17:15:58  * shuaibquit (Ping timeout: 276 seconds)
17:16:23  <chrisdickinson>Domenic_: i've been using beefy to run my tape tests locally before pushing to ci.testling
17:16:26  <chrisdickinson>which'll use the system browserify, or a local browserify if one is available
17:16:29  <chrisdickinson>(not sure if that helps or not, but just another data point on how folk are running tests with browserify)
17:16:56  <Domenic_>chrisdickinson: good data, yeah. we're using mocha
17:17:08  * chrisdickinsonnods
17:17:30  <defunctzombie>Domenic_: there should be no bundling behavior for tests
17:17:42  <chrisdickinson>at work we're using drive.js (which is patterned after mocha tdd), but will be moving that over to tape (potentially) or mocha itself
17:18:03  <defunctzombie>Domenic_: my test files are just simple TDD style with no "bundling" behavior
17:18:07  * shuaibjoined
17:19:04  <Domenic_>defunctzombie: by bundling i mean browserify bundling...
17:19:22  <defunctzombie>Domenic_: right, but your tests don't do that on their own do they?
17:19:50  <defunctzombie>Domenic_: they are just written as is, and then expect to run correctly in some browser environment
17:20:00  <Domenic_>defunctzombie: no, zuul does it. but in production we browserify with another install, i.e. the one in node_modules/browserify, instead of the one in node_modules/zuul/node_modules/browserify
17:20:13  <defunctzombie>right
17:20:31  <defunctzombie>I get the difference in packaging behavior concern
17:20:39  <defunctzombie>many of the things i test with zuul don't depend on browserify
17:20:43  <defunctzombie>at all
17:20:49  <Domenic_>ah i see
17:21:07  <defunctzombie>they are just little libs or whatnot
17:22:03  * defunctzombiechanged nick to defunctzombie_zz
17:25:24  * shuaibquit (Ping timeout: 264 seconds)
17:42:57  * mikolalysenkoquit (Ping timeout: 245 seconds)
17:52:12  * jxsonjoined
17:58:53  * dlmanningquit (Ping timeout: 256 seconds)
18:06:49  <jez0990>Raynos: don't suppose you have an unmerge module...? e.g. unmerge({a:"a",b:"b"},{a:"a"}) // {b:"b"}
18:06:59  <Raynos>no
18:07:02  <Raynos>also that function
18:07:07  <Raynos>is called
18:07:23  <Raynos>difference
18:07:39  <Raynos>https://github.com/Gozala/interset#difference
18:08:30  <jez0990>ahh yes, ty
18:12:15  <jez0990>Raynos: https://npmjs.org/package/deep-diff I don't need the draining board or scrubbing brush but that should do it for me for now :)
18:12:42  <Raynos>cool :)
18:14:28  * fallsemoquit (Quit: Leaving.)
18:22:04  * dominictarrjoined
18:30:01  * fallsemojoined
18:35:15  * jcrugzzquit (Ping timeout: 252 seconds)
18:35:51  * jcrugzzjoined
18:45:19  * stagasjoined
18:53:36  * isaacs_mobilejoined
19:08:25  * isaacs_mobilequit (Remote host closed the connection)
19:20:14  * paul_irish_changed nick to paul_irish
19:23:48  * isaacs_mobilejoined
19:30:44  * mikolalysenkojoined
19:34:46  * isaacs_mobilequit (Remote host closed the connection)
19:57:27  * mikealjoined
20:17:21  * jxson_joined
20:19:23  * jxsonquit (Ping timeout: 246 seconds)
20:29:20  * nicholas_quit (Read error: Connection reset by peer)
20:29:41  * nicholasfjoined
20:37:14  * st_lukejoined
20:40:14  * stagasquit (Quit: ChatZilla 0.9.90-rdmsoft [XULRunner 1.9.0.17/2009122204])
20:57:08  * mikolalysenkoquit (Ping timeout: 245 seconds)
21:25:00  * mikealquit (Quit: Leaving.)
21:28:52  * st_lukequit (Remote host closed the connection)
21:31:26  * timoxleyjoined
21:32:52  <timoxley>substack any clues on running mocha tests via testling locally?
21:34:15  <rowbit>/!\ GitHub user "timoxley" is supporting Testling with the testling_supporter_10 plan! $10/month. Cash money!
21:34:34  * timoxleypays for the answer to this question
21:49:41  <substack>hooray!
21:49:49  <substack>mocha tests hmmm
21:50:14  <substack>well you could cat the mocha harness part and a setup thing in with the browserify part
21:52:24  <substack>cat node_modules/mocha/mocha.js <(echo "mocha.setup({ ui: 'bdd', reporter: 'tap' });") <(browserify test/*.js) <(echo "mocha.run()")
21:52:32  <substack>| testling
21:52:38  <substack>after you npm install -g testling
21:52:40  <substack>that should work
21:58:19  <timoxley>substack hrm it appears the testling example doesn't work
21:58:21  <timoxley>https://gist.github.com/timoxley/5528564
21:58:42  <timoxley>that's just after a git clone + npm install
21:59:30  <timoxley>of the testing repo
22:00:33  <substack>timoxley: does browserify have errors bundling?
22:00:54  <timoxley>substack doesn't appear to
22:02:51  <timoxley>actually the testling executable seems to not like being invoked
22:03:34  <timoxley>substack just running `testling` on its own, no pipes, gives the first two errors in that gist
22:03:53  <timoxley>node 0.10.5
22:05:59  <substack>it's possible it doesn't work with 0.10 yet
22:06:12  <timoxley>seems to be a bug in browser-launcher
22:06:48  <substack>you can also try opening the bundle file in a browser manually
22:06:59  <substack>it should print everything with console.log
22:07:17  * kevino80quit (Remote host closed the connection)
22:10:06  * elliottc1blechanged nick to elliottcable
22:10:21  <timoxley>substack yep, works in browser
22:10:29  <timoxley>same error on node 0.8.x
22:11:33  * AvianFluquit (Remote host closed the connection)
22:11:50  <timoxley>tried upgrading browser-launcher to 0.3.0. still no good.
22:12:04  <timoxley>weird.
22:13:25  <timoxley>I guess it works on your machine?
22:16:27  <Nexxy>:o
22:22:01  * tmcwquit (Remote host closed the connection)
22:29:09  <timoxley>oh good. the act of adding console logs all through the code made it work.
22:29:16  <timoxley>substack it works now for no reason.
22:37:49  * no9joined
22:40:28  <timoxley>substack is it supposed to close chrome after it's done/run it headlessly?
22:44:50  <substack>strange!
22:45:00  <substack>timoxley: yes, it should
22:47:39  <timoxley>FYI last thing I did before it worked was commenting out all the browsers except chrome in https://github.com/substack/browser-launcher/blob/8df79c4a2fdd103c8d3d8cbdf9ff6bb4f393a7ff/lib/detect.js#L6
22:48:17  <timoxley>substack it seemed to be getting stuck in the "check" on line 59
22:53:02  * mikealjoined
23:27:18  * mikealquit (Quit: Leaving.)
23:27:48  * mikealjoined
23:32:37  * tmcwjoined
23:37:34  * tmcwquit (Ping timeout: 272 seconds)
23:55:50  * jibayjoined
23:56:42  * vitorpachecoquit (Quit: Saindo)