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

chore(deps): bump github.com/nats-io/nats-server/v2 from 2.8.4 to 2.9.4 #12134

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 31, 2022

Bumps github.com/nats-io/nats-server/v2 from 2.8.4 to 2.9.4.

Release notes

Sourced from github.com/nats-io/nats-server/v2's releases.

Release v2.9.4

Changelog

Go Version

  • 1.19.2: Both release executables and Docker images are built with this Go release.

Fixed

  • Configuration Reload:
    • The option allow_non_tls would be ignored after a configuration reload. Thanks to @​JulienVdG for the report (#3583)
  • JetStream:
    • Possible deadlock. Thanks to @​ashumkin for the report and @​neilalexander for the contribution (#3555)
    • Possible panic in disk full situations. Thanks to @​fantashley for the contribution (#3560, #3568)
    • "First sequence mismatch" after a restart/deployment with streams that have message TTLs. Thanks to @​MauriceVanVeen for the report (#3567)
    • Update of an R1 consumer would not get a response. The update was accepted by the server, but the client library or NATS CLI would timeout waiting for the response (#3574)
    • Update of a consumer's InactiveThreshold would not always take effect. Thanks to @​neilalexander for the contribution (#3575)
    • A consumer may not be removed based on InactiveThreshold in presence of gateways (#3575)
    • Migration of ephemerals on server shutdown was not working and could create "ghost" consumers on servers restart, that is, consumers that would be listed by the meta leader, but getting information about this consumer would fail. Migration will no longer occur, instead, all R1 pull consumers will be notified that the server is shutting down, invalidating the pending requests (#3576)
    • Consumers on a Limits policy stream could have their replicas changed to R1 (#3576)
    • Ensure that RAFT communication is properly stopped when needed, which otherwise could cause server memory usage increase (#3577)
    • Adding a warning when the inbound of messages causes a lag with the storage layer. In future release, the producers may be notified through a PubAck failure that the message cannot be accepted (#3578)
    • Added pending messages/bytes to pull request errors and status: when the server responds to the client library that a request has timed-out, or server is shutdown, etc..., the response will now include the request pending messages and bytes (#3572, #3587)
    • More messages than the max_msgs_per_subject value could be recovered on server restart following an abnormal server exit (#3579, #3582)
  • Leafnode:
    • Existing subscriptions would be sent to leafnodes even though they violated permissions. The publish side would be doing the right thing by not sending the messages over, but the subscription interest was still sent (#3585)
  • MQTT:
    • Subjects mapping were not working. Thanks to @​ozon2 for the report (#3552)
  • Routing:
    • An implicit route may not reconnect, regardless of the ConnectRetries setting. This can happen in configurations where the routes[] block contains only the seed (and not as a name that could resolve to each IP of the cluster). If a route to a discovered server is disconnected, it may not try to reconnect due to the implicit nature of that connection. Thanks to @​wubumihuo for the report (#3573)

Complete Changes

nats-io/nats-server@v2.9.3...v2.9.4

Release v2.9.3

Changelog

Go Version

  • 1.19.2: Both release executables and Docker images are built with this Go release.

Fixed

  • JetStream:
    • Unresponsiveness (health check failures, routes being blocked) while creating a RAFT group when disk performance if very slow. Thanks to @​TomasVojacek for the report (#3519)
    • Purge with additional options may leave some messages in the stream (#3529)
    • Prevent stack overflow when an account imports its own export. CVE-2022-42709 (#3538)
    • Prevent panic on negative replicas count. CVE-2022-42708 (#3539)

... (truncated)

Commits
  • 0b95294 Merge pull request #3588 from nats-io/release_2_9_4
  • f101e81 Release v2.9.4
  • bd1df4b Bump to 2.9.4-RC.3
  • 95d91b2 Merge pull request #3585 from nats-io/leaf-perms
  • 2e25969 Merge pull request #3587 from nats-io/add_pending_msgs_bytes_on_shutdown
  • 9bbf0aa Merge pull request #3586 from nats-io/client-update-2
  • a746b57 Update Go client to release 1.19.0
  • abcfe2e Add the pending msgs/bytes on 409 Shutdown
  • 9c5ae6b Existing subs would be sent to leafnodes even though pub perms should disallow.
  • 24081ae Bump to 2.9.4-RC.2
  • Additional commits viewable in compare view

Dependabot compatibility score

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 commands and options

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 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)

Bumps [github.com/nats-io/nats-server/v2](https://github.com/nats-io/nats-server) from 2.8.4 to 2.9.4.
- [Release notes](https://github.com/nats-io/nats-server/releases)
- [Changelog](https://github.com/nats-io/nats-server/blob/main/.goreleaser.yml)
- [Commits](nats-io/nats-server@v2.8.4...v2.9.4)

---
updated-dependencies:
- dependency-name: github.com/nats-io/nats-server/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 31, 2022
@telegraf-tiger telegraf-tiger bot added the chore label Oct 31, 2022
@telegraf-tiger
Copy link
Contributor

@MyaLongmire MyaLongmire merged commit c907cc2 into master Nov 1, 2022
@MyaLongmire MyaLongmire deleted the dependabot/go_modules/github.com/nats-io/nats-server/v2-2.9.4 branch November 1, 2022 10:25
popey pushed a commit that referenced this pull request Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant