Originally posted on StackOverflow.

The following code crashes with StackOverflowError and the stacktrace shows a long chain of request calls.

import io.reactivex.rxjava3.core.Flowable
import io.reactivex.rxjava3.core.Single
import io.reactivex.rxj

Motivation

Some IDEs like IntelliJ don't display the javadoc custom tags at all in their javadoc popup.

As a consequence, discovering information about the discard and continue support might be difficult.

Searching the HTML version or the source to look for information about support might still be acceptable, but the tags should not be the only places where eg. a caveat or structuring im

Hi! Thanks again for creating ReactiveSwift! I've searched around a bit online and can't find what I'm looking for.

The APIContracts used to include this best p

Some of the benchmarks don't have the correct scala doc, fixing those.

• https://github.com/monix/monix/blob/master/benchmarks/vnext/src/main/scala/monix/benchmarks/AsyncQueueBenchmark.scala#L41
• https://github.com/monix/monix/blob/master/benchmarks/shared/src/main/scala/monix/benchmarks/CoevalAttemptBenchmark.scala#L38
• https://github.com/monix/monix/blob/master/benchmarks/shared/src/main/

Elastic search has a good set of request parameters that the field mapping request case class does not satisfy:
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-mapping.html

https://github.com/sksamuel/elastic4s/blob/1d6f06346be9cd7acd167976d03df2107eec8819/elastic4s-core/src/main/scala/com/sksamuel/elastic4s/requests/indexes/MappingHandlers.scala#L67-L80

Specific

The Alpakka Kafka documentation should show how the classic KafkaConsumerActor is created when the user has a typed actor system.

I expected Validated to have an ap method or something, but I can't seem to find it. The only docs I can see are https://github.com/aol/cyclops/wiki/Validator, which clearly isn't the current implementation, and I notice aol/cyclops#826 as another issue, but I don't see the proposed ap method.

Currently working with the AvroParquet module writing to S3, and I thought it would be nice to inject S3 configuration from application.conf to the AvroParquet as same as it is being done for alpakka-s3.

In such case, importing hadoop configuration would not be required, but optional.

In which being the original code for creating an avro parquet writer to S3 like:

val writer

Please check the reproducible example here: https://github.com/michaelr524/reactor-netty-ssl-leak

mvn clean package
java -jar target/reactor-netty-ssl-leak-1.0-SNAPSHOT.jar 

• Reactor version(s) used: 0.9.4.RELEASE
• Other relevant libraries versions (eg. netty, ...):
• JVM version (javar -version):
  openjdk version "12.0.2" 2019-07-16
  OpenJDK Runtime Environment (build 12.0

I'm not certain this is a bug in the code, but I feel like I've been mislead with the documentation and the behavior doesn't match what I thought I'd expect. I am using v1.22.0

First off, my use-case I think is a bit non-standard so that could be part of the problem. I have a consistent schema (Tables/Databases) that exist in multiple keyspaces (of which I don't know ahead of time, and aren't sta

Currently websockets are unsupported:

class SttpBackendStub[F[_], S] private (
    monad: MonadError[F],
    matchers: PartialFunction[Request[_, _], F[Response[_]]],
    fallback: Option[SttpBackend[F, S, NothingT]]
) extends SttpBackend[F, S, NothingT] { // TODO

(note the TODO for the NothingT type parameter which specifies what kind of websockets are supported).

The bac

Some docs include code snippets from examples. For example the HTTP README.adoc. We should investigate tooling to extract code from examples to avoid duplication and stale docs.

May be it's finally time to split things in modules and separate files, even the tiny ones. So rewriting it in TypeScript or smth. would be much easier and code will be even easier to parse and test.

Short description

In server-side
It should mention the HandlerFactory.
e.g
When do not using metadata, use GreeterServiceHandlerFactory.create().
When using metadata, use `GreeterServicePower

This issue, similar to #21, collects some interesting cases and pitfalls in the form of Java Puzzlers, giving a scenario and offering 4-6 answers.

Problem or use case

The client is currently only logging errors and warnings. For debugging purposes and during application development, it would be very useful to also have logs detailing the message flow.

Preferred solution or suggestions

TRACE level logging for incoming and outgoing MQTT control packet types, e.g., PUBLISH, SUBSCRIBE, PUBACK, SUBACK.