Wait for explicit stack messages for network state #554
Conversation
This file contains 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
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## dev #554 +/- ##
=======================================
Coverage 99.76% 99.76%
=======================================
Files 62 62
Lines 4586 4594 +8
=======================================
+ Hits 4575 4583 +8
Misses 11 11
☔ View full report in Codecov by Sentry. |
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.
Looks like #553 affected more than just zigbeed, as I've been able to replicate it on EmberZNet 6.9 and 7.1 with NCP USB coordinators...
The root cause appears to be us not properly waiting for stack events to happen (i.e.
NETWORK_UPandNETWORK_DOWN), leading to race conditions or outright failures at random.