Fix ASH reject condition amplification bug#699
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #699 +/- ##
==========================================
- Coverage 99.55% 99.53% -0.03%
==========================================
Files 58 58
Lines 4054 4070 +16
==========================================
+ Hits 4036 4051 +15
- Misses 18 19 +1 ☔ View full report in Codecov by Sentry. 🚀 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.
When communicating with OpenThread firmware, we get into tight loops when the firmware manages to respond with a semi-plausible frame. Our ASH implementation rejects it by sending a
CANCELbyte and aNakFrame, which prompts the firmware to send more data, etc. This isn't right. We should enter a "reject" state and wait until the firmware sends something sensible.See home-assistant/core#156966 (comment).