← Back to issue list

feature request: allow pdb tracing of snapcraft plugin code

View original Launchpad issue

Metadata

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

Current evaluation

Feature request (6+ years old, no labels, no comments) to add built-in pdb tracing of snapcraft plugin code for step-by-step build debugging; motivated by legacy bug 1882124 from the Python 3.6 plugin era.

Suggested action: close stale

Reason: The issue has had zero comments, no labels, and no maintainer engagement for 2278 days (~6.2 years), and its motivating context is obsolete: the referenced bug 1882124 is from the legacy Python 3.6 plugin era and is itself inactive ~6 years, while the current snapcraft is a full parts-based rewrite (snapcraft/parts, snapcraft/extensions) in which the described unsquashfs/snap-try workflow no longer applies. The affected version is no longer supported, so the original problem is no longer applicable.

Impact: 20 Quick Win: 12.0 Staleness: 95 Complexity: 40 Confidence: 70 Support Request: 10

Issue body

It is quite useful to be able to drop into the python code of snapcraft and do things it does step-by-step when it isn't apparent what is going on during the build process. One example of that is this bug: https://bugs.launchpad.net/snapcraft/+bug/1882124 While it is possible to do something like this inside a build VM created by multipass: snap remove snapcraft mkdir /var/tmp/snapraft && cd  /var/tmp/snapcraft unsquashfs ../snapcraft.snap # edit the .py files of snapcraft to insert `import pdb; pdb.set_trace()` snap try squashfs-root/ --classic snapcraft build I think those trace points could be setup inside snapcraft (e.g. at the start of the build function of a given plugin) and invoked via some command. This could be more user-friendly than what I suggested above.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 20
Quick Win: 12.0
Staleness: 95
Complexity: 40
Confidence: 70
Support Request: 10
close stale Feature request (6+ years old, no labels, no comments) to add built-in pdb tracing of snapcraft plugin code for step-by-step build debugging; motivated by legacy bug 1882124 from the Python 3.6 plugin era.
qwen/qwen3.8-27b
Impact: 25
Quick Win: 13.75
Staleness: 95
Complexity: 45
Confidence: 65
Support Request: 10
close stale Feature request to add pdb trace points in snapcraft plugin code for step-by-step build debugging. 6+ years old, zero comments, no labels, no maintainer engagement; plugin code has since moved to the craft-parts library.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 35
Confidence: 90
Support Request: 10
close stale Feature request to add built-in pdb tracing for snapcraft plugins via a CLI flag. Submitted over six years ago with no maintainer response or activity. The request is outdated given modern Python debugging tools and significant changes to snapcraft architecture.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 30
Confidence: 90
Support Request: 10
close stale Feature request to add built-in pdb tracing for snapcraft plugin code. Unlabelled, zero maintainer interaction, inactive for over six years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 45
Confidence: 85
Support Request: 10
close stale Feature request to add built-in pdb tracing for snapcraft plugin code. Unaddressed for over 6 years with no maintainer interaction or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 90
Support Request: 10
close stale Feature request to add built-in pdb tracing for snapcraft plugin code via a CLI flag. Unaddressed and inactive for over six years with zero maintainer engagement.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1882124 (confidence 80%)

    Explicitly cited in the issue body as the motivating bug; confirmed to be a legacy Python 3.6-era pip presence-check error, untriaged and inactive ~6 years.

Related issues

No related issues found above the similarity threshold.