Repository navigation
Let repeater login wait for a long contact list - #38
Merged
Merged
Conversation
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
1 participant
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.
Summary
Logging in to a repeater failed every time on radios with a large contact list, reporting "No reply from the repeater" even though the login was never sent. This lets the login wait for the contact list to finish.
This fix already shipped to testers in beta v1.4.1(1792121415), which was built from a local
devwhere the commit was never pushed. Without it ondev, the next build would bring the bug back. It is a clean cherry-pick of 53ecbe6 onto the currentdev.Testing
flutter analyze: no issues.flutter test: all 2500 pass, 1 skipped, including the new repeater admin frame and session tests.