07:03:55  * saghuljoined
07:19:51  * saghulquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
07:40:16  * saghuljoined
10:22:20  * saghulquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:20  * mylesborinsjoined
10:46:10  * addaleaxquit
10:46:27  * addaleaxjoined
11:28:58  * saghuljoined
11:29:54  * saghulquit (Client Quit)
11:30:41  * saghuljoined
12:04:31  * joocain2_quit (Ping timeout: 250 seconds)
12:06:11  * joocain2joined
12:38:34  * photexjoined
12:39:03  <photex>howdy!
12:40:00  <photex>I'm confused by a failure of uv_async_send to trigger any callback or a timer to be called after recieving bytes over tcp
12:40:34  <photex>everything runs as expected, but as soon as I've recieved any data my timer stops, and any calls to uv_async_send appear to be ignored
12:40:55  <photex>I do not know what to look at to figure out why this is happening
12:40:57  <photex>any tips?
13:22:26  <photex>Last logging output from my code is coming from the alloc callback
13:22:44  <photex>I can read more data and write data
13:57:09  * saghulquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:05:21  * saghuljoined
15:06:28  * saghulquit (Client Quit)
15:09:55  * saghuljoined
16:07:24  * s4ghuljoined
16:10:35  * saghulquit (Ping timeout: 240 seconds)
16:12:14  * s4ghulquit (Ping timeout: 265 seconds)
16:47:55  <txdv>photex: hard to tell man
16:48:03  <txdv>describing your problem like that is hard to debug
16:48:05  <txdv>you need to show code
17:20:04  * saghuljoined
17:24:35  * saghulquit (Ping timeout: 240 seconds)
19:03:22  <photex>txdv: for sure, I'm trying to reduce this to a simple working example of the problem
19:03:32  <photex>had to go do parent stuff for a few hours