01:25:09  * Something12joined
02:20:22  * DarkGodquit (Ping timeout: 260 seconds)
02:23:41  * squeekquit (Ping timeout: 250 seconds)
02:25:53  * squeekjoined
03:32:13  * travis-cijoined
03:32:14  <travis-ci>luvit/luvit#2607 (bugs/many_processes - 00fe21f : Ryan Phillips): The build has errored.
03:32:15  <travis-ci>Change view : https://github.com/luvit/luvit/compare/db3292afd3d6...00fe21fbf019
03:32:15  <travis-ci>Build details : https://travis-ci.org/luvit/luvit/builds/91966248
03:32:15  * travis-cipart
03:48:18  * travis-cijoined
03:48:19  <travis-ci>luvit/luvit#2608 (fixes/lots_of_processes - 3aa653b : Ryan Phillips): The build has errored.
03:48:19  <travis-ci>Change view : https://github.com/luvit/luvit/commit/3aa653b5624e
03:48:19  <travis-ci>Build details : https://travis-ci.org/luvit/luvit/builds/91968311
03:48:19  * travis-cipart
06:21:33  * SkyRocknRolljoined
07:22:27  * Something12quit (Ping timeout: 255 seconds)
08:42:45  * DarkGodjoined
11:01:22  * rjequit (Excess Flood)
11:01:37  * rjejoined
13:00:11  <rphillips>good morning
13:16:12  * SkyRocknRollquit (Ping timeout: 265 seconds)
14:10:21  * urzdsjoined
14:11:58  * urzdsquit (Changing host)
14:11:58  * urzdsjoined
14:57:15  <rphillips>creationix: around?
15:30:12  <urzds>Does anyone know how to workaround this issue in Tap? https://github.com/luvit/luvit/issues/832
15:39:48  <rphillips>urzds: move the server:close before the asserts
15:41:35  <urzds>rphillips: Indeed, that works. Thanks.
15:42:06  <rphillips>np
15:42:38  <urzds>I wonder why that happens. Shouldn't assert() throw an error(), which should kill the app?
15:42:56  <urzds>Or rather: Be caught by Tap?
15:44:22  <urzds>rphillips: Re: your answer on GH: Is Tap unable to catch/output anything while the eventloop is active?
15:45:27  <rphillips>i would expect so
15:45:40  <rphillips>might be a bug
15:47:20  <rphillips>tap does an xpcall
15:47:43  <rphillips>one would think an assert would be caught
16:41:45  <urzds>What do you recommend to use for NodeJS-style futures/promises?
16:42:06  <urzds>I tried several (https://github.com/luvit/luvit/issues/827), but they all have their issues...
16:47:37  <rphillips>i would suggest looking at the coroutine modules tim wrote
16:49:01  <urzds>rphillips: Do you have a link at hand?
16:49:11  <urzds>(or a more specific name)
16:49:15  <rphillips>https://github.com/luvit/lit/tree/master/deps
16:49:19  <rphillips>all the coro-* libraries
16:49:22  <rphillips>they are in lit as well
16:49:43  <rphillips>you can write 'blocking' style but have all the benefits of async
16:54:29  <urzds>Just because I noticed it again: Do you have an idea why the global "exports" table was chosen to carry module meta information?
16:54:54  <urzds>That seems like half a step back to pre Lua 5.2 times...
16:59:48  <urzds>And regarding coro: Do you mean: "Use coro as an example how to build promises" or "core contains a library for promises"? Because I can't find the latter...
17:00:13  * travis-cijoined
17:00:14  <travis-ci>luvit/luvi#791 (fixes/add_holy_build_support - 8d3ee2d : Ryan Phillips): The build passed.
17:00:14  <travis-ci>Change view : https://github.com/luvit/luvi/commit/8d3ee2d0f48b
17:00:14  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92087211
17:00:14  * travis-cipart
17:19:05  <urzds>Ok, I guess I get the gist... The common pattern seems to be the makeCallback() function, which produces a function that resumes the thread from which it makeCallback was originally called. After calling passing that function into NodeJS, coroutine.yield() is called, returning the results from inside NodeJS.
17:19:52  <urzds>Now my naive mind assumes that this leaves the NodeJS threads hanging, because they will never be resumed by anyone... Is that true?
17:19:58  <urzds>@rphillips ?
17:36:11  * SkyRocknRoll_quit (Ping timeout: 276 seconds)
17:38:32  <rphillips>that is correct
17:38:50  <rphillips>we have found that mixing coroutines and callbacks is fraught with issues
17:39:27  <rphillips>so no, there isn't really a promises library. the coroutine way seems to be pretty good though
17:41:56  <urzds>So you say that indeed calling coroutine.resume from arbitrary threads (e.g. from withing libuv) creates trouble? But still it is the recommended way of doing things?
17:50:39  * SkyRocknRoll_joined
17:59:56  <rphillips>tim knows more about it... i just know when we mixed callbacks (luvit style) with coroutines we had some issues
18:16:08  * DarkGodquit (Ping timeout: 246 seconds)
18:31:52  * travis-cijoined
18:31:53  <travis-ci>luvit/luvi#792 (fixes/add_holy_build_support - 0ba25c3 : Ryan Phillips): The build passed.
18:31:53  <travis-ci>Change view : https://github.com/luvit/luvi/compare/8d3ee2d0f48b...0ba25c39dc8a
18:31:53  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92105315
18:31:53  * travis-cipart
18:34:36  <urzds>rphillips: Do you have a suggestion for this? https://github.com/luvit/luvit/issues/835 ("unexpect", which shall be roughly equal to "function() assert(false) end")
18:34:59  * SkyRocknRoll_quit (Remote host closed the connection)
18:35:03  <rphillips>yeah, that is a good idea
18:44:00  * travis-cijoined
18:44:01  <travis-ci>luvit/luvi#793 (fixes/add_holy_build_support - 16603ef : Ryan Phillips): The build passed.
18:44:01  <travis-ci>Change view : https://github.com/luvit/luvi/compare/0ba25c39dc8a...16603efc443d
18:44:01  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92107288
18:44:01  * travis-cipart
18:46:31  * travis-cijoined
18:46:32  <travis-ci>luvit/luvi#795 (fixes/add_holy_build_support - de3de10 : Ryan Phillips): The build passed.
18:46:32  <travis-ci>Change view : https://github.com/luvit/luvi/compare/16603efc443d...de3de10cc229
18:46:32  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92107963
18:46:32  * travis-cipart
19:28:23  * DarkGodjoined
19:31:07  * travis-cijoined
19:31:08  <travis-ci>luvit/luvi#797 (fixes/add_holy_build_support - f2eb2be : Ryan Phillips): The build passed.
19:31:08  <travis-ci>Change view : https://github.com/luvit/luvi/compare/de3de10cc229...f2eb2beff65b
19:31:08  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92117329
19:31:08  * travis-cipart
19:45:26  * travis-cijoined
19:45:27  <travis-ci>luvit/luvi#799 (fixes/add_holy_build_support - 0a59ca5 : Ryan Phillips): The build passed.
19:45:27  <travis-ci>Change view : https://github.com/luvit/luvi/compare/f2eb2beff65b...0a59ca5c3b7a
19:45:27  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92119643
19:45:27  * travis-cipart
19:45:43  <urzds>Does Luvit have a deepcopy() available somewhere?
19:46:50  <urzds>There is "deep-equal" and "utils".deep_equal, but I don't see a deep-copy...
20:09:13  <rphillips>no deep copy by default
20:11:33  * travis-cijoined
20:11:34  <travis-ci>luvit/luvi#801 (fixes/add_holy_build_support - abb68ee : Ryan Phillips): The build passed.
20:11:34  <travis-ci>Change view : https://github.com/luvit/luvi/compare/0a59ca5c3b7a...abb68eedb774
20:11:34  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92124580
20:11:34  * travis-cipart
20:46:59  * piernovquit (Ping timeout: 250 seconds)
20:47:19  * piernovjoined
21:54:50  * travis-cijoined
21:54:51  <travis-ci>luvit/luvi#803 (fixes/add_holy_build_support - 6959f71 : Ryan Phillips): The build passed.
21:54:51  <travis-ci>Change view : https://github.com/luvit/luvi/compare/abb68eedb774...6959f71f2952
21:54:51  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92145844
21:54:51  * travis-cipart
22:00:21  * travis-cijoined
22:00:22  <travis-ci>luvit/luvi#806 (fixes/add_holy_build_support - a3a275f : Ryan Phillips): The build passed.
22:00:22  <travis-ci>Change view : https://github.com/luvit/luvi/compare/6959f71f2952...a3a275f585fe
22:00:22  <travis-ci>Build details : https://travis-ci.org/luvit/luvi/builds/92146683
22:00:22  * travis-cipart