Initialization error in asynchronous reactive-streams
johnmcclean opened this issue · comments
When configuring a reactive-stream (via Spouts) asynchronously, it is possible to push data asynchronously that is recieved by onNext before initialization is complete.
Any attempt to send subsequent requests for more data upstream should check for initialization to complete (on the initialization thread), otherwise the upstream subscription won't be available.
Released in 10.3.0