Thibault Charbonnier
Thibault Charbonnier
Kong 3.6.1 has an old version of the module in which I think such a bug can occur. There's issues with local bazel builds of Kong 3.6.1 so I have...
Could we see the full logs? It is worth noting that each worker has its own context_id counter, so context #1 in pid 1341 is not the same as context...
Are there no other logs after the last line of this file? What if you send another request while it hangs? Are there more logs that appear?
So far I have not been able to reproduce this in either of the Kong 3.6.1 or 3.7.1 images. I've been running the above filter in those docker images and...
Nothing seems wrong with the configuration. Could we also see the request the client is making? Headers and body - so we can try to spot anything that could trigger...
Unable to reproduce and lack of activity.
I am unable to locally test the cpp-sdk as the suggested Docker image does not even build. Can you please provide the *full* error.log file? And possibly the `http_wasm_example.wasm` file...
As far as I can tell this `.wasm` file is correctly loaded and all entrypoints functions are properly invoked by ngx_wasm_module. Why the functions themselves don't actually do anything is...
Thanks for looking into it! Either way sounds good to me...