Repository navigation
fix: report video file initialisation failures - #153
slophisticated wants to merge 1 commit into
Conversation
Raise a clear ValueError for an unavailable video or unreadable first frame, and release the metadata probe on all paths. Add native and adapter regressions for the VideoFile initialisation-error item in petercorke#150.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 8 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
Welcome to MVTB, and thank you for this contribution! This is a nice, careful fix: raising a clear You don't need to hold this behind #149: that PR touches Thanks for picking up an item from #150 — much appreciated. |
petercorke
left a comment
There was a problem hiding this comment.
CI is green; looks good to me.
Summary
Raise a
ValueErrornaming the video when OpenCV cannot open it or cannot decode its first frame, instead of accessingNone.shape. Release the initial metadata-probe capture infinally, including on failure.Related issue
Addresses only the VideoFile initialisation-error item in #150. The other source cleanup tasks remain separate.
Maintainer confirmed that this VideoFile change does not overlap #149 (EarthView), so it can proceed independently: #153 (comment).
Checklist
fix: report video file initialisation failuresValidation
Windows, Python 3.12.14, OpenCV contrib 5.0.0.93:
tests/test_image_sources.py -k videofile: 2 passed.git diff --checkpasses.The full suite and OpenCV 4 were not run. Disk-full errors interrupted the development-environment install; the packages required for these focused tests were repaired and the tests rerun successfully. This does not claim a fully provisioned development environment.
AI-assisted implementation and regression tests using OpenAI Codex.