00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:10  * ircretaryjoined
01:02:53  * rmgjoined
01:07:21  * rmgquit (Ping timeout: 244 seconds)
02:10:51  * inolenquit (Quit: Leaving.)
02:11:28  * jgijoined
03:19:55  * jgiquit (Quit: jgi)
04:14:13  * jgijoined
04:52:34  * seishunjoined
05:17:25  * tellnesquit (Ping timeout: 240 seconds)
05:19:12  * jgiquit (Quit: jgi)
05:28:16  * jgijoined
05:33:23  * jgiquit (Quit: jgi)
05:36:17  * tellnesjoined
06:00:56  * mmickojoined
06:25:39  * seishunquit (Ping timeout: 250 seconds)
07:07:12  * stagasjoined
07:07:53  * SergeiRNDjoined
07:33:02  * rendarjoined
07:42:41  * roxlujoined
08:31:03  <saghul>jwilm_: they serve different purposes, the threadpool (what backs uv_queue_work) uses async handles
08:36:25  * kenansulaymanquit (Ping timeout: 264 seconds)
09:21:06  * inolenjoined
09:33:07  * reqsharkquit (Quit: Be back later ...)
09:33:48  * roxluquit (Quit: My Mac has gone to sleep. ZZZzzz…)
09:38:12  * roxlujoined
10:21:16  <rendar>saghul: what are 'they'?
10:26:46  * stagasquit (Ping timeout: 246 seconds)
10:40:12  * jasnelljoined
10:56:49  * SergeiRNDquit (Quit: Leaving.)
11:00:40  * SergeiRNDjoined
11:11:20  * SergeiRNDquit (Quit: Leaving.)
11:38:35  * kenansulaymanjoined
11:38:59  * kenansulaymanchanged nick to Guest50310
11:39:12  * niskaquit (Ping timeout: 264 seconds)
11:43:55  * SergeiRNDjoined
11:45:13  * niskajoined
11:46:17  * jasnellquit (Remote host closed the connection)
11:59:36  * jasnelljoined
12:00:37  * jasnellquit (Read error: Connection reset by peer)
12:01:22  * jasnelljoined
12:04:09  * Guest50310quit (Changing host)
12:04:09  * Guest50310joined
12:05:51  * Guest50310changed nick to kenansulayman
12:29:37  * jasnellquit (Ping timeout: 246 seconds)
12:37:30  * rmgjoined
12:41:54  * rmgquit (Ping timeout: 250 seconds)
12:54:36  <saghul>rendar: async handles vs uv_work_t requests
13:00:25  <rendar>saghul: i see
13:24:28  * thefourtheyequit (Quit: Connection closed for inactivity)
13:42:40  * jasnell_joined
13:45:55  * jasnelljoined
13:48:04  * jasnellquit (Read error: Connection reset by peer)
13:48:12  * jasnell_quit (Ping timeout: 250 seconds)
13:50:52  * jasnelljoined
13:55:06  * jasnell_joined
13:55:19  * jasnellquit (Ping timeout: 255 seconds)
13:57:59  * jasnelljoined
13:58:38  * jasnell_quit (Read error: Connection reset by peer)
14:02:08  * jasnell_joined
14:02:36  * jasnell_quit (Remote host closed the connection)
14:04:37  * jasnellquit (Ping timeout: 264 seconds)
14:04:38  * alexforsterjoined
14:09:00  * jasnelljoined
14:11:39  * s3shsquit (Quit: Computer has gone to sleep.)
14:18:44  * jasnellquit (Remote host closed the connection)
14:21:08  * jasnelljoined
14:21:33  * jasnellquit (Read error: Connection reset by peer)
14:22:59  * jasnelljoined
14:24:06  <jwilm_>saghul: I perhaps asked the wrong question. The uv_work implementation keeps a queue of completed on the provided loop handle. After completing work, it locks the mutex for that queue, appends the completed work item, and notifies the work async handle on the loop. In an environment where the number of worker threads is high, that lock could have a lot of contention. Using an async handle for each work request instead of the shared queue would prevent that.
14:26:10  <jwilm_>saghul: I am just trying to understand why the current implementation is what it is.
14:28:20  * davi_joined
14:28:30  * mmickoquit (Ping timeout: 250 seconds)
14:28:44  * davi_changed nick to Guest64984
14:33:13  * jasnellquit (Remote host closed the connection)
14:34:39  * jasnelljoined
14:36:58  * AlexisMochaquit (Ping timeout: 244 seconds)
14:38:17  * rmgjoined
14:39:10  * jgijoined
14:42:57  * rmgquit (Ping timeout: 272 seconds)
14:44:56  * evanlucasjoined
14:48:46  * jasnellquit (Remote host closed the connection)
14:49:10  * jasnelljoined
14:56:21  * s3shsjoined
14:57:08  * seishunjoined
14:58:51  * felipealmeidajoined
15:03:04  * jgiquit (Quit: jgi)
15:15:25  * reqsharkjoined
15:36:14  * niskaquit (Ping timeout: 240 seconds)
15:43:47  * niskajoined
15:49:03  * jasnellquit (Remote host closed the connection)
15:51:29  * SergeiRNDquit (Quit: Leaving.)
15:55:24  * rmgjoined
15:59:53  * avalanche123joined
16:01:46  * jgijoined
16:03:58  * reqsharkquit (Quit: Be back later ...)
16:13:01  * s3shsquit (Ping timeout: 255 seconds)
16:13:06  * roxluquit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:19:34  * avalanche123quit (Remote host closed the connection)
16:23:46  * alexforsterquit (Read error: Connection reset by peer)
16:27:51  * reqsharkjoined
17:18:54  * qardjoined
17:48:03  * avalanche123joined
18:07:59  * dap_joined
18:09:25  * qardquit (Ping timeout: 264 seconds)
18:14:14  * qardjoined
18:16:23  * roxlujoined
18:16:49  * Guest64984quit (Ping timeout: 246 seconds)
18:55:50  * evanlucasquit (Ping timeout: 246 seconds)
18:57:08  * davi__joined
19:00:54  * Ralithquit (Ping timeout: 256 seconds)
19:08:23  * qardquit (Quit: Textual IRC Client: www.textualapp.com)
19:18:50  * Ralithjoined
19:36:17  * rendarquit (Ping timeout: 265 seconds)
19:42:03  * rendarjoined
20:04:22  * qardjoined
20:13:33  * seishunquit (Read error: Connection reset by peer)
20:23:52  * davi__quit (Ping timeout: 246 seconds)
20:28:45  * jgiquit (Quit: jgi)
20:35:06  <saghul>jwilm_: definitely a possibility worth exploring!
20:49:22  * roxluquit (Quit: My Mac has gone to sleep. ZZZzzz…)
20:51:47  * inolenquit (Ping timeout: 240 seconds)
20:56:35  * WalrusPony1joined
20:57:25  * WalrusPonyquit (Ping timeout: 252 seconds)
21:01:14  * evanlucasjoined
21:12:28  * s3shsjoined
21:15:57  * jgijoined
21:41:13  * stagasjoined
22:01:48  * inolenjoined
22:02:55  * stagasquit (Ping timeout: 246 seconds)
22:15:20  * evanlucasquit (Quit: Textual IRC Client: www.textualapp.com)
22:17:59  * jasnelljoined
23:08:52  * rendarquit
23:11:43  * jgiquit (Quit: jgi)
23:13:57  * jgijoined
23:16:30  * alexforsterjoined
23:16:51  * alexforsterquit (Client Quit)
23:22:01  * saapasquit (Ping timeout: 264 seconds)
23:22:18  <jeremyw>Any Windows API experts here? For issue 505, I'm not seeing libuv doing anything out of the ordinary: https://github.com/libuv/libuv/issues/505
23:23:07  <jeremyw>I've not inspected the user's code much but debugging isn't producing the error being reported and I see the actual assertion failure happening because a Windows API says that there are no more socket descriptors.
23:24:49  * txdv_joined
23:25:17  * txdvquit (Ping timeout: 250 seconds)
23:33:47  * saapasjoined
23:48:04  * jasnellquit (Remote host closed the connection)
23:52:05  * s3shsquit (Quit: Computer has gone to sleep.)