← Back to issue list

Add file-a-bug functionality on errors

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1741900
Type
issue
State
open
Author
~lucyllewy
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to add file-a-bug functionality when snapcraft hits an error, offering to auto-file an issue with a traceback (flag or prompt), with duplicate detection. Open since 2017, no labels, no comments, no maintainer response.

Suggested action: needs triage

Reason: The issue is a genuine feature request (not a bug or support question) but shows zero signs of maintainer engagement: no labels, no comments, no assignee, and no activity for ~8 years (last activity 2920 days ago). It has never been assessed, categorised, or prioritised, so it needs triage rather than being closed outright. Closing as stale would be premature because the underlying capability (auto-filing bugs with tracebacks, à la ubuntu-bug) is still a plausible, unimplemented feature and there is no evidence it was implemented elsewhere or superseded.

Impact: 35 Quick Win: 14.0 Staleness: 95 Complexity: 60 Confidence: 70 Support Request: 0

Issue body

When snapcraft hits an error it would be nice if we could allow the user to file a new issue to the bug-tracker with a back-trace collected automatically, similar to the `ubuntu-bug` command on Ubuntu derivatives. Two suggestions which could be considered: 1) add a new flag `--create-bug` (wording can be changed) which will run snapcraft and when it hits a failure it raises a new issue automatically. or 2) add a prompt when snapcraft hits a failure to allow the user to choose to file a bug with a message similar to: "Snapcraft encountered an error. Would you like to create a bug in the issue tracker? (Y/n)" This could be silenced with a `--non-interactive` flag or `--quiet` for CI builders. -- Bonus points in either case for automatically detecting duplicate situations and directing the user to an already filed bug when they have the same problem as one already raised so that they may click "me too".

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 14.0
Staleness: 95
Complexity: 60
Confidence: 70
Support Request: 0
needs triage Feature request to add file-a-bug functionality when snapcraft hits an error, offering to auto-file an issue with a traceback (flag or prompt), with duplicate detection. Open since 2017, no labels, no comments, no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 10
close stale Feature request to automatically file bug reports on snapcraft errors via a flag or prompt, including traceback collection and duplicate detection. Currently inactive with no maintainer response or labels after over 8 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 10
close stale Feature request from 8.5 years ago proposing automatic bug filing on CLI errors. Zero maintainer engagement, no labels, and no activity since submission.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 35
Confidence: 92
Support Request: 10
close stale Feature request to add automatic bug filing on errors in snapcraft, either via flag or interactive prompt. Unlabelled, no maintainer interaction, inactive for over 8 years.
qwen3.6-35b-moe-q4
Staleness: 98
Complexity: 35
Confidence: 85
Support Request: 10
close stale Feature request to automatically file bug reports on snapcraft errors via CLI flag or prompt. Issue is over 8 years old with no maintainer interaction or labels.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#1815171 (confidence 55%)

    Related Launchpad bug about showing the traceback directly rather than only offering to send it to LP; both concern how snapcraft surfaces error tracebacks to users.

Related issues

No related issues found above the similarity threshold.