A generated video still needs a receipt and a stopped runtime
The five-second video existed, but the embedded UI had not caught up. Its completion message and receipt field did not update, and its exit button remained disabled. This happened in a private prototype running Wan2.2 TI2V-5B on an L4 in Google Colab. The useful result was more specific than “the tool worked”: generation, receipt, and runtime release each had separate evidence. Inspect the…
A five-second generated video still required a receipt and confirmation of a stopped runtime. The embedded UI failed to update its completion message and receipt field, keeping the exit button disabled. This issue occurred in a private prototype running Wan2.2 TI2V-5B on an L4 in Google Colab. The generated video consisted of a single silent clip of a paper boat moving across water, created using Python 3.12.13, fixed dependencies, and model files with verified hashes. The worker exited successfully, but the UI did not reflect this change.
The operator recovered the MP4 file and its settings JSON by using a helper path to export the existing job's state. The recovered video and JSON matched the recorded receipt records, establishing byte identity. Media validation confirmed that the requested output was correct, with dimensions of 832 × 480, a frame rate of 24 fps, and a duration of 5.000 seconds. The generation graph processed 121 frames, while the exported file contained 120 frames, as per the receipt specification.
The trial verified five claims: that the generation had finished, the worker had exited successfully, the output met the media specification, the media metadata and the saved full-decode check matched, and the same output was received with matching MP4 and settings sizes and hashes. The trial also confirmed that the generation engine stopped, with owned-process and listening-endpoint checks verifying that the runtime was released.
However, the UI's completion display, automatic shutdown, and continuous playback in a browser remained unverified.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
