fix(esp_jpeg): Correctly handle invalid 0xFFFF marker #471
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tore-espressif
force-pushed
the
fix/esp_jpeg_broken_marker
branch
from
6349630 to
35bc4a3
Compare
Test Results15 files 15 suites 1m 10s ⏱️ Results for commit c851221. ♻️ This comment has been updated with latest results. |
|
@peter-marcisovsky This should fix decoding of frames from your camera. @espzav PTAL :) |
igrr
reviewed
Jan 30, 2025
tore-espressif
force-pushed
the
fix/esp_jpeg_broken_marker
branch
from
35bc4a3 to
c851221
Compare
|
@peter-marcisovsky @igrr Thank you very much for the reviews! All fixed |
espzav
approved these changes
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
urlfield definedChange description
Please describe your change here