Skip to content

Show passive progress for automatic backup retries - #4

Merged
AlexanderSmyslowski merged 21 commits into
mainfrom
codex/automatic-retry-progress-v2-4-4
Aug 1, 2026
Merged

Show passive progress for automatic backup retries#4
AlexanderSmyslowski merged 21 commits into
mainfrom
codex/automatic-retry-progress-v2-4-4

Conversation

@AlexanderSmyslowski

Copy link
Copy Markdown
Owner

Summary

  • persist private per-phase backup progress
  • show passive retry progress in the overview and menu bar
  • preserve guest SMB remounts and newer failure alerts
  • keep progress publication fail closed

Validation

  • bash -n bin/backup-google-drive.sh
  • make test
  • scripts/validate-release.sh v2.4.4

@AlexanderSmyslowski
AlexanderSmyslowski merged commit e9907f7 into main Aug 1, 2026
2 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 050e060738

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +3471 to +3473
@"retryRunning": retryRunning ? @"1" : @"0",
@"progressVisible": retryRunning ? @"1" : @"0",
@"progressLabel": retryRunning ? T(language, @"automaticRetryRunning") : @"",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Show progress for all headless running triggers

When an ordinary scheduled or mount-triggered backup is running, its validated durable progress is passed into this method, but every progress field is suppressed because retryRunning only accepts schedule-retry. Consequently, the overview and menu bar remain at the generic running state for the other headless modes even though the backup script publishes their live progress; base visibility on any supported running headless trigger and reserve the retry-specific wording for retries.

Useful? React with 👍 / 👎.

Comment on lines +1993 to +1994
if parse_rclone_progress_fields "$line"; then
write_progress "$label" "$RCLONE_PROGRESS_PERCENT" "$RCLONE_PROGRESS_DETAIL" "$phase"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Clear stale percentages before collision archive copies

When a normal copy has most recently published (for example) 100% and a duplicate-name collision then starts one of the run_rclone_with_progress "$label (ID-Archiv)" calls, durable progress is not reset at that transition and is updated only after another parseable stats line reaches this branch. The backend copyid paths use the default one-minute stats interval rather than RCLONE_OPTS, so a large duplicate can appear complete for up to a minute—and a shorter one for its entire archive copy—contrary to the new no-stale-percentage behavior. Publish an indeterminate phase record whenever each wrapped rclone operation starts.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant