The core documentation on how to make requests says to use xxxNow to make request from a client, but those methods are deprecated, e.g., getNow.

I am struggling to test a verticle isolated and all documentation and examples found only show how to test rest endpoints.

Something as simple as this, always fails with timeout

    @Rule
    public RunTestOnContext rule = new RunTestOnContext();

    @Rule
    public Timeout timeout = Timeout.seconds(5L);

    @Test
    public void should_run_verticle(TestContext context) {

Version

• vert.x core: 3.8.2
• vert.x web: 3.8.2

Context

Currently, some of the metrics for HttpServer is provided with path as a tag (in micrometer implementation). In some of our endpoints, we use UUIDs for two of the path parameters, thus the number of meters easily fill up heapspace if there are large number of requests with different UUIDs.

A suggestion will be to provide

Apologies for probably opening this issue in the wrong repo.

https://vertx.io/docs/vertx-pg-client/kotlin/#_handling_arrays

Shows this example query:

client.preparedQuery("SELECT address, (address).city FROM address_book WHERE id=\$$1", Tuple.of(3), { ar ->
....

The \$$1 is not valid Postgres SQL and will throw an Exception. The Java version correctly uses $1.

This would give us a better starting point for getting a Kubernetes cluster up and running in the future.
Maybe also using the GraalVM with native binaries. As we didn't use reflection and other stuff which would prohibit the use of native binaries the only thing now is that we moved to Java 13 and the GraalVM just started to support Java 11.

The generated code works without errors for js, however the generated ts definitions might contain bugs although this isn't critical at runtime it can cause confusion at dev time.

A report should be generated for all modules inside the generator directory after a build is done.

The task should be more or less as follows:

1. Run the generator
2. Run npm cache to cache the undeployed packa

This is a suggestion/question. Given the introduction of asynchronous data access through the sqlclient, should this be the recommended method for doing data access as documented in the java guide? @jponge, wdyt?

In attempting to use the documentationvertx-jooq-rx-reactive/README.md for gradle, I see an import for GenerationTool, but that doesn't seem to be right. Is it really suppose to be import org.jooq.codegen.GenerationTool?

A faux pas on my part, but I have been using Vert.x with Kotlin Coroutines (💖) for almost a year and only just realized that it's possible to generate suspending methods for my own project.

The documentation mentions that:

...Vert.x generates suspending extension methods for all its asynchronous metho

I see my rx API has methods not marked as deprecated which wrap deprecated methods, so as such I never know that I'm using deprecated APIs. Those annotations/javadoc tags should be propagated to the wrapper APIs.

i noticed the readme lacks the instructions like how to get the nubes, how to run the server etc. I didn't find nubes from maven or anywhere. vertx-jersey has a good starter guide here: https://github.com/englishtown/vertx-jersey i was almost going with that until i noticed how terrible their api is compared to yours. to get more hype, starting with the framework has to be as easy as possible so m

Is your feature request related to a problem? Please describe.
It's very easy to forget about updating META-INF/services for ServiceLoader every time HandlerFactory or ActionFactory is created/deleted.

Describe the solution you'd like
An annotation could be used to automaticaly detect factories. One existing solution is [Google's AutoService](https://github.com/google/auto/tree/mast