Yufu Zhao

I can't run it either. It's core dumped. ``` $ RUST_BACKTRACE=1 RUST_BACKTRACE=full ./devfiler-appimage-x86_64.AppImage 2024-04-20T17:55:25.566483Z INFO devfiler::collector: Collector listening on 0.0.0.0:11000 thread 'main' panicked at src/main.rs:29:35: called `Result::unwrap()` on an `Err`...

@athre0z Sorry, I do not have much knowledge of Wayland. I'm not executing from a terminal in a desktop session, but from a terminal on a remote connection via ssh....

Please move this forward @hbagdi @kikito

@kikito I read the RFC and W3C specifications carefully, and I think the behavior of stripping the port part(if it is equal to the default value) is reasonable even though...

I think the concerns raised by Apao and Enrique are valid. Considering that it seems like a potentially breaking change and doesn't have any substantial impact on functionality, I lean...

The issue is sort of *conditionally* fixed. That is, when you send a JSON request it works (after this PR #11091), but when you send a form data request it...

@catbro666 What about your thoughts?

@tobernguyen Don't forget to change the `--lock-timeout` arg as well, and it can only be passed in via kong cli args and does not support environment variables.

> How feasible it is to expect that if "the thing" doesn't happen in 5 secs, it will happen in 10 secs? I don't have any quantifiable data to provide...

It is highly recommended to use the latest go-pdk version, currently `0.10.0`. We did some refactoring for this in 3.5. For details, please see: - https://github.com/Kong/kong/pull/11819 - https://github.com/Kong/go-pdk/pull/158