Thibault Charbonnier

Thanks for the test case! Long story short, yes as by the Valgrind report, it appears our Lua bridge cannot handle more than one "Lua thread" at a time (`lctx`)....

At first I noticed that in `ngx_http_lua_socket_udp`, the response length is stored in `u->received` which is set to `111` after `ngx_udp_recv`, but later in `ngx_http_lua_socket_udp_receive_retval_handler` it ends up being `0`...

I think we will figure it out; I made good progress this morning, so far both calls resume with the proper `coctx` locally (and proper socket + `u`), just need...

Patch from the `chore/local-builds-llvm` branch which I am deleting (stale): ```patch From 6f017b8a8084cefdad8d278109c4919d0920f7fd Mon Sep 17 00:00:00 2001 From: Hisham Muhammad Date: Wed, 19 Apr 2023 13:55:49 -0300 Subject: [PATCH]...

@hishamhm Should we open a new Wasmer issue so it gets looked at?

Hello, No, there is no mechanism to interact with fuel consumption at the moment. We do not have short or medium term plan for it either. Documentation on fuel consumption...

Do you have a branch somewhere where we could see your modifications on the other nginx integration? This would give me an idea of what to expect. As for the...

> Would you be willing to add argument to the `ngx_wrt_t->call` with name something like fuel? Part of the issue (or should I say "requirements") is that our abstraction of...

Thank you. I also have other concerns with the fuel concept in the context of a reverse-proxy like ours, namely: what behavior to expect when the instance runs out of...

Fair; we use Wasm as a way to extend Kong Gateway (https://github.com/Kong/kong) with non-Lua code (i.e. proxy-wasm-sdk filters). In our case, the code that we run inside of Kong Gateway...