Open
Description
Several users have wound up with bugs when predict()
hasn't cleaned up completely after returning.
For example, a video generation model might write frames to a folder. If that folder isn't cleared out after returning, the next predict() call will append frames to the previous prediction's frames.
The long-term solution is to enforce isolation between predict() calls in code, but for now we should at least put a big warning sign up explaining that for now it's the user's responsibility to clean up between predict() calls.