Arnout Engelen
Arnout Engelen
Leaked children: ``` [info] MqttSessionSpec: ... [info] MQTT server connector ... [info] - should produce a duplicate publish on the server given two client connections *** FAILED *** (46 seconds,...
Still targeting Java 8, but as preparation for raising the minimum Java version for those components where the upstream library requires it.
``` --> [org.apache.pekko.stream.connectors.ftp.FtpsWithProxyStageTest: fromPath] Start of log messages of test that failed with assertion failed: timeout (30 seconds) during fishForMessage, hint: OnNext(_) or OnComplete
``` [info] SolrSpec: [info] Pekko Connectors Solr [info] - should consume and publish SolrInputDocument (757 milliseconds) [info] - should consume and publish documents as specific type using a bean (719...
``` [info] UnixDomainSocketSpec: [info] A Unix Domain Socket [info] - should receive some bytes (34 milliseconds) [info] - should send and receive more ten times the size of a buffer...
It seems to be specifically `establishClientBidirectionalConnectionAndSubscribeToATopic` and `establishServerBidirectionalConnectionAndSubscribeToATopic`
Subtle bugs can appear when you use overlapping connection ids within a session. It would be good to provide an API where the component takes care of this automatically.
The link validator is currently run on PR validation, however it is far too susceptible for intermittent failures not caused by the PR in question. We should probably move it...
If we declare Java 8 support deprecated in/before Pekko 1.1.0, we give ourselves the option to remove it in Pekko 1.2.0 (in the spirit of https://pekko.apache.org/docs/pekko/current/common/binary-compatibility-rules.html#when-will-a-deprecated-method-be-removed-entirely). Depending on feedback we...