Follow a replacement voice flight whatever its predecessor reports

A motion queued behind a voice fly-to now follows a later fly-to in the same reply whether the earlier one arrived, was cancelled or failed. A geocode that loses navigation reports failed, so the motion used to be dropped; and a flight left flying while the next place is looked up could land and run the motion there, taking navigation and cancelling the newer flight. The deadline, abort and stale-reply checks still end the wait.

pitchDeg -90 or -89 from a top-down view is now unchanged rather than a 1° tilt up, and the tilt tests' pitch loops are bounded.
This commit is contained in:
Manjunath committed 2026-11-04 13:40:43 +05:30
1 parent eeb20d24e9
commit 44860df90e
4 files changed
+104 -6

No files matched your search

+11 -3
View File
@@ -1302,9 +1302,17 @@ export function createGevActionRunner({
runOptions.signal,
deadline,
);
// A later fly-to in the same reply cancels this one: follow it to
// where the camera lands, within the same deadline.
while (status === 'cancelled' && voiceFlight !== flight && current()) {
// A later fly-to in the same reply replaces this one: follow it to
// where the camera lands, within the same deadline. Its status does
// not matter. A geocode that loses navigation reports failed, and a
// flight left flying while the next place is looked up can still
// land; running there would take navigation and cancel the newer one.
while (
voiceFlight !== flight &&
status !== 'aborted' &&
status !== 'timeout' &&
current()
) {
flight = voiceFlight;
status = await waitForVoiceFlight(
flight,