errors: add ability to send stack traces to sentry
Metadata
Current evaluation
PR #1947 was closed unmerged and superseded by #1961, merged as commit 364596087 with confirmation-gated Sentry traceback reporting for #1918.
Resolution: closed superseded
Reason: The proposed implementation was replaced by PR #1961. That PR merged as commit 364596087 and delivered the equivalent Sentry reporting feature while closing #1918.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Adds the ability to send reports, asking for confirmation before doing
so. This feature is only enabled for the deb as raven is not provided in
`xenial` and most of the user base will be using the snap.
Closes: #1918
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)?
- [x] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)?
- [x] Have you successfully run `./runtests.sh static`?
- [x] Have you successfully run `./runtests.sh unit`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | PR #1947 was closed unmerged and superseded by #1961, merged as commit 364596087 with confirmation-gated Sentry traceback reporting for #1918. | |
| stealth/space-bunny-alpha | — | closed superseded | PR #1947 (sentry error reporting) was closed unmerged after changes were requested; the same feature landed via PR #1961, merged as commit 364596087, closing issue #1918. | |
| stealth/space-bunny-alpha | — | closed superseded | PR #1946 was closed unmerged after changes were requested; equivalent Sentry traceback reporting landed through #1961 in commit 364596087. | |
| qwen/qwen3.6-35b-a3b | — | — | Feature to send stack traces to Sentry was closed without merging. Reviewers requested changes, leaving 14 comments unresolved. Implementation targeted only the deb package due to dependency constraints, but the pull request was ultimately abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged implementation adding optional stack trace reporting to Sentry with user confirmation, restricted to deb packages due to dependency constraints. Resolves #1918. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
snapcraft#1961
(confidence 99%)
Merged replacement implementation in commit 364596087.
-
Related To:
snapcraft#1918
(confidence 98%)
Original feature request closed by the replacement implementation.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1946 errors: add ability to send stack traces to sentry | snapcraft | closed | Sentry traceback reporting in #1946 was superseded by merged PR #1961, which landed as commit 364596087 with confirmation-gated error reports and closed #1918. | |
| #2036 errors: remove stack data when sending to sentry | snapcraft | merged | Merged PR #2036 removed stack data from Sentry reports, reducing accidental disclosure of local filesystem paths, in commit 96ccad81c. | |
| #2069 Reports | snapcraft | merged | Merged PR #1961 via commit 364596087, adding Sentry traceback reporting with user confirmation prompts and closing issue #1918. | |
| #1961 Sentry | snapcraft | merged | Merged PR #1961 as commit 364596087, adding confirmation-gated Sentry reports for snap builds and closing #1918. |