Repository navigation
Conversation
- drain asynchronous tasks before reporting failures - preserve suppressed errors and interrupt state - retain backup input when restore fails - cover corrupt input and valid empty backups
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Purpose of the PR
A restore worker could fail while reading a damaged JSON/ZIP file or inserting records, yet the command would report success and clean its input directory. Worker failures now reach the existing CLI error path after all submitted work finishes, and failed restores retain their inputs.
Found in the Toolchain integration report.
Main Changes
Verifying these changes
Does this PR potentially affect the following parts?
Documentation Status
Doc - TODODoc - DoneDoc - No Need: restores the existing CLI failure and cleanup contract.Organization and upstream core CI pass. Original and fixed native packages use the same verified Server SDK and fixture; task-owned graphs and services are cleaned up after acceptance.
The native CLI checks answer
nto its existing optional stack-trace prompt before verifying the Unix error exit; this PR preserves that prompt contract.