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

chore(deps): update dependency com.lmax:disruptor to v4 - autoclosed #1990

Closed
wants to merge 1 commit into from

Conversation

solrbot
Copy link
Collaborator

@solrbot solrbot commented Oct 8, 2023

This PR contains the following updates:

Package Type Update Change
com.lmax:disruptor (source) dependencies major 3.4.4 -> 4.0.0

Release Notes

LMAX-Exchange/disruptor (com.lmax:disruptor)

v4.0.0

Compare Source

  • Minimum Java version now 11
  • Issue #​323 - WorkerPool and WorkProcessor have been removed, no more Disruptor::handleEventsWithWorkerPool
  • Disruptor constructors using Executor have been removed. Use ThreadFactory instead.
  • Rolled up event handling extension interfaces on to EventHandler:
    • BatchStartAware
    • LifecycleAware
    • SequenceReportingEventHandler
  • FatalExceptionHandler and IgnoreExceptionHandler now use the JDK 9 Platform Logging API, i.e. System.Logger
  • Add rewind batch feature to the BatchEventProcessor
  • Add a maximum batch size argument to BatchEventProcessor
    • EventHandler::onBatchStart now gets both the batchSize as well as queueDepth (previously it had batchSize which reported queue depth)
  • Added documentation to EventPoller
  • Util::log2 throws if passed a non-positive argument
  • Deprecations
    • Deprecated ThreadHints.onSpinWait()
    • Deprecated Disruptor.handleExceptionsWith() - this had been javadoc deprecated since 2015 but not in the code
    • Removed previously deprecated methods
      • Ringbuffer.resetTo()
      • ConsumerRepository.getLastSequenceInChain()

Configuration

📅 Schedule: Branch creation - "* * * * *" (UTC), Automerge - 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot

@solrbot solrbot force-pushed the renovate/com.lmax-disruptor-4.x branch from 1a3a923 to 7938790 Compare December 13, 2023 22:36
@solrbot solrbot force-pushed the renovate/com.lmax-disruptor-4.x branch from 7938790 to b9bbfd2 Compare February 27, 2024 16:45
@github-actions github-actions bot added the dependencies Dependency upgrades label Feb 27, 2024
@solrbot solrbot force-pushed the renovate/com.lmax-disruptor-4.x branch from b9bbfd2 to c839462 Compare March 20, 2024 01:26
Copy link

This PR had no visible activity in the past 60 days, labeling it as stale. Any new activity will remove the stale label. To attract more reviewers, please tag someone or notify the [email protected] mailing list. Thank you for your contribution!

@github-actions github-actions bot added the stale PR not updated in 60 days label Jun 27, 2024
@github-actions github-actions bot removed the stale PR not updated in 60 days label Jul 17, 2024
@solrbot solrbot force-pushed the renovate/com.lmax-disruptor-4.x branch from c839462 to 26b2072 Compare July 18, 2024 20:25
@solrbot solrbot changed the title Update dependency com.lmax:disruptor to v4 chore(deps): update dependency com.lmax:disruptor to v4 Jul 22, 2024
@solrbot solrbot force-pushed the renovate/com.lmax-disruptor-4.x branch from 26b2072 to fd5b226 Compare July 23, 2024 16:29
@solrbot solrbot changed the title chore(deps): update dependency com.lmax:disruptor to v4 Update dependency com.lmax:disruptor to v4 Jul 29, 2024
@solrbot solrbot changed the title Update dependency com.lmax:disruptor to v4 chore(deps): update dependency com.lmax:disruptor to v4 Aug 7, 2024
@solrbot solrbot changed the title chore(deps): update dependency com.lmax:disruptor to v4 Update dependency com.lmax:disruptor to v4 Aug 13, 2024
Copy link

This PR has had no activity for 60 days and is now labeled as stale. Any new activity will remove the stale label. To attract more reviewers, please tag people who might be familiar with the code area and/or notify the [email protected] mailing list. To exempt this PR from being marked as stale, make it a draft PR or add the label "exempt-stale". If left unattended, this PR will be closed after another 60 days of inactivity. Thank you for your contribution!

@github-actions github-actions bot added the stale PR not updated in 60 days label Oct 13, 2024
@github-actions github-actions bot removed the stale PR not updated in 60 days label Nov 4, 2024
@malliaridis
Copy link
Contributor

malliaridis commented Nov 6, 2024

lmax.disruptor is used for asynchronous logging (performance) and is required by log4j. Support for lmax.disruptor v4 is introduced in logj4 2.23.0, and therefore this PR depends on #2047. Additionally, log4j 2.22.0+ requires JDK 17+, therefore this cannot be backported to branch_9x.

@solrbot solrbot changed the title Update dependency com.lmax:disruptor to v4 chore(deps): update dependency com.lmax:disruptor to v4 Nov 7, 2024
@solrbot solrbot changed the title chore(deps): update dependency com.lmax:disruptor to v4 chore(deps): update dependency com.lmax:disruptor to v4 - autoclosed Nov 15, 2024
@solrbot solrbot closed this Nov 15, 2024
@solrbot solrbot deleted the renovate/com.lmax-disruptor-4.x branch November 15, 2024 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Dependency upgrades
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants