Bump reactor-core from 3.3.4.RELEASE to 3.3.5.RELEASE

[dependabot-preview[bot]]

Bumps reactor-core from 3.3.4.RELEASE to 3.3.5.RELEASE.

Release notes

Sourced from reactor-core's releases.

v3.3.5.RELEASE

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

It also contains all fixes from 3.2.17.RELEASE.

:warning: 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

:sparkles: 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

:beetle: Bug fixes

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

:book: 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 (e4fe960c)

:+1: Thanks to the following contributors that also participated to this release

@OlegDokuka, @pimlock

Commits

• 8571d5d [artifactory-release] Release version 3.3.5.RELEASE
• 9809a9d Prepare release 3.3.5.RELEASE
• ffeaf6d Merge-ignore release 3.2.17
• b3c6230 [artifactory-release] Next development version 3.2.18.BUILD-SNAPSHOT
• d709e29 [artifactory-release] Release version 3.2.17.RELEASE
• efde895 Prepare release 3.2.17.RELEASE
• 714c045 [doc] Polish doc of Iterable operators, clarify iterator() calls (#2135)
• c3839c9 Merge #2134 into 3.3
• d61d331 Fix onDiscard leaks in fused operators with queue (#2134)
• 48ed884 Merge #2126 into 3.3
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)