Update dependency io.projectreactor:reactor-core to v3.4.12 #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
force-pushed
the
renovate/reactor-core.version
branch
from
ca1e01a to
5976b0e
Compare
ghost
force-pushed
the
renovate/reactor-core.version
branch
from
5976b0e to
87bdc94
Compare
ghost
changed the title
ghost
changed the title
ghost
closed this
ghost
changed the title
ghost
reopened this
ghost
force-pushed
the
renovate/reactor-core.version
branch
from
87bdc94 to
74ad0a8
Compare
ghost
changed the title
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will now ignore this update (3.4.12). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.2.0.M1->3.4.12Release Notes
reactor/reactor-core
v3.4.12Compare Source
(curated release note to come)
What's Changed
@NonNullannotation, not JetBrain's NotNull by @simonbasle in Use@NonNullannotation, not JetBrain's NotNull reactor/reactor-core#2808New Contributors
Full Changelog: reactor/reactor-core@v3.4.11...v3.4.12
v3.4.11Compare Source
Reactor-Core
3.4.11is part of2020.0.12Release Train (EuropiumSR12).This service release contains bugfixes and one enhancement.
All changes from
3.3.21.RELEASEare also included and these are listed below with an additional level of indentation.✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build
limit(0)(#2787)👍 Thanks to all contributors who participated to this release
@rs017991
v3.4.10Compare Source
Reactor-Core
3.4.10is part of2020.0.11Release Train (EuropiumSR11).This service release contains bugfixes and polishing changes.
All changes from
3.3.20.RELEASEare also included and these are listed below with an additional level of indentation.Flux.replayunderlying implementation doesn't support 0-size anymore (which was illogical in the first place)Flux.publish()instead (#2741)Disposableobtained by callingmono.share().subscribe()(and that variant only) would terminate/cancel the wholemono.share()for all its subscribers. now this is an individual subscription, much like.subscribe(v -> {})for instance.toProcessor()and explicitly turning the sourceMonointo aMonoProcessorinstead of sharing it, although the whole approach is deprecated.✨ New features and improvements
FluxOnBackpressureBufferStrategyreject sizes <= 0 (#2757)🐞 Bug fixes
hasNext(#2766)📖 Documentation, Tests and Build
👍 Thanks to all contributors who participated to this release
@hisener, @KATKrazy, @keturn
v3.4.9Compare Source
Reactor-Core
3.4.9is part of2020.0.10Release Train (EuropiumSR10).This service release contains bugfixes and new features.
Some changes from
3.3.19.RELEASEare also included and these are listed below with an additional level of indentation.🪲 Bug fixes
📖 Documentation, Tests and Build
8425677👍 Thanks to the following contributors that also participated to this release
@ivyazmitinov
v3.4.8Compare Source
Reactor-Core
3.4.8is part of2020.0.9Release Train (EuropiumSR9).This service release contains bugfixes and new features.
Flux#mergeOrderedhas been deprecated (#2719)mergeComparinghas been introduced as an alternative that is more consistent with other merge operators✨ New features and improvements
mergeComparingas fail-fast alternative tomergeOrdered(complemented with adelayErrorvariant) (#2719)Mono.cacheInvalidateIfandMono.cacheInvalidateWhen(#2717)Predicateon the value when a late subscriber comes in or by associating the cached value with aMono<Void>invalidation trigger that can be externally completed🪲 Bug fixes
📖 Documentation, Tests and Build
2da73e9)👍 Thanks to the following contributors that also participated to this release
@koldat
v3.4.7Compare Source
Reactor-Core
3.4.7is part of2020.0.8Release Train (EuropiumSR8).This minor service release contains build and test improvements as well as one new minor feature.
All changes from
3.3.18.RELEASEare also included and these are listed below with an additional level of indentation.✨ New features and improvements
📖 Documentation, Tests and Build
00afede)👍 Thanks to the following contributors that also participated to this release
@clayly, @eas5
v3.4.6Compare Source
Reactor-Core
3.4.6is part of2020.0.7Release Train (EuropiumSR7).This service release contains bugfixes and new features.
All changes from
3.3.17.RELEASEare also included and these are listed below with an additional level of indentation.MonoDelaydoesn't produce aOverflowExceptionbackpressure error when the delay is so small that it terminates before regular request had a chance to be made (since the operator assume subscribe == request, like a lot ofMonos).reactor.core.publisher.MonoDelay.failOnBackpressurewith valuetrue. ✨ New features and improvements
29d2e3b)🪲 Bug fixes
📖 Documentation, Tests and Build
contextWrite(f)rather than subscriberContext(f) in docs (#2685)main, update CI (#2679)174afcc)👍 Thanks to the following contributors that also participated to this release
@horizonzy, @robotmrv, @vovikdrg
v3.4.5Compare Source
Reactor-Core
3.4.5is part of2020.0.6Release Train (EuropiumSR6).This service release contains bugfixes and a couple implementation improvements forwarded from the 3.3.x line as well as documentation improvements.
All changes from
3.3.16.RELEASEare also included and these are listed below with an additional level of indentation.✨ New features and improvements
🪲 Bug fixes
📖 Documentation, Tests and Build
👍 Thanks to the following contributors that also participated to this release
@berry120, @mickeelm, @underbell
v3.4.4Compare Source
Reactor-Core
3.4.4is part of2020.0.5Release Train (CodenameEuropium).This service release contains a few improvements and new features. It also contains bugfixes from the 3.3.x line.
All changes from
3.3.15.RELEASEare also included and these are listed below with an additional level of indentation.✨ New features and improvements
MonoInnerProducerBase(#2632, #2645)🪲 Bug fixes
Mono.fromSupplier(() -> null).single()previously failed to produce anonError(NoSuchElementException)(#2635)Monothat was implementingCallable(which includesfromSupplier,fromCallable,fromRunnableto some extent...) would exhibit the wrong behaviorFlux#single, which is going to be fixed by #2657 in the next release📖 Documentation, Tests and Build
👍 Thanks to the following contributors that also participated to this release
@kevinten10, @mickeelm, @SimonBerry555, @v-terret
v3.4.3Compare Source
Reactor-Core
3.4.3is part of2020.0.4release train (Europium SR4).This is a maintenance release which also inherit changes from
3.3.14.RELEASE.✨ New features and improvements
switchMap/switchOnNextwith prefetch=0 (#2596)🪲 Bug fixes
skipUntilconditional subscriber logic inconsistent (#2578)concatMap(#2576)📖 Documentation, Tests and Build
TestLoggerbe configured with simplified format (#2538)👍 Thanks to the following contributors that also participated to this release
@richardfearn, @vdjuketic
v3.4.2Compare Source
Reactor-Core
3.4.2is part of2020.0.3Release Train (EuropiumSR3).This service release contains a couple bugfixes inherited from
3.3.13.RELEASEas well as additional documentation polishing.This note focuses on changes specific to this version, see also from
3.3.13.RELEASErelease notes📖 Documentation, Tests and Build
👍 Thanks to the following contributors that also participated to this release
@bbukaty
v3.4.1Compare Source
Reactor-Core
3.4.1is part of2020.0.2Release Train (Europium SR2).This service release contains bugfixes and new features.
This note focuses on changes specific to this version, but all changes from
3.2.22.RELEASEand3.3.12.RELEASEare also included.✨ New features and improvements
Timedwrapper object, allowing richer output ofDurationcompared toelapsed()andtimestamp()(which useTuple2andLong)LoggerUtilsallows the early installation of aLoggerfactory that will forward to a classic factory AND let the user activate a logging indirection later on during testsTestLoggerto capture internal logs from operators that were classloaded earlier than the unit testTestPublishercreateColdNonCompliantvariantContextinStepVerifier, say from which operator the asserted Context was taken (#2518)🪲 Bug fixes
RetryWhenMainSubscriber#onError's calls serial (#2499, Fixes #2488)📖 Documentation, Tests and Build
👍 Thanks to the following contributors that also participated to this release
@dowgiallom, @seants
v3.4.0Compare Source
Reactor-Core
3.4.0is part of2020.0.0Release Train (codenameEuropium).This is the first GA release of Europium 🎉
This note focuses on
3.4.0proper, curating changes from across all milestones.Note that the 3.4.0 effort was started right after
3.3.5.RELEASE, so this version also contains changes from 3.3.6 to 3.3.11 (see the end of the notes for links).firstWithValuenew operator has an undocumented way of checking the cause of failure for individual sources, but it uses a suppressed exception rather than a cause. Please refrain from using that, as we'll switch toinitCausein3.4.1(and properly document the behavior, setting it in stone) => #2459WorkQueueProcessorandTopicProcessor, #2208)Schedulers.elastic()and variants are deprecated, to be removed in 3.5 (#1893)FluxProcessor(as well as all concrete implementations of it) are now deprecated and will be removed in 3.5 (#2188, #2431)MonoProcessoris made abstract and deprecated, to be removed in 3.5 (#2188, #1053 /f04bede, #2431)Flux.subscribe(Consumer<Subscription>)variant is deprecated, to be removed in 3.5 (#1825)firstis deprecated to be renamed tofirstWithSignal(seefirstWithValuein the new features below). The old deprecated method will be removed in 3.5 (#2173)Contextchanges (#2282):Contextat points where there is no use attempting to use write methods are deprecated and will be removed in 3.5 (#2293,7d6c862)ContextView-based variant (see new features below)deferWithContext=>deferContextualwith aContextViewSignal.getContext()=>Signal.getContextView()Contextare renamed to be clearer. Old names are deprecated and will be removed in 3.5 (see new feature below, #2148,eed93d6)Durationand convert it to milliseconds now use nanosecond precision (#1734)Operators.onErrorDroppedno longer throws, but only logs the dropped exception (#1431)onErrorsignal reaches the last (lambda based) subscriber in a chain which doesn't have an error handler, the exception is no longer thrown but only logged (#2176)Schedulernow initiate their backing infrastructure and applySchedulersdecorator instart()rather than the constructor (#1778)start()is also now implicitly called when instantiating aSchedulervia theSchedulers.Factorythisleaking from constructorstart()EmitterProcessorwith a full backpressure queue no longer blocks until data is requested, but fails fast (#2049)nameoperator (#1928, #2302)flowtag has been removed entirelyname({String})operator will replacereactor.prefix in meter names with the user-provided{String}.tags(String...)operator, but notname(String)still creates a sparse set of tags in the application which could be rejected by some metrics backendreactor_requested_requested_amount=>{name}_requestedreactor_subscribed_subscribers=>{name}_subscribed{name}into account from the above changestatustag, introducingcompletedEmptyvalue (#1803)SinksSinksare a new API constructed to replace theFluxProcessorandMonoProcessorAPIs, which have been deprecated (#2431, #1053).We distinguish
Sinks.Many<T>(aFlux-like sink),Sinks.One<T>(aMono-like sink) andSinks.Empty(aMono<Void>-like sink).These sinks are constructed through specs under the
Sinksclass. They expose a two-faced API:tryEmitare atomic, never throw (#2319, #2329, #2336, #2426) and immediately return anEmitResultenum (originally named Emission) indicating various variations of success or error (#2319, #2338)emitattempt to provide an easier facade over the above, take anEmitFailureHandlerallowing to fine tune some aspects of the default behavior (#2377)By default, the instances are "serialized", detecting parallel usage and failing fast in
tryEmit(#2342, #2410, #2365,19fc1ba, #2412).The vanilla reactor sink implementations of
emitAPI terminate with the equivalent of anemitErrorwhen parallel usage is detected (#2365) but by using theEmitFailureHandlerto drive the sink to retry, possibly with a small amount of sleeping, it should be possible to optimistically get rid of the contention.It is also possible to get a low-overhead, low-protection instance of vanilla sinks by using the
Sinks.unsafe()spec (#2418).This doesn't detect parallel usage, so it must be used in a responsible way (in a context where the Reactive Streams contract is already externally enforced).
Sinks also expose a
asFlux()view (orasMono(), as relevant) for them to be passed to downstream and subscribed, and also expose a bit of state throughcurrentSubscriberCount()getter (#2372) and by beingScannable(at a minimum forTERMINATEDandCANCELLEDattributes, #2394).Compared to existing processors, most flavors have a sink equivalent except
DirectProcessor, with two close cousins underSinks.many().multicast()(#2392, #2451):directAllOrNothingwill ignoretryEmitNextattempts when at least one subscriber doesn't have enough demand,directBestEffortwill instead push to the subset of subscribers with demand and drop from the perspective of slow subscribers.This differs from
DirectProcessorin the sense that both these sinks are kept open in such a situation, so slow subscribers that increase their request will start seeing values pushed after that (instead of being immediately terminated in DirectProcessor).There is also a new flavor: an
onBackpressureError()variant of the unicast Sink (#2347)🐞 Bugfixes
See links to Dysprosium releases (3.3.6 to 3.3.11) at the end.
✨ New features
concatMapnow has a variant with 0 prefetch (#2202)Scannableoperators answer the newAttr.RUN_STYLEattribute with aRunStyleenum (#2058, #2123)PublisherandSubscriberlevelRunStyle.SYNCguarantees the operator doesn't change threadsRunStyle.ASYNCindicates the operator MAY change threadsRunStyle.UNKNOWN(the default) indicates there's no available information (eg. due to the operator wrapping an arbitraryPublisher)MetricsRegistryother than the global one can now be configured (#2253,64fd556)Metrics.MicrometerConfiguration#useRegistryfor that purposeContextnow extends a simplifiedContextViewAPI which only expose the read methods (#2279, #2293)Contextwhen the only meaningful operations are read operationsSignal#getContextView(),deferContextualoperator (variant to deferWithContext) and newtransformDeferredContextualoperatortransformDeferredContextualoperator that takes aBiFunction, allowing to access theContextViewin the transformation (#2280 then renamed in #2293)Mono.subscribe(valueConsumer, errorConsumer, ...)errorConsumernow gets notified of exceptions thrown by the valueConsumer(#1995)Contextoperators with clearer names (#2148,eed93d6)Mono.subscriberContext()is not aliased, we now advise to useMono.deferContextual(Mono::just)to get the exact same behaviorsubscriberContext(Context)is replaced bycontextWrite(ContextView)(notice the use ofContextView)contextWrite(Function)f9c7993)Schedulers.setFactoryWithSnapshot(Factory)to get aSnapshotobject while replacing theFactoryresetFrom(Snapshot)VirtualTimeSchedulerto reset previously customized factoriesParallelFlux.subscribe(array)method is now public to allow delegation in wrappers (#2328)Retryobject driving#retryWhenoperator can now store user-provided state in the form of aContextView, which is exposed throughRetrySignal(#2312,bd8db8a)GroupedFlux#key()method is now marked as@NonNull(#2397)firstWithValuefactory operator (#2173,41c937f)first, it let multiple sources competeNoSuchElementExceptionis thrown📈 Improvements
log()will log context access at FINE(ST) level and now uses the more correctcurrentContextprefix (#2220)Mono#materialize()now takes into account that the source IS aMono, so it doesn'tcancel()it when materializing itsonNext(#2424,765bfe8)📖 Documentation, Tests and Build
85da74b)👍 Thanks to the following contributors that also participated to this release
@AayushyaVajpayee, @camsteffen, @cnabro, @hamidshahid, @Inego, @jonenst, @josemalonsom, @OlegDokuka, @robotmrv, @seants, @smaldini, @steppedreckoner, @yschimke
Links to Dysprosium release notes during 3.4.0 development effort
All changes from these releases have been forward-merged into
3.4.0:v3.3.6.RELEASEv3.3.7.RELEASEv3.3.8.RELEASEv3.3.9.RELEASEv3.3.10.RELEASEv3.3.11.RELEASEv3.3.22.RELEASECompare Source
This is the last release of 3.3.x, as the Dysprosium line is now EoL
What's Changed
@NonNullannotation, not JetBrain's NotNull by @simonbasle in Use@NonNullannotation, not JetBrain's NotNull reactor/reactor-core#2808New Contributors
Full Changelog: reactor/reactor-core@v3.3.21.RELEASE...v3.3.22.RELEASE
v3.3.21.RELEASECompare Source
Reactor-Core
3.3.21is part ofDysprosium-SR24Release Train.This service release contains one bugfixe and dependency bumps (including Gradle 7.2).
🐞 Bug fixes
📖 Documentation, Tests and Build
v3.3.20.RELEASECompare Source
Reactor-Core
3.3.20.RELEASEis part ofDysprosium-SR23Release Train.This service release contains bugfixes and polishing.
✨ New features and improvements
FluxOnBackpressureBufferStrategyreject sizes <= 0 (#2757)🪲 Bug fixes
📖 Documentation, Tests and Build
👍 Thanks to all contributors who participated to this release
@hisener
v3.3.19.RELEASECompare Source
Reactor-Core
3.3.19.RELEASEis part ofDYSPROSIUM-SR22Release Train.This service release contains a bugfix, as well as some build/ci polishing.
🪲 Bug fixes
📖 Documentation, Tests and Build
spotlessplugin introduced to check java headers (#2722, #2732)v3.3.18.RELEASECompare Source
Reactor-Core
3.3.18.RELEASEis part ofDysprosium-SR21Release Train.This minor service release contains a few test and build enhancements.
📖 Documentation, Tests and Build
72eaa4a,2e9fb8e)v3.3.17.RELEASECompare Source
Reactor-Core
3.3.17.RELEASEis part ofDysprosium-SR20Release Train.This service release contains a few bugfixes and enhancements.
✨ New features and improvements
29d2e3b)🪲 Bug fixes
📖 Documentation, Tests and Build
main, update CI (#2679)174afcc)v3.3.16.RELEASECompare Source
Reactor-Core
3.3.16.RELEASEis part ofDysprosium-SR19Release Train.This service release contains bugfixes and a couple implementation improvements.
✨ New features and improvements
🪲 Bug fixes
📖 Documentation, Tests and Build
👍 Thanks to the following contributors that also participated to this release
@bruto1
v3.3.15.RELEASE[Compare Sou
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.