Subject: CVS commit: pkgsrc/net/rabbitmq
From: Adam Ciarcinski
Date: 2021-09-28 18:22:27
Message id: 20210928162227.7D853FA97@cvs.NetBSD.org

Log Message:
rabbitmq: updated to 3.9.7

3.9.7:
All Components

All bytecode is now compiled using the +deterministic compiler flag. This should \ 
eliminate the capture of some irrelevant build environment attributes in \ 
produced artifacts, improve consistency between builds, and reduce the file \ 
level diff between release artifacts.
Core Server

Enhancements

Classic queue shutdown now uses a much higher timeout (up to 10 minutes instead \ 
of 30 seconds).

In environments with many queues (especially mirrored queues) and many consumers \ 
this means that the chance of queue indices rebuilding after node restart is now \ 
substantially lower.
Prometheus Plugin

Enhancements

More configurability for metrics exposed via the Prometheus endpoint.
Shovel Plugin

Bug Fixes

Shovel URIs could be logged with credentials in some scenarios.

3.9.6:
Core Server

Bug Fixes

TLS information delivered in Proxy protocol header is now attached to connection \ 
metrics as if it was provided by a non-proxying client.
max_message_size had a one-off error in the validator.
mirroring_sync_batch_size was incorrectly validated as if it represented batch \ 
size in bytes. It represents batch size in number of messages, so the new \ 
default hard cap is now 1M (a very high number that's impractical)
Stream Plugin

Bug Fixes

Offset parameters were not stored correctly in some cases.
Partitions list order is now stable.
When stream clients close connections abruptly, publisher and consumer metrics \ 
get cleaned up correctly.
Management Plugin

Enhancements

Stream publishers are now listed on the individual stream page.
Counters have been added to the tiles of several sections on detail pages.

3.9.5:
Core Server

Bug Fixes

Virtual host metadata (description, tags) was not imported from definitions.
Reduced unnecessary debug logging from streams.
AWS Peer Discovery Plugin

Enhancements

AWS API calls are now retried multiple times.

Contributed by AWS.
Management Plugin

Enhancements

PUT /api/vhosts/{name} now can update metadata (tags and descriptions) for \ 
existing virtual hosts.

3.9.4:
Core Server

Enhancements

New Prometheus metrics for alarms
Nodes will now use four more environment variables, if set: \ 
RABBITMQ_DEFAULT_USER (overrides default_user in rabbitmq.conf), \ 
RABBITMQ_DEFAULT_PASS (overrides default_pass), RABBITMQ_DEFAULT_VHOST \ 
(overrides default_vhost) and RABBITMQ_ERLANG_COOKIE (sets shared authentication \ 
secret value). These variables are not recommended to be used in production but \ 
can be the only realistic option in some environment, such as service \ 
containers, ECS, and so on. Most users should continue using rabbitmq.conf and a \ 
securely generated local cookie file.
Definitions now can be imported from different sources, including those provided \ 
by plugins. Original local filesystem source is still supported in a \ 
backwards-compatible way.

3.9.3:
Core Server

Bug Fixes

Queues that had messages with per-message TTL in them could fail to recover \ 
their indices after a restart.
JSON logging could fail with an exception when a logged event included \ 
epoch-based timestamp value.
JSON logging now uses integers (as opposed to floats) to represent epoch-based \ 
timestamps

Enhancements

RabbitMQ application no longer reports the stopping event to systemd. This was \ 
counterproductive when the application was stopped but the runtime (Erlang VM) \ 
was kept running, e.g. via rabbitmqctl stop_app or by the pause minority \ 
partition handling strategy.

Now systemd service monitoring will recognize a node as stopped only when the \ 
runtime is stopped, which is usually the behavior operators expect.

3.9.2:
CLI Tools

Bug Fixes

rabbitmq-upgrade drain and rabbitmq-upgrade revive now log warning and info \ 
level instead of alert.
Shovel Plugin

Bug Fixes

Multiple Shovels could be started in some cases involving node restarts of failures.
Federation Plugin

Bug Fixes

Multiple Federation links could be started in some cases involving node restarts \ 
of failures.

3.9.1:
Core Server

Bug Fixes

Clients that used global QoS prefetch (deprecated as of 3.9.0) ran into an \ 
exception when acknowledging deliveries.
Improved resiliency of stream coordinator in certain conditions.
Nodes failed to start when hostname contained non-ASCII (broader Unicode) characters.

CLI Tools

Bug Fixes

rabbitmq-diagnostics stream_status fails with an exception when the --tracking \ 
option was used.
rabbitmq-diagnostics stream_status used an outdated documentation guide link.
RabbitMQ Erlang Client

Bug Fixes

New releases of the client are again published to Hex.pm.
connection_timeout was adjusted to avoid a confusing warning.
Corrected a typo in direct connection net tick time adjustment.

3.9.0:
Streams
Erlang 24 Support
Kubernetes
Logging in JSON

Files:
RevisionActionfile
1.57modifypkgsrc/net/rabbitmq/Makefile
1.43modifypkgsrc/net/rabbitmq/PLIST
1.55modifypkgsrc/net/rabbitmq/distinfo