tree 5071003e5e7063be70dab6567185c2776ca576c9
parent 117dd167852c728dadb8e08179a1d8b14784644d
author Boris Zbarsky <bzbarsky@apple.com> 1659990853 -0400
committer GitHub <noreply@github.com> 1659990853 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi8XNFCRBK7hj4Ov3rIwAAdZ4IAHEgMHOGLLRd9qj78rE1H4Ll
 IBff7z9VIcTC2pcuey02a/IV08he13Zi6D/cOdyQYa91LljXw9IsY4C70UOSxqq0
 ep1OR1QgpwNfevTd3ZT/m6kBnH2JfF8wZ7imS4a6jQy3bquxOW9qmg6JDi09VCpj
 36VF4hFhHDFhOUgYzcw9yrrNv1FxAKCX2/6qmLGu2E7JOF5ZzE0+rLHRMRzaXF0W
 cf6jV172dvzuEVw1LxtxZKD0D//WyL5Y3wGeIg20bA1TCqU1z2kdyMO5I5CaVJav
 9wMGX0ely9FMbh3zpcJkeucegFhBVE3e3tk3J5wcE44c6IUcflj+PaJwFUsohRw=
 =E4+D
 -----END PGP SIGNATURE-----
 

Make sure chip-tool interactive cleanup happens on the Matter thread. (#21661)

The interactive cleanup happens while the event loop is still running
(during the execution of the "interactive" command), so queuing the
cleanup on the event loop is reasonable.  And this ensures cleanups
don't run into MAtter locking assertions.