Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump reactor-core from 3.3.0.RELEASE to 3.3.3.RELEASE #110

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps reactor-core from 3.3.0.RELEASE to 3.3.3.RELEASE.

Release notes

Sourced from reactor-core's releases.

v3.3.3.RELEASE

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

  • 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

reactor-core 3.3.2.RELEASE is part of Dysprosium-SR3 Release Train.

💥 Known issues

  • (since 3.3.0.M2) There are regressions with Flux.replay/cache hanging or delivering wrong data (tracked in #2030)

⚠️ Update considerations and deprecations

  • Documentation zip file is now published with -docs classifier (#1975)
... (truncated)
Commits
  • 1b83ddc [artifactory-release] Release version 3.3.3.RELEASE
  • 23f53b2 Prepare release 3.3.3.RELEASE
  • d5bb63f Merge 3.2.x californium release (ignored)
  • 5851b4c [artifactory-release] Next development version 3.2.16.BUILD-SNAPSHOT
  • 8dbeacf [artifactory-release] Release version 3.2.15.RELEASE
  • 9c78ac6 Prepare release 3.2.15.RELEASE
  • 537a0ff Merge polish of flakky test (25508301) into 3.3
  • 2550830 [Polish] Fix a flakky test
  • f9cd50c fix #2050 Use stream().sequential() for Context default putAll
  • c0a7bb8 fix #1992 Reimplement boundedElasticScheduler to allow reentrancy
  • Additional commits viewable in compare view

Dependabot compatibility score

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:

  • 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)

Bumps [reactor-core](https://github.com/reactor/reactor-core) from 3.3.0.RELEASE to 3.3.3.RELEASE.
- [Release notes](https://github.com/reactor/reactor-core/releases)
- [Commits](reactor/reactor-core@v3.3.0.RELEASE...v3.3.3.RELEASE)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Feb 25, 2020
@dependabot-preview
Copy link
Contributor Author

Superseded by #113.

@dependabot-preview dependabot-preview bot deleted the dependabot/maven/io.projectreactor-reactor-core-3.3.3.RELEASE branch March 24, 2020 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants