dependabot[bot] opened a new pull request, #2271: URL: https://github.com/apache/logging-log4j2/pull/2271
Bumps [org.zeromq:jeromq](https://github.com/zeromq/jeromq) from 0.5.4 to 0.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zeromq/jeromq/blob/master/CHANGELOG.md";>org.zeromq:jeromq's changelog</a>.</em></p> <blockquote> <h2>v0.6.0 (2024-02-04)</h2> <h3>Added</h3> <ul> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/964";>#964</a> <a href="https://redirect.github.com/zeromq/jeromq/pull/964";>zeromq/jeromq#964</a> Exports all options default values as constant in ZMQ class. This will allow client libraries to use them.</p> </li> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/963";>#963</a> (<a href="https://redirect.github.com/zeromq/jeromq/pull/963";>zeromq/jeromq#963</a>) Replaces maven-bundle-plugin with the more up-to-date bnd-maven-plugin and configures it to generate a JPMS module descriptor besides the OSGi descriptor.</p> </li> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/949";>#949</a> (<a href="https://redirect.github.com/zeromq/jeromq/pull/949";>zeromq/jeromq#949</a>) Added a way to specify a custom monitor, that don’t need to communicate through a ZMQ socket. It allows to use monitor for logging without hitting hard on the CPU with poller overload. Improved in <a href="https://redirect.github.com/zeromq/jeromq/issues/950";>#950</a> (<a href="https://redirect.github.com/zeromq/jeromq/pull/950";>zeromq/jeromq#950</a>)</p> </li> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/942";>#942</a> (<a href="https://redirect.github.com/zeromq/jeromq/pull/942";>zeromq/jeromq#942</a>) <code>zmq.Ctx</code> can now be provided a thread factory, that can used to tweaks threads. The main purpose of this is to be able to bind thread to CPU using external libraries like <a href="https://github.com/OpenHFT/Java-Thread-Affinity";>https://github.com/OpenHFT/Java-Thread-Affinity</a>. The idea was suggested by issue <a href="https://redirect.github.com/zeromq/jeromq/issues/910";>#910</a>.</p> </li> <li> <p>Also adding a check that prevent modifications of some settings once they have been used by <code>zmq.Ctx</code> initialisation.</p> </li> </ul> <h3>Changed</h3> <ul> <li> <p>Many code smell removed using SonarLint.</p> </li> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/941";>#941</a> (<a href="https://redirect.github.com/zeromq/jeromq/issues/940";>zeromq/jeromq#940</a>) Fix to issue <a href="https://redirect.github.com/zeromq/jeromq/issues/940";>#940</a> by setting `key=null on setKey, added test</p> </li> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/939";>#939</a> (<a href="https://redirect.github.com/zeromq/jeromq/issues/939";>zeromq/jeromq#939</a>) Simplified Mailbox, always thread safe, so `MailboxSafe usages are removed and the class is marked at deprecated.</p> </li> <li> <p><a href="https://redirect.github.com/zeromq/jeromq/issues/936";>#936</a> (<a href="https://redirect.github.com/zeromq/jeromq/pull/936";>zeromq/jeromq#936</a>)</p> <p><code>org.zeromq.ZSocket</code> and <code>org.zeromq.ZMQ.Socket</code> can now read and write <code>zmq.Msg</code> directly.</p> <p>Updating <code>Metada</code> class to provide more data access and functions. <code>ZMetadata</code> is updated too. It internally now uses <code>ConcurrentHashMap</code> instead of the old <code>Properties class</code>. The <code>Properties</code> class ignore null values, <code>ConcurrentHashMap</code> reject them but ZMTP protocol allows empty values. So null values are transformed to empty strings.</p> <p><code>Metada#set</code> is deprecated and replaced by <code>Metada#put</code>, to be more consistent with Map API.</p> <p>Lots of hostile final method declaration removed.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/zeromq/jeromq/commits";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
