User Story
As a developer using FrameStory,
I want robust error handling in the describe_frames method
so that caption generation failures don't crash the entire video processing pipeline.
Background
The current implementation of describe_frames in frame_story/video_describer.py lacks error handling around the image captioning model calls. If the model fails (e.g., due to invalid inputs, API issues, or hardware constraints), uncaught exceptions propagate upward, halting all processing. This is particularly risky given the dependency on external ML models and video input variability. The describe_frames method's loop (lines 45-60) needs structured exception handling to maintain pipeline resilience.
Acceptance Criteria
User Story
As a developer using FrameStory,
I want robust error handling in the
describe_framesmethodso that caption generation failures don't crash the entire video processing pipeline.
Background
The current implementation of
describe_framesinframe_story/video_describer.pylacks error handling around the image captioning model calls. If the model fails (e.g., due to invalid inputs, API issues, or hardware constraints), uncaught exceptions propagate upward, halting all processing. This is particularly risky given the dependency on external ML models and video input variability. Thedescribe_framesmethod's loop (lines 45-60) needs structured exception handling to maintain pipeline resilience.Acceptance Criteria
frame_story/video_describer.pywith error handling indescribe_frames:processor()andmodel.generate()) in try/except blockstests/test_video_describer.pyto verify error containment