00:15:04  * rendarquit (Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!)
01:12:09  * Ruyi-HomePCjoined
01:44:37  * ruyi_du_joined
01:44:37  * Ruyiquit (Read error: Connection reset by peer)
02:16:08  * alexforsterjoined
02:18:11  * alexforsterquit (Client Quit)
02:50:26  * ruyi_du_quit (Ping timeout: 240 seconds)
02:50:54  * ruyi_du_joined
03:28:04  * tunniclm_quit (Ping timeout: 250 seconds)
03:34:44  * metricquit (Remote host closed the connection)
03:35:06  * metricjoined
03:41:48  * rmgjoined
03:46:20  * rmgquit (Ping timeout: 245 seconds)
04:24:38  * brsonquit (Quit: leaving)
04:42:40  * rmgjoined
04:48:02  * rmgquit (Ping timeout: 276 seconds)
06:55:40  * MoZu4k__quit (Quit: MoZu4k__)
07:33:21  * davijoined
07:51:32  * MoZu4k_joined
07:54:41  * MoZu4k_quit (Client Quit)
08:45:41  * rmgjoined
08:50:35  * rmgquit (Ping timeout: 260 seconds)
09:08:12  * daviquit (Ping timeout: 250 seconds)
09:13:59  * davijoined
09:31:59  * daviquit (Ping timeout: 264 seconds)
10:05:38  * davijoined
10:29:18  * tunniclm_joined
10:50:40  * Ruyi-HomePCquit (Read error: Connection reset by peer)
10:53:53  * Ruyi-HomePCjoined
11:00:20  * seishunjoined
11:45:35  <txdv>0 0
11:45:36  <txdv>mono: src/unix/async.c:137: uv__async_io: Assertion `n == sizeof(val)' failed.
11:49:21  <txdv>fails consistantly 64bit
12:57:21  * daviquit (Remote host closed the connection)
13:15:32  * amurzeaujoined
13:16:06  * davijoined
13:47:01  * daviquit (Ping timeout: 245 seconds)
14:01:59  * Ruyi-HomePCquit (Read error: Connection reset by peer)
14:40:12  * mafintoshjoined
14:40:29  <mafintosh>is there anyway to disable SO_REUSEPORT in libuv 0.10 on udp sockets?
14:40:58  <mafintosh>(i have something i want to support in node 0.10 if possible)
14:50:17  * rmgjoined
14:54:56  * rmgquit (Ping timeout: 245 seconds)
15:16:10  <txdv>yeah
15:16:33  <txdv>you get the fd with uv_fileno
15:16:37  <txdv>and then you can do whatever you want
15:16:49  <txdv>i usually wear the fd like a hat
15:29:58  * bradleymeckjoined
15:42:32  * cremesquit (Ping timeout: 250 seconds)
15:47:52  * cremesjoined
15:50:19  * davijoined
15:52:07  * ruyi_du_quit (Read error: Connection timed out)
15:53:03  * ruyi_du_joined
15:57:11  * cremesquit (Ping timeout: 264 seconds)
16:00:01  * cremesjoined
16:24:14  * happy-dudejoined
16:51:49  * rmgjoined
16:56:20  * rmgquit (Ping timeout: 245 seconds)
16:57:04  * Damn3dquit (Ping timeout: 250 seconds)
17:01:08  * Damn3djoined
17:20:21  * bradleymeckquit (Quit: bradleymeck)
17:33:16  * evanlucasquit (Ping timeout: 245 seconds)
17:33:30  * evanlucasjoined
17:55:04  * daviquit (Remote host closed the connection)
17:55:42  * davijoined
18:24:21  * bradleymeckjoined
18:33:02  * steveirejoined
18:33:50  * bradleymeckquit (Quit: bradleymeck)
18:36:50  * daviquit (Ping timeout: 260 seconds)
19:46:40  * Jacob8432joined
19:50:30  * Jacob843quit (Ping timeout: 245 seconds)
19:54:02  * Left_Turnquit (Ping timeout: 252 seconds)
19:55:04  * Jacob8432quit (Quit: Leaving)
19:55:34  * Jacob843joined
20:09:12  * brsonjoined
21:10:44  <saghul>mafintosh: not officially in libuv 0.10, but you can dig into the internals, we are not going to change them now :-)
21:11:17  <mafintosh>saghul: thanks - i'll do that
21:12:15  <saghul>it's usually handle->io_watcher.fd
21:16:11  * Left_Turnjoined
21:27:12  * saghulquit (Remote host closed the connection)
21:36:45  * saghuljoined
21:49:10  * brsonquit (Ping timeout: 250 seconds)
21:59:48  * happy-dudequit (Quit: Connection closed for inactivity)
22:01:16  * steveirequit (Remote host closed the connection)
22:03:12  * amurzeauquit (Quit: Page closed)
22:09:59  * seishunquit (Ping timeout: 276 seconds)
22:33:06  * brsonjoined
23:27:27  * iamtakingiteasyjoined
23:28:51  <iamtakingiteasy>hello, i am looking at many examples of libuv code and i am confused by multitude of examples of heap-allocated loop uv_loop_t* structure, without single one performed on stack. is there a reason why we should not allocate uv_loop_t on stack?
23:32:26  * bwoebijoined
23:33:39  <iamtakingiteasy>mostly, those examples are accompanied by motivation that "so we can use custom memory allocators", or with no comment at all, but what could possibly hold them all from using &var syntax of getting memory address pointing to a stack-allocated instance?
23:35:14  <iamtakingiteasy>is such preference exists due to some background of node.js infrastructure?
23:39:22  <bwoebi>Hey … I've been debugging libuv for hours, but this is just weird … uv__async_init() creates pipe pair on fd 8 and 9. uv__async_send() writes on fd 9, kevent listens on fd 8 … everything is fine the first time uv_fs_open is called (write on fd 9, kevent returns notification about data on fd 8), but second time it is called, uv__async_send is writing one byte on fd 9, but kevent() is blocking and not reporting any ne
23:39:22  <bwoebi>w data on fd 8 (I'm also neither seeing any read between the write and the kevent syscall, neither do I see a delete or disable of fd 8 in any kevent syscall) ... All on newest libuv 1.x on OS X 10.11.3
23:43:21  <bwoebi>oh well
23:43:34  <bwoebi>I see what's going wrong, 5 minutes after I post here <.<
23:43:48  <bwoebi>the fd passed to kevent changed …
23:43:50  <bwoebi>sorry :-/
23:54:24  * fourqchanged nick to fourq|away
23:59:33  * fourq|awaychanged nick to fourq