You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the execution of GenericPlatformManagerImpl::_InitChipStack,SystemLayer().Init() is called, which lands in LayerImplSelect::Init, which tries to set up the WakeEvent bits, which lands in LayerImplSelect::RequestCallbackOnPendingRead, and we log the above because we have no dispatch queue at this point: step 3 above has not happened yet.
The practical effect is that I expect when dispatch queues are being used WakeEvent does not work on Darwin, but I assume that it's also not used on Darwin in that case; instead dispatch to queues is used.
Proposed Solution
A few options:
We could move SetDispatchQueue to before the GenericPlatformManagerImpl::_InitChipStack call. I think that should be safe, but @vivien-apple and @kpschoedel should check.
We could make the log there be a progress log, not an error log.
We could suppress the log during init.
We could do nothing....
The text was updated successfully, but these errors were encountered:
Problem
Run chip-tool. One of the first log lines is:
What's happening here is that the Darwin
PlatformManagerImpl::_InitChipStack
does these, in order:GenericPlatformManagerImpl::_InitChipStack
DeviceLayer::SystemLayer().SetDispatchQueue()
During the execution of
GenericPlatformManagerImpl::_InitChipStack
,SystemLayer().Init()
is called, which lands inLayerImplSelect::Init
, which tries to set up theWakeEvent
bits, which lands inLayerImplSelect::RequestCallbackOnPendingRead
, and we log the above because we have no dispatch queue at this point: step 3 above has not happened yet.The practical effect is that I expect when dispatch queues are being used WakeEvent does not work on Darwin, but I assume that it's also not used on Darwin in that case; instead dispatch to queues is used.
Proposed Solution
A few options:
SetDispatchQueue
to before theGenericPlatformManagerImpl::_InitChipStack
call. I think that should be safe, but @vivien-apple and @kpschoedel should check.The text was updated successfully, but these errors were encountered: