-
Notifications
You must be signed in to change notification settings - Fork 6
fix: free TFT sprite before OTA to fix SSL memory failure (#59) #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a3ca85b
feat: add freeForOTA/updateOTAProgress to DisplayI interface
sjordan0228 b83b4c6
feat: implement freeForOTA/updateOTAProgress in TFTManager
sjordan0228 877f5cb
feat: wire TFT OTA progress into WebServerManager download task
sjordan0228 f93ae20
fix: document intentional TFT task non-recovery after OTA failure (co…
sjordan0228 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
TFT task is not restarted after OTA failure—is this intentional?
After
freeForOTA()deletes the TFT task, if OTA fails the task is never restarted. This means subsequent display calls (e.g.,showReady(),showSpool()) will queue messages to_messageQueuewith no consumer, leaving the TFT stuck on the error screen.This is likely acceptable since OTA failure typically requires user intervention (power cycle or retry), but consider documenting this behavior or adding a note that manual reboot is expected after OTA failure.
🧰 Tools
🪛 Clang (14.0.6)
[warning] 746-746: variable 'cx' is not initialized
(cppcoreguidelines-init-variables)
[warning] 746-746: variable name 'cx' is too short, expected at least 3 characters
(readability-identifier-length)
[warning] 764-764: implicit conversion 'const char *' -> bool
(readability-implicit-bool-conversion)
[warning] 764-764: implicit conversion 'char' -> bool
(readability-implicit-bool-conversion)
🤖 Prompt for AI Agents