You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2017/12/05 17:16:00 UTC

[jira] [Assigned] (SENTRY-2085) Sentry error handling exposes SentryGroupNotFoundException externally

     [ https://issues.apache.org/jira/browse/SENTRY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Peña reassigned SENTRY-2085:
-----------------------------------

    Assignee: Zach Amsden

> Sentry error handling exposes SentryGroupNotFoundException externally
> ---------------------------------------------------------------------
>
>                 Key: SENTRY-2085
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2085
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Zach Amsden
>            Assignee: Zach Amsden
>         Attachments: SENTRY-2085.001.patch, SENTRY-2085.002.patch
>
>
> The fix for SENTRY-769 allowed better differentiation of Sentry errors but also unnecessarily leaked exceptions outside of well defined API components.  This happens because the exception chosen, SentryGroupNotFoundException was created of a subclass of RuntimeError, allowing it to propagate past API boundaries without 'throws' or 'catch' clauses.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)