00:00:40  * travis-cijoined
00:00:41  <travis-ci>luvit/luvit#2770 (master - d648754 : Ryan Phillips): The build passed.
00:00:41  <travis-ci>Change view : https://github.com/luvit/luvit/compare/8c0df114ecbe...d6487545f9a1
00:00:41  <travis-ci>Build details : https://travis-ci.org/luvit/luvit/builds/107907065
00:00:41  * travis-cipart
00:05:30  * Haragethquit (Remote host closed the connection)
00:13:34  <rphillips>got the stack re-released
00:13:46  <rphillips>rhel 32bit passed for me
00:45:23  * DarkGodquit (Quit: Leaving)
00:51:15  * Haragethjoined
00:59:00  * therebelrobotquit (Ping timeout: 256 seconds)
01:33:50  * Something12quit (Ping timeout: 276 seconds)
01:48:05  * Haragethquit (Remote host closed the connection)
03:17:00  * tlhunterjoined
05:17:01  * SkyRocknRolljoined
06:07:28  * SkyRocknRollquit (Ping timeout: 250 seconds)
06:16:03  * tlhunterquit (Quit: WeeChat 0.4.2)
06:36:28  * SkyRocknRolljoined
07:40:08  * SkyRocknRollquit (Ping timeout: 252 seconds)
09:33:13  * SkyRocknRolljoined
09:35:18  * Lukcjoined
09:35:20  <Lukc>_o/
09:35:31  <Lukc>Anyone ever built or used luvit on musl/Linux ?
09:55:15  <Lukc>Well. I guess it builds and runs fine on it. :)
09:55:26  <Lukc>Thanks for your hard work. o/
09:55:33  * Lukcpart
12:53:12  * SkyRocknRollquit (Remote host closed the connection)
13:52:00  <rphillips>good morning
16:14:35  * therebelrobotjoined
16:35:25  <creationix>rphillips, mornin'
16:36:03  <creationix>I'll start on the 32 bit builds for the new luvi
16:36:07  <creationix>I expect it to work
16:36:30  <rphillips>cool
16:36:40  <rphillips>yeah, the rhel 32bit worked for me
16:39:51  <creationix>segfault
16:40:31  <creationix>FAILED: cd /home/tim/luvi/build && /home/tim/luvi/build/deps/luv/luajit -bg /home/tim/luvi/src/lua/luvibundle.lua /home/tim/luvi/build/jitted_tmp/src/lua/luvibundle.lua_luvi_generated.o
16:40:31  <creationix>Segmentation fault (core dumped)
16:41:25  <creationix>pretty short backtrace too
16:41:25  <creationix>#0 0x080bc8a8 in lj_BC_IFUNCV ()
16:41:25  <creationix>#1 0x080acfa0 in lua_cpcall ()
16:41:25  <creationix>#2 0x0804baae in main ()
16:44:28  <rphillips>just for sanity, make clean?
16:44:49  <rphillips>make sure the build/deps/luvit/luajit/src folder is cleaned as well
16:57:51  <creationix>rm -rf luvi; [email protected]:luvit/luvi.git
16:57:54  <creationix>that should do it
16:58:01  <creationix>*git clone --recursive [email protected]:luvit/luvi.git
16:58:24  <creationix>armv7 and bsd both compiled no problem
16:59:03  <creationix>rphillips , that fixed it
16:59:19  <creationix>the publish script tried to clean state before running, but I guess it didn't reach the deeper submodules
17:00:38  <creationix>Ok, added everything except armv6 (which is still building) https://github.com/luvit/luvi/releases
17:01:06  <creationix>rphillips, shall I publish a new luv to luarocks with the /.S/.s/ fix?
17:06:49  <creationix>yay, now I can `luarocks install luv` on linux 32
17:15:43  <rphillips>+1
17:16:09  <rphillips>if luajit is built in the submodule I've noticed it messes with the cmake build
17:18:13  * travis-cijoined
17:18:14  <travis-ci>luvit/luv#195 (1.8.0-4 - 3f11930 : Tim Caswell): The build passed.
17:18:14  <travis-ci>Change view : https://github.com/luvit/luv/compare/0d8b3fdc701c...62618254e3ff
17:18:14  <travis-ci>Build details : https://travis-ci.org/luvit/luv/builds/108074471
17:18:14  * travis-cipart
17:45:20  <creationix>the amalg build is still going on my armv6 pi, hopefully it eventually finishes
18:32:52  <creationix>rphillips, if we publish basic crypto such as md5 and sha1 to lit, then lua (plain lua) can run the API server using luvit-loader
18:34:25  <creationix>Activity Monitor claims it's running at 14.4 MB memory
18:34:54  <creationix>strange, luvit uses 7.4 MB
18:35:16  <creationix>who would have thought lua 5.2.4 from homebrew used so much ram
18:35:28  <creationix>(It was using luv and lua bit-op from luarocks)
19:21:39  * DarkGodjoined
21:29:31  <creationix>Alright, websocket-codec no longer depends on openssl, it's portable outside luvit
21:29:44  <creationix>same for the new coro-postgres we made for super agent
21:30:08  <creationix>tls client is still the elephant in the room I can't avoid, but not all apps need https clients
21:30:51  <creationix>luvit and lit production servers, for example, are only http and ws servers sitting behing nginx which applies tls for them
21:49:33  <rphillips>http://www.lua.org/wshop16.html
21:56:28  <creationix>SF, we should go
21:56:36  <rphillips>yeah
21:56:45  <creationix>maybe even plan MaaS around that time
21:56:49  * Haragethjoined
21:56:51  <creationix>*MaaS week
21:56:52  <rphillips>that is a good idea
21:58:01  <creationix>daurnimator, you going to lua workshop 2016?
22:20:21  <creationix>rphillips, running api server on luvit, lua, and luvit for comparison https://github.com/virgo-agent-toolkit/super-agent/blob/master/api/main.lua#L21-L32
22:20:24  <creationix>luajit by itself is nice
22:21:56  <rphillips>impressive
22:39:30  * Haragethquit (Ping timeout: 256 seconds)
22:43:44  <creationix>with the main.lua shim, it's also a valid luvi app
22:43:55  <creationix>so making a single-file deployment of the API server will be trivial
22:44:03  <creationix>or you could debug using luajit directly
22:44:19  <creationix>giving us access to the debuggers and other tools for luajit
23:00:04  * Adam____joined
23:01:58  <creationix>yeah, finally, a luvi app using the tiny build!
23:02:09  <creationix>api-server is under 1mb when built with luvi
23:06:09  <creationix>I think this workflow will work (Use luvi or luajit in development, use luvi for single-file deployment)
23:06:14  <creationix>no need for luvit at all
23:06:16  <daurnimator>creationix: don't think I have the budget.
23:06:28  <creationix>daurnimator, yeah, long flight
23:06:58  <daurnimator>on the other hand, maybe they'll need me in the usa for other reasons; and I'll try and get the timing right
23:11:46  <creationix>yeah, I have a trip to sf around that time, I'll see if we can make it coincide