Paulo Lopes

@javadevmtl so you're saying that the endHandler triggers before the end() completes? If that is the case, then the bug is that the `endHandler()` should be only after it completes...

Chasing down the endHandler call, it goes to vertx-core. There is is called once the final `buffer` is send to the network usually right after the `bodyHandler`. Once the data...

@omg1492 thanks for the thorough report. I'm rebuilding a Windows 11 VM to test this scenario. I'll be honest, most of the development and testing is happening on Linux, so...

@omg1492 it seems that there's a behavior change in graal debugger. The inspect will always require a port, plus breaking at start now seems to be true by default which...

The latest release 0.16.3 fixed the start of the debugger however there's a regression on Graal that doesn't show any sources so breakpoints don't work at the moment. I'm fixing...

For reasons, the supported way to debug is using `chrome-debugger`. This means that the docs should be updated to avoid the old ways.

I've been looking at this. It seems that the builtin debugger doesn't fully work **anymore** with the vscode default debugger. I've updated the docs. There are 2 way of debugging:...

Hi @tahonaPL, thanks for your message! There have been many requests about adding some shims for node modules, I don't think this would be very complex, I think the major...

some automation has been done to generate manuals from the core vert.x APIs. There are issues that will be addressed as more improvements to the automation is added.

@romero @MeYoGui, could you tell an example string representation? I'm not sure if I follow the full request here. Are you looking for something like? ``` http://example.com/a%25b?x%20yz ``` This IMHO...