← Back to issue list

Stage package cache is never cleaned

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1663051
Type
issue
State
open
Author
~kyrofa
Labels
Created
Updated
Closed

Current evaluation

Snapcraft's stage-package cache (keyed by source hash) is never cleaned and grows unbounded as new packages/sources are fetched. Self-filed by a maintainer ~9.5 years ago with no labels, comments, or follow-up; related Launchpad bug closed without resolution.

Suggested action: close stale

Reason: The issue is 3491 days old with 0 comments, no labels, and no maintainer engagement beyond the original self-filing by kyrofa, and the related Launchpad bug #1661383 ("stage package cache no longer working") was closed without resolution. The hash-based, source-keyed stage-package caching described (Catkin plugin archives, etc.) is from the snapcraft 1.x era, which has since been substantially reworked, so the specific mechanism is likely no longer applicable. Confidence is moderate because code-inspection tools returned no pinned SHA, so I could not directly confirm the current caching behavior.

Impact: 25 Quick Win: 13.75 Staleness: 98 Complexity: 45 Confidence: 55 Support Request: 15

Issue body

Snapcraft caches stage packages in caches unique to the hash of the sources. It does this so, for example, packages from the Catkin plugin (which uses a different set of archives) is kept separate from packages from the normal archives. However, this cache is never cleaned and will grow over time, as new packages are fetched and as sources change.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 25
Quick Win: 13.75
Staleness: 98
Complexity: 45
Confidence: 55
Support Request: 15
close stale Snapcraft's stage-package cache (keyed by source hash) is never cleaned and grows unbounded as new packages/sources are fetched. Self-filed by a maintainer ~9.5 years ago with no labels, comments, or follow-up; related Launchpad bug closed without resolution.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 85
Support Request: 10
close stale Snapcraft stage package cache grows indefinitely without cleanup. Open for nearly 9.5 years with zero comments, labels, or maintainer engagement, indicating it is outdated and likely irrelevant to current project architecture.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 40
Confidence: 90
Support Request: 10
close stale Snapcraft's stage package cache, keyed by source hashes, is never cleaned and grows indefinitely. The issue is over 9 years old with no maintainer response or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 45
Confidence: 85
Support Request: 10
needs triage Snapcraft's stage package cache grows indefinitely due to missing cleanup logic. The issue is over 9 years old with no maintainer response, labels, or comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 99
Complexity: 20
Confidence: 80
Support Request: 10
close stale Snapcraft caches stage packages by source hash but never cleans them, causing unbounded disk growth. The report remains open, inactive for nearly a decade, with zero comments and no labels, requiring triage and assignment.

Update history

No update history recorded yet.

Related work

  • Related To: launchpad#1661383 (confidence 50%)

    Same stage-package cache subsystem; that bug reported the cache failing after clean operations and was closed without resolution, indicating the area was not prioritized.

Related issues

No related issues found above the similarity threshold.