Boris Zbarsky
Boris Zbarsky
> UpdateDevice: This already looks to be deprecated, we should just delete this. It's deprecated for external use. For internal use, we use it to implement `OnFirstMessageDeliveryFailed`. We need a...
> FYI it's an optimization, and isn't strictly necessary for correct behavior. We should assess if we really need that for 1.0 given that. FYI, a spec SHOULD means "do...
Because: > But it can lead to messages not being sent to some bindings which would be a spec violation, no?
Right, the key is that a `Callback` can only be in a single list, so adding `mOnConnectedCallback` and `mOnConnectionFailureCallback` to the list for the new session establishment removes them from...
Note that all-clusters-app specifically is not meant as a "sample app" in any sane form. It does not implement sane device type, and it implements a Test Cluster instance that...
Relevant part of the log: ``` 08-08 16:51:28.376 E/DL (19400): Chip stack locking error at '../../examples/tv-app/android/third_party/connectedhomeip/src/app/util/attribute-storage.cpp:549'. Code is unsafe/racy ... 08-08 16:51:28.699 F/DEBUG (19480): #03 pc 00000000001be0cc /data/app/~~RL33Ljpo3ELRX4IAaR5Ynw==/com.matter.tv.server-wX8VRolotStmt3f9FXbxyA==/lib/arm64/libTvApp.so (chip::Platform::Internal::AssertChipStackLockedByCurrentThread(char const*,...
That is certainly one valid way to solve the problem, yes.
Just to be clear, a spec SHOULD means "it's expected that any good implementation will do this; not doing it must be grounded in very good reasons". So yes, it's...
The only things I can think of there are: 1. There might still be circular dep issues. 2. It would likely involve making ExchangeContext bigger, right?
@raju-apple @manjunath-grl @cjandhyala Please take a look?