[Darwin] MTRDevice ReadClient callbacks need to change state immediately #34796
Assignees
Comments
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Sep 9, 2024
…atter queue. This avoids races where we queue blocks to different queues that both try to change the state, which were resulting in non-deterministic final state. Fixes project-chip#34796
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Sep 9, 2024
…atter queue. This avoids races where we queue blocks to different queues that both try to change the state, which were resulting in non-deterministic final state. Fixes project-chip#34796
ArekBalysNordic
pushed a commit
to ArekBalysNordic/sdk-connectedhomeip
that referenced
this issue
Nov 28, 2024
…atter queue. (#35490) This avoids races where we queue blocks to different queues that both try to change the state, which were resulting in non-deterministic final state. Fixes project-chip/connectedhomeip#34796
yyzhong-g
pushed a commit
to yyzhong-g/connectedhomeip
that referenced
this issue
Dec 12, 2024
…atter queue. (project-chip#35490) This avoids races where we queue blocks to different queues that both try to change the state, which were resulting in non-deterministic final state. Fixes project-chip#34796
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue it to track ReadClient callbacks in MTRDevice that result in state / internal state changes, and how those should be set immediately, instead of the current logic, where the state change happens after async-ing to the MTRDevice's queue.
The text was updated successfully, but these errors were encountered: