tree 96ac90729986fc3cf5212e4bdb3bce54ecda5bcc
parent 00ce511d53994a92939f855e90b9315bc3dae664
author Nate Bosch <nbosch@google.com> 1617667479 -0700
committer GitHub <noreply@github.com> 1617667479 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJga6WXCRBK7hj4Ov3rIwAAdHIIAK5wdBIkuMtFMmcqxSw+gq0r
 BpIaoW+Um/IHXewDrIUsqgxkXzvCddhTonUXvbUbyYWno+JyWNSqD6SgQ/A1u64g
 Yc8HqMW2ZbgREQvsm4aeZ7QL8LDutvkeY7SJRZB/Ccir9Wi86y+BvHUoxHKiXJ0M
 VHCNe68fD/r5AhZm4fQT1zeg1zFpKOUp8jjajOAypqu6eVCmDy1uCaRAadKRA/+c
 l0Xo6e64qgjdzohPpme2x1pIabysHkglPh8u915sv5Ztr3cNNJbtYvdytHIgEc/B
 pUjo0oVWQQMMSHKaZftw/Jivmog/DDAt/cHOakqLjMcVfJVTtw0sMeLmUAW0OSg=
 =OOZ9
 -----END PGP SIGNATURE-----
 

Switch from mustWaitFor to markPending (#1487)

Previously the call to `Invoker.current.removeOutstandingCallbacks`
happened synchronously when the callback was called. After the change to
use `testHandle.mustWaitFor(Future)` the callback would no longer be
called in a `FakeAsync` zone that does not have any further async
progression.

Avoid the complication with a more forgiving non-Future API which
abstracts the trickiness around zones (other than that the
`markPending` call must be in the test zone, which is the case for
all APIs) and errors.