00:00:09  * ircretaryjoined
00:00:13  <tjfontaine>it does do the right thing and call parent.on first
00:01:01  <othiym23>I'm gonna have to step through and see where this.on gets overwritten
00:02:40  <tjfontaine>shouldn't it be when the descendent class calls the parent constructor?
00:02:41  * wolfeidaujoined
00:02:54  <tjfontaine>or rather I guess from the inherits prototype
00:04:47  <othiym23>*sigh*
00:04:50  <othiym23>no, it's flowing mode
00:05:54  <othiym23>sorry, old-style mode
00:06:02  <othiym23>tjfontaine: https://github.com/joyent/node/blob/v0.10/lib/_stream_readable.js#L736-L739
00:06:24  <othiym23>if only I didn't need to do this particular bit of monkeypunching
00:06:28  <tjfontaine>oh oh
00:06:51  <tjfontaine>yup now I see it in my `git grep`
00:07:38  * st_luke_joined
00:07:44  <tjfontaine>othiym23: if it makes you feel better that doesn't happen in 0.11
00:07:45  * st_luke_quit (Read error: Connection reset by peer)
00:08:03  * st_lukequit (Read error: No route to host)
00:08:05  <tjfontaine>because there be no more old mode
00:08:06  <othiym23>tjfontaine: I see that
00:08:17  <othiym23>that will help me at some distant point in the future
00:08:17  <tjfontaine>streams2 is dead, long live streams3
00:08:34  <othiym23>point of fact: since we reopened the beta yesterday, we've already gotten a couple of emails complaining we don't support 0.6
00:08:41  <tjfontaine>><
00:08:49  <othiym23>(o_o)-b
00:09:28  <othiym23>here's the bug I'm trying to fix: https://github.com/newrelic/node-newrelic/issues/50
00:09:36  <othiym23>it would help if I could actually force a repro
00:09:45  <tjfontaine>ouch.
00:11:29  <trevnorris>oh suck a duck.
00:12:25  <othiym23>that sounds unhygienic
00:13:03  <trevnorris>othiym23: so know how we had to create that new object in runAsyncQueue because the domain field was changing.
00:13:16  <trevnorris>well now that means I can't use the object itself as the key
00:14:00  <othiym23>trevnorris: from the C++ side?
00:14:44  <trevnorris>othiym23: from either side. process.removeAsyncListener looks for the same object in the current queue, and removes it. but since the queue is created when runAsyncQueue runs
00:14:49  <trevnorris>all the objects there will be unique
00:15:02  <trevnorris>so process.removeAsyncQueue is busted.
00:15:04  <trevnorris>freakin a
00:15:34  <trevnorris>guess I'll need to add a uid to each object and check those.
00:15:36  <trevnorris>oy, so much sloer.
00:17:01  <trevnorris>*slower
00:17:25  <othiym23>trevnorris: every object will be guaranteed to have at least a listener property / function, right?
00:17:41  <trevnorris>othiym23: yeah
00:18:05  <trevnorris>othiym23: but you can reuse the same listener callback for many items. same with the callbacks object.
00:18:11  <othiym23>right
00:18:14  <othiym23>hm
00:18:51  <othiym23>trevnorris: what if you embedded the {listener, callbacks} object inside the individual listener objects?
00:18:55  <othiym23>then you could key off those
00:20:03  <trevnorris>othiym23: hm. good point. but the question is where do you want the hit? you won't be running removeAsyncListener near as often as runAsyncQueue
00:20:32  <trevnorris>well, have to head. i'll fix these bugs tonight.
00:20:51  <othiym23>tjfontaine: do you have any ideas on how to make this saner? https://gist.github.com/othiym23/6802613
00:20:58  <othiym23>(if you've got a moment for a code review)
00:22:17  <tjfontaine>looking
00:24:45  <qard>I'm getting duplicate error events from domains. Is there something weird with my code? https://gist.github.com/Qard/fbdbd7bc239afa2eda04
00:26:08  * EhevuTovquit (Quit: This computer has gone to sleep)
00:26:39  <othiym23>qard: the fact that you're throwing from the callback you're giving to reportError probably has something to do with that
00:26:41  <tjfontaine>othiym23: painful, but nothing at the moment is coming to me as better
00:26:46  <othiym23>qard: what are you trying to do?
00:26:50  <othiym23>tjfontaine: k, thanks for looking
00:27:20  <qard>Trying to delay the process death long enough to send the error to another server.
00:27:22  <tjfontaine>I'm so sorry you have to work with it like this :)
00:27:51  <qard>So the setTimeout would actually be some http request or something.
00:28:07  <qard>Basically, an async call that will rethrow the error when it is done.
00:28:21  <qard>So the process still dies as expected.
00:28:40  <qard>And no, process.exit() is not a solution here.
00:29:17  <tjfontaine>if you're really going for upstream reporting, shouldn't you have a first class callback from the reporter indicating it sent the message successfully?
00:29:22  <qard>Trying to come up with a way to intercept errors while being transparent.
00:29:47  <qard>So it should behave as if the domain wasn't even there, to the best capacity it can.
00:30:18  <tjfontaine>but you're not being transparent of course, you're delaying a tick, from inside a domain, which means more state can mutate
00:30:49  <qard>Yes, I'm aware of that.
00:30:58  <tjfontaine>sounds like you want a reliable synchronous transport mechanism
00:30:59  <qard>Trying to be as transparent as possible though.
00:31:08  <othiym23>qard: another problem is using enter and exit like that, you probably just want d.run(function () { setTimeout...
00:31:27  <qard>run doesn't work. It has to catch the top level.
00:32:10  <qard>basically I need require('my-module') to catch everything running after it.
00:33:04  <othiym23>qard: it sounds like what you're looking for is process.on('uncaughtException') ;)
00:33:27  <othiym23>qard: if you had an uncaughtException handler that returned true with that setTimeout in it, it would probably be closer to what you want
00:34:11  <othiym23>but everything is still going to be up for grabs once the first error handler fires
00:34:13  <qard>I don't want to interfere with uncaughtException listeners someone else may have attached though.
00:34:33  <othiym23>qard: then have your handler return false
00:34:37  <tjfontaine>well, monkey patch the process.on I guess
00:35:02  <othiym23>or monkeypatch process._fatalException if you're running 0.10 and feel like living dangerously
00:35:09  <tjfontaine>right
00:35:10  <othiym23>NOT THAT I KNOW ANYONE WHO DOES THAT *coughing fit*
00:35:18  <qard>Basically, I want to catch the errors before they hit uncaughtException, report them, and return control back so they still hit uncaughtException as normally expected.
00:36:18  <othiym23>qard: this is what the Airbrake module that was floating around tried to do, and it showed that there are a lot of subtle edge cases to this
00:36:53  <qard>Yeah, it's proving to be a pretty awkward problem to solve.
00:37:11  <qard>Just wondered if anyone had any ideas I hadn't thought of already.
00:37:48  <qard>monkeypatching process._fatalException might be the way to go, as much as I dislike the idea...
00:38:14  <qard>Then again, holding a process open while it's in a bad state probably isn't much better...
00:38:42  <tjfontaine>ya this is risky business, not that I'm a tom cruise fan
00:38:45  <othiym23>qard: I came up with a way to do this for the New Relic module, but it's really hard for me to disentangle the New Relic bits from the generic error-handling
00:38:57  <othiym23>you can take a look at https://github.com/newrelic/node-newrelic/ for ideas if you like, though
00:39:16  <othiym23>qard: lib/dominion.js and lib/errors.js are where the bulk of it is
00:39:28  <tjfontaine>all licenses observed :)
00:39:32  <othiym23>it's all known to work with at least 0.8 and 0.10, but it does some unhygienic stuff
00:39:53  <othiym23>tjfontaine: the code's New Relic's, but the ideas are freeeeeeeeee
00:40:04  <tjfontaine>yes, but it's weird
00:40:19  <othiym23>tjfontaine: agreed, but that's the New Relic Way (tm)
00:40:30  <tjfontaine>nod
00:47:22  * vptrquit (Disconnected by services)
00:47:38  * vptrjoined
00:47:39  * vptr1joined
00:49:33  <vptr>what is the correct way to build libuv if I want to have statically link it with my app?
00:50:10  <tjfontaine>the most supported way is via gyp
00:51:11  <tjfontaine>by default when you call gyp_uv it will build a static library version of libuv unless you specify -Dlibrary
00:54:44  * c4milo_joined
00:54:51  * octetcloudquit (Ping timeout: 248 seconds)
00:55:03  * c4miloquit (Read error: Connection reset by peer)
00:59:56  <tjfontaine>vptr: did that answer your question?
01:00:05  <vptr>I was testing something
01:00:08  <tjfontaine>k
01:00:08  <vptr>so, here is the problem
01:01:07  <vptr>I think I'm just stupid, but anyway. when I have the .a file I have all these unresolved symbols from the foundation framework on my mac
01:01:42  <vptr>If I just build, install and link with -luv
01:01:45  <vptr>I have no problems
01:02:07  <tjfontaine>vptr: gist?
01:02:08  <vptr>do shared objects include all other deps
01:04:07  <vptr>http://codepad.org/IqfsYByE
01:04:36  <vptr>It probably makes sense, since .a is just archive of .o files
01:05:21  <vptr>It's just sucks that you have manually link against all this osx crap
01:06:32  * dapquit (Quit: Leaving.)
01:11:21  * qardquit (Quit: Leaving.)
01:13:31  * superjoequit (Ping timeout: 246 seconds)
01:23:45  * amartensquit (Quit: Leaving.)
01:26:59  * austoquit (Quit: austo)
01:28:21  * abraxasjoined
01:49:45  * mikealquit (Quit: Leaving.)
01:55:25  * TooTallNatejoined
01:55:37  * c4milo_quit (Remote host closed the connection)
01:57:09  * TooTallNatequit (Client Quit)
02:14:13  * amartensjoined
02:14:59  * amartensquit (Client Quit)
02:20:24  * mikealjoined
02:26:41  * austojoined
02:29:15  * mikealquit (Ping timeout: 248 seconds)
02:51:06  * austoquit (Quit: austo)
02:52:34  * vptrquit (Quit: WeeChat 0.3.5)
03:25:12  * c4milojoined
03:27:00  * mikealjoined
03:31:08  * mikealquit (Ping timeout: 240 seconds)
03:32:09  * octetcloudjoined
03:36:18  * inolenquit (Quit: Leaving.)
03:36:37  * inolenjoined
03:36:50  * inolen1joined
03:40:10  * inolen1quit (Read error: Connection reset by peer)
03:41:19  * inolenquit (Ping timeout: 260 seconds)
03:47:46  <othiym23>woo event emitter party, part two
03:53:30  * octetcloudquit (Ping timeout: 264 seconds)
03:58:24  * kazuponjoined
04:01:02  * julianduquequit (Quit: leaving)
04:03:40  * st_lukejoined
04:09:17  * st_lukequit (Remote host closed the connection)
04:19:09  * c4miloquit (Remote host closed the connection)
04:27:26  * mikealjoined
04:31:41  * mikealquit (Ping timeout: 245 seconds)
04:37:09  * defunctzombie_zzchanged nick to defunctzombie
04:44:18  * TooTallNatejoined
04:44:19  * octetcloudjoined
04:45:10  * defunctzombiechanged nick to defunctzombie_zz
04:49:23  * st_lukejoined
04:52:47  * st_luke_joined
04:52:58  * st_lukequit (Read error: Connection reset by peer)
04:54:02  * defunctzombie_zzchanged nick to defunctzombie
05:05:05  <othiym23>at some point I'm going to corner the market on abusing try/finally
05:08:23  * defunctzombiechanged nick to defunctzombie_zz
05:09:00  * mikealjoined
05:09:20  * mikealquit (Client Quit)
05:10:08  * st_luke_quit (Remote host closed the connection)
05:14:25  * mikealjoined
05:17:25  * defunctzombie_zzchanged nick to defunctzombie
05:20:57  * defunctzombiechanged nick to defunctzombie_zz
05:30:21  * octetcloudquit (Ping timeout: 256 seconds)
05:31:08  * TooTallNatequit (Quit: Computer has gone to sleep.)
05:33:23  * paddybyersquit (Quit: paddybyers)
05:35:05  * paddybyersjoined
06:05:55  * c4milojoined
06:07:52  * bajtosjoined
06:08:30  * bajtosquit (Client Quit)
06:27:08  * vptr1quit (Ping timeout: 240 seconds)
06:40:38  * TooTallNatejoined
06:41:31  <MI6>nodejs-v0.10-windows: #240 UNSTABLE windows-ia32 (10/600) windows-x64 (7/600) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/240/
07:00:42  * `3E|ZZZchanged nick to `3rdEden
07:04:09  * TooTallNatequit (Quit: Computer has gone to sleep.)
07:18:09  * rendarjoined
07:36:43  * bnoordhuisjoined
07:38:47  * hzjoined
07:54:22  * kellabytequit (Quit: Quit)
08:00:00  * kellabytejoined
08:08:43  * c4miloquit (Remote host closed the connection)
08:18:41  <bnoordhuis>ircretary: tell vptr libuv master loads CoreServices, CoreFoundation, etc. dynamically - you no longer have to link to them explicitly
08:18:42  <ircretary>bnoordhuis: I'll be sure to tell vptr
08:19:37  * AvianFlujoined
08:32:49  * AvianFluquit (Remote host closed the connection)
09:08:49  * Chip_Zerojoined
09:13:25  * Kakerajoined
09:27:45  <bnoordhuis>fucking hell github
09:28:02  <bnoordhuis>that site goes down more often than a cheap hooker
09:51:03  * AvianFlujoined
09:58:38  * AvianFluquit (Remote host closed the connection)
10:20:55  * kazupon_joined
10:20:55  * kazuponquit (Read error: Connection reset by peer)
10:44:28  * kazupon_quit (Remote host closed the connection)
10:46:08  * kazuponjoined
11:05:44  * AvianFlujoined
11:18:05  * roxlu_quit (Quit: leaving)
11:19:47  * kazuponquit (Remote host closed the connection)
11:36:48  * bnoordhuisquit (Ping timeout: 240 seconds)
11:38:15  * rendarquit (Read error: Connection reset by peer)
11:48:29  * abraxasquit (Remote host closed the connection)
11:49:02  * abraxasjoined
11:53:31  * abraxasquit (Ping timeout: 248 seconds)
12:03:31  * AvianFluquit (Remote host closed the connection)
13:16:28  * AvianFlujoined
13:19:01  * bnoordhuisjoined
13:27:25  * defunctzombie_zzchanged nick to defunctzombie
13:27:28  * bajtosjoined
13:37:13  * c4milojoined
13:46:16  * defunctzombiechanged nick to defunctzombie_zz
13:57:05  * vptr1joined
14:02:05  * vptr1quit (Quit: WeeChat 0.4.1)
14:03:48  * AvianFluquit (Remote host closed the connection)
14:08:06  * c4miloquit (Remote host closed the connection)
14:22:32  * rendarjoined
14:27:44  <MI6>joyent/node: Ben Noordhuis master * 6820054 : src: raise maximum file descriptor limit - http://git.io/hass3A
14:38:45  * kellabytequit (Changing host)
14:38:45  * kellabytejoined
14:38:45  * kellabytequit (Changing host)
14:38:45  * kellabytejoined
14:50:31  * c4milojoined
14:52:45  <MI6>nodejs-master-windows: #385 UNSTABLE windows-x64 (21/644) windows-ia32 (21/644) http://jenkins.nodejs.org/job/nodejs-master-windows/385/
14:56:33  * dapjoined
15:07:26  * kazuponjoined
15:07:32  * mikealquit (Quit: Leaving.)
15:15:07  * TooTallNatejoined
15:16:08  * bradleymeckjoined
16:01:14  * hzquit
16:06:42  * hzjoined
16:15:16  * jmar777joined
16:16:52  * TooTallNatequit (Quit: Computer has gone to sleep.)
16:19:06  * defunctzombie_zzchanged nick to defunctzombie
16:19:45  * bajtosquit (Quit: bajtos)
16:22:05  * bnoordhuisquit (Ping timeout: 240 seconds)
16:24:39  * qardjoined
16:27:15  * octetcloudjoined
16:28:13  * julianduquejoined
16:28:51  * julianduquequit (Client Quit)
16:35:06  * AvianFlujoined
16:40:11  * mikealjoined
16:42:12  * st_lukejoined
16:45:17  * piscisaureus_joined
16:49:00  * bajtosjoined
16:50:38  * mikealquit (Quit: Leaving.)
16:52:51  * AvianFluquit (Remote host closed the connection)
17:19:59  * c4miloquit (Remote host closed the connection)
17:23:21  <piscisaureus_>hello
17:23:25  <tjfontaine>hello
17:23:41  <piscisaureus_>how are things in the bay area?
17:24:08  <tjfontaine>beautiful day today, spending some time in node_crypto.cc though instead of being outside :)
17:25:16  <piscisaureus_>do you like it inside node_crypto.cc?
17:25:22  <piscisaureus_>warm and fuzy?
17:25:25  <piscisaureus_>*fuzzy
17:25:41  <tjfontaine>no, cold and damp, and alone :)
17:25:53  <qard>I imagine node_crypto being kind pirckly.
17:26:07  <qard>prickly*
17:26:40  <tjfontaine>right, so it's just another place we're not clearing the error stack
17:26:50  <tjfontaine>I need to write the test case for it
17:28:53  * st_lukequit (Remote host closed the connection)
17:34:01  * othiym23whistles a cheerful song about murdering every connect middleware author alive
17:34:05  <othiym23>so much jankiness
17:34:17  <tjfontaine>othiym23: I hear you like frameworks
17:35:46  <piscisaureus_>tjfontaine: is that suggestive? Do you have problems with frameworks?
17:36:36  <piscisaureus_>oh must run
17:37:51  <tjfontaine>piscisaureus_: I'm just trolling, I don't really care what people do in js
17:38:22  <wolfeidau>othiym23: Hey i wrote a connect middleware recently hopefully your reach doesn't extend to Australia
17:40:48  * piscisaureus_quit (Ping timeout: 240 seconds)
17:41:46  <othiym23>wolfeidau: my reach is infinite and my hatred unbounded, but you didn't write the middleware I'm trying to destroy with my mind right now, so you're probably safe
17:42:16  <wolfeidau>othiym23: No I try and keep things pretty simple
17:42:52  * c4milojoined
17:46:09  * defunctzombiechanged nick to defunctzombie_zz
17:46:17  <wolfeidau>tjfontaine: I have hacked around with those arm builds based on my testing the pi one works fine the beagle one I am having trouble with
17:46:31  <qard>You can destroy things with your mind? That seems like a pretty awesome power.
17:46:52  <qard>Though horribly inconvenient, if activated accidentally.
17:47:14  * mikealjoined
17:48:19  <wolfeidau>That damn --without-snapshots issue is very frustrating btw
17:59:35  * bnoordhuisjoined
17:59:55  <bnoordhuis>hello people
18:01:00  <MI6>joyent/node: Ben Noordhuis master * f649626 : src: add JS start/stop methods for idle notifier (+2 more commits) - http://git.io/34Uc6Q
18:03:27  <bnoordhuis>tjfontaine: ping
18:05:37  * st_lukejoined
18:08:06  * kazuponquit (Remote host closed the connection)
18:15:28  * amartensjoined
18:24:24  * kazuponjoined
18:24:27  * kazuponquit (Remote host closed the connection)
18:25:02  * saghulquit (Ping timeout: 240 seconds)
18:32:07  <MI6>nodejs-master-windows: #386 UNSTABLE windows-x64 (22/644) windows-ia32 (21/644) http://jenkins.nodejs.org/job/nodejs-master-windows/386/
18:35:22  * saghuljoined
18:43:47  * defunctzombie_zzchanged nick to defunctzombie
18:47:49  * saghulquit (Read error: Operation timed out)
18:55:00  * saghuljoined
18:55:42  * st_lukequit (Remote host closed the connection)
18:57:18  * defunctzombiechanged nick to defunctzombie_zz
19:01:41  * EhevuTovjoined
19:08:43  * bajtosquit (Quit: bajtos)
19:13:58  <MI6>nodejs-master-windows: #387 UNSTABLE windows-x64 (25/644) windows-ia32 (27/644) http://jenkins.nodejs.org/job/nodejs-master-windows/387/
19:16:46  * bradleymeckquit (Quit: bradleymeck)
19:21:37  * mikealquit (Quit: Leaving.)
19:34:57  * kazuponjoined
19:35:26  * kevinswiberjoined
19:40:13  * kazuponquit (Ping timeout: 246 seconds)
19:48:36  * bradleymeckjoined
20:00:26  * bnoordhuisquit (Ping timeout: 245 seconds)
20:07:41  <tjfontaine>ircretary: tell bnoordhuis pong
20:07:41  <ircretary>tjfontaine: I'll be sure to tell bnoordhuis
20:08:22  <othiym23>tjfontaine: I updated https://gist.github.com/othiym23/6802613 to fix a bug
20:08:26  <othiym23>tjfontaine: it's now a real work of art
20:08:34  <othiym23>remind me to never monkeypatch event emitters again
20:08:43  <tjfontaine>poor try catch
20:08:53  <tjfontaine>EEs love getting abused :)
20:09:45  <tjfontaine>this doesn't abuse/obfuscate the stacks to much in the event of an error, right? :)
20:09:50  <othiym23>the Connect limit middleware adds a listener to newListener that removes a listener and then registers another one on nextTick
20:10:02  <tjfontaine>oy
20:10:07  * xaqjoined
20:11:04  <othiym23>it adds a couple frames to the stacktrace, but it's not doing anything magical beyond what you see there
20:11:15  <othiym23>basically everything that CLS does with EEs is in that function
20:11:24  <tjfontaine>excellent.
20:11:39  <tjfontaine>my list of things to try is getting longer and longer
20:12:05  <othiym23>and this behavior only gets added to EEs that are explicitly bound to the CLS namespace
20:13:46  <tjfontaine>right
20:22:22  * mikealjoined
20:25:07  * TooTallNatejoined
20:25:42  * philipsquit (Read error: Connection reset by peer)
20:26:28  * mikealquit (Ping timeout: 240 seconds)
20:26:53  * philipsjoined
20:35:08  * st_lukejoined
20:39:50  * Benviequit
20:39:51  * st_lukequit (Remote host closed the connection)
20:44:33  * jmar777quit (Remote host closed the connection)
20:45:44  * xaqquit (Remote host closed the connection)
20:45:47  <tjfontaine>it would be nice if node v0.8 HEAD didn't core
20:49:30  * mikealjoined
20:52:34  * roxlujoined
20:52:48  * TooTallNatequit (Quit: Computer has gone to sleep.)
20:53:43  <roxlu>hi guys, I'm handling a sigpipe and want to stop/join a thread. I'm using a condition variable which I signal but it looks like the thread does never wake up
20:54:14  <roxlu>is there something special with handling SIGPIPE and signalling condition variables?
20:54:40  * julianduquejoined
21:01:27  <tjfontaine>man 1) I wish this test case was more reliable, 2) wish it still happened on 0.10
21:06:35  * kevinswiberquit (Remote host closed the connection)
21:08:07  <othiym23>tjfontaine: you need to include the --crash-reliably --no-heisenbugs flags
21:08:12  <tjfontaine>oh
21:08:16  * wwicksquit (Quit: wwicks)
21:08:18  <othiym23>yeah, easy to overlook
21:09:08  <tjfontaine>it's not really even clear to me how this isn't failing on v0.10
21:09:31  <tjfontaine>unless we're somehow clearing the openssl error stack unintentionally
21:09:51  <othiym23>I was gonna ask what the bug was, but then I saw openssl and got scared
21:10:10  <tjfontaine>I will gist the test case
21:11:08  <tjfontaine>https://gist.github.com/tjfontaine/6817182
21:11:40  <tjfontaine>do a bad verification, and then do an ssl operation later
21:12:07  <tjfontaine>add a comment with the error
21:14:33  * bradleymeckquit (Quit: bradleymeck)
21:15:20  * EhevuTovquit (Quit: This computer has gone to sleep)
21:15:56  * EhevuTovjoined
21:18:39  * kevinswiberjoined
21:22:30  <tjfontaine>ah, there we go that's better
21:22:38  <tjfontaine>ok it does happen on v0.10
21:34:52  * kevinswiberquit (Remote host closed the connection)
21:37:45  * karupa64quit (Ping timeout: 256 seconds)
21:39:35  * rendarquit
21:40:00  * rendarjoined
21:40:52  * rendarquit (Client Quit)
21:42:10  * zz_karupa64joined
21:56:23  * wwicksjoined
22:01:32  * philipsquit (Quit: http://ifup.org)
22:03:51  * philipsjoined
22:05:38  * mikealquit (Quit: Leaving.)
22:08:28  * mikealjoined
22:12:10  <trevnorris>anyone know how to handle this type of compiler error: "neither visible in the template definition nor found by argument-dependent lookup"
22:12:45  <trevnorris>trying to use a method from a header in a .cc file. but not playing nice.
22:13:48  <trevnorris>nm. there's a clang compatibility doc on it.
22:20:13  * wwicksquit (Quit: wwicks)
22:24:21  <trevnorris>one thing I hate about this -inl.h stuff is that one error causes pages of compiler errors to appear, in ever location it was used.
22:26:26  <trevnorris>oy, where's ben when I need him
22:27:15  <trevnorris>oh, that was simple. just needed to include node.h in the file. :P
22:27:32  * `3rdEdenchanged nick to `3E|ZZZZ
22:28:04  * hzquit
22:35:19  * wwicksjoined
22:35:56  <othiym23>bnoordhuis was inside you all along, trevnorris
22:36:07  <trevnorris>haha
22:37:15  * Kakeraquit (Ping timeout: 248 seconds)
22:39:22  <trevnorris>othiym23: say you: var key = process.createAsyncListener(...);
22:39:22  <trevnorris>I allow you to add that as many times as you'd like, and it'd have to be removed an equal number of times.
22:39:22  <trevnorris>you think I should only allow it to be added once?
22:41:35  <othiym23>trevnorris: let's talk use cases here
22:41:49  <othiym23>how often would you want to stack the same listener?
22:42:22  <trevnorris>so I figured why would the developer do it. and the logic is simpler not having to run through the queue and make sure it hasn't already been added.
22:42:33  <trevnorris>so, it is like it is out of pure laziness. :)
22:47:24  <trevnorris>othiym23: anyways. you have any issue with that? i mean, not like i'm going to throw an error if they do.
22:47:42  <trevnorris>guess I could do something like return true/false if it was added or whatever, but seriously. who would check that?
22:47:59  <othiym23>I don't have an issue with it, although I think conceptually I'm more comfortable thinking of the listners as a set rather than a bag
22:48:25  <trevnorris>set, as in each value is unique?
22:48:41  <othiym23>I mostly care about things like that in my test code, although I just got bitten in the ass hard by a bug where I was wrapping the same function many many many times
22:48:52  <trevnorris>haha
22:49:12  <othiym23>trevnorris: yeah, I think of the value returned by createListener / addListener as an identity, which uniquely identifies a listener
22:49:17  <trevnorris>you and your function wrapping. well, no more of that in v0.12!
22:49:43  <trevnorris>othiym23: well, it has an identifier. just added a uid field.
22:50:10  <trevnorris>because the object itself isn't a unique identifier anymore after you helped me fix the bug where the domain was being changed for all instances
23:06:10  * mikealquit (Quit: Leaving.)
23:12:07  * mikealjoined
23:14:22  * M28joined
23:20:22  <othiym23>oh boy, UIDs!
23:20:53  <othiym23>I added a dunder @ property to my latest monkeypatching business out of solidarity with the hardworking members of TC39
23:21:03  <trevnorris>hah
23:25:58  <trevnorris>oy, for some reason setTimeout is triggering _fatalException twice.
23:28:46  <tjfontaine>dunerheads
23:53:45  * defunctzombie_zzchanged nick to defunctzombie
23:59:32  <tjfontaine>ahem
23:59:33  <tjfontaine>EVP_VerifyFinal() returns 1 for a correct signature, 0 for failure and -1 if some other error occurred.
23:59:41  <tjfontaine>verify called: 0
23:59:41  <tjfontaine>/Users/tjfontaine/Development/node-v0.10/test/simple/test-crypto-verify-failure.js:75
23:59:43  <trevnorris>tjfontaine: this is weird. have a backtrace from a segfault, not a single line from node.
23:59:45  <tjfontaine> throw err;
23:59:47  <tjfontaine> ^
23:59:48  <tjfontaine>thanks for that openssl.
23:59:50  <tjfontaine>Error: 140735256580480:error:04091077:rsa routines:INT_RSA_VERIFY:wrong signature length:../deps/openssl/openssl/crypto/rsa/rsa_sign.c:175: