Repository navigation
Release 4.0.1 - #245
Merged
Merged
Release 4.0.1#245
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #245 +/- ##
=======================================
Coverage 76.12% 76.12%
=======================================
Files 81 81
Lines 6396 6396
=======================================
Hits 4869 4869
Misses 1527 1527
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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
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.
Dates the 4.0.1 heading and bumps
pubspec.yamlfrom 4.0.0.#244 is the only thing merged since
v4.0.0, and its two entries were already in the section, so there is nothing else to write. Checked the README too: this change is internal toSSHChannelControllerwith no public API and nothing the README describes, so it needs no update.Worth not sitting on. The stall it fixes is in the published 4.0.0: a peer that fills the advertised window before the application subscribes leaves the channel at zero credit permanently, and the symptom is a dead socket with no error. The README's own remote forwarding example reaches it, since it awaits
Socket.connect()before subscribing.Verified on the 3.13.2 SDK:
dart formatanddart analyze --fatal-infosclean, 692 tests passing,dart pub publish --dry-runwith 0 warnings.