Release v3.0.2 - #602
Merged
Merged
Release v3.0.2#602
Conversation
oleg-jukovec
force-pushed
the
oleg-jukovec/release-v3.0.2
branch
from
September 10, 2026 14:49
c8e92ba to
082fe86
Compare
bigbes
approved these changes
Sep 10, 2026
sssciel
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch release fixes lost or stuck requests, occasional panics, and a data race on
Connection.Addr()that could surface after a connection drop (server restart, network blip) while requests were in-flight.Fixed
Do→Get→Releaselifecycle was used (Data race between Future.Release() and futureList.clear() on reconnect #600).Connection.Addr()that could be triggered when the connection was reconnecting in the background (e.g. after a server restart or a transient network failure) while the user code was concurrently callingAddr()to log or inspect the endpoint (connection: fix future release race on reconnect #601).