Arnaud Castellanos Galea

Access to the vm outside the handler

2

I want to make a repl, but I'd need access to the internal vm to execute code. I saw pull #9 and it gives access to the vm on initialization,...

Make the handler accept other messages than the http_request

4

Currently the lua actor only accepts http_request messages, but that heavily limits it's functionality, so torchbear apps cannot schedule stuff, cannot have a repl, cannot create new actors, etc.

Currently we are waiting by default for the response ~~~lua local response = client_request.send("google.com") ~~~ exposing futures would look like this ~~~lua local future = client_request.send("google.com") -- we can do...

Should it create the directory or is this sane behaviour?

Gracefully end when address is taken

1

https://actix.rs/api/actix-web/stable/actix_web/server/struct.HttpServer.html#method.bind https://doc.rust-lang.org/nightly/std/io/struct.Error.html

logging improvements

9

- remove actix-something noise in debug and trace mode - remove starting space in lua logs To select the logging level, start torchbear with the `--log` option with the most...

fs entries is working randomly

2

Sometimes it works and some it doesn't, seems to be random at each call of the function. Apparently the rust internal function is sometimes failing, making it return nil instead...

log source module when scope is everything

1

When logging everything (using the log-scope option), which module logged which messages.

Remove prelude and application from settings

2

Currently the *lua_prelude* and *application* settings tell torchbear additional paths from where to include lua packages, but setting additional module paths should be up to the applications, and torchbear should...