Philippus Baalman

ping @softprops

I'm guessing you're using the `kamon-bundle` dependency? I think this is because the kamon-akka reference.conf has these lines: ``` "kamon.instrumentation.akka.instrumentations.akka_25.DispatcherInstrumentation", "kamon.instrumentation.akka.instrumentations.akka_26.DispatcherInstrumentation", ``` and ``` "kamon.instrumentation.akka.instrumentations.akka_25.remote.RemotingInstrumentation", "kamon.instrumentation.akka.instrumentations.akka_26.remote.RemotingInstrumentation" ``` but the akka...

The junit `-q` parameter is no longer supported, since https://github.com/scala-native/scala-native/pull/3425. I've created https://github.com/scala/scala-collection-contrib/pull/243 to remove it.

You can also use the GitHub chatbot-virtual-assistant at https://support.github.com/contact?tags=rr-forks&subject=Detach%20Fork&flow=detach_fork to detach the fork from the original.

If I try it in Kibana, I get the same result. So, it's standard Elasticsearch behaviour. https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-exists.html. Might be a bug though, it seems to me that your expectations are...

You can set the `allow_no_indices` parameter to false to get the required behaviour, something like: ``` client.execute { indexExists("asdsadasd*").copy(indicesOptions = Some(IndicesOptionsRequest(allowNoIndices = false))) }.await.result.isExists ```

Sounds like a good addition!

@NikKozh Would you mind if I started working on adding this API?

Maybe it's a Jenkins thing? https://scala-ci.typesafe.com/job/scala-2.12.x-validate-main/5414/console says "No space left on device".

Is still still an issue after https://github.com/apache/pekko-http/pull/488 ?