exo-explore/exo · error · StopImageGenerationException
Stopping image generation at step {t + 1}/{len(time_steps)}
Error message
Stopping image generation at step {t + 1}/{len(time_steps)} What it means
Error "Stopping image generation at step {t + 1}/{len(time_steps)}" thrown in exo-explore/exo.
Source
Thrown at src/exo/worker/engines/image/pipeline/runner.py:591
latents=latents,
prompt_data=prompt_data,
num_sync_steps=num_sync_steps,
)
ctx.in_loop( # pyright: ignore[reportAny]
t=t,
latents=latents,
time_steps=time_steps,
)
mx.eval(latents)
if t in capture_steps and self.is_last_stage and not self._cancelling:
yield (latents, t)
except KeyboardInterrupt: # noqa: PERF203
ctx.interruption(t=t, latents=latents) # pyright: ignore[reportAny]
raise StopImageGenerationException(
f"Stopping image generation at step {t + 1}/{len(time_steps)}"
) from None
if self._cancelling:
break
# Drain pending ring recvs after cancellation during async steps.
# The last stage sent patches during the final completed step, but
# the first stage will never enter the next step to recv them.
if (
self._cancelling
and self.is_first_stage
and not self.is_last_stage
and self.group is not None
and t >= runtime_config.init_time_step + num_sync_steps
and t != runtime_config.num_inference_steps - 1
):
patch_latents_drain, _ = self._create_patches(latents, runtime_config)View on GitHub (pinned to 21a54c5ea0)
When it happens
Trigger: Thrown at src/exo/worker/engines/image/pipeline/runner.py:591 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of exo-explore/exo@21a54c5ea0 (2026-08-26).
Data as JSON: /api/errors/1a925ca93ed013cd.
Report an issue: GitHub.