-
Notifications
You must be signed in to change notification settings - Fork 593
refactor(cli): ensure auto-maintenance errors are propagated #4851
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
Conversation
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.
Pull Request Overview
This PR ensures that auto-maintenance and repository closing errors are properly propagated rather than being silently logged or overriding previous errors.
- Replaces error logging with error joining to surface auto-maintenance failures
- Preserves original action errors when repository closing fails by joining errors instead of overriding them
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4851 +/- ##
==========================================
+ Coverage 75.86% 76.55% +0.68%
==========================================
Files 470 536 +66
Lines 37301 41167 +3866
==========================================
+ Hits 28299 31514 +3215
- Misses 7071 7607 +536
- Partials 1931 2046 +115 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Prevent running "auto-maintenance" on snapshot create. Ref: - kopia#4851
Prevent running "auto-maintenance" on snapshot create. Ref: - kopia#4851
Prevent running "auto-maintenance" on snapshot create. Ref: - #4851 Context: the test fails because there are concurrent "endurance" runners and each of these advances the clock, some of them significantly (action{Small,Medium,Large}ClockJump), which causes the clock skewness check to fail when (auto-)maintenance runs. The test maintenance action does not experience this issue because it runs exclusively on its own, that is, other actions have to wait until maintenance completes.
Ensure auto-maintenance errors are propagated. This also means that notifications are sent when auto-maintenance fails.
Preserve action error when closing the repository fails.