diff options
author | Peter Leitzen <pleitzen@gitlab.com> | 2019-04-07 10:51:36 +0300 |
---|---|---|
committer | Michael Kozono <mkozono@gmail.com> | 2019-04-07 10:51:36 +0300 |
commit | bbb17ea1ea619664b362a9c984da45b940c412a2 (patch) | |
tree | 617df6d7bd4186c7f1eec0374e975375323d20b9 /changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml | |
parent | ae91b3219aa0b5de20e3452126384341acef75c6 (diff) |
Handle possible HTTP exception for Sentry client
Prior this commit exceptions raised during a HTTP request
weren't caught by the Sentry client and were passed to the user.
In addition the Sentry client tried to catch a non-existent error
`Sentry::Client::SentryError`.
Now, the Sentry client catches all possible errors coming from
a HTTP request.
Diffstat (limited to 'changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml')
-rw-r--r-- | changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml b/changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml new file mode 100644 index 00000000000..8c3a47cf62c --- /dev/null +++ b/changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml @@ -0,0 +1,5 @@ +--- +title: Handle possible HTTP exception for Sentry client +merge_request: 27080 +author: +type: fixed |