Remove Sentry reporting
Metadata
Current evaluation
Merged PR #5592 (commit 0a120c694) removed Sentry/Raven reporting, error-data prompts, and the Launchpad fallback; Snapcraft now shows errors without requesting submissions.
Resolution: closed resolved
Reason: The issue was resolved by merged PR #5592, commit 0a120c694. The change removed Snapcraft Legacy's Sentry/Raven reporting and error-data prompt, along with the Launchpad fallback message.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
If snapcraft fails when building a core20 snap, it will prompt the user to report anonymous data to Sentry:
```
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]:
```
This code and it's accompanying tests should be removed. The user should see the error but not be prompted to send data.
This sentry code gets called [here](https://github.com/canonical/snapcraft/blob/11b5bc02cf4231db691ab6884383b9bda72c960e/snapcraft_legacy/cli/_errors.py#L180). There are lots of supporting functions and constants that can be removed.
The "fallback" reporting message should also be removed:
```
We would appreciate it if you created a bug report at
https://launchpad.net/snapcraft/+filebug with the above text included.
You can find the traceback in file '/tmp/tmpe7ry45l1/trace.txt'.
```
### Why it needs to get done
We no longer use the data submitted for core20 snap failures nor Launchpad for bug tracking. Instead, we rely on bug reports in GitHub.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #5592 (commit 0a120c694) removed Sentry/Raven reporting, error-data prompts, and the Launchpad fallback; Snapcraft now shows errors without requesting submissions. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #5592 (commit 0a120c694), removing Snapcraft Legacy’s Sentry/Raven reporting, error-data prompts, and Launchpad fallback message. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to remove Sentry reporting and fallback error messages was closed and likely abandoned. No fix or pull request is documented in the thread. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The requested Sentry error reporting prompts and fallback Launchpad bug reporting code were removed from snapcraft, completing the cleanup to rely solely on GitHub issues for bug tracking. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved by removing Sentry reporting and fallback Launchpad bug prompts from the codebase. The cleanup task was completed and associated tests deleted. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
snapcraft#5592
(confidence 100%)
PR #5592 was merged as commit 0a120c694 and explicitly removed the reporting and fallback code requested by #5582.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5592 Remove Sentry and fallback error reporting (#5582) | snapcraft | merged | Merged PR #5592 as commit 0a120c694, removing Snapcraft Legacy's Sentry/Raven reporting, error-data prompts, and Launchpad fallback; closed #5582. | |
| #2187 errors: enable sentry by default | snapcraft | merged | Merged PR #2187 in commit f77a6c10a, enabling Sentry error reporting by default and adding SNAPCRAFT_ENABLE_SILENT_REPORTS for prompt-free reports. | |
| #1961 Sentry | snapcraft | merged | Merged PR #1961 as commit 364596087, adding confirmation-gated Sentry reports for snap builds and closing #1918. | |
| #1791968 Snapcraft lies when submission to sentry fails | snapcraft (launchpad) | closed | Snapcraft now handles Sentry submission failures gracefully instead of falsely reporting success. Fix merged in canonical/snapcraft#2271 via commit 859c111e5. | |
| #2242 Error communication improvements | snapcraft | merged | Merged in #2242 via commit 4cdf0c6c2, printing tracebacks when Raven is unavailable and clarifying that internal errors should be reported to Snapcraft. |