refine(otaproxy): allow otaproxy to run even if sqlite3 DB init failed#919
Merged
Bodong-Yang merged 4 commits intomainfrom Apr 24, 2026
Merged
refine(otaproxy): allow otaproxy to run even if sqlite3 DB init failed#919Bodong-Yang merged 4 commits intomainfrom
Bodong-Yang merged 4 commits intomainfrom
Conversation
…n downgraded mode if DB not available
Bodong-Yang
added
the
refinement
for more information, see https://pre-commit.ci
Contributor
📊 OTA Update Performance Comparison Report
⏱️ Execution Time
|
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR adds safety guard around sqlite3 DB preload and init paths at CacheIndex starts up. The back storage sqlite3 DB now can be optional if somehow we cannot make the DB work, allows otaproxy to still run normally without a back sqlite3 DB.
Check list