Commit bbb17ea1 authored by
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.
Showing with 93 additions and 20 deletions
changelogs/unreleased/60149-nameerror-uninitialized-constant-sentry-client-sentryerror.yml 0 → 100644