Simon Baslé <sbasle@vmware.com>: Author Summary

Builds triggered by Simon Baslé <sbasle@vmware.com>

Builds triggered by an author are those builds which contains changes committed by the author.
88
10 (11%)
78 (89%)

Breakages and fixes

Broken means the build has failed but the previous build was successful.
Fixed means that the build was successful but the previous build has failed.
10 (11% of all builds triggered)
8 (9% of all builds triggered)
-2
Build Completed Code commits Tests
REACTOR › RNEXT › #2940 18 hours ago
fix #2451 directBestEffort sink to return OK when fast+slow subscribers
7613 passed
REACTOR › RPOOL › #128 5 days ago
polish #103 0.2.0 Context propagation uses latest Context APIs (#105)
345 passed
REACTOR › RPOOL › #127 5 days ago
Merge branch '0.1.x' into master to take backport into consideration
backport #103 Propagate context from acquire/warmup to allocator
This commit ensures that any `Context` set on either the `acquire()`
Mono or the `warmup()` Mono is passed along to the pool allocator Mono.

Mistakenly merged into 0.2.0 (master), this is a backport of the
original commit.

Reviewed-in: #104
Backport-from: c9db622cef795f5fa534486d876627c77e791539
345 passed
REACTOR › RPOOL › #126 5 days ago
fix #103 Propagate context from acquire/warmup to allocator
This commit ensures that any `Context` set on either the `acquire()`
Mono or the `warmup()` Mono is passed along to the pool allocator Mono.

Reviewed-in: #104
345 passed
REACTOR › RNEXT › #2935 6 days ago
Merge #2436 into 3.4.0
fix #2436 Polish some 3.2 JUnit5 tests and compiler options
This commit is a follow-up to #2344 / #2395, polishing things on 3.2.x.
Merge #2436 into 3.3.11.RELEASE
7608 passed
REACTOR › RNEXT › #2934 1 week ago
fixup merge of #2395 resulting in different commit SHA1
 - in PR and prepared merge commits by @ericbottard we had
 afad7802733ad5958d0748292e05b52e76cab899

 - in GitHub "merge with rebase" to 3.2.x we had
 37b3cee315e03fcab092e557036c904da9fb787e
Merge #2344 into 3.4.0
7608 passed
REACTOR › NEXT › #3091 1 week ago
FluxProcessor and child are now deprecated (#238)
See https://github.com/reactor/reactor-core/issues/2431
and reactor/reactor-core@c7b837d928cc4b29d328d12a3b2bb7561f0d4a0f
364 passed
REACTOR › RNEXT › #2927 1 week ago
fix #2431 Deprecate [Flux|Mono]Processor contracts entirely
This commit deprecates `FluxProcessor` and `MonoProcessor` abstract
classes, in preparation for removal in 3.5.

The concrete child classes were already deprecated, but we initially
intended to keep the abstract contracts. However, most of the APIs
on these two classes are problematic. In the end, we don't think there
are any usage of processors that cannot be reworked into `Sinks` or
another combination of Reactor features / operators.

Another issue is that the Reactor processor APIs has too many
responsibilities, some of which are not relevant in all flavors.

In that regard, the new sinks APIs are far leaner, which also means that
adapting a `Sinks.Many` into a `FluxProcessor` or a `Sinks.One` into a
`MonoProcessor` is not truly possible.

So rather than artificially prolonging the lifetime of the abstract
processors by an extra release train cycle, we elected to deprecate
them right now. This will more strongly enforce a migration to the new
sinks, which is a good thing in the long run (even enabling us to add
more flavors down the road).

As a side effect of this decision, this commit also entirely removes the
`fromSink` adapters that were introduced in 3.4.0-M2.

See the issue https://github.com/reactor/reactor-core/issues/2431 for
further pointers at how to replace usages of processors, as well as
guidance if you think you cannot do without a `FluxProcessor` or a
`MonoProcessor`.

Reviewed-in: #2432
7608 passed
REACTOR › RNEXT › #2926 1 week ago
[polish] Remove unchecked warnings around Sinks
 - in SinkManyBestEffortTest
 - in DirectProcessor
7608 passed
REACTOR › RPOOL › #121 1 week ago
fix #98 Don't fail too fast to acquire if maxPending is reached
This commit ensures that the pool rejects an `acquire` call ONLY if
the `maxPending` is about to be reached AND the pool has no available
element nor capacity to allocate a new one (in a best effort fashion).
[build] Add jcstress plugin
fix #86 Add background eviction
This commit adds an option for background eviction of resources in case
no activity is registered on the pool.

Note that the background eviction is best effort, and will back off
if there are concurrent release / acquire activity. The later actually
checks the eviction predicate too, which allows for some amount of
eviction to occur even if the background task has backed off.

Reviewed-in: #100
Merge #98 #86 into 0.2.0-RC2
[build] Remove errorprone and spring-io plugins
337 passed
Build Completed Code commits Tests
REACTOR › RNEXT › #2908 3 weeks ago
[polish] Polish VoidProcessor and NextProcessor tests
 - Make VoidProcessor implement isDisposed/isCancelled
 - Polish VoidProcessor tests (remove UppercasePrefix, use JUnit5,
   ensure subscribes have error handlers to avoid excessive logging)
 - Polish NextProcessor tests (remove UppercasePrefix, ensure subscribes
   have error handlers to avoid excessive logging)
fix #2394 Make sinks scannable for TERMINATED (and CANCELLED)
1 of 7190 failed
REACTOR › RNEXT › #2903 1 month ago
Merge #2389 into 3.4.0-RC2
1 of 7178 failed
REACTOR › RKAFKA › #890 1 month ago
Prepare release 1.3.0-RC1
Testless build
REACTOR › NETTYWIN › #1141 1 month ago
Back to snapshots
1 of 749 failed
REACTOR › RNETTY › #2199 1 month ago
Prepare release 1.0.0-RC1
1 of 749 failed
REACTOR › RNEXT › #2895 1 month ago
fix #2338 Add new Emission FAIL_ZERO_SUBSCRIBER error code
Reviewed-in: #2357
1 of 7169 failed
REACTOR › RNEXT › #2891 1 month ago
Merge #2362 into 3.4.0-RC1
Merge #2362 into 3.3.10.RELEASE
This merge commit includes reintroduction of cleanup() as well as
adaptation to the fact that `ctx` isn't a field anymore in 3.3.
fix #2362 Prevent ConcurrentModificationEx on bufferPredicate discard
This commit adds some internal synchronization of the buffer in
FluxBufferPredicate in order to ensure that cancellation racing with
onNext doesn't trigger a ConcurrentModificationException (due to the
buffer being iterated by onDiscard while onNext adds an element to it).
Testless build
REACTOR › REACTORRMQ › #416 2 months ago
Back to snapshots
1 of 97 failed
REACTOR › RSITE › #203 3 months ago
Take Version style into account when comparing versions
Testless build
REACTOR › SITENEXT › #3583 3 months ago
Take Version style into account when comparing versions
Testless build
Build Completed Code commits Tests
REACTOR › RNEXT › #2904 1 month ago
[build] Polish granularity of stacks for Nested tests
[polish] Increase timeout duration to 1ms to avoid hiccups
[polish] Leftover use of inners().count() instead of currentSubscriberCount()
7533 passed
REACTOR › RKAFKA › #894 1 month ago
Back to core snapshot
155 passed
REACTOR › RNETTY › #2200 1 month ago
Prepare release 1.0.0-RC1 (bump deps)
748 passed
REACTOR › RNEXT › #2896 1 month ago
Let UnicastManySinkNoBackpressure switch to terminal state (#2367)
This commit polishes the new unicast onBackpressureError so that it
performs the state transition to the TERMINATED state when completing
or erroring the sink.

Also contains some state checks code style polish.
7526 passed
REACTOR › RNEXT › #2892 1 month ago
Merge fixup commit 480f976f4 into 3.4
 - Missing Assertions import
 - Mistakenly replaced a usage of `b` with a usage of `buffer`

See: 480f976f4
See: #2362
fixup merge issues of #2362
 - Missing Assertions import
 - Mistakenly replaced a usage of `b` with a usage of `buffer`

See: 480f976f4
See: #2362
7510 passed
REACTOR › NEXT › #3081 2 months ago
[fixup] Fix test compilation for 3.4.0-M2
364 passed
REACTOR › SITENEXT › #3584 3 months ago
Version#equals should take qualifierVersion into account
Fix compareTo order: evaluate style after qualifierVersion
Testless build
REACTOR › RSITE › #204 3 months ago
Version#equals should take qualifierVersion into account
Fix compareTo order: evaluate style after qualifierVersion
Testless build