All Versions
33
Latest Version
Avg Release Cycle
37 days
Latest Release
1233 days ago

Changelog History
Page 2

  • v3.3.8.RELEASE Changes

    July 20, 2020

    🚀 Reactor-Core 3.3.8.RELEASE is part of Dysprosium-SR10 Release Train.

    🚀 This maintenance release is a recommended update for all Reactor 3 users.

    🚀 This version also contains all changes from v3.2.19.RELEASE.

    🍱 🐞 Bug fixes

    • 🖐 Handle null publisher in MonoDelayUntil (#2245)
    • 🛠 fix #2260 Avoid onSubscribe race in FluxTimeout (#2266)

    📚 📖 Documentation, Tests and Build

    • ⏱ [doc] Fix Scheduler Javadoc (#2190)
    • [doc] fix #2199 Fix typo in reference guide
    • 🏗 [build] fix #2264 add blockhound to testset
    • [doc] Fix small error in TupleUtils asciidoc (#2201)
    • 💅 [polish] fix #2246 Remove usage of globalRegistry in metrics tests
    • 💅 [polish] FluxUsingWhenTest awaitility + order of capturing subscription
    • [doc] fix #2257 Improve flatMapIterable prefetch javadoc

    🚀 👍 Thanks to the following contributors that also participated to this release

    @dennyac, @nicolasgavalda

  • v3.3.7.RELEASE Changes

    June 25, 2020

    🚀 reactor-core 3.3.7.RELEASE is part of Dysprosium-SR9 Release Train.

    🍱 ✨ New features and improvements

    🍱 🐞 Bug fixes

    • Align MonoCollect and MonoCollectList to avoid race condition which leads to NullPointerException (#2186)
    • 🖐 Handle nulls from collectors in Flux.collect() (#2181)

    📚 📖 Documentation, Tests and Build

    • ⏱ [test] Improve thread regrowth test of boundedElastic/Elastic by considering negative values that might be produced as 0 (no regrowth, aka no increase in the number of active threads from the scheduler).
    • 🏗 [build] Ensure tools fat jar is the one published (#2189)
    • 📇 [build] Fix input package rule for OSGi metadata generator (#2185)

    🚀 👍 Thanks to the following contributors that also participated to this release

    @rstoyanchev , @melix , @gurkerl83

  • v3.3.6.RELEASE Changes

    June 25, 2020

    🚀 Reactor-Core 3.3.6.RELEASE is part of Dysprosium-SR8 Release Train.

    🍱 ✨ New features and improvements

    • EnsureDeferredSubscription makes requests serially if there is racing between set / requestN (according to RS spec Rule 2.7)(#2164)
    • Ensure FluxSwitchOnFirst serializes requests (according to RS spec Rule 2.7) (#2161)
    • Ensures next element is dropped if UnicastProcessor disposed to avoid racing between onNext and dispose (#2180)
    • ⏱ Use ZoneId.of(String) to avoid blocking disk load during first access of Schedulers.boundedElastic() (#2143)

    🍱 🐞 Bug fixes

    • Accommodate ASYNC fusion in Mono.metrics() to avoid NullPointerException or hanging in certain cases (#2160 )
    • 🛠 Fix volatile read of first element and ConditionalSubscriber classcast in FluxSwitchOnFirst (#2166)
    • 🔄 Change the Subscription set by reportThrowInSubscribe to an instance compatible with QueueSubscription, preventing fused cases where a ClassCastException would be thrown. (#2152 )

    📚 📖 Documentation, Tests and Build

    • ✅ [test] Fix publishOn scan test, hiccup before asserting BUFFERED
    • 👍 [doc] Better describe Mono.first() and Mono.or() behavior (#2159)
    • [doc] Fix typo Retry.fromFunction() instead of from() (#2172)
    • [doc] Fix RetrySpec doc: throwablePredicate is actually filter (#2162)
    • [doc] Document onCancel / onDipose limited to 1 use (#2015)
    • 🚚 [doc] Remove wrong curly braces in generate code example (#2110)
    • 🏗 [build] Have blockHoundTest fork JVM on every case (see #2144)
    • 🏗 [build] Consistently use tabs for gradle file indentation (#2157)
    • 📇 [publication] Publish Gradle metadata, without optional dependencies (#2151)

    🚀 👍 Thanks to the following contributors that also participated to this release

    @alex-dukhno , @chakas , @berry120 , @OlegDokuka , @PyvesB , @josemalonsom

  • v3.3.5.RELEASE Changes

    April 27, 2020

    🚀 reactor-core 3.3.5.RELEASE is part of Dysprosium-SR7 Release Train.

    🚀 It also contains all fixes from 3.2.17.RELEASE.

    ⚡️ ⚠️ Update considerations and deprecations

    • A corner case of throwing from the subscribe method can lead to two onSubscribe signal if said exception is thrown after having sent the Subscription (#2107, #2111, #2072)
    • Most well-formed subscribers will ignore this, but StepVerifier cannot, which can "hide" the true error
    • This potentially extra Subscription can be identified with Operators.canAppearAfterOnSubscribe(Subscription), which is used by StepVerifier to ignore that particular extra subscription

    🍱 ✨ New features and improvements

    • Unify error-handling in subscribe/subscribeOrReturn mutualized implementation, prevent StepVerifier getting confused by a double onSubscribe in that very specific case ((#2072, #2107, #2111)
    • 🏗 [tools] Support build-time debug instrumentation (#2105)
    • 👍 [tools] Support running reactor-tools as a "normal" Java Agent (#2104, #2098)
    • From 3.2.17:
      • Cover several cases of onNext vs cancel races that would bypass resource discarding (#2134, #2126, #2102, #2124, #2125, #2122, #2077, #2102)
      • Including backport and complement of fixes to UnicastProcessor (#2124, #2125, #980, #2126)
      • Flux#from and Mono#flux consistently apply onAssembly hooks (#2055, #2067)
      • Flux#from/wrap does not call Flux#onAssembly
      • Flux#from and Mono#flux apply onAssembly hooks

    🍱 🐞 Bug fixes

    • 🛠 Fix DefaultStepVerifierBuilder#onSubscribe error format (#2106)
    • From 3.2.17:
      • Propagate rejection error from MonoDelayElement#onNext downstream

    📚 📖 Documentation, Tests and Build

    • ✅ [test] Don't reuse same exception in errorOnSubscribe steps (#2112)
    • 💅 [doc] Polish doc of Iterable operators, clarify iterator() calls (#2135, #2014, #2127)
    • ✅ [test] Split errorOnSubscribe scenarios into separate tests (#2099)
    • 🏗 [build] Follow-up to #2088 bump to Gradle 6.3 : 3.3 specifics (#2088, #2089)
    • 💅 Polish docs, code compilation warnings, flakkt tests, etc... (#2087, #2084, #2084)
    • ✅ [test] Use JUnit Jupiter's @TestFactory in BaseOperatorTest (#2085)
    • ✅ [test] Use JUnit Platform + Vintage engine (#2073)
    • ✅ [test] Add a post-test listener that resets hooks consistently (#2082)
    • from 3.2.17
      • [test] Extract Tracked to MemoryUtils, add OffHeapDetector (#2125)
      • [test] Provides tests suite to expose onDiscard leaks and fixes (#2125)
      • Create CODEOWNERS (#2097)
      • [build] Test with JDK 14, bump to Gradle 6.3 (#2088)
      • [test] Remove testStaticInit task, verify in main test task (#2093)
      • [Polish] Split bndoptions elements in array for clarity (#2091)
      • [build] Simplify stubbing for Java 9+ (#2091)
      • [build] Backport gradle/releaser.gradle to 3.2 (e4fe960)

    🚀 👍 Thanks to the following contributors that also participated to this release

    @OlegDokuka, @pimlock

  • v3.3.3.RELEASE Changes

    February 24, 2020

    🚀 reactor-core 3.3.3.RELEASE is part of Californium-SR16 Release Train.

    ⚡️ ⚠️ Update considerations and deprecations

    • ➕ Added a defer opt-in in VirtualTimeScheduler.create (#1251, #2012)
      • Manually-created VirtualTimeScheduler will now eagerly advance time even if there is no pending task. Use the overload with defer=true to get the old default behavior.
      • StepVerifier-created ones will continue lazily advancing time when no task is scheduled, in order to make testing of things like delays inside a flatMap possible.

    🍱 ✨ New features and improvements

    • 🛠 Fixed Flux.replay / Flux.cache hanging or serving wrong values, by correctly replaying request(UNBOUNDED) when no early subscriber (#2030, #2028)
    • Propagate all req from FluxReplay pre-connect subscribers (#1921)
    • ⏱ Reimplemented boundedElasticScheduler to allow reentrancy (#1992, #2040, #1973)
      • Multiple subscribeOn calls with a BoundedElasticScheduler could easily cause deadlock
      • This also fixes #1973, although there was an intermediate fix in the old implementation
    • From 3.2.15:
      • Discard concatMapIterable/fromIterable's remainder on Cancel (#2014)
      • the remainder of the internal Iterator is discarded when cancelled mid-iteration
      • we avoid the risk of iterating an infinite iterator by first checking if the Iterable is a Collection or its Spliterator has the SIZED characteristic.
      • the above check can result in at most 2 calls to Iterable#iterator for custom iterables
      • [polish] Improve onDiscardMultiple/QueueWithClear resiliency (#2021)

    🍱 🐞 Bug fixes

    • 0️⃣ Avoid parallel insertion in Context's default putAll with foreign Context implementation (#2050)
    • From 3.2.15:
      • Account for requests made to upstream in FluxBufferPredicate (#1937, #2029)
      • collect() discards on consumer error when fused (#2042)
      • Unconditionally dispose worker in MonoSubscribeOn#cancel (#2037)
      • Pass on cancelSupport when lifting ConnectableLiftFuseable (#1860)
      • Correctly count continued errors on flatmapped callable (#2011)
      • Handle "empty Callable" in Flux#collectList (#2023, #2024)
      • Fix fused last(T) not delivering defaultValue (#2020)

    📚 📖 Documentation, Tests and Build

    • Document Flux#next() behavior for an empty Flux (#1899)

    🚀 👍 Thanks to the following contributors that also participated to this release

    @btkelly, @ilyavy, @robotmrv, @yarosla

  • v3.3.2.RELEASE

    January 13, 2020

  • v3.3.1.RELEASE Changes

    December 02, 2019

    🚀 Reactor-Core 3.3.1.RELEASE is part of Dysprosium-SR2 Release Train.

    🚀 It also includes changes from the 3.2.13.RELEASE version.

    ✅ One important change to pick up for testing Reactor is in StepVerifier: the combination of expectNoEvent followed by thenCancel wasn't working terribly well, and a new better terminal expectation has been introduced: expectTimeout (#1913)

    ⚡️ ⚠️ Update considerations and deprecations

    • ⏱ #1911 Instrument ScheduledExecutorService via Micrometer
    • Instead of doing our own executor decorator we now rely on the Micrometer one, but it might have different coverage of tasks

    🍱 ✨ New features and improvements

    • 🚚 #1557 Removed greediness from FluxBufferTimeout
    • 🚚 #1938 Remove overeager toString calls in FluxIndexFuseable
    • #1913 StepVerifier: expectTimeout(Duration) as an alternative to expectNoEvent(Duration).thenCancel()
    • #1902 When transform or transformDeferred apply a transformation to a non-Reactor Publisher, warn when/if the original Context is lost (#1888)
    • #1966 Internal simplification of how the comparator is applied in collectSortedList
    • 🖨 #1962 Avoid extending Map.Entry in Context1 to ensure various libraries don't represent it inconsistenly when printing out collections of Context
    • #1963 Retain insertion order in ContextN (by extending LinkedHashMap instead of HashMap)
    • 🚀 changes from 3.2.13.RELEASE:
      • #1916 Interpret MAX_VALUEms as indefinite caching in Mono#cache(Function, Function, Supplier) (backported)
      • #1746 Add VirtualTimeScheduler#getScheduledTaskCount() (backported)
      • #1968 Make Flux#publish() propagate 1st subscriber Context
      • #1953 Add Exceptions.isTraceback, and a mean to unwrap a composite without the tacebacks (Exceptions.unwrapMultipleExcludingTracebacks)

    🍱 🐞 Bug fixes

    • 🚀 changes from 3.2.13.RELEASE:
      • #1945 Avoid unnecessary wrapping of exceptions in scalar flatMap
      • #1959 GroupedFlux fused with parallel() not replenishing properly

    📚 📖 Documentation, Tests and Build

    • [doc] #1908 Marble diagram for bufferWhile was incorrectly showing dropped separators
    • [doc] #1915 Flux#join javadoc and marble have been clarified
    • 🚀 [dependency] Bumped BlockHound to the release version (#1923)
    • 🏗 [build] Reorganization of the build with separation of concerns (buildSrc, gradle.properties, etc...) (0bd50de, a1dab8a)
    • 🏗 [build] Add reactor.blockhound to OSGI optional bundles (#1932, #1933)
    • 🚀 [build] Prepare for a releasetrain releaser script: add new tasks, allow mavenLocal source (06977a6, #1960)
    • 🚀 changes from 3.2.13.RELEASE:
      • [build] Switched to Gradle 5.6 (8e97f91)
      • [build] Switched publication plugin to maven-publish and artifactory (#1943)
      • [build] Fixed generation of refguide pdf when custom version is used (2c621b6)
      • [polish] Exceptions.multiple(Iterable) now produces a CompositeException, more test coverage of Exceptions util (#1954)

    🚀 👍 Thanks to the following contributors that also participated to this release

    @andreisilviudragnea, @akarnokd, @berry120, @dittos, @EleanorRoseLegg, @gindex, @jabrena, @simondaudin, @slisaasquatch, @thiyagu-7, @ttddyy, @slisaasquatch, @wonwoo

  • v3.3.0.RELEASE Changes

    September 25, 2019

    🚀 Reactor-Core 3.3.0.RELEASE is part of Dysprosium-RELEASE Release Train.

    🚀 This release note covers the first GA release of the 3.3.x cycle, and as such describes the changes from the perspective of a 3.2.x to 3.3.0 comparison.

    🚀 See also release notes from 3.2.12, 3.2.11, 3.2.10 and 3.2.9 for changes that were inherited from the 3.2.x maintenance releases.

    🚀 This release is a big opportunity to polish the APIs and some behaviors with less restriction than maintenance releases.

    ⏱ 🌟 It also introduces a few new features, the highlight of which is the BoundedElasticScheduler:
    ⏱ this one has evolved from the ElasticScheduler and is intended as a future replacement for it.
    ⏱ A cap can be put on the number of threads such a scheduler can spawn. After that cap is reached, further task submissions are deferred (being enqueued) up to a second global limit on enqueued tasks (optionally unbounded).

    ⚡️ ⚠️ Update considerations and deprecations

    • (from RC1:)
    • A few Mono operators have slightly changed their behavior in regards to how when they propagate onNext: they could trigger onError after onNext, which is not permitted in Mono.
      • Mono#usingWhen now waits for the async complete handler termination before propagating onNext (#1832)
      • Mono#using similarly avoids triggering onNext+onError if cleanup fails (#1853)
      • Mono#doOnTerminate now acts similarly to doOnSuccess, executing the side effect before the onNext is propagated downstream (#1752)
    • 🗄 Mono#do[On|After]SuccessOrError has been deprecated and marked for removal in 3.4 (#1854)
    • 💅 usingWhen API has been polished, and some variants deprecated for removal in 3.4 (#1687)
      • A new overload has been introduced that uses BiFunction for error handler (exposing the failure that causes "rollback")
      • A single-handler version has been added to Mono for alignment with Flux. This is the simplest case: same handler for complete, error and cancel terminations.
      • All other overloads have been deprecated. Goal is to favor either the simple 1-handler-covers-all case OR force users to be explicit about ALL possible terminations.
    • (from M3:)
    • 🗄 #1742 Processors and Kotlin extensions deprecations
    • 🚚 the WorkQueueProcessor and TopicProcessor have been marked as deprecated for 3.3.x and will be removed in 3.4
    • 🗄 have been deprecated, due to underlying use of Unsafe
    • Recommended core alternative is to combine EmitterProcessor and publishOn
    • 🗄 the Kotlin extensions are deprecated in core and replaced by a dedicated project/repo, reactor-kotlin-extensions
    • 🗄 in both cases, the deprecated classes don't appear in the generated javadoc jar
    • ⏱ #1764 Deprecated method Schedulers.Factory#decorateExecutorService has been removed
    • #1669 All onBackpressureBuffer(maxSize+error) variants now delay errors
    • 🚚 In debug mode, most of the original stacktrace is artificially moved at the end of the exception's output, after the "backtrace" (#1781)
    • 🗄 #1745 compose() has been deprecated and renamed transformDeferred()
    • 🚚 deprecated operator will be removed in 3.4
    • 🚦 #1451 Dematerialize has been reworked and now expects 1 request per upstream Signal
    • 🚦 This avoids onNext events to be emitted only when the subsequent signal is ready upstream
    • 🚦 This also means that in order to get a terminal signal like onComplete signal, the corresponding Signal must be explicitly requested from upstream (one extra request(1))
    • (from M2:)
    • Exceptions are now unwrapped (Exceptions#unwrap) in most sources that immediately produce an error, acting like a Callable (b6f4d29)
    • 🚚 Moved reactor-tools sources into the core repository (#1731)

    🍱 ✨ New features and improvements

    • ⏱ 🌟 Added a boundedElastic Scheduler that caps number of threads and scales to 0 (#1804)
      • global singleton also cap deferred tasks past the thread limit to 100K (32d2a29)
      • thread cap and task queue capacity can be configured separately, the later can even be unbounded
    • ➕ Add windowUntilChanged operator, ensure the stateful predicate is subscriber-specific and cleaned on cancel (#1850, #1901)
    • 👌 Improve the naming (eg. scan(Attr.NAME) or toString) of global singleton Schedulers (#1885, #1886)
      • for instance, instead of parallel(parallel) this is now Schedulers.parallel()
    • 👌 Improvements around subscription recursivity / subscribe loop performance (#1882)
    • Avoid extra lastAssembly by using CorePublisher where possible (#1883)
    • (from RC1:)
    • Due to a few Throwable constants, class references could leak in multi-classloader environments. This is now avoided by skipping the filling of the stacktrace (#1872)
    • ➕ Add BufferUntilChanged operator (#1706, bb5b2bb)
    • ➕ Added new StepVerifier API to subscribe to source and verify it later (#1848, b2ce5fe)
    • (from M3:)
    • ➕ Add "VirtualTimeScheduler#getScheduledTaskCount()" (#1746)
    • #1763 Flux.parallel now uses Schedulers.DEFAULT_POOL_SIZE (which can be overridden by system property)
    • #1767 Add ParallelFlux#then to compose on parallel termination
    • ⏱ #1722 Make sure ElasticScheduler.CachedService gets disposed
    • #1798 Use bounded wildcard in error(Supplier)
    • 💅 Polish flux metrics (#1802)
      • see also the other commits linked in that PR
    • Actually record executor service metrics to Micrometer (#1795)
    • ➕ Add a Context-aware {Mono,Flux}.deferWithContext (#1819)
    • ⚡️ Eliminate subscribe from stack by optimizing the "tail calls" (#1761, #1826)
    • #1416 Add lambda subscribe variants with a context
    • (from M2:)
    • Avoid triggering Context lookups in error sources (4f2bc7a)
    • Extended blockHound whitelist
      • all ScheduledExecutor offer (95c0884)
      • DelayedWorkQueue#take (#1726)
    • ✂ Remove unnecessary volatile with UnicastProcessor fusion (c86db5a)
    • 👌 Improved cache eviction in ElasticScheduler (#1700)
    • (from M1:)
    • ✅ Compatibility with projects using the Java Module System (JPMS) has been improved by declaring an official Automatic-Module-Name (reactor.core and reactor.test, #1641, #1692)
    • The CorePublisher interface has been introduced to distinguish Publisher from reactor (#1527)
    • ➕ Add a simplified API for wrapping scheduled tasks (#1546)
    • ➕ Add an API-preserving hide() method to ConnectableFlux (#1577)
    • ✅ [reactor-test] Added hasDiscardedMatching method in StepVerifier (#1509)
    • ✅ [reactor-test] Add ToStringConverter and Extractor to StepVerifierOptions (#1558)
      • This allows to override the natural toString representation of classes that are known to have an obscure representation, as well as extracting such objects that would be nested in containers like a Collection, Tuple2, Signal, ...
    • Reworked the format of "backtraces" (#1672, #1702)
      • Backtraces are the additional callsite information captured by debug mode and checkpoint and appended to onError Throwable as a suppressed exception
    • Reactor now integrates into Blockhound 1.0.0.M3 using the SPI on reactor side instead of programmatic explicit registration on blockhound side (#1682, #1690)

    🍱 🐞 Bug fixes

    • (from M2:)
    • Avoid unbounded Flux.replay request with bounded subscribers (#1185)
    • ✂ Removed "checkpoint" prefix in backtraces from return-only callsites (#1740)
    • (from M1:)
    • 🚦 [reactor-test] Prevent StepVerifier collect hang when consuming all signals (#1529)
    • Unwrap CompletionException in Mono#fromFuture (#1652)
    • 🛠 Fix MonoProcessor#block duration.zero change (c995c01)

    📚 📖 Documentation, Tests and Build

    • Document Java9stubs-related importing issues (#1680)
    • [doc] Disambiguate lowTide example in limitRate javadoc
    • Document reactor-tools in refguide (#1903)
    • ✅ [internal test utils] Rework autoCleanup methods into a reusable JUnit Rule
    • ✅ [internal test utils] Add direct assertion method on RetainedDetector
    • (from RC1:)
    • [doc] Add limitRate marble diagrams (#1449)
    • 💅 [build] Polish benchmarks build, remove jmh plugin (#1844, 1ba4944)
    • 🏗 [build] Make it possible to run two JMH tasks - baseline and current (#1862)
    • (from M3:)
    • 🏗 [build] Use "check" task as an aggregator, not "test" (#1776)
    • 👀 [doc] #1539 Add "metrics" section to the reference guide (see also #1812, #1817)
    • (from M2:)
    • 🏗 [build] JMH benchmarks are now in a separate sub-project, forked scrabble benchmark there (8895e94)
    • 🏗 [build] Log console output in Gradle ONLY for failed tests on CI (fc74beb)
    • (from M1:)
    • [doc] Document that BaseSubscriber instances can't be reused (#1490)
    • 🏗 [CI] Sanity check build on JDK12 on Travis (446ca1b)
    • [doc] Use the correct marble diagram for Mono#onErrorResume (#1679)
    • 💅 [build] Polish .gitignore to avoid too broad regex (92ae4e5)

    🚀 👍 Thanks to the following contributors that also participated to the Dysprosium-RELEASE or pre-releases

    @aftersss, @akarnokd, @apuravchauhan, @berry120, @Buzzardo, @dittos, @don-vip, @flambard, @gindex, @hisener, @izeye, @jnizet, @mumukiller, @OlegDokuka, @pcdavid, @pmackowski, @ramonPires, @szpak, @ttddyy, @UgiR, @zhouzhou19950825

  • v3.3.0.RC1 Changes

    September 04, 2019

    🚀 Reactor-Core 3.3.0.RC1 is part of Dysprosium-RC1 Pre-Release Train.

    🛠 This first release candidate of the 3.3.x cycle contains bugfixes and improvements from the GA 3.2.12.RELEASE as well as a few new features. It also involves a few behavior impacting changes and deprecations.

    ⚡️ ⚠️ Update considerations and deprecations

    • A few Mono operators have slightly changed their behavior in regards to how when they propagate onNext: they could trigger onError after onNext, which is not permitted in Mono.
      • Mono#usingWhen now waits for the async complete handler termination before propagating onNext (#1832)
      • Mono#using similarly avoids triggering onNext+onError if cleanup fails (#1853)
      • Mono#doOnTerminate now acts similarly to doOnSuccess, executing the side effect before the onNext is propagated downstream (#1752)
    • 🗄 Mono#do[On|After]SuccessOrError has been deprecated and marked for removal in 3.4 (#1854)
    • 💅 usingWhen API has been polished, and some variants deprecated for removal in 3.4 (#1687)
      • A new overload has been introduced that uses BiFunction for error handler (exposing the failure that causes "rollback")
      • A single-handler version has been added to Mono for alignment with Flux. This is the simplest case: same handler for complete, error and cancel terminations.
      • All other overloads have been deprecated. Goal is to favor either the simple 1-handler-covers-all case OR force users to be explicit about ALL possible terminations.

    🍱 ✨ New features and improvements

    • Due to a few Throwable constants, class references could leak in multi-classloader environments. This is now avoided by skipping the filling of the stacktrace (#1872)
    • ➕ Add BufferUntilChanged operator (#1706, bb5b2bb)
    • ➕ Added new StepVerifier API to subscribe to source and verify it later (#1848, b2ce5fe)

    🍱 🐞 Bug fixes

    • (from 3.2:)
    • 👍 Flux#flatMap with scalar source now supports onErrorContinue (#1684)
    • Flux#doAfterTerminate now executed when onError in fused mode (#1836, #1835)
    • Explicitly catch LinkageError in Traces. This helps with some static analyzers (#1830)
    • 👍 Pass on cancelSupport when lifting ConnectableFlux (#1860)

    📚 📖 Documentation, Tests and Build

    • [doc] Add limitRate marble diagrams (#1449)
    • 💅 [build] Polish benchmarks build, remove jmh plugin (#1844, 1ba4944)
    • ✏️ [doc] Fix several typos in javadocs (#1845)
    • 🏗 [build] Make it possible to run two JMH tasks - baseline and current (#1862)
    • 💅 [polish] Fix MaterializeSubscriber toString, AbstractQueue's won't work (df34ad9)
    • ⚡️ [chores] Update BlockHound to RC1 (#1877)
    • (from 3.2:)
    • 🚚 [github] Removed CONTRIBUTING.md and issue_template in favor of centralized ones (740c048)
    • 🏗 [build] Use JCenter, not MavenCentral for doDownloadBaseline (aa08709, d4f5332)
    • 🚚 [doc] Remove double mention of subscribe in Flux README (#1861)
    • 0️⃣ [doc] Document that default initial delay for interval is the period (#1866)

    🚀 👍 Thanks to the following contributors that also participated to this release

    @gindex, @UgiR

  • v3.3.0.M3 Changes

    July 30, 2019

    🚀 Reactor-Core 3.3.0.M3 is part of Dysprosium-M3 Release Train.

    🛠 This third milestone of the 3.3.x cycle contains bugfixes and improvements (including changes from the GA 3.2.11.RELEASE) as well as some behavior/API impacting changes:

    ⚡️ ⚠️ Update considerations and deprecations

    • 🗄 #1742 Processors and Kotlin extensions deprecations
    • 🚚 the WorkQueueProcessor and TopicProcessor have been marked as deprecated for 3.3.x and will be removed in 3.4
    • 🗄 the Kotlin extensions are deprecated in core and replaced by a dedicated project/repo
    • 🗄 in both cases, the deprecated classes don't appear in the generated javadoc jar
    • ⏱ #1764 Deprecated method Schedulers.Factory#decorateExecutorService has been removed
    • #1669 All onBackpressureBuffer(maxSize+error) variants now delay errors
    • 🚚 In debug mode, most of the original stacktrace is artificially moved at the end of the exception's output, after the "backtrace" (#1781)
    • 🗄 #1745 compose() has been deprecated and renamed transformDeferred()
    • 🚚 deprecated operator will be removed in 3.4
    • 🚦 #1451 Dematerialize has been reworked and now expects 1 request per upstream Signal
    • 🚦 This avoids onNext events to be emitted only when the subsequent signal is ready upstream
    • 🚦 This also means that in order to get a terminal signal like onComplete signal, the corresponding Signal must be explicitly requested from upstream (one extra request(1))

    🍱 ✨ New features and improvements

    • ➕ Add "VirtualTimeScheduler#getScheduledTaskCount()" (#1746)
    • #1763 Flux.parallel now uses Schedulers.DEFAULT_POOL_SIZE (which can be overridden by system property)
    • #1767 Add ParallelFlux#then to compose on parallel termination
    • ⏱ #1722 Make sure ElasticScheduler.CachedService gets disposed
    • #1798 Use bounded wildcard in error(Supplier)
    • 💅 Polish flux metrics (#1802)
      • see also the other commits linked in that PR
    • Actually record executor service metrics to Micrometer (#1795)
    • ➕ Add a Context-aware {Mono,Flux}.deferWithContext (#1819)
    • ⚡️ Eliminate subscribe from stack by optimizing the "tail calls" (#1761, #1826)
    • #1416 Add lambda subscribe variants with a context
    • (from 3.2:)
    • #1793 Reject Context.of calls with duplicate keys
    • 💅 Polish ContextN null checks (#1801)

    🍱 🐞 Bug fixes

    • (from 3.2:)
    • ⏱ #1739 Enforce a name for Schedulers.fromExecutorService
      • without this explicit name, the metrics would use null as a name
    • 👍 #1783 Do not drop errors in MonoCacheTime, better doc (#1784)
    • #1738 FluxRefCount inner doesn't guard against multiple cancels
    • #1797 Explicitly reject null keys/values in Context constructors
    • 👻 #1741 MonoCreate hanging if delayUntil throws exception

    📚 📖 Documentation, Tests and Build

    🚀 👍 Thanks to the following contributors that also participated to this release

    @jbnizet, @izeye, @dittos, @apuravchauhan, @gindex, @hisener, @berry120, @pcdavid, @ttddyy, @ramonPires