Ryan Liptak
Ryan Liptak
> > [Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.](https://travis-ci.org/) > > We'll probably want to migrate our travis stuff to Github...
According to https://github.com/libuv/libuv/issues/2658, pipes to file descriptors are fraught with problems. This is part of what's causing https://github.com/luvit/luvit/issues/1083 and https://github.com/luvit/luvit/issues/1023 Luvit currently creates pipes to `fd` when stdout/stdin come from...
This is a divergence from Lua's `require` within Luvit's `require`, presumably due to Luvit trying to handle relative requires. Example: ``` test.lua luatest.lua deps/ foo/ bar.lua ``` `luvit test.lua` with...
From #709: > There is still a lingering broken edge case when extremely large inputs are sent. If they are so large that the onKey call is broken up into...
With an init.lua of: ``` lua p(process.argv) ``` and a main.lua of ``` lua return require('luvit')(function (...) return require('.') end, ...) ``` `luvit . arg1 arg2` will output: ``` lua...
- [x] https://github.com/luvit/luv/pull/412 [`uv_stream_get_write_queue_size`](http://docs.libuv.org/en/v1.x/stream.html#c.uv_stream_get_write_queue_size); see also the non-standard `luv` function `tcp_write_queue_size`, presumably bound before `uv_stream_get_write_queue_size` was added - [x] [`uv_loop_configure`](http://docs.libuv.org/en/v1.x/loop.html#c.uv_loop_configure) (#103, https://github.com/luvit/luv/pull/496) - [ ] [`uv_setup_args`](http://docs.libuv.org/en/v1.x/misc.html#c.uv_setup_args) (#264); I don't think...
In setting up CI with Github Actions (https://github.com/luvit/luv/pull/551), the valgrind step is reporting leaks (and I can reproduce the leaks locally). It happens with multiple tests (not sure of everything...
Currently, any runtime errors within a callback don't affect the exit code of Lua (they are just printed to stderr and then execution continues). This seems to have changed in...
See #414 and #436. This is a more general problem than I thought. There are two things here: 1. It's possible for Lua to be called out to during lua_close...
From https://github.com/luvit/luv/issues/127#issuecomment-449615737 > Another unrelated thing (which probably requires a separate issue to be opened) is that one must be very careful when converting stack values to strings via any...