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

fix(deps): update dependency org.zeromq:jeromq to v0.6.0 - autoclosed #75

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 3, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.zeromq:jeromq 0.5.2 -> 0.6.0 age adoption passing confidence

Release Notes

zeromq/jeromq (org.zeromq:jeromq)

v0.6.0

Added
Changed
  • Many code smell removed using SonarLint.

  • [#​941] (https://github.com/zeromq/jeromq/issues/940)
    Fix to issue #​940 by setting `key=null on setKey, added test

  • [#​939] (https://github.com/zeromq/jeromq/issues/939)
    Simplified Mailbox, always thread safe, so `MailboxSafe usages are removed and the class is marked at deprecated.

  • [#​936] (https://github.com/zeromq/jeromq/pull/936)

    org.zeromq.ZSocket and org.zeromq.ZMQ.Socket can now read and write zmq.Msg directly.

    Updating Metada class to provide more data access and functions. ZMetadata is updated too. It internally now uses
    ConcurrentHashMap instead of the old Properties class. The Properties class ignore null values, ConcurrentHashMap
    reject them but ZMTP protocol allows empty values. So null values are transformed to empty strings.

    Metada#set is deprecated and replaced by Metada#put, to be more consistent with Map API.

    Lots of hostile final method declaration removed.

v0.5.4

Changed
  • new GPG signature for artifact, id 9C925EE.

  • #​935: With
    org.zeromq.ZMQ.Event.recv(socket, DONTWAIT), if there is no more,
    event to receive, it throws an NPE although the javadoc says it should
    return null. Fixed.

    Also don’t resolve event value for ZMQ_EVENT_MONITOR_STOPPED, it’s a constant.

  • [#​937] (https://github.com/zeromq/jeromq/pull/937): When doing PLAIN or CURVE
    authentication, the logic can be exchanged. The client is doing the bind, and
    the server doing the connect. That was not handled, a connect socket was not
    expected to reuse the session, and so found an already configured zapPipe. It’s
    now handled.

    Some error message was not returning any message, the specification says that an empty error should be returned instead.

    Big rewrite of the tests for mechanisms, the big test function is split and more code is shared.

v0.5.3

Added
  • #​921: Add peer support
    disconnect

  • #​906: Fix issue where
    socket identity was failing with overflow when identity was bigger
    than 127

  • #​903: Make JeroMQ
    compatiable with Android API Level 19

  • #​902: Add tests and
    build on Java 17. Helping dependecies resolution by activating more
    profiles and don't try to publish on forks

  • #​775: ZMQ_HEARTBEAT is not
    useful without sending an hello message.To solve that, the majordomo worker
    still has to implement heartbeat. With this new option, whenever the
    connection drops and reconnects the hello message will be sent, greatly
    simplify the majordomo protocol, as now READY and HEARTBEAT can be handled by
    zeromq.

  • #​783: Jeromq is not thread-safe,
    so port CLIENT and SERVER sockets from libzmq, which are thread-safe sockets.

  • #​808: Add Client/Server support
    to ZFrame.

  • #​837: Radio-Dish implementation.

  • #​880: Port of
    https://github.com/zeromq/libzmq/pull/38713871, router can handle peer
    disconnected.

  • #​898: Adding critical and
    notification exceptions handlers in zmq.poll.Poller.

Changed
  • #​919: Fix deadlock
    issue on socket close

  • #​906: Fix issue where
    socket identity was failing with overflow when identity was bigger
    than 127

  • #​903: Make JeroMQ
    compatiable with Android API Level 19

  • #​777: ZMQ.Socket now remember
    the ZContext that created it and remove from it when closed.

  • Many improvement to error handling, with more error messages.

  • #​772: Fix ZMQ_REQ_CORRELATE.

  • #​797: A new ZBeacon implementation.

  • #​814: IPC protocol now comply to
    java.net.preferIPv4Stack or java.net.preferIPv6Addresses for the choice of
    the TCP stack to use.

  • #​825: Improved monitor, with
    added events in some mechanisms.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/jeromq branch from 32a8e1a to c9641bf Compare September 3, 2023 16:09
@renovate renovate bot changed the title fix(deps): update dependency org.zeromq:jeromq to v0.5.3 fix(deps): update dependency org.zeromq:jeromq to v0.5.4 Sep 26, 2023
@renovate renovate bot force-pushed the renovate/jeromq branch from 29cfde5 to 84bfe15 Compare February 6, 2024 19:40
@renovate renovate bot changed the title fix(deps): update dependency org.zeromq:jeromq to v0.5.4 fix(deps): update dependency org.zeromq:jeromq to v0.6.0 Feb 6, 2024
@renovate renovate bot changed the title fix(deps): update dependency org.zeromq:jeromq to v0.6.0 fix(deps): update dependency org.zeromq:jeromq to v0.6.0 - autoclosed Jul 31, 2024
@renovate renovate bot closed this Jul 31, 2024
@renovate renovate bot deleted the renovate/jeromq branch July 31, 2024 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants