You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Changelog
Go Version
1.17.6: Both release executables and Docker images are built with this Go release.
Added
JetStream:
Ability to get per-subject details via StreamInfo responses. The request needs to include a subjects_filter:<subject> for the server to include the list. The StreamInfo structure now has NumSubjects that will always be set, but optionally Subjects which contains the list of distincts subjects present in the stream with the count of messages per subject (#2833)
Removed
Dynamic account behaviors. The server option AllowNewAccounts and function NewAccountsAllowed() have been removed. Note that the option could only be set for applications embedding the NATS Server since configuration parsing was not parsing this option (#2840)
Fixed
JetStream:
Adding streams may fail with "insufficient resources" in some cases (#2824)
Possible panic when attempting to update a push consumer by removing the deliver subject (#2829)
Consumer updates were not updated on disk and would be reverted after a server restart. Thanks to @oliverpool for the report (#2830)
Behavior of a stream when MaxMsgsPerSubject is set along with DiscardNew discard policy. Unless the stream is reaching a limit, old messages will be removed on a per-subject basis (#2831)
A pull request no_wait:true without expiration was not considering redeliveries (#2832)
BackOff redeliveries would always use the first delay from the list if the consumer's sequence was not matching the stream sequence (#2834)
Under certain scenarios, the number of pending messages (unprocessed messages reported by the NATS CLI) for a consumer could appear to get stuck at 0 (#2835)
When a consumer had no filtered subject and was attached to an interest policy retention stream, the server could incorrectly drop messages (#2838)