00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:00:17  <spion>woah npm publish really is much faster now.
00:00:30  <spion>was like "what, thats it?"
00:02:02  * calvinfoquit (Ping timeout: 264 seconds)
00:02:09  <Raynos>:)
00:02:10  <Raynos>SPEED
00:02:12  <Raynos>#winning
00:03:00  * fronxjoined
00:04:30  <st_luke>isaacs: where food?
00:06:13  * kriskowaljoined
00:06:30  <isaacs>st_luke: i dunno, what kina thing you want?
00:07:07  * fronxquit (Ping timeout: 246 seconds)
00:10:15  <st_luke>im not super hungry so i can do whatever
00:10:24  <st_luke>i think it will depend more on whats open
00:10:59  <st_luke>isaacs: want to try xolo?
00:11:25  <isaacs>st_luke: yes, i enjoy xolo.
00:11:36  <isaacs>becasue the sign looks like yolo, but with an extra leg because yolop
00:14:06  <st_luke>one yolop please
00:14:18  <isaacs>st_luke: leaving in 5 minutes
00:16:47  <st_luke>isaacs: ok, same
00:17:41  * st_lukequit (Remote host closed the connection)
00:19:00  <substack>juliangruber: https://github.com/juliangruber/array-filter/pull/1
00:19:21  <substack>and I've got an array-map module up
00:19:29  <substack>array-reduce coming soon
00:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 5]
00:39:02  * timoxleyjoined
00:48:33  * mikolalysenkoquit (Ping timeout: 272 seconds)
00:51:29  * timoxleyquit (Remote host closed the connection)
00:56:11  * mikolalysenkojoined
00:58:18  * calvinfojoined
01:00:13  * timoxleyjoined
01:00:53  * mikolalysenkoquit (Ping timeout: 248 seconds)
01:02:21  * calvinfoquit (Ping timeout: 240 seconds)
01:13:59  * tilgovi_quit (Remote host closed the connection)
01:14:48  * thlorenzquit (Remote host closed the connection)
01:18:38  <groundwater>oh starbucks limited 20 min wifi, let me introduce you to my friend 'ifconfig en0 ether xx:xx:xx:xx:xx:xx'
01:22:50  <yorick>still have to reconnect then
01:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 15]
01:24:14  * thlorenzjoined
01:24:41  * thlorenzquit (Remote host closed the connection)
01:43:40  * DTrejoquit (Remote host closed the connection)
01:44:22  <groundwater>yorick: yah, i should write an npm module to script that part!
01:44:24  * DTrejojoined
01:47:04  * DTrejoquit (Remote host closed the connection)
01:48:23  <robertkowalski>Happy Xmas, Noders!
01:48:27  <robertkowalski>:)
01:48:30  <defunctzombie>bah
01:57:22  <substack>humbugs
01:59:05  * calvinfojoined
02:02:42  <grncdr>that's one thing about being in a nearly abandoned tourist area for the holidays
02:02:54  <grncdr>I have had very little christmas hassle
02:03:35  * calvinfoquit (Ping timeout: 260 seconds)
02:16:13  <jjjohnny_>Raynos: come over if ye dare
02:16:39  <Raynos>What's happening?
02:17:52  * Maciek416quit (Remote host closed the connection)
02:18:52  <Raynos>Jjjohnny_: maybe in a bit.
02:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 9]
02:25:12  * dominictarrjoined
02:28:07  * calvinfojoined
02:30:36  <jjjohnny_>Raynos: hackin n drinkin
02:36:07  * thlorenzjoined
02:37:11  <defunctzombie>I kinda like making mobile apps with stylus and browserify !
02:37:22  <defunctzombie>maybe I will become a mobile developer haha
02:44:11  * timoxleyquit (Ping timeout: 272 seconds)
02:45:47  * yorickquit (Remote host closed the connection)
02:59:07  * kriskowalquit (Quit: kriskowal)
03:00:13  * shamaquit (Remote host closed the connection)
03:11:39  <jesusabdullah>hellote
03:21:13  * st_lukejoined
03:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 23]
03:26:49  * dominictarrquit (Remote host closed the connection)
03:30:42  * shamajoined
03:35:19  * shamaquit (Ping timeout: 252 seconds)
03:52:51  * jcrugzzjoined
03:59:28  * calvinfoquit (Quit: Leaving.)
04:10:13  <rowbit>substack, pkrumins: These encoders are STILL down: 50.57.103.88(dev)
04:16:02  * Maciek416joined
04:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 23]
04:26:08  * mikolalysenkojoined
04:30:04  * calvinfojoined
04:31:54  * shamajoined
04:34:01  * mikolalysenkoquit (Ping timeout: 272 seconds)
04:34:21  * calvinfoquit (Ping timeout: 252 seconds)
04:36:39  * shamaquit (Ping timeout: 260 seconds)
04:47:41  * jcrugzzquit (Ping timeout: 272 seconds)
04:58:09  * Maciek416quit (Remote host closed the connection)
05:05:30  <johnkpaul>arg documentation
05:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 21]
05:30:47  * calvinfojoined
05:30:48  * trevnorrisquit (Ping timeout: 260 seconds)
05:32:36  * shamajoined
05:35:04  * calvinfoquit (Ping timeout: 246 seconds)
05:35:33  * jcrugzzjoined
05:36:01  * trevnorrisjoined
05:36:02  * trevnorrischanged nick to trevnorri
05:36:49  * shamaquit (Ping timeout: 246 seconds)
05:38:47  * thlorenzquit (Remote host closed the connection)
05:40:53  * trevnorriquit (Ping timeout: 248 seconds)
05:44:19  * jcrugzzquit (Ping timeout: 272 seconds)
05:44:45  * trevnorrisjoined
05:46:59  * thlorenzjoined
05:47:06  * thlorenzquit (Remote host closed the connection)
05:47:09  * st_lukequit (Remote host closed the connection)
05:49:27  * trevnorrisquit (Ping timeout: 260 seconds)
05:49:38  * DTrejojoined
05:52:13  * trevnorrisjoined
06:01:10  * Maciek416joined
06:02:43  * trevnorrisquit (Ping timeout: 246 seconds)
06:09:35  * shamajoined
06:10:10  * trevnorrisjoined
06:11:04  * trevnorrischanged nick to trevnorri
06:14:11  * shamaquit (Ping timeout: 260 seconds)
06:14:34  <substack>ogd: https://github.com/maxogden/node-concat-stream/pull/16
06:14:45  <substack>works with typearrays etc!
06:14:48  <substack>and streams2 woo
06:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 15]
06:31:13  * fronxjoined
06:31:36  * calvinfojoined
06:36:37  * calvinfoquit (Ping timeout: 272 seconds)
06:37:50  * fronxquit (Ping timeout: 240 seconds)
06:38:42  * st_lukejoined
06:54:16  * calvinfojoined
06:58:49  * calvinfoquit (Ping timeout: 252 seconds)
07:12:56  * calvinfojoined
07:18:41  <DTrejo>advice please: I am going to public a new version of a module that is so much better than the old version. should I put it in a different project? Or just make a 2.0 and delete all the old code I'm throwing out
07:18:49  <DTrejo>*publish a new version
07:20:57  * Maciek416quit (Remote host closed the connection)
07:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 27]
07:30:36  <jesusabdullah>DTrejo: I'd 2.0 it, but that's me
07:34:25  <st_luke>just make a new one and eol the old one if you can think of a better name
07:41:28  <DTrejo>hmm, I'm about to publish it on a new branch, and i'll see what you guys think
07:45:53  <jesusabdullah>Do what feels right
07:45:54  <jesusabdullah>:)
07:54:29  * calvinfoquit (Quit: Leaving.)
07:55:20  <DTrejo>jesusabdullah: https://github.com/DTrejo/run.js/tree/2.0
07:55:22  <DTrejo>check it out
07:55:44  <DTrejo>basically, a file watcher that only watches the source files used by your server
07:55:53  <DTrejo>or whatever your javascript is
07:55:55  <jesusabdullah>that's cool
07:59:01  <DTrejo>:)
07:59:16  <DTrejo>jesusabdullah: I'm going to revolutionize npm build scripting ;)
08:01:45  <DTrejo>jesusabdullah: https://gist.github.com/DTrejo/2a509810ddf11672d424
08:02:24  <jesusabdullah>cute
08:02:28  <jesusabdullah>could be good
08:03:42  <DTrejo>dunno if that gist made any sense, but yea, we'll see
08:06:19  <DTrejo>I think it's a good idea to use simple bash commands to "compile" your server for production; and I think that it's a good idea not to have to worry about "compiling" if you're in development
08:07:30  <DTrejo>everyone has seen the millions of tools for restarting your server if server-side code changes, refreshing client-side if html changes, reloading CSS if css changes. I think some simple commands like these could tie all that together in a take-what-you kind of style
08:08:46  <substack>DTrejo: https://gist.github.com/substack/7819530
08:09:13  <substack>for the css and js part of it, not the server reloading part
08:09:20  <DTrejo>oh lol I guess when I looked at catw I didn't fully understand how to use it
08:11:17  * shamajoined
08:11:33  <DTrejo>substack: but yes that's exactly what I'm thinking about, mostly just inspired by your first blog post on it
08:15:50  * shamaquit (Ping timeout: 264 seconds)
08:16:40  * shamajoined
08:17:20  * shamaquit (Remote host closed the connection)
08:19:54  <DTrejo>substack: oh when I looked at catw the first time it didn't have transforms
08:20:05  <DTrejo>nice job
08:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 11]
08:27:27  * calvinfojoined
08:28:08  <DTrejo>time for a new post on task automation with npm run
08:33:29  * fronxjoined
08:38:07  * fronxquit (Ping timeout: 246 seconds)
08:39:07  * DTrejoquit
08:56:54  <juliangruber>substack: sweet, released
09:11:43  * fronxjoined
09:14:37  * fronxquit (Remote host closed the connection)
09:17:56  * shamajoined
09:19:10  * timoxleyjoined
09:22:26  * shamaquit (Ping timeout: 264 seconds)
09:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 37]
09:33:02  * fronxjoined
09:37:51  * st_lukequit (Remote host closed the connection)
09:45:24  * tearmannquit (Read error: Operation timed out)
09:48:10  * timoxleyquit (Remote host closed the connection)
10:01:38  * calvinfoquit (Quit: Leaving.)
10:09:18  * fronxquit (Remote host closed the connection)
10:10:14  <rowbit>substack, pkrumins: These encoders are STILL down: 50.57.103.88(dev)
10:10:47  * fronxjoined
10:19:03  * shamajoined
10:21:39  * peutetrejoined
10:23:59  * shamaquit (Ping timeout: 272 seconds)
10:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 32]
10:47:04  * ralphtheninjajoined
11:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 12]
11:25:48  * peutetrequit (Quit: peutetre)
11:33:45  * yorickjoined
11:35:05  * dominictarrjoined
11:36:16  * jcrugzzjoined
11:37:08  <dominictarr>wow, http://www.technologyreview.com/view/513781/moores-law-and-the-origin-of-life/
11:37:44  <dominictarr>^ THIS makes a very interesting hypothesis!
11:43:04  * fronxquit (Remote host closed the connection)
11:45:55  * fronxjoined
11:53:14  <yorick>ah, panspermia
11:53:24  <yorick>meteorite from mars and all that
12:01:49  <dominictarr>also, this would imply that other life in the universe is the same format (and not just carbon based, but dna)
12:07:50  * trevnorriquit (Ping timeout: 240 seconds)
12:07:57  * trevnorrisjoined
12:14:47  * fronxquit (Remote host closed the connection)
12:23:59  * fronxjoined
12:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 15]
13:05:06  <mmalecki>someone pinged me here?
13:09:30  * fronxquit (Remote host closed the connection)
13:18:13  * shamajoined
13:18:53  * fronxjoined
13:23:13  * shamaquit (Ping timeout: 272 seconds)
13:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 17]
13:24:23  * dominictarrquit (Ping timeout: 240 seconds)
13:37:06  * mafintoshjoined
13:50:24  * dominictarrjoined
14:09:43  * fronxquit (Remote host closed the connection)
14:09:52  * mafintoshquit (Quit: Leaving...)
14:19:00  * shamajoined
14:20:42  * shama_joined
14:23:15  * mafintoshjoined
14:23:33  * shamaquit (Ping timeout: 248 seconds)
14:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 20]
14:25:02  * shama_quit (Ping timeout: 240 seconds)
14:57:54  * thlorenzjoined
14:58:14  * fronxjoined
15:07:15  * mafintoshquit (Quit: Leaving...)
15:09:23  * mafintoshjoined
15:21:28  * shamajoined
15:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 22]
15:26:02  * shamaquit (Ping timeout: 264 seconds)
15:27:27  * mafintoshquit (Quit: Leaving...)
15:29:59  * mafintoshjoined
15:33:58  * fronxquit (Remote host closed the connection)
15:36:44  * fronxjoined
15:38:52  * mikolalysenkojoined
15:39:17  * fronxquit (Remote host closed the connection)
15:44:25  * jcrugzzquit (Ping timeout: 246 seconds)
15:52:32  * fronxjoined
15:53:20  * fronxquit (Remote host closed the connection)
16:00:50  * mikolalysenkoquit (Ping timeout: 264 seconds)
16:10:15  <rowbit>substack, pkrumins: These encoders are STILL down: 50.57.103.88(dev)
16:11:33  * Maciek416joined
16:17:10  * jcrugzzjoined
16:22:09  * shamajoined
16:23:57  <spion>grncdr, since you removed transactions from the pool (afaics) have you ever considered erm "lazy" transactions for connection pools?
16:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 9]
16:24:14  <spion>like, you create a transaction, but it doesn't actually reserve a connection until you tx.query(...
16:24:56  * mafintoshquit (Quit: Leaving...)
16:26:25  * shamaquit (Ping timeout: 246 seconds)
16:26:51  <spion>trying to build a project in terms of composing it using Actions and Views, where Actions are passed a transaction and can be comprised from queries and other actions
16:54:56  * thlorenzquit (Remote host closed the connection)
16:56:28  * shamajoined
17:11:16  * mafintoshjoined
17:11:58  * pfrazejoined
17:16:52  * fronxjoined
17:21:00  * fronxquit (Remote host closed the connection)
17:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 6]
17:27:38  * mikolalysenkojoined
17:31:19  * mafintoshquit (Quit: Leaving...)
17:33:57  * mafintoshjoined
17:42:39  * mikolalysenkoquit (Ping timeout: 240 seconds)
17:49:00  * Maciek416quit (Remote host closed the connection)
17:53:15  * mafintoshquit (Quit: Leaving...)
17:55:20  * AvianPhonejoined
17:55:31  * pfrazequit (Ping timeout: 252 seconds)
17:55:33  * mafintoshjoined
17:59:26  * AvianPhonequit (Ping timeout: 240 seconds)
18:11:43  <grncdr>spion: that seems like a pretty good idea
18:11:56  <grncdr>btw, all this 2.0 stuff isn't quite ready for production use
18:12:40  <spion>nah, I'm still using 1.0.3, just carefully following things
18:12:40  <spion>:D
18:13:15  <spion><3 any-db
18:13:29  <grncdr>I'm pretty excited about having everything be streams
18:14:33  <grncdr>I'd definitely be interested in a PR for lazy transactions
18:14:45  <grncdr>I can't see any reason not to do it
18:15:55  <grncdr>right now I'm working on making events consistent across all the adapters, as that's something that wasn't really tested very well before
18:16:09  <spion>ah
18:16:21  <spion>by streams you mean object streams, each being a row?
18:16:37  <spion>each item*
18:16:45  <grncdr>yeah
18:16:48  <spion>oh yes.
18:16:49  <spion>:D
18:17:02  <grncdr>https://github.com/grncdr/node-any-db-adapter-spec/issues/1
18:19:31  <spion>I like #3 - I suppose you could auto-emit a 'row' event on the stream (not entirely sure if thats a good idea for e.g. performance)
18:19:48  <grncdr>yeah #3 is the way I went with it
18:20:17  <grncdr>I'm not emitting 'row' because it's a major version bump
18:20:27  <grncdr>and I want to encourage people to treat them like streams
18:20:40  <grncdr>legacy code can just s/row/data/ and continue to work
18:21:18  <spion>yeah I guess its not that hard of a refactor
18:21:39  <grncdr>well, the mysql driver still emits 'row' events (for example)
18:22:07  <grncdr>actually, your suggestions about lazy transactions reminded me, should I stop automatically opening connections?
18:22:51  <spion>automatically opening them when?
18:23:01  <spion>and pool initialization?
18:23:18  <spion>s/and/at
18:23:47  <grncdr>right now createConnection(…) will actually establish a connection
18:24:02  <grncdr>pools would still automatically open them
18:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 11]
18:24:16  <grncdr>but like, it's impossible to get a connection from any-db without opening it
18:24:29  <spion>hmm, I don't know
18:25:05  <spion>the reason I asked about transactions is that my "action" abstraction can optionally accept a transaction. but it may do other non-database things before talking to the database
18:25:26  <spion>and since it makes very little sense for them to happen "within the transaction"...
18:26:05  <spion>it would be useful if a LazyTransaction would just sit there and wait :D
18:27:03  <spion>not sure if that would help with connections
18:27:58  <grncdr>yeah, it's one of those things where the drivers I'm wrapping support it, but I don't know why :P
18:28:02  <spion>i mean not sure if there would be any use for connections to be that way
18:28:19  * shamaquit
18:28:41  <spion>so, no idea :)
18:31:11  <spion>though i think i remember that there was something with mysql variables being connection-specific...
18:32:04  * ralphtheninjaquit (Ping timeout: 246 seconds)
18:34:17  <pkrumins>dominictarr: so i'm putting all browserify dependencies on testling, and for some reason through hangs at the 90th test
18:34:33  <pkrumins>dominictarr: even if i run the bundle locally in the latest chrome
18:34:47  <pkrumins>dominictarr: this bundle (see the console) http://git.testling.com/work/pkrumins/repos/e401c5aaf773a1783193b5c1f7f9393bbd938183.1387917709107/1387917709496.cbbb2416.html
18:37:28  <substack>juliangruber: https://github.com/juliangruber/array-filter/commit/99c473673544447a853b9dda67d90943fd6a818c#commitcomment-4938733
18:37:40  <substack>`covert` to the rescue yay!
18:37:45  <substack>also sweet tests and testling badge
18:38:40  <substack>juliangruber: and then I published https://github.com/substack/array-map and https://github.com/substack/array-reduce following your lead
18:38:54  <substack>mostly because publishing modules this way, it's much easier to get to 100% coverage
18:43:17  <substack>dominictarr: that graph is really cherry-picked
18:44:32  <substack>mammals don't have the largest genomes, single-celled organisms do
18:45:04  <grncdr>spion: the thing with mysql variables is that the driver does the interpolation client side (which seems insane to me but w/e).
18:45:29  <substack>dominictarr: http://www.genomesize.com/images/Cvals.jpg
18:45:47  <grncdr>I'm actually fixing that as part of everything else, by ensuring that 'query' events are always fired immediately before the query is enqueued on a live connection
18:48:24  <substack>or this one: https://en.wikipedia.org/wiki/File:Genome_Sizes.png
18:50:13  * dominictarrquit (Ping timeout: 248 seconds)
18:58:17  * thlorenzjoined
19:08:20  * mikolalysenkojoined
19:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 9]
19:24:13  * mikolalysenkoquit (Ping timeout: 272 seconds)
19:41:53  * thlorenzquit (Remote host closed the connection)
19:42:28  * thlorenzjoined
19:46:35  * thlorenzquit (Ping timeout: 240 seconds)
20:02:42  * fronxjoined
20:12:22  * calvinfojoined
20:13:12  * calvinfoquit (Client Quit)
20:16:44  * calvinfojoined
20:17:20  <substack>ogd: https://github.com/maxogden/node-concat-stream/pull/16
20:18:11  <substack>MERRY SATURNALIA
20:18:11  <LOUDBOT>SO GO GET A FUCKING CUP OF WATER
20:20:38  <substack>ogd: ok so next I'm going to make sure that concat-stream will work if you write a bops buffer to it
20:22:42  <substack>ogd: oh wow ok, in the latest bops it just returns Buffer() so everything should be good
20:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 26]
20:25:03  * jcrugzzquit (Ping timeout: 240 seconds)
20:25:42  <grncdr>hrm
20:26:46  <grncdr>if I have a streams2 readable stream, and it never receives any data, and eventually I call `this.push(null)`, should it not emit 'end' ??
20:27:58  <isaacs>grncdr: it should emit 'end', but only if you try to consume it in some way
20:28:12  <isaacs>grncdr: grncdr like if you call read() then it'll return null and emit 'end'
20:28:50  <grncdr>isaacs: ok, that's what I was afraid of...
20:29:06  <grncdr>not that it's bad, just that it might be incompatible with what I'm trying to do
20:30:09  <grncdr>in this case, a SQL query as a stream, where users might expect there to be no results, and therefore never read
20:30:59  <grncdr>e.g. stream = connection.query('INSERT …') won't produce any rows, so it's totally reasonable for a user to not consume that stream, but they still might want to know the query has completed
20:31:34  <grncdr>I could add a different event name ('complete') I suppose...
20:34:58  * shamajoined
20:38:49  * mikolalysenkojoined
20:43:58  <isaacs>grncdr: if you emit 'end' without ever reading, then you screw up proxy cases, where you dont pipe() on the current tick
20:44:12  * mafintoshquit (Quit: Leaving...)
20:44:14  <isaacs>grncdr: this was a serious bug in the first release of streams2
20:44:34  <isaacs>grncdr: streams2 is still less consistent about it. streams3 *never* emits 'end' until you read *past* the EOF marker.
20:44:54  <grncdr>I did not know streams3 was a thing
20:45:24  * fronxquit (Remote host closed the connection)
20:45:24  <grncdr>so, is is this._readableState.emittedEnd not safe to look at?
20:46:59  <grncdr>FWIW the decision makes total sense, I think I'm the one trying put a square peg in a round hole here, may have to think about it a bit more
20:48:55  * mafintoshjoined
20:59:49  * mafintoshquit (Quit: Leaving...)
21:01:36  * mafintoshjoined
21:04:01  <grncdr>hm, is 'close' the appropriate event to use here?
21:04:18  * mafintoshquit (Client Quit)
21:04:34  <grncdr>http://nodejs.org/api/stream.html#stream_event_close implies that it could fire before 'end'
21:04:38  * thlorenzjoined
21:05:12  <isaacs>'close' can fire at any or no time
21:05:27  <grncdr>right, but in my own API, I can guarantee that 'close' is fired
21:05:39  <grncdr>without having to interfere with the promises of Readable
21:05:41  * mikolalysenkoquit (Ping timeout: 248 seconds)
21:05:49  <grncdr>s/promises/contract/
21:06:32  <grncdr>is 'close' one of those things that streams3 is going to do away with though?
21:07:02  <grncdr>I'd rather be building towards the future then the past
21:08:25  * mikolalysenkojoined
21:11:11  <substack>isaacs: https://ci.testling.com/substack/typedarray
21:11:21  <substack>npm ERR! cycle Found a pathological dependency case that npm cannot solve.
21:15:34  * calvinfoquit (Quit: Leaving.)
21:15:52  * fronxjoined
21:20:38  * mikolalysenkoquit (Ping timeout: 240 seconds)
21:21:23  * fronxquit (Ping timeout: 272 seconds)
21:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 6]
21:36:41  * mafintoshjoined
22:00:33  * ralphtheninjajoined
22:01:01  <defunctzombie>substack: what is the issue with typedarray?
22:04:42  * fronxjoined
22:05:54  <substack>defunctzombie: npm complains about a pathological dependency case
22:05:58  * fronxquit (Remote host closed the connection)
22:06:02  <defunctzombie>haha
22:06:07  <defunctzombie>when doing install?
22:06:09  <substack>this is only an issue if you install browserify from the typedarray directory it seems
22:06:15  <substack>but on my local build I don't get that error
22:06:24  <defunctzombie>huh
22:08:53  <jesusabdullah>someone remind me again why I decided to build a gtk+ hello world on a macbook
22:10:16  <rowbit>substack, pkrumins: These encoders are STILL down: 50.57.103.88(dev)
22:15:11  <grncdr>if I have a data source that doesn't support back pressure, what's the "right way" to make a Readable out of it
22:15:39  <grncdr>like, I'm 100% ok with having everything just buffer up in memory, but it seems like calling this.push(data) from a data callback isn't working..
22:17:32  <substack>Readable().wrap(oldstream)
22:17:39  <grncdr>it's not a stream :(
22:17:53  <grncdr>it's sqlite3
22:17:56  <substack>o_O
22:18:13  <grncdr>I looked at what brianloveswords did in streamsql, and there's no backpressure support there
22:18:16  <grncdr>just data events firing willy-nilly
22:18:29  <grncdr>which is fine because he's consuming them as well
22:18:52  <grncdr>not so much in any-db though :|
22:19:09  <grncdr>anyways, I think I'm just seeing things
22:19:11  <substack>how does sqlite3 provide its data?
22:19:18  <substack>maybe you could send a patch upstream?
22:19:37  <grncdr>hm, might be worthwhile
22:19:53  <grncdr>but to be honest I'm really not a fan of sqlite3's API's at all
22:20:06  <grncdr>a "patch" would end up being more of a "rewrite"
22:20:39  <grncdr>like, the native code part of SQLite3 doesn't support pausing query results either afaik
22:24:04  <rowbit>Hourly usage stats: [developer: 0, free: 7]
22:26:07  * Maciek416joined
22:26:24  <substack>grncdr: is it a legacy app or does it need to integrate with existing sqlite3 data?
22:26:33  <substack>you could always port to leveldb
22:26:37  <grncdr>neither?
22:27:04  <grncdr>it's for no purpose whatsoever :P http://npm.im/any-db-sqlite3
22:27:07  <substack>ah
22:31:56  <grncdr>aha, I found it
22:33:58  <grncdr>I forgot I had done something stupid (overrode resume with a no-op)
22:34:49  * mafintoshquit (Quit: Leaving...)
22:35:38  <ralphtheninja>https://github.com/DavidJohnstonCEO/DecentralizedApplications
22:41:41  * st_lukejoined
22:46:12  * fronxjoined
22:48:42  * calvinfojoined
22:49:37  * mikolalysenkojoined
22:50:59  * fronxquit (Ping timeout: 260 seconds)
22:56:13  <grncdr>substack: is there a way to make covert work with scripts that have a shebang?
22:57:11  <substack>grncdr: aha, one sec
22:57:22  <substack>browserify has a check for that but not coverify
22:57:48  <grncdr>ah nice
22:58:29  <grncdr>not urgent btw, just wasn't sure if it was on the radar ;)
22:59:21  <substack>fixed in coverify@0.4.1
22:59:30  <substack>so if you download the latest `covert` you will get the fix
23:00:09  <substack>I just added a quick hack to comment out the #! lines: .replace(/^#!/, '//#!')
23:00:16  <substack>that preserves the line offsets
23:00:23  <substack>since I didn't want to update all of those
23:02:02  <substack>has nobody written a pretty human-readable parser for TAP yet?
23:02:08  <substack>that's the biggest complaint I see about using tap
23:02:17  <substack>so I'm just going to write one of those real quick if not
23:03:12  <defunctzombie>nope, don't think anyone has
23:03:23  <defunctzombie>and yes.. it is a complaint about tap cause no one can read that crap
23:03:50  <substack>well I personally don't mind the output
23:03:57  <substack>what kind of output are you used to?
23:11:19  * fronxjoined
23:12:05  * calvinfoquit (Quit: Leaving.)
23:13:21  * fronxquit (Remote host closed the connection)
23:18:41  <defunctzombie>substack: I like a list
23:18:56  <defunctzombie>substack: with the test name
23:19:09  <defunctzombie>ideally a little checkmark or green if passed and red if failed :)
23:19:49  <substack>sounds good
23:19:58  <defunctzombie>lists are simple
23:20:03  <defunctzombie>and not too verbose
23:24:03  <rowbit>Daily usage stats: [developer: 2, free: 445]
23:24:04  <rowbit>Hourly usage stats: [developer: 2, free: 67]
23:27:46  * calvinfojoined
23:30:45  * jcrugzzjoined
23:34:51  * calvinfoquit (Quit: Leaving.)
23:34:52  * st_lukequit (Remote host closed the connection)
23:46:15  * fronxjoined
23:51:01  * fronxquit (Ping timeout: 248 seconds)