CatMQ v2.8.0

Full Changelog: https://github.com/NTDLS/CatMQ/compare/2.7.6...2.8.0

Be sure to check out the NuGet packages:

https://www.nuget.org/packages/NTDLS.CatMQ.Shared/2.7.6
https://www.nuget.org/packages/NTDLS.CatMQ.Server/2.7.6
https://www.nuget.org/packages/NTDLS.CatMQ.Client/2.7.6

New

• Languages: the web UI is now translated into more than 40 languages.
• Dark mode: a Light / Dark / Auto menu in the top bar.
• Message IDs: every message now gets a unique ID that stays the same when it is redelivered, dead-lettered, or restored after a restart. Subscribers can use it to spot a message they have already handled (MessageId on received messages).
• Linux ARM64 and self-contained builds: Linux packages are now available for both x64 and ARM64, and they include .NET, so there is nothing to install first.
• Deferred delivery through the web API: the enqueue endpoint takes an optional deferSeconds.

Changes

• Web API responses: enqueueing to a missing queue now returns 404 instead of an error. Creating a queue that already exists returns 409, an invalid queue name returns 400, and a successful create returns 201.
• Enqueueing on a stopped server: it now fails with an error instead of looking like it worked.
• Buffered subscriptions: batches are now never larger than the batch size you asked for.
• Charts: they no longer animate on every refresh and pause while the tab is hidden. Lines are smoothed without dipping below zero.
• Validation messages: configuration errors now spell out the real limits and are translated.

Fixes

• A subscribe that the server rejected no longer blocks retrying, so you no longer get “already subscribed” on the retry.
• Reconnect: after a connection drop, clients resubscribe automatically instead of silently going quiet.
• Buffered subscriptions: several fixes:
  • with more than one subscription on a client, each now uses its own batch size and timer;
  • leftover messages are delivered on disconnect instead of being lost;
  • the flush restarts after a reconnect;
  • errors in your batch handler are now reported.
• Purging a busy queue could leave a wrong queue depth, or bring back a deferred message that had just been purged.
• Stopping or deleting a queue no longer logs a false error, and no longer risks a crash when a delivery is still in progress.
• Creating a persistent queue that failed to open could be left half-created. It is now cleaned up and an error is returned.
• The queue depth charts line jumped to a different axis on the first refresh, and could be wrong after a failed refresh.
• A missing queue showed zeros instead of an error.
• Looking up a missing queue now returns nothing instead of a blank queue.
• The “No queues” row now spans the full table width.
• The failed-subscriber count was filled in from the wrong field.