← Back to issue list

Add ability to handle Internet connection failures

View original Github issue

Metadata

Project
craft-parts
Number
#1189
Type
issue
State
open
Author
ofry
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request (external contributor, no maintainer response) to add a config/CLI option that retries failed builds or downloads N times after network failures such as unexpected EOF. Still untriaged in craft-parts.

Suggested action: needs triage

Reason: The issue has zero labels, zero comments, no assignee, and no maintainer engagement after 434 days, so it has never been triaged. Scope is also undetermined: craft_parts/sources/base.py download() performs a single requests.get() and raises NetworkRequestError with resolution 'Check network connection and source, and try again', and no generic retry layer exists (only ad-hoc retries: retry_count = 5 in packages/snaps.py, curl --retry 5 in npm_plugin.py, umount retry in os_utils.py). The upstream snapcraft#5642 counterpart was closed as not planned with maintainers preferring per-network-operation retries over a command-level retry option, so the requested design may need reframing before implementation.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 4 Complexity: 68 Confidence: 78 Actionability: 32

Issue body

### What needs to get done It's related to https://github.com/canonical/snapcraft/issues/5642 Could you add new configuration option, CLI option, etc. which add ability to retry failed command pre-defined number of tries? I want to exclude scenario: ``` snapcraft ``` See failing when connection suddenly closed when downloading any file related to project (unexpected EOF or such). Then immediately I should: ``` snapcraft ``` etc. ### Why it needs to get done It will greatly improve the usability when the user has unstable Internet connection.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 40
Quick Win: 4
Complexity: 68
Confidence: 78
Actionability: 32
needs triage Feature request (external contributor, no maintainer response) to add a config/CLI option that retries failed builds or downloads N times after network failures such as unexpected EOF. Still untriaged in craft-parts.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 14
Complexity: 50
Confidence: 75
Actionability: 70
keep open Feature request to add configurable retry logic for download failures due to unstable internet connections. Redirected from snapcraft#5642. Some retry logic exists in snaps.py and npm_plugin.py but not as a general mechanism.
qwen/qwen3.8-27b
Impact: 45
Quick Win: 18
Staleness: 72
Complexity: 60
Confidence: 78
Support Request: 15
needs triage Feature request to add a retry option for failed network downloads (e.g. unexpected EOF on unstable connections). Unlabelled, 0 comments, no maintainer response; related snapcraft#5642 was closed and redirected here as the proper home.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 45
Confidence: 75
Support Request: 10
needs triage Feature request to add a configurable retry mechanism for network downloads to handle unstable connections. Unlabelled, zero maintainer comments, and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 45
Confidence: 80
Support Request: 10
needs triage Request for a retry mechanism on network failures during downloads to improve usability on unstable connections. Untriaged, no maintainer response, inactive for nearly a year.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft#5642 (confidence 90%)

    Explicitly linked from the issue body; closed as not planned after maintainers favoured retry logic per network operation in craft-parts rather than a Snapcraft command-level retry option.

Related issues

Issue Project State Summary Similarity
#5642 Add ability (opt-in) to handle Internet connection failures snapcraft closed Closed as not planned: maintainer mr-cal redirected retry handling to per-operation retry logic in craft-parts (e.g. retrying downloads on partial/receive errors) and suggested the remote builder, rather than a Snapcraft CLI-level retry option.
80%