mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #524] Non optional dependency on Sentry #372
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#372
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @X-Ryl669 on GitHub (Jan 18, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/524
Currently, the last version added a dependency on Sentry that's not optional.
This sends logs of exception to an account on sentry.io (@phanan, is it your account ?)
Why did not you use LERN instead (since this allow to send the exceptions to email for example if one wanted this) ?
How do you disable this ?
Worst, now the exceptions while developing on my branch will be sent to Sentry's servers, then you (you probably don't care about them, but I do).
This adds a huge sniffer in the code, they get my server name, and all the list of my songs.
Example of what it sends to them:
Honestly, using Sentry should be a personal stuff you set on your/my development branch not something that's on for all user without them knowing about the sniffer.
Also, on Javascript side, I can not use the "Break on uncaught exception" anymore, since Raven/Sentry is catching all of them, so I can't even deal with those exception by myself.
@phanan commented on GitHub (Jan 19, 2017):
Sentry is an experiment, and it's meant for production to help me learn more about the various errors occurred with Koel in different environments. In all honesty, though, it didn't help that much (and the problems with dev, too), so I'm about to remove it myself as well.
@X-Ryl669 commented on GitHub (Jan 19, 2017):
Thanks.