Reapply thread storage fixes for 1.2.1#626
Draft
cquxl wants to merge 1 commit into
Draft
Conversation
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
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.
Summary
Reapplies the thread storage fixes on top of the current Rust/Tauri 1.2.1 codebase.
CODEX_HOMEwhen resolving the Codex local SQLite database path.Thread not found in local storage.Why
Profile/history merge workflows can leave sidebar rows pointing at stale projected thread IDs. The delete flow then reports
Thread not found in local storageand leaves the row visible. Users running with a switchedCODEX_HOMEcan also hit the wrong local storage database if the launcher falls back to the default home path.Validation
cargo test -p codex-plus-core --test assetsnpm run checkcargo build --release -p codex-plus-launchernpm run vite:buildnpm run buildcodex-plus-plus.exestayed running after launch smoke test.