Tomasz Nurkiewicz

+1

It's actually even simpler with Java 8 (which is the primary target for this library) - simply adding `default` methods: ``` java @FunctionalInterface public interface RetryCallable { V call(RetryContext context)...

@felipesere Instead of using "failure callback" you can just register callback on returned `CompletableFuture`: ``` java executor. getWithRetry(() -> new Socket("localhost", 8080)). whenComplete((socket, error) -> { if (socket != null)...

@felipesere It's possible, but much more verbose with `ListenableFuture` API from Guava: ``` java final ListenableFuture future = executor.getWithRetry(new RetryCallable() { @Override public Socket call(RetryContext context) throws Exception { return...

Thank you for this contribution. Can you explain what does it fix? There are no code samples in Markdown (?)

@dependabot rebase

I confirm this is a major issue for me. I tried plain Java kickstart and it [beautifully shows missing resolvers](https://nurkiewicz.com/2019/10/graphql-server-in-java-part-ii.html) on startup, e.g.: ``` Caused by: [...]FieldResolverError: No method or...

Yes, I'm also referring to option `B`. Just like @nort3x I need a sanity check that whatever I run conforms to schema. In other words it's impossible to run application...

Apart from few minor comments I'm more than happy to merge, great work! Can you please address them, especially different usage of Awaitility? I'm not particularly enthusiastic about maven/Gradle dichotomy,...

I get the same behavior on `zsh` with `oh-my-zsh`: ```bash zoxide --version $ zoxide 0.9.3 $ fzf --version 0.42.0 (brew) ``` U have this alias set up: ```bash $ which...