Backup/restore status should more clearly explain error related output
Open
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
When status is run on a completed backup or restore that experienced errors, the inclusion of the latest errors in the status report can make it seem as though the operation was not actually successful.
The human-readable status for both operations should somehow be improved to make it clear that the status of the job (completed/aborted/etc) is independent of the error summary.
Contributor guide
Assessment
This issue has not been assessed yet.