refactor: increase the retry timeout and wrap the error for retry

[chlins]

This pull request introduces logging enhancements and updates to retry configurations across the codebase. The changes improve error visibility by adding detailed logs and adjust retry mechanisms to handle failures more robustly.

Logging Enhancements:

• Added the logrus dependency to internal/pb/pb.go for structured logging.
• Enhanced the Abort method in internal/pb/pb.go to log errors when aborting a progress bar.
• Updated error handling in pkg/backend/processor/base.go and pkg/backend/pull.go to log errors using logrus.Error for better traceability. [1] [2]
• Added debug and error logs in pkg/backend/pull_by_d7y.go to provide detailed information during layer processing.

Retry Configuration Updates:

• Increased the default retry attempts from 3 to 4 and adjusted delay values for retries in pkg/backend/processor/options.go and pkg/backend/retry.go. Delays were updated to 10 seconds with a maximum of 20 seconds to improve resilience. [1] [2]

[gemini-code-assist]

Summary of Changes

Hello @chlins, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on enhancing the robustness and observability of the system. It introduces more detailed error logging across several components and significantly adjusts the retry mechanisms to improve resilience against transient failures.

Highlights

• Enhanced Error Logging: I've integrated logrus for structured logging and improved error visibility by adding detailed error messages, especially when aborting progress bars or processing layers. Errors are now consistently wrapped for better traceability.
• Adjusted Retry Configurations: I've increased the default number of retry attempts from 3 to 4 and extended the retry delays (from 5s to 10s, with max delay from 10s to 20s) in core backend processing and retry logic, aiming for more robust handling of temporary issues.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request enhances logging and updates retry configurations. Error wrapping inconsistencies and code duplication were identified.

[gaius-qi]

LGTM