swananan
swananan
Hi, HTTP/3 also faces similar issues in OpenResty. I have been thinking about how to address this problem. For achieving full-duplex communication in both HTTP/2 and HTTP/3, we can consider...
> > I think the root of the actual problem is that client_body_timeout is between reads. Which the nginx folks think is OK (I agree) and the openresty folks do...
> > Thanks! This looks great. Could you add a test for the debuglink resolution? > > Actually thinking of it, given our current integration-test setup this is _probably_ harder...
> > I was initially planning to add UT, haha. However, I realized I needed to hook the std::fs::read function > > unit test works! But why do you need...
@alessandrod could you review this pr? thanks
Hi @alessandrod this PR failed the public api check phase, but I am not sure if it's the root cause, could you help take a look? thanks!
> Can you take a look at the test failure under miri? I looked into this failure and found an exception, **Invalid ELF header size or alignment**, originating from the...
Update: Refer to this link [here](https://lore.kernel.org/bpf/CADxym3b5zGP_zX3cUurqmwfR-dPhDXKx=QoxVG+-5EVtiadnFA@mail.gmail.com/T/). We have two potential solutions. The first is bpf_core_enum_value_exists, which Aya does not yet support. The second solution involves checking for support in user...
> Hi @swananan. > > I closed #970 because scope changed based on a conversation in the Discord channel. The new approach will take longer to implement, but will offer...