`snapcraft clean <part> --use-lxd` shouldn't wait for network
Metadata
Current evaluation
Part-specific `snapcraft clean --use-lxd` unnecessarily starts a network-configured LXD environment; a maintainer suggested using offline mode, but no fix is recorded.
Suggested action: keep open
Reason: The maintainer identified the provider launch as the cause and stated that `--offline` could be passed with clean, but that eliminating the wait required further analysis. Current code still routes part-specific clean through `_run_in_provider` and `launched_environment`, with no resolving commit or PR found.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
15
Complexity:
48
Confidence:
88
Actionability:
70
Issue body
When cleaning a specific part, please make it so, so that snapd doesn't wait for the availability of internet, it's redundant to wait for network connectivity for the lxd container, while the sole purpose is to just delete a few directories.
This will help developers who are debugging their code and need to clean specific part frequently. All saved seconds are helpful.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
15
Complexity:
48
Confidence:
88
Actionability:
70
|
keep open | Part-specific `snapcraft clean --use-lxd` unnecessarily starts a network-configured LXD environment; a maintainer suggested using offline mode, but no fix is recorded. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
13
Complexity:
38
Confidence:
78
Actionability:
72
|
keep open | Maintainer-acknowledged optimization: part-scoped `snapcraft clean <part> --use-lxd` should not wait for LXD networking. The old provider code moved, but the core22 LXD clean path remains unresolved. | |
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
2
Complexity:
65
Confidence:
72
Actionability:
25
|
keep open | Request to skip the LXD network wait for `snapcraft clean <part> --use-lxd`. Acknowledged by maintainer, but the target code moved to external craft-providers; unimplemented for 1709 days. | |
| stealth/space-bunny-alpha |
Impact:
26
Quick Win:
10
Complexity:
32
Confidence:
63
Actionability:
54
|
needs triage | LXD-backed part cleaning unnecessarily waits for network availability; no maintainer triage, discussion, or follow-up activity. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
16
Staleness:
85
Complexity:
35
Confidence:
55
Support Request:
10
|
needs triage | Feature request: snapcraft clean <part> --use-lxd should not wait for network connectivity since cleaning only deletes directories. No maintainer response or labels in ~4.6 years; the network wait originates in craft-providers' wait_until_ready, which still exists in current code. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Request to skip network wait during snapcraft clean <part> --use-lxd to speed up part cleanup. Unlabelled, no maintainer response, inactive for over four years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to skip network wait during snapcraft clean with LXD to speed up debugging. Issue is 4.5 years old with no maintainer response or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to skip network wait during snapcraft clean part use-lxd to speed up local development. Untriaged, inactive for over 4 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Request to skip network wait during snapcraft clean --use-lxd to speed up part cleanup. Issue is over 4 years old, unlabelled, and has had zero maintainer interaction or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft#1087
(confidence 90%)
Related issue concerning unnecessary LXD network waits during cleanbuild tests.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1746009 clean is checking lxd remote | snapcraft (launchpad) | closed | Snapcraft now initializes the LXD remote lazily, so clean no longer starts a container unnecessarily; fixed by snapcore/snapcraft#1916 (dd4404843). |