00:06:48  <rphillips>yeah, i got the same error message
00:15:37  <rje>rphillips, am looking into manually initializng the dll with the new exe name. i'm going down that path of the dll load error handling (for finding the exe symbols) needs to be in the dll
00:16:37  <rje>rphillips, my current idea is to build a lib with luvi that contains the dll (exe) load handler
00:18:01  <rphillips>if we have a luvi.dll then we will probably not need to munge the name anyway
00:18:48  <dan336>so is it possible to bundle a library with lit in a portable way? and how does loading it work?
00:19:04  <dan336>does it write it to disk and the read it?
00:38:09  <rphillips>dan336: a binary library or a lua one?
00:38:21  <dan336>binary.
00:39:18  <rphillips>dan336: https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent/tree/3fcb481680a3dfdd10368c27b0726c9c1b06635c/libs
00:39:25  <rphillips>you want to do something like this
00:39:34  <rphillips>binary folders and the sigar.lua is the loader
00:40:32  <dan336>got it, then the require writes it to disk and then loads it.
00:42:01  <dan336>so another question, why don't you just link the binary libraries into the resultant executable created with `lit make`?
00:43:23  <dan336>i realize that that step is a bit more complex then I just made it our to be, but wouldn't it solve a lot of strange issues with loading the libraries? (dlls on windows etc.)
00:46:37  <dan336>also memory wouldn't be doubled for all binary libraries included.
01:40:55  <rphillips>dan336: that is what happens
01:41:05  <rphillips>https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent/blob/3fcb481680a3dfdd10368c27b0726c9c1b06635c/package.lua#L10
01:41:30  <rphillips>tim wrote up some docs on it https://github.com/luvit/lit/wiki/Publishing-Compiled-Code
01:41:55  <rphillips>a `lit make` will only pull in the ARCH's binaries
01:45:31  * travis-cijoined
01:45:33  <travis-ci>luvit/luvit#1804 (luvi-up - 72ad682 : Ryan Phillips): The build passed.
01:45:33  <travis-ci>Change view : https://github.com/luvit/luvit/compare/57ce6e475ef2...72ad682311cc
01:45:33  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53742984
01:45:33  * travis-cipart
01:48:23  * joconnorquit (Ping timeout: 256 seconds)
02:17:09  * nateratorquit (Quit: naterator)
03:21:29  * DarkGodquit (Ping timeout: 250 seconds)
03:22:28  * dan336quit (Quit: Leaving.)
04:03:23  * dan336joined
04:21:08  * dan336quit (Quit: Leaving.)
04:41:31  * dan336joined
04:42:33  * dan336quit (Client Quit)
08:11:36  * DarkGodjoined
08:57:37  * Akagi201joined
09:29:59  * DarkGodquit (Ping timeout: 252 seconds)
09:30:04  * dg_joined
10:41:53  * dg_quit (Ping timeout: 265 seconds)
10:42:44  * DarkGodjoined
10:57:37  * dg_joined
10:59:02  * DarkGodquit (Ping timeout: 256 seconds)
11:33:41  * dg_quit (Ping timeout: 244 seconds)
11:34:38  * dg_joined
11:48:47  * DarkGodjoined
11:49:09  * dg_quit (Ping timeout: 246 seconds)
12:33:34  * DarkGodquit (Ping timeout: 245 seconds)
12:34:44  * DarkGodjoined
12:43:09  * nateratorjoined
13:16:31  <rphillips>good morning
14:04:14  <rphillips>https://github.com/virgo-agent-toolkit/virgo-base-agent/pull/153
14:14:11  * nateratorquit (Quit: naterator)
14:32:57  * dan336joined
14:38:48  * UniOnjoined
15:07:13  <creationix>mornin
15:08:54  <creationix>rch: rphillips: sorry, it appears I forgot to publish the osx binaries to lit
15:08:56  <creationix>should work how
15:08:59  <creationix>*now
15:09:40  <rphillips>it does! :)
15:09:41  <rphillips>nice
15:09:57  * rchtries again
15:10:03  <rch>heh fun
15:10:16  <rch>love the ascii modal
15:14:00  <creationix>I think this will work well for the workshop runner
15:14:10  <creationix>it’s termbox isntead of ncurses, much simpler and more modern
15:15:05  <creationix>works on raspbrry pi too https://twitter.com/OhMeadhbh/status/575183055968735232
15:40:04  <rphillips>creationix: perhaps we should think about a release
15:40:20  <rphillips>feels almost ready to me
15:41:00  <creationix>rphillips: luvit 1.0 release?
15:41:17  <rphillips>luvit 2, and luvi 1.0
15:41:20  <rphillips>?
15:43:12  <creationix>right, that’s what I meant
15:43:13  <creationix>2.0
15:43:34  <creationix>I have one more change to get into luvi, but it’s not breaking
15:43:53  <creationix>(the bundle.action helper)
15:44:25  <rphillips>oh yeah, that is a good one
15:44:43  <creationix>then I can remove my polyfills from my ffi bindings and shrink luvit/require a bit
15:44:43  <rphillips>i'm going to go through the luvit 2.0 issues
15:44:59  <creationix>I went through them yesterday
15:45:06  <creationix>I put all the tasks to do in the ready queue on waffle
15:45:20  <rphillips>sweet. i'll check there
15:52:03  <rphillips>https://github.com/luvit/luvit/pull/654
15:59:08  * travis-cijoined
15:59:09  <travis-ci>luvit/luvit#1806 (fixes/unicode_json - 4ee1a7c : Ryan Phillips): The build passed.
15:59:09  <travis-ci>Change view : https://github.com/luvit/luvit/compare/a8c8a632262a...4ee1a7c5bc9e
15:59:09  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53819842
15:59:09  * travis-cipart
16:24:31  * SouLjoined
16:28:09  * joconnorjoined
16:30:02  <rphillips>hmm. uv.pipe_connect is returning ENOTSOCK
16:30:02  <creationix>hmm, lit auth is broken. It appears somthing changed on github’s side
16:32:03  <creationix>rphillips: what are you trying to connect to?
16:32:44  <rphillips>domain socket
16:32:59  <rphillips>looks like uv.read_start(pipe_handle...
16:33:18  <rphillips>it's the read_start that is returning ENOTSOCK
16:33:37  * nateratorjoined
16:35:20  <creationix>so did you create the socket with libuv or are you trying to connect to an existing socket?
16:35:28  <rphillips>existing socket
16:39:28  <rphillips>https://gist.github.com/rphillips/9c4a70bd3fed7ffe6285
16:39:32  <rphillips>example app
16:42:20  <creationix>I see, if the pipe doesn’t exist, connect will give ENOENT
16:42:26  * nateratorquit (Quit: naterator)
16:42:32  <creationix>how did you create the test pipe?
16:42:43  <rphillips>socat - PIPE:/tmp/psock
16:44:19  <creationix>I get ECONNREFUSED trying to connect to that one
16:44:23  <creationix>(linux)
16:46:28  * nateratorjoined
16:59:55  * dan336quit (Read error: No route to host)
17:00:48  * travis-cijoined
17:00:49  <travis-ci>luvit/luvi#425 (master - e1a41b5 : Tim Caswell): The build has errored.
17:00:49  <travis-ci>Change view : https://github.com/luvit/luvi/compare/202f779a6d71...e1a41b58d0c3
17:00:49  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53828830
17:00:49  * travis-cipart
17:07:33  <creationix>rphillips: I think luvi 1.0.0 is ready to be tagged
17:07:47  <creationix>I just tested it heavily in luvit and lit on windows, linux, and osx
17:08:01  <creationix>the lit issue was related to my github token being bad in my env
17:08:56  <creationix>I did update lua-openssl, but the changes there looked like just more tests and minor bug fixes. Also that’s why I tested ssl in luvit and lit
17:08:59  <creationix>https://github.com/luvit/luvi/commit/e1a41b58d0c35aa5323c39a1c5e47047c5d416a7
17:10:46  * nateratorquit (Ping timeout: 256 seconds)
17:11:46  <rphillips>nice
17:11:48  <rphillips>+1
17:15:13  <rphillips>creationix: did we bump libuv to the latest?
17:15:23  <creationix>there is no new release
17:15:26  <rphillips>k
17:15:39  <creationix>and the changes since the last release looked somewhat risky
17:20:58  * nateratorjoined
17:21:08  <rphillips>this libuv pipe connect function does some weird stuff
17:21:10  <rphillips>https://github.com/libuv/libuv/blob/v1.x/src/unix/pipe.c#L146
17:21:26  <rphillips>including, changing the handle to a uv_stream
17:26:09  <rphillips>created a 2.1 luvit release and deferred the domain sockets to 2.1
17:27:25  <creationix>ok
17:28:38  * DarkGodquit (Remote host closed the connection)
17:29:50  * DarkGodjoined
17:38:20  <rphillips>should we have mailing lists for lit+luvi?
17:44:46  <creationix>I think the luvit list is fine
17:45:05  <creationix>I have wondered if we want to rebrand anything since the org is “luvit"
17:45:43  <creationix>one idea was rename luvit to luvit.node or node.lua or luvit.io
17:45:49  <creationix>and then luvi could have the luvit name
17:46:07  <rch>io.luvit
17:46:11  <rch>like io.js
17:46:23  <creationix>io.lua?
17:46:27  <rch>io.luv?
18:19:01  * travis-cijoined
18:19:02  <travis-ci>luvit/luvi#426 (v1.0.0 - e1a41b5 : Tim Caswell): The build passed.
18:19:02  <travis-ci>Change view : https://github.com/luvit/luvi/compare/v1.0.0
18:19:02  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53838946
18:19:02  * travis-cipart
18:28:52  <creationix>luvi 1.0.0 binaries uploaded for windows, osx, linux, and freebsd (linux-arm pending build)
18:28:59  <creationix>https://github.com/luvit/luvi/releases/tag/v1.0.0
18:34:12  <creationix>rye is complete enough to host luvit.io if we want to move to that (it’s currently using the node version called wheaty)
18:48:16  <rphillips>would be slick to use rye
18:48:35  <creationix>should we rename anything before announcing luvit 2.0?
18:48:49  <creationix>luvi is kinda of an implementation detail
18:49:09  <rphillips>rename?
18:49:12  <rphillips>binaries? website?
18:49:21  <creationix>though lit (with embedded luvi) seems to be the nexus of everything
18:49:28  <creationix>right, I
18:49:44  <creationix>I’ve gotten feedback from a few people saying the naming is confusing wrt luv/luvi/luvit/lit
18:50:08  <rphillips>yeah, i've heard similar
18:50:10  <rch>we probably need a HISTORY file or wiki or something to explain what's going on
18:50:17  <rch>a flowchart
18:50:22  <rphillips>blog post
18:50:29  <rphillips>not that we have a blog
18:50:36  <creationix>blog post for sure, the luvit readme has some in the intro
18:50:55  <creationix>https://github.com/luvit/luvit/#luvit-20---nodejs-for-the-lua-inventor
18:51:05  <rphillips>perhaps we drop luv from the published literature
18:51:12  <rphillips>luvi, luvit, lit
18:51:26  <creationix>well, even luvi is somewhat hidden, it’s just the runtime
18:51:40  <creationix>but there are things like LUVI_APP and LUVI_TARGET for advanced usage
18:51:42  <rch>luvi = luv + i for include?
18:51:54  <creationix>integrated
18:51:57  <rch>nice
18:52:14  <creationix>yeah, what blog would be post this to?
18:52:19  <creationix>I could post to medium I guess
18:52:31  <rch>or a luvit blog on luvit.io ?
18:53:11  <creationix>that could be cool, rye is somewhat like the howtonode engine
18:54:10  <rphillips>we could write a what's changed within the readme as well
18:54:26  <creationix>rphillips: more than what’s in there already?
18:54:53  <creationix>the existing userbase isn’t that big to begin with, I don’t want to fill up space talking about old luvit
18:55:21  <rphillips>true... the readme is very nice
18:55:43  <rphillips>creationix: we should trim the old cruft at the bottom of the readme
18:55:55  <creationix>for sure
18:56:11  <rphillips>i'll pr it
18:56:48  <creationix>thanks
18:57:49  <rphillips>https://github.com/luvit/luvit/pull/659
18:58:20  * nateratorquit (Quit: naterator)
18:58:43  * nateratorjoined
18:59:05  * nateratorquit (Client Quit)
18:59:07  <creationix>the luvi part is cruft now too, though not as old
18:59:34  <creationix>maybe we should link to the lit wiki pages on creating modules etc
18:59:41  <rphillips>on it
18:59:43  <creationix>and have a section for how to build and install luvit from git and from lit
19:06:44  * travis-cijoined
19:06:45  <travis-ci>luvit/luvit#1810 (luvi-up - 991621c : Tim Caswell): The build passed.
19:06:45  <travis-ci>Change view : https://github.com/luvit/luvit/compare/3f3eed626d29...991621c36c35
19:06:45  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53844497
19:06:45  * travis-cipart
19:08:17  * travis-cijoined
19:08:18  <travis-ci>luvit/luvit#1809 (fixes/remove_all_cruft - 475870e : Ryan Phillips): The build has errored.
19:08:19  <travis-ci>Change view : https://github.com/luvit/luvit/commit/475870e95e6b
19:08:19  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53844423
19:08:19  * travis-cipart
19:13:05  <rphillips>https://github.com/luvit/luvit/pull/660
19:15:29  * travis-cijoined
19:15:30  <travis-ci>luvit/luvit#1812 (fixes/remove_all_cruft - 96d2a0e : Ryan Phillips): The build passed.
19:15:31  <travis-ci>Change view : https://github.com/luvit/luvit/compare/86e8e11e81d7...96d2a0e4ea5a
19:15:31  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53845645
19:15:31  * travis-cipart
19:25:46  <rphillips>rje: https://github.com/luvit/luvit/pull/493
19:25:48  <rphillips>close?
19:33:50  * travis-cijoined
19:33:51  <travis-ci>luvit/luvit#1815 (luvi-up - 0681c12 : Tim Caswell): The build passed.
19:33:51  <travis-ci>Change view : https://github.com/luvit/luvit/compare/991621c36c35...0681c12d10f4
19:33:51  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53847797
19:33:51  * travis-cipart
19:35:17  * Akagi201quit (Ping timeout: 245 seconds)
19:37:14  * Akagi201joined
19:39:22  * travis-cijoined
19:39:23  <travis-ci>luvit/luvit#1811 (fixes/remove_all_cruft - 86e8e11 : Ryan Phillips): The build passed.
19:39:23  <travis-ci>Change view : https://github.com/luvit/luvit/compare/475870e95e6b...86e8e11e81d7
19:39:23  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53844556
19:39:23  * travis-cipart
19:39:34  <rje>rphillips, yes, close
19:44:01  * travis-cijoined
19:44:02  <travis-ci>luvit/luvit#1813 (fixes/add_build - ebd7317 : Ryan Phillips): The build passed.
19:44:02  <travis-ci>Change view : https://github.com/luvit/luvit/commit/ebd73177e1e9
19:44:02  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53846152
19:44:02  * travis-cipart
19:45:02  * nateratorjoined
20:18:20  <rphillips>i would really like to know why the floating point number is printed out at the prompt sometimes
20:26:51  <rphillips>https://github.com/luvit/luvit/pull/661
20:26:52  <rphillips>trivial
20:27:45  <creationix>I only seem to see the floating point number when it fails
20:27:58  <creationix>I fear it’s in luvi
20:28:48  <rphillips>https://github.com/luvit/luvi/blob/master/src/main.c#L97
20:28:50  <rphillips>could be this pcall
20:30:59  <creationix>if it is, then something in lua is throwing the float
20:31:09  <creationix>pcall only returns truthy in case of lua exceptions
20:31:16  <creationix>lua_pcall at least
20:31:50  <creationix>I don’t see the float when lit errors out
20:32:11  <creationix>might be related to init.lua in luvit (since that’s shared between luvit and r-m-a)
20:34:22  <creationix>rphillips: do you still see the floating point using luvi 1.0.0?
20:34:32  <creationix>I did remove a call to uv.stop() that was causing some trouble
20:34:58  <rphillips>let me see
20:37:15  * travis-cijoined
20:37:15  <travis-ci>luvit/luvit#1817 (fixes/init_lua_rng - c613c34 : Ryan Phillips): The build passed.
20:37:15  <travis-ci>Change view : https://github.com/luvit/luvit/commit/c613c34b4ba6
20:37:15  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53855005
20:37:15  * travis-cipart
20:43:21  * travis-cijoined
20:43:22  <travis-ci>luvit/luvi#427 (master - 26d3ace : Ryan Phillips): The build passed.
20:43:22  <travis-ci>Change view : https://github.com/luvit/luvi/compare/e1a41b58d0c3...26d3ace1f166
20:43:22  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53855382
20:43:22  * travis-cipart
20:44:00  * travis-cijoined
20:44:01  <travis-ci>luvit/luvit#1819 (luvi-up - 92da0ef : Ryan Phillips): The build passed.
20:44:02  <travis-ci>Change view : https://github.com/luvit/luvit/compare/81b9f16d78d0...92da0ef63862
20:44:02  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53855728
20:44:02  * travis-cipart
20:46:30  * hdmsjoined
21:10:26  <rphillips>ok. two open tickets for 2.0
21:13:09  <rphillips>https://github.com/gizak/termui
21:13:14  <rphillips>sorta neat
21:14:10  <creationix>termui is neat
21:14:14  <creationix>new luvit.io is live
21:14:28  <creationix>rphillips: so is the float output gone now?
21:14:38  <rphillips>haven't seen it
21:15:00  <rphillips>the powershell commandlet wont' let me scroll and copy it
21:15:47  <creationix>well that’s annoying
21:15:53  <creationix>but I think triple click will get it all
21:16:07  <rphillips>ah yeah, that it does
21:16:17  <creationix>I’m open to anyone improving the style of luvit.io, it’s pretty messy at the moment
21:17:45  <creationix>hmm, runnin http-client example prints the float
21:18:20  <rphillips>we need to change the clone url for luvi in the docs
21:18:22  <rphillips>https://github.com/luvit/luvi.git
21:19:46  <rphillips>https://github.com/luvit/luvi/pull/69
21:20:10  <creationix>yep https is more accessable
21:20:21  <rphillips>it fails to clone on a box without my ssh key
21:23:27  <creationix>yep, [email protected] urls require github ssh keys
21:26:32  * joconnorquit (Read error: Connection reset by peer)
21:26:37  * joconnor_joined
21:28:27  <creationix>rphillips: I’m testing the examples on luvit.io, the http server seems to work fine
21:28:36  <creationix>but the http client exits with floating point number on my mac
21:30:34  <rphillips>hmm. yeah... my test is with the http client as well
21:31:50  * nateratorquit (Quit: naterator)
21:33:18  * SouLquit (Remote host closed the connection)
21:33:29  <creationix>rphillips: I renamed master to legacy and pushed luvi-up over master
21:33:34  <creationix>master is now default on luvit/luvit
21:33:44  <rphillips>sweet
21:34:21  <creationix>is your fixes/remove_all_cruft branch still pending some stuff
21:34:32  <creationix>looks like it’s 8 behind and 3 ahead
21:36:56  * travis-cijoined
21:36:57  <travis-ci>luvit/luvit#1820 (luvi-up - a502bca : Tim Caswell): The build passed.
21:36:57  <travis-ci>Change view : https://github.com/luvit/luvit/compare/92da0ef63862...a502bca2daeb
21:36:57  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53863452
21:36:57  * travis-cipart
21:37:09  * travis-cijoined
21:37:10  <travis-ci>luvit/luvi#430 (master - 400f8e6 : Ryan Phillips): The build passed.
21:37:10  <travis-ci>Change view : https://github.com/luvit/luvi/compare/26d3ace1f166...8731ed478c8e
21:37:10  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53862218
21:37:10  * travis-cipart
21:44:46  * travis-cijoined
21:44:47  <travis-ci>luvit/luvit#1822 (master - a502bca : Tim Caswell): The build passed.
21:44:48  <travis-ci>Change view : https://github.com/luvit/luvit/compare/7510f3650532...a502bca2daeb
21:44:48  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53863839
21:44:48  * travis-cipart
21:46:18  * travis-cijoined
21:46:19  <travis-ci>luvit/luvit#1821 (legacy - 7510f36 : Ryan Phillips): The build passed.
21:46:19  <travis-ci>Change view : https://github.com/luvit/luvit/compare/legacy
21:46:19  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53863698
21:46:19  * travis-cipart
21:47:51  * travis-cijoined
21:47:52  <travis-ci>luvit/luvit#1823 (master - 2e30922 : Tim Caswell): The build passed.
21:47:52  <travis-ci>Change view : https://github.com/luvit/luvit/compare/a502bca2daeb...2e30922444b1
21:47:52  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53864883
21:47:52  * travis-cipart
21:48:50  <rphillips>creationix: my bisect takes me to the convention changes
21:49:01  <rphillips>not saying that is for sure the spot though
21:49:10  <creationix>I was afraid of that, but I have no idea what it is
21:49:46  <rphillips>with your test, do you see the issue with a5c60bb
21:49:48  <rphillips>of the tree
21:49:54  <rphillips>luvit tree*
21:50:10  <rphillips>make sure to make clean
21:51:09  <creationix>no, but I see an error about destroy being nil
21:52:39  <rphillips>hmm
21:53:23  <creationix>I’ve got an idea
21:53:46  <rphillips>ah hah
21:53:53  <rphillips>the coroutine is swallowing the backtrace
21:54:05  <creationix>well, it’s more than that
21:54:26  <creationix>if I wrap the call to main(…) in init.lua with a pcall, the error is a floating point number somehow
21:55:18  <creationix>but yes, the error was falling through the coroutine.wrap() and getting printed as a string
21:55:26  <creationix>but I still don’t know why the error is a number in the first place
21:57:45  <creationix>smells like a luajit bug to me
21:59:28  * travis-cijoined
21:59:28  <travis-ci>luvit/luvit#1824 (master - c13662f : Tim Caswell): The build passed.
21:59:29  <travis-ci>Change view : https://github.com/luvit/luvit/compare/2e30922444b1...c13662fd3f97
21:59:29  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53866608
21:59:29  * travis-cipart
22:03:09  <rphillips>smells like that as well
22:10:26  <creationix>that’s pretty annoying that any uncaught exception prints a number, that’s kinda a blocker
22:10:48  <creationix>also the http-client example needs updating or the http library needs to add destroy
22:11:07  <rphillips>luvi-up head has a destroy
22:11:42  <creationix>then master does too now
22:11:55  <creationix>I wonder what’s throwing the number
22:12:15  <creationix>can I delete luvi-up since we moved to master?
22:12:28  <creationix>that will keep me from accidentally pushing there on my other boxes
22:13:34  <creationix>must be luajit bug, the formatter in xpcall is never called and/or it’s return value is ignored
22:13:38  <creationix>that’s not correct lua behavior
22:15:21  <creationix>it is still the destroy call that’s crashing us
22:15:30  <creationix>if I comment it out the process exits normally
22:19:33  <rphillips>hmm
22:19:53  <rphillips>creationix: by taking the xpcall out, does it return the crash dump?
22:20:37  <creationix>with xpcall, I capture the thrown float, without, it gets logged by luvi’s uncaught exception printer
22:20:48  <creationix>but I can verify that removing coroutine.wrap from luvi fixes the problem
22:21:21  <creationix>perhaps that was too much convention in luvi
22:21:32  <creationix>luvit doesn’t need or want it anyway
22:23:58  <rphillips>hmm. k
22:24:23  <creationix>I guess I’ll just make luvi do less
22:24:35  <creationix>it will make things slightly harder for coro-based code though
22:25:00  <creationix>I could have luvi read package.lua and have a flag for auto-coro behavior
22:25:31  <creationix>or not, I don’t think it fits
22:25:45  <rphillips>perhaps leave it up to the calling application
22:25:53  <creationix>I guess it’s time for another luvi release :/
22:26:14  <creationix>auto-require and auto-pretty-print is very useful and easy to detect
22:26:23  <rphillips>+1
22:26:23  <creationix>I just check for deps/require.lua and deps/pretty-print
22:26:35  <creationix>but auto uv.run and auto coroutine.wrap is problematic
22:26:39  <creationix>and no way to opt out
22:27:09  <creationix>shall we see how fast I can do a luvi release
22:27:46  <creationix>1.0.1 or force push over 1.0.0 since we havn’t announced yet?
22:28:02  <creationix>it’s a pretty big breaking behavior for coro-based apps
22:28:15  <creationix>luvit will just see better error reporting
22:28:38  <rphillips>we could force push over that tag
22:29:20  * creationixdeletes all the binaries and cries a little
22:29:44  <rphillips>though, this destroy not defined
22:30:16  <creationix>right that’s another issue entierly if you want to fix it
22:30:23  <creationix>I’m going to see how fast I can build another luvi and lit
22:31:05  <rphillips>k... looking into this destroy thing
22:36:49  <rphillips>creationix: https://github.com/luvit/luvit/pull/662
22:37:08  <creationix>nice
22:37:19  <creationix>luvi tag updated, starting builds
22:37:29  <creationix>good news is lit won’t need updating since it will get the new luvi automatically
22:37:54  <rphillips>i'm getting paged for dinner every 2 seconds... bbiab
22:41:24  <creationix>doh forgot to update the unit test for the behavior change, force pushing tag again…
22:41:36  * travis-cijoined
22:41:37  <travis-ci>luvit/luvi#431 (master - d26dc03 : Tim Caswell): The build was broken.
22:41:37  <travis-ci>Change view : https://github.com/luvit/luvi/compare/8731ed478c8e...d26dc0386143
22:41:37  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53872261
22:41:37  * travis-cipart
22:47:48  * travis-cijoined
22:47:48  <travis-ci>luvit/luvit#1825 (fixes/net_socket_destroy - 0a3b8a9 : Ryan Phillips): The build failed.
22:47:49  <travis-ci>Change view : https://github.com/luvit/luvit/commit/0a3b8a989b2c
22:47:49  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53872891
22:47:49  * travis-cipart
22:48:00  * travis-cijoined
22:48:01  <travis-ci>luvit/luvi#432 (v1.0.0 - d26dc03 : Tim Caswell): The build was broken.
22:48:01  <travis-ci>Change view : https://github.com/luvit/luvi/compare/d44b13b2e567...30787041c881
22:48:01  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53872711
22:48:01  * travis-cipart
22:56:54  <creationix>alright, binaries for everything except arm boxes is done and published
22:57:06  <creationix>d2a11d3 is the correct v1.0.0 tag
22:59:30  <rphillips>.
23:02:34  <creationix>rphillips: your patch works for me
23:02:45  <rphillips>creationix: i think we should tweak the example on the website as well
23:02:53  <creationix>that’s fine
23:02:56  <rphillips>remove the 'end' event and destroy
23:03:08  <rphillips>it's superfluous
23:03:13  <creationix>sounds good
23:03:22  <creationix>you should have push access to the luvit.io repo
23:03:30  <creationix>it auto publishes
23:03:52  * travis-cijoined
23:03:53  <travis-ci>luvit/luvi#436 (master - d2a11d3 : Tim Caswell): The build was fixed.
23:03:53  <travis-ci>Change view : https://github.com/luvit/luvi/compare/d26dc0386143...d2a11d3bf6e9
23:03:53  <travis-ci>Build details : http://travis-ci.org/luvit/luvi/builds/53874509
23:03:53  * travis-cipart
23:04:15  <creationix>dinner time for me, the builds are done enough you should be getting the new luvi when you build lit and luvit
23:04:21  <creationix>(unless you’re on a tiny arm device)
23:04:32  <rphillips>k
23:06:20  <creationix>hmm, lit may be broken because of the luvi change
23:07:38  <creationix>no, works fine for me on my machines
23:07:42  <creationix>not sure what’s up with the CI boxes
23:09:00  * travis-cijoined
23:09:01  <travis-ci>luvit/luvit#1828 (master - b93e1cb : Tim Caswell): The build passed.
23:09:01  <travis-ci>Change view : https://github.com/luvit/luvit/compare/c13662fd3f97...b93e1cbdba08
23:09:01  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53875954
23:09:01  * travis-cipart
23:09:09  * travis-cijoined
23:09:10  <travis-ci>luvit/luvit#1827 (fixes/net_socket_destroy - c22385e : Ryan Phillips): The build was fixed.
23:09:11  <travis-ci>Change view : https://github.com/luvit/luvit/compare/0a3b8a989b2c...c22385e65a98
23:09:11  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53874878
23:09:11  * travis-cipart
23:09:35  <rphillips>i think it was because the release was pulled
23:12:36  <creationix>the luvi change didn’t uglify my sample coro app too much https://gist.github.com/creationix/f87eb113a7ebad8ba186
23:12:40  <creationix>it’s just more explicit now
23:14:25  <rphillips>does it build on windows
23:14:35  <rphillips>lit build on windows?
23:17:49  <rphillips>linted the examples on the website
23:23:28  <creationix>hmm, the boxes aren’t wide enough for the inline tostring calls
23:23:36  <creationix>we could change the layout of the webpage
23:24:40  * travis-cijoined
23:24:41  <travis-ci>luvit/luvit#1829 (fixes/net_socket_destroy - a20b0bc : Ryan Phillips): The build passed.
23:24:41  <travis-ci>Change view : https://github.com/luvit/luvit/compare/c22385e65a98...a20b0bcff21b
23:24:41  <travis-ci>Build details : http://travis-ci.org/luvit/luvit/builds/53877438
23:24:41  * travis-cipart