luv
luv copied to clipboard
luvit
Bare libuv bindings for lua
In a number of places luv stores a long-lived reference to `L` such as [src/luv.c:712](https://github.com/luvit/luv/blob/master/src/luv.c#L712). This is not safe, however - `L` may refer to the current thread (coroutine) that...
I've tried some different methods of installing Luv, but so far i got no sucess. I tried both building from source and installig via Luarocks. When building from source, everything...
Currently work and threads do not support passing userdata. Note: I'm using sol2 defined userdata but this shouldn't matter. Example: ```lua local channel = UserDataChannel.new() local thread_id = uv.new_thread(function(chan) print("channel:...
I made an ad-hoc by-line process output reader and it seems that I found a memory leak. I wrapped into a min working example below. This is supposed to `uv.async_send`...
This test is new with the upgrade to libuv 1.32.0. ``` Uncaught Error: tests/test-tcp.lua:158: assertion failed! stack traceback: [C]: in function 'assert' tests/test-tcp.lua:158: in function 'fn' ./lib/tap.lua:48: in function [C]:...
Evening. I'm interested, why we don't pass client handle in **read_start** callbacks? It will be very convenient when you using external functions: ``` local function callback(client, err, chunk) print(type(client) ==...
Working on documenting `uv_req_t` in #409 According to [libuv](http://docs.libuv.org/en/v1.x/request.html#c.uv_cancel): `uv_fs_t`, `uv_getaddrinfo_t`, `uv_getnameinfo_t` and `uv_work_t` are cancellable. However, `uv_work_t` is not cancellable in luv; [uv.queue_work](https://github.com/luvit/luv/blob/cf89aea836bcc662643ccaa7b7a4f8ac0af9095f/src/work.c#L193) doesn't return any userdata. The request...
Build error
Hi all, I'm getting an error from CMake in my attempt to build a recent version of luv for OpenWrt. Essentially I'm using the makefile here: https://github.com/openwrt/packages/blob/master/lang/luv/Makefile and amending the...
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...