[PR #149] [CLOSED] Add support for Sentry panic reporting #811

New issue

Closed

opened 2026-02-27 20:00:03 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:00:03 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/librespot-org/librespot/pull/149
Author: @sashahilton00
Created: 2/12/2018
Status: ❌ Closed

Base: master ← Head: error_reporting

📝 Commits (1)

024cde4 Add support for Sentry panic reporting

📊 Changes

3 files changed (+384 additions, -4 deletions)

View changed files

📝 Cargo.lock (+359 -4)
📝 Cargo.toml (+1 -0)
📝 src/main.rs (+24 -0)

📄 Description

Ok, so the folks over at Sentry.io have given us a FOSS account for the project, allowing us to transparently collect panics when they occur in librespot. Members of librespot-org should be able to sign in and view reported issues, which should aid in triaging and fixing errors/bugs in the long run. Reporting requires no input from users, it is done automatically in the background. However, I'd like views on whether we want to add this, as doing so increases the size of the binary by approx. 5MB in debug mode, due to the need for TLS to secure communication. Also, if people don't feel that this will be useful, we shouldn't bother merge it. Thoughts?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/librespot-org/librespot/pull/149 **Author:** [@sashahilton00](https://github.com/sashahilton00) **Created:** 2/12/2018 **Status:** ❌ Closed **Base:** `master` ← **Head:** `error_reporting` --- ### 📝 Commits (1) - [`024cde4`](https://github.com/librespot-org/librespot/commit/024cde4d959d4bd8ba87f0685d1de0ef1d08da83) Add support for Sentry panic reporting ### 📊 Changes **3 files changed** (+384 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+359 -4) 📝 `Cargo.toml` (+1 -0) 📝 `src/main.rs` (+24 -0) </details> ### 📄 Description Ok, so the folks over at Sentry.io have given us a FOSS account for the project, allowing us to transparently collect panics when they occur in librespot. Members of librespot-org should be able to sign in and view reported issues, which should aid in triaging and fixing errors/bugs in the long run. Reporting requires no input from users, it is done automatically in the background. However, I'd like views on whether we want to add this, as doing so increases the size of the binary by approx. 5MB in debug mode, due to the need for TLS to secure communication. Also, if people don't feel that this will be useful, we shouldn't bother merge it. Thoughts? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>