← 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

Opt-in error reporting existed in legacy Snapcraft, but its Sentry implementation was removed; the missing CI-safe behavior was split into follow-up #1790455.

Suggested action: needs triage

Reason: The 2018 comment shows an anonymous trace/version prompt and explicitly files the CI behavior as snapcraft#1790455. The current tree has no equivalent, while commit 0a120c694 removed legacy Sentry reporting and ffb164b7a removed snapcraft_legacy; with no labels or maintainer decision, maintainers must determine whether this should be redesigned for the current CLI.

Evaluated by: mr-cal-bot

Impact: 35 Quick Win: 5 Complexity: 72 Confidence: 84 Actionability: 48

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
stealth/space-bunny-alpha
Impact: 35
Quick Win: 5
Complexity: 72
Confidence: 84
Actionability: 48
needs triage Opt-in error reporting existed in legacy Snapcraft, but its Sentry implementation was removed; the missing CI-safe behavior was split into follow-up #1790455.
stealth/space-bunny-alpha
Impact: 35
Quick Win: 6
Complexity: 65
Confidence: 82
Actionability: 46
needs triage A 2018 comment reports a traceback-report prompt, but CI lacked a non-interactive option; Snapcraft 8.11 removed legacy core20 error reporting in favor of manual GitHub issues.
qwen/qwen3.6-35b-a3b
Impact: 20
Quick Win: 6
Complexity: 40
Confidence: 70
Actionability: 50
needs triage Feature request to add automatic bug-filing functionality when snapcraft encounters errors, with optional duplicate detection.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 14
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.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1790455 (confidence 100%)

    The comment explicitly identifies this as the follow-up for the prompt being unhelpful in CI.

  • Superseded By: canonical/snapcraft#5592 (confidence 97%)

    Commit 0a120c694 removed Sentry error reporting from snapcraft_legacy, so that implementation no longer exists.

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

    Commit 1c93ab107 added support for disabling error reporting, likely addressing part of the CI concern.

  • Likely Fixed By: canonical/snapcraft#591 (confidence 88%)

    Commit b9258ea73 improved error reporting and corresponds to the anonymous trace/version prompt documented in the comments.

Related issues

No related issues found above the similarity threshold.